When an overdue invoice gets lost in the inbox
You know the scenario: an invoice becomes due, nobody follows up, reminders are sent too late and replies get lost in the email jungle. For small and mid‑sized B2B companies this often means extra manual work, delayed incoming payments and unclear responsibilities.
A structured, event‑driven open‑item workflow solves this everyday pain: Debentra detects status changes (due, overdue, payment received, partial payment) and sends on‑premise webhooks to your infrastructure — automatically, traceably and under your data sovereignty.
What webhooks achieve in dunning
Webhooks are simple HTTP notifications triggered when a defined status change occurs. In dunning this yields two concrete advantages:
- Automated notification and ticket creation: Internal teams are informed immediately instead of tracking invoices manually.
- Synchronized system landscape while retaining your data sovereignty: Information about status and payments flows into your ticket and ERP systems without customer data leaving your own infrastructure.
Debentra on‑premise webhooks: which events and how they arrive
Debentra sends webhooks for relevant status changes: due, overdue, payment received and partial payment. The notification contains structured information about the invoice (invoice number, customer, outstanding amount, due date, status, link to the Debentra instance) so recipient processes can react automatically.
Delivery is made to endpoints you manage within your infrastructure — ideal for companies with their own IT operations that want to retain data sovereignty and control.
Use case 1: Automatic ticket creation in the internal support/finance workflow
Situation: An invoice is 7 days overdue. Instead of waiting for manual reports, the webhook automatically creates a ticket in your ITSM.
Implementation in the workflow:
- Debentra triggers a webhook on the status change "overdue".
- Your endpoint receives the event and creates a ticket with standardized fields: invoice number, customer, outstanding amount, due date, priority.
- The ticket contains links back to the Debentra view and to the original invoice as well as suggestions for the next action (send reminder, follow up by phone, review payment arrangement).
Practical tip: Define rules for prioritization (e.g. high priority for key accounts) and use a ticket field "approval required" when a payment reminder needs manual consent. This keeps control with the user.
Use case 2: Slack/Teams notification for rapid internal responses
Situation: The accounting team wants to be informed immediately without checking the Debentra interface daily.
How you can use webhooks:
- Debentra sends a payload to your middleware endpoint when the status changes.
- The middleware creates a concise message for Slack or Microsoft Teams: customer, invoice number, outstanding amount, deadline, recommended action.
- Optional: Interactive buttons (e.g. "Approve reminder", "Create ticket") forward to internal endpoints that in turn trigger actions in Debentra or create tickets.
Important: Even with push notifications, approval for reminder letters remains under your control. Configure a manual approval in the workflow or an approval webhook path before a dunning notice is sent to customers.
Use Case 3: ERP Synchronization and Account Reconciliation
Situation: A partial payment is received or a payment is fully allocated. ERP systems must adjust the open item.
How synchronization works:
- Debentra sends an event on payment receipt/partial payment with references (Debentra ID, external reference, amount, booking date).
- Your ERP connector compares using the references, performs the allocation and posts the payment receipt or adjusts installment plans.
- On discrepancies (e.g. shortfall) the connector creates a flag or ticket for manual follow‑up.
Practical tip: Use idempotent processing (e.g. based on the webhook event ID) to avoid duplicate postings. Batch processing of large volumes is recommended outside peak business hours.
Security and Reliability of Your On‑Prem Webhooks
Since webhooks go to your own infrastructure, security measures are central. Debentra supports key mechanisms that you should complement within your own network:
- IP whitelist: Accept only connections from defined Debentra source IP ranges in your firewall.
- HMAC signatures: Each payload can be signed with an HMAC header. Verify the signature server‑side to prevent tampering.
- TLS/HTTPS: Mandatory: TLS for all endpoints, valid certificates and up‑to‑date cipher suites.
- Replay protection: Check timestamps and event IDs to detect repeated or delayed requests.
- Logging & monitoring: Log received events, response codes and errors for traceability and troubleshooting.
Additionally, rate limiting and automatic backoff strategies are recommended: if your endpoint returns an error, Debentra will retry according to a defined logic — make sure to consider how your middleware handles this.
Implementation Checklist (practical, concise)
- Provide endpoint: URL, TLS, authentication.
- Configure security rules: IP whitelist, HMAC verification.
- Define mapping: Which fields trigger which actions (ticket, Slack, ERP).
- Idempotency: Store event IDs and prevent duplicate processing.
- Model approvals: Design workflows so reminders are only sent after review.
- Monitoring: Set up alerts for outages or high error rates.
Why on‑premises webhooks with Debentra make sense
The combination of automatic event detection and on‑premises delivery offers tangible benefits for companies with their own IT operations: faster response times, fewer manual assignments and full control over customer data. Debentra delivers the events; your infrastructure decides which follow‑up actions are executed — including approval levels and secure processing.
Conclusion and next step
Webhooks in dunning are not a gimmick but a pragmatic bridge between accounts receivable overview and operational systems. Whether ticket creation, Slack/Teams notification or ERP sync: with clear rules, HMAC signatures and IP whitelists, automated processes can be securely integrated into your infrastructure. Control remains with the user — especially regarding the approval of payment reminders.
Learn more and choose the right edition: Choose an edition.
Next step
Try Debentra yourself
Central overview and process control for open items and payments with full data sovereignty; reduces manual matching work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.