When two people work on the same invoice: everyday occurrence rather than exception
An invoice is overdue. Two team members open the same open item: one records a partial payment while the other changes a dunning date and prepares a reminder. Changes are lost, reminders are sent multiple times or not at all — and tracking becomes opaque. Such situations cost time, create uncertainty and increase the risk of errors in documentation.
Why conflicts arise with open items
- Multiple users access the same open item position at the same time.
- Different subprocesses (payment allocation, dunning, notes) are processed in parallel.
- Communication happens outside the system (email, chat), changes are not synchronized.
- No transparent audit trail: who changed what and when?
The consequence: duplicated work, lost entries and a fragmented documentation state. A structured open‑item workflow with targeted protection mechanisms prevents these problems.
How Debentra detects competing edits
Debentra monitors session states and record versions. With parallel access the system identifies temporal overlaps and inconsistent version numbers. It detects:
- Simultaneous opening of the same record by multiple users.
- Conflict between local changes and the current server version.
- Attempts to overwrite newer entries with older edits.
Detection is the basis for targeted measures: locking, targeted merging or a controlled conflict workflow.
Locking mechanisms: Full lock vs. field‑level locking
Debentra offers two basic locking models that can be combined depending on team size and process needs:
Full lock (Record Lock)
For critical actions such as final approval of a payment or sending a dunning notice, a record lock can be applied. This prevents other users from making concurrent changes until the lock is released or the action is completed. Use case: when changes have significant legal or accounting consequences or consistent finalization is required.
Field‑level locking
A finer alternative is field‑level locking: users lock only the fields they are currently working on (e.g. payment allocation, dunning text, due date). Other team members can edit different fields in parallel — this reduces waiting times and minimizes conflicts during concurrent work.
Practical rule: use full locks where consistency is indispensable; field locks for routine edits that require parallelism.
Merge history and traceability
Conflicts cannot always be resolved automatically. Therefore, a transparent history is crucial:
- Versioned change logs show who changed which fields and when.
- Visual comparison views ("before / after") make it easier to merge edits.
- Automatic documentation of merge decisions records which change was accepted and which was discarded.
This history serves both tracking and internal accountability: audit documentation remains complete without users having to rely on workarounds outside the system.
Conflict Resolution Workflows: Step by Step
An effective conflict workflow consists of clear, simple steps — this keeps control with the user and minimizes errors.
1. Automatic Marking and Escalation
When competing edits are detected, Debentra marks the record and notifies the affected users. Depending on your configuration, the system can immediately suggest a full lock or apply field-level locks.
2. Notification and Brief Info
Affected users see who is currently working on the record, which fields are occupied, and which changes are pending. This allows overlaps to be resolved without back-and-forth questions.
3. Preview & Comparison
Before merging, Debentra offers a comparison view: local change versus current server version. The responsible person chooses whether to accept the local change, keep the server version, or manually merge specific fields.
4. Approval and Documentation
The merge is logged; for actions that affect customers (e.g., payment reminders) approval remains with the user: reminders are prepared, and the final selection and sending require an explicit confirmation.
5. Revert and Audit
Every merge decision can be traced and, if necessary, reverted. The history is preserved, which simplifies internal audits.
Concrete Checklist for Your Team
- Define policy: When is a full lock applied, and when field-level?
- Enable field-level locking for fields frequently edited in parallel (notes, reminder texts, payments).
- Adjust notification settings: who is informed and after what time interval.
- Define review roles: who performs final merges and who is authorized to approve reminders.
- Train the team: practice comparing, merging, and approval processes.
Practical Example: Small Accounting Team
Case: A partial payment arrives, two employees work in parallel on the allocation and the dunning. Debentra detects the simultaneous opening of the receivable, automatically locks the field “Payment Allocation” for the first editor and leaves the field “Dunning Level” open for the second. The second employee notices the lock, adds an internal note and prepares a reminder. The reminder remains in draft until a responsible person reviews the payment situation and approves the dunning. Changes are logged in the merge history. Result: no overwrites, complete documentation, approval remains with the team.
Implementation tips
- Start with conservative lock settings and expand field‑level locking gradually.
- Use audit functions for regular reviews to keep workflows well documented.
- Configure notifications so they inform without causing distraction.
- As a self‑hosted solution, Debentra offers the option to run lock and workflow rules within your infrastructure — data protection and processes remain under your control.
Which edition suits you?
Debentra is available in three editions: BASIS, PRO and PREMIUM. For small teams aiming to reduce parallel work and minimize manual allocations, PRO offers extended matching and automation features. PREMIUM adds integrated accounting functions and deeper process control. Regardless of the edition, approvals and final reminders remain in the hands of your responsible staff.
Conclusion: Prevent conflicts, keep control
Competing edits to open items are a common source of errors and extra work in smaller B2B accounting teams. With targeted locking mechanisms, field‑level locking, an auditable merge history and clear conflict‑resolution workflows, this extra effort can be significantly reduced — without relinquishing control. Debentra links these features with centralized overview and process control on your infrastructure so teams can work more efficiently while retaining data sovereignty.
Act now: Choose an edition and configure the appropriate lock and merge workflows for your team: https://debentra.de
Next step
Try Debentra yourself
Centralized 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.