AUO joins many government registers into one entity, but it never hides where a value came from. This is the compliance value proposition, not an add-on.

​
Every value carries source and as_of

Each field in the canonical block is an object, not a bare value: 
"entity_name": {
  "value": "AUSTRALIAN TAXATION OFFICE",
  "source": "ABR",
  "as_of": "2026-07-02T13:22:15+10:00"
}
  • value is the field’s value (may be null).
  • source names the register the value came from (for example ABR, ASIC_companies, ACNC).
  • as_of is when AUO read that value from the source, where the source dates it.
  • Some fields also carry a note explaining a null or a caveat (see the acn field on a non-company entity).
You can hand this straight to a compliance reviewer: for any assertion AUO makes, you can show which government register said it and when.

​
Conflicts are flagged, not resolved

Registers refresh on different cadences. The ASIC company register updates on a different day from the Australian Business Register, so two sources can briefly disagree about, say, a company’s status. AUO does not silently pick a winner. When sources disagree, the conflict is surfaced in a top-level conflicts array on the candidate: 
"conflicts": [
  {
    "field": "status",
    "values": [
      { "value": "Active", "source": "ABR" },
      { "value": "Deregistered", "source": "ASIC_companies" }
    ]
  }
]
A populated conflicts array is a signal, not an error. It usually means one source has refreshed and another has not yet. Use the per-value as_of timestamps to decide which is more current for your purpose.

​
provenance_complete

Each candidate carries a provenance_complete boolean. It is true when every field in the response could be attributed to a source. Use it as a quick check that the record is fully sourced.

​
Next

Honest boundaries

The flip side of provenance: being clear about what AUO cannot tell you.