Pre-built majesco / sapiens data validation for Oracle Fusion loads — row counts, sum totals, hash signatures, business-key integrity, FBDI validation status, reserve evidence. Signed reconciliation pack per close period for statutory and GAAP sign-off across P&C and L&A.
Loading data into Fusion is half the job. Proving it landed correctly — to statutory accounting, GAAP accounting, actuarial, reinsurance and the state insurance commissioner — is the other half. Most projects underbudget this layer 5x.
Statutory accounting will not sign off on a Fusion close until they can see signed proof that source data tied out to target. Source premium ledger from Majesco Policy module or Sapiens IDITPOL has to equal Fusion revenue to the cent. Source paid-loss from Majesco Claims or Sapiens IDITCLM has to equal Fusion paid-loss GL to the cent. Source ceded-recovery from Majesco Reinsurance or Sapiens ReinsuranceMaster has to equal Fusion ceded GL to the cent. Without that signed reconciliation, the close is blocked.
Most consultant-led projects produce reconciliation in Excel — pivot tables manually assembled from source extracts and Fusion exports, with variances investigated by email. This works for the first month and falls apart by month three when the team that built the spreadsheets has moved on and the next month's variance investigation has no reproducible workflow. State-commissioner market-conduct exams arriving 2-5 years post-cutover then find no chain-of-custody and the response becomes a six-week consultant reconstruction project.
Syntra ETL's majesco / sapiens data validation layer is built to deliver a signed reconciliation pack per close period automatically — counts, sums, hashes, business-key integrity, FBDI status, reserve evidence, chain-of-custody log — so statutory and GAAP accounting sign off in hours, not weeks, and so future state-commissioner audits resolve in queries, not reconstructions.
Each dimension is automated, signed and time-stamped. The output is a reconciliation pack ready for statutory and GAAP sign-off.
Source row count per entity per period vs Fusion target row count per entity per period. Mismatches flag with specific records contributing to the variance.
Written premium, earned premium, paid loss, paid expense, ceded premium, ceded recovery, commission per LOB per legal entity per period — source vs target to the cent.
SHA-256 per-record hashes computed at source extract and recomputed post-Fusion-load. Any drift surfaced with record-level diagnostic.
Every Fusion journal line, AP invoice and AR receipt traces back to source Majesco/Sapiens policy/claim/transaction via preserved business keys — no orphans.
Every Oracle Fusion ESS job completes cleanly with zero validation errors. Any error logged with row-level diagnostic for resolution before sign-off.
Per-claim reserve history (case + IBNR) preserved as evidence metadata on downstream Fusion records for Schedule P loss-development triangle and L&A AAA substantiation.
From data freeze to signed reconciliation pack in hours. Automated, repeatable, version-controlled.
Every record passes schema, lookup-code, segment and business-rule validation before being written to FBDI ZIP. Errors surface locally with row-level diagnostics — never in a 4-hour Fusion ESS job.
FBDI ZIPs submitted to Fusion ESS, monitored to completion. Any ESS validation error captured with row-level diagnostic for immediate resolution.
Fusion target row counts and sum totals pulled via REST APIs. Compared against source counts and totals per entity per period per LOB per legal entity.
Per-record hashes recomputed against Fusion target. Business-key integrity verified — every Fusion record traces back to source via preserved keys.
Per-claim reserve history (case + IBNR) cross-checked between source Claims module and Fusion paid-loss + reserve liability. Schedule P loss-development triangle reconstructed from archive.
Hash-signed reconciliation pack emitted per close: per-entity per-period reconciliation, exception list, source-system query snapshots, chain-of-custody log. Delivered to statutory and GAAP accounting for sign-off.
Hash-signed evidence ready for sign-off, audit and state-commissioner exam response.
Written premium, earned premium and unearned reserve per LOB per legal entity per period — Majesco/Sapiens source vs Fusion target — to the cent with hash signatures.
Indemnity + expense + recovery payments per coverage per claim per period — Claims module vs Fusion paid-loss GL — Schedule P aligned.
Daily cash receipts vs Fusion AR cash application per bank account — full daily cash tie-out for the cutover window and ongoing close.
Ceded premium and ceded loss recovery per treaty per layer — bordereaux register vs Fusion ceded GL — for standard reinsurance audit horizons.
Every reserve change preserved as evidence metadata — actuarial loss-development triangle reconstructible from archive for Schedule P and L&A AAA substantiation.
Per-record signed chain: source extract → transform → FBDI ZIP → ESS job → post-load hash. State-commissioner exam response in queries, not reconstructions.
Majesco / sapiens data validation is the post-load reconciliation layer that proves the data that left Majesco P&C/L&A Core Suite or Sapiens IDITSuite/CoreSuite/ALIS landed in Oracle Fusion Financials correctly — every premium amount, every paid-loss payment, every reserve change, every reinsurance cession, every claimant supplier and every L&A deferred-premium contract. Statutory accounting will not sign off on a Fusion close until they can see a signed reconciliation pack: source premium ledger vs Fusion revenue to the cent, source paid-loss vs Fusion paid-loss GL to the cent, source ceded-recovery vs Fusion ceded GL to the cent. The validation layer produces that pack automatically — it isn't a quarter of consultant time in Excel.
Six dimensions per load. (1) Row counts: source row count per entity per period matches Fusion target row count. (2) Sum totals: written premium, earned premium, paid loss, paid expense, ceded premium, ceded recovery, commission disbursement per LOB per legal entity per period match to the cent. (3) Hash signatures: per-record hashes computed at source and recomputed post-load match. (4) Business-key integrity: every Fusion journal line traces back to its originating Majesco policy or Sapiens claim via preserved business keys. (5) FBDI validation status: every Oracle Fusion ESS job completes cleanly with zero validation errors. (6) Reserve evidence: per-claim reserve history (case + IBNR) preserved as evidence metadata on the downstream Fusion record for Schedule P substantiation.
Three engines. (1) Pre-load validation: every record passes through schema validation, lookup-code validation, segment-validation and business-rule checks before being written to FBDI ZIP. Errors surface locally with row-level diagnostics — not in a 4-hour ESS job that fails on row 200,000. (2) Post-load reconciliation: after FBDI submission and ESS completion, the engine pulls Fusion target counts and totals via REST APIs and compares against source counts and totals. Mismatches are flagged with the specific records contributing to the variance. (3) Signed reconciliation pack: a hash-signed report is emitted per load with per-entity per-period reconciliation, exception list and source-system query snapshots so auditors can verify independently.
P&C validation focuses on premium and paid-loss tie-out per LOB per state per legal entity, with Schedule P loss-development triangle alignment for actuarial substantiation. L&A validation adds deferred-premium recognition tie-out, surrender-value calculation reconciliation, dividend-distribution accuracy, NAIC #797 replacement-record completeness, 1099-R distribution-report alignment for year-end IRS reporting, and cash-value tracking accuracy for participating policies. Both share the reinsurance ceded validation layer (treaty cession, facultative placement, bordereaux extract reconciliation) and the claimant/policyholder supplier matching layer. The validation pack is structured to deliver a P&C section and an L&A section separately for the respective accounting and actuarial sign-off owners.
Three error categories with different paths. (1) Pre-load errors (schema, lookup, segment, business-rule): surfaced locally with row-level diagnostics; fixed in mapping or source-system data; record re-staged and re-validated. (2) Post-load reconciliation variances (sum mismatch, count mismatch): variance investigation pulls the specific records contributing to the gap, identifies root cause (rounding, transaction-date boundary, custom-rule output drift, source-system delta arrived post-extract), and resolves by replay or mapping fix. (3) Business-key integrity failures (Fusion record can't trace back to source): typically indicates source-system data quality issue (missing policy ID, NULL claim number); resolved by source-system data cleanup before re-extract. Every error is logged in the validation pack with resolution evidence.
Reserve history is the actuarial substantiation backbone. The validation layer carries every reserve change (case + IBNR) from Majesco Claims module or Sapiens ClaimsMaster as evidence metadata on the downstream Fusion paid-loss journal line — initial reserve, every adjustment with timestamp and user, every reserve close. The post-load reconciliation cross-checks per-period reserve totals per LOB per coverage between source (Claims module reserve register) and Fusion (paid-loss GL + reserve liability). Schedule P loss-development triangle reconstruction is run on the archive to confirm actuarial integrity. For L&A, equivalent reserve adequacy and assumption-history is validated for Asset Adequacy Analysis (AAA) and VM-20 PBR substantiation.
Yes. The validation pack includes a signed chain-of-custody log per record: source extract timestamp, source extract hash, source-system query snapshot, transform timestamp, transform version, FBDI ZIP hash, ESS job ID, post-load reconciliation timestamp, post-load hash. When a New York DFS, California DOI or Texas DOI market-conduct exam team requests substantiation of a historical premium calculation, paid-loss payment or reinsurance cession, the response is a query against the validation log producing the signed chain in minutes — not a six-week consultant reconstruction. The log retention period matches the longest applicable state-retention rule (typically 10-30+ years per LOB per state).
For daily incremental loads: 5-15 minutes per load (extract, transform, load, validate, reconcile, emit pack). For monthly close reconciliation across all P&C and L&A LOBs: 1-2 hours from data freeze to signed pack. For year-end reconciliation including Schedule P loss-development triangle alignment and L&A 1099-R distribution-report alignment: 4-8 hours. Compared to consultant-led monthly reconciliation in Excel (typically 1-3 weeks per close) the time savings come from automated counts/sums/hash/business-key validation and pre-built per-entity reconciliation logic. The signed pack lands in statutory and GAAP accounting inboxes without manual assembly.
Book a 30-minute discovery call. We'll walk through your Majesco/Sapiens module footprint, your statutory and GAAP ledger requirements across P&C and L&A, your reinsurance treaty structure and your state-commissioner exam history — and propose a concrete data-validation plan with reconciliation pack design.