The everyday problem
Moving opening balances requires an agreed cut-off and a clear mapping between old and new account records. Treat it as a reviewed handover rather than another spreadsheet to load alongside the item list.
A workable process
Prepare the source report for the chosen date and identify the accounts being migrated. Have the responsible accounts person confirm the values and account mapping. After using the supported import or entry workflow, compare the resulting records with the approved source, including signs and account identity.
A practical example
Two suppliers can have similar trading names. Mapping a balance to the wrong account may leave a grand total unchanged while the individual ledger is wrong. Party-by-party checks help expose an error that a total-only comparison cannot detect.
Before you finish
Keep the signed-off source and import file, and agree which transactions belong before or after the cut-off. Avoid entering later payments before the team has confirmed how the opening position was loaded.
Try this check with your team
Select five parties with different positions, including a customer owing money and a supplier due for payment. Compare each imported balance and direction with the approved cut-off list, then reconcile the total and review any bill-wise opening requirements.
What the result tells you
A matching grand total can conceal offsetting party errors. Sign off representative records as well as the aggregate, and preserve the approved source so later queries can distinguish opening-data issues from new transactions.
See this workflow in Speed Plus.
Bring a sample transaction and your questions to a product demo.
Book a free demo ↗