Duck Creek
Insurance suite for policy administration, billing, and claims
ProPay integrates with Duck Creek, a policy, risk, or CRM platform. Duck Creek is a cloud-native core insurance suite, Policy, Claims, and Billing, used by P&C carriers as an alternative to legacy on-premise core systems. ProPay authorizes claims against the context it holds and writes decisions back.
Duck Creek is a cloud-native core insurance suite, Policy, Claims, and Billing, used by P&C carriers as an alternative to legacy on-premise core systems. ProPay reads the context Duck Creek already holds and authorizes the claim against it, writing the decision, and everything that led to it, back as the record of what happened.
What ProPay does with Duck Creek
ProPay captures claim data 24/7 through web form, chat, SMS, and voice, and validates it against the coverage Duck Creek holds, policy configuration and claim records, before authorizing repair versus replace, or approving inside your configured thresholds.
The context that reaches Duck Creek isn’t a call transcript, it’s a structured SMS conversation. ProPay triages the homeowner over text, with 80 to 83 percent responding, and that exchange is what populates the fields Duck Creek needs to authorize the claim correctly the first time.
From there, ProPay sources parts across suppliers, tracks the order, and validates the resulting invoice against the authorization record before payment releases, with every decision written back to Duck Creek alongside the confidence level it was made at.
How the Duck Creek connection works
Duck Creek’s cloud architecture exposes an API for claims and policy data, which is where ProPay reads and writes.
Where Duck Creek doesn’t expose a field ProPay needs, a Forward Deployed Engineer builds the mapping during deployment rather than asking Duck Creek to change. Authorization, parts, and payment can go live against Duck Creek independently of each other.
What stays in Duck Creek
Policy configuration and billing rules stay inside Duck Creek exactly as configured.
What changes is how much of the authorization decision a person has to make by hand. ProPay applies your business rules against the context in Duck Creek and routes only the exceptions to a reviewer.
Data handling and security
The connection to Duck Creek runs on a company-specific ProPay instance, one carrier’s policy and claim data are never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.
Every authorization decision carries a confidence level and the inputs it drew from Duck Creek, and is logged. Decisions above your configured value or confidence thresholds route to a person before anything executes.
Deploying the integration
A dedicated Forward Deployed Engineer works with your team to build and maintain the Duck Creek connection, mapping the specific fields and authorization rules your program already runs on.
Frequently asked questions about ProPay and Duck Creek
Does ProPay replace Duck Creek?
No. Duck Creek remains the system of record for the underlying policy and case data; ProPay executes the authorization decision and the work that follows it.
How does ProPay connect to Duck Creek?
Duck Creek’s cloud architecture exposes an API for claims and policy data, which is where ProPay reads and writes. Where no interface exists, a Forward Deployed Engineer builds the connector during deployment.
Are authorization decisions against Duck Creek auditable?
Yes. Every decision carries a confidence level and the specific inputs from Duck Creek it was based on, and is logged for review.
