How does the ABA routing number check digit formula catch typos?
The 9-digit ABA routing number uses a weighted Modulus-10 checksum where 3 times the sum of digits 1, 4, and 7, plus 7 times digits 2, 5, and 8, plus digits 3, 6, and 9 must be divisible by 10. If the check fails on a 9-digit input, the validator calculates the exact 9th digit required by the first 8 digits so you can spot trailing typos immediately.
Check-digit validation stops most manual data-entry errors before payroll or vendor payments bounce. Under eCFR 12 CFR Part 229 Regulation CC, 9-digit MICR routing numbers govern check collection, return routing, and funds availability across US depository institutions.
Weighted Mod-10 checksum arithmetic and expected 9th digit hints
Each position receives a multiplier of 3, 7, or 1 repeating across the 9 digits. Because adjacent weights (3 and 7, 7 and 1, 1 and 3) differ, swapping two neighboring digits changes the weighted sum unless their difference is a multiple of 5. For European cross-border payments, you can also check an international IBAN using ISO 13616 Mod-97 validation before submitting wires.
Transposition and single-digit error detection limits
Changing any single digit alters the weighted sum by a nonzero amount modulo 10 because 3, 7, and 1 are coprime to 10. Spaces and hyphens are stripped automatically before validation, and any non-numeric character or length other than 9 digits triggers a clear error message.
Decoding Federal Reserve districts and institution prefixes
The first 4 digits form the Federal Reserve routing symbol, where digits 1 and 2 encode both the institution category and one of the 12 Federal Reserve districts. Digits 5 through 8 represent the ABA institution identifier, and digit 9 is the check digit.
As outlined in the Federal Reserve System Structure and 12 Districts, the twelve regional Reserve Banks run from District 01 in Boston through District 12 in San Francisco. Validating the prefix catches fabricated numbers that happen to satisfy Mod-10 arithmetic.
| Prefix range | Institution type | District mapping |
|---|---|---|
| 01 to 12 | Commercial banks | Direct district 1 to 12 |
| 21 to 32 | Thrift institutions and credit unions | Prefix minus 20 (1 to 12) |
| 61 to 72 | Electronic transactions | Prefix minus 60 (1 to 12) |
| 80 | Traveler’s checks | No regional district |
Valid ABA prefix ranges from 01 to 80
Numbers starting with 00, 13 through 20, or 81 through 99 are rejected immediately even if their 9th digit satisfies the Mod-10 equation. Subtracting 20 from thrift prefixes or 60 from electronic prefixes recovers the underlying Reserve district from Boston (1) to San Francisco (12).
Routing symbol, institution identifier, and check digit anatomy
When a number passes validation, the result card breaks out the Type, Federal Reserve district, Federal Reserve routing symbol, Institution identifier, and Check digit. Teams preparing European euro transfers alongside US ACH batches can switch to our SEPA XML generator for European ISO 20022 batches.
Batch validating up to 5,000 routing numbers with safe CSV export
Switching the mode selector from One number to A list lets accounts payable and payroll teams paste up to 5,000 candidate numbers at once. The parser splits entries on newlines, commas, semicolons, or tabs and reports the total valid count alongside per-row failure reasons.
According to the Federal Reserve FedACH Services Overview, FedACH processes batch credits and debits across depository institutions using 9-digit routing identifiers. Screening vendor onboarding lists locally prevents rejected NACHA batches, delayed supplier payouts, and costly bank return fees.
Tip: Use Load example in A list mode to test how valid numbers, invalid checksums, and zeroed prefixes appear in the results table and CSV export.
Clicking Download results (CSV) saves a UTF-8 BOM spreadsheet with formula-injection neutralization so Excel and Google Sheets open the file safely without executing leading symbols. For reconciling settled statements afterward, use Bank statement to Excel to extract transaction tables locally.
Offline checksum scope versus live Federal Reserve directory lookups
Every check runs 100% locally in JavaScript with 0 bytes transmitted over the network. Keeping payroll and supplier routing numbers inside your browser avoids exposing sensitive banking identifiers to third-party lookup APIs.
Keeping payroll and vendor bank identifiers inside your browser
Because no external directory query is made, you can paste confidential vendor onboarding sheets without privacy risk. Click Clear at any time to wipe the input box or batch textarea from memory.
All validation logic, district lookups, and CSV formatting run synchronously in your browser tab without touching external servers or browser cookies. Accounting teams can audit 5,000-row vendor master files immediately on air-gapped or corporate-restricted laptops before importing verified routing numbers into ERP payment runs or payroll clearing batches, saving time during monthly onboarding checks.
Why checksum validity does not confirm an active bank account
Passing the ABA checksum confirms mathematical format validity only; it does not verify the bank name, account ownership, or whether an institution supports ACH versus Fedwire. Always confirm active routing instructions directly with the recipient or your bank before sending funds, and prepare QuickBooks QBO bank statement imports locally without uploading client data when reconciling cleared payments.