Australian address data
Review the address after it leaves the form
The highest-risk defects often appear in labels, exports and job creation. Trace a difficult address through the complete workflow before approving the component.
In this article
Establish the meaning of each field
Ask whether the model distinguishes postal destination, service location and access instructions. Check the behaviour when those belong to different places for the same customer.
Inspect unit, street-number and postcode types. Numeric coercion should not remove a leading zero or reject a letter that the supported address model permits. Confirm the manual-entry path for unmatched records.
Review the meaning of Verified. It should name the evidence obtained, such as a provider match, rather than imply deliverability, occupancy or service eligibility that was never checked.
Follow a deliberately awkward example
Use a synthetic address with a unit, organisation name and long building detail. Create the actual shipping request, service appointment and export supported by the application.
Compare the destination at each boundary. Look for dropped second lines, silent truncation and accidental movement of instructions into public labels.
Change a component after selecting an autocomplete result. The old match association must not survive changes that invalidate it. Also reverse the order of search responses and ensure a stale result cannot overwrite newer input.
Inspect update and history behaviour
Create a completed job and a future job, then correct the customer's postal address. Ask which records should change and demonstrate that only those do.
Check concurrent edits and migration paths. A background normalisation process should not overwrite a user's newer correction, and a schema migration should retain unresolved original data for review.
Confirm that address identifiers are scoped and authorised. Knowing another customer's address ID must not allow a user to retrieve private site information.
Make approval depend on observable results
Request evidence for the supported edge cases and the provider outage path. A demo containing one successful house-address lookup is insufficient for a business application serving varied premises.
Document deliberate restrictions at the point where they apply. If a chosen delivery service cannot accept a particular destination type, the interface should explain that service constraint clearly.
Leave the review with named fixes and reproducible cases. “Address validation needs work” is vague. A failing export that converts 0800 to 800 gives the team a specific defect to close.
Primary sources
Australia Post Developers: address guidanceReferences checked 11 September 2026.