File specifications, formats and the operational detail your accounting team asks for on the second day of implementation.
We accept a NACHA formatted file, 94 characters per record, with no line terminators other than CR LF, uploaded through the Gateway or delivered to our managed file transfer host. Standard entry class codes supported: PPD, CCD, CCD+, CTX, WEB, TEL and CIE. IAT is not supported and an IAT batch in an otherwise valid file rejects the whole file rather than the batch.
The immediate destination is 064209731 with the leading blank the format requires. The immediate origin is your ten digit company identification number, which is your federal employer identification number preceded by a one, and it is stated in your welcome letter. The company identification in batch header records must match the value we have on file for the batch to pass validation, and a mismatch is the single most common reason a first file fails.
Effective entry dates more than two banking days forward are accepted and warehoused. An effective entry date in the past is rewritten to the next banking day, which is not what most originators expect, so check the confirmation.
| Record | What we validate |
|---|---|
| File header, record type 1 | Immediate destination equals 064209731. Immediate origin equals the company identification we have on file. File creation date is within seven days. |
| Batch header, record type 5 | Service class 200, 220 or 225. Standard entry class in the supported list. Company identification matches. Effective entry date is a banking day. |
| Entry detail, record type 6 | Receiving routing number passes the check digit. Amount is not zero except on a prenotification. Individual identification is present on CCD and CTX. |
| Addenda, record type 7 | One addenda on CCD+, up to 9,999 on CTX. Payment related information is not validated for content. |
| Batch and file control, types 8 and 9 | Entry and addenda counts, entry hash, debit and credit totals. A control total that disagrees with the detail rejects the file. |
Comma delimited or fixed width, one record per issued check, transmitted any time before the presentment cutoff. A header row is permitted and ignored if the first field is not numeric.
| Field | Format | Required |
|---|---|---|
| Account number | Numeric, up to 12, no leading zeros required | Yes |
| Check number | Numeric, up to 10 | Yes |
| Issue date | MMDDYYYY or MM/DD/YYYY | Yes |
| Amount | Numeric with an implied two decimal places, or with an explicit decimal point. Do not include a currency symbol or a thousands separator. | Yes |
| Payee name | Up to 80 characters | Only where payee name verification is enabled, in which case it is required and a blank rejects the record |
| Issue or void indicator | I or V | No, defaults to I |
Exception items are presented in the Gateway by 9:30 a.m. Eastern and must be decisioned by 2:00 p.m. Eastern the same banking day. An exception not decisioned by the cutoff defaults to pay, which is the setting most clients arrive with and a setting you can change to return. Ask your implementation specialist to change your default if you would rather an undecided item be returned; we do not change it without a signed instruction because a default of return can bounce a legitimate payroll check.
Clients who deliver files automatically connect to mft.calderbankonline.com over SFTP on port 22. Authentication is by SSH public key. We exchange keys during implementation and we do not accept a password-only connection for payment files.
Each client has a home directory with an inbound folder, an outbound folder and an archive folder. Write your file to a temporary name and rename it into place when the write is complete: our poller picks up any file in the inbound folder on a 15 minute cycle, and a file that is still being written is a file that fails validation. Processed files move to archive and are retained for 45 days.
File names should carry your company identification and a date stamp. We do not enforce a naming convention, which we regret, because reconciling three files named export.txt is not a good use of anyone's morning.
A completed user setup form is accepted from a named company administrator only, and we call back on every entitlement change that adds Payment Approval or User Administration. Send the form through the secure message channel in the Gateway rather than by email.
Treasury Operations. Rev. 02/2026. Questions: (423) 555-0125.