Skip to content

ACH Field Reference

The following tables describe the data requirements for creating identityIDs when making payments through the US • USD • ACH (Automated Clearing House) corridor.

Each table corresponds directly to one of the JSON schema files used in the Payment Data Requirements Utility. The schemas define the precise fields you must include when constructing an identityIDs.

How to read these tables

  • Identity Type: Originator (sender) or Beneficiary (recipient).

  • Use Case: Individual or Business.

  • Field Path: Technical field name aligned with the JSON schema (e.g., Cdtr.Nm, DbtrAcct.Id.IBAN).

  • Description: Human-readable explanation of what the field means.

  • Required: Whether the field is mandatory for this schema.

  • Validation: Field constraints such as character limits, regex patterns, or enumerated values.

Organization of the tables

For ACH, three tables are provided:

  1. Originator • Business

  2. Beneficiary • Individual

  3. Beneficiary • Business

Originator • Business

Field PathDescriptionRequiredValidation
Dbtr.Id.OrgId.Othr.IdOriginator Tax Identification NumberYes1–50 chars; regex:
Dbtr.Id.OrgId.Othr.SchmeNm.CdOriginator Organization ID Document TypeYes4 chars; enum:

Tax ID:TXID
Dbtr.NmOriginator NameYes1–150 chars; regex:

/^[\w ,.&()-]{1,150}$/
Dbtr.PstlAdr.CtryOriginator two-letter Country CodeYes2 chars; regex:

/^[A-Za-z]{2}$/

Beneficiary • Individual

Field PathDescriptionRequiredValidation
Cdtr.Id.PrvtId.DtAndPlcOfBirth.BirthDtBeneficiary Date of BirthYes10 chars; regex: YYYY-MM-DD
Cdtr.PstlAdr.AdrLineBeneficiary Postal AddressYes0–250 chars; regex: /^[\w#@!,.&()\\/\\-]{1,250}$/
Cdtr.PstlAdr.CtryBeneficiary two-letter Country CodeYes2 chars; regex: /^[A-Za-z]{2}$/
Cdtr.PstlAdr.CtrySubDvsnBeneficiary State, County, or ProvinceYes2 chars; regex: /^[A-Za-z]{2}$/
Cdtr.PstlAdr.PstCdBeneficiary Postal CodeYes5–10 chars; regex: /^[a-zA-Z0-9\s-]{3,10}$/
Cdtr.PstlAdr.TwnNmBeneficiary CityYes1–150 chars; regex: /^[\w#@!,.&()\\/\\-]{1,150}$/
Cdtr.StrdNm.FirstNmBeneficiary Given NameYes0–50 chars; regex: /^[\w,.&()-]{0,50}$/
Cdtr.StrdNm.LastNmBeneficiary Family NameYes0–50 chars; regex: /^[\w,.&()-]{0,50}$/
CdtrAcct.Id.Othr.IdBeneficiary Account NumberYes4–21 chars; regex: /^[0-9]{4,21}$/
CdtrAcct.Id.Othr.SchmeNm.CdBeneficiary Account Number ID CodeYes4–5 chars; enum: [Basic Bank Account Number:BBAN]
CdtrAcct.Tp.CdBeneficiary Account TypeYes4 chars; enum: `[Checking:CACC
CdtrAgt.FinInstnId.ClrSysMmbId.ClrSysId.CdBeneficiary Bank Identifier Clearing System CodeYes4–10 chars; enum: [US ACH Bank Routing Number:USABA]
CdtrAgt.FinInstnId.ClrSysMmbId.MmbIdBeneficiary Bank IdentifierYes9 chars; regex: /^[0-9]{9}$/

Beneficiary • Business

Field PathDescriptionRequiredValidation
Cdtr.Id.OrgId.Othr.IdBeneficiary Tax IDYes1–50 chars; regex: /^[A-Za-z0-9]{0,50}$/
Cdtr.Id.OrgId.Othr.SchmeNm.CdBeneficiary ID specification codeYes5 chars; enum: [Tax ID:TXID]
Cdtr.NmBeneficiary Corporate NameYes1–150 chars; regex: /^[\w,.&()-]{0,150}$/
Cdtr.PstlAdr.AdrLineBeneficiary Business Postal AddressYes0–250 chars; regex: /^[\w#@!,.&()\\/\\-]{1,250}$/
Cdtr.PstlAdr.CtryBeneficiary two-letter Country CodeYes2 chars; regex: /^[A-Za-z]{2}$/
Cdtr.PstlAdr.CtrySubDvsnBeneficiary State, County, or ProvinceYes2 chars; regex: /^[A-Za-z]{2}$/
Cdtr.PstlAdr.PstCdBeneficiary Business Postal CodeYes5–10 chars; regex: /^\d{5}([\-]\d{4})?$/
Cdtr.PstlAdr.TwnNmBeneficiary Business CityYes1–150 chars; regex: /^[\w#@!,.&()\\/\\-]{1,150}$/
CdtrAcct.Id.Othr.IdBeneficiary Business Bank Account NumberYes4–21 chars; regex: /^[0-9]{4,21}$/
CdtrAcct.Id.Othr.SchmeNm.CdBeneficiary Account Number ID CodeYes5 chars; enum: [Basic Bank Account Number:BBAN]
CdtrAcct.Tp.CdBeneficiary Business Bank Account TypeYes4 chars; enum: `[Checking:CACC
CdtrAgt.FinInstnId.ClrSysMmbId.ClrSysId.CdBeneficiary Business Bank Identifier Clearing System CodeYes4–10 chars; enum: [US ACH Bank Routing Number:USABA]
CdtrAgt.FinInstnId.ClrSysMmbId.MmbIdBeneficiary Business Bank Identifier CodeYes9 chars; regex: /^[0-9]{9}$/