This is a significantly deeper version of our Stripe guide: with practical reports, typical booking rates, sources of errors and links to official sources. You can adopt the structure directly and adapt it to KontoCSV.
TL;DR for the month-end closing
- Best data source: Payout Reconciliation Report (Stripe → Reporting → Reports). Contains
payout_id,balance_transaction_id,reporting_category,big/fee/net. - For tax and EÜR you need: gross sales (per tax rate/country), Stripe fees, refunds/disputes and the payout data. Just the bank statement is not enough.
- PDF-only? KontoCSV converts Stripe payout PDFs to CSV/DATEV/Lexware - Fees/Refunds/Disputes separately.
1. What you really need from Stripe for accounting
For clean accounting, you need gross sales, Stripe fees, refunds/chargebacks and the payouts for reconciliation with the bank account. A mere bank account statement (net payout) is not enough.
2. Which Stripe reports/exports are there?
Time zone, date range, columns freely selectable; CSV with all payouts in the period.
Good for: Comparison with bank account (when did which payout come, in which currency?).
Not enough for: Which payments/fees are included in the payout.
Lists all balance transactions included for each payout, grouped by category.
Typical columns: payout_id, payout_date, balance_transaction_id, reporting_category, type, gross, fee, net.
Best basis for payout-accurate DATEV booking. (Source: Stripe documentation)
CSV with all balance transactions in the period (similar to account statement), in the settlement currency.
Good for: Completeness check per month and validation of automatic interfaces.
Export directly from the Payments view, columns including fees can be selected.
Good for sales analysis and fees per payment.
Less precise than the Reconciliation Report for payout posting.
3. Export strategies at a glance
Monthly payouts export + payout reconciliation (optional balance summary).
Recommended if you work directly in Stripe and have your own DATEV template.
Upload Stripe payout PDFs, convert to CSV/DATEV/Lexware.
Ideal for archived PDFs or when tax advisor supplies PDF runs.
Stripe apps like Fizard, FinHero, Pathway deliver DATEV-EXTF/Booking batch directly.
Good for high volumes and when receipt images/accruals need to be automated.
- Quickly saves hours per month with many transactions.
- Receipt images, booking batches and accruals run automatically.
- SKR accounts preconfigured, fewer questions from the law firm.
- No fixed costs/subscriptions, full control over mapping.
- No permanent API setup, no live data access required.
- Fast for ad hoc or historical PDF stocks.
4. Step-by-Step: Stripe Payouts as CSV (Method 1)
- Log in to Stripe → Balances → Payouts.
- Top right Export click.
- Select time zone (e.g. Europe/Berlin) and date range.
- Columns: Default / All columns / Custom (ID, Amount, Arrival date, Currency, Status).
- Save CSV.
Tip: For DATEV payout_id, arrival_date, amount, currency, status is often sufficient. Details can be found in the Reconciliation Report.
- Stripe dashboard → Reporting → Reports.
- Report type Payout reconciliation select.
- Date range = period of payouts.
- In the section on Download click and save CSV.
This file is your detailed journal per payout: gross sales, Stripe fees (including dispute fees), refunds/chargebacks, net payout.
- Dashboard → Reports → Balance summary.
- Date range = booking month.
- Download CSV and check against payout amounts.
This way you can ensure that no transaction hangs outside of your payout reports (open amounts, failed payouts).
5. Step-by-Step: Stripe-PDFs with KontoCSV (Method 2)
If you only have Stripe as a PDF statement: KontoCSV is built as a PDF-→CSV/DATEV converter (no permanent Stripe connector).
1. Upload PDF
Drag Stripe-Payout-PDF into KontoCSV.
2. Select export profile
Select DATEV (SKR03/04), Lexware, generic CSV/Excel.
3. Check columns
Gross, fee, refund, dispute fee, net/payout amount are separate.
6. CSV structure: what columns do you need?
Booking date (often payout date)
Payout_ID (po_…)
Balance_Transaction_ID
Description / Transaction Type (Charge/Refund/Dispute/Fee/Payout)
Document number / order ID
Currency
Gross, Fee, Refund, Dispute Fee, Net
Delimiter: mostly in Germany ;
Decimal: ,
Date: DD.MM.YYYY
Lead fees and refunds as negative values.
Example-CSV (German format)
Booking date;Payout_ID;Transaction type;Gross;Fee;Refund;DisputeFee;Net;Currency 02/15/2025;po_123;Charge;119.00;-3.57;0.00;0.00;115.43;EUR 02/15/2025;po_123;Refund;-119.00;0.00;-119.00;0.00;-119.00;EUR 02/15/2025;po_123;DisputeFee;0.00;-15.00;0.00;-15.00;-15.00;EUR 02/15/2025;po_123;Payout;0.00;0.00;0.00;0.00;-18.57;EUR
Formula idea (net payout)
Payout_Netto = SUM(Gross) + SUM(Fees) + SUM(Refunds) + SUM(DisputeFees)
Fees/refunds are usually negative.
7. SKR mapping: Post Stripe sales & fees in DATEV
Sales 19%: SKR03: 8400, SKR04: 4400
EU (B2B, RC): SKR03: 8336, SKR04: 4336
Stripe fees: SKR03: 4970 additional costs for monetary transactions, SKR04: 6855
Bench: SKR03: 1200/1210, SKR04: 1800/1810
Stripe clearing: SKR03: 1360, SKR04: 1460
Sales (EÜR, without debtor, SKR03)
1360 money transit / Stripe 119.00 to 8400 proceeds 19% VAT 100.00 to 1776 VAT 19% 19.00
Stripe fee
4970 additional costs for money transactions 3.57 to 1360 money transit / Stripe 3.57
Payout to bank
1200 Bank 115.43 to 1360 Money Transit / Stripe 115.43
For disputes: also book the dispute fee on 4970/6855; Reduce proceeds in the case of refunds (own account if necessary).
8. Special cases: Refunds, disputes, currencies, OSS
Refunds appear as a separate line with a negative amount in the reconciliation report.
Refund can end up in another payout → always match via payout_id / balance_transaction_id.
reporting_category: charge_dispute + separate fee lines.
Amount is deducted, fee as expense (4970/6855). If the case is won: record a chargeback.
Stripe distinguishes between presentment and settlement currency; Reports provide converted amounts.
Keep the booking currency consistent (often EUR); Exchange rate differences optionally to your own account. Separate OSS/tax rates by destination country.
9. Typical mistakes & how to avoid them
- Decimal or field separator incorrect: In Excel import wizard
;and put a comma. - Incorrect date: Use payment date/payout date, not invoice date.
- Fees hidden in sales: Always post fees as a separate column/account.
- Incomplete reports: Payouts alone are not enough; Use Reconciliation + optional Balance Summary.
- GoBD: Archive original PDF, CSV as working file; Log changes in a comprehensible manner.