GL Audit Numbering Sequence Record Now Exposed via REST API

What changed

The GL Audit Numbering Sequence record is now exposed as a SuiteTalk REST resource at /services/rest/record/v1/glnumberingsequence. The record ID is GLNumberingSequence.

This record lets you configure two types of GL audit numbering sequences:

• Permanent — numbers assigned to GL-impacting transactions are immutable once set.
• Repeatable — the sequence can be re-run, potentially reassigning different numbers to transactions to close gaps caused by GL adjustments.

Supported HTTP methods

• POST — create a new sequence.
• GET — retrieve sequence records (filterable by fields such as numberingType).
• PATCH — update fields (e.g., set isInactive: true, change prefix).

Key fields on POST

• sequenceName — display name of the sequence.
• numberingType — REPEATABLE or PERMANENT.
• orderType — determines sort order; e.g., TRANDATE (Transaction Date).
• accountingBook — reference to the target accounting book.
• period — fiscal period reference.
• subsidiaries — sublist of subsidiary references.
• prefix / suffix — string affixes applied to generated numbers.
• initNum — starting number.
• minDigits — minimum digit width for zero-padding.
• excludeZeroTransactions — boolean.
• recurringType — e.g., NONE.

Restrictions and exceptions

• DELETE is not supported. To deactivate a sequence, send a PATCH with "isInactive": true.
• Two fields are marked internal-only and cannot be read or written via REST: backToPeriodClose and isCopyToNextPeriod.
• The System Notes sublist is search-only — it is not returned on standard GET requests.

Example: Create a repeatable sequence

POST /services/rest/record/v1/glnumberingsequence

{
  "accountingBook": {"id": "1"},
  "excludeZeroTransactions": false,
  "initNum": 1,
  "isInactive": false,
  "minDigits": 1,
  "numberingType": {"id": "REPEATABLE"},
  "orderType": {"id": "TRANDATE"},
  "period": {"id": "579"},
  "prefix": "PREF",
  "recurringType": {"id": "NONE"},
  "sequenceName": "TestRule",
  "subsidiaries": {"items": [{"id": "1"}]},
  "suffix": "SUF"
}

Example: Deactivate a sequence (no DELETE)

PATCH /services/rest/record/v1/glnumberingsequence/<recordID>

{
  "isInactive": true
}

Prerequisites

• The GL Audit Numbering feature must be enabled at Setup > Company > Enable Features (Accounting tab).

What to do

1. If you manage GL audit numbering sequences through custom scripts or manual UI workflows, evaluate migrating to the REST endpoint for automation.
2. Note the absence of DELETE — build your deactivation logic around PATCH with isInactive: true.
3. Do not attempt to read or write backToPeriodClose or isCopyToNextPeriod via REST; these are internal fields and will be ignored or cause errors.
4. If you need System Notes data from this record, use N/search or SuiteAnalytics; the sublist is not returned on standard REST GET calls.
5. Consult the REST API Browser for the full field schema: search for glnumberingsequence in the record list.

Note: The source does not specify which NetSuite release introduced this REST exposure. Check the REST API Browser's change log or your account's release notes to confirm availability in your environment.