FSM Journal Entry Record

In Field Service Management (FSM), a journal entry is a standard NetSuite accounting transaction that records debits and credits against general ledger accounts. FSM Project Labor Cost Posting uses it to record labor costs associated with a project.

The journal stores the resulting accounting amounts and line attribution. The source time bills retain their own time, hourly cost, and costing indicator. For information about calculation, time eligibility, and posting behavior, see FSM Project Labor Cost Posting.

Record Information

These identifiers distinguish the native record from its FSM model and from transaction search fields.

Property	Value
Record type	Standard NetSuite
Record name	Journal Entry
Record ID	`journalentry`
FSM model	`models/journal`
Record identity	Internal ID (`internalid`). Entry No. (`tranid`) is the displayed transaction number.
Posting lines	Native Lines sublist (`line`).
Transaction search type value	`Journal`. This search value differs from the record ID `journalentry` and model ID `models/journal`.

Property

Value

Record type

Standard NetSuite

Record name

Journal Entry

Record ID

journalentry

FSM model

models/journal

Record identity

Internal ID (internalid). Entry No. (tranid) is the displayed transaction number.

Posting lines

Native Lines sublist (line).

Transaction search type value

Journal. This search value differs from the record ID journalentry and model ID models/journal.

Journal entry search data uses NetSuite Transaction search fields. For example, the FSM model reads debitamount and creditamount and writes the line fields debit and credit. Model attribute names and search column names are not interchangeable with saved field IDs. For information about journal entry fields, see Journal Entry - SuiteScript reference. For FSM model mappings, see FSM Record Model Configuration (models/journal).

Forms

Use the standard NetSuite Journal form or an account-created custom Journal form. FSM doesn't supply a dedicated journal entry form. A custom form can present the relevant accounting and Field Service columns without changing their underlying field identities.

NetSuite preferred-form settings affect initial form selection. Journal entry custom forms also support Store Form with Record. When the Store Form with Record box is checked, entries created with that form display the stored form when viewed or edited. See Custom Transaction Forms Properties and Storing Custom Forms with Transactions.

For journal entries created through models/journal, prototype.defaults.customform can supply an account-created custom form's internal ID. The standard journal model assigns no form ID. This creation default doesn't change the form of existing journals. See Custom Forms for Record Creation.

Record Relationships

The journal holds its accounting attribution on individual lines. The supplied FSM reference fields are separate from the native Name and Account fields. In the tables, a reference such as line.entity means field entity on sublist line, rather than a body-field ID.

Related Record	Relationship and Field ID	Purpose
Project	Journal line Name (`line.entity`) references the project in FSM labor-cost entries.	Associates the debit line with the project. More than one line or journal can identify the same project.
Account	Each journal line Account (`line.account`) references a ledger account.	Identifies the account receiving that line's debit or credit.
CRM task	Journal line Field Service Task (trans) (`custcol_nx_task`) references a CRM task (`task`).	Retains the source time bill's FSM Task reference on the labor-cost debit line when a reference is available.
Asset	Journal line Field Service Asset (trans) (`custcol_nx_asset`) references a Field Service Asset (`customrecord_nx_asset`).	Attributes the line to equipment or a service site. The labor-cost debit line receives the asset reference from the source time bill when available.
Case	Journal line Field Service Case (trans) (`custcol_nx_case`) references a case (`supportcase`).	Supplied optional column whose field definition sources the case from the selected CRM task. Labor posting doesn't explicitly copy a case value.
Project task	Journal line Field Service Project Task (trans) (`custcol_nx_projecttask`) references a project task (`projecttask`).	Supplied optional column, distinct from the CRM task column. Labor posting doesn't explicitly copy a project task value.
Subsidiary	Journal body Subsidiary (`subsidiary`) references a subsidiary in OneWorld.	Identifies the accounting subsidiary. FSM labor posting supplies this value from the project.
Time bill	The source time bill stores Customer/Project (`customer`), FSM Task (`custcol_nx_task`), Asset (`custcol_nx_asset`), and Time Costed (`custcol_nx_time_costed`).	Supplies costing input and the separate costing result. The standard FSM action stores no source time bill ID on a journal line and no resulting journal ID on the time bill.

Related Record

Relationship and Field ID

Purpose

Project

Journal line Name (line.entity) references the project in FSM labor-cost entries.

Associates the debit line with the project. More than one line or journal can identify the same project.

Account

Each journal line Account (line.account) references a ledger account.

Identifies the account receiving that line's debit or credit.

CRM task

Journal line Field Service Task (trans) (custcol_nx_task) references a CRM task (task).

Retains the source time bill's FSM Task reference on the labor-cost debit line when a reference is available.

Asset

Journal line Field Service Asset (trans) (custcol_nx_asset) references a Field Service Asset (customrecord_nx_asset).

Attributes the line to equipment or a service site. The labor-cost debit line receives the asset reference from the source time bill when available.

Case

Journal line Field Service Case (trans) (custcol_nx_case) references a case (supportcase).

Supplied optional column whose field definition sources the case from the selected CRM task. Labor posting doesn't explicitly copy a case value.

Project task

Journal line Field Service Project Task (trans) (custcol_nx_projecttask) references a project task (projecttask).

Supplied optional column, distinct from the CRM task column. Labor posting doesn't explicitly copy a project task value.

Subsidiary

Journal body Subsidiary (subsidiary) references a subsidiary in OneWorld.

Identifies the accounting subsidiary. FSM labor posting supplies this value from the project.

Time bill

The source time bill stores Customer/Project (customer), FSM Task (custcol_nx_task), Asset (custcol_nx_asset), and Time Costed (custcol_nx_time_costed).

Supplies costing input and the separate costing result. The standard FSM action stores no source time bill ID on a journal line and no resulting journal ID on the time bill.

The standard labor-cost credit line doesn't receive the project, task, or asset references. Interpret attribution at line level rather than treating those links as journal-wide relationships. For the complete allocation behavior, see Accounting Attribution.

An account-created link doesn't automatically add journal data to FSM Mobile, service history, reports, inheritance, or synchronization. Those uses require their own supported configuration and behavior.

FSM Fields

The tables identify the supplied English labels and useful field IDs. Account labels and form presentation can differ. Unless identified as FSM custom fields, the fields are native NetSuite data.

Accounting Data

These fields describe the journal and its posting lines. Line fields belong to the line sublist.

Field	Field ID	Purpose and Key Values
Date	`trandate`	Journal transaction date. The standard FSM labor action doesn't derive it from time bill dates. NetSuite creation defaults apply unless a configured creation default supplies a value.
Currency	`currency`	Currency of journal amounts. When Multiple Currencies is enabled, FSM labor posting supplies the project's currency.
Exchange Rate	`exchangerate`	Native transaction exchange rate used by NetSuite accounting. It is separate from the time bill's saved hourly cost.
Posting Period	`postingperiod`	Native accounting period. NetSuite accounting preferences and approval rules determine its treatment.
Account	`line.account`	Ledger account for the line. For posting account configuration, see Configuring FSM Project Labor Cost Posting.
Debit / Credit	`line.debit`, `line.credit`	Monetary amounts in the journal currency, not hours or hourly rates. FSM creates a balanced debit/credit pair for each selected time bill.
Memo	`line.memo`	Line description. Available time bill memo values are supplied to both lines of the labor-cost pair.
Department / Class / Location	`line.department`, `line.class`, `line.location`	Accounting classifications. FSM carries available time bill values to both lines when the corresponding NetSuite features are enabled. Location here is an accounting Location, not the asset's service-address text.

Field

Field ID

Purpose and Key Values

Date

trandate

Journal transaction date. The standard FSM labor action doesn't derive it from time bill dates. NetSuite creation defaults apply unless a configured creation default supplies a value.

Currency

currency

Currency of journal amounts. When Multiple Currencies is enabled, FSM labor posting supplies the project's currency.

Exchange Rate

exchangerate

Native transaction exchange rate used by NetSuite accounting. It is separate from the time bill's saved hourly cost.

Posting Period

postingperiod

Native accounting period. NetSuite accounting preferences and approval rules determine its treatment.

Account

line.account

Ledger account for the line. For posting account configuration, see Configuring FSM Project Labor Cost Posting.

Debit / Credit

line.debit, line.credit

Monetary amounts in the journal currency, not hours or hourly rates. FSM creates a balanced debit/credit pair for each selected time bill.

Memo

line.memo

Line description. Available time bill memo values are supplied to both lines of the labor-cost pair.

Department / Class / Location

line.department, line.class, line.location

Accounting classifications. FSM carries available time bill values to both lines when the corresponding NetSuite features are enabled. Location here is an accounting Location, not the asset's service-address text.

Hours and hourly cost remain on the time bill. The journal amount calculation and its lack of hourly-cost currency conversion are explained in FSM Project Labor Cost Posting.

Field Service References and Compatibility Data

The following table lists five stored custom fields, all optional in the supplied field definitions. None has a fixed initial value. Sourcing and values supplied by a creation action are separate from a fixed field default.

Field	Field ID	Purpose and Key Values
Field Service Task (trans)	`custcol_nx_task`	CRM task reference on a line. It is not the Project Task field.
Field Service Asset (trans)	`custcol_nx_asset`	Asset reference on a line. Its supplied sourcing uses the selected CRM task's Field Service Task Asset (`custevent_nx_task_asset`). Labor posting supplies the saved time bill Asset explicitly.
Field Service Case (trans)	`custcol_nx_case`	Case reference on a line, with supplied sourcing from the selected CRM task's native Case relationship.
Field Service Project Task (trans)	`custcol_nx_projecttask`	Project task reference on a line. Availability of this column doesn't mean the labor action populates it.
Field Service Idempotency Key	`custbody_nx_idempotency_key`	Identity field retained for compatibility and visibility. The standard labor-posting action doesn't assign a key to this field.

Field

Field ID

Purpose and Key Values

Field Service Task (trans)

custcol_nx_task

CRM task reference on a line. It is not the Project Task field.

Field Service Asset (trans)

custcol_nx_asset

Asset reference on a line. Its supplied sourcing uses the selected CRM task's Field Service Task Asset (custevent_nx_task_asset). Labor posting supplies the saved time bill Asset explicitly.

Field Service Case (trans)

custcol_nx_case

Case reference on a line, with supplied sourcing from the selected CRM task's native Case relationship.

Field Service Project Task (trans)

custcol_nx_projecttask

Project task reference on a line. Availability of this column doesn't mean the labor action populates it.

Field Service Idempotency Key

custbody_nx_idempotency_key

Identity field retained for compatibility and visibility. The standard labor-posting action doesn't assign a key to this field.

This field doesn't indicate posting progress or prevent repeat posting by the standard labor-posting action.

Approval and Costing Indicators

Journal approval and time bill costing describe different records and different results.

Field or Indicator	Stored On	Meaning
Approved (`approved`) / Approval Status (`approvalstatus`)	Journal entry	Native indicators that reflect journal approval according to the account's approval setup. These indicators don't show the status of FSM processing.
Field Service Time Costed (`custcol_nx_time_costed`)	Time bill	Hidden costing marker, cleared by default. FSM sets the marker after saving the labor-cost journal entry.

Field or Indicator

Stored On

Meaning

Approved (approved) / Approval Status (approvalstatus)

Journal entry

Native indicators that reflect journal approval according to the account's approval setup. These indicators don't show the status of FSM processing.

Field Service Time Costed (custcol_nx_time_costed)

Time bill

Hidden costing marker, cleared by default. FSM sets the marker after saving the labor-cost journal entry.

The marker doesn't identify the journal entry or confirm its approval or posting to the general ledger.

The standard FSM journal definition has no dedicated labor-posting pending, running, completed, or error-reference field. A saved journal entry confirms that the transaction exists. Evaluate the source time bills' costing indicators and the journal entry's native approval state separately. For approval behavior, see Journal Entry Approval Overview. For partial failures and repeated posting, see Processing Model and Lifecycle.

Creation and Update Sources

The creation source determines which values are supplied. Native accounting validation and account customizations still apply.

Source	Record Effect
FSM Project Labour Cost Posting	Creates a journal entry from eligible time for one project and supplies its posting lines and attribution. Time bill costing updates are separate operations.
NetSuite journal entry, copy, import, or scripting	Creates or updates the native transaction using the selected entry mechanism. A manually created journal doesn't itself set the FSM costing indicator on related time bills.
NetSuite approval and accounting processing	Maintains the journal's native approval and posting treatment.

Source

Record Effect

FSM Project Labour Cost Posting

Creates a journal entry from eligible time for one project and supplies its posting lines and attribution. Time bill costing updates are separate operations.

NetSuite journal entry, copy, import, or scripting

Creates or updates the native transaction using the selected entry mechanism. A manually created journal doesn't itself set the FSM costing indicator on related time bills.

NetSuite approval and accounting processing

Maintains the journal's native approval and posting treatment.

Editing, reversing, or deleting a journal doesn't automatically reset the source time bills' FSM Time Costed flag. The FSM labor action also doesn't amend an earlier journal when source time changes. See Limitations and Constraints for those boundaries.

Used by FSM Features

These capabilities create journal data or use its accounting attribution.

Feature	Record Use
FSM Project Labor Cost Posting	Creates the labor-cost journal and updates the selected source time bills.
FSM Profitability Reporting	Provides shortcuts to financial reports. The selected report's accounts, periods, approval and posting treatment, and criteria determine which journal data appears. Asset attribution uses the asset reference on the transaction line.

Feature

Record Use

FSM Project Labor Cost Posting

Creates the labor-cost journal and updates the selected source time bills.

FSM Profitability Reporting

Provides shortcuts to financial reports. The selected report's accounts, periods, approval and posting treatment, and criteria determine which journal data appears. Asset attribution uses the asset reference on the transaction line.

Record Constraints and Data Requirements

A journal must satisfy NetSuite accounting validation, including valid line accounts and equal total debits and credits. Currency, subsidiary, classifications, and other requirements depend on the account's enabled features and accounting setup. See Journal Entries Overview.

The supplied FSM line relationships are not required on every journal entry. Requirements imposed by a custom form, account customization, or a specific posting capability are additional to the supplied field definitions. A valid saved journal is not proof that all time bill costing updates succeeded or that the journal has completed approval.