What connects to Stripe

Stripe collects the money for subscriptions, online shops and platforms, and settles it to your bank in payouts. It is not an accounting system, and its data does not look like one. A single payout is a net figure across many charges, minus fees, refunds and dispute deductions, settled days later.

Stripe therefore connects to wherever the books are kept. For German companies that is often DATEV, through a Buchungsstapel the tax advisor imports, as in Stripe to DATEV, or an accounting tool for smaller businesses such as lexoffice or sevDesk. International setups post into Xero, QuickBooks or an ERP such as NetSuite. In every case the job is the same: gross sale, fee and payout as separate entries that reconcile.

Where Stripe integrations break

The payout is not the revenue. Book the payout as income and the fees disappear, the tax base is overstated, and nothing reconciles. Each charge, fee and refund is booked on its own, with the payout clearing against the bank.
Fees hide in balance transactions. Stripe deducts its fee per charge, but you only see the total in the payout. Each fee has to be posted against its charge so the deposit matches to the cent.
Currency means three numbers. A charge can be presented in one currency and settled in another. Presentment amount, settlement amount and conversion spread each need a home, including realised FX differences.
Tax treatment is your job. Without Stripe Tax, Stripe does not decide VAT treatment. A domestic 19% sale, a 7% item, an EU B2C sale under OSS and a B2B reverse charge are different tax keys or codes in the target system.
Webhooks arrive more than once. Stripe delivers events at least once. Every booking is keyed to a stable Stripe ID so a retry or a re-run never posts the same charge twice.