Setup › Accounting

Payment File Formats

Each format defines how a payment run is written to a file for transmission to the bank. A format is bound to one bank and one payment type; deprecated formats stay listed so historical payment runs remain reproducible.

Formats (10)
Format nameCountryPayment typeFileBankStatusLast used
NACHA CCDUnited StatesCredit Transfer.achFirst Meridian BankActive08/19/2026
NACHA PPDUnited StatesCredit Transfer.achFirst Meridian BankActive08/18/2026
SEPA Credit Transfer pain.001NetherlandsCredit Transfer.xmlRijnmond HandelsbankActive08/20/2026
SEPA Direct Debit pain.008NetherlandsDirect Debit.xmlRijnmond HandelsbankActive08/14/2026
BACS Standard 18United KingdomCredit Transfer.txtThames Clearing BankActive08/17/2026
Faster Payments ISO 20022United KingdomCredit Transfer.xmlThames Clearing BankDraft07/31/2026
Positive Pay CSVUnited StatesCheque.csvFirst Meridian BankActive08/20/2026
Cheque Print MICR LaserUnited StatesCheque.pdfFirst Meridian BankActive08/12/2026
EFT CPA 005CanadaCredit Transfer.txtLaurier Commercial BankDraft06/26/2026
Legacy Wire Batch 1.2United StatesCredit Transfer.datFirst Meridian BankDeprecated02/27/2026
NACHA CCD — field mapping
United StatesCredit Transfer.achFirst Meridian Bank
Record type
Fixed-width, 94 characters per record, CR/LF terminated. One file per originating bank account.
Header record (1)
Immediate destination routing 021000021, origin 5561200088, file creation date, file ID modifier A.
Batch record (5)
Service class 220, company name Wexbourne ERP US, entry description VENDOR PAY, effective entry date from the payment run.
Entry detail (6)
Transaction code 22 for checking credit, receiving DFI + check digit, amount in cents, individual ID = vendor number, trace number sequence.
Batch control (8)
Entry/addenda count, entry hash, total debit and credit amounts, batch number.
File control (9)
Batch count, block count, entry count, hash and totals, padded with 9-filler records to a multiple of ten.
Edit mapping
MC