Following the decision to outsource accounting, a dedicated implementation project begins. A robust project kick-off combines the scope of services, responsibilities, data access, test cases and approvals in such a way that the accounting department is operational by the go-live.
The transition becomes particularly critical if open booking periods, missing access rights or unresolved approval workflows only come to light during the testing phase. Project problems then migrate into subsequent normal operations and cause queries, delays and duplicate work.
Which typical implementation errors in accounting outsourcing the separate error analysis shows what can arise from this.
A robust project plan therefore connects each phase with a clear project deliverable and a definitive sign-off point. This makes it possible to see whether the company is truly ready to launch or whether the go-live needs to be postponed.
The onboarding begins with a clear project brief before the first document transfer. By this stage, the decision to outsource accounting should already have been made or be ready to be made immediately. Companies in an earlier orientation phase will find the fundamental process of outsourcing bookkeeping in a separate overview.
Before kick-off, it must be clear which tasks the external service provider will take over and which activities will remain within the company. This includes, for example, document entry, Account coding, ongoing bookkeeping, reconciliations, preparatory evaluations and defined queries. The target state is equally important. The project needs a clear answer as to which processes must be functional at go-live.
A bindingly clarified scope of services prevents discussions during testing about tasks that should have been decided before the start of the project. This keeps setup and sign-off predictable.
On the company side, at least one person is needed who can gather information, coordinate internal queries and reliably drive decisions forward. On the service provider side, it must also be clear who is managing technical and organisational points. For short-term decisions regarding access, priorities or deviations, the designated contact persons need sufficient decision-making authority.
Before the project starts, it must be clear up to what period the bookkeeping is completed, which reconciliations are missing, and whether there are any backlogs or unresolved legacy data. For every open item, a clear assignment is required, even if processing is completed later. This assignment separates legacy data from the new workflow.
Starting criterionThe project start is robust when the scope of services, target date, responsible persons and known legacy issues are documented. Together with these prerequisites, the calendar date becomes a viable starting point.
A project plan for accounting outsourcing needs to achieve more than just a sequence of dates. Every project phase requires a verifiable deliverable. Only once this deliverable is available can the next approval gate be reached.
| project phase | Project outcome | Approval point | Responsible role |
|---|---|---|---|
| Project preparation | Scope of services, target deadline, initial situation and project team are documented. | Project brief is complete and internally confirmed. | Senior management and project managers |
| Kick-off | Work packages, communication channels, decisions and escalations have been agreed upon. | All parties involved confirm roles, deadlines and open points. | Project management on both sides |
| Provision of data and access | Master data, document workflows, system access and known legacy assets are available or have binding deadlines. | Test environment can be used with realistic data. | Internal subject matter experts and system administrators |
| Setup and test | Representative business transactions were fully processed through the designated procedure. | Deviations are documented, assessed and assigned to an individual. | Service providers and internal auditors |
| Acceptance and handover | Mandatory criteria have been met and remaining points have a controlled processing path. | Go-live is expressly approved or postponed with justification. | Named authorising officers |
| Stabilisation | Queries, corrections and responsibilities operate within the actual working rhythm. | Project is being transitioned to standard operations. | Operational managers on both sides |
Preparation establishes a common basis for work and focuses on the questions crucial for the kick-off. The kick-off translates this foundation into concrete work packages. This involves defining who provides which information, which decisions are necessary by what deadline, and how deviations are to be escalated.
The set-up can be verified as soon as real or realistic processes run through the intended procedure. A successful login demonstrates system access. The test also shows whether documents arrive, information is complete, queries reach the right person and results can be checked transparently.
Acceptance is a conscious decision. It bridges testing and planned standard operation. Open items can accompany the go-live if their impact is known, a responsible person is assigned and the resolution is compatible with the planned start date. Assessed and assigned items form a controlled backlog.
Many onboarding projects involve multiple people while decision-making authority remains unclear. A robust division of roles clearly assigns tasks, approvals and escalations.
Company pageShe provides technical information, data and access. She decides on internal responsibilities, priorities and the approval of the target process.
Service provider pageShe sets up the agreed processes, checks the technical feasibility of the data processing, and documents deviations from the testing phase.
Authorizing personYou evaluate the acceptance criteria, decide on open items and confirm whether the go-live is justifiable under the given conditions.
The person requesting access and the person with go-live approval may have different roles. The service provider may identify a technical deviation, whilst the company is responsible for the internal risk assessment. The project plan should therefore distinguish between processing, review and approval for each critical work package.
An escalation is effective when the recipient and the decision required are clearly identified. The statement „Access is missing“ becomes a manageable escalation as soon as it specifies the blocked work package, the required deadline for a solution, and the person responsible for finding an interim solution or rescheduling.
Typical sticking pointA company has a fixed go-live date, whilst the authority to evaluate missing access, unresolved legacy data or a deviating test posting remains unclear. In this case, the main problem lies in the decision-making structure.
The project plan must distinguish between the information required for setup and the data that will only be provided regularly during ongoing operations. For the test phase, a complete, verifiable subset is required that realistically depicts subsequent processes.
The information required is that which enables business transactions to be processed and audited unambiguously. Depending on the scope of services, this includes, for example, account logic, debtors and creditors, cost centres, open items, bank details and previous reconciliation statuses. The issue of documentation as a whole should be addressed in a separate audit of the required documents for accounting outsourcing.
Access details should be tested practically prior to the test. This concerns the correct system environment, the required functions, and appropriate allocation of rights. Contractual and data protection foundations must be clarified before productive personal data is enabled for processing.
The organisational elaboration on Data protection, access rights and secure data transmission shows how authorisations and data paths are secured for normal operation.
The technical implementation of uploads, exports, sharing and system integrations is covered in the article on digital document workflows and interfaces in depth. In the project plan, each path requires a test date and a clearly defined outcome that confirms it is functioning correctly.
Open accounting periods require a clear interface between previous and new processing. The project team must determine which transactions are still to be completed under the old procedure and which transactions are already moving over to the new process. Electronic documents and posting information must retain their traceability and the necessary retention context during the transition.
Verifiable preparationA verifiable project outcome goes beyond the access request: the designated person can log in, use the agreed functions and carry out a representative process in full, following the intended workflow.
The test phase is the key difference between a general outsourcing process and a specific onboarding project. It checks the practical functionality of the agreed process using the company's actual data, roles and systems.
A test case should map a typical business transaction from receipt to the auditable result. Depending on the company, this can include recurring supplier invoices, bank transactions, customer postings, credit notes or cost centre allocations. In addition, at least one case is needed where information is missing or a query arises. This is the only way to reveal whether the communication channel works as well.
standard caseA complete transaction goes through document flow, processing and verification within the intended standard process.
query caseAny missing information is identified, forwarded to the appropriate person and dealt with via the designated channel.
case of deviationAn unusual incident is documented and handed over to the person who decides on treatment or escalation.
Test caseThe result can be verified using the agreed documents and processing steps.
Acceptance criteria are defined before the test. At this point, it must be clear which functions and results are essential for the go-live. These can include working access, complete mandatory data, traceable processing, reachable contact persons and documented channels for queries.
An open-items list needs at least one responsible person, a target date and an impact on the go-live. An item can block the launch, be handled in a controlled manner after the launch, or be documented as an accepted residual risk. This classification turns the list into a management tool.
The go-live decision is based on functional criteria and the calendar. A go-live is justifiable if the critical test cases have been passed, roles and access permissions are working, and remaining items are transferred to regular operations in a controlled manner. If critical prerequisites remain open, a justified postponement protects operations from known project gaps.
Go-live checkAll agreed project deliverables are available. Critical test cases have been passed. Open items have been assessed and assigned. Persons responsible and escalation paths are accessible. Regular operations can begin with the agreed standard procedures.
The onboarding duration depends on the individual starting point. Two companies of a similar size can have very different project workloads. The decisive factors are the number of bookings, the quality of the starting point, and the number of dependencies.
Scope of servicesThe more tasks, examinations and votes are undertaken, the more processes must be clearly set up before the start.
Data qualityComplete master data and clarified open periods shorten the preparation time. Unclear inventory levels generate additional auditing and decision-making work.
system landscapeMultiple voucher sources, bank connections, approval systems or exports increase the number of technical and organisational test points.
Internal availabilityAvailable contact persons and sufficient decision-making authority accelerate tasks and clarify deviations at an early stage.
Backlog increases the need for clarification. Its impact on project duration depends on transparent scoping and clear assignment for processing. A small, unclarified legacy backlog can disrupt the start more severely than a larger backlog with a clean handover plan.
The testing effort depends on the actual risks of the intended procedure. A simple process with few data paths can be tested using a compact selection of representative cases. A procedure involving multiple companies, approval stages or systems requires more test cases and a more differentiated sign-off.
Realistic schedulingA fixed schedule only appears reliable once baseline data, responsibilities and dependencies have already been checked. Before that, a range or a phase-based plan is more robust than a flat number of days or weeks.
The go-live brings the technical preparation to a close. The stabilisation phase brings the rollout project to completion and demonstrates how queries, approvals and data deliveries function under real-time conditions.
Following the launch, remaining action items still require an owner, a deadline and a clear impact. The project team should distinguish between items that are still part of the rollout and topics that will be handled in the normal workflow going forward.
Following the initial real-world procedures, it must be checked whether the planned contact persons are actually reachable and whether decisions are made within the scheduled time. Roles that only work on paper must be adjusted before the project completion.
Onboarding is complete when the agreed procedures are functioning in regular operation, critical open items have been resolved or handed over in a controlled manner, and those involved are familiar with the ongoing work rhythm. After this begins the monthly routine of current bookkeeping with its recurring appointments, handovers and coordination.
stable routine operationA stable start is demonstrated by queries that are recognised, clearly assigned and answered within a functioning workflow.
Brasser Accounting Solutions GmbH is a specialised accounting service provider that supports companies with financial accounting, payroll accounting, and the structuring of modern digital accounting processes. The aim is a collaboration that is professionally sound, organisationally relieving, and reliably functional in everyday use.
Brasser Accounting Solutions GmbH is part of a corporate group with Quint GmbH Tax Consultancy & Auditing and the Swedish accounting and tax firm Service Place Årjäng AB.
