How to run an accounting services launch review

This is a method for an accounting services launch review, not a review of a named practice or product. No launch has been tested for this article, and no commercial relationship or rating is asserted. The eventual review record must name the independent reviewer, date, scope, evidence, conflicts and unresolved limits.

What to take away

Freeze the candidate service

Write the legal entity, customer population, services, jurisdictions, channels, software, suppliers, staff, fee version and launch date. Identify what is explicitly outside scope. A review of "the firm" is too broad to reproduce.

Inspect source evidence

Sample the engagement, acceptance file, workflow, deadline register, role matrix, training and competence records, access list, supplier assessment, incident plan, complaint route and published pages. Choose records across different risk and customer types rather than accepting a demonstration file selected by its owner.

HMRC's standard for agents provides a current source for applicable tax-agent expectations. The reviewer should map each relevant expectation to an operational control and file evidence, noting where another law or professional standard governs.

Authority is part of the evidence. Under the Money Laundering Regulations 2017, a business providing accountancy services must be supervised for anti-money laundering purposes, either by HMRC — whose money laundering supervision register can be searched online — or by a professional body supervisor such as ICAEW, ACCA, AAT, CIOT or ICAS, all of which are overseen by OPBAS. Check the named supervisor and the registration entry, and confirm the entity's registration (Companies House, for a company) and its professional indemnity cover, before treating supervision as confirmed.

Run end-to-end scenarios

Ask staff to process a representative client from intake to retained output. Include a late record, unusual transaction, reviewer correction, changed client approval and rejected submission. Observe system permissions and communications rather than relying on a written procedure.

Exercise a staff absence and supplier outage. Confirm that the deputy can identify work, retrieve current evidence and protect the deadline. Test an access removal and restoration from backup.

Challenge data handling

Trace a sample identity, transaction, payroll detail or tax record through collection, sharing, support access, retention and deletion. Compare actual decisions with the privacy record and contract.

The ICO's controller and processor guidance explains that roles depend on factual control of purposes and means. Treat an unexplained role allocation or undisclosed subprocessor as a finding, not a paperwork detail.

Review external promises

Compare website, advert, proposal and sales script with service capacity and evidence. Verify credentials, registration, price scope, response claims, testimonials and directory placement. Record the page version and date.

CAP Code section 3 covers misleading advertising, evidence, qualifications, comparisons and testimonials within its remit. A qualification must be visible enough to correct the likely impression.

Report findings by consequence

Classify each finding with affected service, evidence, consequence, root cause, immediate control, owner and deadline. Distinguish a missing document from a control that failed in practice. Do not average a critical launch blocker into a high overall score.

The reviewer should issue one of three bounded outcomes: ready within the tested scope, ready subject to named conditions, or hold. Management records acceptance of residual risks, but the reviewer retains their factual conclusion.

Attach an evidence index to the outcome. It should identify the file version, test case, participant, result and reviewer note without reproducing unnecessary client information. Record unavailable evidence and untested conditions openly. A later reviewer must be able to distinguish an observed pass from a supplier assertion or management explanation.

If the service changes between review and release, assess the difference before relying on the result. A new product edition, subcontractor, pricing page, responsible partner or customer segment can invalidate part of the tested scope.

Retest material corrections before launch. Schedule an early live review after the first complete cycle, because a controlled test cannot recreate every client or deadline pressure. Publish no star rating or "approved" badge from this internal method; it was designed to protect a specific launch, not to compare providers across the UK market.

Before you act

Common questions

What should be frozen before a review begins?

Write the legal entity, customer population and services. Add jurisdictions, channels, software and suppliers. Include staff, fee version and launch date. Identify what is explicitly outside scope, because a review of the firm is too broad to reproduce.

How should a reviewer handle data handling and privacy roles?

Follow a sample record through each stage and check real decisions against the privacy record and contract. An unclear role split or hidden subprocessor counts as a finding, not a minor detail.

What outcomes can a reviewer issue?

The reviewer gives one of three bounded results: ready within the tested scope, ready with named conditions, or hold. Management may accept leftover risks, but the reviewer's factual conclusion stands.