ERP Consultant in Germany

What German companies usually need from a new ERP

The German businesses that contact me tend to fall into two groups. The first is the owner-led Mittelstand manufacturer, often a specialist in machinery, components, plastics or metalwork, whose order book and product range have grown faster than its software. Planning lives in spreadsheets, the shop floor works from printed job cards, and costing a custom variant takes far too long. The second is the German subsidiary of a foreign group, which must satisfy local bookkeeping and tax rules while reporting upward in the parent's structure and language.

Both need the same discipline at the start: a clear picture of how work flows today. I run remote process mapping sessions with the people who do the work, from quotation and order entry through material planning, production, shipping and invoicing, and I record what breaks, where data is retyped and which reports management cannot get.

From that I write a requirement set that separates genuine needs from habits. A manufacturer might need variant configuration and capacity planning; a sales subsidiary might mainly need clean intercompany purchasing and a reliable link to the group ledger. That distinction keeps the shortlist honest. If you are still at this stage, my requirements gathering service explains the method, and the manufacturing page covers production-specific needs.

Bookkeeping, archiving and e-invoicing expectations

German practice puts weight on records that are complete, traceable and protected from silent changes. The principles commonly referred to as GoBD cover how bookkeeping data and supporting documents are captured, stored and made available to an auditor, and they expect a documented description of the procedure. For an ERP that becomes concrete design points: postings that cannot simply be edited after the fact, a visible change history, period locks, receipts stored with their bookings and a retention approach that matches what your advisor requires.

Invoicing is changing too. Germany is moving B2B invoicing toward structured electronic formats, and companies increasingly need to receive such invoices and, over time, issue them. I do not quote timelines, because they depend on your company and shift with official guidance. Instead I check which structured formats each shortlisted platform can read and create, natively or through a connector, and I ask your tax advisor to confirm what applies to you today.

I configure and document; tax and legal advice sit outside my role. The interpretation of GoBD, VAT treatment and e-invoicing obligations stays with your Steuerberater and auditor. What I deliver is a system whose behavior they can understand and verify, plus a draft procedure description they can review. My ERP solution design work covers how these controls are built in.

Choosing between Zoho, Odoo, ERPNext and Dynamics 365 in Germany

German shortlists are rarely decided on features alone. Three questions usually carry more weight: whether a German localization exists and how complete it is, how the platform exchanges data with a DATEV-based tax advisor, and who will support the system in German after go-live. I assess each candidate on those questions alongside the fit-gap results.

• Odoo can suit manufacturers and wholesalers wanting production, purchasing, stock and accounting in one database, provided the German localization and any advisor export are checked carefully.
• Microsoft Dynamics 365 Business Central deserves a close look from subsidiaries already standardized on Microsoft at group level, and for firms expecting a partner-led rollout.
• ERPNext appeals to companies that value open source and have a reliable hosting and development arrangement, though German-specific features need closer verification.
• Zoho fits service companies and smaller trading firms that put CRM and sales workflows first and leave the ledger with their advisor.

Hosting location belongs in the discussion as well. Many German buyers prefer data held within the EU, so I check which data center options each vendor currently offers. The findings feed a weighted scoring sheet within my ERP evaluation service, and you decide with the evidence in front of you.

Works councils, payroll and the people side

A system change in a German company is not only a technical project. Where a works council exists, tools that log user activity, record times or could be used to assess performance are typically discussed with it before rollout. I cannot advise on co-determination law, but I can make that conversation easier: I prepare plain descriptions of each role, what it can see, what the system logs and why, so HR and management have accurate material to present.

Payroll is another boundary. German payroll is specialized and usually stays with a dedicated provider or with the tax advisor's payroll service. My design treats it as an integration: cost centers and summarized journals flow into the ERP, while individual pay data stays where it is governed. The same thinking applies to GDPR more widely. I map where personal data enters the ERP and CRM, restrict access by role and agree retention rules with your data protection contact.

Language is handled openly. The engagement runs in English, which suits many subsidiaries and export teams. German-language documents, shop-floor training and communication with staff are delivered by German-speaking key users on your side or a training provider you choose, using the English process maps, test scripts and training outlines I write. My ERP training approach is built around exactly that train-the-trainer model.

How a remote engagement with a German team runs

I work remotely with businesses in Germany and keep live sessions inside the overlap between the Central European morning and my afternoon in India. Workshops, design reviews and acceptance testing happen in that slot; configuration checks, documentation and vendor follow-up happen around it, so progress continues between calls. A visit is possible by arrangement; few projects need one.

Each engagement has a named owner on your side, a shared decision log and a short weekly status note in English that management and, where relevant, group headquarters can read. When a German implementation partner is involved, I act for you, not for them: I review their proposals, test their configuration against the agreed design and keep scope changes visible. That role is described on my fractional ERP lead page.

Data migration deserves its own plan. Older German installations often hold many years of article numbers, customer records and open items in formats that need cleaning before they move. I run trial loads, reconcile against the balances your advisor has confirmed and time the cutover around a period end. For more context on this market, visit my Germany page, read the ERP migration checklist or get in touch.