ACH Record Now Exposed via SuiteTalk REST API

What changed

NetSuite now exposes the Automated Clearing House (ACH) record to the SuiteTalk REST API. This is a top-level record (not a subrecord) with record ID automatedclearinghouse.

The endpoint is:

• /services/rest/record/v1/automatedClearingHouse

Confirmed supported HTTP methods:

• POST — create a new ACH payment instrument
• PATCH — update an existing ACH record by internal ID

Additional methods (GET, DELETE) are not shown in the source examples. Check the REST API Browser for the full list of supported operations and query parameters.

Key fields

Based on the documented code samples, the record accepts at minimum:

• entity — reference (customer internal ID)
• accountOwnerName — string
• bankAccountNumber — string
• routingNumber — string (ABA routing number)
• bankName — string
• isDefault — boolean
• limit — currency / float
• paymentMethod — reference (payment method internal ID)
• preserveOnFile — boolean
• memo — string

For the complete field list and field types, consult the REST API Browser’s automatedclearinghouse reference page.

Prerequisites

1. Enable the Payment Instruments feature (Setup > Company > Enable Features).
2. Enable the Credit Card Payments feature (required even though this is ACH, not credit card — the feature gates the underlying payment-instrument infrastructure).

What to do

1. If you manage ACH records via CSV import, SuiteScript, or SOAP today — evaluate whether migrating to the REST endpoint simplifies your integration. The REST record supports standard SuiteTalk REST conventions (JSON payloads, external-ID upsert via ?replace=, etc.).
2. Verify supported operations. The release note only shows POST and PATCH examples. Before building a full integration, confirm GET and DELETE support in the REST API Browser at /services/rest/record/v1/metadata-catalog/automatedClearingHouse.
3. Review field-level permissions. Bank account numbers and routing numbers are sensitive PCI-adjacent data. Confirm that your REST roles have appropriate field-level access and that responses mask or omit these values as expected.
4. Check SuiteScript compatibility. The release note does not clarify whether record.load({ type: 'automatedclearinghouse' }) is also newly supported or was already available. Test in sandbox before assuming SuiteScript parity.
5. Update sandbox first. Enable both prerequisite features in a sandbox account and run POST/PATCH calls against the new endpoint before promoting to production.

Gaps in the source

The release note does not specify which NetSuite release introduced this record. The version could not be determined from the URL or title. Verify the target release in the SuiteAnswers release-notes index or your account’s Release Preview notes.