Educational

Address Cleansing vs Verification vs Standardization

Four terms that often overlap, defined from published sources, with what cleansing did to a messy 10,000-row list and a table of when you need which.

Elizabeth Parker
October 6, 2026 · 8 min read · Last reviewed

Address cleansing is the umbrella term: Smarty defines it as the collective process of standardizing, correcting and then validating a postal address. Parsing splits an address into fields. Standardization rewrites it with postal abbreviations. Verification checks it against authoritative address data for accuracy, completeness and deliverability. An address cleansing API typically runs these steps together. When we cleansed a messy 10,000-row list in October 2026, 7,473 rows (74.7%) came back ready to mail, and 1,192 (11.9%) were set aside for a person to check instead of being changed without a word.

The four terms, defined

Each definition below is quoted from a published source. The last column shows what an API that does that step returns, using sthan.io field names from live calls on October 4, 2026, rechecked on October 6, 2026.

TermDefinitionSourceWhat an API returns
Parsing"a method of breaking down a postal address into individual components so that each can be analyzed, standardized, and validated."Loqate glossarySeparate fields: addressNumber, streetName, streetPostType, unitType, city, stateCode, zipCode
Standardization"A standardized address is one that includes all required address elements and that uses the Postal Service standard abbreviations"USPS Publication 28, section 211One address in postal format, for example 233 S Wacker Dr STE 3300, Chicago, IL 60606-6387
Verification"the crucial process of checking the accuracy, completeness, and deliverability of a physical address against an authoritative, official source of truth."Loqate glossaryA deliverability result, for example dpvConfirmation Y and deliverableStatus Confirmed
Cleansing"the collective process of standardizing, correcting, and then validating a postal address."SmartyThe results of all three steps together

Loqate also notes that verification is "often referred to as Address Validation", while saying the two are slightly different.

One building, two calls, live

The same input, 233 south wacker drive suite3300 chicago illinois, sent to the sthan.io parser and to sthan.io verification on October 6, 2026.

Parser callVerification call
Address returned233 S Wacker Dr, Chicago, IL 60606-7147233 S Wacker Dr, Chicago, IL 60606-7147
UnitNot returned; unit marked UnmatchedNot returned; unit marked Unmatched
DeliverabilityNot part of a parsedpvConfirmation D, deliverableStatus ConfirmedPrimaryOnly: the building is confirmed, the suite is missing
Match signalNear, confidence 0.9Near, confidence 0.9

Both calls standardized the returned address the same way, and both said they could not match the suite glued to its number. Only verification added a deliverability status: D means the primary number was DPV-confirmed and the secondary (unit) information was missing. Here the building was confirmed and the suite was missing, so a form should ask for the suite. With the suite typed as "Suite 3300" and the ZIP included, both calls returned 233 S Wacker Dr STE 3300, Chicago, IL 60606-6387, and verification returned dpvConfirmation Y (Confirmed). Parsing tells you what the parts are. Verification adds a postal deliverability status.

What cleansing 10,000 addresses did

On October 12 and 13, 2026 we ran a 10,000-row spreadsheet through sthan.io Address Cleaner. Every row was a real US address from public address records that had never been sent to us. We made the list messy the way customer lists are: about 40% of rows left as typed, about 20% with two letters swapped in the street name, about 20% with no ZIP (2,009 rows) and about 20% all in lower case. Because we knew the right address for every row, we could check every answer.

Address Cleaner progress while a file runs: 232 of 300 rows cleaned, with counts for verified, corrected, unit missing or not deliverable, needs review, waiting for deliverability verification and not found
While a file runs, every row lands in one of these piles as it finishes. This is a smaller 300-row test file, two thirds of the way through.

Here is where the 10,000 rows ended up:

ResultRowsShareWhat it meansCharged
Verified6,05260.5%Gets mail as typed. Short forms written out, a missing ZIP added.Yes
Corrected1,42114.2%Gets mail after a fix. Every fix is listed next to the row.Yes
Unit missing3793.8%The building gets mail, but the apartment or suite number is missing.Yes
Not deliverable5115.1%A real address the post office does not deliver to.Yes
Needs review1,19211.9%A likely answer that changes more than we can be sure of.No
Not found4454.5%No match.No
Address Cleaner results page for the 10,000-row file: 6,052 verified, 1,421 corrected, 379 unit missing, 511 not deliverable, 1,192 needs review, 445 not found, and 1,679 changes listed
The results page for the 10,000-row file, finished October 13, 2026. Every change is also listed in the file, next to the address as it was typed.

Most fixes were small. Address Cleaner fixed 1,104 misspelled street names, 536 wrong or short town names (like "atl" for Atlanta), 25 street directions and 14 ZIP codes. It also added a ZIP to 1,884 of the 2,009 rows that had none.

Of the 8,363 rows that got an answer we charge for, 8,117 matched the known right address exactly. We read the other 246 by hand: each one was the same address written the postal way, such as a spelled-out word or an added plural. None was a different address.

Row as typedRow after cleansingResult
1321 ROKCY CREEK DR, PFLUGERVILLE TX 786601321 Rocky Creek Dr, Pflugerville, TX 78660-2931Corrected: street name
3794 adamsville dr sw, atl GA 303313794 Adamsville Dr SW, Atlanta, GA 30331-3707Corrected: town
231 N ESSEX AVE, NARBERTH PA (no ZIP)231 N Essex Ave, Narberth, PA 19072-1801Verified, ZIP added
702 LEMNORE AVE, ROCKVILLE MD 20850702 Lenmore Ave, Rockville, MD 20850-1220Unit missing: add the apartment number
2708 W MAIN ST, WAYNESBORO VA 229802708 W Main St, Waynesboro, VA 22980Not deliverable
12049 AUUBRN CT NW, PICKERINGTON OH 4314712049 Auburn Ct, Pickerington, OH 43147-8466Needs review: street name and direction both differ

The last row shows why a review pile matters. "Auburn" is the obvious fix for the typo, but the answer also drops the "NW". That might be the right building or a different one, so a person decides. Your own numbers will depend on your list: a clean export from a CRM will have more verified rows, and addresses typed by customers on a phone may need more fixes.

When you need which

Your goalStep you needWhy
Split one address field into street, city, state and ZIP columnsParsingYou need the parts, not a postal check
Store or print addresses in one consistent postal formatStandardizationPublication 28 abbreviations and formatting; adding a missing ZIP+4 needs a lookup in postal data
Check that an address is deliverable before you shipVerificationA verification call returns a postal deliverability status
Fix an old customer list in one passCleansingStandardize, correct and validate every row

In practice the steps stack. Loqate describes the order: once the data is parsed, "the next step is to standardize it and convert it to a consistent format." Smarty adds that before an address can be validated it must first be in the official postal format. The sthan.io verification API, for example, returns the standardized address and the deliverability result in one call.

Where sthan.io fits. sthan.io offers these steps two ways. For code, the US Address Parser API returns separate fields with a match tier and confidence (3,000 free a month, up to 100 a day, then $8 a month for 10,000), and the US Address Verification API returns the standardized address, ZIP+4 and a deliverability status (3,000 free a month, up to 100 a day, then $12 a month for 10,000). Neither free tier needs a credit card. For a whole file, Address Cleaner takes an Excel or CSV file of up to 100,000 rows and returns every row cleansed: the first 100 rows a day are free, then $1.20 per 1,000 rows verified against national address records, with a $1.00 minimum. Rows that need review or are not found are free. The 10,000-row file above cost $9.94. sthan.io is not CASS-certified.

Frequently Asked Questions

Smarty defines address cleansing as the collective process of standardizing, correcting, and then validating a postal address. Loqate describes it as reviewing and reformatting postal addresses to make them accurate, complete, and updated.
Standardization rewrites an address in postal format; USPS Publication 28 calls an address standardized when it has all required elements and uses the standard abbreviations. Verification checks the accuracy, completeness and deliverability of the address against an authoritative source.
Yes, it usually comes first. Loqate describes parsing as breaking an address into individual components so that each can be analyzed, standardized, and validated.
The terms are often used for the same thing. Loqate says verification is often referred to as validation, while noting the two are slightly different.
Use parsing to split an address into columns, standardization for a consistent postal format, and verification for a postal deliverability status. A sthan.io verification response includes the standardized address, the ZIP+4 and a deliverability status in one call.
In our October 2026 test of 10,000 messy rows, 60.5% were deliverable as typed, 14.2% were fixed automatically, 8.9% were real addresses that need a unit number or do not get mail, and 11.9% needed a person to check. A clean list will do better, and a list typed by customers on a phone may do worse.

Sources

Read October 4, 2026, and rechecked October 6, 2026: smarty.com/articles/address-cleansing; loqate.com/en-us/glossary pages for address parsing, address verification and address cleansing; USPS Publication 28 section 211 on pe.usps.com; live sthan.io v2 address parser and v2 address verification responses (the same input to both, October 6, 2026); sthan.io/pricing/united-states. sthan.io Address Cleaner run of a 10,000-row test file, October 12 to 13, 2026, checked row by row against the known right addresses. Prices change; check the vendor page before you buy.

Try parsing and verification free

3,000 parses and 3,000 verifications a month, no credit card.

Elizabeth Parker
Written by Elizabeth Parker

Elizabeth Parker writes about how verification works, deliverability statuses, missing unit numbers, and how to measure an address API's accuracy.

More from Elizabeth Parker