When an invoice sits unnoticed in the inbox
You know the scenario: an invoice is overdue, no one followed up, reminders are sent too late or replies get lost in the email inbox. The result: unnecessary effort in accounting and receivables management, delayed payments and missing follow‑up. This is exactly where a structured open‑items workflow comes in — with custom dunning templates and clear escalation logic.
What you can achieve with dunning templates and escalation
With purposefully structured templates per customer group and graduated escalation rules you can:
- make the approach consistent and appropriate to the customer situation,
- automatically notify internal stakeholders (e.g. key account managers),
- standardize and document follow‑up,
- reduce manual allocations and inquiries — while retaining full data sovereignty on your own infrastructure.
Preparation: group customers and define rules
Before you create templates, pragmatically clarify two questions:
- Which customer groups need different tone or content? (e.g. key accounts, new customers, small service providers)
- Which escalation levels should exist? (e.g. 7 days, 21 days, 35 days overdue; escalation to key account manager after 21 days)
Create a simple matrix in Debentra: customer group × dunning level → desired action (template, CC, approval required?). This matrix is your roadmap for implementation.
Step 1: Create customer groups in Debentra
How to create targeted groups:
- Open customer management and create new tags or segments (e.g. "key account", "new customer", "payment behavior: low").
- Link existing customer data to the groups — Debentra works centrally with customer records so invoices automatically fall into the correct group.
- Check the assignments by spot‑checking older open items.
Step 2: Create dunning templates per customer group and dunning level
Less is often more: focus on clear, modular templates that you can adapt for multiple groups.
- Choose template structure: subject, email text, footer, signature, attachments (e.g. invoice, payment link).
- Use placeholders: {{Kundenname}}, {{Rechnungsnummer}}, {{Betrag}}, {{Fälligkeitsdatum}}. Debentra replaces these automatically when sending.
- Tone per reminder level: phrasing suggestions
- Reminder level 1 (friendly): "Reminder: Invoice {{Rechnungsnummer}} dated {{Fälligkeitsdatum}}"
- Reminder level 2 (firm): "Second reminder: Please settle invoice {{Rechnungsnummer}}"
- Reminder level 3 (escalating, factual): "Final reminder before further follow-up: Invoice {{Rechnungsnummer}}"
- Variants for key accounts: shorter, more personal address and automatic CC to the responsible Key Account Manager.
- Testing: send a preview to a test account, check placeholders and attachments, then approve.
Step 3: Configure escalation logic
The escalation logic determines which action is triggered at which time. In Debentra set up these rules as follows:
- Define triggers: e.g. days since due date, no response after reminder X, partial payment received.
- Specify actions: send a particular template, add CC to Key Account, create tasks for accounting, mark case for manual review.
- Prioritization: decide whether certain groups have stricter rules (e.g. immediate CC to sales for key accounts).
- Approval stages: determine whether reminders are sent automatically or require approval before sending. This control remains with the user and can differ per rule.
Practical rule examples
A few typical, immediately actionable rules:
- Rule A (new customers): 7 days overdue → friendly reminder, automatic approval.
- Rule B (standard customers): 14 days overdue → second reminder, CC to accounting, automatic send.
- Rule C (Key Account): 21 days overdue → escalation: send factual reminder, CC Key Account Manager and create task for account representative; send only after manual approval.
Maintain control: approval and review mechanisms
Automation should ease work, not remove responsibility. Configure approval pipelines in Debentra, for example:
- Automatic sending up to reminder level 2,
- at reminder level 3 automatic notification to responsible parties and sending only after OK,
- logbook: every sent reminder and received reply is documented — for traceability and audit.
Monitor and adjust: metrics you should watch
Set regular checks to optimize rules. Relevant metrics include, for example:
- Delivery rate and bounce rate of reminder emails,
- Response rate to reminders (whether an inquiry or payment was received),
- Average time to payment after sending a dunning stage,
- Number of manual interventions per dunning case.
Based on these metrics you adjust subject lines, tone, and escalation timing — Debentra facilitates this cycle through centralized analysis and tracking.
Typical mistakes — and how to avoid them
- Too many templates: Maintain clear, scalable templates instead of individual one-off documents.
- No test runs: Always use preview and test sends so that placeholders and attachments are correct.
- Automation without oversight: Set fixed approval thresholds, especially for key accounts.
- Unclear internal responsibilities: Define who gets informed and who is accountable during escalation.
Practical example: From reminder to internal follow-up
A mid-sized company creates three customer groups in Debentra: Key Accounts, Standard Customers, and New Customers. For Key Accounts there is a separate template with personal wording and a CC to the Key Account Manager. The rule is: 21 days overdue → generate reminder email, notify the Key Account Manager, send only after manual approval. Result: communications are personally tailored, internal responsible parties are automatically informed, and all steps remain documented.
Integration and editions in brief
Debentra is self-hosted and offers different editions (BASIS, PRO, PREMIUM). For setting up templates and escalation rules, the basic functions are more comfortably usable in the higher editions: PRO reduces manual allocation work, PREMIUM enables supplementary accounting features. Decide based on your requirements and IT resources — Debentra runs on your own infrastructure so you retain data sovereignty.
Checklist: Quickly implemented
- Define groups (Key Account, Standard, New Customer).
- Create templates with placeholders (subject, body, attachments).
- Configure escalation rules by days and by response.
- Set approval workflows (automatic vs. manual).
- Set up test sends and monitoring, adjust rules based on the data.
Conclusion and next steps
Custom reminder templates and well-thought-out escalation logic reduce routine work, improve internal tracking, and ensure that responsible parties are informed at the right time — all under the control of your approval rules. Start with a few clear customer groups and expand rules iteratively.
Act now: Choose the appropriate edition and set up dunning templates and escalation rules in Debentra to improve dispatch, response rate and internal tracking. Choose edition: https://debentra.de
Next step
Try Debentra yourself
Central overview and process control for outstanding items and payments with full data sovereignty; reduces manual reconciliation work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.