Overview
Every identity document, license number, and financial identifier in the United States follows a specific, publicly documented format — a fixed length, an allowed character set, and often a mathematical check digit buried in the last position. That structure exists so that a single transposed digit or a mistyped letter can be caught before the number ever reaches a database. Airlines catch it. Clearinghouses catch it. The DMV catches it. The problem is that they usually catch it after you've submitted the form, which means a wasted trip, a delayed claim, or a bounced application.
This guide walks through eight identifiers that Americans regularly need to enter correctly the first time: a US passport number, a state driver's license, a vehicle's VIN, a Medicare Beneficiary Identifier, a healthcare provider's NPI, a business's DUNS number, a security's CUSIP or ISIN, and a Known Traveler Number for TSA PreCheck or Global Entry. Each of these has a different length, different allowed characters, and in several cases a check-digit formula that a human cannot verify by eye but a validator can confirm instantly.
None of the tools linked below check a number against a live government or financial database — they check structure only, which is exactly the layer where most real-world submission errors occur: a swapped digit, a letter that looks like a number, or a format from the wrong document entirely. Running a number through the matching validator before you submit it anywhere takes ten seconds and eliminates the single most common cause of a rejected form.
Step 1: Confirm Your US Passport Number Format
A modern US passport number is 9 characters long. Passports issued after 1981 use a straightforward 9-digit numeric format, but some special-issue and older passports include a leading letter (for example, diplomatic or official passports use different prefixes). Because airline booking systems, visa applications, and ESTA forms often enforce their own input masks, a passport number that's perfectly valid can still get rejected by a form that only accepts 9 digits with no letters, or vice versa.
The most common submission error isn't an invalid passport — it's a transcription mistake. People routinely confuse the number 0 with the letter O, or drop a leading zero because a spreadsheet or form auto-formatted the field as a number. A 9-digit passport number that starts with a zero will silently lose that zero if it's ever pasted into an Excel cell formatted as a general number, and the resulting 8-digit string will fail every downstream check.
Before entering a passport number into any government or travel form — TSA PreCheck enrollment, a visa application, an airline booking, or a hotel's international guest registration — run it through the US Passport Validator. It confirms the number matches the expected length and character pattern, which catches the dropped-zero and letter/number confusion errors before they reach a form that may not tell you exactly what went wrong.
If you're renewing or applying for the first time, double-check the number against the physical document itself rather than a scanned copy or a photo, since image compression and OCR tools frequently misread the numeral 1 as a lowercase l or vice versa in low-resolution scans.
Step 2: Check Your State Driver's License Number Pattern
Unlike a passport, which follows one federal format, a US driver's license number format is set independently by each state's DMV. Some states use a purely numeric string (commonly 8 or 9 digits), others use a single leading letter followed by digits, and a handful of states embed encoded information like sex or birth date into specific digit positions. There is no universal rule, which means a license number that's valid in one state's format would be rejected as malformed if it were submitted as though it belonged to a different state.
This matters in practice whenever a form asks for both a license number and an issuing state — background check services, notary applications, and car rental agreements all cross-reference the two fields. If the number doesn't match the expected pattern for the state you selected, some systems reject the submission outright, while others silently accept it and only fail later during a manual review, which delays the process without telling you why.
The most frequent mistake is copying a license number from an ID card where the state's format includes a letter that resembles a number — for example, a leading "O" versus a "0," or an "I" versus a "1" — and the OCR scan on some rental car kiosks or check-in systems misreads it as the wrong character. A second common error is simply entering a license number under the wrong state, particularly for people who moved states recently and are still mentally defaulting to their old ID.
Use the US Driving Licence Validator to confirm your license number matches the format expected for its issuing state before submitting it on a form, a rental agreement, or a professional licensing application that cross-checks the two fields.
Step 3: Validate a Vehicle Identification Number (VIN)
A VIN is a fixed 17-character code assigned to every motor vehicle manufactured for the US market since 1981. It deliberately excludes the letters I, O, and Q because they're easily confused with the digits 1 and 0 — if a VIN you're reading appears to contain any of those three letters, it has been misread, mistyped, or is fraudulent. Position 9 of the VIN is a check digit, calculated using a weighted-sum formula defined by the National Highway Traffic Safety Administration (NHTSA) across the other 16 characters, and a VIN that fails this calculation is not a valid VIN regardless of how plausible it looks.
VIN errors show up constantly in used-car transactions, insurance quotes, and DMV title transfers. A single transposed digit produces a VIN that might still be 17 characters and might still "look right," but will pull up the wrong vehicle's history — or no vehicle at all — when run through a vehicle history report. Because these reports often cost money per lookup, catching a transposition error before you pay for the report saves both time and the report fee.
The physical VIN plate, the vehicle's registration, the title, and the insurance card should all show an identical 17-character string. In practice they sometimes don't, usually because someone transcribed the VIN by hand from a badly lit dashboard plate or a low-resolution photo, and confused a 5 for an S or an 8 for a B.
Before you rely on a VIN for a vehicle history report, a title transfer, or an insurance application, run it through the VIN Validator to confirm both the character set and the position-9 check digit are correct. This single check will immediately flag a mistyped character even if the rest of the VIN looks perfectly plausible.
Step 4: Verify a Medicare Beneficiary Identifier (MBI)
Since 2018, Medicare has used an 11-character Medicare Beneficiary Identifier (MBI) instead of the old Social Security Number-based Health Insurance Claim Number. The MBI format is deliberately restrictive: it uses only digits 0-9 and a specific subset of letters, explicitly excluding S, L, O, I, B, and Z because each one is visually similar to a digit or another letter (S/5, L/1, O/0, I/1, B/8, Z/2). Positions in the MBI alternate between numeric and alphanumeric characters in a fixed pattern.
For healthcare providers and billing staff, an incorrectly formatted MBI is one of the most common reasons a Medicare claim gets rejected before it's even reviewed for medical necessity — the claim simply bounces at the eligibility-check stage. For patients, an MBI typo on an enrollment or benefits form can delay coverage confirmation by weeks, since Medicare's systems will not match a malformed identifier to an existing beneficiary record.
The excluded letters are exactly the ones most likely to be mistyped from a scanned or photographed Medicare card, since low-resolution images make S/5 and B/8 nearly indistinguishable. If an MBI you've transcribed contains any of the six excluded letters, that's an immediate signal the number was misread rather than a sign the beneficiary has an unusual identifier.
Before submitting a claim, entering enrollment information, or updating billing records, check the MBI against the Medicare ID Validator to confirm it uses only the allowed character set and matches the expected 11-character structure.
Step 5: Confirm a National Provider Identifier (NPI)
Every individual healthcare provider and healthcare organization in the US that transmits health information electronically is required to have a National Provider Identifier (NPI) — a 10-digit number where the final digit is a Luhn check digit computed against a fixed 24-digit prefix specific to the NPI system (this is the same Luhn algorithm used for credit card numbers, but applied with an NPI-specific prefix). This means an NPI is not just any random 10-digit string; only numbers that satisfy this specific checksum are valid.
NPI errors are expensive in a very concrete way: a claim submitted with a malformed or mistyped NPI is rejected by the clearinghouse before a human ever reviews it for medical necessity or coverage, which means the entire claim has to be corrected and resubmitted, adding days or weeks to the reimbursement cycle. For a busy practice submitting hundreds of claims a week, a single transposed digit in a commonly-used referring provider's NPI can cascade into dozens of rejected claims before anyone notices the pattern.
The most common source of NPI errors is manual entry from a printed referral letter or an outdated provider directory, where a provider's NPI was recorded incorrectly at some point and has been copied forward ever since. Because the check digit will catch a single-digit transposition but obviously can't catch an NPI that was wrong from the very first time it was recorded, it's worth periodically re-verifying NPIs for your most frequently billed referring providers.
Run any NPI through the NPI Validator before submitting a claim, credentialing application, or prior authorization request — it takes a fraction of a second and can prevent a multi-week reimbursement delay.
Step 6: Check a DUNS Number for Federal Contracting
A DUNS (Data Universal Numbering System) number is a 9-digit identifier issued by Dun & Bradstreet, historically required for organizations registering in SAM.gov to do business with the federal government, apply for federal grants, or bid on federal contracts. While the federal government has been transitioning toward the newer Unique Entity Identifier (UEI) system, DUNS numbers still appear throughout legacy documentation, older grant applications, and many state and local government contracting portals that haven't migrated away from the DUNS standard.
The most common confusion is mixing up a DUNS number with an EIN (Employer Identification Number) — they're both 9-digit numbers issued to businesses, but they come from completely different systems (Dun & Bradstreet versus the IRS) and are not interchangeable on forms that specifically ask for one or the other. A grant application that requests a DUNS number will reject an EIN entered into that field, and the two numbers look similar enough at a glance that this substitution happens regularly, especially when a form doesn't clearly label which identifier it wants.
A second common error is simply mistyping a digit when copying a DUNS number from an old registration document, since many organizations only look up their DUNS number once a year or less and rely on whatever document they can find, which increases the chance of copying from a source with an existing typo.
Before entering a DUNS number into a SAM.gov registration, a grant application, or a state contracting portal, check its format with the DUNS Validator to confirm it's structurally valid — and if a form specifically wants a DUNS number rather than an EIN or UEI, double check you're entering the identifier the form is actually asking for.
Step 7: Validate a CUSIP or ISIN Securities Identifier
Financial securities in the US and Canada are identified by a 9-character CUSIP (Committee on Uniform Securities Identification Procedures) number, while internationally traded securities use a 12-character ISIN (International Securities Identification Number) that wraps a two-letter country code and a check digit around a CUSIP-like core. Both formats include a check digit calculated from the preceding characters, meaning a single mistyped character will produce a code that fails validation even if it's the correct length.
The confusion between the two formats shows up constantly when investors move a security identifier between platforms — a brokerage statement showing a 9-character CUSIP won't work directly on an international trading platform or a European settlement system that expects the 12-character ISIN, and simply padding a CUSIP with extra characters does not produce a valid ISIN (the country code and check digit have to be correctly calculated, not just appended). Someone converting between the two formats manually, without recalculating the check digit, will frequently end up with an ISIN-length string that fails validation.
For anyone reconciling a portfolio, entering a security into a tax reporting tool, or double-checking a trade confirmation, a single mistyped character in a CUSIP or ISIN can result in a mismatch that looks like a data error in the reporting system, when the actual problem is a transcription mistake at the point of entry.
Use the CUSIP/ISIN Validator to check both formats — including their respective check digits — before entering a security identifier into a portfolio tracker, tax software, or trade confirmation form.
Step 8: Verify a Known Traveler Number Before You Fly
A Known Traveler Number (KTN) is issued when you enroll in TSA PreCheck, Global Entry, NEXUS, or SENTRI, and it's the number you enter when booking a flight so your boarding pass carries the PreCheck indicator that lets you use the expedited security lane. It's typically 9 digits and is printed on your Trusted Traveler Program membership card, and it also appears in your online Global Entry or TSA PreCheck account.
The single most common reason a traveler shows up at the airport expecting PreCheck and doesn't get it is a KTN typo entered at booking — a single wrong digit, or entering the number from an expired membership card instead of a renewed one (renewal sometimes issues a new KTN, which people don't always realize). Airlines match the KTN against the TSA's Secure Flight database at booking, and if the number doesn't match exactly, the PreCheck indicator simply won't appear on the boarding pass, with no error message explaining why.
A second common mistake is entering a family member's KTN instead of your own when booking multiple travelers on a single reservation — since the numbers are the same length and format, this substitution is easy to make and won't be flagged until you're standing in the standard security line wondering why PreCheck didn't apply.
Before booking a flight, run your Known Traveler Number through the Known Traveler Number Validator to confirm it matches the expected 9-digit format, and double-check it against your Trusted Traveler Program card or online account rather than relying on memory — especially if your membership has recently renewed.
Step 9: Build a Pre-Submission Habit
The eight identifiers in this guide share a common failure mode: they're all rejected downstream — by an airline, a clearinghouse, a DMV, or SAM.gov — rather than at the point of entry, which means the person entering the number rarely gets immediate, specific feedback about what went wrong. A rejected claim, a bounced grant application, or a boarding pass without PreCheck all look like unrelated problems, but the root cause is frequently the same: a single mistyped character in a structured identifier.
The practical fix is to treat format validation as a standard pre-submission step rather than something you only do after a rejection. For recurring workflows — a billing office submitting NPIs and MBIs daily, or a contracting office handling DUNS numbers regularly — building a validation check into the intake process (even a simple copy-paste into the relevant validator before the number goes into the official system) catches transposition errors in seconds rather than days.
For one-off submissions like a passport number on a visa form or a Known Traveler Number before a single flight, the habit is simpler: paste the number into the matching validator once, confirm the structure is correct, and only then enter it into the official form. This single step eliminates the majority of typo-driven rejections covered in this guide.
Key Terms
- VIN (Vehicle Identification Number) — a fixed 17-character code assigned to every US motor vehicle, excluding the letters I, O, and Q, with a check digit at position 9.
- NPI (National Provider Identifier) — a 10-digit identifier for US healthcare providers, with a Luhn check digit calculated against a fixed 24-digit NPI-specific prefix.
- Medicare ID / MBI — the 11-character Medicare Beneficiary Identifier, which excludes the letters S, L, O, I, B, and Z to reduce transcription errors.
- DUNS Number — a 9-digit business identifier issued by Dun & Bradstreet, historically required for federal contracting and grant registration.
- CUSIP/ISIN — CUSIP is a 9-character US/Canada securities identifier; ISIN is a 12-character global securities identifier built around a similar core with a country code and check digit.
- Known Traveler Number — the identifier issued through TSA PreCheck, Global Entry, NEXUS, or SENTRI enrollment, entered at flight booking to trigger expedited security screening.
- US Passport Number — the 9-character identifier printed on a US passport, typically all-numeric for standard books issued after 1981.
- Check Digit — a single digit at a fixed position in an identifier, calculated from the other digits using a defined formula, used to detect transcription errors.