ERP Compliance in DACH: GoBD, RKSV & GeBüV

Up front: ERP compliance in DACH means your system meets the bookkeeping, record-keeping and documentation obligations in Germany, Austria and Switzerland at the same time – and does so on a country-by-country basis. Germany requires GoBD conformity plus a certified TSE for point-of-sale systems, Austria demands tamper protection under the RKSV and export to BMD or your tax advisor, and Switzerland insists on the GeBüV and the QR-bill. Anyone selling across borders needs an ERP that maps all three sets of rules cleanly. This article shows you what each country specifically requires, where the differences lie and what to watch for when choosing a system. When in doubt, your tax advisor is always the legally binding authority – this piece frames the requirements from a subject-matter perspective.

What ERP compliance in DACH actually covers

In the ERP context, compliance revolves around four core areas: proper bookkeeping, immutability and traceability of the data, retention over statutory periods, and machine-readable evaluability for the tax authorities. All three DACH countries pursue the same goal – tamper-proof, auditable records – but implement it through their own legal frameworks. An ERP therefore has to apply different rules per entity and per country. That is a strong argument for genuine multi-entity capability: a DE entity with a TSE connection, an AT entity with an RKSV signature, a CH entity with a QR-IBAN – all in the same system, but with separate rule sets.

Germany: GoBD, KassenSichV/TSE and e-invoicing

Germany has the densest set of rules of the three countries. There are three topics you need to keep apart.

GoBD and retention obligations

The GoBD (principles for the proper keeping and retention of books in electronic form) require traceability, completeness, immutability and timely recording. In practice that means: bookings must not be overwritten without a trace, every change needs an audit trail, and the entire process must be described in procedural documentation. On the retention obligation, a relief has applied since 2025: accounting vouchers now only have to be kept for 8 instead of 10 years (Fourth Bureaucracy Relief Act), while commercial books, inventories and annual financial statements must still be retained for 10 years. A GoBD-compliant ERP archives vouchers in an audit-proof way and exports them in GDPdU format for a tax audit.

KassenSichV and TSE

Anyone taking cash payments falls under §146a AO and the Cash Register Anti-Tampering Ordinance. Every electronic recording system needs a certified technical security device – the KassenSichV/TSE – which signs and chains every transaction. On top of that come the receipt-issuance obligation and the obligation to report registers to the tax office, which has run mandatorily via ELSTER since 2025. If your retail operation has POS or register functions, the ERP has to connect to a BSI-certified TSE (hardware or cloud).

E-invoicing: the 2025 / 2027 / 2028 staggering

For B2B e-invoicing, the exact deadline is what counts. The obligation to receive has already applied since 1 January 2025 – every company must be able to accept structured e-invoices. The obligation to issue is staggered: from 1 January 2027 for companies with more than €800,000 in prior-year revenue, and from 1 January 2028 for everyone else. The relevant standard is the European format under EN 16931, implemented as XRechnung or ZUGFeRD. A plain PDF invoice does not meet the requirement. So check early whether your ERP can generate and read these formats – you will find the details in our article on e-invoicing.

Austria: RKSV, BAO and BMD

Austria starts on tamper protection earlier than Germany, but has no general B2B e-invoicing obligation yet.

Cash register obligation under the RKSV

Businesses with more than €15,000 in annual revenue and more than €7,500 in cash revenue are required to use a cash register. The Cash Register Security Ordinance requires a security device with a signature-creation unit that signs every cash transaction and links it into a tamper-proof chain. Every receipt carries a machine-readable QR code, together with an obligation to issue and to accept receipts. An ERP for the Austrian market must generate this signature chain and the monthly and annual receipt export cleanly.

BAO retention periods and connecting to BMD

The Federal Fiscal Code (BAO) prescribes a retention period of 7 years – shorter than in Germany. For accounting, the BMD software (BMD NTCS) dominates in Austria; many tax advisors work with it. Your ERP should deliver a clean export to BMD, just as export to DATEV is standard in the German market. For invoices to the federal government (B2G), e-invoicing via ebInterface or Peppol has been mandatory for years.

Switzerland: GeBüV and the QR-bill

Switzerland regulates bookkeeping through the Code of Obligations and the Ordinance on the Keeping and Retention of Books (GeBüV). Key points: retention of the business books and vouchers over 10 years, proper keeping, plus integrity and immutability of the data. For electronic archiving, non-alterability must be technically guaranteed. A statutory cash register obligation like Austria's does not exist.

In payments, the QR-bill has been mandatory since 30 September 2022 and has fully replaced the red and orange payment slips. It contains the Swiss QR Code with the QR-IBAN and all payment data. An ERP for the Swiss market must generate this QR code correctly and reflect the current VAT rate of 8.1%. You will find details on deadlines and format under GeBüV & QR-bill.

Country comparison: what your ERP must handle per country

The following overview summarizes the central obligations:

The table makes it clear: a single standard setup is not enough for DACH. With multi-country setups, make sure the system applies the right chart of accounts, the correct tax regime and the proper voucher workflow per entity.

What to look for when choosing an ERP

Don't treat compliance capabilities as an afterthought – make them a hard selection criterion. These points belong on your checklist:

• Audit-proof archiving with a gapless audit trail and procedural documentation.
• Certified TSE connection (DE) and RKSV signature chain (AT), if registers are involved.
• EN 16931 formats (XRechnung, ZUGFeRD) for receiving and issuing e-invoices.
• QR-bill with the correct QR-IBAN for the Swiss market.
• Standardized exports to DATEV and BMD – without manual rework.
• Separate entities with country-specific tax rates and charts of accounts.

Compare the systems in the ERP directory and via the comparison against exactly these criteria. For the technical implementation of the connections – TSE, DATEV/BMD interface, e-invoicing formats – a structured ERP integration helps ensure the compliance building blocks work together cleanly instead of standing side by side as isolated solutions.

Conclusion

ERP compliance in DACH is not a checkbox but a country-specific, ongoing task. Germany requires GoBD conformity, a TSE and, from 2027/2028, e-invoicing; Austria demands RKSV tamper protection and BMD export; Switzerland relies on the GeBüV and the QR-bill. Anyone selling across borders needs a multi-entity system that serves all three rule sets in parallel. Put the retention periods and the receipt and signature obligations into your requirements spec early – and when in doubt, have the specific tax-law assessment confirmed by your tax advisor.