How the 9-digit US EIN structure and IRS prefix ranges work
A US Employer Identification Number consists of 9 digits formatted with a hyphen after 2 digits, where the first two digits represent the issuing IRS campus or electronic pool and the remaining 7 digits form a sequential serial. This structure is defined in IRS Publication 1635 Understanding Your EIN for corporations, partnerships, sole proprietors, nonprofits, trusts, and estates.
This client-side private EIN validator normalizes both compact 9-digit strings and hyphenated inputs locally in memory.
Decoding two-digit IRS campus codes and online application pools
Historically, the IRS assigned distinct two-digit prefixes to regional service centers such as Andover (10, 12), Brookhaven (01 through 06, 11, 13, 14), Cincinnati (30, 32, 35 through 38), Ogden, and Philadelphia. Modern online applications draw from national internet blocks including 20, 26, 27, 45 through 47, 81 through 88, 92, 93, and 99.
Because businesses keep their assigned EIN permanently even after moving headquarters, a legacy campus prefix does not have to match a vendor’s current mailing state. If you also onboard North American suppliers across the border, you can verify 9-digit Canadian Business Numbers with Luhn checks in the same offline suite.
Why the seven-digit serial number cannot be all zeros
Even when the two-digit prefix falls inside an assigned range, the checker rejects any number whose seven trailing digits are 0000000. Placeholder strings such as 12-0000000 or 99-0000000 fail immediately so accounting teams catch dummy Form W-9 entries before importing vendor files.
Do US Employer Identification Numbers have a mathematical check digit?
US EINs do not include a mathematical check digit, meaning no Luhn or Modulo calculation can detect a single-digit typo inside the seven-digit serial. Only the 9-digit length, the assigned two-digit prefix list, and the non-zero serial rule can be verified offline, as outlined in IRS Employer ID Numbers Guidance.
When you compare international tax identifiers, the absence of a check digit sets the US system apart from Commonwealth and European registries. For example, Australian companies use a Modulo-10 Australian Company Number checker where a transposed digit fails the checksum automatically.
| Identifier type | Total digits | Formatting pattern | Mathematical check digit | What offline check verifies |
|---|---|---|---|---|
| US EIN | 9 digits | XX-XXXXXXX |
None | Assigned IRS 2-digit prefix and non-zero serial |
| US SSN / ITIN | 9 digits | XXX-XX-XXXX |
None | Not supported in EIN checker |
| Canada BN | 9 digits | XXXXXXXXX |
Luhn (Mod-10) | Root checksum and 2-letter program code |
| Australian ABN | 11 digits | XX XXX XXX XXX |
Weighted Mod-89 | Checksum after subtracting 1 from first digit |
| Polish NIP | 10 digits | XXX-XXX-XX-XX |
Weighted Mod-11 | Official checksum rejecting remainder 10 |
Format validation versus official IRS TIN Matching for Form 1099
Pre-screening vendor tax IDs before year-end filing prevents costly IRS CP2100 notices and mandatory backup withholding errors. Understanding what offline validation catches versus what requires government e-Services keeps your compliance workflow accurate.
Catching W-9 typos before vendor onboarding
When accounts-payable staff receive a handwritten or scanned Form W-9, common errors include eight-digit or ten-digit typos, transposed XXX-XX-XXXX SSN formatting, or unassigned prefixes like 00, 07, 08, 09, 17 through 19, 28, 29, 49, 69, 70, 78, 79, 89, 96, or 97. Running a quick check flags those structural mistakes instantly while you also catch ACH payment routing typos before vendor payouts.
Confirming legal name and TIN pairing through IRS e-Services
Because EINs lack a checksum and offline tools never query government databases, a passing format check does not confirm that an EIN is active or belongs to a specific company name. Authorized Form 1099 payers must verify legal name-and-TIN combinations through IRS Taxpayer Identification Number (TIN) Matching before filing information returns.
Tip: Treat offline structural checks as a fast first-pass hygiene filter on W-9 spreadsheets, not as certified tax or legal advice. Always retain signed W-9 forms and confirm active payer-payee matches with a qualified accountant or tax authority through official IRS channels.
Batch checking up to 1,000 EINs and exporting formula-safe logs
Finance teams preparing annual 1099-NEC or 1099-MISC sweeps often need to clean hundreds of vendor records at once. The bulk checker processes multi-line lists locally without exposing sensitive tax identifiers to external servers.
Filtering passed and failed rows across 1,000-line batches
Paste up to 1,000 lines (up to 50,000 characters, or roughly 50 KB of text) into the EIN or list textarea, one number per line, in either XX-XXXXXXX or unhyphenated 9-digit form. When checking multiple lines, use the All, Passed, and Failed filter buttons above the table to isolate invalid prefixes and zero-serial entries.
If your vendor master file includes European contractors alongside US suppliers, you can also validate French 14-digit SIRET numbers for European suppliers in a separate browser tab.
Formula-injection protection in CSV and Excel (.xlsx) exports
Click Download results (CSV) or Download Excel (.xlsx) to save an RFC 4180 audit log containing the raw input, normalized string, formatted XX-XXXXXXX value, pass/fail status, and IRS campus origin. Every text cell passes through spreadsheetText() sanitization to prefix leading =, +, @, -, or | characters, protecting downstream Excel workbooks against CWE-1236 formula injection while keeping 0 bytes on external networks.
The output includes 5 structured columns so compliance teams can audit every checked line item without reformatting.