Key Takeaways
- Count every touch from the due date, not the invoice date; the first overdue touch comes within 7 days whatever the terms.
- In an Australian field experiment, a reminder letter raised the probability of payment by about 25 percentage points; sending it one, two or three weeks late made no difference after seven weeks (Gillitzer and Sinning, IZA, 2018; journal version 2020).
- Published day counts are convention, this page’s matrix included: test two cadences on matched customers for eight weeks.
- German law needs one Mahnung at most; a business debtor defaults at the latest 30 days after the due date and receipt of the invoice (§ 286 BGB, current text 2026).
- CollectPulse from Transformance actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams (Transformance customer data, 2026).
In This Article
- Key Takeaways
- What dunning cadence works for B2B customers?
- How do payment terms change the cadence?
- How should the cadence differ by customer segment?
- What does the evidence say, and what is only convention?
- When does an invoice leave the cadence?
- How do German Mahnstufen and ERP dunning levels map onto the cadence?
- How do you set up and automate your own cadence?
What dunning cadence works for B2B customers?
A working B2B dunning cadence counts from the due date: remind before it, chase within a week, call by day 14 to 30, formal notice by day 30 to 60.
B2B dunning cadence by segment (net 30; days relative to the due date; a starting policy, not a benchmark)
Counted from the due date, not the invoice date. Every cell is a design choice.
A dunning cadence is the schedule of channels, messages and owners that moves an overdue invoice from a pre-due reminder to a formal notice, counted from the due date; dunning letters are its written part.
On average, executives surveyed in 20 European countries say 12.13% of their revenues are paid late, above the 12.08% they could receive late without hurting operations (Intrum, European Payment Report 2026, April 2026; 8,385 executives).
No published study identifies a best cadence; the matrix is our policy, built on the evidence below and on common practice.
Worked example (illustrative, USD). An invoice of USD 48,000 issued October 31 on net 30 falls due November 30. The mid-market row gives six touches:
- November 27: reminder email; November 30: due-date email.
- December 7: first overdue email (is it in the next payment run?).
- December 14: collector call for a dated commitment.
- December 30: formal notice; January 14: final notice from a named owner.
In an AR aging report, this invoice moves through the 1-30 and 31-60 day delinquency buckets; the cadence decides what happens inside each.
How do payment terms change the cadence?
Longer terms move the pre-due check earlier and stretch the later stages; the first overdue touch stays within a week, because the invoice is late on the due date.
Every row also gets a due-date message. Days are our design, not a benchmark. The rule behind them:
- Pre-due check = the customer’s approval lead time. Two days suffice on net 15; on net 90 you need two weeks to fix a missing purchase order before the payment run.
- First overdue touch = 7 days at most (3 on net 15). A silent week after the due date is a week of free financing.
- Later stages stretch less than the terms. The final notice lands at day 45 on net 30 and day 90 on net 90, not day 135.
Why not stretch the whole sequence for long terms? The one measured timing result found that earlier reminders brought faster payment with no loss in the share that eventually paid (Gillitzer and Sinning, IZA, 2018). It studied tax debts, so it supports the direction only.
Long terms need the earlier check because an invoice that never entered the customer’s approval workflow (wrong PO, missing goods receipt) surfaces only when late; that is our reading from practice. Many AP teams pay in weekly or monthly runs, so ask for the run calendar at onboarding.
How should the cadence differ by customer segment?
Segment decides who acts and how firmly: the system sends early touches, a collector calls from day 14, and an account owner joins strategic accounts before anything formal.
Segments are rules, not labels: revenue with you, average days past due over 12 months and invoice size, reviewed quarterly. To rank invoices inside a segment by expected cash, see how to prioritize AR collections with AI.
Channel follows the stage:
- Email for the early touches, if it arrives (why dunning emails land in spam).
- Phone from the human-contact stage.
- The customer’s AP portal, where one is used: check the invoice status before you chase.
- Formal notices in writing, for the record.
A person takes over at the human-contact stage, and at once when a reply raises a dispute. Wording per stage (helpful, direct, firm, formal) is in the dunning email templates.
A human collector makes 15-20 calls a day; the Transformance AI calling agent makes 15-20 calls an hour in 70+ languages (Transformance platform data, 2026). Calling 600 long-tail invoices at day +15 would take a collector 30 to 40 working days (illustrative), so that call can be automated while the strategic call at +21 stays with the account owner (AI calling agent guide).
Who may call a customer’s CFO, stop deliveries or refer to an agency belongs in an escalation matrix. Groups keep one baseline with entity overrides: see enterprise dunning automation across entities.
What does the evidence say, and what is only convention?
Only the direction is evidenced: in an Australian experiment a reminder raised payment probability by about 25 percentage points, and earlier reminders sped payment; every day count is convention.
Gillitzer and Sinning studied business taxpayers with a compliant payment history who had missed their 26 May 2017 tax deadline. Cases were randomly allocated to a reminder letter one, two or three weeks after the due date, or to a control group with no letter for the seven-week trial (IZA Discussion Paper 11599, June 2018; Journal of Economic Behavior & Organization, 2020). A simple letter raised the probability of payment by about 25 percentage points. Moving it within those three weeks had no effect on payment within seven weeks of the due date; early letters meant faster payment.
The limits: tax debts owed to an authority, good-history taxpayers, one letter each. No source we found measures whether a call on day 14 beats day 10, whether three emails beat two, or whether a firmer tone lifts payment.
To get your own evidence, run two cadences inside one segment for eight weeks, split by odd and even customer number, and compare days to pay, promises kept, reply rate and disputes raised. Never compare across segments.
Read the cadence with four numbers: overdue invoices touched within 24 hours, promises to pay kept (how AI tracks promise to pay), average days delinquent and the collections effectiveness index. Formulas are in the AR collections KPI guide; see also which AR metric to use when DSO misleads.
Some invoices are late because of the invoice itself (wrong PO, missing proof of delivery): see the DSO reduction playbook.
When does an invoice leave the cadence?
An invoice leaves the cadence on a dispute, a dated promise to pay, a partial payment or a hard-stop rule; each exit needs an owner and a return date.
- Dispute. Route the disputed amount to the dispute and deductions track with a named owner; the undisputed part keeps running (AI dispute management in AR).
- Promise to pay. Hold all touches until the promised date. If it breaks, resume the next day one stage further on.
- Partial payment or unapplied cash. Match the cash first, then chase the rest. A customer who has paid must never get a reminder, so cash application runs before the dunning run (partial payments and deductions).
- Hard stop. A delivery stop, a change of terms or an agency referral is a decision a person makes, within limits by amount, entity and customer.
- No response. Silence after the formal notice is its own case: see when a B2B customer does not respond.
How do German Mahnstufen and ERP dunning levels map onto the cadence?
German law needs one Mahnung at most: under § 286 BGB a business debtor defaults at the latest 30 days after the due date and receipt of the invoice.
The statute in brief (gesetze-im-internet.de, current text, read October 2026); statute text, not legal advice:
- A debtor who does not pay after a Mahnung sent after the due date is in default, Verzug (§ 286 (1) BGB).
- No Mahnung is needed where the payment date is fixed by the calendar or can be calculated from an event such as delivery (§ 286 (2) nos. 1 and 2).
- A debtor of a payment claim defaults at the latest 30 days after the due date and receipt of an invoice (§ 286 (3)); consumers only if the invoice says so.
- Between businesses, default interest is 9 percentage points above the base rate, plus a flat EUR 40 (§ 288 (2), (5) BGB); the calculation is in late payment interest in Germany.
- Terms over 60 days after receipt of the goods or service (or of a later invoice) are valid only if expressly agreed and not grossly unfair to the supplier (§ 271a (1) BGB): relevant to the net 90 row.
Practice adds a ladder the law does not require. The Dortmund chamber of commerce writes that one Mahnung is legally required, up to three are common, and writing is advisable because the supplier carries the burden of proof (IHK Dortmund, “Kaufmännisches Mahnen”, April 2021). The number of Mahnstufen is a business choice.
In SAP, the dunning run (Mahnlauf) turns the grid into letters. A dunning procedure, entered in the customer’s master data, holds up to nine dunning levels. An item’s level follows its days in arrears against the net due date and rises by one at a time, so no level is skipped. Grace days keep an item out of the run just after the due date but are not counted in the days in arrears. The dunning interval is the minimum number of days before an account is dunned again. SAP’s example uses levels at 7, 14, 21 and 28 days, two grace days and a seven-day interval (SAP Learning, page undated, read October 2026).
So a different cadence per segment means a different dunning procedure, and with a seven-day interval the run sends at most one letter a week per account: pre-due reminders, calls and closer touches sit outside it. More: receivables management in the German Mittelstand.
How do you set up and automate your own cadence?
Set up a dunning cadence in six steps: segment, anchor to the due date, set days per term, assign owners and channels, define exits, then measure for eight weeks.
Six steps to your own dunning cadence
- Segment customers by revenue with you, payment history and invoice size.
- Anchor every touch to the due date, not the invoice date.
- Set days per payment term: early first touch, longer gaps for longer terms.
- Assign a channel and an owner to each stage: system, collector, account owner.
- Define exits: dispute, promise to pay, partial payment, hard stop.
- Run it for eight weeks, compare days to pay and promises kept per segment, and adjust.
CollectPulse from Transformance actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams, and Vero handles 60-80% of routine touches (Transformance customer data, 2026). The AI calling agent identifies itself as AI at the start of every call.
Vero works on Customer 360, one graph per customer that holds payment history, promises to pay, disputes and deductions: the context a collector needs before each touch. Transformance customers capture 3x more promises to pay than with manual work, and DSO falls 8-12 days on average (Transformance customer data, 2026).
When an exception comes up, such as a short payment, Vero investigates it from Customer 360 plus internal and external sources and proposes the next step with the evidence; a person approves, within thresholds by amount, entity and customer.
Transformance reads open items and customer master data and writes updates back, including reversals. SAP S/4HANA, SAP ECC, NetSuite, Dynamics 365 and Odoo run in production with customers; Oracle and Infor are supported. The ERP connection typically takes 2-3 days; your IT team may be involved (ERP integrations guide). To size a cadence on your own aging, Book a Call.
Who Transformance is for
- ERP: finance teams that run AR in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations or Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.
Conclusion: write the policy, then test it
Count from the due date, chase early, let terms stretch the later stages and segment decide who calls. Treat every day count, ours included, as a hypothesis to test. Book a Call.
Key terms
- Dunning: the sequence of reminders and notices for overdue invoices, with rising firmness.
- Payment terms: the agreed days to pay; the clock every cadence is anchored to.
- Past due: an invoice not paid by its due date.
- Promise to pay: a customer’s stated payment date; it pauses the cadence until then.
- Escalation matrix: who takes over at which stage, with what authority.
- Delinquency bucket: an aging band, such as 1-30 days past due, that sets the next action.
Related guides
- Which ERP systems does Transformance integrate with?
- Late payment interest in Germany: how do Verzugszinsen work?
- When does DSO mislead, and which AR metric should you use instead?
- Dunning process: email templates and automation
- Enterprise dunning automation across multiple entities
Frequently Asked Questions
How many dunning reminders should you send before escalating a B2B invoice?
Our starting policy is three to four written touches over 30 days before a formal notice, set per segment and term in the matrix above; in Germany the law requires only one Mahnung.
When should a person take over from automated reminders?
At the human-contact stage: around day 14 for mid-market payers, day 21 for strategic accounts and day 7 for new customers, and at once when a reply raises a dispute.
How does the dunning cadence change for net 60 or net 90 terms?
Move the pre-due check to 7 to 14 days before the due date and stretch the later stages, but keep the first overdue touch within a week, because the invoice is late on the due date whatever the terms.
How many Mahnungen does German law require, and when is a debtor in default?
One Mahnung is enough by statute. A business debtor is in default at the latest 30 days after the due date and receipt of the invoice, or without any Mahnung when the payment date is fixed by the calendar (§ 286 BGB). Statute text, not legal advice.
Which ERP systems does Transformance work with?
SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo, all running in production with customers; Oracle and Infor are supported. The ERP connection typically takes 2-3 days; your IT team may be involved.
Which companies is Transformance built for?
Mid-market to large enterprise teams with 250 to 2,000+ employees, handling from under 1,000 to over 100,000 payments a month, including groups with several entities and shared service centers.
How long does it take, and what does it cost?
A full rollout takes up to 4-8 weeks; a proof of value runs 4-5 weeks on one entity. Cost depends on scope (cash application alone or the full order-to-cash) and the number of entities: Book a Call.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
