SAP Dunning Process Step by Step

What is the SAP Dunning Process?

The SAP dunning process step by step is one of those things that sounds scary at first but makes perfect sense once you understand it. Essentially, dunning is SAP's automated way of chasing customers for payment on overdue invoices. Think of it as your friendly but persistent payment reminder system that sends letters, emails, or blocks further credit—without you having to manually track every overdue invoice.

In SAP, dunning lives in the Accounts Receivable (AR) module and is managed through transaction code F150. The beauty of dunning is that it's completely customizable: you decide how many reminder levels you want, when each reminder goes out, and what happens at each stage (like suspending deliveries or blocking credit). If you've ever wondered how large organizations stay on top of thousands of invoices, dunning is a big part of that answer.

Let's walk through how it works in practice, starting with the configuration and then moving into execution.

Step-by-Step Guide to SAP Dunning Process Configuration

Step 1: Access the Dunning Configuration Area

First, you'll need to get into the right place. Open transaction code F150 in SAP. This is your command center for all dunning activities. You'll see options like "Dunning Area," "Dunning Levels," "Dunning Procedures," and "Dunning Letters." Start by accessing Customizing → Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Dunning in transaction SPRO (SAP Project Repository).

Step 2: Define Your Dunning Area

A dunning area is a way to segment how you handle reminders for different customer groups or regions. You might have one area for domestic customers and another for international ones, for example. In SPRO, navigate to Define Dunning Areas. Give your dunning area a code (usually something like "01" or "DE" for domestic) and assign it a name.

The dunning area is stored in table TVDT (Dunning Area Master). Each dunning area can have different procedures, so you have real flexibility here. You'll assign this dunning area to your company code later.

Step 3: Set Up Dunning Levels

This is where you define the escalation path. Most companies use 2–4 dunning levels:

• Level 1: First friendly reminder (e.g., 10 days overdue)
• Level 2: Firmer reminder with fees (e.g., 20 days overdue)
• Level 3: Final notice before action (e.g., 30 days overdue)
• Level 4: Credit block or legal referral (e.g., 45+ days overdue)

For each level, you define:

• Days in Arrears: How many days overdue before this level triggers (stored in table DUNV)
• Dunning Block: Whether to block further orders, deliveries, or credit
• Dunning Fee: Any additional charge to apply
• Letter Text: The tone and content of the reminder
• Automatic Processing: Whether this level runs automatically or needs manual intervention

Step 4: Assign Dunning Procedures to Company Codes

A dunning procedure is a bundle of levels with specific rules. You need to assign your dunning procedure to your company code so SAP knows which procedure to use when dunning runs. This is done in SPRO → Define Dunning Procedures and links your company code to your dunning area. The table you're updating is TVDP (Dunning Procedure Assignment).

Step 5: Create or Customize Dunning Letters

Letters are the communication tool of dunning. SAP comes with standard letter templates, but you'll want to customize them for your business. Access transaction FDITTEXT or go through SPRO → Dunning Letter Texts. You can control:

• Salutation and tone
• Payment deadline
• Fees or interest charges
• Footer and legal disclaimers

These letters are tied to dunning levels and can be printed or emailed directly from SAP.

Executing the Dunning Run

How to Run Dunning in SAP

Once you've configured your dunning procedure, actually running dunning is straightforward:

1. Open Transaction F150 in your SAP system.
2. Click "Dunning Run" and select "Create New Dunning Run."
3. Specify Your Selection Criteria: Choose your company code, dunning area, and the customers you want to include. You can filter by customer group, region, credit score, or any field in table KNA1 (Customer Master).
4. Set the Posting Date: This is the date SAP uses to calculate "days overdue." It's usually today's date.
5. Run the Analysis: Click "Execute" and SAP will analyze your open invoices against your dunning rules. It won't post anything yet—it's just showing you what it would do.
6. Review the Dunning List: SAP displays all customers flagged for dunning, showing which level they've reached and what action will be taken. This is your chance to spot-check and exclude specific customers if needed.
7. Post the Dunning Run: Once happy, click "Post" and SAP will:

• Create dunning notices (stored in table DUNNV — Dunning Notice)
• Apply dunning fees (if configured)
• Apply dunning blocks to customer accounts
• Generate output (letters, emails) ready for distribution

The dunning run is recorded with a Dunning Run ID, making it fully traceable and auditable. If you need to reverse or modify a dunning run, you can do so through F151 (Dunning Run—Reverse).

Important Fields and Tables You'll Encounter

As you work through dunning, these SAP objects become your daily companions:

• KNA1: Customer Master table (links to dunning area)
• BSID: Open customer invoices (AR)
• TVDT: Dunning area definitions
• DUNV: Dunning procedure levels
• TVDP: Procedure assignments to company codes
• DUNNV: Dunning notices created
• F110: Automated payment program (sometimes used alongside dunning)

If you're writing custom reports or trying to troubleshoot, knowing these tables will save you hours of searching.

Best Practices for Dunning Success

Here's what we've learned works well in the real world:

• Start Conservative: Your first dunning level should be friendly. You don't want to damage customer relationships over a delay in processing. Save the tough talk for level 3 or 4.
• Automate Levels 1–2: Let SAP handle routine reminders. Save manual intervention for serious situations.
• Build in Exemptions: Some customers (think strategic accounts or special payment arrangements) should be excluded. Use customer dunning indicators in the master record (field MAHNA in KNA1) to flag these.
• Monitor Dunning Blocks: Credit blocks and delivery holds are powerful but can upset customers. Review them regularly and clear them as soon as payment is received.
• Test First: Run dunning in test mode before going live. A practice run can reveal issues with letter text or procedural logic.
• Schedule Regular Runs: Most organizations run dunning weekly or monthly. Set it as a recurring activity in your finance calendar.

Common Pitfalls to Avoid

After seeing dunning implemented hundreds of times, these mistakes pop up repeatedly:

• Forgetting to Post: If you run dunning but don't post, nothing happens. The analysis is just sitting there. Always remember to post after reviewing.
• Miscalculating Days Overdue: Make sure your posting date is accurate. If you run dunning on a weekend, the posting date might not be what you expect.
• Not Excluding Credit Memos: Dunning should ignore open credit memos or partial payments. If your selection criteria are too broad, you'll dunning customers who've partially paid.
• Ignoring Dispute Flags: SAP allows customers to flag invoices as disputed. Don't dunning disputed items—you'll just create friction.
• Setting Fees Too High: Late fees are legitimate, but overly aggressive fees can turn a late payment into a customer complaint.

Real-World Example

Let's say you work for a manufacturing company with 500+ customers. You've configured three dunning levels:

• Level 1 (10 days): Polite reminder letter, no fees, no blocks.
• Level 2 (20 days): Formal second notice, $50 dunning fee, delivery hold applied.
• Level 3 (30 days): Final notice with credit block, $100 total fee, referral flag for collections.

You run dunning weekly every Friday. SAP analyzes all invoices against these thresholds, identifies 47 customers spanning levels 1–3, and you review the list to exclude your top 5 accounts (which you're handling manually due to pending dispute resolution). You post the run, and SAP generates 47 letters, applies blocks and fees, and flags the invoices. Finance team prints and mails letters Monday morning. By next Friday, payment recovery has improved by 15%.

That's dunning working the way it's designed.

Next Steps

Now that you understand the SAP dunning process step by step, you're ready to configure or optimize your own setup. Remember: dunning isn't about being harsh—it's about being systematic and fair. Get your procedure right, test it thoroughly, and you'll see measurable improvements in cash flow and days sales outstanding (DSO).

Want to deepen your SAP Finance skills with practical, hands-on training? Head over to Automate & Graduate to explore courses that take you from the basics through to expert-level SAP consulting.