DUCK CREEK DOMAIN MIGRATION

    Duck Creek Policy, Billing, Claims, Rating Migration — Domain-Object Deep Dive

    Per-domain migration treatment of Duck Creek's four core domain objects — Policy, Billing, Claims, Rating. Each with separate sign-off, separate testing, separate cutover discipline. Multi-state ratebook variance, treaty cession, reserve roll-forward all preserved. Domain owners stay accountable.

    4 domains
    Policy, Billing, Claims, Rating
    Per-domain sign-off
    Owners stay accountable
    50 states
    Per-state complexity managed
    Sequenced cutover
    Domain dependency order

    Why duck creek policy, billing, claims, rating migration treats each as a separate domain object

    Each domain has separate ownership, separate semantic complexity and separate downstream consequences. Monolithic treatment produces sign-off paralysis and concentrated risk.

    Duck Creek's data model has four core domain objects — Policy, Billing, Claims, Rating — and each represents months of insurance-industry expertise embedded in the product configuration. Policy carries the contract lifecycle with multi-term policies, written-premium and earned-premium curves, multi-state ratebook variance, endorsement and cancellation handling. Billing carries account-level aggregation across policies, premium-due scheduling, payment processing, agency commission flows. Claims carries the claim lifecycle through FNOL, features per coverage, case reserves with adjuster work plans, IBNR allocations, salvage and subrogation handling. Rating carries the rate-calculation engine with per-state ratebooks, surcharge and fee application, premium tax computation, FAIR Plan and JUA assessments.

    Treating duck creek policy, billing, claims, rating migration as one monolithic effort produces predictable failure modes. Sign-off paralysis — no single executive can be accountable for everything at once, so sign-off stalls. Risk concentration — one bug in one domain blocks progress across all four. Owner disengagement — domain owners can't see their domain clearly in a monolithic deliverable, so they default to passive review rather than active accountability. Carriers that pursue monolithic Duck Creek-to-Fusion migration consistently report budget overruns, schedule slips and post-go-live stabilization issues that trace to inadequate domain-by-domain treatment.

    Syntra ETL's duck creek policy, billing, claims, rating migration treats each as a separate workstream with named owners, separate mapping deliverables, separate translation rule sets, separate testing and separate per-domain sign-off. The four workstreams run with controlled overlap — policy mapping completes before billing mapping starts in earnest (because billing depends on policy structure); claims runs in parallel with billing (because they have independent data models); rating depends on policy and surfaces in both billing and claims. Final consolidated cutover ties the domains together for the Duck Creek-side switch. Each domain owner stays accountable for their domain through go-live and into steady-state.

    The four domains and their named owners

    1
    Policy
    Chief underwriting officer / chief product officer. Policy lifecycle, multi-term, multi-state ratebook variance, earned-premium curve.
    2
    Billing
    Chief financial officer / billing operations head. Account-level aggregation, premium-due, payment processing, agency commission.
    3
    Claims
    Chief claims officer / chief actuary. Claim lifecycle, features per coverage, case reserves, IBNR, salvage, subrogation.
    4
    Rating
    Chief actuary / chief product officer. Rate algorithm execution, per-state ratebook, surcharge/fee/tax/assessment calculation.

    What each Duck Creek domain object actually contains

    The data shapes, transactions and semantic complexity per domain that the migration has to preserve.

    📜

    Policy domain

    Header, term, transaction, transaction detail. Bind/endorse/cancel/reinstate/renew. Multi-state premium split. Daily-pro-rata or 24ths earning. State-of-risk surcharge application.

    💵

    Billing domain

    Account (aggregator across policies), installment plan, premium-due transactions, payment receipts, NSF, write-offs, return premium, agency commission per producer per LOB.

    📉

    Claims domain

    Claim (per loss event), claim feature (per coverage), case reserve, IBNR, indemnity payment, LAE payment, salvage, subrogation, recovery, claim-close per feature.

    🧮

    Rating domain

    Per-state ratebooks, base premium calculation, surcharge application, policy fee + inspection fee + MVR fee, premium tax per state, FAIR Plan and JUA assessment, point-in-time ratebook lookup.

    🔗

    Cross-domain integrations

    Policy feeds Billing (premium-due schedule). Policy feeds Claims (claim attaches to policy). Rating drives Policy (premium calculation). Reinsurance overlays Policy + Claims.

    📊

    NAIC + state DOI surfaces

    Pages 14/15 reporting from Policy + Claims. Schedule F from Reinsurance + Claims. PT-1 premium tax from Billing. Surplus lines filings from Policy + Billing for non-admitted business.

    The duck creek policy, billing, claims, rating migration sequence

    Sequenced per domain dependency. Final consolidated cutover ties domains together.

    1

    Foundation — Weeks 1–3

    Fusion enterprise structures, ledgers, BUs, COA segments. Master crosswalks (state, currency, LOB). Policy/Billing/Claims/Rating workstream kickoffs with named owners.

    2

    Policy Migration — Weeks 3–10

    Policy lifecycle mapping. Earned-premium curve translation. Multi-state premium split. Mock cutover #1 and parallel-run cycle. Sign-off by chief UW officer / chief product officer.

    3

    Billing Migration — Weeks 8–14

    Account aggregation mapping. Premium-due schedule translation. Payment processing flow. Agency commission flow. Mock cutover #1 and parallel-run cycle. Sign-off by CFO / billing ops head.

    4

    Claims Migration — Weeks 10–18

    Claim and feature mapping. Case reserve and IBNR translation. Salvage and subrogation reversal. Mock cutover #1 and parallel-run cycle. Sign-off by chief claims officer / chief actuary.

    5

    Rating Domain Integration — Weeks 14–20

    Per-state ratebook mapping. Surcharge/fee/tax calculation translation. Point-in-time ratebook lookup for historical recomputation. Sign-off by chief actuary / chief product officer.

    6

    Consolidated Cutover + Stabilization — Weeks 18–26

    Final consolidated cutover ties domains together. Duck Creek event stream switches to Fusion-only across all domains simultaneously. 4–8 weeks of heightened-monitoring stabilization. Each domain owner monitors their domain through steady-state.

    Per-domain insurance-finance translation rules — the engine reads these as configuration

    The pre-built logic that turns Duck Creek domain events into Fusion-native postings.

    📅

    Earned-premium curve

    Daily-pro-rata or 24ths method per policy. Cancellation short-rate or pro-rata. Endorsement mid-term proration. Returns reverse the curve correctly.

    💰

    Account aggregation

    Premium-due per account per installment date. Payment application waterfall per account terms. NSF reversal + re-aging. Write-off per carrier policy.

    📒

    Reserve roll-forward

    Case + IBNR per claim feature per accident period. Adverse and favorable development tracked. Schedule P loss-triangle reconstitution-ready.

    🔄

    Salvage + subrogation reversal

    Recovery posts against original loss account same claim feature. Net paid loss after recovery preserved for Schedule P.

    🧮

    Rating + premium tax

    Per-state ratebook lookup. Surcharge/fee application per LOB per state. Premium tax to state-tax liability account. FAIR Plan and JUA assessment per state convention.

    💼

    Commission per producer

    Base + override + contingent + bonus per producer. Producer hierarchy (agency-manager) mapped to Fusion AP supplier parent-child.

    Frequently asked questions

    What does duck creek policy, billing, claims, rating migration involve?+

    Duck creek policy, billing, claims, rating migration is the deep domain-object work of moving each Duck Creek system-of-record into Fusion or a target downstream — and the four domains each have distinct shape and complexity. Policy: policy lifecycle events (bind, endorsement, cancellation, reinstatement, renewal) with multi-term policies, written-premium and earned-premium curves, multi-state ratebook variance per LOB. Billing: account-level billing aggregation across policies, premium-due transactions, payment processing, NSF and write-off handling, agency commission flows. Claims: claim creation through FNOL, claim features per coverage, indemnity and LAE payments, case reserves with adjuster work plans, salvage and subrogation handling. Rating: rate algorithm execution at quote and bind, surcharge and fee calculation, premium tax computation per state, FAIR Plan and JUA assessments. Each domain is a separate workstream with separate sign-off, separate testing and separate cutover discipline.

    Why are policy, billing, claims and rating treated as separate domain objects?+

    Because they have separate ownership, separate semantic complexity and separate downstream consequences. Policy is owned operationally by underwriting and product management — changes to policy lifecycle handling have product implications. Billing is owned by billing operations and finance — changes affect cash receipts, agency commissions and customer-facing statements. Claims is owned by claims operations and the chief actuary — changes affect reserve adequacy and loss-development reporting. Rating is owned by actuarial and product — changes affect premium adequacy and state-DOI rate-filing compliance. Treating them as one monolithic migration produces sign-off paralysis (no one can sign off on everything at once) and unmanaged risk concentration (one bug in one domain affects all four). Treating them as separate domain objects with separate sign-off, separate testing and separate cutover discipline keeps the project moving and keeps each domain owner accountable for their domain.

    How does Duck Creek's policy domain object actually work?+

    Policy is the top-level entity in Duck Creek's insurance-core data model. Each policy has a policy header (policy number, named insured, effective date, expiration date, line of business, state, agency, producer), one or more policy terms (typically 12-month terms; commercial policies may have shorter or longer terms; some specialty lines run multi-year), and many policy transactions per term (bind, endorsement, cancellation, reinstatement, renewal, audit). Each transaction has transaction details (one per coverage or per item endorsed) carrying the premium and commission implications. The earned-premium curve runs across the term per daily-pro-rata or 24ths-method calculation. Cancellation triggers return-premium on short-rate or pro-rata basis per the policy's cancellation clause. Endorsement triggers additional or return premium prorated for the remaining term. Multi-state policies (commercial fleet, national accounts, surplus lines) split premium across states per the situs of risk.

    How does Duck Creek's billing domain object actually work?+

    Billing operates above the policy level. A billing account aggregates all policies for a single billed party — typically a named insured for personal lines, a parent corporation for commercial lines, an MGA for delegated authority business. The account has an installment plan (annual pay-in-full, semi-annual, quarterly, monthly, monthly EFT, monthly credit card), driving the premium-due schedule. Each premium-due transaction posts on its due date and feeds Fusion AR. Payment receipts apply against premium-due transactions per the account's payment-application waterfall. NSF reversals back out the original payment and re-age the underlying premium-due. Write-offs handle uncollectible premium per the carrier's write-off policy. Agency commissions are calculated per producer per LOB and post as AP entries paired to the corresponding AR receipt cycle. Cancellation for non-payment is triggered by aged unpaid premium-due transactions per state-specific rules.

    How does Duck Creek's claims domain object actually work?+

    A claim is created via FNOL (First Notice of Loss) — typically through an agent, a call center, a customer portal or an automated channel. The claim attaches to a policy and creates one or more claim features per coverage involved in the loss (auto policy with bodily injury and property damage produces two claim features; homeowners policy with dwelling, personal property and loss-of-use produces three). Each feature has its own case reserve (the adjuster's estimate of ultimate cost), IBNR allocation (the actuarial team's estimate of unreported development), paid history (indemnity payments to the claimant plus LAE payments to adjusters and vendors), and recovery history (salvage and subrogation). Case reserves move as the adjuster gathers information. IBNR moves as the actuarial team re-estimates. Paid loss moves as claim payments issue. The claim closes when all features are resolved — typically months or years after the loss event for liability claims, sometimes decades for catastrophic claims like asbestos.

    How does Duck Creek's rating domain object actually work?+

    Rating is the calculation engine that converts a policy submission into a premium quote and then a bound policy premium. Duck Creek runs ratebooks per LOB per state — each state's regulatory environment, loss experience and market conditions produce different rates. The rating engine takes policy attributes (risk address, vehicle/dwelling characteristics, drivers/occupants, prior losses, credit factors where permitted) and computes base premium, applies surcharges (high-risk, surplus lines, etc.), fees (policy fee, inspection fee, MVR fee), premium taxes per state, FAIR Plan and Joint Underwriting Association assessments where applicable. The output is the premium that flows to the policy transaction and then through billing to AR. Rate changes require state-DOI filing approval before implementation, and the rating domain has to support point-in-time ratebook lookup to recompute historical premiums under historical rate sets.

    How does the migration handle multi-state and multi-jurisdictional complexity?+

    Through governed crosswalk tables and per-state translation rules. State of risk drives a stack of decisions: which ratebook applies, which surcharges and assessments apply, which premium tax rate applies, which surplus lines tax applies (for non-admitted business), which NAIC Annual Statement Pages 14/15 column the premium and loss report into. Multi-state commercial policies split premium per situs of risk and the integration tracks each split per Fusion COA segment combination. Surplus lines business in states where the carrier is non-admitted has additional reporting requirements per state surplus-lines tax filing rules. Carriers operating across many states (large national personal-lines carriers may operate in all 50 states plus DC plus US territories) get the per-state complexity captured as crosswalks — adding a new state post-go-live is a crosswalk update, not a project.

    How are policy, billing, claims and rating cutover sequentially or together?+

    Sequenced. The cutover strategy schedules domains in dependency order: foundation (Fusion enterprise structures, ledgers, COA, master crosswalks) first; policy migration second (policy lifecycle events to Fusion AR + GL with earned-premium curves); billing migration third (account-level aggregation and premium-due flows); claims migration fourth (claim financial events to Fusion AP + GL with case-reserve and IBNR roll-forward); rating fifth (historical premium recomputation for any back-period adjustments). Reinsurance and commission flows layer on each domain. Each domain has its own parallel-run, mock rehearsal and sign-off. Final consolidated cutover ties them together — Duck Creek event stream switches to Fusion-only across all domains simultaneously after each domain has independently signed off. Sequenced domain cutover reduces concurrency risk; consolidated final cutover ensures Duck Creek-side switch is one event.

    Plan a domain-aware duck creek policy, billing, claims, rating migration

    30-minute call with our P&C insurance-finance integration team. We'll walk through your Duck Creek policy lifecycle, billing structure, claims workflow and rating engine — and scope a domain-aware migration plan before the call ends.