Cloud ERP in Germany: GoBD, E-Invoicing, Works Councils and Realistic Go-Live Costs
Adding or replacing ERP in a German entity is shaped by GoBD, the 2027–2028 e-invoicing deadlines, DATEV and the works council. Here's what each requires, plus realistic budgets and timelines.
Why a German entity changes your cloud ERP shortlist
If your group is adding a German subsidiary, or replacing an old on-premise system at one, the software won't decide much of the project. Four local factors shape a cloud ERP Germany project more than any feature list: GoBD record-keeping rules, the phased B2B e-invoicing mandate, your tax adviser's DATEV workflow, and the works council's right to co-determine how the system is introduced.
Our position: for most German entities under roughly 200 users that report into a non-German parent, a global platform with mature German localization is the better fit. That means Microsoft Dynamics 365 Business Central, SAP S/4HANA Cloud Public Edition, SAP Business ByDesign or Oracle NetSuite. Group consolidation, a shared chart of accounts and one vendor relationship are worth more than the last few percent of local functionality. The exception is a manufacturer with complex variant production. There, German mid-market vendors such as proALPHA or abas deserve a serious look.
This guide explains how the rules generally work. Get binding answers from a German Steuerberater (tax adviser) and an employment lawyer before you commit.
GoBD: what the system must do and what you must document
GoBD is the tax administration's set of principles for keeping books and records electronically. Records must be traceable, complete, accurate, timely, orderly and unalterable. In practice, a GoBD-compliant ERP must:
- Prevent deletion of posted entries. Corrections go through reversals, and every change is logged.
- Support timely recording. Cash transactions are expected to be recorded daily, and non-cash transactions generally within about ten days.
- Keep documents in their original format. For an e-invoice, the structured XML is the legal original, not a PDF rendering of it.
- Give tax auditors machine-readable access through direct read access, indirect evaluation, or a data export on a storage medium.
Retention periods generally run ten years for books and financial statements, eight years for accounting vouchers such as invoices (shortened from ten in recent reforms), and six years for commercial correspondence. Confirm current periods with your adviser.
The part that catches buyers out is the Verfahrensdokumentation, the procedural documentation. It describes your processes, controls, interfaces and archiving, and it's your responsibility, not the vendor's. No official GoBD certification exists. An auditor's attestation of the software, such as one under IDW PS 880, is useful evidence. It doesn't make your procedures compliant.
Plan for the legacy system too. Its data must stay accessible for audits for the full retention period.
B2B e-invoicing in Germany: deadlines and what to configure
B2B e-invoicing in Germany covers domestic transactions between businesses. Invoices must be structured and comply with the European standard EN 16931. Two formats dominate. XRechnung is pure XML, in either UBL or CII syntax. ZUGFeRD is a PDF/A-3 file with the XML embedded. Its EN 16931, EXTENDED and XRECHNUNG profiles qualify, but MINIMUM and BASIC WL don't.
| Date | Requirement |
|---|---|
| 1 Jan 2025 | All domestic businesses must be able to receive e-invoices. An email inbox is enough. |
| Through 31 Dec 2026 | Issuers may still send paper invoices, or PDFs if the recipient agrees. |
| 1 Jan 2027 | Businesses with prior-year turnover above EUR 800,000 must issue e-invoices. Smaller businesses, and EDI used with the recipient's consent, may continue until end-2027. |
| 1 Jan 2028 | All domestic B2B invoices must be e-invoices. EDI is allowed only if EN 16931-compliant data can be extracted. |
If your entity is over the threshold, outbound e-invoicing must be live at the start of 2027. Invoices up to EUR 250 are exempt. Invoices to public-sector buyers already require XRechnung with a buyer routing ID (Leitweg-ID).
Configure four things:
- Inbound validation that rejects malformed XML
- Mapping of incoming invoices into accounts payable
- Archiving of the XML as the original document
- Clean master data for outbound invoices and self-billed credit notes
Also ask each vendor about its roadmap for transaction reporting. The EU's ViDA package introduces digital reporting for intra-EU supplies from 2030, so a system that handles structured invoice data well today is less likely to need rework.
DATEV integration: setting the boundary with your tax adviser
Most German companies use a Steuerberater for VAT returns, annual financial statements and the electronic tax balance sheet (E-Bilanz), and most advisers work in DATEV. Decide early where your ledger ends and theirs begins. Three models are common:
- Ledger in the ERP, batches to DATEV. You book everything in the ERP and export monthly booking batches in DATEV format, with accounts mapped to the SKR03 or SKR04 standard charts and DATEV tax keys applied.
- Documents to the adviser. The ERP runs operations, and the adviser books from document images uploaded through DATEV Unternehmen online.
- Fully in-house. The adviser only reviews and files.
For a subsidiary that reports monthly to its group, model one is usually right, because consolidation needs the ledger inside the ERP. Test the integration before you sign:
- Tax-key mapping
- Transfer of the linked document image
- Customer and supplier master data
- What happens after the adviser locks a period in DATEV
Once a period is locked, corrections have to come back as new postings in the ERP. Prefer connectors from DATEV's partner marketplace over a generic CSV export.
Works council co-determination: the gate foreign groups miss
Under Section 87(1) no. 6 of the Works Constitution Act (BetrVG), an elected works council (Betriebsrat) has co-determination rights over technical systems capable of monitoring employees' behavior or performance. German labor courts read this broadly. A system only has to be objectively capable of monitoring, so an ERP with user logs, timestamps and transaction histories qualifies. The works council also has information rights while the system is still being planned, and it can generally bring in experts at the employer's cost.
The usual outcome is a works agreement (Betriebsvereinbarung). It typically covers:
- The system's purpose and the categories of employee data it processes
- The role and permission concept
- A ban on performance evaluations of individual employees
- How long logs are kept
- How new modules and features get approved
Cloud ERP vendors ship updates several times a year, so define change categories that don't need a fresh negotiation for every release. If the parties can't agree, the matter goes to a conciliation board (Einigungsstelle). Going live without consent risks an injunction that stops the rollout.
Which body you negotiate with depends on scope: the local, company-wide or group works council. Budget roughly two to six months, and inform the works council at shortlist stage, not after you've signed.
Hosting location, data access and audit questions
No law requires a cloud ERP to be hosted in Germany. The Fiscal Code (Abgabenordnung) generally lets companies keep electronic books in another EU member state. Hosting outside the EU generally needs the tax office's approval, and auditors' data access must be guaranteed wherever the data sits.
Expectations go beyond the law. German finance teams, works councils and larger customers typically ask for:
- An EU data-center region
- A GDPR data processing agreement (Auftragsverarbeitungsvertrag)
- A published list of sub-processors
- ISO 27001 certification and often a BSI C5 attestation
Pick an EU region and write it into the contract. Also check where support staff can access your data from. That's where questions about transfers outside the EU usually arise.
Indicative go-live costs and timelines
The figures below are typical 2026 market ranges for a cloud ERP Germany rollout, shown in USD. They vary by contract, partner and scope. German pricing is usually quoted in euros, so confirm with vendors and implementation partners.
| Cost item | Small entity (10–30 users) | Mid-size entity (50–150 users) |
|---|---|---|
| Subscription per full user per month | $70–$130 | $90–$200 |
| Implementation and localization | $40k–$150k | $150k–$600k |
| E-invoicing add-on or service (setup) | $3k–$15k plus per-document fees | $10k–$40k plus per-document fees |
| DATEV interface | $2k–$10k | $5k–$25k |
| Works council process (counsel, experts) | $5k–$20k | $15k–$60k |
| Procedural documentation and GoBD review | $5k–$20k | $15k–$50k |
| Legacy data archive | $5k–$25k | $15k–$75k |
| Typical timeline | 4–7 months | 8–14 months |
Hypothetical example: a 45-person German distribution subsidiary of a Singapore-based group moves to Business Central, with 35 full users and 10 light users. The subscription runs roughly $40k–$50k a year. Add $120k–$200k for implementation and $40k–$90k for the e-invoicing, DATEV, works council, documentation and archive items. That puts the first year at about $200k–$340k, with go-live in seven to ten months, provided works council talks start in month one.
Red flags and a selection sequence that holds up
Walk away from, or push hard on, any of these:
- "GoBD-certified" offered as the whole answer to compliance
- E-invoicing that only produces plain PDFs, or ZUGFeRD MINIMUM or BASIC WL
- A DATEV "integration" that's really a generic CSV export
- A partner with no works agreements behind it
- No plan for keeping legacy data accessible
- Hosting outside the EU that nobody has squared with the Fiscal Code
Then follow this sequence:
- Agree the DATEV model with your Steuerberater.
- Inform the works council at shortlist stage.
- Run scripted demos with German test cases: an inbound XRechnung with errors, a ZUGFeRD credit note, a DATEV batch export and a tax-audit data export.
- Get EU hosting, the data processing agreement and advance release notes written into the contract.
- Draft the procedural documentation during the build, not after go-live.
- Archive the legacy data before you switch the old system off.
Decision rule: if a vendor and its partner can't run the scripted German test cases live in a demo, take them off the shortlist.
Common questions
Is there an official GoBD certification for ERP software?
No. GoBD compliance depends on how you use the system, so software alone can't be certified. Vendors may hold an auditor's attestation, for example under IDW PS 880. That's useful evidence, but you still need your own procedural documentation and controls.
Do we have to host our ERP data in Germany?
Generally no. Electronic books can usually be kept in another EU member state, and hosting outside the EU generally needs the tax office's approval. Many German stakeholders still expect EU hosting, a GDPR data processing agreement and certifications such as ISO 27001 or BSI C5. Confirm your setup with your tax adviser.
Which e-invoice format should we choose, XRechnung or ZUGFeRD?
Your ERP should handle both for incoming invoices, because suppliers will send either. For outgoing invoices, ZUGFeRD in the EN 16931 profile suits customers who still want a readable PDF. XRechnung suits public-sector buyers and customers whose systems process pure XML.
Do we need a works council agreement if our German entity has no works council?
Co-determination applies only where employees have elected a works council. Local HR can tell you quickly. Without one, GDPR and German employee data protection rules still apply to user logs and monitoring, so document what you collect and why.
Can our tax adviser keep doing the bookkeeping in DATEV after we go live?
Yes. Many entities run operations in the ERP and send document images to the adviser through DATEV. Subsidiaries that report monthly to a group usually do better keeping the ledger in the ERP and exporting booking batches. Agree the model with your adviser before you configure the system.
How long does a German ERP go-live realistically take?
Small entities typically take four to seven months, and mid-size entities eight to fourteen. Works council negotiations of roughly two to six months often decide the schedule, so start them at shortlist stage. These are indicative ranges, so confirm them with your implementation partner.
Written by the Cargodeskflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.