Invoice Fraud Checks in Client Records 2026

Check suspect supplier invoices against authority, delivery and payment evidence, with a clear escalation record before the client’s accounts are approved.

Published
Updated

Invoice fraud uses a deliberately false or manipulated invoice to obtain payment or misstate a transaction. Check a suspect charge against independently held purchase and delivery records before approving it.

What Invoice Fraud Looks Like in the Books

Supplier invoice fraud can involve a charge for work never performed, an inflated amount or a genuine bill deliberately presented twice. An unusual invoice is a reason to investigate. It does not establish intent.

Invoice Patterns to Investigate

PatternWhat the records might showPossible ordinary explanation
Duplicate invoiceThe same supply appears in two bills or paymentsA document was imported twice
Fictitious invoiceA charge has no matching purchase or delivery evidenceSupporting records were filed elsewhere
Altered invoiceQuantity, amount or payment details differ between versionsA supplier issued a genuine correction
Collusive invoiceA supplier and staff member arrange an unsupported or inflated chargeAn unusual charge has a documented commercial basis

A duplicate paid by mistake is an error. Evidence that someone knowingly resubmitted the paid invoice changes the investigation. Preserve the documents that support that distinction instead of labelling every duplicate as fraud.

Keep the review centred on the client’s transaction. Establish what the business ordered, what it received and what it paid. A genuine supplier name or a payment leaving the bank does not establish that the billed work occurred.

A Fictional Unsupported Charge

Suppose a fictional business, Example Supplier A, bills a client $2,200 including GST for warehouse repairs. The description gives no job reference. The client’s usual maintenance contact cannot find a corresponding work order.

Start with the purchase approval and agreed scope. Obtain the delivery or job-completion record from the person who received the work. Compare the bill with the supplier statement and trace any payment to the client’s bank record.

The missing work order could reflect poor filing. A job record and independent confirmation of completed repairs could support a genuine charge. A supplier’s acknowledgement that it billed the wrong customer could establish a billing error.

If the client denies ordering or receiving the repairs and the supplier cannot explain the charge, keep it unresolved and escalate. Record those facts separately from any suspicion about who created the invoice.

Check the Invoice Against Independent Evidence

Match the invoice to records created outside the invoice itself. Start with the individual charge, then examine related transactions if the mismatch suggests a wider pattern.

Before reviewing, obtain authorised access to the relevant client records. Keep an unchanged copy of the invoice and record the ledger entry it relates to. If payment is pending, alert the client’s authorised payment approver to the unresolved item.

Evidence Checks in Order

  1. Confirm the supplier. Compare its legal name and ABN with the approved supplier record and Australian Business Register details. A matching registration supports the identity of the registered business, not the occurrence of this purchase.
  2. Find the purchase authority. Match the invoice to an approved order, contract or documented instruction. Compare the agreed quantities and rates with the billed items. Ask the authorised purchaser about differences.
  3. Confirm delivery. Obtain a goods-received record, service report or other evidence from the receiving staff member. For services, check the agreed deliverable and who accepted the work. A purchase order alone does not show completion.
  4. Search prior invoices. Compare references, amounts and descriptions across supplier records, including duplicate supplier accounts. Distinguish a credit note or replacement invoice from a second claim for the same supply.
  5. Check payment details. Compare the bank account with independently approved supplier details and the change history. Resolve a new account through a trusted contact already held by the client before payment approval.
  6. Reconcile the books. Trace the invoice through the payable, any credit and the bank payment. Confirm whether a flag concerns two documents, two ledger postings or two actual payments.

The ATO’s GST record guidance requires records that support reported amounts and GST credits. Keep the tax-invoice requirements separate from proof that the business received the supply. A document headed tax invoice cannot establish both on its own.

What Anomaly Tests Can Establish

Anomaly tests identify transactions that differ from an expected pattern. Examples include repeated references, invoices just below an approval limit and an unusual increase in a supplier’s charges. Each flag needs an explanation grounded in transaction records.

A Benford test compares leading-digit frequencies with an expected distribution. It can help select monetary transactions for investigation when the dataset suits the method. It cannot establish that an invoice is false or identify who acted dishonestly.

AICPA’s explanation of Benford testing excludes assigned numbers and values restricted to a predetermined range. Invoice numbers are assigned identifiers. A small set of fixed-price monthly charges is also a poor basis for assuming a Benford pattern.

Before interpreting results, document the population, amount field and exclusions. Reconcile the extracted totals with the ledger. Check whether missing credits, currency conversion or duplicated imports explain an apparent pattern before expanding the investigation.

Assess Invoice Fraud Detection Software

Oversight’s duplicate-detection material describes fuzzy matching across vendor, invoice and voucher data. That method can flag similar records even when invoice references differ. A similarity flag still needs comparison with the original documents.

For any invoice fraud detection software, establish which records it receives and what its test actually compares. Determine whether it examines invoices, payments or both. Missing supplier accounts or absent credit notes can change the meaning of its results.

Retain the rule or model explanation supplied with a flagged transaction. Check its suggested duplicate against the underlying purchase and payment records. A score without traceable supporting records is insufficient for a reviewer decision.

Preserve and Escalate the Finding

Preserve the original records and document what you know before requesting a correction or making an allegation. Assign the unresolved item to a reviewer who has authority to decide the next action.

An Investigation Record

Keep the invoice version and its ledger reference with the following information.

Record fieldWhat to record
Observed anomalyThe precise mismatch, such as two payments against one supply
Evidence obtainedPurchase approval, delivery record and relevant payment references
Explanation requestedThe question, recipient and response received
Remaining uncertaintyWhich part of the charge still lacks support
Reviewer decisionFinding, reasons, authorised action and person responsible
Follow-upEvidence still needed, agreed review point and outcome

Use factual descriptions such as duplicate payment under review. Keep allegations separate and restrict access to staff handling the matter. If a purchaser or approver may be involved, escalate outside that person’s reporting line.

Request the missing evidence specifically. For the fictional repairs invoice, ask for the job reference and completion record. If the supplier says it billed the wrong client, request its written explanation and the appropriate credit or corrected document.

Make an authorised correction through the accounting software’s normal adjustment procedure. Link the reversal or correction to the original entry and retain the reason and approval. Preserve the original invoice and earlier ledger evidence instead of overwriting them.

Review the accounting and tax consequences separately. A ledger correction does not amend an already lodged statement. Check whether the affected expense or GST credit has entered a return or BAS before treating the matter as resolved.

Reporting and Professional Obligations

The TPB’s statement-correction guidance applies when its conditions for a materially false or misleading statement are met. An unexplained invoice in an unlodged ledger does not by itself establish those conditions.

For a statement prepared for a client, the required actions can include advising correction and explaining the consequences of inaction. Further duties depend on the client’s response, the conduct involved and, for notification, the specified substantial-harm condition.

Assess those conditions with the engagement partner. Record the advice and the client’s response. Escalate a refusal to correct before continuing work that relies on the disputed amount, and apply the guidance’s withdrawal and notification requirements where triggered.

The TPB’s confidentiality guidance also addresses non-compliance with laws and regulations. It explains that the professional framework does not permit a disclosure contrary to law. Obtain legal advice where disclosure authority or duties are unclear.

Close the finding only when the reviewer records the supported treatment and the authorised corrections are traceable. If evidence remains missing, keep the item unresolved and name the person responsible for obtaining it before the affected accounts are approved.

One client form. One finished return.

Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.

See how Tax Genie works

Made for Australian accounting firms

Tax GenieSee how Tax Genie works