Overview
In Germany, GoBD requires proper retention and traceability of accounting-relevant documents, including bank statements.
The key idea: keep the original documents, document every transformation (PDF → CSV), and make sure files cannot be changed without leaving traces.
Quick summary:
- PDF statements are usually the most stable source for consistent imports.
- Structured conversion reduces manual cleanup in recurring monthly workflows.
- CSV, Excel, QuickBooks, and Xero can be handled in one process.
3 methods at a glance
KontoCSV
PDF-first conversion with consistent output fields.
Typically ~30 sec per page
Bank export
Native and free, but often limited by period or format.
Typically ~10 min
Manual entry
Works for tiny datasets, scales poorly for multi-page statements.
Typically ~5 min per page
Method 1: KontoCSV (Recommended)
- Automatic parsing of bank-specific PDF structures
- Stable columns for recurring monthly and quarterly runs
- Target profiles for CSV, Excel, QuickBooks, and Xero
- Lower manual correction effort after import
- Use original bank PDFs whenever possible
- Choose target profile explicitly for mixed currency workflows
- Run a short plausibility check before final booking
Method 2: Native banking export
Typical flow:
- Sign in to online banking and open the account
- Select period and open the export section
- Export and validate columns in your target system
Native exports are useful but not always consistent across periods and statement variants. For PDF-heavy bookkeeping, a standardized PDF-to-CSV workflow is often more reliable.
Method 3: Manual entry
Manual copy/paste can work for one-offs but becomes fragile quickly. Error risk rises with each additional page, especially for date, sign, amount, and balance consistency.
Method comparison
KontoCSV
Fast, consistent, and scalable for recurring imports.
Bank export
Free, but often constrained by period and layout changes.
Manual
Best reserved for exceptions, not recurring bookkeeping.
Step-by-step with KontoCSV
1. Archive the originals (PDFs) in a stable system
Store original statements in a write-protected or versioned archive. Keep them organized by account and period.
2. Document conversions and keep exported CSV/QuickBooks files
If you convert PDFs to CSV, record when and with which profile/tool it happened. Store the export alongside the original PDF.
3. Use consistent exports and reconcile regularly
Prefer repeatable exports (profiles) over manual edits. Reconcile totals against statements so your records stay complete.
Best practices
- Use consistent file naming per client/account and month.
- Validate date, amount, sign, and balance before final posting.
- Keep one output profile per recurring workflow to reduce remapping.
- Avoid manually editing transaction data; re-export instead so changes are traceable.
- Use clear folder naming and keep a simple log for conversion batches.
- Restrict access and keep backups; audit-proof storage is also about availability.
FAQ
Do I need to keep both PDF and CSV?
Keep the original PDF (or original export from the bank) as the source document. CSV is a derived working format that should be traceable back to the original.
Does GoBD require a specific tool?
No. It requires processes: retention, immutability, and traceability. Many tools can work if your workflow enforces these principles.
Conclusion
For PDF-based statement workflows, a standardized conversion process is usually the most reliable option for clean, repeatable imports.
It improves consistency across recurring monthly runs and reduces manual follow-up in accounting tools.
Try KontoCSVGerman original (more detail)
For the full German version with deeper context and local wording, open the original article: