Recalculating Billing Events

If you change certain information for a timecardClosed A mechanism for logging time against a project or an assignment., milestoneClosed A fixed target, which when achieved, can be billed to the customer for a fixed fee or by logging time against it., expenseClosed A record of expenses incurred by resources assigned to a project or opportunity., or miscellaneous adjustmentClosed A catch-all business record that allows you to correct data entry errors or adjust transactions. that is included in a billing eventClosed A means of generating billing information that can be fed into a financial system which has not yet been released, you should recalculate the billing event to make sure it matches the changed record. You will not be able to release the billing event if it no longer matches the business record.

Recalculate the billing event if any of the following information changes:

  • A timecard's amount, bill rate, budget allocation, customer reference, description, quantity, project, or start date.
  • A milestone's actual date, amount, budget allocation, customer reference, description, or project.
  • An expense's billing amount, budget allocation, customer reference, description, expense date, project, or type.
  • A miscellaneous adjustment's amount, budget allocation, customer reference, description, effective date, or project.
Note:

A business record's customer reference is derived from the customer purchase order budget or billable expenses budget that the record is allocated to via its budget allocation.

To recalculate billing details:

  1. On the Billing Event page, click Recalculate Billing.
  2. Read the information message.
  3. Click Recalculate Billing to continue.

If you want to recalculate multiple billing events, use the Billing Events Awaiting Release tab. For more information, see Billing Events Awaiting Release Tab.

Note:

You cannot undo the Recalculate Billing action.

When multiple billing events are recalculated simultaneously, the Apex Flex Queue may reach its limit of 100 batch jobs. To avoid batch jobs failing to start, PSA uses the asynchronous framework to initiate a callable that checks for available space in the Flex Queue before starting a batch job.

For more information, see Managing Billing Events When Apex Flex Queue is Full.