Check a NACHA file before it goes to your bank. The open-source Moov ACH engine reports structural errors with line numbers, and we apply the 2026 Nacha Company Entry Description rule: PAYROLL for wage credits, PURCHASE for online goods debits. A structural validator alone cannot catch that, because it does not know why you are paying.
We are preparing an API for ACH file checks, including the 2026 Nacha rules, ACH to ISO 20022 conversion checks and return / NOC matching. Tell us what you send and to which bank, and get early access.
It reads your NACHA file with the open-source Moov ACH engine (v1.63.7) and reports structural errors with line numbers: record lengths, batch and file control totals, entry and addenda counts, trace sequences. It then applies the 2026 Nacha Company Entry Description rule (PAYROLL / PURCHASE) using the payment purpose you declare.
Since 20 March 2026, PPD credits that pay wages to consumer accounts must carry PAYROLL in the Company Entry Description, and WEB/TEL debits for online purchases of physical goods must carry PURCHASE. A normal structural validator cannot see this, because it does not know why you are paying.
No. The file is checked in a temporary sandbox and deleted right after the check. Account numbers and names are never shown in the report.
No. It means the file is structurally readable and passes the selected 2026 rule for the purpose you declared. Your ODFI may apply its own limits, cut-off times and rules that are not checked here.
IBANgen provides synthetic QA data. Simulated files and responses do not reflect how any real bank or operator processes payments.