NACHA file reference
Supported SEC codes, accepted file type, Company ACH ID format, and how validation and errors work for NACHA files.
Keep this reference handy while preparing and uploading NACHA files: the supported SEC codes, the accepted file type, the Company ACH ID format, and how validation errors are surfaced. For the upload and management workflow, see Manage your NACHA files.
Supported SEC codes
A file must only contain entries using one of the following Standard Entry Class (SEC) codes. Files containing any other SEC code fail validation on upload, so check your source file first.
| SEC Code | Description |
|---|---|
| CCD | Corporate Credit or Debit — business-to-business payments. |
| CTX | Corporate Trade Exchange — business-to-business payments with addenda. |
| PPD | Prearranged Payment and Deposit — consumer payments such as payroll. |
| TEL | Telephone-Initiated Entry — consumer payments authorized by phone. |
| WEB | Internet-Initiated Entry — consumer payments authorized online. |
Support for additional SEC codes is planned for future releases; this page will be updated as that support becomes available.
Supported file type
Passport currently accepts Unbalanced NACHA files. If you generate files from your own originating system, confirm with your implementation contact that your export is configured to produce an Unbalanced file — other file types aren't accepted at this time. Support for additional file types may be introduced in future releases.
Company ACH ID format
Every file must use a Company ACH ID in the following format:
000 + Passport Account IDFor example, if your Passport Account ID is 1234567, your Company ACH ID should be 0001234567.
Files that use a different Company ACH ID format fail validation, so this is a good first thing to check if a file is rejected unexpectedly. Support for custom Company ACH IDs is planned for a future release.
Understanding validation and errors
- When you upload a file: Passport validates it immediately. If something doesn't check out — an unsupported SEC code, an incorrect Company ACH ID, or a structural issue in the file — the file is marked Rejected and no batches or transactions are created.
- Once a file is accepted: issues can still arise later in processing, such as a batch failing due to insufficient balance or a limit breach. These surface as a Failed or Pending status at the batch or entry level, not against the whole file.
- Reviewing what went wrong: For a rejected file, view a consolidated summary of all validation issues in one place (subject to your role) rather than working through them one at a time. For batch- or entry-level issues, hover over the status to see the specific reason.
- Fixing and re-uploading: Correct the issues in your source file and upload it again as a new file. Passport treats the corrected file as a fresh upload and validates it independently — a rejected file can't be edited or resubmitted in place.
Key considerations
- Double-check your Company ACH ID follows the required format before uploading.
- Stick to supported SEC codes — CCD, CTX, PPD, TEL, and WEB.
- Make sure your file is an Unbalanced NACHA file; other formats aren't accepted.
- Entries can't be cancelled once they're past their Effective Entry Date (EED), so act early if something needs to be pulled back.
- Review validation errors carefully before re-uploading a corrected file — it saves a second round trip.
- Customer Portal visibility into NACHA files depends on your organization's configured processing settings.
- You need the right role-based permissions to access NACHA File Management and take actions within it — check with your Passport administrator if something seems missing.
See also
- NACHA File Management: overview, scenarios, and file lifecycle
- Manage your NACHA files: upload, track, drill down, and take actions
- Error Codes and Messages: reason and return codes when a transaction fails
Updated about 11 hours ago