In this article
Key takeaways
- Agree a cutover date and balanced starting position.
- Assign one source to each posting stream.
- Accept the first month in the actual receiving system.
1. Choose a representative client and a clear cutover
Suppose the existing books are complete through 31 August and Hans starts current-period processing on 1 September. Record that boundary explicitly.
Choose a client whose real work includes the transactions you want to automate: routine invoices, recurring contracts, bank payments and, where relevant, provider settlements. Include an exception and a payment against an earlier invoice.
Retain the old documents and transaction detail. A cutover date separates current processing; it does not remove the need to explain historical balances.
2. Establish the starting books
Hans supports imports of master data, accounts and opening balances. Review identities, account mappings and the import preview before accepting the data.
A deliberately simple opening trial balance could be:
| Account at 1 September | Debit | Credit |
|---|---|---|
| Bank | β¬12,000 | β |
| Customer receivables | β¬900 | β |
| Supplier liabilities | β | β¬600 |
| Equity | β | β¬12,300 |
| Total | β¬12,900 | β¬12,900 |
The figures demonstrate a balanced starting position, not a recommended client account structure. A real import needs the full applicable trial balance, with the detail required by the supported import format.
The β¬900 customer balance might represent an unpaid August invoice. Its later payment clears that balance; it must not create September revenue again. Preserve the invoice-level history needed to identify the payment. Importing an aggregate balance does not import historical OPOS detail.
The supplier-mapping guide shows a payment against both an opening balance and a new invoice.
3. Assign one source to each posting stream
| Work | Example assignment | Check |
|---|---|---|
| Current purchase invoices | Hans | No second invoice import from another tool |
| Sales invoices | Agreed sales source processed through the chosen workflow | Webshop and processor records do not duplicate revenue |
| Assigned bank movements | Hans | The receiving bank workflow does not post them again |
| Payroll journal | Existing payroll system into the receiving ledger | Payroll expense and liabilities are present |
| Final returns and annual accounts | Firm's established process | Required submissions remain separately tracked |
Where payroll is recorded only in DATEV, the combined DATEV ledger is the complete payroll-inclusive result. Hans bank entries alone cannot supply payroll expense absent from Hans. Agree report scope accordingly; the payroll guide gives a complete reconciliation.
4. Configure the receiving format
DATEV: journal and master-data CSV files plus a document ZIP with associated references. Confirm account numbers, tax-key treatment, invoice references and the actual document retrieval workflow. Direct DATEV transfer is planned.
Agenda FIBU and Lexware buchhaltung: configurable CSV profiles matched to the receiving fields and conventions. Verify the client's actual import settings. Lexware buchhaltung is a different product from Lexware Office; this is not a claim of an Office API connection.
Other CSV workflows: custom profiles can adapt columns, account mappings, tax keys and date or number formats. The target must support the required import and preserve the information needed by the firm.
When continuing an existing target ledger, do not send its historic opening balances back into it as new activity. Agree whether the export contains current transactions, opening entries or another explicitly defined scope.
5. Accept the first complete month
A useful acceptance check follows transactions through the receiving books:
- A known supplier retains its existing account.
- A new supplier arrives with the required master data.
- A payment against an old balance clears the intended item.
- A current invoice, correction and payment appear once with their references.
- Bank, customer, supplier and provider balances reconcile.
- Tax results agree after the target's import rules have run.
- Supporting documents can be found from the corresponding entries.
Keep trial comparison files separate from accepted import packages. Retain the accepted version and import outcome. The export guide covers partial imports and control totals.
Measure setup separately from recurring work. Once the month has been checked, reuse the established process for the next suitable client, adapting its own facts and settings.
Start with your first mandate free
Your first named mandate stays free, with all features and personal setup help. Practice costs β¬40 net per month for two total mandates, then β¬40 each. Growth costs β¬300 net per month for ten total mandates, then β¬30 each. No payment card is needed for the free mandate; additional paid capacity requires your price confirmation. See the current firm pricing.
Bring the client's software setup and representative records to the demo. The useful demonstration ends with the reviewed monthly books and a handover your firm can assess.
Sources
Sources were checked on 06 October 2026. This article provides orientation and is not tax, legal, or accounting advice.