XRechnung · ZUGFeRD · SEPA · DATEV
SaaS billing with e-invoicing, ready for 2027.
From 2027, German companies above €800,000 revenue must issue B2B invoices as e-invoices, and from 2028 everyone must. Kontier bills subscriptions and usage, issues XRechnung and ZUGFeRD, collects by SEPA and hands off to DATEV. Your payment provider stays.
14 days free · from €199/month · card required to start
German e-invoicing mandate
Three deadlines. The next one is close.
Since 2025, every company in Germany must be able to receive e-invoices. From 2027, companies above €800,000 prior-year revenue must also issue them, and from 2028 everyone must. The dates are in the law (Growth Opportunities Act, § 14 UStG), not on a product roadmap.
Timeline of the German e-invoicing mandate. Today: 17 Nov 2026. 1 Jan 2025, Receiving (Every company): In force. 1 Jan 2027, Issuing (Above €800,000 prior-year revenue): Next deadline, in 45 days. 1 Jan 2028, Everyone (Every company): After that.
In Kontier today
- XRechnung 3.0UBL and CII Live
- ZUGFeRD 2.3PDF/A-3 with XML Live
- DATEV exportposting batch CSV Live
- Peppol deliveryvia Storecove Live
- DATEV Unternehmen onlineinterface Approval pending
Issue your first XRechnung within the 14-day trial, on your own plans.
Check the deadlines at the Federal Ministry of Finance ↗Inside an XRechnung
An invoice that software can read.
Since 2025, German law treats a PDF as an “other invoice”. An e-invoice is structured XML under EN 16931: every value sits in a fixed place with a fixed number, the business term (BT). Kontier fills each one from your billing and checks the file before it goes out.
- PDF by emailOther invoice
- Not allowed in domestic B2B from 2027 above €800,000 revenue, and for everyone from 2028.
- XRechnungE-invoice
- Structured under EN 16931, so your customer's accounting reads it without retyping.
-
BT-10
Buyer reference
For public bodies, the Leitweg-ID. If it is missing, validation reports BR-DE-15 and the invoice stays in quarantine.
-
BT-81
Payment means 59
Code 59 means SEPA direct debit. The mandate and creditor ID sit right next to it.
-
BT-129 · BT-146
Quantity times price
8,402 calls above the included volume at €0.004 each. The line comes to €33.61 net.
-
BT-109 · BT-112
Totals that add up
€33.61 net plus €6.39 VAT is €40.00. The validation rules recompute every total.
SEPA and DATEV
Returned on Friday. Paid on Wednesday.
Kontier collects by SEPA direct debit through GoCardless, Mollie or your own bank (pain.008). When a debit comes back, Kontier reads the reason from the camt.054 statement, schedules the next collection and moves the case into dunning. At month end the invoice sits in the DATEV posting batch for your tax advisor.
- 01 Oct Issued Invoice for €40.00, sent as XRechnung
- 06 Oct Collecting Debit submitted · mandate KTR-00217 · CORE
- 09 Oct Returned Return AM04 · insufficient funds · from camt.054
- 09 Oct Scheduled Next collection on 12 Oct, a bank business day
- 12 Oct Collecting Debit submitted again
- 14 Oct Paid Credit in camt.054 · invoice settled
| Umsatz | S/H | Konto | Gegenkonto | BU | Belegdatum | Belegfeld 1 | Buchungstext |
|---|---|---|---|---|---|---|---|
| 40,00 | S | 10001 | 8400 | empty | 0110 | KT-2026-0412 | api_calls 10/2026 |
40,00;"S";"EUR";;;;10001;8400;"";0110;"KT-2026-0412";"";;"api_calls 10/2026"
10001 is the customer account, 8400 the 19% revenue account in SKR03. As an automatic account, 8400 splits out the VAT itself, so the tax key (BU) stays empty. SKR04 and the tax keys for § 13b, OSS and small businesses come from the same export. Column names stay in German, as DATEV writes them.
Keep your payment provider
Keep Stripe. Add the e-invoice.
Kontier is the billing layer above your payments, not a new PSP contract. Every Stripe invoice becomes an XRechnung: cents become decimals, Stripe fields become business terms. The mapping is open and readable on GitHub.
Live today StripeGoCardlessMollieSEPA via your own bank
BT-10BT-10 (Leitweg-ID / buyer reference) does not come from Stripe. It comes from the buyer's master data.
For developers
One event in. One XRechnung out.
Your product reports what happened. Kontier runs the meter, the tiered price, the VAT and the e-invoice, without another line of billing code in your repository.
$ curl -X POST https://api.kontier.eu/v1/usage-events \ -H "Authorization: Bearer sk_live_…" \ -d { "customer_id": "cust_8f2k", "metric_key": "api_calls", "quantity": 18402 }→ 202 · usage.reported
Add subscription_id, product_id and an idempotency_key, so a webhook retry never counts twice.
In the plans
What German finance teams ask for, in the Starter plan.
Every row below is in the plan named next to it, from €199 a month net. Above the included volume, a revenue share applies to all revenue you bill through Kontier: subscriptions, usage and one-off charges.
Compare plans and revenue share →-
E-invoicing
XRechnung 3.0 and ZUGFeRD 2.3 from the same invoice, validated against EN 16931 and the KoSIT rules before they go out.
XRechnung · ZUGFeRD 2.3 · Factur-X
Included from: Starter
-
VAT
The tax per invoice line: 19% domestic, reverse charge with a VIES-checked VAT ID, OSS for consumers in other EU countries.
§ 13b UStG · OSS · VIES
Included from: Starter
-
SEPA direct debit
Mandates, pre-notifications and collection, returns with their reason, retries and dunning.
CORE + B2B · pain.008 · camt.054
Included from: Starter
-
DATEV export
A monthly posting batch with the correct tax keys, ready for your tax advisor.
SKR03 · SKR04 · CSV
Included from: Starter
-
Data location
Platform data is processed in the EU. Payment data handled by Stripe can be transferred to the US, as the subprocessor register states.
EU platform data
Included from: Starter
-
GoBD audit trail
Every invoice and every price change versioned and archived, so an auditor can trace each figure back.
Versioning · archive
Included from: Scale
Keep reading
More on e-invoicing
- E-invoicing mandate 2027 (DE) Who must issue by when, with sources
- E-invoicing API Generate XRechnung and ZUGFeRD, read the findings
- ZUGFeRD and XRechnung (DE) Which format your customer needs
- DATEV export (DE) Posting batch for your tax advisor
- Stripe to XRechnung (DE) Free integration pack with the field map
Guides
Articles on this topic
- XRechnung for SaaS invoices: the fields your billing data must supplySeats, prorated add-on seats and API usage as an XRechnung: the fields your billing data model has to supply, and where the Leitweg-ID comes from.
- Validating XRechnung against EN 16931: schema, Schematron, rejectsThree validation layers, one validator, five recurring rule failures: how SaaS teams check XRechnung before sending instead of after the customer complains.
- Peppol in your billing system: access points, participant IDs, statusPeppol is a delivery network, not a format. When SaaS vendors need it, how access points and participant IDs work, and what your billing system has to store.
- E-invoicing software for SaaS: German deadlines and a buyer checklistReceiving since 2025, issuing from 2027 or 2028: which capabilities e-invoicing software for SaaS needs, when, and what to test in the vendor demo.
- GoBD for SaaS billing: immutability, audit trail and eight yearsGermany's GoBD principles applied to a SaaS billing stack: locking, versioned master data, deletion dates from year end, and process documentation that keeps up with releases.
Your first XRechnung, before the deadline.
Set up your plan, issue an invoice and download the XRechnung. Your payment provider stays connected.
from €199/monthStarter, net plus VAT
- From €199/month net
- 14 days free
- Card required to start
- No setup fee
- Cancel monthly