Problem and solution
Most teams can export files. The hard part is turning payout raw data into a stable recurring import flow.
KontoCSV supports that preparation step: normalize first, import second.
Drop one PDF or multiple PDFs here
Works with digital PDFs, scans, and photos from banks worldwide - retail, business, and fintech. Multiple PDFs are automatically processed as one batch and exported as a ZIP with individual CSV files.
How this workflow runs in real teams
- Collect all payout sources for the period.
- Normalize signs, dates, references, and fee handling.
- Keep provider and payout traceability intact.
- Export one recurring structure for accounting handover.
Why native exports are often not enough
Provider exports are source-centric, while accounting imports need one consistent cross-source structure.
Accounting reality
A preparation layer turns raw payout data into a process teams can rely on each month.
Common payout data pain points
Step-by-step workflow
Step 1: Define period and sources
List payout sources and collect all files for the close cycle.
Step 2: Centralize raw data
Combine CSV exports and PDF backups in one run.
Step 3: Normalize structure
Align core fields and payout logic in KontoCSV.
Step 4: Run plausibility checks
Validate signs, fee splits, and net reconciliation.
Step 5: Export import-ready file
Generate one consistent file for DATEV-oriented imports.
Step 6: Keep a monthly checklist
Reuse mapping rules and checks period after period.
Who this is a fit for
Best fit for
- Bookkeeping teams importing payouts monthly
- Tax advisors handling mixed payment-source clients
- Companies with historical PDF and CSV periods
- Teams building predictable close-cycle workflows
- Organizations moving away from ad-hoc spreadsheet fixes
What gets recognized / prepared
Prepared output
- Payout date and reference context
- Fee/refund separation
- Gross/net transparency for reconciliation
- Normalized date and amount formatting
- Consistent import columns
- Structured handover for accounting and tax offices
Privacy, hosting, and reliability
Trust and compliance
- GDPR-compliant processing with EU hosting in Frankfurt.
- Built for German bookkeeping and tax-office collaboration.
- Credit-based pricing instead of forced subscriptions.
- Deletion and privacy controls for sensitive finance files.
Important note
KontoCSV is not an official DATEV product or service. It is a neutral third-party workflow for preparing import data.
Start your payout import preparation workflow
No forced subscription: use credits when needed and keep costs transparent.
FAQ
Which payout files should I collect first?
Start with files that explain net bank payouts: payout exports, fee/refund detail, and PDF fallback periods.
How important is bank reconciliation?
Critical. Net bank movements should be explainable by normalized payout and fee detail.
Can this workflow handle PDF-only historical months?
Yes. PDF periods can be normalized into the same recurring structure.
How do we reduce tax-office clarification loops?
Use stable columns, explicit references, and documented mapping rules each month.
When does central normalization pay off most?
As soon as multiple providers, mixed formats, or recurring cleanup effort are involved.
Helpful internal links
Workflow sources
Status as of Friday, March 6, 2026. These sources reflect the current workflow landscape.