Odoo Integration Services in Germany
Integrations are easy to demonstrate and hard to run. The work is not the connection, it is what happens on the day one side is down.
What changes the cost of an Odoo integration in Germany
The delivery method is the same everywhere. What moves the number is what this market demands of the system, and how much of that Odoo already covers.
Germany runs E-Rechnung. That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
7 of the 19 payment options that matter in Germany are not shipped with Odoo, so they need a paid connector or a build. 12 ship in the box.
10 of the 14 couriers used in Germany have no Odoo connector. 4 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's Germany localization does not cover everything. The gaps are listed on the country page and each one is either a build or a bought module.
Statutory payroll in Germany has its own rules. Whether Odoo ships a payroll localization for this market decides if that is configuration or development.
Market facts on this page checked on 22 August 2026 by Waqas Riasat, Way4Tech.
Where Germany starts from
Germany runs 6 native Odoo localization items and 4 custom ones. Integrations here sit on top of whichever of those already exists, which is a different job to building on a market with no localization at all.
Where we deliver in Germany
An integration depends on which systems sit on the other end, not on which city the business sits in. Berlin, Munich, Frankfurt, Hamburg, Cologne, Stuttgart and Dรผsseldorf, and businesses across Bavaria, North Rhine-Westphalia, Baden-Wรผrttemberg and Hesse, are covered on the same terms.
What odoo integration has to satisfy in Germany
The rules that decide how much of this is configuration and how much is a build. Everything below is from our Germany register, checked against a primary source.
Every German business has had to be able to receive structured e-invoices since 1 January 2025. Issuing is still in transition: 2026 is the last full year in which paper or PDF is allowed with the buyer's agreement.
- A structured electronic format that is issued, sent and received electronically and meets the European standard under Directive 2014/55/EU. XRechnung (pure XML) and ZUGFeRD (PDF with embedded XML) both qualify. Parties may also agree another format if the required data can be extracted correctly and interoperably.
- Post-audit, not clearance. There is no government platform and no real-time reporting for B2B. Transmission is free choice, for example email or Peppol.
- Transition under section 27 UStG: paper and other electronic formats stay allowed with the recipient's consent for supplies up to 31 December 2026, and up to 31 December 2027 if the issuer's total turnover in the previous calendar year was 800,000 euro or less. Legacy EDI that does not meet the standard also runs to 31 December 2027.
- Invoices must be kept for 8 years under section 14b UStG.
- Federal B2G: XRechnung as the standard, the Leitweg-ID as a mandatory field carried in the buyer reference, plus bank details, payment terms and an email or De-Mail address, submitted through the federal portal after registering a user account. Direct contracts up to 1,000 euro are exempt.
- Tax The standard VAT rate is 19% and the reduced rate is 7% (section 12 UStG). A 0% rate applies to certain solar installations.
- Tax From 1 January 2026 food served in restaurants and catering moved from 19% to the 7% rate under the Steueraenderungsgesetz 2025. Drinks stay at 19%. It also covers bakeries, butchers, food retail, catering and canteens in schools, kindergartens and hospitals.
- Tax Preliminary VAT returns (Umsatzsteuer-Voranmeldung) are due by the 10th day after the end of each period and must be transmitted electronically in the officially prescribed dataset. The period is the calendar month if the previous year's tax was more than 9,000 euro, otherwise the calendar quarter. The tax office can waive preliminary returns if the previous year's tax was 2,000 euro or less.
- Tax Small business rule (section 19 UStG): no VAT is charged if total turnover did not exceed 25,000 euro in the previous calendar year and does not exceed 100,000 euro in the current year.
- SKR03 and SKR04 charts of accounts, SKR03 by default
- Balance Sheet, Profit and Loss, Umsatzsteuervoranmeldung tax report, EC Sales List and Intrastat
- DATEV export for the tax adviser, split into documents and journal entries
- GoBD traceability: creator, creation date, modification date and modifying user on every record
- Point of sale technical security system and DSFinV-K export
- XRechnung CIUS and Peppol BIS Billing 3.0 among the standard e-invoicing formats, with Odoo acting as its own Peppol access point and SMP and Germany on the eligible list
- ELSTER filing. Odoo produces the Umsatzsteuervoranmeldung report but does not transmit it to ELSTER. Third-party export modules exist.
- Leitweg-ID for federal B2G invoices. Handled by a third-party module rather than the standard localization.
- E-Bilanz under section 5b EStG. Not in Odoo. It stays with the tax adviser's software.
- ZUGFeRD profile coverage and inbound reading of supplier e-invoices into vendor bills. Confirm per project rather than assuming.
Reviewed 2026-08-22. The full Germany register
How we run the work
5 stages, the same in every market: Data flow mapping, Interface and access setup, Build with failure handling, Testing the unhappy paths, Go-live and reconciliation. The method does not change by country, so it is written up once rather than repeated here.
The integrations this market usually needs
Badged by what it takes in Odoo. Anything not marked In Odoo is a paid connector or a build, and that is the part quotes usually miss.
Questions we get asked
- How long does a typical integration take?
- A single well-documented flow with sandbox access on both sides is a short piece of work. What extends it is nearly always outside the code: waiting for credentials, discovering the other API is undocumented in the area you need, or finding that nobody has decided which system owns the customer record.
- Can you integrate a system that has no API?
- Often, through file exchange, database access or scheduled exports, and the result works. It is less immediate and needs stricter reconciliation because there is no acknowledgement to rely on. We would rather do that properly than pretend a scraped interface is an integration.
- Does Odoo have an official localization for Germany?
- Yes. Odoo ships 6 native items for Germany, covering the basics of the chart of accounts and statutory setup. 4 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in Germany?
- Every German business has had to be able to receive structured e-invoices since 1 January 2025. Issuing is still in transition: 2026 is the last full year in which paper or PDF is allowed with the buyer's agreement. The Germany e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in Germany?
- The standard VAT rate is 19% and the reduced rate is 7% (section 12 UStG). A 0% rate applies to certain solar installations.
- Do you work with businesses in Berlin and other parts of Germany?
- Yes. An Odoo integration runs remotely by default, and being based in one city inside Germany does not change the plan or the price. Cities we cover for on-site visits: Berlin, Munich, Frankfurt, Hamburg, Cologne, Stuttgart, Dรผsseldorf. Regions we cover: Bavaria, North Rhine-Westphalia, Baden-Wรผrttemberg, Hesse. We travel on-site for discovery workshops and go-live week when the engagement calls for it.