An ABN contains 11 digits. You see it on almost every Australian procurement record. The number comes from the Australian Business Register (ABR), operated inside the Australian Taxation Office rather than the corporate regulator most people expect.
That placement changes how the data behaves. The ABR is not ASIC’s company register. It sits inside tax administration and covers companies, partnerships, charities, government bodies, plus sole traders. When tracing entities tied to procurement, political donations, or subcontracting chains, the ABN lookup tends to appear early in the trail. Sometimes first.
AU is not active in OpenRegistry’s MCP server right now. The live coverage matrix lists other registers instead: GB Companies House, FR INPI, DE Handelsregister, RU FNS, KY General Registry, along with several US state registers. ABR support is planned but currently offline. Queries cannot run through the server yet. The underlying register remains public through the official ABR search service.
What the ABR dataset actually returns
The public ABR search exposes a defined group of fields tied to each ABN record. A typical lookup returns identifiers, status flags, and classification codes used by the tax system.
Three fields appear in many investigations:
• abn — the 11‑digit identifier issued under the A New Tax System (Australian Business Number) Act 1999
• entity_name — the legal or trading name recorded with the ABR
• entity_status — usually Active or Cancelled, paired with a status date
Dates carry more weight than people assume. The ABR exposes both abn_status_effective_date and entity_status_effective_date. Those values can diverge when an entity restructures or shifts category inside the register.
Industry tagging is present too. Each record may include an anzsic_code, taken from the Australian and New Zealand Standard Industrial Classification system. Reporters rely on this field when grouping subcontractors in construction investigations. The same code helps isolate clusters of mining service firms in Western Australia. Patterns show up quickly.
Address data is thin. Still useful. The business_address field usually contains suburb, state, and postcode. Street details often stay hidden. Even that partial location helps when matching entities against procurement databases or electoral donor disclosures.
Another quirk sits in the classification fields. The record often carries entity_type_ind alongside entity_type_text. Those markers separate companies from trusts, partnerships, or sole traders. If a supposed contractor turns out to be a sole trader operating under a personal ABN, the register exposes it immediately.
What the ABR does not give you
Ownership information is the obvious gap. The ABR does not list shareholders or directors. Those live in ASIC company records, and access to many of those documents still sits behind fees. Anyone who needs director names usually buys an ASIC extract or hunts through filings collected elsewhere.
Beneficial ownership is absent as well. Australia has discussed a central beneficial ownership register for years. None exists in public form. Most investigations end up combining ABR entries with ASIC filings, court records, and procurement disclosures. The ABR alone is rarely enough.
Historical coverage stays fairly shallow. The register focuses on current status and a few key dates rather than a full change history. If an entity has changed names several times, the public search may show only part of that sequence. Older states can vanish.
Automated collection runs into friction. The public ABR web service applies request limits. During heavier automated access it sometimes introduces CAPTCHA checks. Anyone who has tried to gather contractor names during a large procurement investigation has likely met that wall. Scripts stall. Researchers go back to manual queries.
Query shape when ABR support returns
Once the AU jurisdiction becomes active in OpenRegistry, the normal starting point will be a name search against the ABN dataset.
Example MCP call:
search_companies({
"jurisdiction": "AU",
"query": "Southern Cross Infrastructure"
})
That request should return candidate ABN records containing both the entity name and the identifier. From there the next step is straightforward. Retrieve the full profile tied to a specific ABN.
get_company_profile({
"jurisdiction": "AU",
"company_number": "XXXXXXXXXXX"
})
The response would surface the upstream ABR fields inside jurisdiction_data. Keeping the original field names matters during reporting. A fact‑checker can trace each value back to the exact label used by the source register. No reshaped schema in the middle.
Some registers expose structured notices or filing updates. If the ABR publishes such material, they would appear through list_filings. Not every jurisdiction offers a feed like that. Behaviour depends entirely on what the ABR endpoint makes available.
Why investigators keep returning to the ABR
The ABN functions as a shared identifier across several Australian datasets. Procurement portals reference it. Charity registers link back to it. Electoral disclosures sometimes include the number as well. Once you have the ABN, matching records across those systems becomes far easier.
Cross‑border work often follows the same pattern. An entity named in an Australian infrastructure tender may turn out to be owned by an offshore holding company. The Cayman register might list directors. The ABR entry confirms the operating entity inside Australia. That anchor point matters.
Investigations published by groups such as OCCRP or ICIJ often follow this route. Start with the operating company. Locate the ABN. Then expand outward through corporate registers, court filings, and procurement disclosures.
If ABR support returns to the OpenRegistry MCP server, the change will be practical. The tax register becomes queryable alongside other statutory registers through the same interface. The usual cycle of manual lookups and spreadsheet stitching shrinks. Current coverage appears in the registry matrix at https://openregistry.sophymarine.com/mcp.
Top comments (0)