DATEV + KudTax
Export booking-ready e-commerce data directly into DATEV – seamlessly transfer journal entries, tax keys, contra accounts and digital document attachments.
In this connection DATEV is not the data source but the destination: KudTax turns your marketplace, payment and shop data into a posting batch your tax firm can import without rework. What matters is less the file format than what is in it — accounts, tax keys, document fields and document links that do not come back as an import error log.
How DATEV works with KudTax
01
Connect sales & payment channels
Connect your marketplaces, shops and payment providers (Amazon, Shopify, Stripe, PayPal) to KudTax.
02
AI reconciliation & tax mapping
KudTax processes transactions into GoBD-compliant entries using your client's custom chart of accounts (SKR03 / SKR04).
03
Generate DATEV-compliant export
Creates structured EXTF / CSV posting files complete with document fields, tax keys and document image links.
04
Direct import into DATEV
Import the error-free posting batch into DATEV or transfer it directly to your tax consultant.
What KudTax reads from DATEV
- Where the export lives
- Import target in DATEV Unternehmen online or DATEV Rechnungswesen → import documents / posting batch
- What the portal calls the file
- EXTF posting batch (DATEV format) including document images
- Formats
- CSV (EXTF)ZIP
Line-item types recognised
- Journal entries with debit/credit accounts
- Tax key per line
- Document fields 1 and 2
- Document date and posting text
- Linked document images
- Contra accounts for fees and refunds
What to watch for with DATEV
One wrong tax key rejects the whole batch
DATEV validates line by line on import. An implausible combination of account, tax key and amount gets the batch rejected or partly discarded. The error surfaces at the firm rather than with you, and the time it costs there is billable.
Without a document link the evidence chain breaks
A journal entry with no linked document does not meet the GoBD requirement for traceability. Marketplace settlements are the document behind the payout; they belong in the export, not separately in a folder.
Locked periods do not change any more
Once a month is locked in DATEV a corrected batch can no longer be imported; it takes correcting entries instead. So the period cut has to be right before the export, not after it.
Why connect DATEV with KudTax
Zero manual data entry
Eliminates spreadsheet copying and manual posting errors for tax firms and accounting teams.
Mapped chart of accounts
Fully customizable G/L accounts, contra accounts and tax keys matching SKR03 or SKR04.
Audit-proof Belegbild links
Embeds digital document links directly in journal entries for 100% GoBD compliance.
Error-free batch validation
Validates every line before export so batches import into DATEV without rejection logs.
DATEV integration – FAQ
An EXTF posting batch of the kind DATEV Unternehmen online and DATEV Rechnungswesen read, including document fields and linked document images.
Yes. Accounts and tax keys are mapped before the export so the batch matches the client's chart of accounts rather than a default.
The usual causes — missing contra accounts, implausible tax keys, documents without a date — are checked before the export, so the error does not first appear at the firm.
KudTax processes your e-commerce data and exports DATEV-compliant EXTF posting batches with digital document links directly for import into DATEV.
KudTax supports SKR03, SKR04 and custom client account charts mapped before export.
Automate your DATEV accounting today
Join the online sellers who let KudTax handle the numbers. Create a free account and connect DATEV in minutes.
