Configuring FSM Case Unbilled Amount Calculation
Case unbilled calculation has no feature-specific JSON switch, formula, or source-filter setting. Its amounts depend on linked source records and their billable values. Use this page to locate the related setup that affects those inputs. For the capability and processing behavior, see FSM Case Unbilled Amount Calculation.
Properties and Defaults
The following table lists the source inputs and record fields that affect unbilled amounts.
|
Property or Setting |
Location |
Accepted Value |
Default |
Calculation Basis |
Effect |
|---|---|---|---|---|---|
|
Billable time setup |
Time bills and the Billing Rule field on tasks |
Supported billing and time setup |
Standard Billing Rule behavior, when applicable. |
Rate × decimal hours |
Affects qualifying time amounts. For billing options, see Configuring FSM Billing Rules. |
|
Expense Reports feature and billable lines |
Enable Features page and expense reports |
Expense Reports feature enabled and billable expense lines linked to the case |
Account and transaction values. |
Transaction amount excluding tax |
If the Expense Reports feature is disabled, Unbilled Expenses is zero. |
|
Field Service Case link |
Sales Order |
Case record |
Transaction value. |
- |
Associates the sales order's Amount Unbilled value with the case. |
|
Field Service Case Type |
Case |
Case type record |
Case value. |
- |
Required for background case selection. |
|
Update Unbilled |
Case |
Checked box |
Record- |
- |
Requests recalculation. This request does not change the calculation or indicate that a script is running. |
Changing the Source Setup
There is no JSON override required to enable a different calculation. Configure billable outcomes and related time or expense inputs in Configuring FSM Billing Rules. Preserve case and task links when changing supported record-model mappings. For more information, see FSM Record Model Configuration.
Case invoicing uses separate rules to select charges and create transactions, so the unbilled summary does not determine which records are invoiced. For invoicing settings, see Configuring FSM Case Invoicing.
Dependencies and Customization Limits
The calculation has no supported JSON overrides for enablement, formulas, or source filters.
A processing request can remain pending. Background processing excludes a case with a matching active error that has not been recovered. For request states and error-selection criteria, see FSM Case Unbilled Amount Calculation. For shared error and script details, see Field Service Error Record and FSM Script Reference. Changing processing fields is not a substitute for configuring the source data.
When Changes Apply
Source setup and source-record changes affect later recalculation. Previously saved case totals can remain until recalculation successfully writes the recalculated category values.