FSM Invoice Record

An invoice is a standard NetSuite billing transaction. Field Service Management (FSM) uses its customer, project, case, asset, and task references to connect billed items, time, and expenses to service work.

FSM Case Invoicing can create an invoice from an eligible sales order or from case details and available charges. The invoice stores the resulting transaction and its relationships. For information about source selection, billing eligibility, and invoice content, see FSM Case Invoicing.

Record Information

The following table summarizes the invoice record.

Property	Value
Record type	Standard NetSuite transaction
Record name	Invoice
Native record ID	invoice
Record identity	NetSuite Internal ID (internalid)
Display number	Invoice number (tranid)
FSM record model	models/invoice, derived from models/transaction
Supplied form	Field Service Invoice (custform_nx_invoice)

models/invoice identifies the FSM model and configuration area. transaction is the shared transaction base and search context, rather than a separate FSM invoice record. For more information about the native invoice record, see Invoice record reference.

Use the internal ID to identify a saved invoice. The displayed invoice number is not a substitute for a unique integration key. For more information, see Invoice Import.

Forms

The supplied Field Service Invoice form is based on the native Standard Service Invoice. Under Service Details, the form groups these optional header fields: Customer, Asset, Case, Task, and Project Task. It also shows the corresponding service references on item lines. The form requires Custom Form, native Customer/Entity, and Date.

The supplied form is not marked as preferred. You can use your own invoice forms and native form preferences. Form selection changes presentation and form requirements. It doesn't change the underlying field IDs. Preserve the service fields needed for the account's invoicing and reporting.

NetSuite always stores a custom invoice form with the transaction. Store Form with Record is not an optional setting for invoice forms. When the invoice is viewed or edited, NetSuite uses the stored form rather than the preferred form. See Storing Custom Forms with Transactions.

The standard invoice model has no default custom form ID. An invoice creation path doesn't necessarily select the supplied Field Service Invoice form. For information about model form defaults and form selection, see Custom Forms for Record Creation.

The standard FSM Mobile configuration has no editable invoice resource. Its Quote and Sales Order resources use different transaction records. Loading a NetSuite form to generate FSM Mobile elements is separate from storing the invoice's UI form. For information about generating FSM Mobile elements from a NetSuite form, see Form Properties.

Record Relationships

Header references describe the invoice as a whole. Line references describe an individual charge or item line. Each custom reference in the following table holds one related record. Several invoices or lines can reference the same service record.

The following table describes invoice relationships.

Related record	Relationship and field ID	Purpose
Customer	Invoice native Entity (entity) and Field Service Customer (custbody_nx_customer)	Identify the billing entity and FSM customer context. FSM keeps these values consistent through its transaction handling.
Project	Invoice native Project (job), or Entity (entity) in accounts without Project Management	Connect the transaction to its project context. The FSM project attribute writes to job with Project Management and to entity without it.
Case	Invoice Field Service Case (custbody_nx_case) references a native case (supportcase)	Connect the invoice to the service case. A case can have more than one linked invoice.
Asset	Invoice Field Service Asset (custbody_nx_asset) references an FSM asset (customrecord_nx_asset)	Identify the header's service equipment or site. This doesn't replace an individual line's asset reference.
CRM Task	Invoice Field Service Task (custbody_nx_task) references a CRM task (task)	Identify a task associated with the transaction. It doesn't list every task represented in the invoice's charges.
Project Task	Invoice Field Service Project Task (custbody_nx_projecttask) references a project task (projecttask)	Identify a project task context where the relevant NetSuite feature is enabled. Project task is distinct from CRM task.
Source Sales Order	Invoice native Created From (createdfrom) identifies the source transaction when the invoice is transformed from an order	Preserve the native source relationship. The case's Transaction selection is stored separately on the case in custevent_nx_case_transaction.
Service records on lines	Invoice line fields custcol_nx_task, custcol_nx_projecttask, custcol_nx_case, custcol_nx_asset, and custcol_nx_consumable	Attribute individual lines to service work and source usage. For field meanings, see the Line fields table.
Time Bills and expense charges	Invoice Billable Time and Billable Expenses contain charges from separate source records	Retain the distinction between the invoice and its billing sources. Default case invoice selection uses their CRM task references. A header case or customer link alone doesn't describe every source charge.

The case's selected Transaction, the invoice's case link, and native Created From are separate relationships. An invoice created from case details need not have a source sales order. A header asset, case, or task reference doesn't establish that every line has the same reference.

Account custom links remain account customizations. Adding a reference doesn't automatically provide FSM inheritance, FSM Mobile access, service history, reporting, or synchronization.

FSM Fields

Labels can differ between forms and accounts. The supplied form uses short labels such as Customer, Asset, Task (trans), and Asset (trans). Use the field IDs to distinguish native fields, header references, and line references.

Header Fields

The following table describes FSM header fields.

Field	Field ID	Meaning and important values
Field Service Customer	custbody_nx_customer	FSM customer reference, distinct from native Entity and the asset's owner. Invoice transaction handling synchronizes it with the native billing context.
Field Service Asset	custbody_nx_asset	Asset associated with the invoice. An associated CRM task or project task can supply this value.
Field Service Case	custbody_nx_case	Service case associated with the invoice. The supplied field can source the case from the selected header CRM task. Case-details invoice creation also supplies it directly.
Field Service Task	custbody_nx_task	Header CRM task reference. It is separate from task references on individual item, time, or expense lines.
Field Service Project Task	custbody_nx_projecttask	Header project task reference. The FSM model includes its mapping when Project Management is enabled.
Field Service Customer Signature	custbody_nx_customer_signature	Optional stored rich-text signature content. A populated value is not a payment or invoice-processing status.
Field Service Idempotency Key	custbody_nx_idempotency_key	Optional stored compatibility field for earlier creation identity. It is not the invoice number, a billing state, or proof of duplicate protection for Generate Invoice.

Line Fields

The following table describes FSM line fields.

Field	Field ID	Meaning and important values
Field Service Task (trans)	custcol_nx_task	CRM task associated with a line. Case Invoicing uses this reference on available time and expense charges. If the invoice column is unavailable, Case Invoicing looks up the reference on the source record.
Field Service Project Task (trans)	custcol_nx_projecttask	Project task associated with a line. It is distinct from the CRM task reference used by default case time and expense selection.
Field Service Case (trans)	custcol_nx_case	Case associated with a line. The supplied field sources the case from the line's CRM task. It is separate from the invoice's header case.
Field Service Asset (trans)	custcol_nx_asset	Asset associated with a line. The supplied field sources the asset from the line's CRM task. The supplied asset profitability report uses this line reference.
Field Service Consumable	custcol_nx_consumable	Reference to a Field Service Consumable (customrecord_nx_consumable) associated with the transaction line. It identifies source usage. It is not an invoice completion flag.

For time and expense selection, see FSM Case Invoicing. For source usage and asset financial attribution, see FSM Consumable Processing and FSM Profitability Reporting.

Native Fields Used by FSM

The following table describes native fields used by FSM.

Field	Field ID	FSM context
Customer/Entity and Project	entity, job	Native billing context. Project handling depends on the enabled NetSuite features and accounting preferences.
Created From	createdfrom	Source transaction for an invoice created by transformation.
Date	trandate	Transaction date. For an invoice created from case details, FSM supplies the date using the case's time zone.
PO/Check #	otherrefnum	Customer purchase-order reference. Case-details invoice creation supplies the case's PO number.
Email	email	Transaction email address. FSM can fill a blank value from the linked case.
Subsidiary	subsidiary	Native subsidiary context. Case-details creation supplies the case subsidiary when Multi-Subsidiary Customer is enabled.
Status	status	Native invoice business state. It doesn't indicate that FSM background processing is running or complete.
Amount Remaining / Amount Paid	amountremaining, amountpaid	Native payment amounts shown on the supplied invoice form. These amounts are separate from the case's unbilled summaries.
Item and Quantity	Item sublist item, quantity	Identify the billed item and its quantity. NetSuite billing and the selected source determine the available lines.

Processing Context

The invoice has no supplied FSM pending-unbilled checkbox or dedicated FSM execution-status field. Its linked case stores Field Service Update Unbilled (custevent_nx_unbilled_update). Under standard FSM handling, saving or deleting a case-linked invoice can request recalculation for that case.

The request and resulting calculation are separate from the invoice save. A saved invoice doesn't establish that the case totals were refreshed. See FSM Case Unbilled Amount Calculation for request, selection, and completion meanings, and FSM Script Reference for execution monitoring.

Creation and Update Sources

The following table describes invoice creation and update sources.

Source	Effect on the record
Native NetSuite Invoice entry, billing, import, or integration	Creates or updates the native transaction subject to NetSuite validation and the applicable account setup. An invoice's FSM fields don't automatically apply the selection rules for FSM Case Invoicing to these creation paths.
FSM Case Invoicing using a Sales Order	Creates an invoice by transforming the selected eligible source order. Native transformation supplies the available transaction content.
FSM Case Invoicing using Case details	Creates an invoice with the case's customer, case link, asset, PO number, and date context, plus the applicable project and subsidiary context.
FSM Invoice form and transaction handling	Supports customer and asset selection and synchronizes Customer and Entity. Sources the asset from a linked task and can fill a blank email address from the case.
Related Case transaction updates	Can update the project and case references of the transaction selected on a case through separate background handling. Saving a case doesn't prove that this related update completed.

The supplied script deployments use INVOICE as the deployment identifier for the native invoice record.

Invoice form handling uses Field Service User Event (customscript_nx_userevent, deployment customdeploy_nx_invoice_userevent) and Field Service Client (customscript_nx_client, deployment customdeploy_nx_invoice_client). Field Service Suitelet (customscript_nx_suitelet) handles the case invoice request. Associated case unbilled calculation uses Field Service Scheduled (customscript_nx_scheduled, deployment customdeploy_nx_unbilled). Script execution and deployment controls belong in FSM Script Reference.

Used by FSM Features

The following table describes how FSM features use invoices.

Feature	How the Invoice is used
FSM Case Invoicing	Stores the billing transaction created from an eligible order or case details.
FSM Customer and Asset Selection	Supports related customer and asset choices and transaction relationship sourcing.
FSM Case Unbilled Amount Calculation	Uses a case-linked invoice change as a source of recalculation requests.
FSM Profitability Reporting	Uses financial transaction data. Asset attribution in the supplied report depends on the line asset reference.

Record Constraints and Data Requirements

The supplied FSM header and sales-line custom fields are stored and are not universally required in their field definitions. Form requirements, NetSuite transaction validation, and individual feature requirements apply separately. An invoice can contain FSM references without every field being populated.

Project and subsidiary context depend on enabled NetSuite features and accounting preferences. A Project label doesn't change a customer value into a project reference. The native billing entity, FSM customer, and asset owner are distinct concepts.

Header links don't establish line attribution or charge eligibility. The default rule for selecting task-linked time and expenses applies to FSM Case Invoicing. The rule is not a universal requirement for manually created invoices.

Additional Information

• FSM Case Invoicing
• FSM Case Unbilled Amount Calculation
• FSM Profitability Reporting

Related Topics

• FSM Records
• FSM Case Record
• FSM Expense Report Record
• FSM Sales Order Record
• FSM Time Bill Record

General Notices