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 address file, and deciding whether they describe the same property. "Unit 4, 12 Smith St" on a bank statement and "4/12 Smith Street" on a utility bill are the same place, so an exact string comparison would wrongly reject them. A reliable check standardises both addresses, compares them component by component (unit, street number, street, suburb, state, 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. In a typical applicant file the same residential address appears 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: standardise before comparing

Standardisation puts each address in the same shape so remaining differences are real. Five rules cover most of the noise:

1. Fold case and strip punctuation: "UNIT 4, 12 SMITH ST." becomes "unit 4 12 smith st".
2. Map street types to one form: St/Street, Rd/Road, Ave/Avenue, Cres/Crescent, Pde/Parade.
3. Move the unit to its own field: "4/12", "Unit 4, 12", "U4 12" and "Flat 4/12" all become unit = 4, street number = 12.
4. Keep alphabetic suffixes and ranges intact: "12A" and "12" are different, and "10-14 Smith St" is a range that identifies a building rather than a single number.
5. Validate the state against the postcode: a four-digit postcode that does not belong to the stated state or suburb is an error to review, not to auto-correct.

The slash format is the main trap in Australian files. "4/12 Smith St" is read by a naive parser as a fraction or a date, and the unit is lost. Parse the slash into two fields before comparing.

Units, flats and lots

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

• Position differs. "Unit 4, 12 Smith St" versus "4/12 Smith St" versus "12 Smith St, Unit 4" is a format difference. Treat all three as a match.
• Label differs. "Unit", "Flat", "Apartment" and "U" 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. "12 Smith St" versus "4/12 Smith St" is a partial match: the building is confirmed, the dwelling is not. Ask for a document that shows the unit.

Rural addresses with lot numbers, "Lot 7 Creek Rd", and PO Box addresses need a separate rule, because a postal address may not be where the person lives.

The Geocoded National Address File: what it can confirm

The Geocoded National Address File (G-NAF) is published by Geoscape Australia through data.gov.au and updated quarterly. As of its February 2026 release notes, it held 15,860,127 addresses, each with state, suburb, street, number and a geocode. It does not contain personal information or details relating to individuals. A G-NAF match confirms that a street address exists and how it is recorded (data.gov.au); it does not show who lives there, so it supports an address check but is not proof of residence.

Used correctly, an address reference file does three jobs in a file check:

• It supplies the canonical spelling to compare both documents against.
• It catches impossible combinations, such as a suburb that is not in the stated state.
• It shows whether a unit is recorded. If a lookup returns only the street number, the check proves the building, and the unit has to come from the document.

Check the licence terms on the dataset page before building it into a product.

What AUSTRAC expects, and what it leaves open

Reporting entities under the AML/CTF Act 2006 must carry out customer identification procedures, and AUSTRAC publishes the rules and guidance for them. The obligations have been under reform, so read the current AUSTRAC guidance for your sector, including which customer details must be collected and verified, rather than relying on an older summary.

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 information used in matching is subject to the Privacy Act 1988 and the Australian Privacy Principles, which the OAIC explains; collect only what 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 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 "4/12" the tool could not parse, or a document 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 "4/12" and "Unit 4, 12" as equal.

"Do I write the unit before or after the street number?" Either works for a person, so forms should accept both 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

Standardisation, component-level comparison and reference-file lookups 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 rental 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 "4/12 Smith St" the same as "Unit 4, 12 Smith Street"?

Yes, when the rest of the address agrees. The check should split the slash into unit 4 and street number 12 and compare the parts.

Does a G-NAF match prove the applicant lives at the address?

No. It shows the address exists and how it is recorded. 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 postcode difference fail automatically?

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