Automating dunning doesn't mean sending reminders blindly, but building the entire path leading up to it cleanly: pulling open items from your accounting system, checking due dates, matching incoming payments, and preparing the right reminder level for every overdue invoice. NordFlux connects accounting, bank, and inbox into one process. You see every case and continue to approve sending yourself.
Open items sit in the accounting system, but nobody enjoys the daily checking, matching, and drafting. So reminders go out whenever there's time, and that costs twice over: money that arrives later, and customers who feel wrongly reminded.
This page describes the whole path from open items to the finished reminder, not a single letter. In the end, nothing goes out until you approve it.
The process pulls the open items from your accounting system and checks every day which invoice has passed its due date. Instead of glancing at a list whenever there happens to be time, you get an up-to-date overview of overdue invoices with amount, customer, and days overdue. Nothing slips through just because nobody checked.
Savings 2–4 h per weekBefore a reminder is even prepared, the process matches the open invoice against the account transactions, even if the payment reference is messy. Anyone who has already paid drops off the reminder list before an awkward reminder goes out. This exact matching step is the one most often done by hand today, or forgotten.
Impact no reminders to paying customersPayment reminder, first reminder, second reminder, handover: you set the deadlines and tone per level once, and the process picks the right level for every overdue invoice. Reminder fees and late-payment interest are calculated according to your rules and inserted into the text. This way, no third reminder ever goes out where a first one never did.
Impact clean escalation without jumpsNot every customer is treated the same: regular customers get a friendlier tone or a longer deadline, and disputed invoices are excluded from the reminder run. Anything that reaches the last level lands on a list for handover to a collection agency or lawyer, instead of being reminded endlessly. The rules for this live in one place and can be changed at any time.
Impact Customer relationship stays intactThe process prepares the due reminders as finished drafts, you approve them individually or in a batch, and only then do they go out by email or letter. Every step is logged: which invoice reached which level when, and who approved it. If a question comes up, you see the complete reminder history of an invoice in seconds.
Savings Reminder run in minutes instead of hoursWe don't replace your accounting system, we build the paths to it and back. Which tool we use depends on your environment, not on our preference.
Many sources, one processYour accounting system, bank account, and inbox don't talk to each other on their own. n8n connects these sources into a single pipeline and, on request, runs on a server in Germany so your customer and payment data never leave the building. This is the standard approach when several systems need to work together.
Microsoft 365 already in useIf you work with Microsoft 365, the approval of the reminder run happens directly in your environment: as an approval card in Teams or Outlook, with storage in SharePoint. The standard connectors needed for this are already covered by your Microsoft 365 license. If the process accesses systems outside Microsoft 365, a premium license may be required, which we clarify openly in advance.
The open items come from the system in which they're already managed anyway, whether DATEV, Lexware, sevDesk, or an ERP module. If a system has an interface, we use it; otherwise a software robot reads the data from the user interface. We have a dedicated page covering DATEV integration in detail.
From the first conversation to a running dunning process in 30 days, at a fixed price instead of an open-ended timesheet.
60 minutes, no obligation: we look at how your open items arise today, who reminds when, and where payment matching gets stuck. Afterward, you know which part is worth automating.
You get a concrete proposal: which systems we connect, how your reminder levels and deadlines are mapped, and what it costs. One number, no surprises at the end of the month.
We build the pipeline and test it with your real overdue invoices from a closed period, including edge cases. You compare the result with what your team would have done by hand.
Your team gets a walkthrough and documentation showing where to change the rules and how to intervene. On request, we take over operation with a fixed service level.
This page describes the dunning pipeline in detail. If you mean the overall process from collecting receipts to handover to your tax advisor, the accounting automation page is the right starting point, and there's a dedicated page with more depth on incoming invoices.
In the free initial analysis, we work out together how much time dunning costs you today and how much faster your money arrives with a clean process. 60 minutes, no obligation, no sales pressure.
Automated dunning means overdue invoices are detected on their own, matched against incoming payments, and assigned to the right reminder level, instead of someone going through the open items by hand. The process prepares the reminders as drafts. You continue to decide whether and when they go out.
No, that's exactly what the process prevents. Before every reminder, the open items are matched against the account transactions; anyone who has paid drops out of the reminder run. Because sending only happens after your approval, there's a second safeguard against incorrect reminders.
Yes. The open items come from the system in which you already manage them, whether DATEV, Lexware, sevDesk, or an ERP module. If the system has an interface, we use it; otherwise a software robot reads the data from the user interface. We never write past your accounting system.
You keep control. The process prepares the due reminders as drafts and submits them to you for approval, individually or as a batch, and only then do they go out. On request, uncontested first payment reminders can be sent automatically, with only the higher levels submitted for approval; you decide.
The price depends on how many systems need to be connected and how branched your reminder levels and exceptions are, so we don't quote a flat rate into the blue. After the free initial analysis, you get a fixed price for a clearly defined scope, not an open-ended timesheet. If automation doesn't pay off for your invoice volume, we'll tell you so in the first conversation.
