An SAP FI dunning procedure controls how overdue customer receivables are identified and followed up using reminders at defined levels. It draws on open-item due dates, customer dunning data, intervals and configured exceptions to propose which notices may be sent. Dunning is a collections communication process, not automatic proof of debt, a write-off, a cash receipt or permission to contact a disputed account.
Start with the actual overdue item
An invoice becomes eligible for overdue analysis based on payment terms, the baseline date for payment and relevant posting or clearing status. A due invoice can remain open for legitimate reasons, such as a payment in transit, a disputed charge or an approved payment arrangement. Before a reminder is sent, Accounts Receivable should reconcile the item to current account information and consider any configured blocks or grace periods.
How levels and timing shape communication
A procedure may define several dunning levels with minimum intervals between runs, grace periods, minimum amounts and different notice wording. The selection and notice logic depends on customer or company-code data and the configured rules. The first communication may be a courteous reminder; later stages may require collections escalation. A higher level is not a substitute for checking whether the underlying receivable remains valid.
A realistic collections decision
An invoice is ₹50,000 and 18 days past due. The team checks open-item status, any payment in transit, dispute flags and the customer dunning block. If valid and eligible, the reminder can progress according to policy. If the customer has already paid but the bank receipt is unmatched, the right next step is to resolve cash allocation, not escalate the notice.
Why proposals must be reviewed
Even an automated dunning run needs controlled exceptions. The team should review proposal items against disputes, payment promises, recently settled invoices and sensitive accounts before dispatch. The approved communication should state the outstanding amount, reference and customer response channel.
Controls beyond the reminder text
Dunning parameters can include minimum overdue amounts, grace periods, level escalation intervals and block rules. Review whether the customer company code has a suitable procedure and whether any amount should remain excluded from collection. The collection manager should approve tone and escalation thresholds, while Accounts Receivable maintains correct items and master data. A notice itself does not clear a debt or post a payment.
Review exceptions and outcomes
Monitor incorrect notices, unresolved disputes, unmatched cash, promise-to-pay follow-ups and aged open items. A customer credit memo or payment may change the amount due and the next dunning decision. Escalation should be grounded in verified balance and documented policy, with sensitive accounts reviewed by the appropriate business owner.
Consultant questions
Which dates decide when an item is due? What blocks a dunning notice? Who reviews proposal exceptions? How do teams prevent sending duplicate notices for a paid invoice? Which communication channels are acceptable, and how is customer feedback captured before the next scheduled run?
Read next
Customer Invoice Accounting, Incoming Payment Processing, Customer Credit Memo Accounting and Customer Business Partner Master Data. Return to the SAP FI / FICO hub.