Move your bookkeeping to Odoo, from SnelStart, Exact and others

Moving a company from its bookkeeping package to Odoo is mostly careful, repetitive work: matching the old accounts to the new chart, matching VAT codes to taxes, getting the opening balance and the unpaid invoices right, and then proving to the accountant that nothing was lost. Rekhu Builder for Odoo now does that work with you, from the project chat.

It starts from the audit file

Every Dutch bookkeeping package can export the audit file (XAF), because the tax authority asks for it: SnelStart, Exact Online, Twinfield, AFAS, e-Boekhouden and others. One file holds the chart of accounts, customers and suppliers, VAT codes, the opening balance and every entry of the year, with its own control totals. Upload it to the Odoo project in your Rekhu account, together with the list of open items on the start date when you have it, and ask the builder to bring it into Odoo.

No audit file? Four exports are enough

Packages abroad export their own audit files (SAF-T in Portugal, Poland and Norway, FEC in France, DATEV files in Germany), and the builder reads those the same way. From Xero, QuickBooks, Sage or a spreadsheet kept by hand, four plain exports are enough for a move at the start of a year: the chart of accounts, the trial balance on the start date, the open invoices of customers and suppliers, and the list of customers and suppliers. Add the journal report when the transactions of the year should come along.

Moving from Odoo Online to your own server is different: the database moves as a whole, with its files, and is not imported record by record.

What the builder does

• Agrees the scope first: the start date (usually the first day of a financial year), and whether the transactions of the current year come along or only the opening balance and the open invoices.
• Builds an import module in your Odoo: a wizard that reads the file on the server, also when it is tens of megabytes, so the data never has to pass through the chat.
• Maps instead of copying: the old accounts onto the Dutch chart in Odoo, VAT codes onto Odoo's taxes, day books onto journals. You see every row and accept it before anything is imported.
• Imports on a staging copy first: customers and suppliers with their VAT numbers and IBANs, the opening balance, and the open invoices one by one per customer and supplier, so every payment that comes in later can be matched in Odoo. Running the import again updates what it made; it never doubles it.
• Proves the numbers: a report per account, per month and per customer and supplier against the file and its control totals. The import goes to production only when every difference is zero.

Your client's data

Bookkeeping data is personal and financial data. The builder reads the real file only to learn its structure; its contents never go into the module's code, tests or the chat, and the tests use a small invented file. Build and test on a staging copy of the client's database, and agree the processing of their data with your client before you start.

Get started

Create an Odoo project in your Rekhu account, install Rekhu Builder on a staging copy of the client's database, upload the audit file and say what you want. A new account starts with $10 credit. Read more on the Rekhu for Odoo page.