Australian address data
Name who fixes an address when the reference data disagrees
A workable handover separates customer corrections, provider coverage issues and integration defects. Each needs a different owner and evidence trail.
In this article
Give support a way to explain the current record
Show the address role, confirmation state, source and revision in an appropriate administrative view. Support should be able to tell whether a customer typed the address manually or selected a provider candidate.
Keep the original and normalised forms available where the records policy permits. This helps identify whether a unit disappeared during entry, matching or label generation.
Provide a safe correction workflow that previews affected future work. Staff should not need direct database access to fix an ordinary destination error.
Divide ownership by the cause
Customer service can confirm intended address details. Dispatch owns the practical service destination and access requirements. Engineering owns field loss, stale-response races and integration formatting defects.
Assign an owner for provider coverage reports and dataset updates. An unmatched new site should not remain an untracked support workaround for months.
Use a synthetic rehearsal where a valid manual address becomes available in the provider later. The team should update its evidence without unnecessarily changing the customer's confirmed destination or historical jobs.
Document the dependency lifecycle
Record the lookup service, credentials owner, quota monitoring and supported fallback. If using a locally maintained dataset, include update ingestion, validation and rollback procedures.
Keep licensing and permitted-use decisions with the responsible business owner. Engineers need to know which caching and redistribution patterns are approved for the selected data, rather than rediscovering that during an outage.
Include provider schema changes in the integration watch list. A renamed component or changed address type can break a label even when the search endpoint remains available.
Review failures using actual destinations
Periodically examine sanitised examples of returned mail, corrected jobs and repeated manual-entry cases. Separate input friction from downstream corruption before choosing improvements.
Make sure the resulting fixes reach regression fixtures and support guidance. A one-off customer correction closes the immediate case, while a fixture preserves the lesson for the next release.
The handover is usable when a new operator can identify the relevant address role, apply a scoped correction and verify its output without changing unrelated customer work.
Primary sources
Australia Post: addressing guidelinesAustralian Government: G-NAF datasetReferences checked 11 September 2026.