Customer Billing Dunning Message Delivery Coverage

A business has configured payment reminders, but several notices go to an old address and another customer receives duplicate emails after paying. This metric checks whether required collection messages reach the proper billing audience at the relevant unpaid state.

Define dunning as the agreed sequence of factual payment reminders or failure notices for an unpaid customer balance, which is not a licence to threaten or shame a customer. Stripe documents separate settings for failed-payment notices and unpaid recurring-invoice reminders, so different collection methods can require different workflows.

Start with a valid unpaid invoice or confirmed failed payment, since a disputed or incorrect invoice may need review before routine collection messaging. Define each required message window under the applicable contract and billing policy, not a generic cadence assumed from software defaults.

Identify the verified billing contact, customer entity and preferred authorised channel, because an active product user may not be allowed to receive finance notices. Distinguish created, queued, sent, accepted by provider, delivered and read, as the system may not provide evidence for every stage.

If delivery cannot be verified, label the uncertainty and follow an approved alternate route rather than counting a sent message as certainly received, and check bounce and suppression lists because a perfectly configured template cannot reach an address the mail system rejects. Before each reminder check current payment status, since a payment may settle between scheduling and send time.

If a partial payment or approved credit changes the balance, include the current amount rather than repeating the original full sum. For several invoices specify which one is due, and align messages with any formal dispute process so a contested charge is not presented as settled fact.

Keep content specific, with the invoice reference, due date, current amount, reason for contact and a way to resolve or question it, and check that the secure link points to the intended customer account. Use secure payment paths and do not ask customers to reply with card numbers or credentials.

For cross-border accounts review local language, holiday and legal notice requirements, verify the actual policy and date before stating that service may be suspended, and use an approved accessible or language-specific format where the customer has asked for one. Define the denominator as required message opportunities for eligible unpaid invoices, and count a message as covered only at the chosen delivery-evidence threshold and correct recipient within the window.

Show failed delivery, suppressed, cancelled because paid and disputed cases separately, and report material exceptions individually because an overall rate may conceal high-value accounts with stale contacts. Account for processing time on direct-debit or bank-transfer arrangements, pair coverage with recovery outcomes and complaints since more messages are not automatically better, and when a reminder fails assign a human follow-up instead of resending to a known bad address.