Dunning in S/4HANA: When Customers Who Paid Get Reminders, F150 Is Not the Problem
If collections sends reminders to customers who already paid, the dunning run is not the problem. The open items are.
The tip
If collections sends reminders to customers who already paid, the problem is not the dunning run (F150). Before you run it:
- Payments posted and cleared
- Dunning blocks set on accounts and items that must not be dunned, such as items under dispute
- The dunning procedure (FBMP) reflects your policy: line item grace periods, minimum days in arrears and dunning levels
Do you dun from FI or work collections in Collections Management?
Why it matters
The dunning run evaluates open items by their due dates and the dunning procedure. A payment that is not posted, or not cleared against the invoice, leaves the invoice open, and the run treats it as overdue.
Steps and configuration
- Post and clear incoming payments before the dunning run.
- Review the dunning procedure: dunning interval, minimum days in arrears for the account, line item grace periods, dunning levels, charges and texts.
- Run dunning with F150 or the Create Dunning Notices app, then edit the proposal: block an account or a line item, or change an item’s dunning level. These changes apply to that run.
- Set a dunning block on the account or item when it must stay out of dunning.
Edition differences
- Private Cloud and On-Premise: dunning procedure in FBMP, run with F150 or the Create Dunning Notices app.
- Public Cloud: dunning is configured through the configuration apps and run with the Create Dunning Notices app.
Official sources
- SAP Learning: Configuring the Dunning Program
- SAP Learning: Executing the Dunning Process
- SAP KBA 3630644: Dunning after open item migration (FBMP, F150, Create Dunning Notices)
Validated against: SAP S/4HANA 2025 FPS02 (Private/On-Prem) and Public Cloud 2608, reviewed 21 Nov 2026.
Originally shared on X (18 Nov 2026, in Spanish): view the post. More tips: SAP Tips.