← All integrations
20 integrations

DATEV integrations

In short

A DATEV integration turns data from your shop, payment provider, expense tool or HR system into something your Steuerberater can import: a Buchungsstapel with the right SKR03 or SKR04 accounts and tax keys, or payroll data for LODAS or Lohn und Gehalt. It rarely fails on the file format. It fails on account mapping, tax keys, debtor numbers, and periods the Kanzlei has already locked.

DATEV API changelog → No breaking changes or deprecations in the last 90 days

What connects to DATEV

DATEV is where the Steuerberater works: the Kanzlei imports the bookings, prepares the advance VAT return (Umsatzsteuervoranmeldung) and the annual accounts, and often runs payroll too. Everything upstream has to arrive in a form that office accepts without rework.

That makes DATEV the most common target in a DACH stack. Shops and marketplaces send revenue, refunds, and fees, as in Shopify to DATEV. Payment providers send settlements, as in Stripe to DATEV. For a one-off PayPal or Stripe export, our free converter turns it into a booking batch. Spend and travel tools send card transactions and expense reports with input VAT split out, as in SAP Concur to DATEV. HR systems send master data, wage types, and absences for payroll, as in Personio to DATEV, where LODAS and Lohn und Gehalt expect different import formats.

Where DATEV integrations break

// scoping request

Connecting DATEV to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.

We reply within one working day. No newsletter, no sales sequence.