Shopify sevDesk integration

What a Shopify to sevDesk integration actually does

Shopify holds the commercial truth of every sale: the line items, the tax collected per rate, the discount, the shipping, the refund three days later, and the Shopify Payments payout that lands next week net of fees. sevDesk is where that has to become accounting: a contact (Debitor), an invoice or booking voucher with the right tax type, and a bank transaction that closes the open item once the money actually arrives.

The work lives in the gap between those two systems. A Shopify to sevDesk integration closes it automatically. It reads each relevant order, refund, and payout from Shopify, applies your bookkeeping rules, and writes clean records into sevDesk that your bookkeeper - and by extension your tax advisor pulling the DATEV export out of sevDesk - can trust without re-checking figures by hand.

What data moves

Shopify object / event	Becomes in sevDesk	Notes
Paid order	Invoice (Rechnung) or booking voucher (Beleg)	Model chosen per your bookkeeping; consistent across all orders
Order customer	Contact (Debitor)	Matched on email / customer number, deduplicated, never created twice
Line items	Document positions with per-item tax rate	Article mapping optional; revenue split by rate
Tax lines	sevDesk tax type + position rate	Domestic 19% / 7%, EU OSS, reverse-charge, third-country export, Kleinunternehmer
Shipping & discounts	Separate positions	Shipping is itself taxable; discounts reduce the correct base
Refund / partial refund	Credit note or reversing voucher	Same contact, accounts, and tax type as the original, dated to the refund
Provider payout	Clearing-account (CheckAccount) transaction	Shopify Payments / PayPal / Klarna each on their own clearing account
Provider fees	Expense voucher	Netted payout matched to gross sales plus fees
Payment match	Booking against the open invoice	Sets the invoice status to paid once the payout reconciles

The tax types, clearing accounts, and the invoice-versus-voucher decision are agreed once and encoded in the pipeline. After that, nobody maps them again by hand.

The details that break naive imports

A CSV import or a generic connector app gets you most of the way and leaves the expensive part on your bookkeeper’s desk:

• Contact deduplication. Shopify guest checkouts have no stable customer identity. Without a defined match key, every order spawns a fresh Debitor and sevDesk fills with duplicate contacts. The pipeline resolves each order to exactly one contact.
• Tax type, not just tax rate. sevDesk distinguishes a domestic sale, an EU distance sale under OSS, an EU reverse-charge B2B sale, and a third-country export at the document level, not only per position. The destination country and the customer’s status decide it - and a wrong tax type quietly corrupts the VAT return.
• The payout is not the revenue. Shopify Payments settles net of fees, days later, in a batch spanning many orders. Booking the payout as revenue reconciles to nothing. The sale and the settlement have to be separate records joined through a sevDesk clearing account, with fees booked as their own expense.
• Payment matching. An invoice in sevDesk stays open until a transaction is booked against it. The integration has to link each payout back to the right orders so invoices actually close as paid, rather than showing a growing pile of open items no one collected.
• Refunds and chargebacks. A partial refund has to reverse the exact contact, accounts, and tax type of the original order, dated to the refund, not the sale.
• Idempotency. Re-run a naive import and you book the same day twice. The pipeline knows which Shopify events it has already posted and never creates a duplicate record.

How we build and run it

We treat this as a pipeline, not a nightly script. Shopify order, refund, and payout events are pulled on a schedule or by webhook, validated, transformed into your agreed sevDesk model, and written through the sevDesk API - contacts matched, invoices or vouchers created with the right tax type, payouts posted to the clearing account and matched to their open items.

The pipeline is idempotent: every Shopify event carries a stable identifier, so a retry or a re-run never produces a duplicate contact, invoice, or booking. It runs on cloud-native, fully EU-hosted AWS infrastructure, so order and customer data never leaves the EU - which keeps your DPA / AVV and your GDPR obligations clean.

Then we keep it running. Monitoring, alerting, incident response, and - critically - watching for Shopify and sevDesk API changes are our responsibility under contract, with a named owner and an SLA. Shopify deprecates Admin API versions on a fixed schedule and sevDesk evolves its endpoints; when that happens it is our problem to fix, not a surprise your finance team discovers at month-end.

When this integration is worth building

If you process a handful of orders a month at a single VAT rate, entering them in sevDesk by hand is genuinely fine and we will tell you so. The integration earns its place when order volume climbs, when you sell across EU borders under OSS, when refunds and multiple payment providers turn reconciliation into a monthly chore, or when duplicate contacts and unmatched payouts mean someone spends the first week of every month cleaning up sevDesk instead of closing the books.