Define the problem before choosing a format

The trigger may be a departing accountant, transaction growth, delayed reporting, unexplained customer balances or a single tax question. “We need an accountant” leaves the provider to infer the problem.

Describe the current state and desired result. “Records exist, but receivables are not reconciled after month-end; we need an explained balance listing” is more actionable than “put things in order”. Identify urgent obligations and historical issues separately.

A one-off repair and continuing support may both be needed. Distinguish work required before the routine process starts from work repeated each period, so inherited problems do not continually interrupt current accounting.

Describe the operations and data condition

Document count is only one input. Ten recurring transactions differ from ten contracts involving currency, partial acceptance and returns. Include complexity, repetition, evidence quality and exceptions.

Information for a scope discussion
AreaDescriptionEffect
TransactionsSales, purchases, inventory, projectsAccounting processes
ScaleDocuments, accounts and employeesRecurring workload
ComplexityCurrency, imports, branchesAdditional review needs
DataSystems, closed periods and archivesReadiness to start
IssuesGaps, disputes and missing filingsSeparate priorities
OutputReports and decisions management needsDeliverable package

An initial discussion can use anonymised descriptions and ranges. Do not place employee records, identification documents or complete accounts in a public enquiry form. Agree the task and transfer channel first.

Choose full support, a defined function or a project

Full recurring support provides an external accounting process with agreed document flows. A defined function can complement an internal team. A project addresses a bounded need such as handover, reconstruction or analysis.

These are organisational choices, not uniform packages suitable for every business. A returns-only arrangement does not automatically correct the source documents and entries produced elsewhere.

If work remains internal, define the hand-off: who produces the data, checks completeness and corrects differences? Otherwise both teams may wait for each other to act.

Assign responsibilities by action

Article 9 of the accounting law allows contracted accounting while retaining management’s responsibility for organising it. Separate preparation, checking, approval and submission in the operating arrangement.

Illustrative responsibility discussion
ActionCompany roleProvider role
Source recordsConfirm transaction factsAssess accounting usability
CalculationsSupply complete inputsCalculate and explain
PaymentsAuthorise and executePrepare data where agreed
ReportsApprove inputs and authorityPrepare and submit as agreed
Disputed issuesMake management decisionsExplain facts and options

This table is a negotiation aid, not a universal legal allocation. Actual duties, authority and consequences must be consistent with the contract and applicable rules.

Compare the same scope across proposals

Ask what each period includes: document processing, reconciliations, calculations, reports, routine questions and the closing package. Then list exclusions such as reconstruction, unusual transactions, migration, disputes and unplanned projects.

Clarify how employee growth, new activities, foreign-currency transactions or a new branch change the work. Agree how additions are identified, assessed and authorised before they become disagreements.

Assess providers through verifiable information, their operating process and ability to explain boundaries. “Everything included” and an impressive website are not substitutes for checking capability. Examples of previous work must respect confidentiality; displayed logos alone prove little.

Define observable period outputs

An agreed package might contain reports and registers, filing confirmations, balance schedules, missing-document lists, open issues and the next action calendar. Its composition should reflect the contract and management’s needs.

Illustration: the owner expects a monthly customer-debt analysis, while the proposal includes only tax returns. Timely delivery of the contracted returns will not meet that unspoken expectation. Add the required schedule and identify its data inputs.

Monitor agreed dates, unresolved-issue age, input completeness and repeated errors. Message count and promises that no tax questions will ever arise are poor measures of accounting quality.

Agree the transition and exit before starting

Set the transfer date, access checks, opening figures and unfinished-work register. The first-period plan should reflect actual data limitations. Do not assess routine service speed from a period that also contains several months of reconstruction.

Agree data ownership, access to copies, export formats and permission handover on exit. Include open questions and filing evidence. A company should not discover these terms only when changing providers.

A useful BMS enquiry includes the operating profile, accounting condition and desired outputs. These support a comparable scope and a format both parties understand, including the company’s own role in making it work.

Support for your task

Discuss your task

Describe the situation and the output you need. Establish the work and information required to begin.