Problem and solution
Stripe reports are useful, but accounting teams still need a stable structure that keeps payout context and fee breakdown intact.
KontoCSV is positioned as the practical normalization layer between raw Stripe files and recurring German bookkeeping imports.
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
- Payout and reconciliation data are normalized into one recurring format.
- Fees, refunds, and disputes remain separated for posting clarity.
- CSV and PDF source files can be processed together.
- The output is aligned with German accounting handover workflows.
Why native exports are often not enough
Native exports are valuable, but often not directly identical to your import template.
Accounting reality
KontoCSV does not claim official DATEV integration. It is a third-party preparation layer for practical imports.
Common payout data pain points
Step-by-step workflow
Step 1: Collect monthly source files
Gather payout/reconciliation exports and PDF fallback records.
Step 2: Upload into KontoCSV
Process CSV/PDF and choose one consistent export profile.
Step 3: Validate transaction classes
Keep charges, fees, refunds, and disputes separately visible.
Step 4: Retain payout references
Preserve payout IDs and dates for bank reconciliation.
Step 5: Export normalized structure
Create one import-ready file for DATEV-oriented workflows.
Step 6: Reuse the monthly setup
Keep one mapping and checklist for recurring periods.
Who this is a fit for
Best fit for
- German bookkeeping teams using Stripe payouts
- Tax advisors handling recurring payout reconciliation
- Businesses with mixed CSV and PDF source quality
- Teams that need fee/refund transparency before import
- Organizations preferring credit-based usage over forced subscriptions
What gets recognized / prepared
Prepared output
- Payout references and net context
- Fee and refund split per period
- Normalized date and amount formatting
- Clean booking text fields
- 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 Stripe payout cleanup workflow
No forced subscription: use credits when needed and keep costs transparent.
FAQ
Do I need a native DATEV connector for Stripe?
Not always. For mixed or historical data, a normalization workflow is often enough and easier to control.
Which Stripe data matters most for bookkeeping?
Payout context plus fee/refund breakdown, not only the net amount on the bank statement.
Can this handle backlog periods from PDF files?
Yes. PDF periods can be normalized into the same recurring structure.
How does this reduce tax-office back-and-forth?
By keeping references, signs, and fee logic consistent in every monthly file.
Does this support multi-currency teams?
Yes, as long as settlement context stays explicit in your recurring workflow.
Helpful internal links
Workflow sources
Status as of Friday, March 6, 2026. These sources reflect the current workflow landscape.