Glossary
Quick definitions of key terms
Setup & configuration
An ERPNext cutover you can prove
Opening balances are not a data-entry task. They are the moment the new system either inherits the credibility of the old one or loses it. This guide covers the order that keeps the trial balance provable at every stage.
How do I load opening balances into ERPNext?
Pick a cutover date at a period boundary, freeze the old system, then load in dependency order: masters, then open receivables and payables item by item, then stock quantity and valuation, then a single balancing journal for everything remaining. Reconcile after each stage rather than at the end, because a difference found after the last load can originate anywhere.
Before you start
- A signed-off trial balanceFrom the old system as at the cutover date, agreed by whoever owns the accounts.
- Open item listingsReceivables and payables broken down by document, not just totals — you need the individual invoices to age correctly.
- Stock valuation reportQuantity and value by item and warehouse as at the same instant as the trial balance.
- A completed chart of accountsAccount types set, company defaults filled in. Loading balances into an unfinished ledger means loading them twice.
- A test environmentDo the whole cutover once in a copy before doing it for real. The rehearsal is where you find the surprises.
The order that stays reconcilable
Choose the date and freeze behind it
Pick the end of a period, never mid-month. From that instant the old system is read-only for postings. If people keep transacting in it, the reconciliation you do tomorrow describes a position that no longer exists.
Decide how much history to carry
Balances only is the least work and is enough for statutory continuity. Carrying full transaction history is possible but multiplies effort and risk. The usual middle ground is balances plus the current financial year's transactions, with earlier years left in the old system and archived.
Load master data and check it before any balance
Customers, suppliers, items, warehouses. Every opening balance attaches to a master record, so a missing or duplicated master becomes a misposted balance.
Where Data Import
Load open receivables and payables document by document
Post each outstanding invoice as an opening entry against the party, carrying its original date and reference. Loading a single net figure per party destroys ageing and makes collections useless from day one.
Use the temporary opening account as the contra so these entries stay identifiable.
Load stock with quantity and valuation together
Stock entered without a value posts nothing to the ledger, so inventory and accounts stop agreeing before you have even started. Use the opening stock entry so quantity and value land at the same moment.
Where Stock > Stock Reconciliation
Post one balancing journal for the remainder
Everything not covered above — bank, fixed assets, equity, reserves, tax balances — goes in as a single dated journal against the opening account. One entry is easier to review and to reverse than twenty.
Clear the temporary opening account to nil
If it does not clear, something has been loaded twice or missed. A non-zero opening account is the single most reliable signal that the cutover is not finished.
Run parallel for one period if the risk warrants it
For a business where a wrong number has consequences beyond inconvenience, run both systems for one full cycle and compare the closing position. It costs a period of duplicated effort and removes most of the argument about which system is right.
Where cutovers go wrong
A moving cutover date
Balances extracted on one date and stock counted on another cannot be reconciled to each other, and no amount of adjustment makes the difference explainable.
Net balances per party
Loading one figure per customer loses the invoice-level detail that ageing, collections and reconciliation all depend on.
Stock quantity without valuation
The warehouse looks right and the ledger does not move. The gap is usually found weeks later, at close.
Skipping the rehearsal
The first attempt always surfaces something — a missing master, a rounding difference, an account type set wrongly. Better that it surfaces in a copy.
Letting the old system stay open
One helpful person posting a late invoice in the old system after the freeze invalidates the reconciliation without anyone noticing.
Proving the cutover
- The temporary opening account has a nil balance.
- The ERPNext trial balance agrees line for line with the signed-off trial balance from the old system.
- Receivables and payables ageing in ERPNext matches the open item listings, by document and by bucket.
- Stock value in the Stock Balance report equals the stock account balance in the general ledger.
- A sample of individual invoices can be traced from ERPNext back to the original document in the old system.
- Whoever signs the accounts has seen the comparison and accepted it in writing.
Questions people ask
Yes, and many do. Pick a period end, carry the year-to-date position as opening balances, and keep the old system available read-only for the comparatives your auditor will ask about.
Only if there is a concrete reason, such as needing item-level history for warranty or traceability. It multiplies the migration effort and the number of things that can be subtly wrong, and the statutory record lives in the old system either way.
Stop and find it rather than posting a plug. A difference at this stage is a symptom of something loaded twice, loaded to the wrong account type, or missed entirely, and all three get harder to trace once live transactions sit on top.
Read-only for as long as you need comparatives and audit evidence, which in practice usually means through the next statutory audit. Keep an exported copy independent of the software licence.
This guide covers ERPNext configuration and migration practice. It is not accounting, audit or tax advice, and it does not determine how your opening position should be presented in statutory accounts.
Related guides
Cutting over soon?
The reconciliation plan matters more than the data load. Tell us your cutover date and what you intend to carry, and we will tell you where it usually breaks.
Talk it through