NetSuite REST icon

NetSuite REST

Call NetSuite SuiteTalk REST operations.

Actions979

Check → Insert record

AI-generated

Summary

Create a new Check record in NetSuite via the SuiteTalk REST API.

Inputs

  • entity — Reference to the payee (customer, vendor, employee, etc.).
  • amount — Dollar amount of the check. Use userTotal or total; NetSuite updates this amount based on line items.
  • tranDate — Posting date of the check. Defaults to today if omitted.
  • class — Optional classification applied to the check.
  • department — Department for the transaction.
  • currency — Currency used for the check.
  • department — Optional department for the check.
  • location — Location where the check is issued.
  • address — Custom address for the payee.
  • payeeAddress — Detailed address components for the payee.
  • memo — Memo line printed on the check.
  • toBePrinted — Whether the check is queued for printing.
  • status — Initial status of the check (e.g., V for void, Z for saved).
  • customFields — Custom fields to set on the record via the CustomField collection.
  • isDebugMode — If true, the output includes full request and response details.

Output shape

Returns the created Check record as JSON in the first output item. If debug mode is enabled, the output item includes two fields, request and response, containing the full HTTP payloads.

All fields are optional from the UI, but NetSuite requires at least the payee (entity), amount, and transaction date to successfully create a Check. Missing required fields will result in a validation error from NetSuite.

Examples

Example 1: Create a check for a vendor

Set entity to the vendor’s internal ID, amount to 500, tranDate to 2024-08-20, and toBePrinted to true

Example 2: Insert a check with a specific custom form

Specify customForm.id as 153 (Korean Print Form) and provide memo and address details

Example 3: Create a check and store response for debugging

Enable Debug Mode; the resulting output will contain request and response data with full payloads.

Discussion