Procurement Fraud: Red Flags and Bank Evidence

Procurement Fraud Across the Tender Cycle

Procurement fraud can enter at specification, bidding, evaluation or contract delivery. Each stage leaves different records.

Stage	Scheme and who commits it	Records to compare
Defining the requirement	An insider tailors specifications to a favoured supplier or divides one requirement into smaller orders.	Draft specifications, emails, estimated total value and purchase requisitions.
Receiving bids	Suppliers coordinate bids so an agreed supplier wins. Related businesses submit bids that appear independent.	Original bids, submission records, ownership information and bidder communications.
Evaluating and awarding	An evaluator conceals a conflict or changes scores to favour a supplier.	Conflict declarations, score versions, panel minutes and approval records.
Delivering and paying	An insider and supplier use unjustified variations or payments to the decision-maker to extract private gain.	Variation approvals, delivery evidence, invoices and bank movements.

Supplier-only schemes include bid rigging, which can operate without a corrupt employee. Insider schemes include deliberately splitting orders and concealing a personal interest. Joint schemes combine an insider’s influence with a supplier’s payment or benefit.

The Australian Competition and Consumer Commission (ACCC) describes bid rigging as suppliers agreeing who wins and at what price. Losing bidders can receive subcontracting work as compensation. A bank transfer can establish that money moved, while the bid records and communications establish the arrangement it supported.

Fictional Government Agency Example

A government agency seeks equipment maintenance. An evaluator adds a technical requirement copied from one supplier’s material, despite an earlier draft accepting equivalent equipment. The supplier wins, and its director later transfers $8,000 to the evaluator’s relative.

The specification versions establish who introduced the restriction. The evaluation file shows its effect on competing bids. Statements from the director and relative establish the payment. Evidence of the relative’s dealings with the director then tests whether the transfer was payment for legitimate work or a concealed benefit.

Fictional Private Company Example

A private company receives four orders of $9,800 for one installation. Its internal policy requires additional quotes for purchases above $10,000. The requisitions share a project description and the same approver, and the supplier’s director later pays $3,000 into that approver’s personal account.

The orders total $39,200. The project records establish whether the company already knew the full requirement when it approved the first order. Bank records establish the personal payment and its timing. Together, those records test whether the split purchases helped secure work in exchange for a benefit.

Red Flags in Tender and Contract Records

Tender red flags show where to investigate coordination, concealed interests or changes to the buying process. Compare related procurements before treating an isolated irregularity as a scheme.

Examine losing bids from businesses with shared directors or addresses. A common owner can make supposedly independent quotes misleading. Related bidders alone do not establish an agreement to rig the tender.

The ACCC’s procurement detection guide identifies identical spelling or calculation errors across bids as a warning sign. Compare original files to test whether a common adviser or supplied template explains the similarity. Also examine a winner that later subcontracts work to a losing bidder, particularly when that pattern repeats.

Contract variations can move the final price well above the tendered figure. Compare each variation with the original scope, the reason recorded and the work actually delivered. A genuine scope change explains extra cost. Repeated additions that were foreseeable before tendering can show that the original competition used an incomplete price.

Procurement fraud detection can begin through different channels:

• A tip-off can identify a private relationship, a conversation about a predetermined winner or pressure to alter specifications.
• An audit exception can expose missing quotes, an undeclared panel conflict, an unsupported variation or approvals outside a delegation.
• Data analysis can show repeated awards to one supplier, shared supplier details or payment clusters below limits across many transactions.

Preserve the underlying records and test each lead against an innocent explanation. Separate what a person reported from what the tender file or statement establishes.

Split Orders Below the Threshold

Grouping supplier payments by date and amount exposes purchases that may have been divided to avoid a quote, approval or tender limit. Group by the underlying project as well as supplier name, because related suppliers can divide the same work.

Start with purchase orders and requisitions, then match invoices to bank payments. Sort the ledger by supplier, project and approver. Review clusters over a short period and purchases spread across the project’s full life. Include credit notes and cancelled orders so the total reflects actual spending.

A payment below a threshold is only the starting point. An instalment under one properly approved contract differs from several separately approved purchases for a known combined requirement. Inspect the original estimate and communications to distinguish the two.

For Commonwealth procurements, the Commonwealth Procurement Rules prohibit dividing a procurement solely to avoid a threshold. Value includes the maximum contract value, options and extensions. The non-construction threshold for non-corporate Commonwealth entities is $125,000, including GST. Division 2 applies at or above that value unless an exemption applies, and limited tender requires an allowed condition or exemption. Other entity types and construction have different thresholds.

Bank Evidence Linking Officials to Suppliers

Bank evidence can connect a supplier’s funds to an official or relative, including through an intermediary. Work from statements obtained through lawful authority and preserve the original files beside the transaction analysis.

Search personal statements for payments from the supplier and its directors. Compare deposits with contract awards, approvals and variations. Search known intermediary names too, then follow matching debits and credits across supplied accounts. A delayed or divided payment can disappear from a search confined to the award week.

A statement description can suggest a counterparty, but account ownership needs supporting records. Match bank identifiers with supplier bank details and account-holder information. Compare company records with employee disclosures and other authorised employee records. Test shared addresses and directors against the relevant period, because an old address or professional registered office can create an incidental match.

Use relationship mapping through link analysis. Record which document establishes each relationship. A shared account is stronger evidence of common payment arrangements when ownership records support it. Keep an inferred relationship distinct from a confirmed one.

Where the suspected benefit is a secret payment to a decision-maker, kickback tracing examines that payment. For the procurement investigation, connect it to the decision the official influenced and the supplier’s resulting contract.

FinTrace saves investigators and forensic accountants hours of statement review by consolidating supplied PDFs into a searchable ledger and a clear findings report. The analysis flags suspicious transactions and follows transfers across related accounts. Every finding cites its source PDF filename and page, putting the bank evidence beside the analysis while you examine the tender records.

Reporting Paths for Public Sector Matters

The reporting path depends on the public body involved and the conduct suspected. Commonwealth corruption goes to the National Anti-Corruption Commission (NACC) within its jurisdiction. State and local government matters use the relevant state integrity body and its reporting rules.

Under section 33 of the National Anti-Corruption Commission Act 2022, a Commonwealth agency head has a mandatory referral duty for qualifying staff conduct. The duty arises when the head suspects the corruption issue could involve serious or systemic corrupt conduct. Intelligence agencies have a separate referral path under section 34.

Sections 37 and 38 address exceptions, timing and information. A required referral must be made as soon as reasonably practicable, subject to permitted later timing. The NACC’s mandatory referral guidance explains the required reasons and relevant information, including further information received later. Reasonable grounds that the NACC already knows the issue can remove the referral requirement.

For a procurement matter, organise the allegation and chronology beside the specifications, original bids and evaluation records. Include conflict declarations, approvals, variations and relevant payment evidence. Explain why the issue could be serious or systemic. Preserve originals and identify what each record establishes without waiting for a completed internal investigation to satisfy a referral duty.

State duties differ. In Western Australia, the Corruption and Crime Commission’s notification guidance requires a notifying authority’s principal officer to notify suspected serious misconduct on reasonable grounds. Its jurisdiction covers relevant WA public officers, rather than ordinary private company purchasing.

Government procurement also operates within control rules beyond the individual tender. The Commonwealth Fraud and Corruption Control Framework includes a legislative Rule for entities under the public governance framework. It requires reasonable measures to prevent, detect and respond to fraud and corruption. Its Policy binds non-corporate Commonwealth entities, while corporate entities and Commonwealth companies are encouraged to adopt it.

The Fraud and Corruption Policy sets procedural requirements for managing incidents, including investigations and reporting. An agency’s procurement response must follow those requirements and its control arrangements alongside any NACC referral obligation.

Controls That Prevent Procurement Fraud

Procurement controls reduce the opportunity to manipulate a tender or conceal a benefit when different people check the decision and its payment. Match each control to the scheme it must interrupt.

Separate ordering from approval and payment. Require an independent reviewer for specifications that restrict competition, and record the commercial reason for those restrictions. Keep evaluation criteria and score changes in the tender file.

Evaluation panel members must declare conflicts before examining bids and update their declarations when circumstances change. Compare declarations with supplier ownership information. Remove a conflicted evaluator from the decision and record how the conflict is managed.

Before approving a new supplier, independently check its identity and business details. Match supplier bank accounts, addresses and directors against authorised employee records. Resolve matches before payment, using account ownership and relationship evidence instead of automatically treating every match as misconduct.

Make the split-order review a regular control. Aggregate spending across supplier aliases and related projects, then examine clusters below approval limits. Give someone outside the purchasing chain responsibility for investigating exceptions and recording the outcome. Review contract variations against the initial requirement so extra work cannot bypass the original competition unnoticed.

For a supplier that keeps winning below the limit, start with the combined requirement and approval trail. If those records reveal a concealed relationship, connect the supplier payments to the relevant personal accounts and route the evidence through the applicable reporting process.