Find routing-number checksum errors, missing account numbers, duplicate routing/account pairs and spreadsheet damage. Get a report that identifies the source row, affected field and next action — without guessing lost digits.
CSV or TSV only. Preview: first five US rows, sample file up to 256 KB. Paid report: every row within your order limit, file up to 5 MB. Checks do not establish account existence, ownership or ACH/Fedwire eligibility.
Download a synthetic US sample CSV
| Source row | Status | Field | Finding / next action |
|---|
No file or row values are saved or sent to AI providers. US checks are deterministic. For CSV exports, import routing/account columns as Text in Excel: opening a CSV directly can strip leading zeros. US account checks use a digits-only CSV input policy and the 17-character ACH field limit, not a bank-specific account format. This is not a NACHA-file validator.
Illustrative synthetic US rows. OK means the stated checks passed, not that an account exists.
| Source row | Routing Number | Account Number | Status | Finding |
|---|---|---|---|---|
| 2 | 110000000 | 000123456789 | OK structure | Not an account-existence or ownership check |
| 3 | 71124821 | 076841393430 | Fail | Routing length: a leading zero may be lost. Re-export the original as text. |
| 4 | 110000000 | 7.684139343E+10 | Fail | Scientific notation: do not guess the original digits. |
Upload a UTF-8 CSV or TSV with routing and account columns. Map custom headers if needed, then preview the first five US rows free. The full-file report checks every row within the paid order limit and identifies source rows, affected fields and next actions.
It checks routing/account columns in a spreadsheet export, not native NACHA records, SEC codes, batch totals, addenda or payment authorization. A CSV structure pass does not certify an ACH file or establish ACH/Fedwire eligibility.
Yes. ABA structure and checksum are separate from account existence and ownership. Account checks here detect missing, non-digit, damaged or oversized CSV values; they do not confirm a bank-specific format, balance or account holder.
Excel can interpret identifiers as numbers and strip leading zeros or export scientific notation. Keep routing and account columns as Text. The report flags suspected damage but never guesses replacement digits; recover the original values from your trusted source.
No. Duplicate pairs and suppliers with multiple pairs are review flags. Check the supplier record and intended payment destination before changing data; the audit does not make a fraud determination.
No. Uploaded files are checked in memory and are not persisted or sent to AI providers. Send only a supplier reference and the bank fields needed for the audit. Column mapping templates contain column names, not row values.
The first-five-row US structure preview is free for sample files up to 256 KB. Existing one-time audit offers provide a full row-by-row CSV report for up to 1000 or 5000 rows, within the 5 MB upload limit. The displayed order allowance applies; it is separate from Pro API quotas.
Keep supplier-file checks separate from generated test data. Use US QA generation for fixtures or Stripe ACH test accounts and webhook QA for documented test outcomes and an offline checker. For European supplier files, use the IBAN/BIC audit.
The audit checks bank data, not account ownership or balances. A clean report does not guarantee that a payment will be accepted.