When payments arrive without a reference – and accounting becomes a detective team
The common case: a credit appears on the bank statement that does not match any open invoice — the customer number is missing from the payment reference, the name is spelled differently, or it is a partial payment. In many companies this booking process lands in an employee's email inbox, who must manually allocate payments. That costs time, creates errors and delays dunning sequences.
Why rule-based matching reduces the problem
Rule-based matching automates the assignment of bank transactions to open items using clear, traceable criteria. Instead of checking every deviation manually, the software evaluates defined rules (e.g. amount tolerance, temporal proximity, account relation, name similarity) and proposes matches or performs allocations automatically — with full control by your team. In Debentra, such rules can be run on your own infrastructure so you retain data sovereignty and adapt processes to your internal requirements.
Which matching rules make sense (and how they work)
Start with a few well-defined rules. Each rule should be documented clearly and prioritized.
Amount + tolerance
Base rule: compare the bank amount with the outstanding invoice amount. Add a tolerance range (e.g. fixed cents deviation or percentage value) to account for variations due to fees, third-party amounts or rounding differences. Use partial payment logic if partial amounts are accepted.
Timestamp / payment window
A payment is often expected within a few days after invoicing or due date. Define a time window (e.g. invoice date up to X days after the booking date) that serves as a criterion. Shorter windows increase precision; longer windows catch late payments or delayed statements.
Bank account / counterparty account
If you have multiple bank accounts or subsidiaries, the counterparty account is a strong distinguishing feature. Rules applied to specific accounts reduce misallocations because they only match payments with the relevant open items.
Customer name / string matching
Name fields are often incorrect. Use sensible text-matching strategies: exact match, normalization (remove diacritics, spaces) and fuzzy matching (Levenshtein distance or token comparison) for slight variations. Prioritize exact hits and use fuzzy hits as a secondary criterion.
Combination of rules and weighting
Combine multiple criteria into a weighted rule: one rule point for exact amount, one point for date within the window, one point for account match. Rules with a high score are preferred. Thus a match suggestion with several matches takes precedence over one matching only a single criterion.
Prioritization for ambiguities: How to make safe decisions
Multiple open items can match the same payment. Define a transparent prioritization logic:
- Score threshold: If a hit reaches a defined score, the allocation is performed automatically. If the score is below that, the posting goes into the manual review queue.
- Tie‑breaker: For equal scores, choose defined successors: prefer exact amounts over fuzzy names, newer invoices over older ones, or specific accounts over general ones.
- Partial payments: If several possible invoices match sums, enable a partial payment rule that either suggests a split or requires manual approval.
- Blacklist/whitelist: Mark regular exceptions (e.g., intercompany transfers) for automatic exclusion.
Documenting the decision in Debentra
After each automatic or manual allocation, the decision and the rules applied should be stored in a traceable way. Pay attention to the following documentation points:
- Rule reference: The matching rule applied is logged in the transaction (rule name, version, weighting).
- Score and criteria: Stored details of which criteria were met (amount, date, account, name similarity) and the resulting score.
- Attachments and notes: Relevant bank statement lines, email communication, or screenshots are associated with the item.
- Audit trail: Who approved or overrode the allocation and when? This information is important for traceability and internal controls.
In Debentra these details remain on your own infrastructure so that compliance and data protection requirements can be met.
Practical step‑by‑step setup
How to pragmatically set up rule‑based matching:
- Start with a base rule: exact amount + account match. Test mode: generate suggestions only, do not post automatically.
- Add a time window (e.g. invoice date ± X days) and enable normalization of the customer name.
- Add fuzzy matching as a secondary criterion and define a score for each match.
- Set an automatic threshold: only scores ≥ the defined value are posted automatically; low scores go into the review queue.
- Create an exception list for common deviations and test the rules over an observation period (e.g. two weeks).
- Analyze misassignments: adjust tolerances, shift priorities, add rules for recurring cases.
Typical mistakes and how to avoid them
- Too narrow tolerances: Lead to many manual cases. Start conservatively and tighten later.
- Too many automatic rules without a review mode: Prevent incorrect postings by proceeding in stages (suggestion → semi-automatic → fully automatic).
- No audit trail: Without a traceable history, accounting confidence decreases. Documentation is mandatory.
- No regular maintenance: Rules must be maintained and adapted to changed payment practices.
Practical benefits for your team
With a lean set of rules you will significantly reduce the number of manual allocations. Debentra allows you to operate rules yourself, finely control priorities, and document every decision. Control over automatic postings remains with the user: you determine from which score an automatic allocation occurs and which cases go into manual approval. In Debentra's PRO mode you can thus specifically reduce manual allocation work; in the PREMIUM edition, matching can be seamlessly linked with integrated accounting.
Maintenance and monitoring
Set up short monitoring: weekly evaluation of unallocated transactions, list of overridden automatic allocations, and a quarterly review of rule performance. Adjust tolerances and priorities based on real cases.
Conclusion and next step
Rule-based matching reduces routine work, speeds up the settlement of open items, and creates transparency — provided rules are well thought out, prioritized, and every decision is documented traceably. Debentra provides the tools to define rules flexibly and keep control with the user. Start with a few clear rules, observe the results, and expand iteratively.
Test now: Choose an edition — Learn about the available options and choose the right edition for your receivables management: https://debentra.de
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.