Choosing bookkeeping support for a growing company

Bookkeeping support should fit transaction volume, complexity and the decisions the business needs to make. Define the work: document capture, coding, reconciliation, credit control, payroll interfaces or management reporting. Do not assume that a service described as bookkeeping includes tax returns or statutory accounts.

Agree responsibilities, deadlines, software access and the route for unresolved questions. Check competence for the business's actual systems and activities. Keep the company in control of its records and understand how information will be handed over if the engagement ends.

Define the work the company needs covered

List transaction volume, payment channels, currencies, payroll interfaces and reporting needs. Identify whether the business needs routine entry, reconciliations, credit control, management reports or help preparing records for annual accounts. These tasks are related but not identical. A proposal for monthly bookkeeping may exclude tax advice, year-end adjustments or chasing customers, so agree the actual scope before comparing fees.

Describe current problems with examples: missing receipts, unreconciled platforms, late reports or unexplained director balances. Ask the prospective provider how those issues will be handled and what information the company must supply. A service cannot produce reliable records from missing facts indefinitely. The engagement should make both parties' responsibilities clear rather than promise a complete solution without discussing the underlying evidence.

Review competence and the reporting process

Ask about experience relevant to the company's business model and software. A retailer with stock and several payment platforms has different needs from a small consultancy billing fixed-fee projects. Review who performs the work, who checks it and how questions are escalated. Avoid assuming that an impressive dashboard demonstrates the quality of reconciliations or accounting judgement behind it.

Agree the monthly timetable, query format and deliverables. Directors should receive a clear view of unresolved issues and material balances. GOV.UK confirms that directors remain responsible for company records and accounts even when professionals are engaged. ^[1] Delegating preparation should improve visibility, not leave the company unable to explain its own figures or access the supporting evidence.

Keep access and ownership under company control

Use individual permissions appropriate to the work and retain suitable company administrator control. Do not give unrestricted banking or system authority where read-only or narrower access is sufficient. Define payment responsibilities separately from bookkeeping. If the provider handles personal information, assess the relationship, contract and security requirements rather than relying only on the software's brand reputation.

Use Data processing contracts with suppliers for relevant processing arrangements and Accounting records when changing software for migration and handover planning. Agree who owns subscriptions, how records are exported and what happens on termination. The company should not discover during a change of adviser that attachments or historic reconciliations are accessible only through an account it cannot control.

Compare price with assumptions and exceptions

Check transaction limits, extra charges, clean-up work and support outside the ordinary cycle. A low monthly fee may assume fully organised records or exclude complex platforms. Ask how additional work is approved and how a material increase in volume changes the arrangement. Compare proposals on equivalent scope rather than choosing between totals that represent different services.

Agree a process for corrections and performance concerns. If a recurring problem appears, identify whether it arises from late company information, software configuration or provider work. Keep the discussion evidence-based and record the change needed. Avoid measuring service quality only by how quickly the ledger is marked complete if unresolved items are simply moved into miscellaneous categories.

For Limited company bookkeeping, provide a representative month, current systems and the reports directors need. Request a clear scope and a practical transition plan with opening balance checks. Review the first reporting cycle against agreed deliverables and resolve setup gaps early. As the company grows, revisit the arrangement so responsibility, access and reporting remain suitable instead of assuming the original package covers every new activity indefinitely.

Test the service using a realistic handover question

Ask a prospective provider how they would handle a missing invoice, a disputed director balance and an urgent cash report. Their explanation should identify what they need from the company, what they will investigate and which questions require a different specialist. This gives more useful evidence of fit than a broad promise to take care of everything.

Confirm the communication route and how unresolved items appear in regular reporting. Request a sample deliverable with fictional or properly anonymised data if available, and assess whether directors can understand it. Keep the company's own approval responsibilities clear. A well-matched service should make outstanding decisions visible and manageable, rather than produce apparently tidy books while important factual questions remain hidden in an internal provider inbox.

Illustrative scenario

A growing retailer appoints support for bank coding but expects payment platform reconciliations to be included. The scope discussion identifies the gap and adds the required settlement review with a monthly timetable. Directors know which reports they will receive and which questions still need their input.

Preparation checklist

• List the tasks and systems requiring support.
• Agree deliverables, timing and responsibility for evidence.
• Set appropriate access and payment approval controls.
• Document record ownership, export and termination arrangements.