Pre-built majesco / sapiens migration reconciliation framework for Oracle Fusion cutover and ongoing close. Premium, paid-loss, cash, ceded and reserve registers reconciled per close period with hash-signed evidence across P&C and L&A.
Insurance reconciliation isn't a row-count check. It's a per-LOB, per-state, per-period proof that written/earned/unearned premium, paid-loss, ceded recoveries and reserve history all tie out — and that the chain back to source survives 30+ years.
Most ERP migration reconciliation projects produce a one-page summary: source rows = target rows, source total = target total, done. Insurance migration reconciliation can't operate that way. Premium ledger doesn't equal revenue — it splits into written, earned and unearned with different Fusion GL accounts and different recognition cadences. Paid-loss has to align with Schedule P loss-development triangle for NAIC statutory filing. Reserve history (case + IBNR) has to reconcile per claim per period for actuarial Asset Adequacy Analysis (AAA). Reinsurance ceded reconciliation has to tie bordereaux to source policies and claims across 30+ year horizons for long-tail liability.
Without a structured framework, mid-market insurers end up with consultant-built Excel pivot tables that work for the first close and fall apart by the third. State-commissioner market-conduct exams arriving 2-5 years post-cutover then find no signed reconciliation chain and the response becomes a six-week reconstruction project at consulting rates.
Syntra ETL's majesco / sapiens migration reconciliation framework delivers five hash-signed registers per close period — premium, paid-loss, cash, ceded and reserve evidence — automated, version-controlled and retained indefinitely in the long-term archive so future state-commissioner queries resolve in minutes, not weeks.
Each register is automated, hash-signed and retained for the longest applicable state-retention rule. Sign-off is by statutory accounting, GAAP accounting and actuarial.
Written, earned, unearned premium per LOB per legal entity per period — source Policy module vs Fusion revenue + unearned liability — to the cent. Written/earned/unearned split honored per LOB.
Indemnity + expense + recovery payments per coverage per claim per period — source Claims module vs Fusion paid-loss GL — Schedule P loss-development triangle aligned for NAIC statutory.
Daily cash receipts per bank account — source Billing module vs Fusion AR cash application — full daily tie-out for cutover window and ongoing close cycles.
Ceded premium and ceded loss recovery per treaty per layer — source Reinsurance bordereaux vs Fusion ceded GL — preserved for 30+ year long-tail liability audit horizons.
Per-claim reserve change history (case + IBNR) preserved as evidence metadata on Fusion paid-loss records and in archive — actuarial loss-development triangle reconstructible for Schedule P and L&A AAA.
Per-record signed chain: source extract → transform → FBDI ZIP → ESS job → post-load hash. Retained for longest state-retention rule (typically 10-30+ years per LOB per state).
From initial bulk load through cutover to long-term archive retention. Structured, automated, signed.
Initial bulk extract of historical Majesco/Sapiens data reconciled to source: counts per entity per period, sum totals per LOB per legal entity, hash signatures per record. Variances investigated and resolved before parallel run.
Source vs legacy integration target vs Syntra ETL target reconciled per close period. Variances between legacy and Syntra investigated and root-caused. Once clean for 1-2 close cycles, statutory + GAAP sign off.
Final delta replay reconciled to source. Cutover-cut-off cleanly captured in chain-of-custody log. Legacy integration retired. Production cut to Syntra pipeline.
Daily reconciliation for first 30 days post-cutover with elevated review cadence — premium, paid-loss, cash, ceded and reserve evidence checked against source daily.
Standard per-close reconciliation: five registers hash-signed and emitted within 1-2 hours of data freeze. Quarterly Schedule P loss-development triangle reconstruction for actuarial sign-off.
Per-close reconciliation packs retained in long-term archive partitioned by close period and LOB. State-commissioner market-conduct exam queries resolve in minutes from archive — no consultant reconstruction.
When reconciliation flags a variance, the framework categorizes, drills down and routes to resolution. No more manual Excel investigation.
Sub-cent variances auto-accepted within configured tolerance threshold. Logged for transparency. No human investigation required.
End-of-period crossover variances (transaction-date vs accounting-date drift) auto-categorized; fixed in mapping; record re-staged and re-validated.
Rate Manager or RuleXpress rule output drift (e.g., schedule-rating-credit changed mid-period) flagged with source rule version; decoding logic updated; re-validated.
Source-system delta arrived post-extract; auto-detected by modified-since watermark; record replayed and re-reconciled.
Missing policy ID, NULL claim number, orphaned premium transaction in source — escalated to source-system data owners; resolution evidence logged in reconciliation pack.
Every variance and resolution logged in the reconciliation pack with timestamp, owner and resolution evidence. Auditors verify resolution path independently.
Majesco / sapiens migration reconciliation is the structured framework that proves every Majesco P&C/L&A Core Suite or Sapiens IDITSuite/CoreSuite/ALIS source record was correctly migrated into Oracle Fusion Financials — at row level, sum level and hash level — and that any variance is identified, root-caused and resolved before sign-off. It is wider than data validation (which is per-load) because it covers the full migration arc: initial bulk load reconciliation, parallel-run reconciliation across 1-2 close cycles, cutover-day reconciliation, post-cutover stabilization reconciliation and the multi-year historical archive reconciliation. Statutory accounting, GAAP accounting and actuarial all consume the reconciliation framework output.
Six reasons specific to insurance. (1) Premium ledger doesn't equal revenue — it equals written premium, of which only the earned portion is revenue, with unearned reserve as liability. Reconciliation has to honor the written/earned/unearned split per LOB per period. (2) Paid-loss has to align with Schedule P loss-development triangle for NAIC statutory filing. (3) Reserve history (case + IBNR) has to reconcile per claim per period for actuarial AAA substantiation. (4) Reinsurance ceded reconciliation has to tie bordereaux to source policies and claims across 30+ year horizons. (5) L&A deferred premium has its own recognition cadence and 1099-R reporting alignment. (6) State-of-admission spread means reconciliation runs per legal entity per state — not just per company.
Five outputs per close period. (1) Premium register reconciliation: written, earned and unearned premium per LOB per legal entity per period — Majesco/Sapiens source vs Fusion target — to the cent with hash signatures. (2) Paid-loss register reconciliation: indemnity + expense + recovery payments per coverage per claim per period — Schedule P aligned. (3) Cash register reconciliation: daily cash receipts vs Fusion AR cash application per bank account. (4) Ceded register reconciliation: ceded premium and ceded loss recovery per treaty per layer — bordereaux register vs Fusion ceded GL. (5) Reserve history evidence: per-claim reserve change history preserved for Schedule P and L&A AAA. All five outputs are hash-signed for statutory and GAAP sign-off.
During parallel run (typically 1-2 close cycles), the legacy Majesco/Sapiens → Fusion integration continues feeding Fusion alongside the new Syntra ETL pipeline. The reconciliation framework runs three-way: source (Majesco/Sapiens) → legacy integration target (Fusion records loaded by legacy path) → Syntra target (Fusion records loaded by Syntra path). Any variance between legacy and Syntra Fusion records is investigated and root-caused — typically the variance traces to a mapping difference, a custom-rule-output decoding difference or a transaction-date boundary handling difference. Once 1-2 close cycles run clean (zero variance between legacy and Syntra), statutory and GAAP accounting sign off and the legacy integration is retired.
Schedule P is the NAIC P&C statutory filing that requires loss-development triangles per LOB per accident year showing cumulative paid losses and case+IBNR reserves at each evaluation date. The reconciliation framework reconstructs the loss-development triangle from the migrated reserve history (preserved as evidence metadata on Fusion paid-loss records and in the archive) and compares against the same triangle reconstructed from the source Majesco/Sapiens Claims module. Any cell-level variance in the triangle is flagged with the specific reserve changes or paid-loss payments contributing to the gap. Actuarial signs off on the triangle alignment before the Schedule P filing is generated from Fusion data.
L&A reconciliation adds five layers on top of P&C. (1) Deferred premium recognition: per-contract per-performance-obligation recognition reconciliation between ALIS source and Fusion Revenue Recognition target. (2) Cash value tracking: per-policy cash value at each policy anniversary reconciled between source and archive. (3) Dividend distribution: per-policyholder dividend payment reconciled between source ALIS, Fusion AP and 1099 reporting. (4) Surrender values: per-policy surrender value calculation reconciled at surrender event. (5) NAIC #797 replacement records: per-replaced-policy record completeness verified for state-commissioner exam response. The framework delivers an L&A reconciliation section separate from the P&C section so the respective accounting and actuarial sign-off owners can review independently.
Three-tier investigation workflow. (1) Auto-categorization: variance flagged with category — rounding (sub-cent), transaction-date boundary (end-of-period crossover), custom-rule output drift (Rate Manager / RuleXpress rule output differs), source-system late delta (record arrived post-extract), source data quality issue. (2) Drill-down: specific records contributing to the variance pulled with source and target snapshots side-by-side. (3) Resolution: rounding variances accepted with tolerance threshold; date-boundary issues fixed in mapping; custom-rule drift fixed in decoding logic; late deltas replayed; source data quality issues escalated to source-system data owners. Every variance and resolution is logged in the reconciliation pack with evidence so auditors can verify the resolution path independently.
Indefinitely for the multi-year archive — and per the longest state-commissioner retention rule for the per-close reconciliation packs. New York indefinite for L&A. New York 6 years for P&C. Texas 10 years. Reinsurance ceded layers stretch retention 30+ years for long-tail liability. The reconciliation framework retains per-close packs hash-signed in the long-term archive partitioned by close period and LOB, so state-commissioner market-conduct exams arriving 5-15 years post-cutover can query the reconciliation pack for any historical close period in minutes — not weeks of consultant reconstruction.
Book a 30-minute discovery call. We'll walk through your Majesco/Sapiens module footprint, your statutory + GAAP + actuarial sign-off owners, your Schedule P and L&A AAA requirements, and your state-commissioner exam history — and propose a concrete reconciliation framework with five-register design.