ABN Verification for Business Onboarding: A Compliance Guide

Why ABN verification matters at onboarding

When you onboard a business client, borrower, or vendor in Australia, verifying their Australian Business Number is the first line of defence against fraud, deregistered entities, and compliance risk.

An active ABN confirms that the business is registered with the Australian Tax Office and legally authorised to operate. A cancelled or deregistered ABN is a significant red flag — the entity may have been wound up, struck off, or may not have existed at all.

What a proper ABN check covers

A basic ABN check confirms the number is valid and active. A thorough KYB-grade ABN verification covers:

• Registration status: Is the ABN currently Active or Cancelled?
• Legal name match: Does the legal name on the ABR match what the business has provided to you?
• Entity type: Is it a company, trust, sole trader, or partnership? Trusts and partnerships carry higher compliance complexity.
• GST registration: Is the entity registered for GST? An unregistered company or trust is a risk indicator.
• State of registration: Where is the entity registered? Does it match the address provided?
• Registration date: How long has the entity been registered? Newly registered entities warrant additional scrutiny.

Manual ABN verification — the limitations

The ABR public lookup allows anyone to check an ABN manually. For low-volume onboarding this is workable but has significant gaps:

• No audit trail — there is no verifiable record that the check was performed at a specific time
• No risk scoring — the ABR lookup returns raw data but does not assess structural risk
• Human error — manual processes introduce transcription mistakes
• Not scalable — impossible to support high-volume onboarding

Building an auditable ABN verification process

For compliance purposes, your ABN verification process needs to be documented, timestamped, and reproducible. A regulator or auditor should be able to see exactly what was checked, when it was checked, and what the result was.

The components of an auditable ABN verification:

1. Live registry query — the check must hit the ABR at the time of onboarding, not rely on cached data
2. Timestamped result — the registry response must be recorded with an exact timestamp
3. Cryptographic seal — the verification record should be tamper-evident so it cannot be altered after the fact
4. Officer decision record — who approved or rejected the entity and when
5. Risk assessment — what risk signals were present at the time of verification

ABN verification for different onboarding flows

How you integrate ABN verification depends on your onboarding flow:

• Self-service onboarding: The applicant enters their ABN in your form. Your system calls the verification API and returns a pass/fail or risk score in real time.
• Assisted onboarding: Your compliance officer receives the ABN from the applicant and runs the check manually via the Enterprise portal.
• Link-based onboarding: You send the applicant a secure link. They enter their own ABN. The result lands in your portal automatically.

See Applicant Onboarding Portal for details on the link-based approach, or read the Verify Entity API reference for direct integration.

What happens when an ABN is cancelled?

If a business presents a cancelled ABN during onboarding, your verification system should flag this immediately as high risk. Common reasons an ABN may be cancelled:

• The business has been voluntarily deregistered
• The ATO has cancelled the ABN due to non-compliance
• The entity has been wound up or liquidated
• The ABN was fraudulently obtained and subsequently cancelled

In Osapher's Fracture Score™ system, an inactive registration adds 60 points to the risk score — the highest single signal. Any entity with a cancelled ABN will score at least 60/100, placing it in the High Risk band.

Learn more about how risk scoring works in the Fracture Score™ documentation or on the Risk Engine page.