Moving onto a new ERP means telling it where your books stood on day one. Here's how our self-service opening balance workflow lets your own team enter that starting point directly, with built-in checks — including evidence tracking and audited-accounts support — that catch mistakes before they reach your accounts, plus a live reference example you can click through yourself.
Every ERP rollout has the same first milestone: telling the new system where your books stood on the day you switched over. We call these your opening balances — every account balance, every customer who owes you money, every supplier you owe. Everything the system reports from that point on is built on top of this starting position, which is why getting it right matters more than almost anything else in an onboarding.
Some clients hand Sempya a spreadsheet and have our team key the figures in. Others prefer to enter them directly themselves, on their own schedule, with their own accountant driving. For that second group, we built a self-service workflow directly into CloudERP.
What it looks like in practice
A small number of people at your company — typically whoever owns your books day to day — get access to a single working record: your company's Opening Balance Batch. It's organized into the sections you'd expect from any handover: trial balance, debtors, creditors, bank and cash, stock, and fixed assets where applicable. There's nothing to set up or configure — it's ready to open and fill in.
An Onboarding Progress panel sits at the top of that record the whole time, showing each section as Complete or still outstanding, plus any checks currently failing — so at a glance, both your team and ours can see exactly what's done and what's left, instead of everyone re-deriving status from a spreadsheet or an email thread.
A safety net most spreadsheets don't have
The part we think matters most: before anything can be submitted, the system checks that total debits equal total credits across everything entered — standard double-entry bookkeeping, enforced automatically rather than trusted to a manual review. If it doesn't balance yet, the system shows exactly where the gap is, so it can be fixed on the spot rather than surfacing three months later as an unexplained variance. That check can be re-run as many times as needed while work is still in progress — there's no penalty for checking early and often.
Showing your workings
Not every figure carries the same weight on day one. A bank balance can usually be confirmed to the last cent; a stock count pulled together during a handover might be an honest estimate pending a proper physical count. The workflow lets your team flag each figure for exactly what it is — confirmed by a third party, backed by audited accounts, documented, your own best assertion, an estimate, or a plug figure while something is still being tracked down — and attach the actual supporting document (a bank statement, a ZRA portal extract, audited financial statements) directly against the line it backs up. If your outgoing accountant already produced audited accounts, that's now a first-class option here, not something to explain away in an email thread.
Our reviewers see this at a glance: which figures are proven, which are still resting on your own word, and — just as usefully — which of the statutory lines a Zambian business your size would normally carry (VAT, PAYE, NAPSA, NHIMA, withholding tax) this batch doesn't have yet. None of this blocks you from moving forward; it just means nothing quietly falls through the cracks. A dedicated Line Checklist shows every single line across every schedule with its own coverage verdict — covered, missing its evidence, still a soft assertion, or not tagged yet — so a reviewer never has to hunt through the whole batch line by line to find what still needs attention.
Catching invoices that already settled
One thing that trips up almost every migration: a debtor or creditor still showing as outstanding that was, in fact, already paid off around the cutover date — the payment just hadn't been matched to the invoice yet when the listing was pulled together. The workflow can scan a bank statement against your debtors and creditors listings and flag exactly these cases before they turn into opening invoices nobody ever settles, so your reviewer resolves them once, at the source, instead of everyone chasing down a mismatch six months later. A Bank Exception Scan report does this on demand — point it at a debtors or creditors listing and a statement, and it lists each candidate match with the amount, the date gap, and the statement line it lined up against.
From your desk to your live accounts
Once a batch is submitted, it moves through a short review:
Draft → Submitted for Review → Under Review → Awaiting Sign-off → Approved → Committed
Our onboarding team reviews for consistency and sends anything that needs a correction back with a specific note on what to fix. Once it checks out, one of your own team gets the final say — a sign-off confirming the figures are correct — before we commit it into your live accounts.
The same checked-approval pattern carries into everyday use once you're live: quotations, invoices, and purchase orders move through a similar Draft → Check → Approval path, with exactly who can approve what configured around how your own team is actually structured — not a one-size-fits-all default.
Why this matters
A self-service opening balance workflow only works if the people entering figures can trust the system to catch their own mistakes before those mistakes become someone else's problem. That's the design goal here: give clients direct control over their own data entry, without giving up the guardrails that keep a migration honest.
See it filled in, not just described
We keep a permanent reference example live for a fictional hardware trader: a trial balance that balances, debtors and creditors listings, stock, a fixed asset register, a realistic mix of evidence quality (including one figure we deliberately left as a plug, so you can see how the system flags it rather than hides it), and the bank exception scan turning up two invoices that were already settled before cutover. Nothing you do there can be submitted or saved permanently — it resets on a schedule so the next visitor sees the same clean example — so feel free to click through the Line Checklist, run the Bank Exception Scan, or try changing a figure to see how the checks react.
That hardware trader is one of eighteen fictional businesses we keep running, one per industry — the rest have already gone all the way through this exact workflow and are live, transacting companies with real invoices and payments on the books, so you can see both ends of the process: a business partway through onboarding, and what it looks like once you're through it. See them all.
Get in touch for a login, or to walk through it together on a call.
Migration from Google or Microsoft included, backed up nightly.
See business email →