Set up collections
Dunning sequences
Set up dunning sequences: steps by days overdue, automatic steps or collector tasks, contact rules, a preview before each run and native reminders.
updated: applies-to: 1.2.0.0
A dunning sequence decides what happens to an overdue invoice as it gets older: an email, a statement, a reminder, a call, a credit hold or an escalation. The daily collections job runs the sequences. Bitta Collections builds on the native reminder terms and levels: a Reminder step calls the native create, issue and send functions, so fees, interest and reminder texts stay as you set them up in Business Central.
Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.
Before you start
- You need the BAA COLL SETUP permission set to create and change sequences.
- Email and Statement steps need an email account for the Collections email scenario and the email templates. See Email and templates.
- Reminder steps need native reminder terms with levels on the customers.
- Sequences run in the collections job. Check that it is scheduled on Bitta Collections Setup with Schedule Jobs. See Getting started.
The recommended sequences
The assisted setup creates two sequences. You can also create them with Create Recommended Sequences on the Collections Sequences page. Existing sequences are not changed. The number in Days Overdue counts from the due date; a negative number runs before the due date.
STANDARD (Standard dunning) fits most customers:
| Step No. | Days Overdue | Action | Run Mode | Description |
|---|---|---|---|---|
| 10 | -3 | Email (COURTESY) | Automatic | Courtesy email before the due date |
| 20 | 1 | Email (REMINDER1), invoice copies | Automatic | Friendly email with invoice copies |
| 30 | 15 | Statement (STATEMENT) | Automatic | Send a statement |
| 40 | 30 | Email (FIRM), invoice copies | Automatic | Firm email with invoice copies |
| 50 | 35 | Reminder | Automatic | Create and issue a reminder |
| 60 | 45 | Call Task | Collector Task | Call the customer |
| 70 | 60 | Credit Hold | Automatic | Put the customer on credit hold |
| 80 | 75 | Email (FINAL), invoice copies | Collector Task | Review and send the final notice |
| 90 | 90 | Escalate | Automatic | Escalate to the escalation collector |
Step 50 is created only when reminder levels exist in the company.
GENTLE (Gentle dunning for key accounts) waits longer and lets the collector review the firm email:
| Step No. | Days Overdue | Action | Run Mode | Description |
|---|---|---|---|---|
| 10 | 5 | Email (REMINDER1) | Automatic | Friendly email |
| 20 | 30 | Call Task | Collector Task | Call the customer |
| 30 | 45 | Email (FIRM) | Collector Task | Review and send a firm email |
| 40 | 60 | Escalate | Automatic | Escalate to the escalation collector |
The Escalate steps of both sequences have no Escalate To collector, so they give the work item to the escalation collector of the customer's collector. When that collector has no escalation collector, the work item goes to the Default Collector Code in Bitta Collections Setup.
How a sequence runs
The job looks at each open invoice of each customer and applies these rules:
- The right step. Each invoice gets the highest step that is due after the last step done for it. Lower steps that were passed over are recorded as skipped and never sent later. A failed step is tried again on the next run.
- One contact per run. When several invoices of a customer are due for outbound steps, they are grouped into the highest of those steps, so the customer gets one email, not several.
- Cool-off. After any outbound contact, automatic or logged by a collector, an automatic step waits Min. Days Between Contacts (default 3) before it contacts the customer again.
- Minimum amount. When the invoices of a step total less than the step's Min. Amount (LCY), the step waits and is tried again on the next run.
- Paused invoices. Invoices that are on hold, disputed, promised or in an active payment plan are paused.
- Skipped customers. Customers blocked for all transactions or for privacy are skipped, and so are blocked sequences.
Step actions and run modes
| Action | What an automatic step does |
|---|---|
| Queues a collections email from the step's template, with invoice copies or a statement if the step asks for them. | |
| Statement | Sends a customer statement with the step's template as the cover note. |
| Reminder | Creates a native reminder and, by Reminder Mode, issues it or issues and sends it. |
| Call Task | Sets the next action Call for the collector. |
| Credit Hold | Places a credit hold with the reason Dunning Step. |
| Escalate | Gives the work item to the step's Escalate To collector, or else to the escalation collector of the customer's collector, or else to the default collector of the setup, sets the next action Escalation Review, and can notify that collector by email. |
| Send to Agency | Proposes a placement with a collection agency for review, or also sends the packet when Send Agency Packets Automatically is on. See Collection agencies. |
| Creates a letter or statement for physical mail. See Physical mail. |
Run Mode is Automatic or Collector Task. A collector task does not contact the customer. It sets a next action on the work item, such as Email, Statement or Review Credit Hold, and the collector decides what to send.
Create or change a sequence
- Search for Collections Sequences, or choose Setup > Collections Sequences on the role center.
- Choose New, enter a Code and a Description, or open an existing sequence.
- In Steps, add one line per step. Give steps with a higher Step No. the same or more Days Overdue.
- Fill in the step fields that the action needs.
- Choose Prepare > Check Sequence and fix every problem it lists.
| Step field | What it does |
|---|---|
| Description | Shown as the next action note and in the activity log. |
| Days Overdue | When the step becomes due for an invoice. |
| Action, Run Mode | What the step does, and whether it runs by itself. |
| Email Template Code | The template for Email and Statement steps. |
| Invoice Copies, Statement | Attach copies of the overdue invoices, or a statement. Statement steps always attach one. |
| Reminder Mode | Create Only, Create and Issue or Create Issue and Send. Hidden by default. |
| Min. Amount | The least total in local currency for the step to run. Hidden by default. |
| Escalate To, Notify | The collector for an Escalate step, and whether to email that collector. Leave Escalate To blank to use the escalation collector of the customer's collector, or else the default collector. |
| Agency | The agency for a Send to Agency step. Blank uses the default agency in the setup. |
| Mail Document, Letter Tone, Mail Without Review | The settings of a Mail step. |
To pause a sequence for everyone, turn on Blocked on the sequence. To give a customer another sequence, change Dunning Sequence Code on the Customer Card.
No. of Customers on the sequence counts the customers that run it: the customers it is assigned to and, for the default sequence, every customer without a sequence of its own. Choose the number to see these customers.
Check and preview before a run
- Check Sequence lists every setup problem at once, such as a missing template. It also warns when two steps start on the same day, and when a native Reminder Automation group covers the reminder terms of the sequence's customers. An Escalate step without Escalate To is a problem only when a collector of the sequence's customers has no escalation collector and the setup has no default collector (or a blocked one).
- Preview Sequence on the Customer Card (Collections > Dunning) shows, for each open invoice, what the next run would do and why. Outcome is Run, Skip, Wait, Paused or No Step. Nothing is sent or written.
- Run Sequence Now on the same menu runs the customer's sequence at once instead of waiting for the job.
- The Dunning Proposal report shows what the next run would do for many customers. It writes nothing.
Native reminders and finance charges
Bitta Collections keeps disputed and promised invoices out of the native reminders and finance charge memos too, including Create Reminders and Reminder Automation. Two fields on Bitta Collections Setup control this, and both are on by default:
- Exclude Promised Entries on the Promises FastTab.
- Exclude Disputed Entries on the Disputes FastTab.
You can keep using native Reminder Automation next to the sequences. If both cover the same customers, those customers can get two reminders. Leave the Reminder steps out of the sequence, or remove those reminder terms from the automation group.
Follow the results
- Dunning History lists every step that ran, per invoice, with its Status: Done, Task Created, Skipped or Failed. Open it from the sequence, the customer card or Customer Ledger Entries.
- On Bitta Collections Setup, the Job status FastTab shows Last Job Failure Count and Last Job Failures. The Failed Dunning Steps action opens Dunning History filtered to the steps that failed in the last run, each with its error. One customer's error never stops the others.
NOTE
A Reminder step picks the invoices through the customer's own reminder terms, so the native reminder can cover more invoices than the step. When the reminder terms create no reminder for a grouped contact, the lower Email steps are recorded as skipped.
What's next
Set up the emails that the sequences send: Email and templates.