eBay DATEV integration

What an eBay to DATEV integration actually does

eBay knows everything about a sale - the line items, the tax it collected, the shipping, the return two weeks later, the final value fee it deducted, the Managed Payments payout that lands in your bank next week net of everything. DATEV, and the tax advisor working inside it, needs all of that expressed as bookings: the right account, the right tax key, the right posting date, split correctly between the revenue and the money that actually arrives.

The gap between those two worlds is where the work lives. An eBay to DATEV integration closes it automatically: it reads each relevant record from eBay’s Finances and Fulfillment data, applies your accounting logic, and hands DATEV a clean booking batch your Kanzlei can import without touching a spreadsheet.

What data moves

eBay object / event	Becomes in DATEV	Notes
Paid order (order + line items)	Revenue booking, split by VAT rate	Coded to the correct SKR03 / SKR04 revenue account per tax treatment
Collected-tax field on a transaction	Tax key, or a facilitator-neutral coding	Where eBay remitted the VAT as deemed supplier, your own VAT is not booked again
Return / cancellation / partial refund	Reversing booking	Same accounts and tax keys as the original, dated to the refund
Final value & regulatory operating fees	Expense booking	Percentage fees, often themselves subject to VAT on the fee
International & cross-border fees	Separate expense line	Triggered by buyer or item location, not every order
Promoted Listings ad fees	Marketing expense booking	Standard and Advanced ad fees kept distinct from selling fees
Managed Payments payout	Clearing-account settlement	One payout spans many orders; reconciled per marketplace and currency

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

The details that break naive exports

An eBay report download or a generic connector app gets you 80% of the way and leaves the expensive 20% on your desk:

• eBay collects some of your VAT for you. As marketplace facilitator, eBay charges and remits VAT on certain EU distance sales and imports (including consignments under the IOSS threshold). Book that VAT a second time and your advance return (Umsatzsteuervoranmeldung) is overstated. The integration reads the collected-tax fields per transaction and codes those sales differently from the ones where you still owe the tax.
• The payout is not the revenue. Managed Payments settles net of final value fees, ad fees, and refunds, days later, in a batch spanning many orders. Booking the payout as revenue reconciles to nothing. Sale and settlement must be separate bookings joined by a clearing account.
• Chart of accounts and tax keys. SKR03 and SKR04 number the same concept differently, and a domestic 19% sale, a 7% reduced-rate item, an EU OSS distance sale, and an export are four different tax keys. One wrong key and the OSS return or the VAT return is wrong.
• Marketplaces and currencies. eBay.de settles in EUR, but eBay.co.uk and eBay.com sales settle in GBP or USD. Each marketplace needs its own clearing account and a consistent exchange-rate treatment, not a mixed pot.
• ID matching and dedup. eBay order IDs, line-item transaction IDs, and payout IDs all have to line up so a refund reverses the exact original and a re-run never books the same period twice. A naive export has no memory; a pipeline does.

How we build and run it

We treat this as a pipeline, not a batch job. eBay order, return, fee, and payout records are pulled from the Finances and Fulfillment APIs on a schedule, validated, transformed into your agreed DATEV coding, and written out as a DATEV-Format booking batch - or delivered through the DATEV Rechnungsdatenservice into DATEV Unternehmen online where that suits your Kanzlei’s workflow.

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

And then we keep it running. Monitoring, alerting, incident response, and - critically - watching for eBay and DATEV API changes are our responsibility under contract. eBay deprecates and versions its APIs on its own schedule; that is a change we absorb, not a break your month-end close discovers. You get a named owner and an SLA rather than a script somebody has to remember to run.

When this integration is worth building

If you process a handful of eBay sales a month at a single VAT rate on one marketplace, a manual export is genuinely fine and we will tell you so. The integration earns its place when volume climbs, when you sell across eBay.de, eBay.co.uk, and eBay.com in different currencies, when returns and Promoted Listings fees make reconciliation a monthly chore, or when eBay’s own VAT collection means every export needs hand-correcting before your tax advisor will import it. At that point a managed pipeline is cheaper than the clean-up it replaces.