Address Matching Verification: Formats, Abbreviations, Units

Address matching verification means comparing the address written on one document with the address on another document, the application form, or a reference source, and deciding whether they describe the same delivery point. "Unit 900, 602 Cobden Rd" on a bank statement and "900-602 COBDEN ROAD" on a utility bill are the same place, so an exact string comparison would wrongly reject them. A reliable check standardizes both addresses, compares them component by component (unit, civic number, street, municipality, province, postal code) and sends only genuine differences to a person.

This article is provided for informational purposes and does not constitute legal advice. Consult a qualified professional for situation-specific guidance.

Which fields are compared, and against what

The comparison is always field against field. In a typical applicant file the same residential address shows up in four or five places, each with its own habits.

The first decision is which source is the anchor. In most onboarding files it is the address the applicant declared, and every document is compared to it. Comparing two documents only to each other lets two wrong addresses agree.

Step 1: standardize before comparing

Standardization puts each address in the same shape so remaining differences are real. Canada Post's civic address guidelines describe three accepted placements for a unit number: before the civic number with a hyphen, after the street information with a unit identifier, or on the line above the street information. Its example shows both "900-602 COBDEN RD" and "602 COBDEN RD APT 900". Where a unit number has been assigned, Canada Post treats it as an integral part of the address (Canada Post), so a check that drops it changes the delivery point.

Five rules cover most of the noise:

1. Fold case and strip punctuation: "602 COBDEN RD., APT. 900" becomes "602 cobden rd apt 900".
2. Map street types and directions to one form: Rd/Road, St/Street, Ave/Avenue, Blvd/Boulevard, N/North.
3. Move the unit to its own field: "900-602", "Unit 900", "Apt 900" and "#900" all become unit = 900, civic number = 602.
4. Keep suffixes on the civic number: "123A" and "123" are different, and so is "123 1/2".
5. Normalize the postal code: upper case, letter-digit-letter, space, digit-letter-digit (for example K1A 0B1). Compare it as a separate field from the province.

The hyphen format is the main trap for Canadian files. "900-602 Cobden Rd" is read by a naive parser as a range or a single number, and the unit is lost. Parse the hyphen into two fields before comparing.

Units, suites and rural routes

A unit number is part of the address. Three patterns recur in real files:

• Position differs. "Apt 900, 602 Cobden Rd" versus "602 Cobden Rd Apt 900" versus "900-602 Cobden Rd" is a format difference. Treat all three as a match.
• Label differs. "Apt", "Unit", "Suite" and "#" can all point to the same sub-address when the rest agrees. Match on the identifier and record the equivalence.
• Unit missing on one side. "602 Cobden Rd" versus "900-602 Cobden Rd" is a partial match: the building is confirmed, the dwelling is not. Ask for a document that shows the unit.

Rural route addresses and P.O. boxes need a separate rule, because they do not follow the civic number and street pattern and a mailing address may not be where the person lives.

What FINTRAC expects, and what it leaves open

Reporting entities under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA) must verify the identity of the people they deal with using methods set out in FINTRAC's guidance, such as a government-issued photo identification document, a credit file or a combination of reliable sources. Which fields you must record, and whether an address is part of the record, depends on your sector and the transaction, so confirm the requirement for your sector in the current guidance rather than assuming one rule for all.

None of these texts prescribes how an address string is formatted. Your matching rules are an internal policy, which you should write down and apply consistently. Personal data used in matching falls under PIPEDA for most private-sector organizations, with provincial laws applying in some provinces; collect only the address elements the check needs.

What a mismatch looks like, and what the reviewer does next

Each outcome needs a defined next step, or reviewers improvise and the same file gets different answers on different days.

A licence or government letter carries the address as of its last update, so a mismatch against a newer bill is common after a move and is not by itself a red flag. The reviewer records which source is more recent and why.

What users actually ask

Applicants on consumer finance forums raise two questions again and again.

"My proof of address was rejected but it is my address." The usual cause is formatting or completeness: the unit missing in the form, a hyphenated "900-602" the tool could not parse, or a statement type the provider does not accept. Ask the applicant to enter the address exactly as it appears on the document, and check that your own rule treats the hyphen format and the "Apt" format as equal.

"Does the unit go before or after the street address?" Either, as long as it appears. Canada Post accepts several placements, so forms should accept any and split it afterwards.

The same logic applies to names across documents, and the documents that can serve as evidence are covered in proof of address verification methods. The wider process is described in the document verification pillar guide.

Where automation helps and where it stops

Standardization, component-level comparison and postal-format checks are mechanical and consistent, which suits automation. Judgment calls do not: whether a six-month-old licence address is acceptable, whether a billing address stands in for a home address, whether a unit missing from the reference is a problem.

CheckFile compares fields across the documents in a file, including address components, and flags the differences for a reviewer. It describes what differs; it does not decide that a document is genuine. For leasing and property files, see the real estate solution; for regulated onboarding, the banking and KYC solution. Data handling is covered on the security page.

Frequently Asked Questions

Is "900-602 Cobden Rd" the same as "602 Cobden Rd Apt 900"?

Yes. Canada Post accepts both placements, and its own example uses them. The check should split each into unit 900 and civic number 602 and compare the parts.

Does matching an address to a postal format prove the applicant lives there?

No. It shows the address is well formed. Residence needs its own evidence, such as a recent bill or statement addressed to the applicant.

How should a missing unit number be treated?

As a partial match, not a pass. The building is confirmed and the dwelling is not, so ask for a document that shows the unit before accepting the file.

Should a one-character postal code difference fail automatically?

It should go to review. A single character can point to a different street, but it can also be a typo on one document that a second source resolves.