Validate Free+ Pro Beta CSV · NACHA · XML
Payment file check
Use for Before you send or import a payment file
  1. 1Upload a supplier CSV
  2. 2Map the bank columns
  3. 3Download the row-by-row report
For finance and AP teams

Check your supplier bank details before the payment run

Audit IBAN/BIC lists or US routing/account CSV files. Find checksum errors, duplicate bank details and data problems, then download a row-by-row report. Bank-level SEPA observations are included where available for IBAN files.

Free five-row US preview

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

Choosing a file does not upload it. Only use the columns needed for the audit.

Full-file report pricing

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.

What we check on every row

IBAN is validCountry format, length, MOD-97 checksum and, for Germany, the national account check.
BIC matches the bankThe BIC in your file against the bank behind the IBAN, from a licensed bank directory.
Duplicate accountsShared IBANs and suppliers with several IBANs are review flags, not proof of fraud. US mode checks the routing/account pair.
Available SEPA observationsBank-level participation in EPC registers where available. These observations do not verify the account or guarantee payment acceptance.

Sample report

Illustrative rows with published example IBANs. OK means the stated checks passed, not that an account exists.

SupplierIBANStatusBankSEPA InstantFinding
Beta SARLFR14 2004 1010 0505 0001 3M02 606OKLa Banque PostaleYes—
Acme GmbHDE89 3704 0044 0532 0130 00ReviewCommerzbankYesSame IBAN also used by “Echo Srl”
Gamma LtdGB29 NWBK 6016 1331 9268 19ReviewUK bankNoBIC in file (DEUTDEFF) does not match the bank
Delta BVDE89 3704 0044 0532 0130 01Fail——Invalid checksum digits
Up to 1,000 suppliers
$99
  • One file, one-time payment
  • Instant CSV report, up to 3 uploads
  • File checked in memory, not stored
Order audit — $99
Up to 5,000 suppliers
$149
  • One file, one-time payment
  • Instant CSV report, up to 3 uploads
  • File checked in memory, not stored
Order audit — $149

How it works

  1. Pay securely with Stripe.
  2. Choose IBAN or US routing/account mode and upload a CSV with an optional supplier reference.
  3. Download the report right away and fix the flagged rows before the payment run.

What does the payment file audit check?

Choose IBAN or US routing/account mode. IBAN reports check format, checksum, supplied BIC mismatches and available bank-level SEPA observations. US CSV reports check routing format and ABA checksum, missing or damaged identifiers, duplicate routing/account pairs and suppliers with multiple accounts. Neither mode verifies account existence, ownership or payment acceptance.

Does the audit confirm the account holder name?

No. Matching the name to the account is Verification of Payee, run by the payee bank at payment time. The audit tells you whether the bank takes part in VoP and flags data problems before the payment run.

What happens to my file?

It is checked in memory and is not stored or sent to AI providers. Upload only a supplier reference and the bank fields needed for your chosen mode. Export identifiers as text to preserve leading zeros. This tool accepts CSV/TSV, not XLSX or native NACHA files.

Testing an integration instead?

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.

Next in your workflow