When a reminder gets lost in the inbox: a typical morning
You open your email inbox, see three payment queries, two responses from customers — and behind them a string of overdue invoices for which no reminders were sent and no calls documented. In many small and medium B2B companies, scenarios like this create lost time, inconsistencies and follow‑up work. Automatic channel selection for payment reminders can provide relief here — provided the solution respects customer preferences and your data protection requirements.
Why automatic channel selection makes sense
Not every reminder should be sent by email. Some customers prefer SMS, others require postal delivery for formal dunning notices. Rule‑based channel selection reduces manual decisions while increasing the likelihood that the message is noticed. Important: Delivery must originate from your infrastructure if you want to ensure data sovereignty and compliance.
Concrete benefits for your team
- More efficient follow‑up: Reminders reach customers via the channel on which they typically respond.
- Less manual work: Rules handle assignment of channel and template, while the team remains in the approval loop.
- Data protection control: Sending jobs run on‑premise, so customer data does not leave your infrastructure.
How Debentra organizes channel‑based delivery
Debentra makes it possible to decide by rule whether a reminder should be sent by email, SMS or postal letter. The process follows clear steps that you can configure and, if needed, approve manually:
- Import invoice → detect open items
- Rule check: customer preference, response history, urgency
- Assignment of delivery channel and template
- Orchestration of local send jobs (email queue, SMS gateway, print/postal dispatch process)
- Follow‑up: detect receipt or response signals and update documentation
Rule components you configure in Debentra
The rules typically consist of a few, easy‑to‑understand elements:
- Customer preference: Explicitly stored preferences (email, SMS, postal).
- Response history: Last contact channels and response times; e.g., “Customer responds quickly to SMS.”
- Due date/Urgency: Time since due date, dunning level or amount thresholds.
- Rule priority: Rules in a logical order so conflicts are resolved deterministically.
Practical rule examples
Here are two practical rule sets you can use as templates:
Example 1 — Routine case (first reminder)
- Conditions: due > 7 days, customer preference is “E‑mail” or no preference.
- Action: assign the e‑mail template “First Reminder”; place the send job into the e‑mail queue.
- Follow‑up: if no response after 10 days, activate the rule for SMS or postal follow‑up.
Example 2 — Urgent Case (high amount / second reminder)
- Conditions: outstanding amount > defined threshold OR reminder level = 2.
- Action: check customer preference; if preference is “Post”, initiate local print and dispatch job; otherwise prepare SMS + e‑mail in parallel.
- Approval: before printing, a release request is sent to the responsible team.
Orchestrating Local Send Jobs: keeping everything within your network
A central point is the local execution of send jobs. In Debentra you define for each channel how the sending is technically performed:
- E‑mail: internal SMTP servers or an internal relay; Debentra places messages in a queue and your infrastructure handles delivery.
- SMS: integration with an internal GSM gateway or an in‑house operated SMS service; Debentra sends the messages to the gateway.
- Postal dispatch: generation of print‑optimized PDFs, handover to a local print server and tracking of the print/envelope job.
The advantages: you retain full control over communication data, access to logs and can implement data protection requirements directly without involving third‑party clouds.
Tracking and Documentation
Every sent reminder is documented in Debentra: channel, template, send time and incoming reactions are linked. The platform recognizes payments, partial payments and replied messages and automatically updates the open item status. This keeps the history fully traceable.
Control instead of Blind Automation: Approvals and Exception Handling
Automation should reduce work, not remove responsibility. Therefore Debentra allows automated send suggestions to be presented for approval before sending. Typical rules for approvals:
- Automatic sending only for items < X euros; above that, approval is required.
- Deviating payment or communication history results in a manual review task.
- Postal dispatch is by default approved manually to check wording and attachments.
Implementation Steps: How to get started in three phases
- Analysis: Collect customer preferences and review response times. Define channel rules for standard cases.
- Configuration: Set up Debentra rules, integrate local SMTP/Gateway/Print servers and define approval processes.
- Test and Rollout: Test rules with pilot customers, monitor log data and adjust priorities.
Which editions support which needs?
Debentra is available in three editions:
- BASIC: Central overview of open items and manual workflow support — suitable for getting started.
- PRO: Reduces manual allocations through advanced rule mechanics and automations, including channel-based assignment.
- PREMIUM: Offers additional integrations, for example with accounting, and extends the orchestration of local processes.
For automatic channel selection and the orchestration of local delivery jobs, PRO is often the practical middle ground; companies with tight accounting integration choose PREMIUM.
Practical checklist: Rules for automatic channel selection
- Have you systematically recorded customer preferences?
- Are response history and dunning levels available as decision factors?
- Is your local SMTP/SMS/print stack connected and tested?
- Are approval thresholds defined so that critical cases are reviewed?
- Who documents exceptions and adjusts rules?
Conclusion
A rule-based, automatic channel selection increases efficiency in receivables management and raises the chance that payment reminders are seen — provided delivery is controlled on your infrastructure. Debentra combines rule-based decisions with the orchestration of local delivery jobs so that data protection and operational control are maintained. The decision about sending and approval remains with the user; automation handles the routine work.
Ready to professionalize the delivery of your payment reminders? Choose the appropriate edition and start with a pilot configuration: Choose edition
Next step
Try Debentra yourself
Central overview and process control for open items and payments with full data sovereignty; reduces manual allocation work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.