Overview
Scanned statements and photos are the hardest case: there is no selectable text, tables are skewed, and numbers can be misread.
Modern AI/OCR can extract structured transactions reliably, but results depend on scan quality. This guide shows a practical workflow and best practices.
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. Scan or photograph with enough quality
Aim for 300 DPI scans or a sharp phone photo with good light. Avoid shadows and make sure the page is flat.
2. Upload and let OCR extract transactions
Upload the PDF or image to KontoCSV. AI/OCR detects the table rows and pulls dates, amounts, and descriptions.
3. Verify and export CSV/Excel
Spot-check a few rows and reconcile totals. Then download CSV/Excel (or QuickBooks/Xero profiles for accounting imports).
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.
- Straighten pages: skewed scans reduce OCR accuracy the most.
- Increase contrast: clearer text and lines lead to better table detection.
- If one page is problematic, re-scan just that page instead of the full statement.
FAQ
Can OCR handle old and low-quality statements?
Often yes, but quality matters. Clear scans with readable text work best. Very blurry or heavily compressed images can cause missing digits or wrong separators.
Why does generic OCR often fail on statements?
Statements are tables with repeating columns and multi-line descriptions. Generic OCR might read text, but it does not reliably reconstruct the row/column structure.
What is a good validation step?
Compare statement totals and balances with the exported CSV sums. Also check a few random rows for date and sign correctness.
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: