Create an Airwallex account today
Get started
HomeBlogBilling
Published on 6 August 20269 minutes

What is dunning management? A 2026 guide for Malaysian businesses

Cherie Foo
Growth Content Manager

What is dunning management? A 2026 guide for Malaysian businesses

Key takeaways:

  • Dunning management is the process of recovering failed or overdue payments through automated reminders, retries, and escalation.

  • For Malaysian businesses, involuntary churn from failed payments is a growing risk as more SMEs move to recurring billing or credit-term invoicing.

  • Airwallex's Subscription Management and Billing tools come with built-in retry logic and reminders, so you don't need a separate dunning tool.

Dunning management is how you recover money from customers after a payment fails or an invoice goes unpaid. It combines automated reminders, payment retries, and a clear escalation path, so a missed charge doesn't turn into a lost customer.

For Malaysian businesses, this matters more than it used to. More SMEs now bill customers on a recurring basis, whether through SaaS subscriptions, retainer-based services, or long-term supply contracts.

Every one of these models depends on payments actually going through, and payments fail more often than most business owners expect.

This guide explains what dunning management means, how the process works, and what to do differently if you're billing customers in Malaysia.

What is dunning management?

Dunning management is the process a business uses to recover a payment after it fails or an invoice goes unpaid. It covers everything from the first automated reminder to the final attempt before an account is paused or a debt is escalated further.

The word "dunning" comes from an old term for making repeated demands for payment. In a modern billing context, it rarely means letters or phone calls anymore. Most dunning today runs through email, SMS, in-app notifications, and automatic retries on a stored card or bank mandate.

Dunning is often confused with debt collection, but the two sit at different points in the payment lifecycle. Here’s the difference:

  • Dunning happens early and is usually automated. Its goal is to fix the problem quietly and keep the customer, whether that means retrying a declined card or reminding someone their invoice is overdue.

  • Debt collection happens much later, after dunning has failed repeatedly, and it is typically manual, more formal, and focused on recovering the money rather than preserving the relationship.

For a subscription business, dunning usually deals with failed card payments. For a business that invoices on credit terms, it deals with unpaid invoices. Both versions follow the same logic: notify, retry, and escalate only if nothing else works.

Why dunning management matters for Malaysian businesses

Failed payments are common, not exceptional. Globally, they cost the economy more than US$118 billion in 2020, and 80% of businesses that experienced high volumes of failed payments said they lost customers as a result.¹

Without a process to recover those payments, that revenue is simply lost.

In Malaysia, failed payments can happen for several reasons:

  • Cards expire or are reissued, often after fraud checks, causing recurring payments to fail.

  • FPX e-mandates can lapse if customers switch banks or don't renew their authorisation.

  • Malaysian-issued cards may see higher decline rates on international billing platforms that aren't optimised for local banks.

For businesses that invoice on credit terms, the challenge is different. Overdue invoices tie up cash flow, delay supplier payments, and become harder to collect the longer they remain unpaid.

Whether it's a declined subscription payment or an overdue invoice, the outcome is the same: revenue is at risk. That’s where dunning management comes in: this helps you recover your payments before they become permanent losses.

How the dunning process works

A complete dunning process runs in three stages, whether you're managing subscription payments or unpaid invoices.

Stage 1: Prevention

Prevention happens before a payment actually fails. This means flagging cards that are close to their expiry date and prompting the customer to update their details, or reminding a customer whose FPX e-mandate is about to lapse to renew it.

For invoice-based businesses, this looks like a reminder sent a few days before the due date rather than after.

Prevention catches the easiest failures before they happen, and it's the cheapest stage to run because it needs no retries or escalation at all.

Stage 2: Notification and retries

Once a payment does fail, the system notifies the customer and starts retrying the charge.

A good retry schedule doesn't hammer the same card repeatedly; it spaces attempts out over a few days to a few weeks, timed around when a retry is more likely to succeed, such as after a payday.

Notifications should be short, clear, and give the customer a one-click way to update their payment details or settle the invoice. For unpaid invoices, this stage is where reminder emails escalate gradually from a friendly nudge to a firmer follow-up.

Stage 3: Escalation

Escalation only kicks in once retries and reminders have failed. At this point, you decide whether to pause the account, restrict access, or cancel the subscription outright.

Pausing is usually the better first move for customers who look inattentive rather than unwilling to pay, since it keeps their data intact and makes it easy for them to come back.

For overdue invoices, escalation might mean a firmer notice, a call from your team, or, as a last resort, referring the account to formal collections.

Manual vs automated dunning management

You can run dunning by hand or let software handle it. The right choice mostly comes down to how many customers or invoices you're managing.

Aspect

Manual dunning

Automated dunning

Retry timing

Set and triggered by a person, often inconsistently

Runs on a fixed schedule, timed for the best chance of success

Communication

Emails or calls written and sent one at a time

Templated reminders sent automatically across email, SMS, or in-app

Consistency at scale

Breaks down once volume grows past a handful of accounts

Handles hundreds or thousands of accounts the same way

Time cost

High: someone has to track and chase every case

Low: the system runs in the background

Best suited for

Very small customer bases or high-value accounts needing a personal touch

Subscription businesses and any business billing at volume

Manual dunning can still make sense for a small number of high-value clients, where a personal follow-up matters more than speed.

But once you're managing more than a handful of recurring payments or invoices, automation becomes less about convenience and more about not losing revenue to accounts nobody had time to chase.

Dunning management best practices

Recovering failed payments requires the right mix of timing, automation, and customer communication. Here are the best practices to follow:

1. Use multiple channels

Email is still the default for payment reminders, but it's not the only channel that matters. Many Malaysian customers check WhatsApp and SMS more often than email, and in-app notifications catch people who are already using your product.

Sending the same reminder across two or three channels increases the odds someone actually sees it before you have to escalate.

2. Time retries around local pay cycles

Most Malaysian salaries are paid around month-end, so a card retry attempted right after payday is more likely to succeed than one run mid-month.

The same logic applies to invoice reminders for B2B clients, whose own payment runs often follow a similar monthly rhythm.

For FPX e-mandates, send a renewal reminder well before the mandate lapses, not after a payment has already failed because of it.

3. Keep communications respectful and compliant

Dunning only works if customers trust the message.

Keep the tone neutral and helpful rather than accusatory, and make it easy for someone to fix the issue in one click. When you store payment details, contact information, or billing history to run these reminders, handle that data in line with Malaysia's Personal Data Protection Act requirements.

Sending too many reminders too quickly can also backfire, pushing a customer toward cancelling rather than fixing the problem.

How Airwallex helps Malaysian businesses manage dunning

Airwallex helps you recover failed payments without adding a separate dunning tool to your billing workflow.

  • Recover failed subscription payments automatically. Subscription Management includes built-in smart retries and payment reminders, helping you recover more failed card payments with less manual work.

  • Manage subscriptions and invoices in one place. Whether you're collecting recurring payments or sending one-off invoices, Billing keeps reminders, payment collection, and reconciliation in a single platform.

  • Scale as your business grows. Accept subscription payments in 180+ countries with Airwallex.

Recover failed payments automatically with Airwallex
Sign up now

Frequently asked questions (FAQs)

What is a dunning letter?

A dunning letter, or dunning notice, is a message sent to a customer letting them know a payment has failed or an invoice is overdue, along with what they need to do next. Today, "letter" usually means email, SMS, or an in-app notification rather than a physical letter. The most effective ones are short, neutral in tone, and include a direct link to update payment details or settle the invoice.

How long should a dunning sequence run?

Most dunning sequences run over two to four weeks, weighted toward the first two weeks after a payment fails, with a handful of reminders spaced out rather than sent all at once². Running the sequence too short risks giving up on payments that would have recovered with more time, while running it too long delays the decision to pause or cancel an unresponsive account. The right length also depends on whether you're chasing a subscription payment or a B2B invoice, since invoice payment cycles tend to run longer.

What causes payment failures in Malaysia?

The most common causes are expired or reissued cards, insufficient funds, and lapsed FPX e-mandates. Malaysian-issued cards can also see higher decline rates on platforms not built around local banks, and this is one reason Airwallex supports local payment methods directly rather than relying solely on international card rails. For invoice-based businesses, late payment is more often a cash flow or oversight issue than a technical failure.

Is dunning the same as debt collection?

No. Dunning happens earlier in the payment lifecycle and is usually automated, focused on fixing the issue and keeping the customer. Debt collection happens later, after dunning has failed, and is typically manual and focused on recovering the money rather than the relationship.

Can dunning management work for unpaid invoices as well as subscriptions?

Yes. The same notify, retry, and escalate structure applies whether you're recovering a failed card payment or chasing an overdue invoice. The main difference is timing and tone: invoice reminders usually follow a slower cadence tied to payment terms, while subscription dunning reacts immediately to a failed charge. For more on managing unpaid invoices specifically, see our guide to accounts receivable in Malaysia.

Is there a good benchmark for dunning recovery rates?

There isn't one universal benchmark, because recovery rate can be measured in different ways. Looking at the percentage of failed payments successfully recovered after a genuine retry attempt is more useful than a raw recovery rate that includes payments you never actually tried to fix. Tracking the trend over time, and by failure reason, tells you more than comparing your number to an industry average.

Sources

  1. https://stripe.com/resources/more/dunning-management-101-why-it-matters-and-key-tactics-for-businesses

  2. https://baremetrics.com/blog/dunning-management

This publication does not constitute legal, tax, or professional advice from Airwallex nor substitute seeking such advice, and makes no express or implied representations / warranties / guarantees regarding content accuracy, completeness, or currency. This publication is not intended to be relied on for the purpose of making a decision about a financial product and users should verify details independently.

All comparisons and information contained in this publication reflect only Airwallex’s own research using public documentation on the stated dates and have not been independently validated.

Product features, pricing and other details are subject to change. All third-party names, products, and logos are trademarks of their respective owners and are referred to for identification and compatibility purposes only. If you would like to request an update, feel free to contact us at [[email protected]].

Airwallex (Malaysia) Sdn. Bhd., a company incorporated under the laws of Malaysia with company registration number 201801007747 (1269761-X), is regulated as a licensed remittance business under the Money Services Business Act 2011 (Licence number 00743 with an expiry date of 3 August 2028, an E-Money Issuer and a registered merchant acquirer under the Financial Services Act 2013.)

Cherie Foo
Growth Content Manager

Cherie is a Growth Content Manager at Airwallex, where she develops content for businesses in Singapore and across Southeast Asia. She focuses on turning complex topics like cross-border payments, business accounts, and spend management into clear, practical guides that help founders and finance teams make confident decisions.

Posted in:

Billing
Share
In this article

Create an Airwallex account today

Share

Related Posts

SST invoice format Malaysia: Requirements & tax codes (2026)
Billing

SST invoice format Malaysia: Requirements & tax codes (2026)

8 minutes

What is Wero? A guide for Malaysia merchants (2026)
Online payments

What is Wero? A guide for Malaysia merchants (2026)

10 minutes

Usage-based pricing model: 2026 guide for Malaysian SaaS
Billing

Usage-based pricing model: 2026 guide for Malaysian SaaS

8 minutes