What is NCOA processing? Why mail lists go stale and how to fix them

NCOA processing checks the names and old addresses on a mailing list against permanent change-of-address records filed with USPS. If the name and address clear the matching rules, you may get a new address back. If they don't, you may get a code explaining why. The practical reason to run it is simple: don't spend production and postage on mail addressed to people, families, or businesses that have moved.

The proper name for the service is NCOALink. USPS maintains the change-of-address data and licenses approved organizations to process it securely. Its limits matter, especially on a B2B list. NCOA can't tell you whether Jane still works at Acme, and it won't uncover a move nobody filed. I treat it as one cleaning pass, never as proof that a piece will find the right desk.

How NCOA processing works

You send recipient names and postal addresses through an authorized processing workflow. The addresses are usually parsed and standardized first using current CASS-certified software. A record entered as "125 North Main Street, Suite 4" might come back as "125 N MAIN ST STE 4," along with ZIP+4 and other postal codes when USPS data supports them.

Only then does NCOALink compare the standardized record with permanent change-of-address filings. A street match isn't enough. The name and old address have to agree closely enough under USPS matching logic, which is why a perfectly recognizable address can still produce no update.

Names matter in a shared building. NCOALink sorts matches into three broad move types. An individual move covers one named person. A family move was filed under a shared surname. A business move applies to a company or organization.

A strong match may return the new address. Plenty of records won't. Their codes can indicate no match, a move without a forwarding address, an insufficient name match, or a new address that can't be used. I want those codes in the output. A processor that quietly swaps whatever it can and hides the rest makes review harder than it needs to be.

Keep the submitted address, standardized old address, returned address, and match or reason code as separate fields. Keep the processing date too. This sounds fussy until an old CRM sync restores the bad address you just fixed, or a questionable business update needs to be traced three months later.

For a fuller preflight sequence, see this address verification workflow for direct mail.

What the 18-month and 48-month files mean

The two common NCOALink service levels look back across different periods of permanent change-of-address records. That's all the numbers mean. They aren't promises that USPS will forward a mailpiece for 18 or 48 months.

USPS supplies 18 months of data to limited-service licensees and 48 months to full-service licensees. So the provider's license level determines the history available. Ask which window was actually used. "NCOA processed" isn't a complete answer.

Here's the easy mistake. Your CRM has records nobody has touched for three years, but the list gets an 18-month pass. Someone who moved two years ago can be missed even though the matching worked exactly as designed. Their filing is simply outside the window.

The 48-month file is the better choice for older records, though it still has an edge. Moves filed more than four years ago no longer appear. For records that old, current company and contact research will usually tell you more than another run against the same file.

What NCOALink catches and what it misses

NCOALink is good at one specific job. A person, family, or business filed a permanent change with USPS, and your list has a compatible name at the old address. In that situation, it can catch an ordinary household move or a properly filed office relocation before you've paid for print and postage.

Some results need judgment. A move may not include a usable forwarding address. I wouldn't automatically apply a family move to a piece meant for a business contact. And if a business move conflicts with fresher information from the account owner, I'd hold the record for review rather than trust the batch process.

What slips through? Quite a bit:

• A person or business moved without filing a permanent change of address.
• A temporary forwarding request was used instead of a permanent move.
• The list name is too different from the name on the filing.
• A company changed its legal name, used a division name, or filed under another variation.
• A contact left the company while the company remained at the same address.
• A remote employee never worked at the headquarters address on the list.
• The building is valid, but the suite or internal mail routing is wrong.

Business moves are especially messy. Consumers have good reasons to forward bills, government mail, and personal correspondence. Companies are less consistent, and branch closures, hybrid work, acquisitions, and registered offices don't fit neatly into the idea of a move. In my experience, employment and office-status checks catch B2B failures that NCOA was never built to find.

A clean result means "no matching filed move found." It doesn't mean "this contact is here."

CASS vs NCOA vs DPV

People lump these checks together. They shouldn't. Each answers a different question.

CASS stands for Coding Accuracy Support System. It evaluates the software used to standardize, correct, and code addresses. That processing can fix street suffixes, directionals, city names, and ZIP Codes, then add postal information when there's a reliable match.

DPV stands for Delivery Point Validation. It checks whether the house number or unit-level delivery point appears in USPS delivery data. The street may be real while "Suite 900" isn't. DPV is what exposes the difference.

NCOA asks a separate question: did the recipient move? A perfectly standardized, DPV-confirmed address may belong to an office the target company left last month. The reverse matters too. A correct NCOA update still has to produce a deliverable new address.

My practical order is CASS and DPV first, then NCOA. Validate returned addresses again if the workflow doesn't do that automatically. Contact, company, and suppression checks come last. The steps for building a deliverable B2B mail list cover that wider process.

Why B2B mailing lists go stale so fast

Roughly 10% of Americans move in a typical year, based on broad USPS household and population reporting. The exact number shifts with the year and the way it's measured. For planning purposes, the useful fact is that a consumer address file starts losing accuracy as soon as it's saved.

Business data goes stale in more ways, and some are harder to spot. Companies relocate, close branches, merge, rename offices, adopt remote work, or change receiving policies. Meanwhile, contacts switch jobs or departments while the street address remains perfectly valid. Industry benchmark reports often show substantial annual job-title and employment turnover, but the range varies too much by market for one tidy number to be honest.

I separate that decay into two buckets:

1. Postal staleness: The address itself is wrong or incomplete.
2. Recipient staleness: The location is deliverable, but the intended person or company is no longer there.

NCOA mainly helps with the first. B2B research and CRM ownership checks have to handle the second, which is often the bigger problem on an account-based list.

Measure both rates by source. I like to record the share updated by NCOA, the share rejected during address validation, the share removed after employment review, and the confirmed undeliverables after the campaign. One blended "bad address" number tells you almost nothing. You need to know whether the trouble came from an old CRM segment, event data, or a purchased list.

Bad address data also distorts campaign reporting. No one can respond to a piece that never arrived. When you compare results with B2B direct mail response-rate benchmarks, separate known undeliverables from delivered records.

When a B2B list needs NCOA processing

Run NCOA close to the mail date, after you've chosen the audience and before final production. A master database processed six months ago doesn't tell you much about the export sitting in front of you today.

I wouldn't skip it when:

• The list has never been processed or the processing date is unknown.
• Records came from an older CRM segment, acquisition, event, or outside source.
• You are mailing dormant customers or closed-lost prospects.
• A campaign includes residential addresses or remote employees.
• Returned mail has increased.
• The piece is costly enough that one bad address matters.
• Your mailing must meet the applicable USPS Move Update standard.

For eligible commercial First-Class Mail and USPS Marketing Mail, USPS rules generally require an approved Move Update method within 95 days before the mailing date. NCOALink is one accepted method. Confirm the current rules and exact mail class with the team preparing the mailing. Preparation and eligibility details matter here.

Frequency should follow risk. If you mail weekly, make processing part of every production run. If you mail quarterly, clean each final audience. And for a high-cost gift, I'd directly confirm the recipient and location shortly before sending even when NCOA reports no move. The cost of one miss can justify the extra check.

Don't apply every match blindly. Individual, family, and business moves need to follow the campaign's recipient rules. Hold the ambiguous ones, and keep suppressions for earlier hard returns. Then write verified changes back to the CRM with a source and date. That makes the next triggered direct mail campaign safer instead of repeating the same failure.

Frequently asked questions

What does NCOA processing mean?

It means matching names and old addresses against permanent change-of-address records filed with USPS. A licensed NCOALink process can return a new address for a qualifying match or a reason code when it can't. It reduces mail sent to recorded movers. It won't verify current employment or find an unreported move.

How often should you run NCOA processing?

Run it before each meaningful mailing and as close to production as practical. At minimum, process again when the previous run falls outside the timing required for your mail class or the list has changed. Expensive B2B sends need a fresh person-and-company check too. NCOA can't confirm who works at an address.

Does NCOA verify an address?

No. NCOA alone doesn't verify that an address is deliverable. CASS-standardized matching and DPV handle formatting and delivery-point checks; NCOA looks for a permanent move tied to a matching name and old address. A complete workflow uses all three, then verifies the B2B recipient.

What is the difference between 18-month and 48-month NCOA?

It's the reach of the change-of-address history. Limited-service NCOALink covers the previous 18 months; full-service processing covers 48 months. ANKLink can flag a move from months 19 through 48 without returning the new address. Older lists, and lists cleaned infrequently, usually benefit from the longer window.