Automatic Time Bill Processing in FSM
Field Service Management (FSM) creates automatic time bills from service Start and Complete activities. For prerequisites, capture behavior, and restrictions, see FSM Service Time Tracking.
Automatic tracking must be enabled, and the CRM task's task type must have a Service Time Item. The activity dates and times must produce a positive duration.
FSM rounds the calculated duration to two decimal places in hours. It creates no automatic time entry when the selected activity values are missing or do not produce a positive duration after rounding. The Hours limits on the Time tab do not cap this calculated interval.
FSM creates a time bill for each distinct employee in the task's assigned employee and team at processing time. Each entry uses the calculated interval. The employee who captured an activity is not the sole basis for selecting the time bill employee.
FSM compares the required entries with existing automatically generated entries using the task, employee, and captured start and completion values. It creates missing entries and leaves existing matches unchanged.
Reopening a task or changing its activities does not reverse existing time bills. If processing is requested again for a different captured interval, additional entries can be created. The earlier entries are not replaced.
Processing Requests and Results
For a tracked task type, a change to Task Type or the task's Field Service End timestamp can check the Field Service Log Activity Time box (custevent_nx_time_log_activities). Both values must be present. When a task save changes this box to checked, FSM requests background time processing. Account maintenance can also request time processing. The time processor selects tasks with the box checked.
The following table explains what capture, processing, and time-entry results establish.
|
Stage or Result |
Meaning for Time Tracking |
|---|---|
|
Start or Complete captured in FSM Mobile |
Local task and activity data have been captured. This does not prove that their separate synchronization requests have succeeded. |
|
Field Service Log Activity Time checked |
The task is awaiting time processing. The box does not indicate a currently running script. |
|
Time processing runs |
FSM evaluates the task's activities and creates missing qualifying time bills when automatic tracking is enabled. |
|
Field Service Log Activity Time cleared |
The processing action finished its assessment. This can happen without creating a time bill, including when tracking is disabled or no qualifying interval exists. |
|
Time bill present |
The time entry exists in NetSuite. Check its employee, hours, service item, and task to identify the result. |
The associated deployment is Field Service Scheduled : Time (customdeploy_nx_time). Use its execution status and logs to distinguish a pending task request from an execution in progress. For deployment and monitoring details, see FSM Script Reference.
After time processing clears the request, FSM requests status processing. An In Progress task with a Field Service End timestamp and a cleared activity-time box can then become Completed. This status result does not prove that time was created. See FSM Case and CRM Task Status Automation.
Errors and Outstanding Work
A failure before the time-processing request is cleared can leave the task awaiting processing and delay its NetSuite completion. An active, unrecovered error for the same processing action can prevent another attempt in a later execution. Other eligible task actions can still run, and entries already created before a failure remain saved.
Some errors become eligible for a later attempt after a delay. Eligibility does not guarantee that another execution will run or succeed. For error meanings and recovery states, see FSM Error Record. For shared execution and retry behavior, see FSM Script Reference.