FSM Item Receipt Record

In Field Service Management (FSM), an item receipt is a standard NetSuite transaction that records items received. The Receive tab in FSM Mobile confirms stock received from a transfer order at its destination, such as a technician's van warehouse.

The transfer order records the requested stock movement, the item fulfillment records what was shipped, and the item receipt records what was received. The receipt's items, quantities, and service-work references connect the received stock to its source and relevant task. Native purchase-order and customer-return receiving are separate uses of the same record type.

Record Information

The following table summarizes the record's identifiers and FSM Mobile configuration.

Property	Value
Record type	Standard NetSuite
Record name	Item Receipt
Record ID	`itemreceipt`
Record identity	Internal ID (`internalid`) identifies the record in NetSuite. Transaction Number (`tranid`) identifies the saved receipt for reference.
FSM Mobile resource	`receive`
FSM Mobile article base	`models/transaction`, with the article record set to `itemreceipt`

Property

Value

Record type

Standard NetSuite

Record name

Item Receipt

Record ID

itemreceipt

Record identity

Internal ID (internalid) identifies the record in NetSuite. Transaction Number (tranid) identifies the saved receipt for reference.

FSM Mobile resource

receive

FSM Mobile article base

models/transaction, with the article record set to itemreceipt

The FSM Mobile resource ID identifies a tab and its processing. It is separate from the NetSuite record type. For native scripting and creation by transformation, see Item Receipt.

Forms

Use the applicable standard or account-created item receipt transaction form in NetSuite. FSM supplies transaction body and item-line fields for this record but doesn't supply a dedicated FSM item receipt form.

NetSuite always stores an item receipt's custom form with the transaction. Store Form with Record is therefore not an optional checkbox for this transaction type. When the receipt is viewed or edited, the stored form is used. See Storing Custom Forms with Transactions.

For native transaction transformations, linked forms and role restrictions can affect the initial form selection. If no linked form is specified, NetSuite uses a preferred form, subject to role restrictions. See Linking Transaction Forms.

The built-in FSM Mobile Receive tab defines its own elements rather than generating them from a NetSuite form. The tab's presentation and validation rules require an Order selection, hide source IDs, and make the item table read-only. Changing a NetSuite receipt form doesn't automatically change those elements. For Receive tab settings, see Configuring FSM Mobile Receive. For information about shared form-generated field rules, see Form Properties.

Record Relationships

The receipt stores the following native and FSM references. Body references describe the transaction as a whole. Item-line references describe an individual line and can differ from the body values.

Related Record	Relationship and Field ID	Purpose
Source transaction	Receipt Created From (`createdfrom`) references its originating transaction. In the built-in FSM Mobile Receive workflow, this is the transfer order (`transferorder`).	Identifies the order from which stock is received. One transfer order can have multiple related receipts.
Item Fulfillment	Native receipt search relationship `appliedtotransaction` can identify the related item fulfillment (`itemfulfillment`).	Associates the receipt with its shipment when required by transfer costing. FSM Mobile initializes the transformation with the hidden `itemfulfillment` value, which is not an FSM custom receipt field.
Location	Receipt searches use native `location`, and the source transfer order stores its destination in `transferlocation`.	Identifies the receiving stock location. FSM Mobile uses the employee's Field Service Location (`custentity_nx_location`) as its receiving context.
Item	Each receipt line stores Item (`item` on the `item` sublist).	Identifies the stock received on that line. A receipt can contain multiple item lines.
CRM Task	Receipt Field Service Task (`custbody_nx_task`) references a CRM task (`task`).	Associates the receipt with service work. The built-in Receive search uses this body relationship.
Project Task	Receipt Field Service Project Task (`custbody_nx_projecttask`) references a project task (`projecttask`).	Provides the separate project task association used by the Receive search.
Case	Receipt Field Service Case (`custbody_nx_case`) references a case (`supportcase`).	Retains service-request context separately from the source transaction.
Customer	Receipt Field Service Customer (`custbody_nx_customer`) references a customer (`customer`).	Retains the service customer separately from native transaction relationships.
Asset	Receipt Field Service Asset (`custbody_nx_asset`) references a field service asset (`customrecord_nx_asset`).	Identifies the asset associated with the transaction. This is separate from an asset record's own Transaction reference.
Line-level service context	Receipt item lines can separately reference Asset (`custcol_nx_asset`), Case (`custcol_nx_case`), CRM Task (`custcol_nx_task`), and Project Task (`custcol_nx_projecttask`).	Associates an individual received line with service work. The built-in Receive item table doesn't expose these four fields.

Related Record

Relationship and Field ID

Purpose

Source transaction

Receipt Created From (createdfrom) references its originating transaction. In the built-in FSM Mobile Receive workflow, this is the transfer order (transferorder).

Identifies the order from which stock is received. One transfer order can have multiple related receipts.

Item Fulfillment

Native receipt search relationship appliedtotransaction can identify the related item fulfillment (itemfulfillment).

Associates the receipt with its shipment when required by transfer costing. FSM Mobile initializes the transformation with the hidden itemfulfillment value, which is not an FSM custom receipt field.

Location

Receipt searches use native location, and the source transfer order stores its destination in transferlocation.

Identifies the receiving stock location. FSM Mobile uses the employee's Field Service Location (custentity_nx_location) as its receiving context.

Item

Each receipt line stores Item (item on the item sublist).

Identifies the stock received on that line. A receipt can contain multiple item lines.

CRM Task

Receipt Field Service Task (custbody_nx_task) references a CRM task (task).

Associates the receipt with service work. The built-in Receive search uses this body relationship.

Project Task

Receipt Field Service Project Task (custbody_nx_projecttask) references a project task (projecttask).

Provides the separate project task association used by the Receive search.

Case

Receipt Field Service Case (custbody_nx_case) references a case (supportcase).

Retains service-request context separately from the source transaction.

Customer

Receipt Field Service Customer (custbody_nx_customer) references a customer (customer).

Retains the service customer separately from native transaction relationships.

Asset

Receipt Field Service Asset (custbody_nx_asset) references a field service asset (customrecord_nx_asset).

Identifies the asset associated with the transaction. This is separate from an asset record's own Transaction reference.

Line-level service context

Receipt item lines can separately reference Asset (custcol_nx_asset), Case (custcol_nx_case), CRM Task (custcol_nx_task), and Project Task (custcol_nx_projecttask).

Associates an individual received line with service work. The built-in Receive item table doesn't expose these four fields.

In FSM Mobile, the Order selection can represent a transfer order alone or a combination of a transfer order and fulfillment. Its hidden transferorder and itemfulfillment values supply source identifiers for receipt creation. They don't replace the saved receipt's native Created From relationship.

A body or line reference alone doesn't add the receipt to every FSM Mobile resource, asset history, service report, or synchronization process. Those capabilities use their own supported searches and mappings. An additional account custom link also requires separately defined behavior.

FSM Fields

The following tables use the supplied English labels. Labels and form presentation can vary by account without changing field IDs.

Receipt Identity and Quantities

The following table describes receipt identity and quantity fields.

Field	Field ID	Purpose	Values and Behavior
Internal ID (standard)	`internalid`	Identifies the saved item receipt.	Separate from the FSM Mobile entry's local identity and source-order ID.
Transaction Number (standard)	`tranid`	Identifies the saved receipt for reference.	The Receive tab reads this value from NetSuite. Saving locally doesn't confirm that NetSuite has assigned a transaction number.
Status (standard search field)	`status`	Supplies the receipt's native transaction status.	The Receive map reads display text without writing Status. It is separate from FSM Mobile synchronization or script execution state.
Created From (standard)	`createdfrom`	References the originating transaction.	Displayed through the FSM Mobile Order element. The standard map reads the saved relationship. Receipt creation uses the hidden source IDs.
Date (standard)	`trandate`	Receipt transaction date.	A transfer receipt cannot precede its shipment date. Receive has no explicit tab-specific date default.
Location (standard search field)	`location`	Identifies the receiving location in receipt selection.	The built-in Receive search restricts saved receipts to the user's Field Service Location and current CRM task or project task.
Item (standard sublist field)	`item` on sublist `item`	Stock item received.	Mapped from the receipt's item lines. FSM Mobile uses the `items` table property, and NetSuite uses the `item` sublist ID.
Quantity (standard sublist field)	`quantity` on sublist `item`	Quantity recorded as received on the line.	The saved receipt is the record of received quantities. Choices loaded in FSM Mobile can contain earlier shipped quantities.
Quantity Remaining (standard sublist field)	`quantityremaining` on sublist `item`	Quantity still available to receive on the transformed receipt.	Read during standard FSM Mobile creation to supply the received quantity. It is not a separate FSM quantity field.
Receive (standard sublist field)	`itemreceive` on sublist `item`	Marks a receipt line for receiving.	Standard FSM Mobile creation sets this to true on the transformed lines, including when Default Items to Zero Received/Fulfilled is selected.

Field

Field ID

Purpose

Values and Behavior

Internal ID (standard)

internalid

Identifies the saved item receipt.

Separate from the FSM Mobile entry's local identity and source-order ID.

Transaction Number (standard)

tranid

Identifies the saved receipt for reference.

The Receive tab reads this value from NetSuite. Saving locally doesn't confirm that NetSuite has assigned a transaction number.

Status (standard search field)

status

Supplies the receipt's native transaction status.

The Receive map reads display text without writing Status. It is separate from FSM Mobile synchronization or script execution state.

Created From (standard)

createdfrom

References the originating transaction.

Displayed through the FSM Mobile Order element. The standard map reads the saved relationship. Receipt creation uses the hidden source IDs.

Date (standard)

trandate

Receipt transaction date.

A transfer receipt cannot precede its shipment date. Receive has no explicit tab-specific date default.

Location (standard search field)

location

Identifies the receiving location in receipt selection.

The built-in Receive search restricts saved receipts to the user's Field Service Location and current CRM task or project task.

Item (standard sublist field)

item on sublist item

Stock item received.

Mapped from the receipt's item lines. FSM Mobile uses the items table property, and NetSuite uses the item sublist ID.

Quantity (standard sublist field)

quantity on sublist item

Quantity recorded as received on the line.

The saved receipt is the record of received quantities. Choices loaded in FSM Mobile can contain earlier shipped quantities.

Quantity Remaining (standard sublist field)

quantityremaining on sublist item

Quantity still available to receive on the transformed receipt.

Read during standard FSM Mobile creation to supply the received quantity. It is not a separate FSM quantity field.

Receive (standard sublist field)

itemreceive on sublist item

Marks a receipt line for receiving.

Standard FSM Mobile creation sets this to true on the transformed lines, including when Default Items to Zero Received/Fulfilled is selected.

For full-receipt behavior and the distinction between displayed and saved quantities, see Receiving.

Service-Work Fields

The following table lists supplied FSM fields enabled for item receipts. The field definitions store values but don't make these fields required.

Field	Field ID	Purpose	Values and Behavior
Field Service Customer	`custbody_nx_customer`	Customer context for the transaction.	Stores a customer reference. The reference alone doesn't establish billing or receipt eligibility.
Field Service Asset	`custbody_nx_asset`	Asset context for the transaction.	The Transaction model can source the asset from a linked CRM task or project task during initialization and validation.
Field Service Case	`custbody_nx_case`	Case context for the transaction.	The field definition sources the case from Field Service Task's native Support Case relationship.
Field Service Task	`custbody_nx_task`	CRM task associated with the receipt.	Used by the Receive search independently of the item-line Field Service Task (trans) field.
Field Service Project Task	`custbody_nx_projecttask`	Project task associated with the receipt.	Used by the Receive search independently of the item-line Field Service Project Task (trans) field.
Field Service Asset (trans)	`custcol_nx_asset` on sublist `item`	Asset associated with an item line.	The field definition sources the asset from the line's Field Service Task.
Field Service Case (trans)	`custcol_nx_case` on sublist `item`	Case associated with an item line.	The field definition sources the case from the line's Field Service Task.
Field Service Task (trans)	`custcol_nx_task` on sublist `item`	CRM task associated with an item line.	Separate from `custbody_nx_task`; a line link alone doesn't satisfy the standard Receive body-field filter.
Field Service Project Task (trans)	`custcol_nx_projecttask` on sublist `item`	Project task associated with an item line.	Separate from `custbody_nx_projecttask`.

Field

Field ID

Purpose

Values and Behavior

Field Service Customer

custbody_nx_customer

Customer context for the transaction.

Stores a customer reference. The reference alone doesn't establish billing or receipt eligibility.

Field Service Asset

custbody_nx_asset

Asset context for the transaction.

The Transaction model can source the asset from a linked CRM task or project task during initialization and validation.

Field Service Case

custbody_nx_case

Case context for the transaction.

The field definition sources the case from Field Service Task's native Support Case relationship.

Field Service Task

custbody_nx_task

CRM task associated with the receipt.

Used by the Receive search independently of the item-line Field Service Task (trans) field.

Field Service Project Task

custbody_nx_projecttask

Project task associated with the receipt.

Used by the Receive search independently of the item-line Field Service Project Task (trans) field.

Field Service Asset (trans)

custcol_nx_asset on sublist item

Asset associated with an item line.

The field definition sources the asset from the line's Field Service Task.

Field Service Case (trans)

custcol_nx_case on sublist item

Case associated with an item line.

The field definition sources the case from the line's Field Service Task.

Field Service Task (trans)

custcol_nx_task on sublist item

CRM task associated with an item line.

Separate from custbody_nx_task; a line link alone doesn't satisfy the standard Receive body-field filter.

Field Service Project Task (trans)

custcol_nx_projecttask on sublist item

Project task associated with an item line.

Separate from custbody_nx_projecttask.

The Receive tab has no explicit article.defaults block. Its receipt is created by transforming the selected transfer order. Don't assume that the tab independently defaults every service field from the current task, or that every body value is copied to each item line.

Mobile Creation Identity

The following table describes fields used to identify creation requests from FSM Mobile.

Field	Field ID	Purpose	Values and Behavior
External ID (standard)	`externalid`	Stores technical identity used by standard FSM Mobile record synchronization.	FSM uses the `fsm_` prefix to recognize repeated creation requests for the same entry. This is separate from the source order and receipt number.
Field Service Idempotency Key	`custbody_nx_idempotency_key`	Older custom identity field retained for compatibility and visibility.	Current standard FSM Mobile creation uses External ID instead. This field is not a receipt-processing or stock-arrival indicator.

Field

Field ID

Purpose

Values and Behavior

External ID (standard)

externalid

Stores technical identity used by standard FSM Mobile record synchronization.

FSM uses the fsm_ prefix to recognize repeated creation requests for the same entry. This is separate from the source order and receipt number.

Field Service Idempotency Key

custbody_nx_idempotency_key

Older custom identity field retained for compatibility and visibility.

Current standard FSM Mobile creation uses External ID instead. This field is not a receipt-processing or stock-arrival indicator.

For reservation and repeated-request behavior, see FSM Mobile Duplicate Creation Protection.

Creation and Update Sources

The following table describes how receipts are created or updated.

Source	Effect on the Record
NetSuite receiving	Creates the item receipt from its source transaction. Native form, inventory, and transaction requirements apply. Other native receiving processes use this record type independently of FSM Mobile.
FSM Mobile Receive	Transforms the selected transfer order into an item receipt, using its related fulfillment where applicable. The saved receipt records the quantities received.
NetSuite edits or mapped changes from FSM Mobile	Can update permitted receipt fields, subject to NetSuite restrictions. The built-in FSM Mobile source choice locks after a receipt has a transaction number, and its item table is read-only.
Field and model sourcing	Can supply service context from linked tasks. Sourcing rules and transformation values apply within their respective scopes and are not universal receipt defaults.

Source

Effect on the Record

NetSuite receiving

Creates the item receipt from its source transaction. Native form, inventory, and transaction requirements apply. Other native receiving processes use this record type independently of FSM Mobile.

FSM Mobile Receive

Transforms the selected transfer order into an item receipt, using its related fulfillment where applicable. The saved receipt records the quantities received.

NetSuite edits or mapped changes from FSM Mobile

Can update permitted receipt fields, subject to NetSuite restrictions. The built-in FSM Mobile source choice locks after a receipt has a transaction number, and its item table is read-only.

Field and model sourcing

Can supply service context from linked tasks. Sourcing rules and transformation values apply within their respective scopes and are not universal receipt defaults.

During synchronization, FSM Mobile processes receipts through the Field Service Mobile Suitelet deployment (customdeploy_nx_mobile) of the Field Service Suitelet script (customscript_nx_suitelet). For information about script execution and deployment, see FSM Script Reference.

Used by FSM Features

The following table describes how FSM features use item receipts.

Feature	Record Use
FSM Mobile Stock Transfers	Stores the receipt result of an incoming transfer and connects received stock to its source and service task.
FSM Mobile Duplicate Creation Protection	Uses the receipt's technical creation identity when the request follows standard record synchronization.

Feature

Record Use

FSM Mobile Stock Transfers

Stores the receipt result of an incoming transfer and connects received stock to its source and service task.

FSM Mobile Duplicate Creation Protection

Uses the receipt's technical creation identity when the request follows standard record synchronization.

Record Constraints and Data Requirements

An item receipt is created from a source transaction. Native SuiteScript doesn't support creating a standalone item receipt with record.create. Integrations use a supported transformation. The built-in FSM Mobile path transforms a transfer order. See Item Receipt.

For transfer receipts, NetSuite applies the following native constraints:

Received quantities are limited to the order.
The receipt date must be on or after shipment.
Received serial or lot numbers and lot quantities must match the fulfillment.

Transfer-cost settings also affect the required fulfillment and receipt quantity relationship. These are native transaction constraints. See Receiving Fulfilled Transfer Orders.

The field definitions don't require values for the six supplied FSM body fields or four FSM item-line fields. An account form, enabled inventory feature, or transaction rule can impose additional requirements. The standard Receive element in FSM Mobile requires an Order selection independently of a native field's required setting.

The built-in Receive workflow receives all remaining quantities on the transformed receipt and doesn't provide partial-receipt input or destination-bin selection. A valid native receipt can therefore involve choices outside the built-in FSM Mobile workflow. For the supported FSM Mobile boundary, see Receiving and Configuring FSM Mobile Receive.

FSM Item Receipt Record

Record Information

Forms

Record Relationships

FSM Fields

Receipt Identity and Quantities

Service-Work Fields

Mobile Creation Identity

Creation and Update Sources

Used by FSM Features

Record Constraints and Data Requirements

Additional Information

Related Topics