Final balance migration is validated by freezing an agreed migration key date, reconciling legacy control totals to the balances created in SAP, checking the relevant accounting dimensions and open items, explaining every material variance, and obtaining accountable Finance sign-off. A technically successful migration load is only one step in that control chain.
Start with the migration key date and source control totals
Before the final load, the team needs a controlled source population. Finance should know which company codes, ledgers, accounts, currencies and open-item populations are included as of the migration key date. The source totals used for reconciliation must be retained as evidence. If the source keeps changing while validation is in progress, a target variance may be caused by timing rather than a migration defect.
Validate the target at the same level of detail
A total company balance can agree while important sub-ledger or account-level errors remain hidden. Reconcile at the level required by the design: for example ledger, company code, G/L account and currency, then add customer, supplier or other dimensions where the migration scope requires them. SAP documentation for reconciliation activities emphasizes matching opening balances and open items using defined accounting assignments rather than relying only on a single grand total.
Migration clearing accounts should explain the bridge
SAP's migration documentation describes posting logic in which migrated accounting records create balanced accounting documents and migration clearing accounts act as the offset during transfer. A key control is that the intended migration clearing accounts resolve as expected after the complete load population is processed. A remaining balance should be investigated and explained, not ignored because individual documents posted successfully.
Open items need their own consistency checks
Customer, supplier and open-item-managed G/L accounts require more than a balance comparison. The sum of relevant open items should support the corresponding opening balance at the agreed key date, subject to the chosen migration design. SAP Help describes reconciliation checks that compare opening balances with the total of open items for open-item-managed accounts. This is why the team should retain both balance evidence and detailed open-item evidence.
Every variance needs an owner and a disposition
Some differences may be legitimate—for example a documented late source posting handled by an approved delta process. Others indicate an extraction, transformation, mapping, currency or load problem. The variance log should state the amount, dimension, cause, correction or acceptance decision, owner and sign-off. “Explained” means someone can trace the difference to evidence and an approved treatment.
Use rehearsals to make final reconciliation predictable
Mock loads should prove the extraction logic, transformation rules, load sequence and reconciliation workbook before go-live weekend. The final cutover is not the time to invent the control method. Rehearsals should establish who produces the source totals, who runs migration, who executes target reports, who investigates differences, and what evidence is required before the go/no-go decision.
What a strong sign-off pack contains
A practical sign-off pack normally includes the migration key date, source extracts or control reports, target reports, reconciliation worksheets, variance explanations, migration-job evidence and named approvals. The exact documents differ by organization and regulatory context, but the principle is stable: an independent reviewer should be able to understand what population was moved, what target result was expected, what differences remained and who accepted them.
Example: the total agrees but one currency does not
Suppose the company-code total matches the legacy source in local currency, but one group-currency balance is wrong. That is not a clean reconciliation. The team should isolate the affected accounts and postings, confirm the migration object's currency treatment and mapping, correct or explain the variance, rerun the relevant reconciliation and retain the evidence. Aggregate agreement cannot compensate for a material dimensional mismatch.
Read next
Continue with How Final Master Data Loads Are Planned, How Open Transactions Are Handled During Cutover, What a Mock Cutover Is and How a Cutover Plan Is Built. Return to the Consulting & ERP Projects hub.