Dunning Blocks

Set, review, and selectively lift dunning blocks for customers or items.

Besides creating and sending reminders, Bilendo offers many functions to manage your different dunning stops. Specific document types or customers can be excluded from the dunning run altogether. A temporary dunning stop is also possible at any time.

You can put a dunning stop (with or without an end date) on customers and journal entries, which automatically excludes them from dunning. Every dunning stop carries a dunning block reason that records why the block exists.

The following dunning stops can be managed in Bilendo:

• Dunning stop on customer level:

  • With this dunning stop you block dunning for all journal entries of a customer.

• Dunning stop on journal entry level:

  • With this dunning stop you block dunning for a single journal entry only.

Dunning block reasons

A dunning block reason describes why a customer or journal entry is not dunned, for example "Installment plan agreed" or "Legal dispute". It corresponds to the dunning block in your ERP system and consists of a code and a description. This way the dunning block reason gives every colleague the context of a dunning stop.

• Manual dunning block reasons are the ones you choose yourself when you set a dunning stop in Bilendo.

• External dunning block reasons come from your ERP system through the data import. They are shown, but cannot be changed or removed in Bilendo. When a later import no longer delivers the reason, the dunning stop is lifted automatically.

The list of dunning block reasons applies per System, separately for customers and journal entries. It is set up by your Bilendo contact. If there is only one manual dunning block reason, it is always preselected automatically when you set a dunning stop. A dunning block reason on a customer does not automatically apply to that customer's journal entries.

Manage the dunning stop of a customer

• Open the customer under Data Hub › Customers

• Under "Options", click "Manage Dunning Stop"

• Under "Reason", select the matching reason

• If needed, set an "Expiration date" for a temporary dunning stop. Without a date, the dunning stop stays until you remove it

• Confirm with "Submit"

To change the reason, simply select another reason and submit; you do not need to remove the dunning stop first. "Remove manual dunning stop" lifts the manual dunning stop.

Manage the dunning stop of a single journal entry

• Open the journal entry under Data Hub › Journal Entries

• Next to "Dunning Stop", click "Edit"

• Configure the dunning stop as described above

Set a dunning stop on several journal entries at once

• Open the customer under Data Hub › Customers and go to their journal entries

• Select the journal entries

• Under "Options", choose "Add manual Dunning Stop"

• Select a dunning block reason and, optionally, an expiration date

The selected journal entries must belong to the same System, because every System has its own dunning block reasons.

Find, filter and export dunning block reasons

• In the lists under Data Hub › Customers and Data Hub › Journal Entries you can show the column "Dunning Block Reason".

• The filter "Dunning block reason" finds all customers or journal entries with a specific reason, "With Dunning Block Reason" or "Without Dunning Block Reason".

• The export offers the description of the dunning block reason and two code fields: one for the code of the manual and one for the code of the imported dunning block reason. This way reasons set in Bilendo can flow back into your ERP system.

• The dunning stop history in the "Manage Dunning Stop" dialog shows the reason for every entry. When a reason changes, the old entry is closed and a new one is started.

You also choose a dunning block reason when you close a clarification, in clarification workflows with the effect "add dunning stop", and for promises to pay.

Note:
The manual dunning stop on customer and journal entry level is complemented by automatically set dunning stops. An automatic dunning stop can be set when the journal entry is part of an open clarification or when it was provided during the data import. This can be based on the document type or on a transmitted difference reason or dunning block reason. Externally set dunning stops cannot be removed by users. Only a dunning stop set manually by a user can also be lifted by a user. How the system manages external and automatic dunning stops can be found in the article on dunning stop configuration or discussed with your Bilendo contact.

Frequently asked questions

Can I create my own dunning block reasons?
The list is set up and adjusted together with your Bilendo contact, ideally matching the dunning block reasons in your ERP system.

Can I add a comment to a dunning stop?
The dunning block reason replaces free text: it reads the same for everyone, can be filtered and can be exported with its code to your ERP system.