• 1Enable the operation: Accounting → Send Accounting Orders.
• 2Connection: Select your NetSuite connection (Production or Sandbox) → Test → Save.
• 3Template: Select or create a Send Accounting Orders Mapping Template and choose your SKU option (Order-level vs PO-level).
• 4Schedule: Turn on Scheduled and set a cadence (e.g., Every 30 Minutes) or run on demand.

Flxpoint can bring FFL information from NetSuite orders. NetSuite doesn’t have a native FFL field on Sales Orders or Purchase Orders; use your NetSuite custom body field and map it to Flxpoint’s Order FFL in the Get Orders mapping template.

• In Get Orders → Mapping Template, map your NetSuite custom field to Order FFL in Flxpoint.
• Enter the NetSuite field id with the cf_ prefix.
• Example: If your NetSuite field id is custbody_ffl_number, enter cf_custbody_ffl_number and map it to Order FFL.

• Provide Customer Id or map Email/Name so the customer can be found/created.
• Confirm your SKU choice (Order-level vs PO-level) matches vendor expectations.
• For dropship, verify vendor associations so a PO is created from the SO.

• Customer not created/found: Provide Customer Id or ensure Email/Name mapping exists.
• Wrong SKUs on lines: Verify template choice (Order-level vs PO-level) and vendor associations.
• SO created but no PO: Check FR type (PO generation only for external/dropship).
• Validation errors: Confirm IDs (Category, Custom Form, Entity Status, Subsidiary) match NetSuite values.

Partial invoicing is supported. When a vendor bills only some PO lines:

• First bill: Send all lines; for not-yet-billed items use quantity: 0.
• Later bill(s): Send only newly invoiced items with billed quantities.

{
  "items": [
    { "orderLine": 1, "quantity": 1 },
    { "orderLine": 2, "quantity": 0 }
  ]
}

{
  "items": [
    { "orderLine": 2, "quantity": 1 }
  ]
}

• 1Enable & Connect: Turn on Accounting → Send Accounting Shipments, pick your NetSuite connection (Production/Sandbox), Test → Save.
• 2Configure: Choose default inventoryLocation behavior and any header options required by your account.
• 3Template: Select or create the Send Accounting Shipments template and map key fields (below).
• 4Schedule or Run: Toggle Scheduled for automatic syncing or use Run Now for ad-hoc pushes.

Multiple shipments are supported via partial fulfillments:

• Create a fulfillment for the shipped lines (attach tracking to those lines).
• Leave unshipped lines unfulfilled; the Sales Order remains Partially Fulfilled.
• Later shipments create new fulfillments for remaining lines.

• Sales Order exists and is accessible to the integration role.
• Template maps SKU, Quantity, and Tracking Number(s).
• Default or mapped inventoryLocation aligns with the SO.

• No fulfillment created: Ensure the Accounting Order (SO) exists and the operation is enabled/scheduled.
• Tracking on wrong line: Verify SKU parity between Flxpoint and NetSuite.
• Partial not reflected: Only include shipped lines in a given fulfillment.
• Transform error: Include a valid inventoryLocation and confirm it’s allowed for the SO.