When an invoice gets lost in the inbox: Why mapping is more than just technology
An invoice is overdue, nobody followed up, reminders are sent too late — and responses get lost in email chaos. In many cases the problem is not only with accounting but with poorly imported master data: missing debtor IDs, incorrect currencies, or unrecognized partial payments. A structured import mapping prevents such errors and ensures that open items are reliably represented and tracked in Debentra.
What matters: Core principles for the import
- Define clear required fields: import only complete records.
- Primary matching rule: unique debtor ID instead of names.
- Detect errors early: test runs, plausibility checks and logs.
- Control stays with the user: notifications and approvals for reminders.
Import Mapping Debentra: Preparation phase
Before you move data, establish these fundamentals:
- Backup and test system: Create a database backup and, if possible, use a Debentra test instance or a separate environment.
- Involve stakeholders: Coordinate accounting, IT and debtor managers — especially on currency rules and cash discount policies.
- Check the source: Verify exports from ERP/FiBu/Excel for completeness, character set (UTF-8), date formats and decimal separators.
Required fields and useful additions
For robust mapping, the following fields should be available by default. Adapt the list to your Debentra configuration:
- Debtor ID: Primary key for assignment. If not present, define a consolidation procedure.
- Invoice number & invoice date: Check uniqueness, avoid duplicate imports.
- Due date: Relevant for dunning processes and cash flow planning.
- Invoice amount & currency (ISO code): Use consistent currency identifiers; for foreign currency also provide the rate reference date.
- Cash discount and payment terms: Cash discount percent / days as separate fields, clear mapping to internal conditions.
- Partial payments & installment plans: History with date and amount or linkage to open partial items.
- Tax codes: Consistent assignment to accounting accounts; mark deviations.
- Document files/attachments: Provide file paths or hashes so attachments can be matched.
- Free text/notes: For internal remarks, e.g. payment agreements.
Debtor matching: rules and fallbacks
A robust matching process prevents duplicates and incorrect assignments:
- Primary: Exact customer ID. If present, always prefer it.
- Fallback: If no ID is available, define a combined rule (e.g., company + postal code + country).
- Limit fuzzy matching strictly: Use name variants only with a score threshold and manual approval to avoid incorrect merges.
- Display warnings: Mark records for manual review in case of potential conflicts.
Currency and Discount Mapping
- Use ISO currency codes (e.g., EUR, USD) instead of free-text currency names.
- For foreign currencies, include the exchange rate date and source (ERP rate, bank rate).
- Pass discounts as clearly structured fields (percentage, payment term in days) so Debentra can automatically calculate possible discount deductions.
- Observe formats: keep decimal separators consistent (e.g., period or comma) and convert them before import if necessary.
Duplicate Checking: Practical Procedure
- Primary check rule: combination of customer ID + invoice number. If this combination already exists, move the record to review mode.
- Checksum: create a checksum for each record (e.g., invoice text + amount + date). This helps detect accidental double imports.
- Consider partial payments: clarify the difference between a new invoice and an additional payment.
- If in doubt: automatic stop and notification to the responsible person instead of automatic overwriting.
Test Run Strategies: Dry-Run and Quality Control
Immediately before the production import, perform the following tests:
- Dry-Run: Import into a test mode that logs validation errors, conflicts, and suggested actions but does not overwrite any data in the production system.
- Sample analysis: Check a random selection of 50–200 records: customer assignment, amounts, currency, and discounts.
- Totals comparison: Compare the total number of invoices and the sum of open items before and after the test import.
- Error reporting: Categorize and prioritize all errors (format errors, missing required fields, match conflicts).
- Rollback plan: Define how a faulty import will be undone (backup restoration, targeted deletion of import batches).
Step-by-Step Procedure for the Production Import
- Create a backup of the production database.
- Perform a test import and review the validation report.
- Fix identified errors and adjust the source file.
- Start the import in small batches (e.g. 100–500 records); do not import everything at once.
- After each batch, perform plausibility checks and reconcile totals.
- Submit conflicts to the review workflow; avoid automatic overwrites.
- If successful, continue with subsequent batches; otherwise perform a rollback according to plan.
- Finally: archive complete audit and change logs.
After the import: monitoring and follow-up
- Check open items for plausibility (count, total amount, distribution by due dates).
- Plan manual follow-up for flagged conflicts – prioritize by importance (e.g. high amounts first).
- Regular operation: run automatic matching jobs, but keep approvals for payment reminders.
- Set up reports that alert on unusual patterns (sudden increase in open items for a single debtor).
Practical notes on Debentra editions
Debentra is available as a self-hosted solution in three editions. Two benefits are relevant for import mapping:
- PRO: Supports extended automation in assignment and reduces manual allocation work through improved matching rules.
- PREMIUM: Adds integrated accounting features to receivables management, making mapping to GL accounts and tax codes easier.
Regardless of edition, control over reminders and approvals remains with the user – automations are recommended but should be secured by roles and approval processes.
Security and infrastructure note
As a self-hosted solution, Debentra enables full data sovereignty: import files and logs remain on your infrastructure. Ensure that access rights, transport encryption and backup strategies are checked before the import.
Conclusion: How to avoid common import pitfalls
The quality of the import determines whether open items are reliably represented in Debentra and whether automated workflows can be used effectively. Focus on clean debtor IDs, consistent currency and discount information, strict duplicate checks and thorough test runs. When in doubt, prefer small batches and manual reviews – this keeps control with the user, makes errors reversible and keeps operations stable.
Put it into practice now: Choose the appropriate Debentra edition and plan the first test import. Choose edition: https://debentra.de
Next step
Try Debentra yourself
Central overview and process control for outstanding items and payments with complete data sovereignty; reduces manual allocation work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.