Importing a book
When your organisation moves onto the platform, its existing accounts come across as a book import. You run it yourself, one step at a time, and you can see what each step still has to do before and after you run it.
You do not need a configuration file, and nothing starts on your behalf. You choose which accounts to bring across, work through the steps, and post the books when the result looks right.
What you are importing
The page names the snapshot your configuration was transformed from, the date the source system stood at, and how many accounts it holds. That date matters: it becomes your trading date, so the whole book is brought in as it stood on that day and walked forward from there.
If your organisation has no snapshot recorded, the page says so and offers no steps. There is nothing to import until that is in place.
The steps
An import is seven steps. Each one reports how much of its work is outstanding for the accounts you selected, counted from the book itself rather than from what it remembers doing — so if you widen your selection, the steps that were finished have work to do again.
| Step | What it brings across |
|---|---|
| Exchange rates | The historical rate series, so back-dated amounts price correctly |
| Reference data | The operating entities, structures and counterparties your accounts name |
| Accounts | The accounts themselves, without any transactions |
| Transactions | The movements on those accounts |
| Legacy history | The pre-cutover history your reports draw on |
| Books | The general ledger and the period closes |
| Instalment legs | The forward schedule each account reports on |
Steps wait for each other. Accounts cannot come across before the rates that price them, or before the reference data they point at. When a step is waiting, the page names what must run first.
Working through it
- Select Start a conversion.
- Enter how many accounts you want and select Select accounts. Start small — twenty accounts is enough to check that the shape is right.
- Run each step that shows as Ready, in turn.
- Check the result. If a step brought something across wrongly, correct the cause and run it again.
- Widen your selection and repeat, until the whole book is in.
Summarised history
Your legacy system may have booked interest and revaluations every day. Brought across day by day, that is decades of daily entries in your books. If your organisation chooses summarised history, the books step posts one entry a month instead.
| What | How it comes across |
|---|---|
| The transaction types your organisation lists, in complete months before the snapshot month | One entry per month, per ledger account pair, per cost centre |
| Every other transaction type | One entry each, as it was |
| The snapshot month itself | One entry each, as it was |
Payments, advances and redemptions keep their own entries, so the ones an auditor asks about by name are still there.
What stays exact
Every ledger balance at every month-end is the same, to the cent, as daily posting would give. Each day is still converted at its own day’s exchange rate, and the monthly entry adds up the converted days. Only balances part-way through a summarised month differ.
The account itself keeps every daily transaction. Nothing on the account is summarised.
Reading a summarised month
A summarised entry says what it stands for. On the Trace and Entries panels, its row reads covers 30 transactions, March 2019. Select it, and the account’s transaction list opens on that month.
A summarised revaluation reads covers 21 daily revaluations, March 2019, with no link. Those daily revaluations came from your legacy system and are not account transactions. Your legacy revaluation report is where you read them.
Moving cost centre after a summarised import
You cannot move an account to a new cost centre with an effective date before the books opened. For an imported book, the books open on the snapshot date. Before that date your legacy system owned the account’s centre, and it has already reported that history.
Running a step again
Some steps can be run again after you correct something. Before it runs, you are told what running it again replaces and how many accounts that affects — a step that cannot say what it would replace will not run again at all.
Running a step again is destructive: it discards what that step wrote and writes it afresh. It is a separate permission from running a step in the first place, so your organisation can let you run the import without letting you undo parts of it.
Posting the books
Posting the books closes the book to further accounts. Once they are posted, you cannot widen the selection or bring more accounts across — so post them only when the accounts you want are all in and you have checked them.
What your organisation configures
- Which snapshot your configuration was transformed from, and the date it stood at.
- Who may run the import, and separately, who may run a step again destructively.
- Whether history comes across daily or summarised by month, and which transaction types are summarised. This is chosen before the import and cannot change during it.
- The account types, numbering schemes and counterparty types your accounts refer to. An account naming something your organisation has not set up will stop the step that needs it, and the step names what is missing.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.