An invoice is overdue, nobody followed up, and payment confirmations get lost in the email inbox. Weeks later the accounting department is faced with a stack of bank statements in different formats: CSV from online banking, MT940 from the company account and camt.053 as an XML file. The question is: how can you quickly and reliably determine again which payments belong to which invoices — while keeping full control over your own data?
Why the file format matters
Bank files differ in structure and level of detail. MT940 is a widely used format with compact booking records, camt.053 (ISO 20022 XML) provides more structured information such as references and detailed booking descriptions, while CSV files vary greatly depending on the bank and export settings. The correct import approach ensures that as many payments as possible are assigned automatically — and only the real exceptions need to be checked manually.
Before import: quick checks and preparation
- Identify the file type: MT940, camt.053 or CSV? This determines the parsing and mapping steps.
- Ensure CSV quality: Check whether columns for date, amount, currency, IBAN, booking text and value date are present. A consistent delimiter and UTF-8 encoding prevent errors.
- Consistency of character sets: Special characters in payment references can interfere with matching — clean them up beforehand if necessary.
Import into Debentra: how the process runs on‑prem
Debentra runs on your own infrastructure and processes all three file types. The import follows a clear procedure:
- Upload file: Select the file in the bank imports interface. Debentra recognizes MT940 and camt.053 automatically; for CSV you can choose or create an import profile.
- Check mapping: For CSV Debentra shows a preview and allows assigning columns (amount, date, IBAN, payment reference). MT940/camt.053 are parsed and presented as booking records.
- Apply import rules: Predefined assignment rules are checked (more on this below). Results are shown as "automatically assigned", "ambiguous" or "no assignment".
- Audit log and storage: All imported bookings are stored in a tamper-proof manner on your infrastructure — traceability is preserved.
Automatic assignment rules: principles and priorities
The core of the automation consists of rule-based matching rules that can be configured in Debentra. Important types of rules:
- Direct matching by invoice number: If the payment reference contains the invoice number, this is the most precise allocation.
- Amount and currency matching: Exact match or definable tolerances (e.g. bank fees, rounding differences).
- Payer identification: Matching via IBAN, BIC or debtor name, if available.
- Partial payments and installments: Rules that assign partial amounts to an open invoice or to an installment plan.
- Priority logic: Debentra executes rules in a defined order — first unique reference matches, then heuristic hits (e.g. amount + name similarity).
Practical tip: Start with strict rules (invoice number + amount) and gradually widen tolerances if too many genuine payments are not being recognized.
Special challenges and how Debentra handles them
- Bank fees and splits: MT940 and camt.053 often include separate fee entries. Debentra can automatically assign fees to a payment receipt or record them as a separate booking, depending on the rule.
- Altered payment references: If a customer only provides part of the invoice number or uses abbreviated texts, name and amount heuristics as well as a fuzzy-matching option help.
- Partial payments: Installment plans are taken into account so that partial amounts are correctly allocated to an open item.
- Multiple invoices in one payment: Debentra offers the option to split payments across multiple invoices when a match can be detected by totals and references.
Manual review paths: When automation isn’t enough
Automatic allocation reduces effort, but exceptions remain. Debentra provides a clear review process for this:
- Exception queue: All non-uniquely allocated postings land in an overview with filter and search functions (date, amount, payment reference, account).
- Context information: For each exception, invoice data, debtor history and previous communication notes are visible — this speeds up decision making.
- Manual actions: Postings can be assigned via drag & drop, split across multiple invoices, marked as fees or rejected.
- Team workflow and approvals: Responsible persons can assign tasks; important reminders or dunning notices remain subject to approval so control stays with the user.
- Documentation: Every change is logged — who made which allocation and when. This simplifies inquiries and later audits.
Practical everyday examples
Example 1: A payment without a clear invoice number, exact amount — Debentra finds the matching open item by IBAN and amount and marks the match as high confidence. The accounting team confirms and the invoice is automatically posted as paid.
Example 2: Payment entry with fees: A transaction transfers 1.000 EUR, bank fee 2 EUR booked separately. Debentra recognizes both items in the MT940/camt.053 and either aggregates them correctly or assigns the fee as a separate expense — depending on the rule.
Example 3: Multiple invoices in a collective payment: Debentra offers the option to split the payment pro rata or based on available references and thus document official settlements cleanly.
On‑prem, data sovereignty and editions
Debentra runs on your infrastructure, so bank files and allocations remain under your control. For companies with their own IT operations, this is a central advantage over cloud-only solutions.
Editions:
- BASIS: Basic imports and manual allocations.
- PRO: Advanced automation to reduce manual allocation work (rule-based matches, partial payments, exception queue).
- PREMIUM: Additionally integrated accounting features and extended interfaces for seamless processes.
Important: Regardless of the level of automation, users retain approval authority — payment reminders or dunning letters are only sent after review and approval.
Implementation checklist for the first import
- Detect file type and check encoding.
- For CSV: create an import profile and map columns correctly.
- Test strict matching rules, then gradually widen tolerances.
- Set up an exception queue and assign responsibilities.
- Check the audit log and schedule regular backups of the on‑prem installation.
Conclusion: Less manual work, full control
The correct import of MT940, camt.053 or CSV significantly reduces manual effort — provided you work with clear matching rules and a defined review path for exceptions. Debentra supports this process on‑prem: automated allocations, configurable rules, documented exceptions and manual review paths when necessary. PRO editions noticeably reduce allocation work; PREMIUM additionally offers integrated accounting features for tightly integrated processes.
Do you want to test the payment import in your own data center and choose the appropriate edition? 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 license models.