When invoices get lost in the inbox
An invoice is overdue, nobody followed up, reminders are sent too late or not at all — replies get lost in a general email inbox. Such everyday situations show how unreliable Excel spreadsheets are as a central tool for open items: scattered data, duplicate entries and hardly traceable changes. A structured migration to an on-premise solution like Debentra creates clarity, automates routine tasks and preserves data sovereignty — without surrendering control.
Why a planned migration is crucial
The real work starts before the import: only clean, consistent data allow reliable matching, automated payment reminders and smooth tracking. This guide describes the practical steps small accounting teams should take — from data cleansing to a rollback plan.
Benefit in focus
Let’s focus on two concrete benefits: 1) reduced manual matching work through clean data and 2) secure, controlled commissioning in an on-prem Debentra instance. Automation is enabled only where the team grants approval.
1. Preparation phase: Inventory and export
- Export all relevant tables from Excel/Sheets as CSV (customers, invoices, payments, partial payments/installments, attachments/notes).
- Create a field overview: which column corresponds to which information (e.g. invoice number, due date, outstanding amount)?
- Involve responsible persons (accounting, IT, admin): define roles and decisions for the cutover.
2. Step: Data cleansing (must-do)
Clean data are the foundation. Work systematically:
- Unify formatting: standardize date formats, currencies and thousand separators; amounts as numeric fields.
- Complete missing master data: check customer IDs, correct legal form, email addresses and billing addresses.
- Review historical postings: mark reconciled payments, assign clear statuses to open items (open, partially paid, canceled).
- Attachments and evidence: collect links to PDF invoices or organize them in a folder — Debentra can reference documents if files are named consistently.
Quick checks: reconcile totals of open items with balance lists; manually verify random samples of 20–50 entries.
3. Step: Duplicate detection and consolidation
Duplicates are a major cause of inconsistencies. Approach:
- Exact matches: Invoice number + customer + amount identify and be merged.
- Fuzzy check: For name variants (e.g. typos) match names, addresses and tax numbers; set a flag for manual decision.
- Rules for merging: Prioritize more complete records; retain historical payment receipts and consolidate partial payments.
Document every merged case: who made the decision and according to which criterion. This traceability is important for audits and subsequent inquiries.
4. Step: Field mapping for Debentra
Create a mapping table from your source fields to Debentra fields. Typical fields:
- Customer ID → Debentra: Kunde.ID
- Name, address, e‑mail → Debentra: Kunde.Stammdaten
- Invoice number, invoice date, due date → Debentra: Rechnung
- Amount, open balance, currency → Debentra: Offener Posten
- Payments, date, amount → Debentra: Zahlungseinträge / Teilzahlungen
- Installment plans → Debentra: Ratenplan (if available) or create as a note
- Notes / history → Debentra: Documentation / notes
Consider optional fields (e.g. internal GL accounts, dunning levels). Define default values when source fields are empty.
5. Step: Test import into an on‑prem Debentra instance
Use a test instance that is isolated from your production environment:
- First import a small sample (e.g. 50–200 records) and review the presentation in Debentra.
- Check: customer assignments, open balance per customer, payment history and attachment links.
- Simulate workflows: create reminders, run the approval process for dunning (Important: reminders remain under your control).
- Perform a reconciliation: totals of open items before and after import must match.
Fix mapping errors iteratively and document changes in your mapping table.
6. Validation, acceptance criteria and go/no‑go
- Formal acceptance: no differences in totals, correct customer assignment, complete payment history.
- User tests: tasks such as matching, creating a reminder and documenting must be executable without errors.
- Approval process: rules for reminder creation defined and responsible approvers named.
7. Rollback checks and contingency plan
Prepare the rollback before you go into production:
- Complete backup: database dump, file system and configuration files. For VM operation: snapshot before cutover.
- Rollback script: documented steps to restore the previous database and files.
- Test the restore in an isolated environment so the team is confident that a rollback works.
- Communication plan: who is informed internally if a rollback becomes necessary?
8. Cutover and follow‑up
Practical tips for the transition:
- Schedule the cutover outside critical billing cycles.
- After a successful import, initially disable automatic reminders; work with manual approval for the first weeks.
- Perform daily checks for the first 14 days (spot checks, error messages, user feedback).
- Train users in the approval and documentation routine – a short checklist instead of long manuals.
Typical mistakes and how to avoid them
- Incomplete backups: verify the backup before importing.
- Too large first import: always start with a sample.
- Duplicates merged without documentation: log every merge.
- Activating automatic reminders immediately: first manual approval, then gradual automation.
Conclusion
A clean, step‑by‑step migration from Excel to Debentra reduces manual effort and creates transparency for open items – without handing control over to an external system. The key is careful preparation: data cleansing, duplicate detection, clear field mapping, test imports and a tested rollback plan. This keeps your team operational and retains data sovereignty on your own infrastructure.
Act now: Choose the appropriate Debentra edition (BASIS, PRO, PREMIUM) and start with a controlled test import. 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.