Billing Settings

When a billing cap is applied to a project, this field controls whether PSA is allowed to automatically split billing events in order to bill closer to the billing cap. For example, if you are releasing a billing event with a value of 1000 but the amount remaining in the project's bookings is 250, PSA can split the billing event and release items that together do not exceed the value of 250. The unreleased items are saved to a new billing event.

Select this field if you want to prevent PSA from splitting billing events automatically.

For more information, see Releasing Single Billing Events When Billing Is Capped.

When selected, an email is sent when a billing event mass process, such as Generate, Release, Combine, and so on is successful.

You can add a value that references the API name of a Budget object's custom field set, where you have defined the fields to be displayed in:

• The Select Budgets grid within the Generate Billing Events windows.

• The table on the Budgets tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Expense object's custom field set, where you have defined the fields to be displayed in:

• The Select Expenses grid within the Generate Billing Events windows.

• The table on the Expenses tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Milestone object's custom field set, where you have defined the fields to be displayed in:

• The Select Milestones grid within the Generate Billing Events windows.

• The table on the Milestones tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Miscellaneous Adjustment object's custom field set, where you have defined the fields to be displayed in:

• The Select Miscellaneous Adjustments grid within the Generate Billing Events windows.

• The table on the Miscellaneous Adjustments tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Timecard Split object's custom field set, where you have defined the fields to be displayed in:

• The Select Timecard Splits grid within the Generate Billing Events windows.

• The table on the Timecards tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Budget object's custom field set, where you have defined the fields to be displayed in:

• The Select Budgets filters within the Generate Billing Events windows.

• The filters on the Budgets tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Expense object's custom field set, where you have defined the fields to be displayed in:

• The Select Expenses filters within the Generate Billing Events windows.

• The filters on the Expenses tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Milestone object's custom field set, where you have defined the fields to be displayed in:

• The Select Milestones filters within the Generate Billing Events windows.

• The filters on the Milestones tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Miscellaneous Adjustment object's custom field set, where you have defined the fields to be displayed in:

• The Select Miscellaneous Adjustments filters within the Generate Billing Events windows.

• The filters on the Miscellaneous Adjustments tab on the Project Billing and Account Billing pages.

You can add a value that references the API name of a Timecard Splits object's custom field set, where you have defined the fields to be displayed in:

• The Select Timecard Splits filters within the Generate Billing Events windows.

• The filters on the Timecards tab on the Project Billing and Account Billing pages.

If true, billing events and batches remain open when using the Projects Awaiting Billing and Billing Event Generation tabs. Any new billing event and its items are appended to an existing generated billing event or batch that matches its account, project and currency.

If false, separate billing events or batches are created.

If this option is true when releasing billing events and batches using the Billing Event Generation tab, a billing event that is part of a failed release batch job is treated in one of the following ways:

• A billing event and its items are appended to an existing billing event or batch if the billing event’s account, project and currency match an existing, generated billing event.

  The merged billing event or batch and its items are then ready to be released.

• A new billing event or batch is generated if one of the following conditions applies:
  • The billing event’s account, project, and currency do not match an existing, generated billing event.
  • The billing event’s account, project, and currency match an existing, generated billing event, but it is already being released.

A release is blocked if one or more billing events match the combination of region, practice, group, account, currency or time period of an active billing event generation. You could reduce the number of billing events to release, or release when generation of the current billing events and batches has completed.

When any generation or release job completes, the Billing Event Generation tab is refreshed. If this happens when you are selecting filters for generation or billing events for release, your selections are lost.

Before selecting items for generation or release, we recommend that you check the processing status of current jobs.

For project and account billing, billing events can be added to open billing event batches.

See also the time period setting ignoreTimePeriodWhenAppendingItems

You can add a value that references the API name of a Billing Event object's custom field set, where you have defined the fields to be displayed on the Billing Event Generation page.

You can add a value that references the API name of a Billing Event Batch object's custom field set, where you have defined the fields to be displayed on the Billing Event Generation page.

You can add a value that references the API name of a Billing Event Item object's custom field set, where you have defined the fields to be displayed on the Billing Event Generation page.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when clearing billing.

For more information, see Customizing Billing Processes.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when combining billing events.

For more information, see Customizing Billing Processes.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when invoicing billing events.

For more information, see Customizing Billing Processes.

Name of the namespace prefix of the custom classes that implement the various billing interfaces. You can use this option to customize the billing invoice process in PSA.

For more information, see Customizing Billing Processes.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when recalculating billing.

For more information, see Customizing Billing Processes.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when releasing billing events.

For more information, see Customizing Billing Processes.Customizing Billing Processes.

When using the PSA API for billing, you can add a value for the name of the class that the API uses when removing billing events.

For more information, see Customizing Billing Processes.

Billing Event Generation tab only.

The format of the billing event item Description field for budget records, where {0} is the Actual Date field from the record.

Billing Event Generation tab only.

The format of the billing event item Description field for expense records, where {0} is the resource name and {1} is the expense date. For example, Joe Bloggs on 02/02/2012.

If true, and useFlexiblePeriodMode is also true, billing events are generated for eligible business records that fall only within time periods that are completed on or before the specified cutoff date.

Example: If the cutoff date is April 29 and the time period type is Month, billing is generated for eligible business records that fall on or before March 31. Items dated April 1 or later are not included because the monthly time period of April is not complete on April 29.

When true, all projects that belong to a master project are grouped, usually into the same billing event, which references the record ID of the master project that the billing event belongs to. Other configurations for appending, and the billing event batch groupings on account, currency and time period are still respected.

This setting works for all billing methods.

If true, and appendGeneratedItems is true, billing events are appended to existing billing event batches that match the account and currency, regardless of time period.

For project and account billing, billing events can be added to open billing event batches, regardless of the time period.

maxBEIsPerBE

The number of billing event items that can be added to a billing event is unlimited, but you can set a maximum. If this is exceeded, more than one billing event is generated.

Limits the set of records included when generating billing events on the Billing Event Generation or Projects Awaiting Billing tabs.

When including prior periods, defines the number of days prior to the end of the selected period to generate billing events for.

When scheduling a billing event and including prior periods, defines the number of days prior to the selected period for which to generate billing events for billing event items.

Billing Event Generation tab only.

The format of the billing event Description field for milestone records, where {0} is the Actual Date field from the record.

Billing Event Generation tab only.

The format of the billing event item Description field for miscellaneous adjustment records, where {0} is the Description field from the record.

The number of time periods to be displayed in the Time Period drop-down list on the Billing Event Generation or Projects Awaiting Billing tabs, when generating billing events.

If true, budget pre-bill amounts are generated into separate billing events from other eligible business record types.

If true, expenses are generated into separate billing events from other eligible business record types.

Enables further separation of expenses when separateExpenses is true.

Add a value for each separate billing event that is to be created. Each value must contain a comma separated list that contains the expense types to include in the billing event. You must also enter a sort order for the billing events.

Expense types that are not listed in the value are included on an ordinary billing event.

If true, milestones are generated into separate billing events from other eligible business record types.

If true, miscellaneous adjustments are generated into separate billing events from other eligible business record types.

If true, timecard splits are generated into separate billing events from other eligible business record types.

Billing Event Generation tab only.

The format of the billing event description field for timecard records, where {0} is the resource name, {1} is the start date, {2} is the end date, and {3} is the total hours or days. For example Beth Gomez between 2021-8-15 and 2021-8-21 for 38.0 total hours/days.

If set, and unitTypeSubfiltersis true, defines the first Region, Practice, and Group (RPG) selector in the Generate Billing Events section of the Billing Event Generation tab.

If set, and unitTypeSubfilters is false, defines whether the Region, Practice or Group selector is shown by default.

If true, all of the Region, Practice, and Group (RPG) selectors are shown in the Generate Billing Events section of the Billing Event Generation tab.

If false, only the Region selector is shown by default.

You can also use this with unitType.