Due Diligence 15 November 2026 · Gumshoe

What a Supplier Ledger Audit Finds in a Typical Supplier List

Your supplier list is the control that failed before the payment even left the bank.

Your supplier list is the control that failed before the payment even left the bank.

An invoice lands in the queue. The ABN checks out on the portal. The GST status shows registered. The bank details match what's on file. Everything ticks — except the entity behind that ABN was deregistered six months ago, the trading name belongs to a different legal structure entirely, and the director has three other companies in liquidation. The payment processes anyway because the master record never caught up.

Most finance teams treat the supplier master file as a static reference — set once at onboarding, updated only when a creditor demands it. In reality it drifts daily: entities deregister, directors cycle through failed structures, trading names shift between related parties, and GST registrations lapse or get cancelled. The payment run doesn't know any of this. It reads the record as written and pushes the funds.

The control failure isn't the payment approval. It's the assumption that the data behind that approval is still true. Every dollar paid to a deregistered ABN, a mismatched entity name, or a supplier whose GST status you never verified is a dollar the business cannot defend — not to the ATO, not to an auditor, and not to a liquidator chasing preferential payments.

The Ghost Supplier: Paying Entities with Inactive or Cancelled ABNs

An ABN cancellation is a public signal that an entity has ceased trading, been wound up, or failed to meet its tax obligations. Yet the master file in most ERPs treats that signal as optional background noise. The supplier record stays "active" because nobody owns the job of checking the ABR after onboarding. Invoices keep arriving. Purchase orders keep generating. Payments keep clearing.

The mechanics are straightforward: a director winds up Company A, walks away from its debts, and starts Company B with a fresh ABN. Company A's cancelled ABN remains in your supplier master. Your AP team pays invoices addressed to Company A — often for goods never delivered, or services rendered by Company B under the old name. The money leaves your bank account and lands in a structure that no longer exists as a legal entity, or one controlled by the same director who just shed the liabilities.

Directors and CFOs must maintain accurate books and records. Paying a cancelled ABN isn't just a data hygiene issue; it creates a transaction trail that cannot be substantiated. When a liquidator examines preferential payments, or the ATO queries a GST credit, the defence collapses at the first question: "Why did you pay an entity that the public register showed had ceased to exist?"

The recovery path is deliberately narrow. Once funds settle in an account linked to a cancelled ABN, the recipient entity has no legal capacity to hold obligations or return value. The CFO is left explaining to the board why a six-figure payment cleared to a ghost.

Automated ABR monitoring closes the window. A batch check against the Australian Business Register flags cancelled, inactive or replaced ABNs before the next payment run — not at year-end when the auditor asks for the supplier master extract. The control is binary: if the ABN status is not "Active", the supplier record is suspended and no purchase order or invoice posts until a current ABN is verified and re-attached. That single gate stops the bleed that manual review never catches consistently.

Name Mismatch: When the Legal Entity Doesn't Match the Payee

The invoice says "Apex Civil Pty Ltd". The ABN lookup returns "Apex Group Holdings Pty Ltd". The BSB and account number match the purchase order. The AP clerk ticks the three-way match and the payment clears. Nobody asks why the legal entity on the tax invoice differs from the entity registered to the ABN — until the ATO issues a position paper denying the GST credit because the supplier name on the invoice does not match the ABN registration, or a liquidator challenges the payment as a preferential transfer to a related entity that wasn't the contracted counterparty.

This mismatch is the fingerprint of a shell structure. A single operating entity trades under multiple trading names, each with its own ABN, while invoices are issued from a central billing entity that holds none of the contracts, carries none of the insurance, and employs none of the workers on site. The payer thinks they engaged a licensed builder; the ABN trail leads to a shelf company with no assets. When a workplace incident occurs or a subcontractor chain collapses, the contractual chain evaporates — the entity you paid was never the entity that did the work.

The mischaracterisation risk is sharper than most CFOs realise. You pay for "civil construction" but the ABN entity is registered for "management consulting". The GST credit you claim rests on a tax invoice that describes services the registered entity never performed. Under the GST Act, the Commissioner can deny the input tax credit where the invoice does not properly identify the supplier — and a name mismatch is the textbook trigger.

Automated ABN validation at onboarding catches the obvious gaps. It does not catch the drift: the supplier who quietly shifts invoicing to a related entity six months in, or the subcontractor who on-charges through a labour-hire company with a different ABN. The control is not the initial check — it is the periodic re-verification that the legal entity on every invoice still matches the ABN on file, and that the ABN's registered activity aligns with what you are actually buying. Without that rhythm, the three-way match becomes a three-way fiction.

GST Compliance Gaps: Unverified Tax Status on Supplier Records

You claim the GST credit the moment the invoice hits the ledger. The ATO checks the supplier's registration status the moment you lodge the BAS. If those two moments disagree — the supplier was deregistered, never registered, or registered under a different ABN — the credit is denied and the penalty clock starts. No fraud finding required. A documentation gap is enough.

The risk compounds in bulk. A single unverified supplier might cost a few thousand in denied credits. Across a supplier list of 500 entities, where 15% have stale or incorrect GST status, the exposure scales to six figures before the first audit query lands. The Commissioner's view is straightforward: you are responsible for verifying the tax invoice is valid at the time you claim the credit. Relying on the supplier's word, or on a registration check performed at onboarding three years ago, is not a defence.

Most AP teams run the ABN Lookup once — at onboarding — and treat the result as permanent. It isn't. Suppliers deregister, change entity structure, or let their registration lapse while the invoices keep coming. The ATO assesses the validity of a tax invoice at the time you claim the credit, not at the time you set up the vendor. If a supplier deregisters for GST but keeps issuing "tax invoices", each payment you process can create a denied credit. The penalty regime under the Taxation Administration Act treats each incorrect credit as a separate shortfall amount.

The operational fix is a scheduled re-verification cycle, not a one-off clean-up. Regular ABN status checks against the live register catch deregistrations before they hit the BAS. Reconciliation of claimed GST credits against supplier registration status at invoice date turns a retrospective exposure into a prospective control. The table below contrasts the two approaches.

GST Verification: Correct Practice vs High Risk
Control PointCorrect PracticeHigh Risk
Initial verificationABN Lookup + GST registration confirmed before first paymentSupplier provides ABN; no independent check
Ongoing monitoringAutomated monthly re-check against ABR; flag changes to APNo re-check after onboarding
Invoice-level validationSystem verifies supplier GST status matches invoice dateAssumes all invoices from registered suppliers are valid tax invoices
BAS preparationReconcile claimed credits to supplier status at invoice dateClaim credits based on invoice face value only
Exception handlingPayments to deregistered suppliers held until status resolvedPayments processed; credit claimed; issue found at audit

The gap between "we checked once" and "we check continuously" is where the ATO collects. A supplier list that was clean in 2021 is a liability in 2024 unless the verification process runs on a calendar, not on memory.

The Missing ABN: Payments to Unregistered or Unknown Suppliers

An invoice lands without an ABN. The AP clerk processes it anyway — small amount, regular supplier, "we'll chase it up later." That single decision breaks the chain of evidence the ATO expects and the Corporations Act implies. No ABN means no verification of identity, no confirmation of GST status, and no defensible position when the compliance query arrives.

The risk isn't theoretical. A supplier without an ABN on file cannot issue a valid tax invoice. Any GST credit claimed on that payment is exposed to reversal, plus penalties and interest. The onboarding gate didn't just fail — it was left open. For transactions above the $75 threshold (excluding GST), the payer is required to withhold 47% under the PAYG withholding rules when no ABN is quoted. Most AP teams don't know this rule exists until the ATO raises it.

The $75 threshold isn't a suggestion — it's the line where the payer becomes the withholder. Process a $200 invoice from a supplier with no ABN and no withholding, and the liability sits with the business that paid it, not the one that disappeared. The ATO doesn't accept "we meant to follow up" as a defence. The withholding obligation triggers at the moment of payment, not at the moment someone remembers to ask for the form.

This is where onboarding discipline pays for itself. A supplier master record that requires an ABN before the first invoice can be entered — enforced by the ERP, not by policy — removes the decision from the AP clerk entirely. The gate either holds or it doesn't. Gumshoe's supplier audit surfaces every record missing an ABN, every ABN that fails validation, and every payment made to them in the last twelve months, so the fix happens before the ATO asks for the ledger.

Uncommon Insights

Most finance teams treat the supplier master file as a static directory — a list of names, ABNs and bank details that gets updated when someone remembers. The real control gap isn't the data sitting in the file; it's the absence of a recurring, automated reconciliation between that file and the actual payment ledger. A supplier's ABN can be valid today, cancelled tomorrow, and the ERP will still happily process next week's invoice because nobody built a check that runs after onboarding.

Manual invoice review catches typos. It does not catch a supplier that stopped trading six months ago but keeps submitting invoices from a dormant shell. It does not catch a GST registration that lapsed mid-contract, turning every input credit claimed since into a compliance exposure. The only way to find those is to run the ledger against live ABR and ATO data — every payment, every period, not just the new vendors. Gumshoe does this by design: matching each payment against current ABN status, GST registration and entity name at the point of each transaction.

The pattern repeats across industries: a construction firm pays a subcontractor, unaware the entity deregistered months earlier. A professional services practice claims input credits on a consultant whose GST registration lapsed mid-engagement. Neither shows up in a sample audit because the invoices look correct — sequential numbers, familiar logos, approved purchase orders. The breakdown is temporal, not visual. The control that fails is the one that assumes onboarding validity persists indefinitely.

Automated reconciliation shifts the question from "is this invoice correct?" to "was this entity valid on the date we paid it?" That distinction catches the deregistered ABN, the lapsed GST registration, the name change that never flowed through to the bank account. It also creates an evidence trail the ATO accepts: a point-in-time verification for every transaction, not a retrospective justification. The supplier list becomes a living control rather than a static directory, and the audit cost drops from weeks of manual sampling to a single automated run across the full ledger.

What a Supplier Ledger Audit

Key Takeaways

  • Onboarding is not a control that lasts. A supplier verified at setup can deregister, lose GST registration, or change legal structure without your AP team knowing.
  • Invoice accuracy does not equal entity validity. Sequential numbers, correct logos and approved POs only prove the document looks right — not that the payee is still who they claim to be.
  • Point-in-time verification is the only evidence the ATO accepts. Retrospective sampling cannot prove a supplier was compliant on the date you paid them; automated ledger reconciliation can.
  • Name mismatches and missing ABNs are onboarding failures, not payment errors. They signal the gate was never closed, and every subsequent payment compounds the compliance exposure.
  • The supplier list is a control surface, not a directory. Treat it like a ledger: every change, every lapse, every discrepancy gets recorded and flagged at the moment it matters.
VERIFY NOW

Run a free supplier check in seconds

Search by business name, ABN, or ACN. Instant PASS/WARN/FAIL across 8 verification signals.

Start verifying →
VERIFY A SUPPLIER
Run a free check in seconds

Search by business name, ABN, or ACN. Get a real-time PASS/WARN/FAIL report across 8 verification checks.

Start verifying →

Contains data sourced from the Australian Business Register and ASIC, © Commonwealth of Australia, licensed under CC BY 3.0 AU.