FCA authorised · FRN 724952 0117 325 0027Quote & buy →
Software projects
Yes. If you design and configure ERP, finance, CRM or HR and payroll systems for clients, you need professional indemnity insurance. The expensive failures on implementation projects come from decisions and settings: a tax code mapped wrongly, a pay rule left untested, a go-live called too early. They cause financial loss rather than injury or damage, so public liability will not pay. PI answers the client’s claim that your work fell short; it does not refund your own overrun on a fixed-price job.
Part of: Professional indemnity for IT professionals
In short
Implementation partners turn a client’s processes into system settings, and a wrong setting can run unnoticed for months. VAT treatment, payroll deductions, approval rules and user permissions are common sources of claims, alongside go-lives that fail and projects that stall. In business contracts in England, Wales and Northern Ireland, the Supply of Goods and Services Act 1982 implies a duty of reasonable care and skill. A fixed-price promise to deliver a working system can go further, and PI is built for negligence, not guarantees. Signing off user acceptance does not always end your exposure. PI usually responds to client claims; cyber covers attacks on your own systems.
Last reviewed 5 October 2026 by the Apex professional indemnity team.
An implementation partner sits between a software product and the way a client actually runs. You lead discovery, write the solution design, set up the chart of accounts, tax codes, pay elements, workflows and user roles, configure integrations and steer the client through testing and go-live. The product may work exactly as its publisher intended; the question in a dispute is whether you set it up correctly for this client.
When that goes wrong, nobody is injured and no property is damaged, so public liability (PL) insurance has nothing to answer. The client is left with wrong invoices, wrong pay or a system its staff cannot use, and it claims the cost of putting things right and the trade it lost. That is an allegation of professional negligence or breach of contract, which is what professional indemnity (PI) is for.
Insurers normally write PI for implementation firms as technology errors and omissions cover. Check that the business description names configuration, integration and any custom development, not only “consultancy”.
The five scenarios here are illustrative, not accounts of real claims. Each shows the failure, who lost money and what they would allege.
Implementation disputes are argued against the contract, the client’s legal obligations and what a competent partner would have built.
| Rule or source | What it says | Why it matters to you |
|---|---|---|
| Supply of Goods and Services Act 1982, ss.13, 14 and 16 (business contracts, England, Wales and Northern Ireland) | A business supplier must use reasonable care and skill, and work within a reasonable time where none is fixed. Express terms can vary these duties, subject to the Unfair Contract Terms Act 1977, but only displace them where inconsistent. | The baseline for any negligence-style claim. Extra promises in a statement of work sit on top of it. |
| VAT domestic reverse charge (HMRC) | For certain building and construction services reported under the Construction Industry Scheme and supplied on or after 1 March 2021, the customer accounts for the VAT, and the supplier’s invoice must make clear the reverse charge applies. HMRC told businesses to make sure their accounting systems and software could deal with it. | One wrongly mapped tax code produces wrong invoices and wrong returns until someone notices. |
| Making Tax Digital for VAT (VAT Notice 700/21) | VAT-registered businesses must keep certain records digitally in functional compatible software. Data moving within or between the programs that make up that software must move digitally; manual transfer is not acceptable. | An implementation that leaves a copy-and-paste step between the ledger and the VAT return breaks a link the client needs. |
| PAYE real time reporting (HMRC) | Employers send a Full Payment Submission on or before each payday. | A payroll go-live that slips past payday, or files wrong figures, puts the client in breach from the first run. |
| UK GDPR, Article 25(2) | The controller must ensure that by default only personal data necessary for each purpose is processed, and that it is not made accessible without the individual’s intervention to an indefinite number of people. | The duty is your client’s, but it relies on the roles and sharing rules you configure to meet it. |
The pricing model changes the kind of promise you make, and PI follows the promise.
Three clauses decide how far a fixed-price dispute can reach: change control, and whether you actually used it; liquidated damages for late go-live, which PI usually excludes or limits; and the overall liability cap. Price the risk you keep, and leave PI to the negligence claims it is designed for.
Partners often hope that user acceptance testing (UAT) sign-off moves all risk to the client. It rarely works that cleanly. Acceptance usually shows that the agreed tests passed; it does not prove the design behind them was right, and many contracts keep a warranty period or defects regime running after go-live.
Government buyers draft for this deliberately. Guidance on the Model Services Contract says a milestone is not complete until all deliverables, including acceptable test results, are produced, and it distinguishes “acceptance” of a service from an Authority to Proceed, which leaves the supplier with the risk of failing to meet the agreed specification. Expect well-advised private clients to take a similar line.
| Usually covered by PI | Often excluded or limited | Needs a different policy |
|---|---|---|
| Negligent configuration of tax codes, pay rules, workflows and permissions | The cost of finishing or redoing your own work on a fixed-price project | A ransomware attack on your own network (cyber) |
| Negligent advice on design, go-live readiness and cutover | Liquidated damages and service credits for late delivery | Injury or damage at a client’s offices (public liability) |
| Errors in integrations or custom code you wrote, where declared | Promises that the system will achieve a result | Theft of client money by one of your own staff (crime or fidelity cover) |
| Data damaged or lost during migration through your negligence | Tax, interest or pay the client owed in any event | Injury to your own employees (employers’ liability) |
| Defence costs, including independent system experts | Fines and penalties, which wordings commonly exclude | Directors’ personal liability for running your firm (D&O) |
Cover is subject to the insurer’s acceptance and the policy terms. If you also resell subscriptions, say so: a defect or outage in the publisher’s product is not your professional error, and claims about it may fall outside PI.
For the life of a project your consultants hold administrator rights on the new platform, keys for its integrations and, often, extracts of live data for testing and migration. That access decides how PI and cyber split the risk.
Remove your administrator accounts when hypercare ends and delete extracts you no longer need. Expect insurers to ask how you control privileged access to client environments.
Your PI limit will usually come from the client’s contract, often linked to the project value or the liability cap, and public sector tenders state a figure. Check whether the requirement is each and every claim or in the aggregate, and whether your cap applies per claim, per year or across the whole contract.
Duration matters. A misconfigured tax or pay rule can run through several reporting periods before anyone notices, often at a year-end, an audit or a tax inspection. PI is claims-made, so the policy that responds is the one in force when the client complains, not the one you held during the build. Keep cover continuous, protect your retroactive date if you change insurer, and arrange run-off if you sell the firm or stop trading. The difference between the two policy bases is explained in claims-made and occurrence cover compared.
A complete proposal gets better terms than a bare one, and a broker can only present what you tell us. Have these ready:
Speak to a broker
PI for software implementation specialists, placed by a named broker
Start the online proposal and save it as you go, or leave your number and a named broker will call you back, usually the same working day.
Apex Insurance Brokers is an independent insurance broker based in Bristol, established in 2009 and authorised and regulated by the Financial Conduct Authority. We are not tied to one insurer: we work with over 30 markets, including Lloyd’s syndicates through wholesale brokers, and every client has a named broker who handles the placement, mid-term changes, certificates for clients and the renewal.
Yes. Clients rely on the settings and advice you provide, and a wrong tax code, pay rule or go-live call can cost them heavily. Public liability does not cover that kind of financial loss. PI pays defence costs and compensation if your work is alleged to be negligent, subject to the policy terms.
No law requires implementation partners to hold PI. Clients do: many implementation contracts and public sector tenders set a minimum PI limit, often tied to the project value or the liability cap, and ask for evidence of cover before work starts. Some also require you to keep cover for a period after the project ends.
No. Finishing or redoing your own work is a commercial risk you accepted when you agreed the price. PI responds when the client claims its own losses because your work was negligent, such as the cost of another partner correcting a faulty configuration, subject to the policy terms.
It may. Acceptance usually shows that the agreed tests passed, not that the design was right, and many contracts keep warranty or defect obligations running after go-live. Whether sign-off limits a claim depends on your contract wording, so keep a record of what was tested, what was left open and what you advised.
It can, if the error was negligent and caused the client a loss, such as correction work, adviser fees or payments to staff. It won’t pay tax or wages the client owed anyway, and wordings commonly exclude fines and penalties. Tell your insurer as soon as the error comes to light.
Agree it in the contract before the project starts. A common split is that the client owns the quality and cleansing of its source data, while you own the mappings, scripts and loads you build, with reconciliations signed off by both. Leaving it vague invites argument after a difficult go-live.
Apex arranges professional indemnity insurance for software implementation specialists across the UK. Tell us about your work and we’ll find cover that fits. Or call 0117 325 0027.
Start your PI proposal Call 0117 325 0027Apex Insurance Brokers Limited is authorised and regulated by the Financial Conduct Authority. Registered in England and Wales, company number 07014570. This page is general information, not advice on your individual circumstances. Cover is always subject to the insurer’s acceptance and the policy terms, and this page does not guarantee that cover will be available or on what terms.
