What you will get from this guide
DATEV imports are picky: wrong delimiters, swapped date columns, or missing signs can break the import or create incorrect postings.
Use this checklist to produce a consistent CSV export and validate it with a small test import before you load a full year of statements.
Step-by-step
1. Prepare a clean CSV export
Use a consistent header, keep amounts signed (debits negative), and include at least booking date, amount, and description. Add value date and IBAN when available.
2. Pick the right DATEV import path
Depending on your setup (Rechnungswesen / Unternehmen online), the import UI differs. Always verify the preview and column mapping before confirming.
3. Run a small test import and reconcile totals
Import one month first. Check totals vs. the original statement and verify that negative/positive signs and dates match expectations.
Best practices
- Use the KontoCSV DATEV profile to avoid manual column mapping.
- Keep the original PDF in your archive and document when/how the CSV was generated (audit trail).
- If an import fails, simplify: remove empty columns and re-test with a small date range.
FAQ
Why do DATEV imports fail even when the CSV opens in Excel?
Excel is forgiving. DATEV imports are strict about column mapping, delimiters, and the sign/date interpretation. Use a profile or re-check mapping.
Do I need booking date or value date?
Booking date is the minimum for most workflows. Value date can be helpful for reconciliation and interest calculations, but depends on your accounting process.
German original (more detail)
If you want the full German version with screenshots and extra edge cases, open the original guide here: