Guidewire billing docs show how delinquency workflows drive policy cancellations

In Guidewire BillingCenter, a past-due invoice can trigger payment requests and, if needed, a cancellation message to the Policy Administration System. Delinquency reaches across billing, policy administration, compliance, and customer service.

Delinquency is a policy workflow, not just an accounts receivable flag

Guidewire’s billing model makes the control point explicit. Every delinquency plan is tied to one or more delinquency reasons and one or more workflows, and an account cannot be created without a delinquency plan. If a policy does not carry its own delinquency plan in BillingCenter, the account-level plan applies, which makes delinquency handling part of the system’s core configuration rather than an optional add-on.

The practical effect is that the billing platform has to know more than whether money arrived. It has to know whether the account is “past due,” meaning some payment has been received but the full amount due as of today has not been received, or “not taken,” meaning the insured opted not to take the policy and never sent any payment. Those distinctions change the workflow path, the notice sequence, and the downstream policy action.

The delinquency chain reaction, step by step

A well-designed P&C billing workflow follows a predictable order, and the order matters because each handoff can affect coverage status and customer treatment.

Cancellation is a billing outcome with policy consequences

Guidewire treats cancellation as a policy transaction that ends a policy before its expiration date or original effective date. That definition matters because insurer-initiated cancellations usually take longer to complete, since regulations often require notice to the policyholder. In other words, the billing workflow does not end when the system flags delinquency; it continues into a regulated policy transaction.

Once a policy is canceled, planned invoice items are typically moved onto a final invoice. If the payer has overpaid, those excess funds can be disbursed or applied to another policy.

Reinstatement sits on the other side of that same loop. When delinquent payment is later resolved, the canceled policy period can be made effective again, and if the delinquency plan specifies a reinstatement fee, that fee is applied as an additional charge.

Regulation forces delinquency logic to stay configurable

The reason these workflows cannot be hard-coded is that state rules can change the permissible collection sequence overnight. New Jersey’s April 9, 2020 emergency action directed P&C insurers to refrain from canceling policies for nonpayment, refrain from collection activity, and refrain from applying late fees and other charges during the COVID-19 disruption. New York also issued grace-period guidance and policyholder notices tied to COVID-era payment relief.

A carrier operating across states cannot rely on a one-size-fits-all reminder sequence when one jurisdiction may allow collection activity and another may restrict it entirely. The billing platform has to preserve the state-specific rule set while still tracking when an account crosses into delinquency.

Where Guidewire and Duck Creek position the problem

Guidewire BillingCenter is explicit about the mechanics of delinquency, which makes it a reference point for the Tier-1 carrier segment where policy-adjacent controls have to be precise. Duck Creek uses more consumer-facing language: it describes Duck Creek Billing as “an established leader in the P&C insurance billing sector” and calls it “Modern Billing for a Modern Consumer.” Duck Creek Payments is presented as an insurance payment platform and digital insurance payment solution.