# Hand records to an external accountant without losing control

An external accountant may maintain local books, prepare returns or file annual accounts. The company still needs a clear record of what it supplied, what the accountant changed and what was submitted. A shared folder without an agreed population and acceptance record leaves those questions unanswered.

Use this method to establish a monthly handoff or repair a process that relies on emails and unexplained journals. The controls are editorial recommendations. The engagement agreement and country rules determine the accountant's actual authority and responsibilities.

## Agree the scope of the engagement

Identify the entities, periods and deliverables covered. Separate bookkeeping, payroll, tax-return preparation, submission, payment and statutory accounts. A person who prepares a return may not be authorized to submit it or release the payment.

Record who approves accounting judgments and who can reopen a period. Name the person responsible for resolving incomplete documents. Define what happens when the company supplies a late invoice after the accountant has completed the return.

## Specify the handoff contents

Use a manifest to identify the records included in each handoff. Include documents, not only totals, where the accountant needs transaction-level evidence. Preserve original structured invoices and their references alongside readable copies.

| Population | Supporting material |
|---|---|
| Sales and credits | Legal document identifiers, customer data and correction links |
| Purchases | Supplier invoices, approval status and receipt evidence |
| Cash | Bank statements, reconciliation and unsettled items |
| Payroll | Approved payroll journal, liabilities and payment totals |
| Inventory and assets | Valuation schedules, movements and adjustments |
| Prior submissions | Filed versions, acknowledgements and unresolved authority messages |

Do not send personal or confidential records merely because they are available. Define the necessary fields and recipients for the task. Restrict access to the relevant entity and engagement, and record how access ends when the engagement changes.

## Separate completeness from accounting approval

The accountant's receipt confirms that a package arrived. It does not necessarily confirm that all records were usable, correctly classified or included in a filing.

Agree separate states for received, incomplete, accepted for processing, reconciled and approved for submission. Maintain a list of exceptions with the record identifier, missing information, responsible person and due date. Avoid a single "done" label that hides an unresolved tax classification.

## Reconcile a monthly package

Consider a hypothetical handoff containing 240 purchase documents with a gross total of 72,000 currency units. The accountant accepts 237 documents totalling 71,100 and rejects three totalling 900 because the attachments are missing.

The control equations are 237 + 3 = 240 and 71,100 + 900 = 72,000. Receipt of the 240-file archive is therefore not acceptance of all 240 transactions.

The company later supplies the missing attachments. The accountant processes the three existing document identifiers. They do not become three additional purchases. A revised acceptance record should show all 240 accepted and no unresolved amount.

This is a completeness example, not a conclusion that every accepted invoice qualifies for a tax deduction. Tax eligibility and accounting classification remain separate review decisions.

## Return adjustments in a usable form

Ask the accountant to return each adjustment with an identifier, posting date, accounts, amount, explanation and evidence. Link it to the original transaction where relevant. Specify whether the company must post it in the operational ERP or retain it only in local statutory books.

An unexplained closing balance cannot show which errors were corrected. A journal file without identifiers can be imported twice. Preserve both the adjustment package and the company's acceptance result.

Before approving the period, reconcile the revised ledger to the original handoff and accepted adjustments. Differences should be explained at transaction or approved adjustment level, rather than absorbed into a general suspense balance.

## Approve and retain the actual filing

Approval should identify the entity, period, return type and version. Save the approved output and the authority's response together. A successful upload is not necessarily acceptance, and an accepted return does not prove that the payment was made.

If the filing is rejected, keep the rejected version and the reason. If a correction is submitted, preserve its relationship to the original. The handoff process should let the company see the latest accepted position without deleting earlier evidence.

Record the accountant's delegated-access arrangement separately from document-sharing access. Both need an owner, but they perform different functions.

## Plan the last handoff before changing accountants

Agree the final period and unresolved items. Obtain original documents, ledgers, mappings, fixed-asset schedules, filed returns and acknowledgements in usable formats. Confirm who retains access to historical periods and how retrieval works after the engagement ends.

Test the export before the final deadline. Open a sample, follow an adjustment to its evidence and reproduce one reconciled period. If the export omits attachments or filing receipts, arrange that transfer before access is removed.

## Copyable handoff record

| Field | Record |
|---|---|
| Entity and period | Legal identifier and reporting period |
| Engagement scope | Books, returns, accounts, payroll and excluded tasks |
| Package | Identifier, date, document counts and totals |
| Acceptance | Accepted, rejected and unresolved records |
| Adjustments | Returned journal IDs, explanations and company posting status |
| Approval | Named approver and exact version |
| Submission | Sender, timestamp, response and payment status |
| Archive | Storage location, access owner and retrieval result |
| Exit | Last period, open issues and final export acceptance |

Related: [Local statutory accounts](https://erplocalization.com/guides/local-statutory-accounts-group-reporting/), [invoice archive operations](https://erplocalization.com/guides/e-invoice-archive-operations/), and [local-ledger operation](https://erplocalization.com/guides/operate-local-ledger-group-erp/).

## Worksheet: Hand records to an external accountant without losing control worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet

Copy this worksheet for each country or entity decision.

### Scope

- Legal entity:
- Country:
- Period covered:

### Decisions

- Arrangement chosen:
- System owning legal invoices:
- System owning statutory reports:
- Interface owner:

### Evidence to retain

- ☐ Product/edition documented
- ☐ Filing or export sample reviewed
- ☐ Acceptance criteria signed

## Related on this site

- [Country pages](https://erplocalization.com/countries/): key facts with sources
- [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support
- [All guides](https://erplocalization.com/guides/)

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-19.

Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

---
Canonical: https://erplocalization.com/guides/accountant-record-handoff/ · Last updated: 2026-10-19 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. License: data CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/), attribution "ERP Localization (erplocalization.com)"; commercial use needs a paid commercial licence: https://erplocalization.com/data-licence/ (hello@erplocalization.com).
