Address Matching Verification: Formats, Abbreviations, Flats

Address matching verification means comparing the address written on one document with the address on another document, the application form or an official address register, and deciding whether they describe the same delivery point. "Flat 2, 14 High St" on a bank statement and "14 High Street, Apt 2" on a utility bill are the same place, so an exact string comparison would wrongly reject them. A reliable check normalises both addresses, compares them component by component (flat, number, street, town, postcode) 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, never page against page. In a typical applicant file, the same residential address appears in four or five places, and each has its own habits of formatting.

The first question is which document is the anchor. In most onboarding files it is the address the applicant declared, and every document is compared to it. Comparing two documents with each other and ignoring the declaration lets two wrong addresses agree with one another.

Step 1: normalise before comparing

Normalisation turns every address into the same shape so that differences you see afterwards are real. Five rules cover most of the noise:

1. Fold case and strip punctuation: "FLAT 2, 14 HIGH ST." becomes "flat 2 14 high st".
2. Expand or contract abbreviations consistently: St/Street, Rd/Road, Ave/Avenue, Apt/Apartment, Flat/Fl.
3. Move the sub-building to a dedicated field: "Flat 2", "2/14", "14/2" and "Apartment 2" all become sub-building = 2, building number = 14.
4. Normalise the postcode: remove the space, upper-case it, then re-insert the space before the last three characters.
5. Keep house numbers with suffixes intact: "14A" and "14" are different delivery points, and so are "14" and "14 1/2".

Rule 3 is where most false mismatches come from. Fix it and a large share of "address does not match" cases disappear before any human sees them.

Flat numbers: the field that causes the most disputes

A flat number is part of the address, and dropping it changes the delivery point. Three patterns recur in real files:

• Position differs. "Flat 3, 22 Station Road" versus "22 Station Road, Flat 3" is a format difference. Treat it as a match.
• Label differs. "Flat 3", "Apt 3", "Unit 3" and "3" alone all point to the same sub-building when the rest of the address is identical. Treat as a match, record the equivalence.
• Number missing on one side. "22 Station Road" versus "Flat 3, 22 Station Road" is not a match. It is a partial match: the building is confirmed, the dwelling is not. Ask for a document that shows the flat.

Building names create a fourth case. "Flat 3, Rosewood House, Station Road" has no house number at all, so an algorithm that requires a number will fail it. Compare the building name instead.

Postcode and the Royal Mail PAF

Royal Mail describes the Postcode Address File (PAF) as its addressing database, with about 32 million UK delivery addresses and 1.8 million postcodes, constantly updated as homes are converted into flats. A PAF lookup confirms that a postal delivery address exists and how Royal Mail writes it (Royal Mail PAF); it does not confirm that the applicant lives there.

Used correctly, PAF does three jobs in a file check:

• It supplies the canonical spelling to compare both documents against.
• It catches an impossible combination, such as a postcode that does not serve that street.
• It shows whether a flat is listed. If a lookup returns only the building, the check proves the building exists and the flat number has to come from the document.

A postcode mismatch is more serious than a spelling difference. "SW1A 1AA" against "SW1A 2AA" is a different address even if the street name is identical, so route it to review rather than auto-correcting.

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

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

For the UK regulated sector, address verification sits inside customer due diligence under Regulation 28 of the Money Laundering Regulations 2017, which requires verification on the basis of documents or information from a reliable and independent source. The JMLSG guidance and the FCA Financial Crime Guide set out how firms apply that in practice. None of them prescribes an address string format, so your matching rules are an internal policy that you should write down and apply consistently.

What users actually ask

Applicants and small-firm staff on consumer finance forums tend to raise the same two questions.

"My proof of address was rejected but it is literally my address." The usual cause is a formatting or completeness gap, not a wrong address: the flat number missing on the form, an abbreviation the tool could not read, or a bank statement shown where the provider wanted a bill. Ask the applicant to enter the address exactly as it appears on the document, and ask your own team to confirm that the rule treats "Apt" and "Flat" as equal.

"Do I write the flat number in line 1 or line 2?" Either, provided it appears. Forms that force a single line should accept "Flat 2, 14 High Street" and split it later. Forms that reject the flat entirely create the mismatch you then have to chase.

Related checks belong in the same file review. The same normalise-then-compare logic applies to names across documents, and the document types that can serve as evidence are covered in proof of address verification methods. The wider file process is described in the document verification pillar guide.

Where automation helps and where it stops

Normalisation, component-level comparison and PAF-style lookups are mechanical and consistent, which is why they suit automation. Judgement calls do not: whether a six-month-old licence address is acceptable, whether a billing address stands in for a home address, whether a flat that is absent from the register 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 lettings and agency 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 "Flat 2, 14 High Street" the same as "14 High Street, Apartment 2"?

Yes, when the other components agree. Order and label are format variations. The check should split both into sub-building 2, number 14, street High Street and compare the parts.

Does a PAF match prove the applicant lives at the address?

No. It shows the address is a valid Royal Mail delivery point and gives its standard spelling. Residence needs its own evidence, such as a recent bill or statement addressed to the applicant.

How should the check treat a missing flat number?

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

Should a one-letter postcode difference fail automatically?

It should go to review rather than fail or auto-correct. A single character can move the address to a different street, but it can also be a typo on one document that a second source resolves.