1. Field Service Management
  2. FSM Features
  3. FSM Consumable Processing
  4. FSM Consumable Billing Eligibility and Processing Lifecycle

FSM Consumable Billing Eligibility and Processing Lifecycle

Field Service Management (FSM) assesses linking, billing, and fulfillment work in separate phases. Completion of a customer relationship management (CRM) task can identify an eligible case, but transaction links and script execution have distinct meanings. For the overall flow and prerequisites, see FSM Consumable Processing.

Processing Requests and Eligibility

FSM requests consumable processing when a task with a Field Service Task Type is created as Completed or changes to Completed. It also requests processing when a consumable is created or changed under these conditions:

  • The consumable has a task.

  • The task is Completed and has a case.

  • The consumable has no Billing Transaction.

Requesting processing does not establish that the scheduled script is running or that transaction updates have finished.

When billing is enabled, the assessment selects cases through consumables with no Billing Transaction whose tasks are Completed. Consumables without a case do not identify an eligible case.

These conditions use the task's NetSuite status. For tasks that qualify for Track Service Time, FSM Mobile can show completion before that status becomes Completed. For completion processing, see FSM Case and CRM Task Status Automation.

Case Billing Scope

The billing operation collects consumables for the selected case that have no Billing Transaction. This collection does not apply a second task-status filter or filter out nonbillable entries.

The assessment condition differs from the collection condition because completion identifies eligible cases, and billing gathers unlinked consumables by case.

Important:

A completed task can make a case eligible for billing. Collection for that case can then include unlinked consumables associated with other unfinished tasks. Completing one task does not restrict the collection to that task's consumables.

Assessment Priority and Record Linking

FSM reassesses available work during scheduled processing. The following table shows the priority of the matching phases.

Priority

Matching Work

Processing Effect

1

A sales order line references a consumable, and the related case has no transaction.

Sets the case's transaction reference to the sales order.

2

A sales order line references a consumable whose Billing Transaction is blank.

Sets the consumable's Billing Transaction to that sales order.

3

Earlier phases have no actions, billing is enabled, and an eligible case has unlinked consumables.

Adds consumable lines to the case's sales order, attempts to transform another linked transaction into a sales order, or creates a sales order.

4

Earlier phases have no actions, fulfillment is enabled, and Locations is enabled.

Processes eligible sales order lines for fulfillment.

A phase runs when matching work exists. Initial billing can add lines before the link phases have work to complete. Later assessments complete the missing links before considering additional billing or fulfillment.

Linking the consumable to a sales order precedes the fulfillment phase. Billing Transaction therefore identifies the sales order and does not establish successful fulfillment.

Processing Visibility and Errors

The background deployment is Field Service Scheduled : Consumable, customdeploy_nx_consumable, under Field Service Scheduled, customscript_nx_scheduled. The runner requests another execution when its time or governance limits prevent it from processing the remaining assessed actions.

For deployment details and execution monitoring, see FSM Script Reference. For error fields and states, see Field Service Error Record.

The case processing banner can display Update Sales Order when the consumable assessment identifies work. This entry does not supply an execution status and does not establish that the script is running.

Active, unrecovered errors for this deployment can exclude a case from subsequent assessment. The exclusion includes cases associated with errors on their sales orders or consumable records.

The runner reports nonignored action failures through Field Service Error records. Record collisions are treated separately. The supplied consumable actions define no automatic retry pattern.

An execution with no assessed actions can finish even when cases excluded by errors still have incomplete work. Check the intended record results when assessing completion.

The following table distinguishes the evidence available on related records.

Record Evidence

Established Result

Verification Limit

Sales order line references the consumable.

The consumable has a transaction-line relationship.

This does not establish invoice creation or fulfillment.

Case transaction references the sales order.

The case has its sales order reference.

This does not establish that every consumable was processed.

Consumable Billing Transaction references the sales order.

The consumable has its sales order reference.

This does not establish that the item was fulfilled.

Related item fulfillment contains the intended lines and quantities.

Those lines and quantities were included in a fulfillment.

This does not establish that every sales order line was fulfilled.

Related Topics

General Notices