When an invoice gets lost in the email stack — and the open items list grows
An invoice becomes overdue, nobody followed up, reminders are sent too late or replies get lost in the email inbox. Exactly in these situations a structured import and validation pipeline helps: it transfers invoices from your local accounting software (e.g. DATEV export or generic CSV) cleanly into the open items overview and reduces manual rework.
Why clean invoice imports are important
An incorrect import creates duplicate entries, unclear assignments and gaps in tracking. That costs time and worsens receivables management metrics. Debentra, as a self-hosted solution, is designed to accept invoice exports, map fields accurately and run validation rules before ingestion — while the approval of payment reminders always remains in your hands.
Step by step: prepare the invoice export
Start in the local accounting program with a clean export. For DATEV exports or CSV files: reduce possible sources of error already before exporting.
- Select a consistent date range (e.g. end of month to end of month).
- Export all relevant fields: invoice number, invoice date, due date, net amount, tax amount, gross amount, customer number, customer name, customer address, open item status, payments received and links to attachments.
- Use a consistent date format (e.g. YYYY-MM-DD) and consistent decimal separators (dot or comma, depending on the system).
- If possible: use a column with a unique invoice ID (invoice number + client) for duplicate detection.
Mapping checklist: which fields Debentra expects
During import you map columns from the file to Debentra fields. Check the following mappings systematically:
- Client / Company code: mandatory when multiple clients are managed.
- Customer number: preferred key variable for assigning debtors. If missing: name + address for fuzzy match.
- Customer name and address: for identity verification and documentation.
- Invoice number: central for duplicate checks.
- Invoice date and due date: for calculating dunning periods.
- Amounts: net, tax amount, gross — check consistency (net + tax == gross).
- Status: open/paid/partially paid — important for open items.
- Partial payments / instalments: separate lines or linked booking lines should be importable as a payment history.
- File path / document link: reference to scan or original document for documentation.
Validation rules before importing (Dry‑Run)
Before data is finally loaded into Debentra, automated checks in dry‑run mode are recommended. These validation rules detect inconsistencies, prevent duplicates and highlight where manual follow-up is required.
- Check required fields: customer number (if client requirement), invoice number, invoice amount, due date.
- Format validation: date fields, numeric formats, e‑mail/phone formats for contacts.
- Sum consistency: verify whether net + tax = gross. Flag deviations.
- Duplicate detection: compare based on invoice number + client or invoice number + customer number; optional fuzzy match on name/date.
- Missing debtors: list records without customer number and offer options (create new, match by name, skip import).
- Partial payments and instalments: validate assignment of incoming payments to open items; report inconsistencies.
Result of the dry‑run: an error list and a preview of the open items to be imported. Correct the file or define rules in Debentra before triggering the final import.
Typical sources of error and how to avoid them
- Duplicates: Causes are duplicate exports or different numbering ranges. Solution: use unique keys and test duplicate rules in a dry run.
- Missing customer numbers: Many accounting exports do not include a customer number. Solution: match addresses by name/address or manually add them before import.
- Inconsistent amounts: Rounding differences arise from different tax rates or total calculation errors. Solution: enable sum checks and flag discrepancies.
- Incorrect date formats: Especially common with international exports. Solution: use a standardized date format in the export file.
Practical procedure in Debentra — concrete process
In your Debentra instance the following procedure is recommended, combining control and automation:
- Create an export from DATEV/CSV and upload the file to Debentra.
- Perform mapping: assign columns to fields; save the mapping as a template for recurring exports.
- Start a dry run: run validation rules, review the results, correct errors or define exceptions.
- Approve the import: after visual inspection import — accounting entries appear as open items.
- Post-processing: review open items, allocate partial payments (PRO reduces manual allocation) and prepare dunning levels.
- Prepare payment reminders: review and approve texts — Debentra creates the template, you decide on sending and timing.
How Debentra eases daily work — two concrete benefits
- Reduced manual allocations (PRO): Imported records provide clear keys for matching. Debentra suggests allocations, you review and confirm — fewer clicks, fewer errors.
- Complete data sovereignty: Self-hosted operation on your own infrastructure; all checks and approvals remain controllable locally, automated processes remain controllable through approval steps.
Best practices
- Save mapping templates for monthly exports.
- Regularly perform a dry run before importing large amounts of data.
- Assign roles in Debentra: who may import, who may approve dunning letters.
- Keep the original exports and the import log for audit purposes.
Conclusion and next step
A structured invoice import reduces post-processing, prevents duplicates and makes open items easier to handle. With clear mapping templates, binding validation rules in the dry run and a controlled approval routine you keep control over the dunning process — while Debentra simplifies the routine work.
Learn more and test Debentra: Choose the appropriate edition and see how invoice imports from DATEV/CSV run cleanly on your own infrastructure. Choose edition
Note: Debentra supports the central management of customers, invoices, open items and payments. The release of payment reminders remains with the user; Debentra is not a complete accounting software or legal advice, but a tool for process control in receivables management.
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.