Problem and solution
Multi-provider setups are common in German e-commerce and SaaS. The challenge is not download access, but import consistency across sources.
KontoCSV acts as a neutral conversion layer that keeps provider context while normalizing recurring import structure.
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
- Different providers expose fees and payouts differently.
- One normalized model reduces recurring mapping errors.
- CSV and PDF records can be processed together.
- The output is tailored to German bookkeeping handover workflows.
Why native exports are often not enough
Each provider has native exports, but cross-provider consolidation is where most accounting friction starts.
Accounting reality
A central normalization layer improves reliability and auditability for recurring close cycles.
Common payout data pain points
Step-by-step workflow
Step 1: Define provider scope
List payout sources and period boundaries for the monthly close.
Step 2: Centralize raw files
Collect CSV exports and PDF records in one processing run.
Step 3: Normalize field logic
Align payout references, fees, refunds, dates, and signs.
Step 4: Keep source traceability
Preserve provider identity per row for support and audit questions.
Step 5: Export recurring import file
Create one consolidated structure for DATEV-oriented imports.
Step 6: Document monthly routine
Store mapping and checks so teams can repeat the process safely.
Who this is a fit for
Best fit for
- Businesses running multiple payment providers in parallel
- Accounting teams with complex payout close cycles
- Tax offices supporting e-commerce and SaaS clients
- Organizations with mixed CSV and PDF source quality
- Teams needing one stable monthly handover format
What gets recognized / prepared
Prepared output
- Provider source context per row
- Fee and refund structure by provider
- Bundled payout references
- Normalized date and amount formats
- Consistent import columns
- Structured handover package 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 multi-provider payout normalization
No forced subscription: use credits when needed and keep costs transparent.
FAQ
Can we merge Stripe, PayPal, and Shopify in one run?
Yes, if source traceability is preserved and the target schema is consistent.
How should fees be handled across providers?
Keep fee lines explicit per provider/type instead of collapsing everything into net totals.
What changed with DATEV payment-provider services in 2026?
DATEV launched dedicated data service paths in January 2026, but many teams still need cleanup for mixed and historical data.
Is one consolidated handover file useful for tax offices?
Usually yes, as long as provider references remain auditable.
When is native export alone enough?
Mostly in simple single-provider setups with stable source quality.
Helpful internal links
Workflow sources
Status as of Friday, March 6, 2026. These sources reflect the current workflow landscape.