Steady-state duck creek oracle fusion integration. Real-time event streams for cash receipts, bordereau, large losses, treaty reinstatements. Batch journals for monthly reserves, UPR, DAC. OnDemand + Platform unified. Survives Duck Creek upgrades. Scales through renewal season and CAT events.
Different Duck Creek event types need different latency, different aggregation and different Fusion target shapes. One-size-fits-all integration doesn't work.
Cash receipts on the Duck Creek Billing side should hit Fusion AR within seconds — treasury needs current cash positions, bank reconciliation needs current AR receipt data, daily cash forecasting needs current receipt actuals. Sending cash receipts in an overnight batch wastes a full day of treasury visibility. On the other hand, monthly case-reserve adjustments per claim feature don't need real-time latency — they are aggregated period-end calculations that the actuarial team produces on a defined cadence, and posting them as one consolidated monthly GL journal per LOB per accident period is much cleaner than streaming individual reserve-adjustment events. Both approaches are correct, for different event types.
Syntra ETL's duck creek oracle fusion integration runs both modes — real-time for time-sensitive events, batch for period-aggregated events — and routes each event type to its appropriate mode based on a default configuration that carriers can tune to their preference. The same underlying Insurance-Finance Translation Engine handles transformations for both modes, so per-event translation logic is consistent regardless of latency mode. Fusion-side posters use the appropriate Fusion mechanism per mode: REST API for real-time AR receipts and AP invoice creation, FBDI bulk loads for batch period aggregations.
The integration is built to survive Duck Creek's evolution. The OnDemand REST API surface evolves quarterly. The Platform DCSB schema evolves with each Platform release. Many carriers are mid-transition from Platform to OnDemand and need both surfaces to operate simultaneously for 24–36 months. The integration handles all of this through the canonical event schema insulation layer — Translation Engine and Fusion-side posters operate against the canonical schema, not against raw Duck Creek payloads, so OnDemand API upgrades, Platform version upgrades and OnDemand-Platform transitions all roll through without rework. Customers don't chase Duck Creek deprecation announcements — Syntra ETL ships extractor updates tracking the Duck Creek roadmap as part of the standard release channel.
Pre-configured routing per event type. Tunable per carrier preference.
Cash receipts, NSF reversals, bordereau cession transactions, treaty reinstatement premium — to Fusion AR/AP within seconds via REST.
Large-loss notifications and same-day case-reserve adjustments — to Fusion GL within seconds. Executive reporting reflects significant losses immediately.
Premium-due transactions aggregated per producer per LOB per day. One Fusion AR invoice per aggregation. Producer commissions paired.
Case + IBNR reserves aggregated per claim feature per accident period. Monthly Fusion GL journal per LOB per accident period.
Unearned-premium reserve and deferred-acquisition-cost roll-forward per policy per LOB. Monthly Fusion GL journal.
Reinsurance bordereau aggregations per treaty per period. Ceded premium AP and recoverable AR. Schedule F-ready posting structure.
Real-time and batch modes operating together in steady-state production.
OnDemand Insights API event stream and Platform DCSB subscriptions running continuously. Every Duck Creek financial event captured to the staging layer within seconds of commit. Hash signature attached at capture.
Time-sensitive events (cash, bordereau, large-loss, treaty) transformed and posted to Fusion via REST within seconds. Idempotency-checked. Real-time hash validation on arrival.
Premium-due transactions aggregated per producer per LOB per hour. Producer commissions paired. FBDI AutoInvoice submitted to Fusion AR ESS. Reconciliation hash per batch.
Daily aggregations finalized. Producer commission settlements posted. Salvage/subrogation reversals consolidated. Daily reconciliation pack produced and signed.
Case + IBNR reserve journals. UPR roll-forward. DAC roll-forward. Reinsurance bordereau aggregations. Monthly statutory reconciliation produced. Schedule F-ready.
Historical event replay against current Fusion configuration. Used for Duck Creek source-correction propagation, Translation Engine rule changes, COA structure adjustments.
The details that matter when the integration has to run unattended for years.
Every event carries Duck Creek source ID. Duplicates detected and rejected at integration layer. Never produces duplicate Fusion postings.
Translation-engine and FBDI-submission workers scale automatically with queue depth. CAT-event spikes to 150K events/day absorbed without operator intervention.
TLS 1.3 in transit. KMS at rest for credentials and event payloads. SOC 2-compliant audit logging across the full event path.
Prometheus metrics for throughput, latency, error rates per event type. Grafana dashboards. Alerts via email, Slack, PagerDuty, webhook per severity.
Failed events land in DLQ with full diagnostic context. Structured runbook per error class. Replay-on-resolution standard.
Canonical schema insulation. OnDemand API minor versions, Platform release upgrades and Platform-to-OnDemand transitions absorbed by extractor layer. Translation and Fusion sides unaffected.
Duck creek oracle fusion integration is the steady-state operational pattern that flows financial events from Duck Creek Policy, Billing and Claims into Oracle Fusion AR, AP and GL. Distinct from a migration — which is a one-shot move from legacy finance to Fusion — integration is the recurring ongoing pattern that operates indefinitely after Fusion goes live. The integration runs in two complementary modes: near-real-time for time-sensitive events (cash receipts, bordereau transactions, large-loss notifications, treaty reinstatements) using Duck Creek Insights API event streams (OnDemand) or DCSB subscriptions (Platform); and batch for high-volume, period-aggregated events (monthly reserve journals, monthly UPR journals, daily premium-due aggregations). Both modes feed the same underlying insurance-finance translation engine that converts Duck Creek events into Fusion-native postings with full audit context.
Real-time mode operates on individual events as they occur — typically within seconds of the event committing in Duck Creek. The Insights API event subscription (OnDemand) or DCSB subscription (Platform) delivers each event to the integration layer, which transforms it through the insurance-finance translation engine and posts the corresponding Fusion AR/AP/GL entry within seconds. Used for: cash receipts (so treasury cash forecasting is current), bordereau transactions (so reinsurance reporting is current), large-loss notifications (so reserve adjustments hit Fusion same-day), treaty reinstatements (so cession capacity is reflected immediately). Batch mode operates on event aggregations over a defined period — typically end-of-day or month-end. Used for: monthly reserve journals (case + IBNR per claim feature), monthly UPR journals (per policy), daily premium-due aggregations to AR (per producer per LOB). The duck creek oracle fusion integration uses each mode for its appropriate event type — not one-size-fits-all.
Real-time: cash receipts (so treasury and bank reconciliation are current), bordereau transactions (so reinsurance treaty reporting reflects cession in-period), large-loss notifications (so reserve adjustments hit Fusion same-day for executive reporting), treaty reinstatements and profit commission settlements (so cession capacity is current), salvage and subrogation recoveries (so net-loss reporting is current). Batch — end-of-day or month-end: monthly case-reserve and IBNR journals to GL (aggregated per claim feature per accident period), monthly UPR roll-forward journals (per policy), monthly DAC roll-forward, daily premium-due aggregations to AR (one Fusion AR invoice per producer per LOB per day rather than one per policy transaction), monthly reinsurance bordereau aggregations. The duck creek oracle fusion integration template ships these conventions out-of-the-box, configurable per carrier preference.
Through the canonical event schema insulation layer. Syntra ETL's integration sits on a canonical event schema that the extractor normalizes Duck Creek API or DCSB events into before transformation. The Insurance-Finance Translation Engine and the Fusion-side posters operate against the canonical schema — not against raw Duck Creek API or DCSB payloads. So when Duck Creek upgrades OnDemand API versions (typical quarterly cadence), or when the carrier upgrades Duck Creek Platform from one major version to the next (typical every 18–24 months), the extractor layer absorbs the change and the canonical schema stays stable. Translation rules and Fusion-side posters don't need to change. The integration survives Duck Creek upgrades without rework — and Syntra ETL ships extractor updates tracking the Duck Creek roadmap so customers don't chase API deprecation announcements.
Five layers. (1) Idempotency — every event carries a stable Duck Creek source identifier (policy transaction ID, claim payment ID, treaty cession ID); duplicate events posted to Fusion are detected and rejected at the integration layer, never producing duplicate AR/AP/GL postings. (2) Hash validation — every event hash-validated on arrival at Fusion; mismatches alerted within 30 seconds. (3) Checkpoint-resume — failed batch runs resume from the last successful checkpoint rather than restarting. (4) Dead-letter queue — events that fail translation or fail Fusion posting after retry land in a dead-letter queue with full diagnostic context for operator review. (5) Replay-on-demand — operators can replay any historical event or event range against current Fusion configuration, useful when Duck Creek source corrections need to flow forward. The carrier's integration ops team has a structured runbook for each error class — no improvisation under pressure.
P&C insurance has predictable volume peaks — renewal season (typically Q4 personal lines, Q1 commercial lines), CAT events (catastrophic weather creating spikes in FNOL and claim payments), policy bind season (often Q1 commercial lines for January-effective books). The integration scales horizontally — additional translation-engine workers spin up automatically based on event-queue depth, additional Fusion FBDI submission workers parallelize per-domain (AR, AP, GL run in parallel rather than serial). Throughput in production: a typical mid-market carrier sees 20K events per business day in normal operation, spiking to 80K events per day during renewal season and 150K events per day in the days immediately following a CAT event. The duck creek oracle fusion integration handles these spikes without operator intervention. Carriers consistently report that the integration absorbs CAT-event volume better than the legacy finance systems it replaces.
Many carriers are mid-transition from Duck Creek Platform to Duck Creek OnDemand — a 24–36-month transition for a large carrier moving primary books to the SaaS platform. During the transition, financial events originate from both deployments. The integration handles this by routing both deployments to the same canonical event schema before transformation, so Fusion sees one consistent event stream regardless of origin. As lines of business migrate from Platform to OnDemand, the integration's per-event routing updates automatically — no Fusion-side change. Reconciliation tracks per-deployment-of-origin so during transition the carrier can confirm that a transaction originated on Platform vs the same transaction type originated on OnDemand produces identical Fusion postings. Post-transition (when all production lines are on OnDemand) the Platform-side extractor scales down to historical-only operation.
The integration's real-time event stream feeds Fusion AR receipt postings within seconds of cash receipt on the Duck Creek side. Fusion AR aging and cash-position reporting are therefore current to within minutes. For forward cash forecasting — projecting premium receipts and claim payments forward — the integration exposes a forecasting dataset combining Duck Creek policy-due aggregations (premium expected per future period per LOB per producer), Duck Creek claim-pending aggregations (claim payments expected per future period based on case reserves and adjuster work plans), and Duck Creek reinsurance bordereau timing (cession settlements expected per treaty per future bordereau cycle). Treasury teams use the forecasting dataset directly in Fusion Cash Management or feed it to their downstream cash forecasting tool. The duck creek oracle fusion integration thereby modernizes both the after-the-fact recording side and the forward-looking cash forecasting side simultaneously.
30-minute call with our P&C insurance-finance integration team. We'll walk through your Duck Creek deployment, your event-type latency requirements, your renewal-season and CAT-event volume profile — and scope a duck creek oracle fusion integration before the call ends.