Stripe sevDesk integration

What a Stripe to sevDesk integration actually does

Stripe knows everything about the money: the charge, the card fee it kept, the refund three days later, the subscription invoice that renewed overnight, the payout that lands in your bank next Tuesday as one net batch spanning dozens of transactions. sevDesk needs all of that expressed as vouchers - the right revenue account, the right tax rate, the right booking date, and the fee and the payout kept separate from the sale so your bank reconciliation actually closes.

The gap between those two worlds is where the work lives. A Stripe to sevDesk integration closes it automatically: it reads each relevant event from Stripe, applies your bookkeeping logic, and writes clean vouchers and payments into sevDesk that your bookkeeper - and, downstream, your Steuerberater via sevDesk’s DATEV export - can rely on without touching a spreadsheet.

What data moves

Stripe object / event	Becomes in sevDesk	Notes
Successful charge / PaymentIntent	Revenue voucher (Einnahmenbeleg)	Coded to the correct revenue account and tax rate per treatment
Stripe Billing invoice	Voucher or invoice with line items	Subscription line items and tax preserved, not collapsed to a lump sum
Customer	Contact (Kontakt / Debitor)	Matched by email or VAT ID to avoid duplicate contacts
Refund / partial refund	Reversing voucher	Same revenue account and tax rate as the original, dated to the refund
Stripe fee (balance transaction)	Expense voucher (Ausgabenbeleg)	Booked to a payment-fee account, not netted into revenue
Payout	Clearing-account settlement (Geldtransit)	Net batch reconciled against gross charges minus fees and refunds
Dispute / chargeback	Reversal plus fee booking	Revenue reversed and the dispute fee booked separately

The exact accounts, tax rates, and clearing account are agreed once with you and your tax advisor and encoded in the pipeline. After that, nobody maps them again by hand.

The details that break naive imports

A CSV import or the thin built-in connector gets you most of the way and leaves the expensive part on your desk:

• The payout is not the revenue. Stripe settles net of fees, days later, in a batch that spans many charges, refunds, and adjustments. Book the payout as revenue and nothing reconciles. The charge, the fee, and the settlement must be separate bookings joined by a clearing account, tied together through Stripe’s balance-transaction record.
• Fees have to come out cleanly. Every Stripe charge carries a processing fee that Stripe deducts before payout. If it disappears into a net figure, your revenue is understated and your expenses are invisible. It belongs on its own fee account.
• Currency. A USD charge settles into EUR at Stripe’s rate with a conversion fee. sevDesk needs the EUR figure, but you still need the original currency, rate, and spread for the audit trail. Rounding this wrong is where cent-level drift creeps in.
• Tax treatment. A domestic 19% sale, a 7% reduced item, an EU B2C distance sale, a reverse-charge B2B invoice, and a Kleinunternehmer sale with no VAT are all different. The customer’s country and tax status drive the sevDesk tax rate, not a single default.
• Refunds, disputes, and idempotency. A partial refund must reverse the exact account and tax rate of the original, on its own date. A chargeback adds a fee and a reversal. And re-running a naive import books the same week twice - the pipeline has to know each Stripe object ID it has already sent and never post it again.

How we build and run it

We treat this as a pipeline, not a batch job. Stripe charges, invoices, refunds, and payouts are pulled by webhook and reconciled on a schedule, validated against Stripe’s balance-transaction record, transformed into your agreed sevDesk coding, and written as vouchers, contacts, and payments through the sevDesk API.

The pipeline is idempotent: every Stripe object carries a stable ID (ch_, in_, po_, txn_), so a retry or a re-run never produces a duplicate voucher. It runs on cloud-native, fully EU-hosted infrastructure, so payment and customer data never leaves the EU - which keeps your DPA / AVV and your GDPR obligations clean.

And then we keep it running. Monitoring, alerting, incident response, and - critically - watching for Stripe and sevDesk API changes are our responsibility under contract. You get a named owner and an SLA. The month-end close stops depending on someone remembering to run an export.

When this integration is worth building

If you process a handful of EUR charges a month at a single tax rate, sevDesk’s built-in import is genuinely fine and we will tell you so. The integration earns its place when volume climbs, when Stripe Billing subscriptions and multiple currencies enter the picture, when fees and refunds make the payout reconciliation a monthly chore, or when your bookkeeper is spending hours each month correcting vouchers that a pipeline should have delivered right the first time.