What Is Dunning? A Simple Guide for Small Businesses

If you sell software, you have probably heard “dunning” in the context of failed card charges. If you run a project-based business, the word might sound foreign. In both worlds, the core idea is the same: a defined process to bring an unpaid balance back on track with a series of clear communications and internal actions. For paper-and-email B2B invoices, dunning is less about retrying a card and more about a respectful reminder sequence that does not let receivables drift.

A plain definition

Dunning is the structured follow-up for money that was expected but not received under agreed terms. It includes the timing, channels, and templates you use to ask for status, and the internal rules for when a human should intervene. It is a process label, not a tone: you can run customer-friendly dunning with calm language, or you can run harsh dunning that damages trust. The word does not require either; your policy decides the voice.

Dunning compared to debt collection

Dunning, as product teams use the term, is usually not a substitute for a licensed collection agency, legal demand letters, or court processes. It is the layer before (or sometimes parallel to) those steps where you are still working inside a business relationship. Debt collection, in everyday language, often means third-party collection or a formal program with regulatory obligations depending on your country. Your automated dunning for outstanding invoices should stop short of language you are not actually willing to back with process. When you need true collections, you change tools, documentation, and probably counsel—not just a sharper email template.

Reminder cadence: enough structure to be fair

A good cadence has no surprises. If you always send a payment reminder after the due date at a steady interval, customers learn what to expect. If you are silent for three weeks, then send an angry message, you train them that deadlines are not real. Many teams pair a pre-due nudge, a first overdue check-in, and then staged follow-ups. That is exactly the shape good dunning software encodes, without requiring your team to remember the calendar.

Customer-friendly dunning in practice

• Use neutral facts: number, amount, days past term—without moralizing.
• Offer one path to fix errors: a single point of contact for invoice corrections.
• Be explicit about business consequences that are true: work pauses, late fees, or credit hold, per contract.
• When the customer is in good faith but late, a short phone call can beat five clever emails.

The software angle: dunning without becoming “that vendor”

Dunning software in SMB contexts should not turn you into a faceless collection bot. The point is to keep cadence, tone, and history consistent across many threads. For businesses that work in email, an email-native approach—reminders that look like the rest of your communication—often lands better than surprising someone with a portal they have never used. That is the philosophy behind tools like Arkvela: stay in your customer’s primary channel, keep reminders professional, and use automation to remove forgetfulness, not to replace judgment on disputes. If you are mapping keywords for growth, dunning software sits next to “invoice reminder software” and “accounts receivable automation”; they are adjacent labels for overlapping jobs.

Try Arkvela on a real receivable path

You can read theory forever; the useful test is whether a tool fits how you already send invoices. Arkvela’s live demo is the fastest way to see email-native follow-up in motion without committing to a full migration. You will not get a fake statistic from us on “percent faster”—you will get a product flow you can compare to the way you chase invoices today. If this guide was useful, the resources on how to reduce late payments in a small business and on accounts receivable automation round out the operational side.