Address validation — because a notice that doesn't arrive doesn't count
Several of your compliance obligations are discharged by mail. A B-Notice has to reach the payee. A recipient 1099 has to be furnished. TIN Comply validates and standardizes every payee address against USPS records first — and when one can't be verified, tells you exactly why and what to fix.
Runs in the same call as IRS TIN matching. Portal, bulk, and API.
37th District of Texas
Travis County
Corrections applied during standardization: ZIP+4 corrected.
Part of every TIN Comply plan from $20/mo — not a separate purchase. See pricing
This isn't shipping. It's whether your compliance mail lands.
Most address validation is sold for parcels and checkout forms. The reason it matters in vendor compliance is narrower and sharper: some of what you're required to do, you're required to do by mail — and a bad address quietly breaks it.
B-Notices that never arrive
A CP2100 gives you a short window to notify the payee. Mailing to an unverifiable address consumes the window without reaching anyone.
Returned recipient 1099s
Furnishing a recipient copy is an obligation. Returned mail turns into rework at exactly the point in the calendar when there's no slack.
Stale vendor master data
Addresses decay faster than names. A vendor file that's never been standardized carries years of moves, typos, and missing unit numbers.
Undocumented outreach
"We sent it" is weaker than "we sent it to a USPS-verified address on this date." One of those supports a reasonable-cause position.
Standardized is not the same as deliverable. An address can be corrected into perfect USPS format and still come back as one where deliveries aren't made, or where the building is valid but the unit number couldn't be confirmed. Those are reported separately, because they need different follow-up.
More than a pass/fail flag
- The standardized address in USPS format — the version that should be stored in your vendor master.
- ZIP+4 and delivery point digits, which is what actually determines routing.
- County and congressional district, useful for jurisdiction-driven reporting and public-sector workflows.
- An itemized list of corrections applied during standardization — so you can see whether the ZIP+4 changed or the whole street name did.
- A specific reason on failure, plus the recommended fix and a route into W-9 correction outreach.
The corrections list is the part people underestimate. A silently "fixed" address that actually swapped the street name is a very different thing from one that gained a ZIP+4 — and only one of those is safe to write back to your vendor master unreviewed.
Issues identified by USPS: the street number is confirmed, but the secondary unit could not be verified.
Incorrect street number, a typo in the street name, or a newly built address not yet in the USPS database.
Ask the vendor to confirm their mailing address, then re-run validation.
USPS validation results — and what each one actually means
Address APIs tend to return a number. These are the results you'll see, in plain language, with the action each one calls for.
| Result | What it means | What to do |
|---|---|---|
| Verified | Address successfully verified against USPS records. | Store it |
| Valid, but no delivery | The address is real, but USPS does not deliver there. | Request an alternate mailing address. |
| ZIP not recognized | The ZIP isn't recognized and the area can't be derived from city and state. | Confirm the ZIP with the vendor. |
| No street address | No street address was supplied at all. | Collect it — usually a data gap, not an error. |
| Street not found in ZIP | No matching street name in that ZIP or the surrounding area. | Confirm the street name. |
| House number missing or unmatched | The street number is absent or doesn't match USPS records for that street. | Confirm the number. |
| Number out of range | The street matched as an alternate name, but the house number isn't in the expected range. | Verify the full address. |
| Unit not verified | The building is valid but the secondary unit couldn't be confirmed. | Confirm unit |
| Multiple matches | Ambiguity in the suffix, direction, street name, unit, ZIP or city produced several candidates. | Disambiguate with the vendor. |
| Too many corrections needed | Correcting it would require more changes than can be made confidently. | Re-collect the address. |
| Flagged as incorrect | The address appears on a USPS list of known-bad addresses. | Do not mail |
Corrections are itemized too — ZIP+4 corrected, street suffix corrected, city corrected, house or unit number corrected, street standardized, and so on — so a record that changed a lot is distinguishable from one that changed a little.
Never a separate step
Address validation isn't a product you have to remember to use — it's part of the same submission.
With TIN matching
Submit a TIN, name and address and every validation that data supports runs in one call.
In bulk
Standardize an entire vendor population in one upload, ahead of a B-Notice or year-end mailing.
Via API
Validate at the point of entry so a bad address never reaches the vendor master.
Into W-9 outreach
An unverifiable address can trigger a correction request the same way a TIN mismatch does.
Questions about address validation
Why does this matter for 1099 compliance?
Because several obligations are discharged by mail. A B-Notice has to reach the payee; a recipient copy of a 1099 has to be furnished.
An address that fails USPS verification is a mailing that may never arrive — which means the obligation may not be met even though you sent it on time. That's a failure mode that doesn't show up anywhere until it's too late to fix.
What exactly does it return?
The USPS-standardized address, ZIP+4, delivery point digits, county, congressional district, and coordinates — plus an itemized list of the corrections applied during standardization, so you can see precisely what changed.
What happens when an address can't be verified?
You get the specific reason rather than a generic failure — unrecognized ZIP, missing or out-of-range house number, street not found in that ZIP, unverifiable unit, and so on.
Each comes with the likely cause and the recommended correction, and the record can be routed straight into W-9 correction outreach.
Is a standardized address the same as a deliverable one?
No, and conflating the two is a common mistake. An address can be standardized into correct USPS format and still be flagged as one where deliveries aren't made, or one where the building is valid but the secondary unit couldn't be confirmed.
Those are reported separately because they call for different follow-up — one needs a new address, the other just needs a unit number.
Does it run with IRS TIN matching?
Yes. Submitting a TIN, legal name and address runs every validation that data supports in a single call, so address validation returns alongside IRS TIN matching and sanctions screening rather than as a separate step you have to remember.
Can addresses be validated in bulk?
Yes — it's one of the validation types available in bulk file processing, so an entire vendor population can be standardized in one upload before a B-Notice campaign or a year-end mailing.
The rest of the vendor validation stack
Make sure the mail actually lands
Standardize every payee address before the B-Notices go out — and know exactly which ones won't reach anyone, while there's still time to ask.
Included in the same call as IRS TIN matching.