The last step in the dunning process involves printing the dunning notices.
The print program for the dunning procedure performs the following:
- Groups items to be dunned with a dunning notice according to various rules.
- Generates a dunning notice for each group.
- Enters the dunning date and dunning level in the list of dunned items and accounts.
The system prints dunning notices in a sequence defined by sort criteria.
If you need to send dunning notices to one-time customers, only update the dunning data for relevant items. For information about undoing changes to dunning data in accounts and documents, see SAP Note 6591.
Grouping Items in the Dunning Notices
Items to be dunned can be grouped together in dunning notices if they have the same company code, dunning area, and account.
The system groups the items of a one-time account in a single dunning notice if they have the same address.
Special Groupings
Grouping Items
- Dunning by dunning level
- Grouping key
- Decentralized processing
You can group items by the following criteria:
- Dunning by dunning level:
In the company-code-specific settings for the dunning program, you can choose whether to print a separate dunning notice for each dunning level. In this case, the system selects the text for the dunning notice according to the dunning levels of the grouped items.
- Grouping key:
You can enter a grouping key in the customer or vendor account to group items that have the same values in the fields assigned to the grouping key in dunning notices. You can use the fields in the index tables for the open items BSID (customers) and BSIK (vendors).
- Local processing:
If a customer has a head office with several branch offices, the system posts items to the central account. As a result, the head office usually receives one dunning notice with all the items due from its branch offices. If Local Processing is selected in the branch accounts, meaning the dunning is processed locally, the system sends the notices to the branch offices.
Dunning Notice for Each Group
You can use cross-company-code dunning to combine overdue items from different company codes in one dunning run. The overdue items from one customer in separate company codes are dunned with a single dunning notice. This means you do not have to send the customer a separate dunning notice for each company code.
Note
The system groups the overdue items according to predefined rules (dunning levels, dunning areas, or dunning grouping) and assigns them to one or more dunning notices.
If you want to dun separate company codes at the same time, you have to assign the relevant company codes to a shared dunning company code. The system uses the dunning procedure assigned to the account in the dunning company code. The system checks the dunning frequency and dunning blocks individually, from each separate company code.
Note
If a date for the legal dunning procedure for an account has been specified in the dunning company code, this also affects the dependent company codes.
Dunning Notices
You can print dunning notices with an attached payment form for bank transfer (Germany) or ESR payments (Switzerland). The customer can use this payment form to pay the dunned amount.
You can attach the payment form to the dunning notice or print it on a separate page. This means you have to change the dunning notice form so that it contains a separate window for the payment form, or you have to create a separate form for the additional page.
The dunning notice must only contain items with the company code currency.
The payment program can create a payment advice note containing the items in the dunning notice. When the customer pays the dunned amount, you can use this advice note to assign the incoming payment to the relevant items.
The payment advice number has 10 digits and starts with 08. You have to define the payment advice type 08 in the configuration settings.
You can print the payment advice number on the dunning notice and the payment form (for example, in the Reference field).