Payment Reminders That Escalate on Their Own: Dunning Levels, Fees, and Where the Machine Stops
Chasing an unpaid invoice is not difficult work. It is work that has to happen on the right day, and the right day is almost never the day somebody remembers it. A customer who owes money for three weeks is a normal business event; a customer who owes money for three months because nobody looked is a different problem, and it is the more expensive one.
Firmspace CRM treats the reminder as a small engineered process rather than a habit. An invoice has four reminder levels, defined as levels one through four. Every level does the same three things: it raises the level by one, it adds that level's fee to the invoice, and it gives the customer a new, short payment date. What changes between the levels is the wording and the amount.
The wording is not written by hand each time. The system keeps a text for each level, and in German, the language of the reference market, the four steps read as a familiar escalation: Zahlungserinnerung, zweite Zahlungserinnerung, letzte Zahlungserinnerung, and finally letzte Mahnung vor rechtlichen Schritten. The last one says what it means: the next move is not another email.
The fee is a setting, not a fixed truth. By default the four levels charge nothing, nothing, 2.50 and 5.00, with a tenth unit reserved for a fourth level, and a firm can change every number because what is defensible depends on the market and on the contract. Each charge is added as the level is reached, so the invoice accumulates the sum of the steps it has actually climbed rather than a single penalty applied at the end.
The new payment date is also a setting, seven days by default. Raising a level does not reopen the original deadline; it sets a fresh one, which is what makes the next escalation defensible. The invoice keeps the date in its own log entry, so the history says not only that a reminder went out but when the customer was asked to pay by.
The overdue clock starts before any of this. A daily sweep looks for invoices that were sent and whose due date has passed, and moves them to overdue. Invoices without a due date are left alone: an invoice that never named a deadline cannot fairly be called late. An invoice is never called late twice, because the status change itself is the evidence that it already happened.
Beyond that point there are two ways up the ladder. The first is a person, who sends the next reminder deliberately, usually after a phone call or when a customer asks for the paperwork again. The second is the automatic sweep, and the difference between them is exactly the kind of detail that decides whether an automation is trustworthy.
The automatic sweep runs once a day, together with the other scheduled work. It looks only at invoices already marked overdue. It waits a configurable interval, seven days by default, counted from the last reminder or from the due date if there has never been one. Only then does it raise the level, and it records in the history that this step was taken automatically rather than by a person.
Each reminder also leaves the system as a message. The invoice is attached as a PDF that already shows the raised level and the accumulated fee, and it goes out from the firm's own mailbox, with the language of the reminder following the customer. The result of that email is reported honestly rather than assumed: sent, skipped because the firm's own rule handles it, no recipient found, no mailbox connected, or failed.
One body of work is deliberately left to people. The automatic sweep stops at the fourth level. Above it the system does not continue on its own, because what comes next is a legal step rather than a polite nudge, and a decision with consequences should have a name attached to it. The tool says the same thing in a single line: the highest level has been reached, and the next move is yours.
A second boundary is drawn around the money itself. Late-payment interest is calculated and shown for reference next to the invoice, and it is calculated on the invoice total plus the accumulated reminder fees, using a rate the firm must set. But it is not added to what the customer owes, and the reason is stated plainly: the correct rate depends on the contract in front of you and on the statutory base rate behind it.
That is a boundary a bookkeeper will recognise and appreciate. The system will do the arithmetic and show the number, and it will not silently post that number into an invoice, because the interpretation is a professional judgement rather than a constant. The same restraint appears in the reminder text: it states the facts of the debt and the new deadline, and it does not threaten.
Put together, the escalation is unglamorous and that is the point. Level one happened on the day it should have, level two happened seven days later without anyone remembering, the invoice carries the fees it earned and a log entry for every step, and the fourth step waits for a human who can read the situation. The automation is not there to replace the decision. It is there to make sure the decision arrives at the right time.