NetSuite Migration Reconciliation — Saved Search to Fusion, Cent-Level

netsuite migration reconciliation is the framework that proves NetSuite Saved Search exports of source-of-record balances tie to Oracle Fusion balances at every level of granularity — consolidated, per-ledger, per-subsidiary, per-book, per-period, per-account, per-transaction, per-obligation. Data validation is the per-record post-load equivalence check. Reconciliation is the higher-level framework that organizes those checks into a sign-off pyramid: bottom-level per-transaction equivalence rolls up to per-account totals, which roll up to per-period TB, which rolls up to per-subsidiary, which rolls up to per-book, which rolls up to consolidated. Syntra ETL's netsuite migration reconciliation runs the full pyramid with hash-signed evidence at every level.

Because Saved Searches are what finance already trusts. Every NetSuite finance team has built up a library of Saved Searches over years — trial balance by subsidiary, AR aging by BU, AP aging by vendor, inventory valuation by location, deferred revenue rollforward, fixed asset depreciation schedule. These Saved Searches are the canonical source-of-record reports that finance closes the month on. Reconciliation that ties Fusion to these specific Saved Search outputs is reconciliation finance can sign off on without learning a new tool. Syntra ETL's netsuite migration reconciliation engine ingests the key Saved Search outputs as CSV exports plus the underlying Saved Search SQL via SuiteAnalytics Connect — and proves Fusion balances tie row-by-row.

Six levels in a sign-off pyramid. Level 1: per-transaction equivalence (every NetSuite transaction has a corresponding Fusion record with matching key fields and hash signature). Level 2: per-account roll-up (every NetSuite GL account's debit/credit total matches the corresponding Fusion account). Level 3: per-period TB (subsidiary TB per period matches Fusion ledger TB per period). Level 4: per-subsidiary roll-up (OneWorld subsidiary TB matches Fusion Primary Ledger TB per LE). Level 5: per-book roll-up (multi-book GAAP/IFRS/Tax preserved via Secondary Ledgers). Level 6: consolidated (NetSuite consolidated parent TB matches Fusion consolidated reporting). Each level signed off independently before the level above is run.

OneWorld subsidiaries operate in their base currencies; consolidation runs in the parent's reporting currency. NetSuite stores transactional amounts in subsidiary base + transaction currency, with consolidation translation via period-end rates (closing rate for balance sheet, average rate for P&L, historical rate for equity). Fusion preserves the same model via Primary Ledger functional currency + reporting currencies + period-end translation. The netsuite migration reconciliation engine validates per transaction (entered amount + functional amount), per subsidiary (functional TB matches), per period-end translation (translated amounts match using same rate library), and per consolidated TB (parent reporting currency matches). Multi-jurisdiction subsidiaries (USD, EUR, GBP, AUD, INR) handled out of the box.

Yes — and it's typically the hardest reconciliation in any NetSuite engagement. ASC 606 deferred revenue rollforward is a standard NetSuite Saved Search: opening deferred revenue balance per period + new performance obligations + recognized revenue (decrease) = closing deferred revenue balance. The netsuite migration reconciliation engine reproduces the rollforward in Fusion Revenue Management: opening + new obligations + recognized = closing, and ties each line to the NetSuite Saved Search output. Multi-year arrangements (3-year SaaS subscription, 5-year enterprise licensing) carry through with the full recognition schedule preserved. Signed off cent-level per arrangement per period before cutover.

Saved Searches use NetSuite's SuiteQL dialect — joins via dotted-notation field paths (transaction.customer.address.country), formula columns with NetSuite functions (NSF, BUILTIN.DF), and parameter prompts. Translating to Fusion OTBI logical SQL requires resolving each dotted path through Fusion's data model. The Syntra ETL netsuite migration reconciliation engine parses each Saved Search via SuiteAnalytics Connect, resolves the field-path graph through the source-target crosswalk, and emits an equivalent OTBI logical SQL or BI Publisher data model. Both side-by-side outputs are compared row-by-row during reconciliation; any variance investigated to root cause before sign-off.

Three-tier operational cadence. Tier 1 (per load increment): five-stream data validation pack issued within 24 hours of each load. Tier 2 (weekly during parallel run): rollup reconciliation pack covering all increments in the week, with daily delta replay reconciled against Saved Search outputs. Tier 3 (per parallel month-end): full six-level pyramid reconciliation, signed off per subsidiary per book by finance owners. Internal audit reviews every tier; external auditors review tier 3 sign-off packs during interim and year-end audits. SOX retention of all three tiers is 7 years; Syntra ETL preserves them in long-term archive.

Open sales orders, open purchase orders, in-flight work orders, AR open invoices, AP open invoices and customer payments in transit need per-record equivalence: every open transaction in NetSuite at cutover date must have a corresponding Fusion record with matching status, amounts, line detail and approval state. The netsuite migration reconciliation framework runs per-transaction equivalence check + roll-up count check + roll-up dollar total check. Variances surface at the transaction level with the exact field-level reason. Common root causes: NetSuite custom workflow approvals that don't have a Fusion equivalent (route to Fusion AMX), or NetSuite fulfillment-in-progress status that needs sub-status mapping to Fusion's workflow.