Bring historical accounting into Books

This feature is in early access: it is built and tested, but not yet switched on for every organisation or not yet tried with the outside provider. Ask us on WhatsApp if you would like to try it.

The workspace owner can open Books → Historical migration (/books/migration) with full Books closing access. Import customers and suppliers first. Use the organisation’s base currency and main branch; other currencies and branches are not supported by this importer.

1. Download the CSV template. Supply one ledger line per row, grouped by a stable external ID. Choose journal, opening, invoice or bill. Reuse the same source-system identifier for later exports from that system.
2. Supply account keys or id:ACCOUNT_ID, dates and debit/credit amounts. For invoices and bills include the existing party ID, original total, tax, paid amount and due date. Use the contact’s ID from its Kluvan URL, not its name.
3. Upload CSV, TSV or XLSX: at most 250 KB, 500 lines and 100 entries per batch. Select the sheet and map headings.
4. Preview every entry. Debits must equal credits. Compare source balances and document totals. Confirm the reviewed content explicitly, then run the batch.
5. Read the reconciliation receipt and open the created documents. Resume an interrupted batch from its saved page; do not change source IDs to retry it.

Invoices and bills retain original dates and create canonical paid, partly paid or unpaid documents. Their receivable/payable line equals total minus paid. Do not also import the same party balance through list opening balances or a generic opening journal: that would count it twice. Generic journal/opening entries cannot contain receivable/payable accounts.

An optional posting date supports a later open cutover period while preserving the original document date. Closed periods and future-posting restrictions remain enforced. Historical VAT lines are kept in the ledger but excluded from new tax returns. Review your source trial balance separately; a balanced batch alone does not prove a complete migration.

Repeated source identities with unchanged content are safe to resume; changed content is refused. Receipts retain source references. There is no whole-batch undo: correct posted records using the normal permitted accounting correction process. This flow uses no AI credits.