Skip to content
Rechnungskit
Bookkeeping
Playbook

E-invoices and DATEV: how e-invoices reach your tax advisor

E-invoices reach DATEV in two ways. Incoming invoices from suppliers can come in through the DATEV E-Invoicing Platform (E-Rechnungsplattform) and are filed in DATEV Unternehmen online (Belege online). Outgoing invoices from your shop or payment provider go to your tax advisor as a posting batch in DATEV format (EXTF), ideally with document links so every booking shows its e-invoice. For an e-invoice you must keep at least the XML part, unchanged, for eight years.

Incoming and outgoing are two routes

People searching for "DATEV e-invoice" usually mean one of two questions. How do my suppliers' e-invoices get into DATEV? And how do my own invoices to customers get there? The answers differ because the invoices travel in opposite directions.

Incoming e-invoices are records of expenses and input VAT. They come from outside: you receive them, check them and file them. Outgoing e-invoices are produced by your own system, in online retail usually automatically from order and payment. For those, your tax advisor needs the matching booking as well as the invoice: revenue, VAT, payment, fee and payout.

Two directions · two routes into DATEV
Incoming and outgoing invoices
Incoming invoicefrom a supplier
Record ofexpenses and input VAT
Arrives viaPeppol, TRAFFIQX or email
Route into DATEVE-Invoicing Platform or upload to Belege online
Your jobcheck it, file the original
Outgoing invoicefrom you to customers
Record ofrevenue and VAT
Created fromorder and payment
Route into DATEVposting batch (EXTF) and document package with document links
Your jobdeliver invoice and booking
Rechnungskit only works on the right-hand side. Your suppliers' invoices stay with your incoming route.

Since 1 January 2025, every business in Germany has to be able to receive e-invoices. Transition periods apply to sending (§ 27(38) UStG, German). The page on the e-invoicing mandate explains what applies when.

Incoming e-invoices in DATEV

For receiving, DATEV offers the DATEV E-Invoicing Platform (German). Suppliers send invoices via Peppol, the TRAFFIQX network or email. The e-invoice inbox lists them together and can pass them on to DATEV Unternehmen online automatically. The inbox itself does not archive. For further processing and GoBD-compliant filing, DATEV recommends the Belege online module in DATEV Unternehmen online.

Incoming invoices also work without the platform: you upload e-invoices that arrive by email to Belege online. What matters is that you upload the original file, meaning the XRechnung as XML or the ZUGFeRD invoice as a PDF with the embedded XML. A printout or a PDF generated afterwards without the XML is no longer the e-invoice.

You still have to check incoming invoices yourself. Validation shows format and rule errors, but it does not replace checking that the invoice is complete and correct, for example whether the VAT rate is right (BMF letter of 15 Oct 2025, para. 35a, German).

Outgoing e-invoices from your shop and payment provider

Your own invoices are a different matter. A shop or SaaS business issues hundreds of invoices a month, not one. Uploading each of them to Belege online and having them booked there one by one would mean a lot of manual work. The usual route is a posting batch in DATEV format, often called EXTF after the identifier in its first line (DATEV format, German). Your tax advisor imports it into DATEV and has all revenue bookings for a month in one go.

A batch without documents falls short, though. Every booking needs a document (GoBD para. 61 ff., German), and your tax advisor wants to see it on the booking. That is what the document link (Beleglink) is for. The invoices go to DATEV Unternehmen online as a document package, and each booking line in the batch points to its invoice through a document link. The order is fixed: upload the documents first, then import the batch. Only then does every link find its document image.

Outgoing invoices · one month
From payment to booking in DATEV
Shop and payment
Order and paymentfrom shop system and payment provider
ShopifyWooCommerceStripePayPal
Invoice and archive
  1. Issue the e-invoiceZUGFeRD or XRechnung under EN 16931
  2. ArchiveXML unchanged, eight years
  3. Export the monthposting batch with document links and document package
DATEV
1. Belege onlineupload the document package
2. Posting batchimport EXTF, every booking shows its invoice
The order in DATEV matters: documents first, then the posting batch. Otherwise the document link finds no document image during import.

Two things often get mixed up. First, the payout from your payment provider is not revenue. It is money moving between two of your own accounts. Revenue and VAT arise with the invoice, and the provider's fees are an expense. The Stripe DATEV export guide shows how this works for Stripe, and the WooCommerce DATEV export guide covers WooCommerce. Second, a CSV report from your shop or payment provider is not a posting batch yet. It contains the payments, but accounts, tax keys and the link to the document are missing.

Each line in a posting batch has fixed fields (DATEV format, German). For a revenue booking, the ones that matter most are the amount, the debit/credit flag, account and contra account, document date, document field 1 with the invoice number, the booking text and, in field 20, the document link.

Example with demo data · SKR04
One revenue booking in the posting batch
Invoice SN-2026-1047 of 04.10.2026, €21.00 grosswith document link
Field 1 · Amount (Umsatz)21,00
Field 2 · Debit/creditS
Field 7 · Account1200 debtor
Field 8 · Contra account4400 revenue at 19% VAT
Field 10 · Document date0410 day and month
Field 11 · Document field 1SN-2026-1047
Field 14 · Booking textDE Erika Muster Bestellung ABO-5EMYP3-1
Field 20 · Document linkBEDI "6f1c2a9e-…" points to the document image in Belege online
Excerpt of one line with demo data. A CSV report from your shop or payment provider has no account, no contra account and no document link.

What your tax advisor needs

Before you set anything up, ask your tax advisor how they work. Their answers decide what you deliver:

  • Chart of accounts: SKR03 or SKR04, and which revenue accounts apply to your sales, for example domestic sales, EU consumers under the OSS scheme, and reverse charge.
  • Advisor number and client number: both go in the header of the posting batch and assign it to the right client.
  • Documents: does your tax advisor work with DATEV Unternehmen online and want to see the invoices on the bookings? Then a document package with document links. Otherwise a ZIP of the invoices is often enough, matched to the booking through the invoice number in the document field.
  • Payments: do they want your payment providers' payments, fees and payouts booked as well as revenue? Then you need a second batch.
  • Rhythm: monthly for the advance VAT return or less often, and who locks the month (Festschreibung).

A clean month has one simple property in the end: every revenue booking points to exactly one invoice, and every invoice is booked exactly once. A cancellation invoice gets its own booking, and the original stays as it is.

Archiving: the XML is the original

Invoices have to be kept for eight years, incoming and outgoing (§ 14b(1) UStG, German; for accounting records § 147(1) no. 4 and (3) AO, German). For an e-invoice, at least the structured part must be kept so that it stays intact in its original form (BMF letter of 15 Oct 2025, para. 60, German). That is the XML record. For a ZUGFeRD invoice, this means the original file with the embedded XML, not a printout of it.

The GoBD as amended on 14 Jul 2025 (German) go a step further. For outgoing invoices from an invoicing program you need not keep an image copy, as long as a copy with identical content can be produced at any time (para. 76). For received e-invoices the structured part is enough, as long as the image part holds no additional tax-relevant information such as booking notes (para. 131).

Retention · eight years
What of an e-invoice belongs in the archive
Original file with the XMLXRechnung as XML, ZUGFeRD as a PDF with embedded XML, unchanged
Keep
Printout or newly generated PDF without XMLThat is no longer the e-invoice
Not enough
Image copy of an outgoing invoiceNot needed if your invoicing program can produce a copy with identical content at any time (GoBD para. 76)
Optional
Image part of a received e-invoiceOnly needed if it holds additional tax-relevant information such as booking notes (GoBD para. 131)
Case by case
Period: eight years under § 14b(1) UStG and § 147(3) AO. The obligation is yours, even if a copy sits in DATEV.

The document package in DATEV is a practical copy for bookkeeping. It is not automatically your archive. The retention obligation lies with you as the business owner. Whether you meet it in DATEV, in your invoicing software or in both is best agreed with your tax advisor. The GoBD guide covers what else a compliant archive has to do.

E-invoices and DATEV with Rechnungskit

Rechnungskit covers the outgoing side. Orders and payments from your shop or payment provider automatically become a ZUGFeRD invoice, or an XRechnung for customers with a Leitweg-ID. The XML under EN 16931 is archived in immutable storage with a SHA-256 checksum that is verified on every retrieval.

For DATEV, Rechnungskit produces two posting batches per month in EXTF format, one for revenue and one for payments, for SKR03 or SKR04. If your tax advisor works with DATEV Unternehmen online, each revenue export comes with a DATEV package: the batch with one document link per invoice booking, and a document transfer package with document.xml and the ZUGFeRD invoice as a PDF. Your tax advisor uploads the document package and then imports the batch. The export page in Rechnungskit shows this order too.

Rechnungskit, export #5 revenue July 2026 as a draft with the buttons Download DATEV EXTF, DATEV package (29 documents), Lock and Delete, the note Order in DATEV: documents first, then the booking batch, and the DATEV package protocol with 32 bookings, 32 with document link, 0 without document and 29 documents in the package

If your tax advisor does not use DATEV Unternehmen online, you get the documents as a ZIP without document links, or the batch alone. You pick one of the three options in the DATEV settings.

Rechnungskit, DATEV settings, card Documents for the tax advisor with the question whether the tax advisor uses DATEV Unternehmen online, and three options: option 1 Belegtransfer with document links (selected and current), option 2 Documents as a ZIP, no links, option 3 Booking batch only, each with what it means in DATEV, for the archive and for the effort, and a line on when it fits, below it the note that the invoices stay in the Rechnungskit GoBD archive in any case

You invite your tax advisor under Settings → External access. The advisor access is free for them. There they check accounts, download exports and lock them. If they want, Rechnungskit creates the previous month's batches as drafts on a fixed day each month. Nothing is ever locked automatically.

Rechnungskit tax firm access, overview of the client Nordlicht Kaffee GmbH for 2026-07 with client number 20117, consultant number 31447, SKR04 and the tiles revenue €1,860.76 (32 booking lines), payments €1,296.16 (37 booking lines) and open items €0.00

Two limits, so you can plan: documents reach DATEV by file upload, and there is no direct online transfer to DATEV. And Rechnungskit does not process your suppliers' invoices; your incoming route stays in charge of those. The DATEV export feature page, the DATEV integration and DATEV export for online shops show the export in detail.

FAQ

Yes. The DATEV E-Invoicing Platform (German) receives invoices via Peppol, the TRAFFIQX network or email. It does not archive them. For further processing and GoBD-compliant filing, DATEV points to Belege online in DATEV Unternehmen online.
Read more
Guide Getting documents into DATEV Unternehmen online: upload, Belegtransfer and data services Guide E-invoicing for B2C in Germany: does the mandate apply to online shops? Guide E-invoicing in Germany: the mandate explained for founders Guide Invoicing in a foreign currency in Germany: which exchange rate applies? (ECB, DATEV, OSS) Guide Clearing account (Geldtransit): booking PayPal, Stripe, Klarna, Mollie and Shopify Payments in DATEV Guide GoBD explained: principles, retention and what they mean for your invoices Guide Small-amount invoices in Germany (§ 33 UStDV): when the buyer's address can be left out Guide E-invoicing for small businesses in Germany (Kleinunternehmer): duties, exemptions, thresholds 2026 Guide The German cancellation button (§ 312k BGB): who needs it and how it works Guide The date of supply on German invoices: shipping date or payment date? Guide Leitweg-ID: what it is, how it is structured and how it gets onto the invoice Guide OSS return in Germany: deadlines, filing in the BZSt portal, nil returns and corrections Guide The OSS scheme explained: the €10,000 threshold, registration and an example Guide PayPal in DATEV: setup, bookings and documents for your tax advisor Guide Deferred revenue for SaaS and online courses in Germany: when a pRAP is required Guide Proforma invoices in Germany: what they are for and why they are not invoices Guide Deferred revenue in German accounting (pRAP): definition, bookings and an example Guide Changing the billing address on a German invoice afterward: is it possible? (without a cancellation) Guide Correcting an invoice in Germany: which route for which error? Guide Server-side tracking for Meta: Conversions API with a lean consent bar Guide Shopify and DATEV: interface, export and bookkeeping for Shopify stores in Germany Guide Shopify gift cards in Germany: gift card, discount code and store credit for VAT Guide Shopify Payments and Klarna in Germany: fees, payouts and bookkeeping Guide Shopify invoices in Germany: what Shopify does, what is missing, what applies from 2027 Guide Shopware invoices: what Shopware 6 does on its own and what is missing Guide Stripe DATEV export: getting Stripe payments into DATEV as a booking batch Guide Booking Stripe fees in Germany: clearing account, reverse charge and Stripe Technology Europe Ltd Guide Stripe Invoicing in Germany: creating invoices, pricing and e-invoicing Guide Stripe invoices with payment terms as e-invoices: bank transfer to the Stripe IBAN Guide Stripe invoices in Germany: what Stripe Invoicing and Billing do, what is missing, and what applies from 2027 Guide Shipping costs and VAT in Germany: 7%, 19% or tax-exempt? Guide The German withdrawal button (§ 356a BGB): mandatory since June 19, 2026 Guide WooCommerce DATEV export: options, file format and account mapping Guide WooCommerce invoices in Germany: plugins, mandatory details, e-invoicing Guide XRechnung or ZUGFeRD? The difference and who gets which format Guide XRechnung vs ZUGFeRD: the XRechnung format explained Guide Payment terms on invoices in Germany: rules, due date calculation and wording Guide ZUGFeRD: format, example and profiles of the German e-invoice

Rechnungskit is not a tax advisory or law firm. This article explains general principles and does not replace advice from a tax advisor (Steuerberater, § 5 StBerG) or a lawyer (§ 3 RDG). Rechnungskit is built for businesses based in Germany and prepares documents, tax rates and bookings automatically. How your specific case is treated remains your decision, ideally together with your tax advisor or a lawyer.

Every invoice automatically as a valid e-invoice.

Connect your payment provider and we take care of format, validation and archive. Start for free in test mode.

Try it now
de en