Flexible Dunning

Flexible dunning is the practice of tailoring the payment recovery process — the communications, retry attempts, escalation steps, and eventual outcomes applied to overdue or failed payments — to the specific context of each customer account rather than processing all payment failures through a single, uniform sequence. The word "dunning" derives from historical business terminology for the process of persistently requesting payment of a debt; in modern subscription commerce, it describes the systematic workflow for recovering revenue that was not successfully collected on its initial due date.

In a rigid dunning model, every failed payment receives the same treatment: a retry on day 3, a reminder email on day 5, a second retry on day 7, a final notice on day 14, and service suspension at day 21, regardless of whether the account is a strategic enterprise customer who has been a reliable payer for four years or a new SMB account that has already shown two previous payment failures. The rigidity of this approach produces predictable failures at both ends of the spectrum: strategic accounts experience unnecessary friction that damages the commercial relationship over what is almost certainly an administrative error, while genuinely non-paying accounts receive insufficient escalation that allows the revenue exposure to compound over time.

Flexible dunning resolves this by making the dunning sequence a configurable policy with account-aware branching: the specific communications, retry schedules, escalation triggers, and service impact actions applied to each payment failure are determined by the account's context — segment, contract value, payment history, relationship tenure, and current account health status.

In B2B recurring revenue operations, the financial stakes of dunning effectiveness are significant. Research across subscription businesses consistently shows that 20-30% of involuntary churn (customer loss caused by payment failure rather than cancellation intent) is recoverable through better dunning design. For a company with £10M ARR and a 15% gross churn rate, if 25% of that churn is involuntary, effective dunning improvements could recover £375,000 in annual revenue that would otherwise be lost to payment processing failures rather than genuine customer dissatisfaction.

Signalon's analytics module supports flexible dunning by providing the account health and engagement signal data that enables intelligent dunning segmentation. An account that has recently been active in its digital sales room and is in active commercial discussions is treated differently from an account that has shown declining engagement and no recent interaction — because the payment failure context and the appropriate recovery approach differ significantly between these two situations. The connection between commercial engagement data and billing operations is one of the highest-leverage revenue recovery opportunities available to B2B revenue operations teams.

---

Flexible dunning is related to several adjacent terms across subscription management, accounts receivable, and revenue recovery:

• Smart dunning — used by some subscription management platforms to describe AI-assisted or rules-based dunning that adapts its approach based on account characteristics. Functionally equivalent to flexible dunning; the "smart" label emphasises the automation and intelligence layer.
• Adaptive dunning — describes dunning sequences that modify their behaviour based on real-time signals — payment attempt outcomes, card update activity, account engagement — rather than following a fixed pre-defined schedule. Adaptive dunning is the most sophisticated variant of flexible dunning.
• Dunning management — the broader organisational practice of designing, implementing, and continuously improving the payment recovery process; encompasses flexible dunning as its core operational methodology.
• Revenue recovery — used particularly in SaaS and subscription contexts to describe the aggregate financial impact of dunning improvement; focuses on the revenue outcome (how much was recovered) rather than the process (how the recovery was conducted).
• Involuntary churn prevention — describes the outcome objective of flexible dunning: preventing customer loss caused by recoverable payment failures rather than genuine cancellation intent. Involuntary churn prevention is the strategic framing; flexible dunning is the operational mechanism.
• Accounts receivable collections — the broader AR function that encompasses dunning as one of its activities; see accounts receivable collections for the complete framework.

---

Flexible dunning operates across four design dimensions: account segmentation, retry schedule configuration, communication personalisation, and escalation pathway definition.

Account segmentation for dunning treatment

The starting point for flexible dunning design is defining the account segments that will receive differentiated treatment. The most operationally useful segmentation combines two dimensions: payment risk (the probability that this payment failure represents a genuine non-payment risk rather than a recoverable technical failure) and relationship value (the commercial and strategic importance of the account to the organisation).

This two-by-two segmentation produces four treatment categories:

• *High value, low payment risk*: Strategic accounts with strong payment history. Treatment: minimal automated intervention, immediate personal outreach from the account manager, no service interruption without escalation review.
• *High value, elevated payment risk*: Strategic accounts with concerning payment signals (previous failures, overdue balance). Treatment: immediate personal outreach, accelerated escalation, executive sponsorship of recovery conversation.
• *Standard value, low payment risk*: Regular accounts with clean payment history. Treatment: automated retry sequence with standard communication cadence, account manager notification at escalation threshold.
• *Standard value, elevated payment risk*: Regular accounts with payment risk signals. Treatment: aggressive automated retry, escalated communication cadence, earlier service impact triggers.

Retry schedule configuration

Payment retry logic is the technical core of dunning: when is the failed payment retried, how many times, with what interval between attempts, and what card network signals or account characteristics inform the retry timing?

Effective retry scheduling incorporates several principles. Card network signals (decline codes) indicate whether a retry is likely to succeed or waste an attempt: "insufficient funds" suggests waiting for the payment date; "do not honour" suggests contacting the customer before retrying; "card expired" indicates a card update is needed before any retry will succeed. Account payment timing patterns — which day of the month the account typically settles invoices — inform retry timing: retrying on the day after the customer's typical payment date is more likely to succeed than retrying on an arbitrary schedule. Account balance signals — whether the customer's bank account shows activity consistent with funds being available — are increasingly used by sophisticated dunning platforms to time retries for higher success probability.

Communication personalisation

Dunning communications — the emails, in-app notifications, and direct contact attempts that accompany the payment recovery process — should reflect the account context and the relationship. A payment failure email sent to a £500K ARR strategic account that uses the same template as one sent to a £2K account on a trial plan is a relationship management failure, regardless of the financial outcome.

Effective dunning communication personalisation addresses: tone (formal and empathetic for strategic accounts; clear and direct for standard accounts), channel (phone call from the account manager for strategic accounts; email automation for standard accounts), content (account-specific context acknowledging the relationship; specific instructions for resolving the payment issue), and urgency calibration (the appropriate level of urgency communicated at each step of the sequence, based on the account's context and the elapsed time since payment failure).

Escalation pathway definition

The escalation pathway defines what happens when the automated retry and communication sequence does not resolve the payment failure: when does the dunning workflow escalate from automated to human, from account manager to finance team, from finance team to legal, and from service maintenance to service suspension?

Flexible dunning designs escalation pathways that reflect commercial reality: service suspension of a strategic account before the account manager has been given the opportunity to resolve the issue through a direct conversation creates disproportionate relationship damage. Conversely, maintaining full service access for an account with a 90-day overdue balance and no engagement with recovery communications is an unsustainable revenue exposure.

---

SaaS Companies

Pain points: SaaS companies with large volumes of subscription accounts face dunning challenges at two extremes simultaneously. At the enterprise end, rigid dunning sequences create relationship friction with high-value accounts over recoverable payment failures — a card expiry or a bank ACH rejection that could be resolved in one phone call is instead processed through an automated sequence that sends impersonal escalation emails to a CFO who is a strategic partner. At the SMB end, overly lenient dunning sequences allow at-risk accounts to accumulate overdue balances before the system escalates — by the time service is suspended, the account owes three months of subscription fees that are unlikely to be recovered.

Use case: A B2B SaaS platform with 1,200 active accounts segments its dunning into three tiers based on ARR contract value and payment history score. Tier 1 (>£20K ARR and clean payment history): account manager is notified within 4 hours of payment failure; no automated service changes for 21 days; a single personalised email from the account manager is sent within 24 hours. Tier 2 (£2K-£20K ARR): automated retry sequence runs over 14 days; account manager is notified at day 7 if unresolved; service downgrade (reduced seat count) at day 21 if unresolved. Tier 3 (<£2K ARR or payment risk flags): aggressive retry schedule; automated communications at days 3, 7, 10, and 14; service suspension at day 21.

Dunning recovery rates improve from 61% to 79% of failed payments recovered within 30 days. The improvement is driven primarily by Tier 1 recovery (from 74% to 94%) — the personal account manager intervention resolves payment failures that the previous automated sequence was failing to recover — and Tier 3 recovery (from 58% to 72%) as the earlier escalation and service suspension triggers reduce the amount of service delivered against unrecoverable balances.

Financial Services and Fintech

Pain points: Financial services B2B companies face dunning complexity driven by the regulatory dimensions of payment recovery communication. In regulated sectors, dunning communications must comply with financial promotion rules, debt collection regulations, and data protection requirements — a "reminder" email that includes certain language may constitute a regulated communication requiring specific disclosures. Rigid dunning sequences that apply generic templates to all accounts regardless of communication compliance requirements create regulatory exposure.

Use case: A fintech platform with 180 institutional clients implements compliance-reviewed dunning communication templates for each escalation tier, pre-approved by the compliance function. Each template specifies permitted language, required disclosures, and delivery channel constraints. The dunning workflow enforces template selection by account type and jurisdiction: a UK institutional client receives a different communication from a EU corporate client, reflecting the different regulatory frameworks applicable to each. For the highest-value accounts (>£100K ARR), dunning escalation above day 14 triggers a mandatory legal review before any formal demand is issued. Dunning-related compliance incidents decrease from 6 per year to zero following the template implementation.

Manufacturing

Pain points: Manufacturing companies typically manage dunning across a customer base that includes both large, relationship-critical accounts (OEM customers, major distributors) and smaller transactional accounts (spare parts purchasers, smaller service customers). The dunning approach appropriate for an OEM customer representing £2M of annual revenue is fundamentally different from the approach appropriate for a £5K spare parts order — yet without flexible dunning infrastructure, the finance team is applying the same process to both.

Use case: A European equipment manufacturer implements a relationship-based dunning policy. Accounts flagged as "strategic" in the CRM receive a dedicated key account finance manager who personally manages all payment issues; no automated dunning communications are sent without the key account manager's approval. Standard accounts receive a three-step automated dunning sequence with escalation to the regional sales manager at step 2. Transactional accounts receive a fully automated sequence with early service restriction. The policy reduces the time the CFO spends managing ad hoc dunning escalations from strategic accounts — previously a significant source of unplanned management time — by 85%, while improving overall overdue balance recovery from 77% to 91% within 45 days.

Professional Services and Consulting

Pain points: Professional services firms face dunning challenges rooted in the relationship-intensive nature of their business model. A consulting firm that sends an automated payment reminder to a senior client executive — particularly if the tone is impersonal or the context misrepresents the nature of the overdue amount — creates reputational damage that is disproportionate to the value of the payment at issue. Yet manual dunning management for every late invoice is operationally unsustainable as the client portfolio scales.

Use case: A management consulting firm implements a dunning approach that distinguishes between relationship-sensitive and transactional communication. For retainer and multi-phase engagement invoices, all payment follow-up is routed through the engagement partner — the automated system flags the overdue invoice to the partner and provides a suggested communication, but the partner reviews and personalises it before sending. For discrete project invoices below £10K, a fully automated sequence applies, with the engagement manager notified only if the invoice reaches 45 days overdue. The hybrid approach reduces the frequency of relationship-damaging dunning incidents from 8 per quarter to 1 while recovering 88% of overdue balances within 60 days.

Technology and IT Services

Pain points: MSPs face dunning complexity at renewal time: a managed service agreement that comes up for renewal simultaneously with an overdue payment creates a delicate commercial situation. Aggressive dunning that threatens service suspension at the same time as a renewal discussion is underway risks both the payment recovery and the renewal. Without coordination between the billing and commercial processes, the dunning system and the account management team can work at cross-purposes — the account manager is negotiating a multi-year renewal while the billing system is sending a service suspension warning.

Use case: A UK-based MSP implements a dunning-renewal coordination rule: any account where a renewal opportunity is flagged in the CRM as active (within 90 days of renewal) automatically triggers a 30-day dunning hold — the dunning sequence is paused and the account manager is notified of the overdue balance to incorporate into the renewal conversation. The account manager is accountable for resolving the overdue balance as part of the renewal negotiation (typically by including a payment plan or past-due clearance condition in the renewal terms). The coordination rule eliminates 23 instances per year where the dunning sequence and renewal negotiation were operating in conflict, and improves renewal conversion for accounts with overdue balances from 48% to 67%.

---

• Higher payment recovery rates through context-appropriate treatment. The most direct benefit of flexible dunning is improved payment recovery: when strategic accounts receive personal intervention rather than automated sequences, and at-risk accounts receive appropriately escalated treatment rather than lenient patience, the aggregate recovery rate improves. The improvement is most pronounced at the extremes — the highest-value accounts and the highest-risk accounts both benefit significantly from treatment differentiated from the middle-tier default.
• Reduced involuntary churn and improved net revenue retention. Involuntary churn from payment failures is directly reduced when dunning sequences are effective: payment failures are recovered before they become cancellations. For companies tracking net revenue retention as a key metric, the improvement in dunning recovery directly improves NRR by reducing the revenue lost to recoverable payment failures rather than genuine customer dissatisfaction.
• Relationship preservation for strategic accounts. Impersonal automated dunning sequences sent to senior executives at strategic accounts create relationship damage that persists beyond the payment issue itself. Flexible dunning that routes strategic account payment issues through the account manager preserves the commercial relationship by ensuring that payment recovery is handled in the context of the ongoing partnership rather than as an isolated transactional event.
• Finance team efficiency through appropriate automation. Flexible dunning does not mean more manual work — it means better-targeted manual work. Standard and transactional accounts are handled entirely through automation; the human intervention is concentrated on the accounts where it adds the most value (strategic accounts) and where it is most urgently needed (high-risk accounts). Finance team time on dunning-related activities typically decreases even as recovery rates improve.
• Reduced revenue exposure from high-risk accounts. For accounts with genuine payment risk signals, flexible dunning enables earlier escalation and earlier service impact decisions — reducing the amount of service delivered against an unrecoverable balance. This reduces both the direct revenue write-off and the indirect operational cost of providing service to accounts that will not pay for it.
• Compliance risk reduction in regulated industries. Flexible dunning enables compliance-reviewed communication templates to be applied based on account jurisdiction and sector, ensuring that dunning communications meet the regulatory requirements applicable to each account type without requiring manual compliance review of every communication.
• Data foundation for continuous dunning improvement. Every dunning interaction produces data: which retry timing succeeded, which communication triggered a response, how long accounts in each segment took to resolve payment failures. Systematic collection and analysis of this data enables continuous improvement of the dunning design — which retry schedules work best for which card types, which communication templates produce the fastest resolution, and which escalation triggers are set at the optimal threshold.
• Commercial and billing process coordination. Flexible dunning enables rules-based coordination between the billing recovery process and other commercial processes — renewal negotiations, expansion discussions, support escalations — ensuring that the dunning system and the commercial team are working in concert rather than in conflict.

---

Payment history data — the complete record of all payment attempts, successes, and failures for each account, including the decline codes and payment methods involved — is the foundational dataset for dunning risk segmentation. Accounts with clean multi-year payment histories are treated very differently from accounts with recurring payment issues; payment history data provides the objective basis for this differentiation.

Account health signals from commercial engagement data enrich the dunning segmentation with signals that billing data alone cannot provide. An account that has recently been active in commercial discussions, shown product engagement, and met with the account management team is a different risk profile from an account that has gone dark across all engagement channels — even if their payment histories are identical. Signalon's analytics module provides the engagement signal data that enables this enrichment.

Contract value and segment data from the CRM determines the tier assignment and therefore the dunning treatment applied to each account. Contract value, customer segment, and account strategic status are the primary segmentation criteria that determine which dunning pathway an account enters.

Decline code and payment processor data provides the technical intelligence that informs retry scheduling. Different decline codes warrant different retry approaches: some indicate a temporary technical failure that will resolve on immediate retry; others indicate that no retry will succeed without customer action (card update, bank contact, payment method change).

Resolution timeline data — how long accounts in each segment typically take to resolve payment failures — enables calibration of dunning sequence timing to realistic resolution patterns. If strategic accounts with clean payment histories resolve payment failures in an average of 3.2 days, the dunning sequence can be designed with patience at early stages; if at-risk SMB accounts typically do not resolve failures without service impact, the escalation timeline can be calibrated accordingly.

---

Billing and Subscription Management Systems

The billing system is the operational foundation of dunning: it generates the failed payment trigger, executes the retry attempts, and implements the service impact decisions that result from unresolved payment failures.

• Failed payment event data — including the payment amount, the decline code, the payment method type, and the account identifier — must be passed to the dunning workflow in real time to initiate the appropriate sequence immediately.
• Retry execution — the technical act of resubmitting a payment to the payment processor — should be orchestrated by the dunning system based on configurable retry schedule rules, not by the billing system's default retry logic.
• Service impact actions — account downgrade, feature restriction, service suspension — must be executed by the billing/provisioning system based on dunning workflow triggers, ensuring that the service impact decision is governed by the dunning policy rather than by billing system defaults.
• Signalon's analytics module integrates with billing system data to surface overdue balance trends and dunning recovery rates alongside commercial engagement metrics.

CRM Platforms

CRM integration connects the dunning workflow to the commercial context that determines account segmentation and treatment.

• Account segment, contract value, and strategic status from the CRM determine the dunning tier assignment at the point of payment failure.
• Account manager assignment from the CRM ensures that personal dunning interventions are routed to the correct account contact without requiring manual lookup.
• Payment failure notification to the account manager — triggered when an account enters their managed portfolio's dunning sequence — ensures that the commercial team is aware of payment issues in their accounts before they escalate.
• Renewal opportunity status from the CRM enables dunning-renewal coordination rules: accounts with active renewal opportunities receive modified dunning treatment that preserves the commercial conversation.

Analytics and Revenue Intelligence

Analytics integration transforms dunning activity data from a compliance record into a continuous improvement resource.

• Dunning recovery rate by tier and segment provides the performance data that validates whether the current segmentation and treatment design is producing the intended outcomes.
• Payment failure frequency and resolution time trends reveal whether payment recovery is improving or deteriorating over time, enabling early identification of systemic issues (a payment processor reliability problem, a change in customer payment behaviour) before they become material.
• Signalon's analytics module provides the account engagement signals that enrich dunning segmentation and the portfolio-level analytics that enable systematic dunning performance management.

Customer Communication Platforms

Email, in-app notification, and direct messaging platforms deliver the dunning communications that form the customer-facing layer of the recovery process.

• Communication delivery confirmation — whether emails were delivered, opened, and acted upon — provides feedback signals that enable dunning sequence adaptation: if a tier-2 account has opened the first dunning email but not acted, a different follow-up communication is warranted than if the email was not opened.
• Template management with variable personalisation fields — account name, invoice amount, payment method, account manager contact details — enables mass-personalised dunning communications at the standard tier while maintaining the personal touch that relationship-sensitive accounts require.
• Channel preference data — whether accounts prefer email, phone, or in-app notifications — enables the dunning communication to reach accounts through their most responsive channel.

---

• Configurable segmentation without engineering dependency. The ability to define and modify dunning tiers, retry schedules, and communication sequences without requiring developer involvement is critical for finance and revenue operations teams that need to adapt their dunning strategy as their account base evolves. Evaluate whether the platform provides a business-user-accessible configuration interface.
• Intelligent retry scheduling using decline code logic. Platforms that retry all failed payments on a fixed interval regardless of decline code are wasting retry attempts and reducing recovery rates. Evaluate whether the platform supports decline-code-aware retry scheduling that optimises retry timing based on the specific reason for payment failure.
• CRM integration for account context at the point of failure. Dunning segmentation that relies on manual account tier tagging in the billing system will always lag behind the CRM's more current view of account status. Evaluate whether the platform can pull real-time account context from the CRM at the point of payment failure, rather than relying on static billing system attributes.
• Communication template management with compliance controls. For businesses operating in regulated industries or multiple jurisdictions, the dunning communication system must support compliance-reviewed templates with versioning and approval workflows. Evaluate whether the platform provides template governance capabilities alongside the personalisation features.
• Coordination with renewal and commercial workflows. The ability to define dunning rules that respond to commercial context — pausing sequences for accounts in active renewal discussions, routing escalations through the account manager — is the feature that distinguishes flexible dunning from standard dunning with a few configuration options. Evaluate whether the platform supports this commercial coordination natively.
• Analytics and recovery rate reporting. Dunning improvement is a continuous process that requires systematic performance measurement. Evaluate whether the platform provides dunning recovery rate analytics by tier, segment, payment method, and time period — enabling the finance team to identify which elements of the dunning design are performing and which require adjustment.

---