§ InsightsNo. 299

Software contract exit terms for an accounts review tool

What to check on change notice, support, liability and exit before signing a contract for an accounts review tool, from UK GDPR, UCTA and ISQM (UK) 1.

A practice partner and manager discussing a supplier agreement, checking the software contract exit terms for a review tool

This article is stated as at 22 November 2026. The ICO's guidance on processor contracts is under review following the Data (Use and Access) Act 2025, and legislation.gov.uk shows amendments to UK GDPR Article 28 from 30 September 2026, so check the current wording. Take advice on your own circumstances before acting.

Software contract exit terms are the clauses most partners read last, usually on the day they want to leave. They belong in the same exercise as choosing an accounts review tool, so before you sign or renew, check four things: how the vendor tells you about changes to the service, what support you get when files are due, where liability sits, and what happens to your client data at the end. UK GDPR Article 28 already requires a processor contract to give you, as controller, the choice of return or deletion of personal data at exit. Most of the rest depends on what the contract says and what you negotiate.

Why the contract belongs on your quality file

For a firm within the scope of ISQM (UK) 1, which applies to firms performing audits, reviews and other assurance or related services engagements, a review tool is a resource obtained from a service provider. ICAEW guidance cites the quality objective at paragraph 32(h): resources from service providers must be appropriate for use in the system of quality management and in performing engagements. And ICAEW is plain that “The firm remains responsible for its SoQM irrespective of whether the resources are provided directly through the firm or through a service provider.”

ICAEW names the service agreement as a good starting point for the information a firm needs to make that judgement, including how often updates will be provided, any limitations on use and how the provider handles confidentiality of data, and adds that the information has to be kept up to date. So record the vendor in your list of service providers. The FRC’s thematic review on network resources and service providers makes a further point: for a cloud based disclosure checklist, a SOC report over IT resilience and security does not provide assurance that the content is kept up to date and accurate.

So ask two separate questions. How is the service secured? And how does the vendor keep its technical content current with FRS 102, FRS 105 and Companies Act changes, and how will you know when it has? If your practice prepares accounts but carries out no engagements within ISQM (UK) 1, the same evidence is still a sensible record of why you chose the tool, and our guide to quality management for accounts preparation covers what that file can look like.

How much notice should a vendor give before changing the tool?

Standard terms often let the vendor change features, content or the underlying model by posting an update on its website, with no right for you to leave if the change makes the tool unsuitable. That sits awkwardly with a quality judgement you are meant to keep current, because the tool you evaluated may no longer be the tool you are using.

Under section 3 of UCTA, in England, Wales and Northern Ireland, a vendor dealing on its written standard terms cannot rely on a term letting it deliver something substantially different from what you reasonably expected unless the term is reasonable; section 17 gives similar protection in Scotland. But a clear change clause is worth more than a later argument about reasonableness.

When you read the change clause, look for:

  • written notice of material changes to a named contact at the practice, with release notes that describe changes to the review content as well as the screens;
  • a definition of material change wide enough to include the underlying model and the standards and legislation the tool covers;
  • a right to terminate without penalty, with help to export your records, if a material change makes the tool unsuitable.

When a material change arrives, evaluate the tool again before relying on it for the next batch of files. Running it over a sample of files you have already signed is a practical way to see what has moved, and our note on piloting a review tool on signed files sets out how to do it.

What support should a practice ask for in the accounts season?

ICAEW’s contractual guidance recommends a service level agreement covering response and fix times, clear severity classifications, and clarity on whether you can contact the vendor directly. Read the severity definitions as well as the headline response times, because a scale that treats “the tool cannot complete a review” as a moderate fault is of little use when a filing deadline is days away.

Check the hours of cover against your own busy periods, whether a manager can raise a ticket directly or only through a nominated administrator, and how long older versions stay supported. ICAEW cites desktop products whose support was discontinued, effectively rendering them unusable, so the end of support deserves a place in the exit terms too. And keep a fallback of your own: a reviewer who can finish a file without the tool, since the sign off stays with the partner whatever the software is doing that day.

Liability caps and what the law allows

Where vendor terms cap liability, for example by reference to fees paid, whether the cap holds in England, Wales and Northern Ireland depends on the reasonableness test in section 11 of the Unfair Contract Terms Act 1977: the term must have been a fair and reasonable one to include, given the circumstances known or contemplated when the contract was made. Where liability is capped at a specified sum, regard is had in particular to the resources available to meet it and whether cover could have been obtained by insurance, and the burden of proving reasonableness is on the party relying on the term. The Schedule 2 guidelines add the parties’ relative bargaining strength, whether you could have contracted elsewhere without a similar term, and whether you knew or ought reasonably to have known of it. In Scotland, section 17 gives a term in a standard form contract no effect to exclude liability for breach if it was not fair and reasonable to incorporate it.

There is therefore no general answer to whether a cap of twelve months’ fees is enforceable. Before signing, ask what insurance the vendor holds and whether it would meet the cap, whether data protection losses sit under a separate cap, and whether loss or corruption of data is excluded altogether, because for a review tool that may be the loss that matters most.

Data protection liability runs separately. Under UK GDPR Article 82 the practice, as controller, can be held liable for the entire damage to a client, while the vendor as processor is liable only for breaching processor obligations or acting outside your instructions. ICO guidance adds that you may claim back the processor’s share and that it may be contractually liable to you, so the contract decides how much you can recover. None of it moves responsibility for the accounts, which stays with the partner who signs them.

Software contract exit terms for client data

UK GDPR Article 28(3)(g) requires the processor contract to say that the processor, “at the choice of the controller, deletes or returns all the personal data to the controller after the end of the provision of services relating to processing, and deletes existing copies unless domestic law requires storage of the personal data.” The choice is the practice’s, so make it in writing when you give notice and ask for written confirmation once deletion is done.

The contract should deal with backups separately. ICO guidance on processor contracts accepts that data in backups or archives may not be deleted immediately on termination, provided safeguards are in place, such as putting the data beyond use at once, and the data is deleted as soon as possible, for example on the processor’s next deletion cycle. Agree that position and a stated timescale in the contract.

Return is harder than deletion. ICAEW points out that data protection rules give rights over personal data but not necessarily over business data, and the review points raised, the responses and the sign off trail are your evidence of review. Whether you get them back, and in what form, depends entirely on the contract. ICAEW also warns that standard exports are often reports rather than full data extracts, that APIs can be limited, and that a short notice period is of little use if migration takes much longer. It counts having no exit strategy among the biggest adoption pitfalls.

So ask for an export of the review records in a usable format, test it during the first year rather than at exit, and make sure the notice period and any read only access together cover the time a migration would really take.

Subprocessors, audit rights and the rest of Article 28

Under a general written authorisation, the vendor must tell you of intended additions or replacements of other processors, giving you the opportunity to object, and it remains fully liable to you for any subprocessor’s obligations. The contract must also give you the information needed to demonstrate compliance, allow for audits, including inspections, by you or an auditor you mandate, and commit the vendor to help with data subject requests, security, breach notification and any DPIA for the review tool. ICAEW notes that some vendors charge for responding to auditor requests, so check whether that applies. For the questions to put to a vendor before you get to the contract, see our list of questions for an AI supplier.

ICO guidance expects controllers to check a processor’s compliance on an ongoing basis, so put a periodic contract review in the diary. Our guide to client data and UK GDPR covers the data protection terms in more depth.

A checklist before you sign, renew or buy a practice

An acquirer inherits the target’s software contracts along with its files. Before completion, check whether each contract can be assigned or survives a change of control, whether historic review records can be exported before the target’s subscription ends, and who will be the controller of the client personal data in the tool from completion.

Term What to look for Basis
Changes to the service Written notice of material changes, release notes on content, right to terminate UCTA s.3 and s.17; ISQM (UK) 1 via ICAEW
Technical content How FRS 102, FRS 105 and Companies Act changes are reflected, separate from security assurance FRC thematic review
Support Response and fix times, severity definitions, direct contact ICAEW contractual guidance
Liability Cap level, insurance behind it, data loss exclusions UCTA s.11 and Schedule 2; s.17 in Scotland
Return or deletion Your written choice, confirmation of deletion UK GDPR Article 28(3)(g)
Backups Beyond use at once, deleted on the next cycle with a timescale ICO guidance
Export and read access Review points, responses and sign off trail in usable form; any charges ICAEW data guidance
Subprocessors and audit Notice and right to object; audit and information rights UK GDPR Article 28(2), (3)(h) and (4)
Renewal and price Automatic renewal, notice periods, price change terms, data escrow ICAEW checklist

Where the contract is large or the vendor will not move on standard terms, take legal advice before signing, because the reasonableness test is decided on the facts of each case.

Questions practices ask

Can the vendor delete our data from its backups straight away?

Not always, and the ICO accepts that. Its guidance says data in backups or archives may not be deletable immediately on termination, provided safeguards are in place, such as putting the data beyond use at once, and the data is then deleted as soon as possible, for example on the next deletion cycle. Ask for that position and a stated timescale to be written into the contract.

Can we keep read only access to old review files after we cancel?

Only if the contract provides for it. ICAEW lists the lack of an exit strategy as a common software adoption pitfall and points to whether read access continues, whether it is charged for and whether data can be bulk downloaded. Agree these before signing, and make sure the notice period plus any read only access covers the time a migration would really take.

Who is responsible under ISQM (UK) 1 if the review tool gets something wrong?

The firm. ICAEW guidance says the firm remains responsible for its system of quality management whether resources are provided directly or through a service provider, so the firm has to judge that the tool is appropriate for use and keep that judgement current. A review tool supports the reviewer, but the judgement and the sign off stay with the partner.

If we sell the practice, does the software contract transfer to the buyer?

That depends on the assignment and change of control terms in the contract, so a buyer should read them before completion rather than after. The buyer should also confirm that historic review records can be exported before the seller's subscription ends, and agree who will be the controller of the client personal data held in the tool from completion.

Sources

Part of the guide: Choosing an accounts review tool: questions to ask and how to test it