ECCTA failure to prevent fraud for public-sector suppliers and outsourcers
Suppliers and outsourcers to the public sector deliver through subcontractors, consortium partners, and bid intermediaries, and a fraud committed for the firm's benefit — manipulated tenders, false framework declarations, or overstated delivery claims — can engage the ECCTA failure-to-prevent-fraud offence. DefenceFile organises the evidence that fraud-prevention procedures existed and operated, so bid-governance and legal reviewers have a record to examine.
Not sure if you are in scope? Most government suppliers and public-sector outsourcers that meet the large-organisation size test are in scope — check the size test or the scope Q&A.
The sample board pack opens in your browser — no email, no form. 90-day pilots are £950/month; the setup fee is waived if the first working session does not produce the agreed artifacts.
Why government suppliers and public-sector outsourcers tend to be in scope
Many government suppliers, prime contractors, and outsourcing groups meet the large-organisation size test once turnover, balance-sheet, and headcount are aggregated across group undertakings. Subcontracting chains, consortium and SME-flowdown arrangements, and UK contracts and delivery typically keep the UK-nexus and associated-person questions firmly in play.
Scope is a legal assessment that turns on your group size and facts. See the UK-nexus and scope Q&A and reserve the conclusion for qualified reviewers.
Associated persons to map in public sector suppliers
An associated person is wider than payroll. These are the relationships worth organising evidence around for this sector.
- Subcontractors and SME partners delivering under prime contracts
- Consortium and joint-bid partners on framework tenders
- Bid-writing consultants and procurement intermediaries
- Sub-processors and IT or service delivery partners on contracts
- Agents and resellers representing the firm to public bodies
Fraud scenarios and the evidence to capture
Illustrative scenarios where a listed base fraud offence could be committed to benefit the organisation. They are prompts for human review, not findings.
Manipulated or collusive bids — cover pricing, false declarations, or bid-rigging — used to win public contracts for the firm.
Evidence focus: Capture the bid-governance, declaration-verification, and competition-compliance controls applied to public tenders.
False eligibility, social-value, or framework-compliance statements submitted so the firm qualifies for or retains public work.
Evidence focus: Organise the self-certification, substantiation, and sign-off records that support declarations made to contracting authorities.
Overstated delivery, milestone, or outcome claims raised to draw down public payments the firm has not earned.
Evidence focus: Record the milestone-verification, performance-evidence, and invoice-substantiation controls that govern claims against public contracts.
What the defence file should prioritise
- A register of subcontractors, consortium partners, and bid intermediaries with onboarding controls
- Attestations from subcontractors and partners that fraud-prevention expectations were communicated
- Bid-declaration and delivery-claim sign-offs linked to the policies that govern them
- Board and audit-committee oversight of the public-sector-fraud risk assessment
Public sector suppliers ECCTA fraud questions
- Are subcontractors and consortium partners associated persons under the failure-to-prevent-fraud offence?
- A subcontractor or partner can be an associated person where it performs services for or on behalf of the supplier, assessed on all the circumstances. The classification is a legal judgement; DefenceFile helps you organise the evidence by relationship so qualified reviewers can decide.
- Do framework subcontractors and delivery partners count as associated persons?
- They can, where a subcontractor or delivery partner performs services for or on behalf of your firm under the contract or framework, assessed on all the circumstances. Flowdown and consortium structures do not settle the question on their own. DefenceFile organises the contract and flowdown evidence so qualified reviewers can decide.
- How do we evidence that milestone and delivery claims against public contracts are substantiated?
- Maintain milestone-verification, performance-evidence, and invoice-substantiation records tied to each claim and linked to your fraud-prevention policies. DefenceFile keeps these discoverable and review-ready, without asserting that any individual claim was correctly earned.
Related sectors
- ConstructionHow construction firms organise ECCTA failure-to-prevent-fraud evidence across subcontractors and agents — scope, risks, and a reviewable defence file.
- Professional servicesConsultancies, accountants, and advisory firms carry ECCTA fraud exposure through associates and referral partners. Organise scope, risks, and a defence file.
- TechnologySoftware and SaaS firms face ECCTA failure-to-prevent-fraud exposure via resellers and channel partners. Organise scope, risks, and a defence file.
Keep going
- Failure to prevent fraud: the offence explainedThe statutory offence, the size test, and what a defence file is for.
- Reasonable proceduresHow the six principles map to evidence you can organise and review.
- Failure to prevent fraud: straight answersDirect, sourced answers on scope, penalties, the deadline, and the defence.
- Pricing and pilotsHow a structured pilot review of your evidence works.
DefenceFile organises evidence for legal and compliance review. It does not provide legal advice, create privilege, certify scope, certify reasonable procedures, or guarantee that a statutory defence will succeed.