When the invoice is overdue but nobody follows up
An invoice is overdue, reminders are sent too late and replies get lost in the general email inbox. Accounting imports payment files, yet many items remain unresolved because account details or payment references do not match 1:1. That costs time, nerves and ties up personnel resources.
Why rules for automatic payment allocation help
A structured open‑items workflow simplifies exactly this routine: take over invoice → recognize open item → follow up → prepare payment reminder → approve and send → detect reply or payment → document the process. In Debentra PRO you set up automatic matching rules that recognize recurring patterns and process payment imports without manual intervention. You still retain control: rules speed up allocation, approvals and exceptions remain visible and auditable.
Purpose of the rules
Less manual work while maintaining high reliability. This article presents 10 practical rules you can configure in Debentra PRO — with concrete examples for booking reference, amount tolerance and name variations.
The 10 rules (with concrete examples)
1. Exact invoice number matching (booking reference)
Rule: If the payment reference contains the exact invoice number, then automatic allocation.
Example: Payment reference “Rechnung INV-2025-0812” → matches invoice INV-2025-0812. Recommendation: normalize (case, remove hyphens) before matching.
2. Recognize partial payments (partial sums & installment plans)
Rule: If the received amount is smaller than the open item, create a partial payment entry and link it to the corresponding installment plan or open item.
Example: Open item €1,200.00; payment €400.00 → mark as partial payment and update remaining balance. In PRO you can set up installment plans so recurring partial payments are posted consistently.
3. Amount tolerance for bank fees and rounding
Rule: Allow an absolute or percentage tolerance in amount matching (e.g. ±€2.00 or ±0.5%).
Example: Invoice €99.95; payment €100.00 → difference €0.05 within tolerance → automatic allocation. This way small bank fees or rounding differences are tolerated automatically.
4. Consolidated payments (one payment for multiple invoices)
Rule: If the payment reference contains multiple invoice numbers or the amount equals the sum of several open items, then allocate to all affected items.
Example: Payment €3,450.00 equals the sum of three invoices of €1,150.00 each → automatic split posting across the three invoices.
5. Fuzzy matching on payer names
Rule: Use fuzzy string matching to account for variations in payer names (typos, abbreviations, missing company suffixes). Assign a match score threshold to trigger automatic allocation.
Example: Payer name “Müller GmbH” vs. bank reference “Mueller GmbH” → high similarity → auto‑match if score above threshold. Configure thresholds to balance recall and precision.
Rule: Use normalization and fuzzy matching (e.g., removal of legal forms, spaces, umlaut substitutions) and set a match-score threshold (e.g., 85%).
Example: “Müller GmbH”, “Mueller GmbH”, “Müller G.m.b.H.” → all are recognized as the same payer. Recommendation: remove terms like GmbH, AG, UG before matching.
6. Variations in reference formats (prefixes, spaces, character sequences)
Rule: Register patterns (e.g., INV, RE, RG) and set regular expression filters to recognize invoice numbers with and without prefixes.
Example: Invoice “2025/0812” vs. payment reference “RG20250812” → a regex like '\d{4}0?8?12' (configured in PRO) helps with recognition.
7. Post fees and deductions separately
Rule: Differences that exceed tolerance and are identifiable as fees (e.g., “Bank fee” in the purpose text) are recorded as expense items and the remaining amount is allocated.
Example: Payment €98.00 for an invoice of €100.00 with purpose “Fee 2.00” → €2.00 recorded as bank fee, €98.00 covers the invoice.
8. Currency deviations and conversion
Rule: For payments in foreign currency, use the exchange rate at booking time or configurable tolerances for small differences after conversion.
Example: Invoice €1,000.00, payment in USD equals €999.20 after conversion → difference within tolerance → allocation possible.
9. Prioritization when multiple matches occur (timestamp, account source)
Rule: If multiple open items potentially match, prioritize by payment order date, bank account, or most recently modified item. Flag remaining uncertainties for manual review.
Example: Two matching invoices, but the payment execution date matches the due date of one of them → allocate that one first.
10. Define exceptions and manual approvals
Rule: Large amounts, new payers, or deviations above thresholds are marked for manual approval. This way you retain control despite a high automation rate.
Example: Payments > 10.000,00 € or new IBANs require approval by a clerk before the allocation is posted final.
Typical mistakes and how to avoid them
- Rules that are too strict: Not setting tolerances leads to many unmatched payments. Solution: Start with moderate tolerances and reduce them as needed.
- Excessive trust in fuzzy matches: Too many false positives occur with thresholds that are too low. Solution: Combine name matching with additional criteria (amount, account, reference).
- Lack of documentation: Rules without version history are hard to trace. Solution: Give rules descriptive names and document changes.
Practical example: A payment import in three steps
1) Import payment file: Debentra PRO reads the file and normalizes fields (reference, name, amount).
2) Apply rules: first exact reference matches, then partial payments and tolerance checks. Detection rules automatically mark settled items; multiple allocations are split.
3) Review & release: hits with a high confidence level are posted; exceptions go to a review list. Case handlers confirm large amounts and unusual deductions.
The result: significantly fewer manual allocations, an auditable trail and complete documentation on your own infrastructure.
Concrete benefits for your finance teams
With a few well-designed rules you reduce routine effort, error sources and customer queries. The PRO edition of Debentra provides rule management and matching logic to process payment imports automatically — with full data sovereignty on your infrastructure. Control stays with the user: approvals and exceptions are kept transparent and auditable.
Short checklist to get started
- Identify the most common deviation types in your payment data (fees, name variants, partial payments).
- Start with 5 rules: exact reference, amount tolerance, partial payments, name fuzzy, multiple allocation.
- Set thresholds for manual approvals (amount, new payer, unusual payment purposes).
- Document and test rules using a test import before enabling them in production.
Automatic matching is not a substitute for control – it is a lever to halve repetitive work and make your receivables management more efficient.
Act now
Choose the appropriate edition and set up your first matching rules in Debentra PRO: Choose 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.