Opening balance reconciliation proves that NetSuite starts from an approved financial position and that the supporting detail agrees with it. A balanced journal is necessary, but it is not sufficient: debits and credits can balance while customers, vendors, stock or currencies are wrong.
Design the reconciliation before loading data. Define the source cutoff, accounting basis, mapping version, target reports and reviewers. Then use the same controls during rehearsals and final cutover. This article describes a control method; your controller should approve the actual entries and accounting treatment.
Obtain the final trial balance and supporting schedules from the source system. Record entity, date, posting period, currency, accounting basis and report filters. Freeze a copy before transformation so later changes can be distinguished from mapping errors.
Identify adjustments still expected after the extract. Give each a reference, approver and treatment in the final migration. If source users can continue posting, define a controlled delta process. Otherwise the source and target may disagree simply because they represent different points in time.
Confirm that the source itself reconciles. A difference between the legacy receivables report and its general ledger does not disappear when both are moved. Resolve it or carry an explicitly approved reconciliation item with enough evidence for later review.
Use the approved account crosswalk to transform the source trial balance. Preserve source account identifiers even when several accounts map to one target account. For split mappings, retain the documented basis and calculation.
Include subsidiary, currency and reporting dimensions where they affect the required opening position. Do not compare a consolidated source total to an individual target entity or mix transaction-currency amounts with base-currency balances.
Produce a reconciliation bridge with source balance, approved adjustments, mapping effect, expected target and actual target. Every difference should be visible. Avoid using an unexplained “migration adjustment” to force agreement.
Decide which target records establish the opening balances. Imported invoices, bills, credits and inventory transactions may create ledger postings. A separate opening journal must complement those postings rather than duplicate them.
Oracle explains that its Opening Balances page creates journal entries. That feature does not determine the complete migration accounting design. The controller should approve how opening journals, open items and any clearing accounts interact for the chosen record types.
Reconcile accounts receivable and payable at document and counterparty level. Preserve due dates, remaining amounts and unapplied credits where needed for the future operating process. A control-account tie cannot prove that settlement will be applied to the correct document.
For inventory, compare quantity and valuation separately. Quantities should be checked by the relevant item, location and traceability dimensions. Values should follow the approved costing and opening-stock method. A matching total value can hide wrong quantities or allocation between locations.
Review fixed assets, prepaid expenses, accruals, deferred balances and other material schedules according to scope. Decide which details will operate in NetSuite and which remain in approved supporting systems. Confirm that their totals agree with the opening ledger and that ownership is clear.
For intercompany balances, verify counterparties and matching positions between entities. Investigate differences before consolidation obscures their origin. Where currencies are involved, separate source differences from translation effects.
Historical equity and consolidated reporting may require more than importing a local-currency trial balance. Oracle's OneWorld historical-balance guidance describes complications involving historical rates and different equity accounts.
Use that documentation with qualified accounting review for the group's actual structure. Do not copy an example exchange rate or journal sequence into a different situation. Validate both entity-level results and the intended consolidated presentation after the approved method is applied.
Record the exchange-rate sources and assumptions used in the reconciliation. A future reviewer should be able to distinguish an intentional translation treatment from an accidental rate mismatch.
Assume an approved source trial balance includes 40,000 in receivables, represented by open customer documents totaling the same amount. In a hypothetical migration design, importing those documents creates the 40,000 receivable balance in NetSuite.
If a separate opening journal also debits receivables by 40,000 without an offsetting design, the target receivable can become 80,000. The journal may still balance because another account received the credit. This is why a balanced trial balance does not establish a correct migration.
The controller designs the complete posting approach, then tests the combined effect. The accepted result is a 40,000 control balance with the intended open documents and an explained treatment of any migration clearing accounts. The exact entries depend on the approved record and conversion method.
First check scope: are source and target using the same cutoff, entity, basis and currency? Next check completeness: did every intended record load, and were any records duplicated? Then check mappings, signs, periods and exchange rates. Finally inspect record-specific behavior and approved adjustments.
This sequence reduces unnecessary rework. A report filter mismatch should be corrected in the comparison before anyone edits transactions. Keep each finding linked to the affected records and the approved correction.
After correction, rerun the relevant controls and record the new evidence. Do not overwrite the original discrepancy report without preserving its relationship to the resolution.
The reconciliation pack should include source reports, mappings, batch references, target reports, adjustment approvals and unresolved items. Name the preparer and independent reviewer where appropriate to the organization's controls.
Use explicit acceptance criteria: all material balances explained, supporting populations complete, approved tolerances met and remaining items assigned. Small unexplained differences should not be dismissed solely because their net total is low.
Before go live, have the controller approve the opening position and operational owners confirm that open documents can be used. Retain the package for the first close and subsequent audit requests. A well-reconciled opening position gives the team a dependable starting point for every report that follows.