When invoices from different companies end up in the same inbox
Monday morning: the email inbox contains several payment reminders and inquiries for three different brands of your corporate group. Accounting is unsure which receivables belong to which accounting unit, dunning letters are sent late and replies get lost in general distribution lists. The result: extra work, incorrect allocations and increased risk during audits.
Why clean client management is more than comfort
Multiple legal entities within a single company require clear separation lines. It's not just about appearance or branding: data isolation, correctly filtered overviews, client-specific templates and reliable reporting mechanisms are crucial for data security, auditability and efficient processes in receivables management.
What IT and finance teams must pay attention to
- Data sovereignty: customer data, invoices and payment proofs must remain on the company's own infrastructure.
- Access control: only authorized users may view client data or send documents.
- Client scope for templates: each entity needs its own communication templates and footer text.
- Reporting and archiving: reports must be exportable per client and be audit-proof.
- Control mechanisms: automations may prepare actions — approvals remain with the user.
Client management in Debentra: The practice
Debentra as a self-hosted solution was designed so that IT teams retain data sovereignty and finance teams can map clear, client-specific procedures. The most important components at a glance:
Data isolation
In an on-premise Debentra instance, customer masters, invoices, open items, payments and documents remain within the respective client context. Users by default only see the records they are authorized to access. For IT this means: storage and backups take place on company infrastructure, and data processing workflows are traceable and under control.
Client filters and role-based access
The user interface and API queries are client-aware: an active client filter ensures that lists, search results and dashboards are immediately limited to the relevant entity. Combined with roles (e.g. Finance, Accounts Receivable Manager, Admin), this prevents accidental data mixing and provides clear responsibilities for approvals and dispatch.
Template scopes: branding and legal texts per entity
Templates for dunning notices, payment reminders or invoice enclosures can be created per client. This ensures consistent customer communication: logo, company name, payment terms and legally relevant notes can be configured individually per client. Automated reminders are prepared in the respective template — the decision to send remains with the user.
Client‑specific reporting and audit trail
Reports can be run per client or — for authorized users — displayed in a consolidated view. Important for audits: every action is documented. Who prepared, approved or sent which dunning notice? Which payments were assigned to which posting ledger? This traceability simplifies collaboration with internal audit or external reviewers.
A concrete workflow: Three brands, one system
Practical example step by step, without technical jargon:
- Setup: IT installs Debentra on‑prem and creates three clients (Brand A, Brand B, Brand C). For each client, storage locations, backup intervals and access rules are defined.
- User assignment: Finance management assigns staff: accounts receivable managers are each assigned to a brand, central admins have overview rights for all clients.
- Data intake: Incoming invoices or payment confirmations are assigned to the appropriate client — manually or via rules (e.g. customer number prefixes).
- Preparation of reminders: Accounts receivable managers see only the open items for their client, generate client‑specific payment reminders and submit them for approval.
- Approval: A finance lead reviews the reminders and releases the sending with one click. Communication is sent with the correct branding and the appropriate legal notices for the respective client.
- Documentation: Incoming replies, payment reconciliations and partial payment agreements are documented in the client context; reports are created and exported per client.
Which edition fits which need?
Debentra is available in three editions: BASIS, PRO and PREMIUM. A brief positioning without technical promises:
- BASIS: Core functions for client management and process control — suitable if you primarily need data sovereignty and separated workflows.
- PRO: This edition further reduces manual allocation work through extended matching and rule mechanisms — sensible if many payments should be assigned automatically.
- PREMIUM: Additional features for tighter integration into accounting processes — useful if accounts receivable processes should be more closely linked with financial accounting.
Important: Debentra is not a full ERP, nor a replacement for accounting software or a debt collection service. The system structures the invoice → open item → follow‑up → reminder → approval → payment recognition and documentation and returns control to users.
Practical checklist for rollout
- Define client structure: clearly name legal entities, brands or ledgers.
- Assign users and roles per client.
- Create templates for each client (branding, payment terms, legal notices).
- Set up approval workflows for reminders — automation may prepare, not decide.
- Enable audit logs and client‑specific exports for audits.
- Test reporting and data access with a proof‑of‑concept before going live.
Conclusion and next step
With a self‑hosted client management, different companies, brands and ledgers can be cleanly separated — without giving up the benefits of centralized process control. Debentra provides the features IT teams need to maintain data sovereignty and compliance, while finance teams can use clear, client‑specific workflows. Control over automated steps remains with your employees.
If you want to check which edition fits your client structure, choose your edition now: 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.