Self-service duck creek historical reporting against archived Policy, Billing, Claims, Treaty and statutory reporting data — across OnDemand and Platform deployments. OTBI / BI Publisher / Tableau / Power BI — same Parquet archive, NAIC SAP + GAAP basis preserved, audit-grade access logging on every retrieval.
The day after a Duck Creek Platform book moves off active workflow, the reporting load doesn't disappear — it shifts to retrospective questions that take years to fully play out.
When a P&C carrier moves a book of business off Duck Creek Platform (to a newer Platform release, to OnDemand, or to a different insurance core entirely), active policy and claim workflow moves to the successor system within weeks. The reporting workload does not. Statutory accountants still chase prior-year NAIC Annual Statement reconciliation, reserve roll-forward substantiation and Schedule F treaty totals — typically for 7+ years post-cutover. Finance still chases prior-year P&L variance and combined-ratio analysis. Actuarial still runs loss-development triangles spanning the retired instance — long-tail liability triangles routinely span 20+ years. Claims litigation counsel still answers subpoenas, coverage disputes and bad-faith claims years after the underlying policy expired. State market-conduct examiners still arrive for periodic exams. Reinsurance teams still respond to treaty audits going back multiple bordereau cycles.
Keeping the source Duck Creek Platform instance alive solely to serve this retrospective reporting load is the expensive way to solve it — $200K to $2M+ per year per zombie instance in licensing, infrastructure and support staff. Duck creek historical reporting on the long-term archive is the cheaper way: archive the data once, decommission the source, serve every retrospective query from the archive's Parquet store through OTBI, BI Publisher, Tableau, Power BI or any analytic tool your statutory accountants, finance team and actuarial team already use.
The reporting layer preserves NAIC statutory accounting (SAP) and GAAP dual basis on every record. Pre-built subject areas cover combined ratio trend, premium-earning curves, reserve roll-forward, loss-development triangles, NAIC Schedule F reconstruction, market-conduct exam packages, and audit-substantiation views. Every retrieval is logged for audit substantiation — one log serving NAIC examiners, SOX auditors, state regulators and reinsurance treaty auditors. The duck creek historical reporting layer is designed to outlast the question 'what was our 2018 combined ratio for California auto' by however many years your retention requires.
Pre-built dashboards and report templates covering the queries P&C carriers actually run post-cutover.
Loss ratio + expense ratio decomposed by LOB, state, accident year and policy year — across pre- and post-cutover periods. Drives underwriting profitability and pricing review.
Per-LOB per-accident-year triangles supporting actuarial reserve analysis. Long-tail lines (workers' comp, GL, professional liability, environmental) trace 20+ years.
Written, earned and unearned premium by policy period, LOB and state. Pro-rata and 24ths-method curves preserved. Endorsement and cancellation impact retrievable.
Pre-built BI Publisher templates for Pages 14/15 (premium and loss by state and LOB), Schedule F (reinsurance ceded), Schedule P (loss development) reconstruction against the archive.
Per-treaty per-bordereau ceded premium, loss-ceded, recoverables, reinstatement premium and profit commission. Treaty audit packages exported on demand.
Subpoena, coverage dispute, bad-faith and state market-conduct exam retrieval interface. Sub-15-second per-record lookup. Every retrieval logged for audit substantiation.
Once the archive is populated (see duck creek data archival), turning on the reporting layer takes weeks not quarters.
Controller, statutory reporting lead, finance VP, actuarial lead, claims counsel walk through user roles. SAP vs GAAP basis access configured per role per domain. Litigation discovery interface scoping configured.
Pre-built combined ratio, loss development, premium earning, NAIC Annual Statement, Schedule F and market-conduct exam dashboards deployed to OTBI / BI Publisher. Customized to your COA, fiscal calendar, LOB taxonomy and state footprint.
Tableau, Power BI, Looker or your analytic platform of choice connected to the archive Parquet endpoint with role-based scoping. Litigation discovery interface stood up for claims counsel. Treaty audit interface stood up for reinsurance team.
Sample queries validated against known historical results (last NAIC Annual Statement filing, recent Schedule F submission, recent market-conduct exam response). Sub-15-second SLA verified per dashboard. Controller, statutory reporting lead and external auditor liaison sign off.
Duck creek historical reporting layer goes live. Users trained on dashboard access. Claims counsel trained on litigation retrieval. SIEM integration verified for audit logging. Source-Platform reporting workload retired.
Dashboards run on demand. Retrievals logged. Per-state retention enforcement automatic — purged records return 'not retrievable' with the retention basis. Annual review of dashboard catalog and retention policy.
Six structural advantages of reporting from the archive instead of from the retired source system.
$200K–$2M/yr per zombie Platform instance vs $20K–$150K/yr for archive-based reporting. 70–85% TCO reduction on the retrospective reporting workload.
Parquet-backed Snowflake / Redshift / BigQuery analytic queries beat SQL Server / Oracle DB replicas at 5–50× on the trend queries that dominate retrospective insurance reporting.
Per-role, per-basis access enforced uniformly. No more giving every statutory accountant DBA access to Platform just because they need a Page 14 reconstruction.
Every retrieval logged centrally with auditor-grade context. No more piecing together Platform audit logs from multiple zombie instances during a state market-conduct exam.
Per-state retention rules enforce automatic purge with signed certificate of destruction. Source Platform either over-retains (liability) or accidentally under-retains (regulator finding).
Single query spans OnDemand and Platform history. Source-Platform reporting requires writing the same query against each retired instance and reconciling by hand.
Duck creek historical reporting is self-service access to historical policy financial events, billing transactions, claim financials, reserves and reinsurance cession data drawn from retired or downsized Duck Creek Platform and OnDemand instances — without keeping the source system live. Statutory accountants retrieve prior-year Annual Statement reconciliation; finance chases prior-year P&L variance and combined-ratio analysis; actuarial runs loss development triangles spanning the retired instance; claims litigation counsel responds to subpoenas and coverage disputes; reinsurance teams reconstruct historical cession for treaty audits; internal audit and state examiners run market-conduct exams over the full retention window. The data lives in the long-term archive (S3 / GCS / Azure Blob); the duck creek historical reporting layer is OTBI, BI Publisher, Tableau, Power BI or your data warehouse views on the archive Parquet store, scoped to user role and statutory accounting basis, with every retrieval logged for audit substantiation.
Three reasons. First, the source Duck Creek Platform SQL Server / Oracle DB schema is not user-friendly — hundreds of DCT tables with cryptic column names and undocumented joins designed for the application, not for ad-hoc reporting. Second, statutory reporting requires preserving the specific NAIC line-and-state segmentation, policy-period earning conventions, reserve roll-forward sequences, and reinsurance cession lineage that go into Annual Statement Pages 14/15, Schedule F and Schedule P. Generic ad-hoc reporting tools strip this context. Third, retention rules vary per state and per line of business, and a query that returns purged or held-only records breaks user trust. Duck creek historical reporting on a dedicated archive solves all three: clean canonical schema, NAIC-aware reporting views, retention-aware query filtering.
Everything the archive holds, scoped per user role. Policy: bind, endorsement, cancellation, reinstatement, renewal, term, transaction details. Billing: premium-due, payment receipts, NSF, write-offs, return premium, agency commissions. Claims: claim header, claim feature per coverage, indemnity payments, LAE payments, case reserves, salvage and subrogation recoveries. Reserves: case, IBNR, unearned premium, loss-adjustment-expense reserves. Reinsurance: treaty registry, ceded premium per bordereau, loss-ceded entries, recoverables, reinstatement premium, profit commission. Pre-built dashboards cover combined ratio trend, loss-development triangles, premium-earning curves, reserve roll-forward, NAIC Schedule F treaty balance reconstruction, payer-mix and producer-mix shift analysis, and audit-substantiation views for state examiners.
P&C carriers report on both bases — statutory for state insurance departments and NAIC, GAAP for SEC filings and external auditors. Duck creek historical reporting preserves both — each financial fact in the archive is tagged with its SAP and GAAP attributes where they diverge (deferred acquisition cost treatment, non-admitted assets, reinsurance recoverable classification, dividend treatment, etc.). OTBI subject areas and BI Publisher templates expose either basis. A statutory accountant reconstructing the prior-year Annual Statement Page 14 pulls SAP-basis numbers. A GAAP financial reporting analyst pulls GAAP-basis numbers from the same underlying records. The duck creek historical reporting layer never forces users to choose between bases — both run from one consistent archive.
The archive Parquet store registers as an external data source in Fusion's analytic layer via Oracle Autonomous Database or direct Parquet connector. Fusion OTBI subject areas surface the historical Duck Creek data alongside current Fusion finance data — a single OTBI dashboard can show current-fiscal-year Fusion AR aging alongside prior-fiscal-year Duck Creek premium-due aging from the archive without ETL'ing the archive into Fusion. BI Publisher pixel-perfect reports (NAIC Annual Statement reconstruction, Schedule F treaty package, audit packages, regulator submissions) consume the same archive views. Tableau, Power BI and Looker users connect through the same Parquet endpoint with their own role-based scoping. The duck creek historical reporting layer is intentionally tool-agnostic — wherever your statutory accountants, finance team and actuarial team work, the archive is reachable.
Yes — and that is one of the highest-value use cases. The claims litigation counsel or compliance team issues a query against the archive scoped to the policy or claim identifier, the date range and the document types requested. The archive's indexed retrieval returns matching records in sub-15 seconds. Each record viewed is logged with counsel identity, requester identity (claimant attorney, regulator, opposing carrier), scope, purpose and recipient. The team exports the records (often in a PDF package signed and timestamped) and the disclosure log lands in SIEM. When state market-conduct examiners arrive for a periodic exam, the same retrieval mechanism produces the policy-by-policy and claim-by-claim packages they request — typically in minutes rather than the weeks required to restore a retired Platform instance.
Yes — the reporting layer treats OnDemand and Platform data as deployments of the same underlying insurance data model. This matters most for queries that span a deployment boundary: a 10-year combined-ratio trend spanning the Platform-to-OnDemand transition, a long-tail claim development triangle including claims that originated on Platform and continue settling under OnDemand, a Schedule F treaty reconstruction spanning treaty periods that straddle the migration. Duck creek historical reporting is deployment-agnostic — the data is what matters, and the archive carries it all in one canonical schema. Users see one continuous reporting context. The audit log captures source-deployment attribution per record so chain-of-custody back to the original OnDemand or Platform deployment is always retrievable.
A typical carrier keeping a retired Duck Creek Platform instance alive solely for retrospective reporting pays $200K–$2M+ per year — SQL Server / Oracle DB licensing, server infrastructure, application-support staff, security patching, DR replication. Duck creek historical reporting on the archive runs $20K–$150K per year for storage, query infrastructure and the operational overhead of one engineer fractional-FTE. The 70–85% TCO reduction reported by carriers running the archive applies to the reporting workload too — and unlike keeping the source live, the archive scales storage independent of query infrastructure, so adding 10 more years of long-tail claim retention does not require buying another database license.
30-minute scoping call: we walk through the user roles, SAP/GAAP basis access, NAIC reporting templates, litigation discovery workflow and tool integrations — and have duck creek historical reporting in production within weeks of archive population.