DVTX ABN & ACN Validation
Catch a bad ABN before it costs you
A mistyped or invented ABN means invalid tax invoices, GST you cannot claim, and suppliers who do not exist. DVTX answers the three questions that matter in one call: is this identifier real, is it active, and does it actually belong to the business that gave it to you?
Live on RapidAPI. Subscribe on the marketplace — authentication and billing are handled there, so a key is all you need.
{
"abn": "51824753556",
"checksum_valid": true,
"abn_active": true,
"entity_name": "EXAMPLE HOLDINGS PTY LTD",
"entity_type": "Australian Private Company",
"gst_registered": true,
"gst_registered_from": "2000-07-01",
"business_names": ["Example Trading"],
"location": { "state": "NSW", "postcode": "2000" },
"name_match_score": 0.94,
"name_match_matched": "Example Trading",
"abr_status": "ok",
"abr_retrieved_at": "2026-07-30T04:04:21Z"
}What comes back, and what it means
- checksum_valid
- The ATO's mod-89 algorithm, computed locally. A fabricated number fails here instantly, with no lookup and no dependency on anyone's uptime.
- abn_active
- Whether the register currently shows the ABN as active — the difference between a real business and one that was wound up in 2019.
- gst_registered
- Whether the supplier is registered for GST, and from when. If they aren't, their invoice cannot charge you GST.
- name_match_score
- Send the name you were given and get back 0 to 1 for how well it matches the registered entity and business names, with the matched name returned so a human can judge a near miss.
- abr_status
- ok, not_found, or unavailable. If the register is unreachable the checksum verdict still stands and this says so — your request never fails because a government service is down.
Two layers, one call
The checksum layer is local, deterministic, and always on — it catches typos and invented numbers on its own. The register layer adds what only the Australian Business Register knows: status, entity name and type, GST registration, registered business names, and state. Register data is passed through exactly as received, with the time it was retrieved.
Explainable, not a verdict
Every answer is a named field rather than an opaque pass or fail: checksum_valid, abn_active, gst_registered, name_match_score. When a number fails, reason says why in plain words. You decide what your business rules make of it.
Business identifiers only
DVTX validates ABNs and ACNs. It does not accept, validate, or store tax file numbers or any personal tax data, by design — a nine-digit input is treated strictly as an ACN. Nothing you send is kept.
What DVTX guarantees
Every line below is checkable rather than asserted — that is the whole point of the brand.
- Deployed to its own production origin
- Register integration verified end to end against the live service
- 28 automated tests, register calls fully mocked so they never hit production
- Graceful degradation proven: checksums answer when the register does not
Start using DVTX
Plans, quotas, and rate limits are on the listing itself, so what you read there is always what you are billed — we never restate prices here where they would go stale. There is a free tier to try it on your own documents first. Processing supplier invoices as well? DVAP extracts, validates, fraud-checks, and PO-matches them on the same engine, with the accuracy published.