Export for the tax adviser
Checked document by document against the source system. And why a difference of exactly twice the tax was a sign error.
- Task
- Export bookings, personal accounts and chart of accounts from the ERP system into the import format of the tax adviser's accounting software
- Format
- CSV with 41 fields, character set cp1252, optionally a ZIP with document PDFs
- Checks
- More than 140 automated tests, trial runs against a test system
The problem
Two systems, one set of figures
The accounting runs in the ERP system, while the tax adviser works in their own software. In between, a route is needed that transfers bookings, accounts and documents without loss, in a format that is strict: fixed number of fields, character set, date format.
The solution
An export in the recipient's format
A wizard in the ERP system creates the import file and, on request, puts the documents as PDFs into a ZIP. The import itself happens at the tax adviser, manually, in their software. There are also exports for personal accounts, general ledger accounts and the chart of accounts.
Workflow
From document to import
- Own systemBookings in the ERP systemInvoices, bank, miscellaneous
- Own systemExport wizardprepares the linesTax codes, booking types, split for several tax rates
- DataFile and ZIP41 fields, cp1252, documents as PDF
- External systemImport at the tax advisermanually in the accounting softwareTrial run possible, duplicate check only there
What we learned
What we found along the way
The difference of twice the tax
In the trial run, the accounting software reported: totals do not match. The difference was exactly twice the tax. The cause was the sign of the tax amount. The fix and the counter-check were quick. We only found it because we compared the totals.
Document by document
In the trial run we exported eleven months of outgoing invoices and checked 161 documents one by one against the ERP system. 159 were identical, 2 deviated (a negative invoice line and a rounding of one cent). Both are fixed, and the next run was error free.
A warning that belongs in the documentation
The accounting software only checks for duplicates in the trial run, not in the real import. That is why it appears as an explicit warning in our documentation.
A similar problem?
Tell us about it. The case studies show how we work, but every project starts with listening.
Discuss a project