Government Procurement and Supplier Fraud: Who Bears Liability When a Contractor Isn't Legitimate?

Government procurement sits at the intersection of public funds, probity obligations, and personal accountability. When a fraudulent contractor receives payment without proper due diligence, the question of who is responsible lands on the procurement officer who approved it.

What probity requires in government supplier verification

Probity in procurement does not have a single definition, but the consistent thread across Commonwealth, state, and local government frameworks is this: procurement decisions must be made on the basis of documented, verifiable information. An officer who approved a contractor without checking their legitimacy cannot point to the absence of a policy as a defence.

For local councils, councillors and senior officers can face personal liability when public funds are misapplied. A fraudulent contractor payment is not just an organisational risk.

The pattern: valid ABN, fraudulent contractor

The most common government contractor fraud pattern does not involve an obviously fake entity. It involves a legitimately registered company with a valid ABN that has no genuine capability to deliver the contracted services. What distinguishes a legitimate contractor: a real web presence predating the tender period, a phone number connecting to an actual business, no insolvency or FWO compliance history, and director checks not surfacing associations with previously deregistered entities.

What Gumshoe checks at the tendering stage

A pre-award verification on a shortlisted contractor covers: ABN status and age, ASIC company registration, insolvency history, FWO compliance actions, SG compliance, web presence and domain age, and phone verification. This takes under a minute per entity and produces a saved, timestamped case record that becomes part of the procurement file.

Ongoing monitoring for panel contracts

Government supplier panels are particularly vulnerable to the phoenix pattern. A contractor on an approved panel may be legitimate at approval but enter administration during the contract period. Without ongoing monitoring, payments continue to a contractor no longer legally able to fulfil the contract. Phoenix Shield flags changes to registration status, insolvency register, and compliance history before the next payment is released.

Uncommon Insights

One lesser-known aspect of government procurement is that, under section 536(1) of the Corporations Act 2001, a procurement officer may be personally liable for a contractor payment if they have not exercised reasonable care in verifying the contractor's legitimacy. This means that even if the procurement agency has not established a clear policy for due diligence, the officer's failure to conduct basic checks, such as an ABN status check or ASIC company registration check, can still result in personal liability.

The Australian Taxation Office (ATO) has identified a pattern of contractor fraud involving legitimate companies with valid ABNs, but no genuine capability to deliver contracted services. In these cases, the contractor may have a real web presence, phone number, and no apparent insolvency or Fair Work Ombudsman (FWO) compliance history, making them appear legitimate at first glance. However, further investigation may reveal associations with previously deregistered entities or other red flags, highlighting the need for thorough due diligence.

ASIC's enforcement patterns suggest that procurement officers and agencies are increasingly being held accountable for failing to conduct adequate due diligence on contractors. In recent cases, ASIC has taken action against officers and agencies for breaching their probity obligations, resulting in significant fines and reputational damage. This trend emphasizes the importance of implementing robust due diligence processes, such as pre-award verification and ongoing monitoring, to mitigate the risk of contractor fraud.

The use of technology, such as automated monitoring tools, can significantly enhance due diligence processes and reduce the risk of contractor fraud. For example, tools like Phoenix Shield can flag changes to a contractor's registration status, insolvency register, and compliance history in real-time, enabling procurement officers to take prompt action and prevent payments to non-compliant contractors. By leveraging these technologies, procurement agencies can strengthen their probity frameworks and minimize the risk of liability associated with contractor fraud.