Field-level duck creek to oracle fusion data mapping for Policy, Billing, Claims, Reserves and Reinsurance. Multi-state ratebook complexity, treaty cession rules, commission structures all captured as governed crosswalks. Signed off by controller, chief actuary and chief reinsurance officer.
Duck Creek's P&C-native data model has no clean analog in a general-purpose ERP. The mapping is the place where insurance reality meets Fusion's AR/AP/GL shape.
Duck Creek Technologies, taken private by Vista Equity Partners and Apax Partners in 2023, presents a P&C-native data model that is alien to anyone whose ERP experience is rooted in distribution, manufacturing or services industries. Policy is not a customer order — it is a contract with a term, transactions (bind, endorsement, cancellation, reinstatement, renewal) and transaction details that each carry premium and commission implications across a daily-pro-rata or 24ths-method earning curve. Claim is not an expense — it is a claim with one or more features (one per coverage involved in the loss), each with its own indemnity reserve, LAE reserve, paid history, salvage history and subrogation history. Treaty is not a contract terms record — it is a cession engine that consumes premium and loss transactions and produces ceded premium and loss-ceded entries per its proportional, excess-of-loss or facultative configuration.
Duck creek to oracle fusion data mapping has to bridge all of that to Fusion's AR Invoices, AP Invoices and GL Journals without losing the insurance-finance integrity that NAIC, state DOI, external auditors and the carrier's own actuarial team depend on. The mapping is the most important artifact in the whole integration project. Get the mapping wrong and the integration build is wasted; get the mapping right and the build becomes mechanical configuration.
Syntra ETL approaches duck creek to oracle fusion data mapping as a structured field-level exercise. Every Duck Creek attribute on every Duck Creek entity gets an explicit decision — Fusion field, Fusion DFF, insurance-finance translation rule input, or audit-layer-only. The decisions are captured as governed crosswalk tables with named owners and signed-off versions. The Syntra insurance-finance translation engine reads those crosswalks directly as configuration, so what the controller signs is what the integration runs.
Each crosswalk is a governed table with named owners and signed-off versions. The engine reads crosswalks directly — no hand-coded mapping logic.
Every Duck Creek LOB code (personal auto, homeowners, commercial property, GL, workers' comp, specialty marine, etc.) mapped to a Fusion COA product-line segment.
Every state code mapped to its Fusion ledger or COA state segment per the carrier's multi-state operating model and NAIC reporting structure.
Each treaty mapped to a Fusion supplier (for ceded premium AP) and a Fusion customer (for recoverables AR), with cession rule captured as engine configuration.
Producer registry mapped to Fusion AP supplier parent-child hierarchy. Commission types (base, override, contingent, bonus) mapped to AP invoice categories.
Case reserve, IBNR, LAE reserve, unearned-premium reserve, ceded-loss reserve each mapped to dedicated Fusion GL accounts per NAIC Annual Statement structure.
State-specific surcharges, policy fees, premium taxes, FAIR Plan and JUA assessments mapped to their NAIC-correct GL accounts and state-tax liability accounts.
A repeatable per-domain mapping workflow with explicit sign-off gates between domains.
Fusion enterprise structure walkthrough — ledgers, BUs, COA segments, currencies, cross-functional flexfields. Proposed COA structure from the assessment reviewed and finalized. Master crosswalks (state, currency) populated.
Policy header, term, transaction, transaction detail mapped to Fusion AR Invoice + GL. Earned-premium calculation rule captured. LOB → COA crosswalk signed off. Controller and AR lead sign off.
Account, premium-due, payment receipt, NSF, write-off, return premium mapped to Fusion AR + Receipt. Account-level reconciliation rule captured. AR lead and treasury sign off.
Claim, claim feature, indemnity, LAE, case reserve, IBNR, salvage, subrogation mapped to Fusion AP + GL. Reserve roll-forward rule captured. AP lead, chief actuary and head of internal audit sign off.
Treaty registry, cession calculations, ceded premium, recoverables mapped to Fusion AR + AP. Producer commission structures mapped. Chief reinsurance officer, chief actuary, controller and AP lead sign off.
Final consolidated mapping document signed by full steering. Crosswalk tables loaded into the Syntra insurance-finance translation engine. Engine configuration validated against sample extracts. Integration build proceeds against signed-off mapping.
The signed artifact handed off to the integration build team.
400–2,400 rows. Every Duck Creek attribute mapped to Fusion field, Fusion DFF, translation-rule input or audit-only with explicit decision rationale.
LOB, state, treaty, producer, claim-feature, reserve-type, surcharge, fee, tax — each as a governed table with sign-off owner.
Earned-premium calculation, cession calculation, salvage/subrogation reversal, commission calculation — captured as engine configuration parameters.
Per-domain sign-off with named owner, date, version. Re-sign-off triggered by any change to the mapping post-go-live.
What Duck Creek context is retained for lineage even when not posted to Fusion — claim narrative, treaty terms, policy notes.
Per-domain test cases for the integration build — sample transactions, expected Fusion postings, expected reconciliation outcomes.
Duck creek to oracle fusion data mapping is the field-by-field crosswalk that turns Duck Creek's insurance-core data model into Fusion's AR, AP and GL data model without losing statutory accounting integrity. The Duck Creek source side includes Policy (header + term + transaction + transaction detail), Account (the billing aggregator), Claim (with one or more claim features per loss), Reserve (case and IBNR per claim feature), and Treaty (with proportional, excess-of-loss and facultative cession configurations). The Fusion target side is AR Invoices tied to Customer Accounts and Receivables Distributions, AP Invoices tied to Suppliers and Payables Distributions, GL Journals with full COA segment coding, plus DFFs preserving insurance audit context. Duck creek to oracle fusion data mapping makes every Duck Creek field reach its right home on the Fusion side, with the right insurance-finance translation in between.
Field-level. Every attribute on every Duck Creek entity has an explicit decision: maps to a Fusion field, maps to a Fusion DFF, drives an insurance-finance translation rule, or is retained in the integration audit layer for lineage but not posted to Fusion. The mapping document is typically 400–800 rows for a single-deployment single-line carrier and 1,200–2,400 rows for a hybrid multi-line carrier with complex reinsurance. Common explicit mappings include Duck Creek policy term effective date → Fusion AR Invoice transaction date with policy-period DFFs, Duck Creek line-of-business code → Fusion COA product-line segment via crosswalk, Duck Creek claim-feature coverage type → Fusion AP Invoice expense category via crosswalk, Duck Creek treaty cession percentage → Fusion AR Invoice amount via cession calculation rule. No field is left implicit.
Controller (for GL coding integrity), AR lead (for premium-receivable mapping), AP lead (for claim-payment and reinsurance-cession mapping), chief actuary (for reserve mapping), chief reinsurance officer (for treaty cession mapping), head of statutory reporting (for NAIC and state-DOI lineage), data architect (for technical execution feasibility). Sign-off is per-domain rather than monolithic — the policy mapping signs off first, then billing, then claims, then reserves, then reinsurance — so the integration build can start on signed-off domains while later domains are still in design review. Without proper sign-off, mapping decisions get re-litigated during testing and the project slips. Syntra ETL's duck creek to oracle fusion data mapping process uses a structured sign-off workflow with explicit decision records to prevent this.
Yes. The mapping is built against the canonical event schema that Syntra ETL's extractor produces — which itself normalizes events across OnDemand REST APIs and Platform DCSB/SQL surfaces. So the mapping does not have to be done twice for hybrid carriers. The canonical schema is documented and stable across Duck Creek upgrades — OnDemand API minor version bumps and Platform release upgrades are absorbed by the extractor layer, not by the mapping. This insulation is critical for long-tenured estates: a carrier running Platform 8 today migrating to Platform 9 next year, or migrating from Platform to OnDemand over a 24-month transition, does not have to redo the duck creek to oracle fusion data mapping each time. The mapping is done once and remains stable through Duck Creek estate evolution.
Through governed crosswalk tables. Duck Creek runs state-specific ratebooks with state-specific surcharges, fees, taxes and assessments — many of which post to specific NAIC Annual Statement Page 14 columns or state DOI premium-tax fields. The mapping crosswalk explicitly captures each ratebook component to its Fusion COA destination: base premium to product-line + state segments, individual surcharges to dedicated revenue accounts or DFFs depending on NAIC treatment, fees to fee revenue accounts, premium taxes to a state-tax liability account, FAIR Plan and Joint Underwriting Association assessments to dedicated liability accounts. Per-state variance is captured as crosswalk rows with state code as a key dimension. Adding a new state post-go-live is a crosswalk update, not a project.
Reinsurance is the most complex mapping domain. The treaty registry on the Duck Creek side carries proportional cession percentages (for quota share treaties), per-risk attachment points and limits (for excess-of-loss treaties), per-occurrence attachment points and aggregates (for catastrophe excess), and facultative-specific terms (for individual risks). Each treaty has a counterparty (the cedant) that becomes a Fusion supplier (for ceded premium AP credit memos) and a Fusion customer (for recoverable AR invoices). The mapping makes each treaty's cession rule explicit: which premium events drive a cession, what percentage cedes, what entry the cession produces in Fusion AR and AP, how recoverables track per claim per treaty, and how Schedule F reconciliation reconstitutes from Fusion. Chief reinsurance officer and chief actuary jointly sign off.
Yes. Producer commissions are a major flow on the Duck Creek side — base commission per policy, override commissions for agency managers, contingent profit commissions paid annually based on portfolio loss ratio, and bonus commissions on growth or retention thresholds. The mapping captures each commission type to its Fusion AP destination: base and override commissions to per-producer AP invoices generated alongside the corresponding premium-receivable, contingent commissions as periodic AP invoices generated from the actuarial profit calculation, bonus commissions as one-off AP entries. Producer hierarchy is mapped to Fusion supplier parent-child structures. Commission tax 1099 reporting from Fusion AP picks up where Duck Creek leaves off.
The deliverable is the executable specification for the integration build. The Syntra ETL insurance-finance translation engine reads the mapping crosswalks directly as configuration — line-of-business codes, state crosswalks, treaty registry, commission types, reserve types, claim-feature taxonomy. Build engineers don't rewrite the mapping in code; they configure the engine from the signed crosswalks. This eliminates the typical integration failure mode where the mapping document and the code drift apart over the build. It also accelerates updates post-go-live — a new state added to the carrier's footprint is a crosswalk row, not a code change. A new line of business launched on Duck Creek is a Manuscripts configuration on Duck Creek plus a crosswalk update on the integration side. Maintenance burden drops materially versus hand-coded integration.
30-minute call with our P&C insurance-finance integration team. We'll walk through your Duck Creek deployment, your line and state footprint, your reinsurance program and your Fusion COA — and scope a fixed-fee duck creek to oracle fusion data mapping engagement before the call ends.