Odoo vs Lexware: Accounting for the Mittelstand 2026

In German mid-sized companies, the question is rarely asked the way it is meant. Anyone asking "Odoo or Lexware?" is usually not comparing two accounting programmes with each other, but looking for an answer to an entirely different question: how much of the business itself should actually sit inside a single system?

This comparison deliberately lists no prices. Not out of reticence, but because they decide nothing here: Lexware Office publishes its tariffs openly, they sit in the lower range of the market, and additional user accounts incur no extra cost according to the vendor (lexware.de, accessed 15 August 2026). Anyone looking for the cheapest invoicing software therefore already has their answer — and we will not pretend it is a different one.

The question that actually costs money in the Mittelstand, Germany's mid-sized business sector, lies elsewhere: where does the functional scope of an accounting package end, and who does the work after that? That is precisely what this comparison is about. At doo.FINANCE we accompany this boundary decision regularly — and it is almost never made while looking at an invoice, but while looking at a process.

Lexware, DATEV and Odoo: three tools, three different places

The German accounting market has a peculiarity that often derails comparisons: the best-known names do not sit at the same point in the chain at all.

DATEV sits with the professional practices. By its own account the cooperative has more than 40,000 members — Steuerberater (German tax advisers), Wirtschaftsprüfer (auditors) and lawyers — and itself describes companies as normally obtaining access to its solutions "über die Zusammenarbeit … mit einem Steuerberater", that is, through the collaboration with a Steuerberater (datev.de, accessed 15 August 2026). DATEV is therefore the infrastructure between your company and your practice, not a programme you deploy independently of it.

Lexware sits with the company itself. Lexware Office is the software you pick up when you want to keep receipts, invoices, banking and payroll in house — and which then hands the data over to the practice via a DATEV export. The vendor addresses its target group unmistakably: "Ideal für Selbstständige, Unternehmer, Handwerker, Freelancer" — ideal for the self-employed, business owners, tradespeople and freelancers — and advertises "einfacher Bedienung ohne Buchhaltungskenntnisse", straightforward operation without bookkeeping knowledge.

Odoo sits in a third place. It is not an accounting programme with additional functions, but an ERP in which accounting is one of many applications on the same database — alongside inventory, purchasing, sales, projects, manufacturing and CRM.

Distinguishing these three places is the actual starting point. A company that manages nothing but receipts and payroll is right to compare Lexware with other accounting software. A company whose goods, projects or subsidiaries grow along with it is no longer comparing programmes, but perimeters.

What Lexware Office does well — and why that counts

A comparison that concedes nothing to the competitor is not one. Lexware Office solves three things cleanly, and anyone who needs them should not give them up lightly.

• The entry threshold is low. Operating it presupposes no bookkeeping knowledge. For a company with a manageable volume of receipts that is a real advantage, not a marketing promise.
• Collaboration with the practice is built in. The DATEV export belongs to the standard scope, and the Steuerberater receives their own access with full sight of the data. The handover is solved.
• Additional user accounts cost nothing extra. The vendor writes it itself: "Mehrere Benutzeraccounts ohne Zusatzkosten anlegen" — create multiple user accounts at no additional cost. Anyone who wants to grow is not penalised per head for it.

That is a solid offering for the purpose it was built for. The only question is whether that purpose is still yours.

The perimeter: where Lexware Office ends

Three limits are documented by the vendor. None of them is a shortcoming — they are design decisions. But they become expensive as soon as a company crosses them.

One account, one company

The clearest limit stands in the vendor's Help Center: "Jeden Lexware Office Account können Sie immer nur für eine Firma bzw. ein Gewerbe nutzen" — each Lexware Office account can only ever be used for one company or one trade. For every further entity you need a further account — and for each of them a separate email address.

The decisive part is the second sentence: "Die Daten aus verschiedenen Accounts lassen sich nachträglich nicht automatisiert zusammenführen" — data from different accounts cannot subsequently be merged in an automated way (help.lexware.de, accessed 15 August 2026).

What that means in daily practice is familiar to every holding and every group with a sales entity and an asset-holding entity: the group view arises in a spreadsheet. Every month anew, by hand, without an audit trail. The effort stands in no relation to the price of the software — it arises alongside it, in working hours, and it grows with every further entity.

Inventory, projects, CRM: partner instead of module

The Lexware Office feature overview lists more than 60 functions: invoices, receipt capture, banking, payroll, fixed-asset management, EÜR (the cash-basis statement of income and expenditure), the Umsatzsteuer-Voranmeldung (preliminary VAT return) via ELSTER, Germany's official tax filing portal, DATEV export, quotations, delivery notes and dunning.

What does not stand there is equally revealing: no warehouse management, no manufacturing, no standalone CRM, no project management. The vendor refers these areas to its partner ecosystem — inventory management for e-commerce, "Cloud-Lösungen zu Projektmanagement und Projektzeiterfassung" (cloud solutions for project management and project time tracking), CRM for organising "Kunden, Leads und Vertriebsaktivitäten" (customers, leads and sales activities) — in each case as a connected third-party application (help.lexware.de, accessed 15 August 2026).

Connected is not the same as integrated. Every interface brings three recurring costs with it that stand on no invoice:

1. Reconciliation work. Two systems hold two truths about the same transaction. Someone has to hold them against each other regularly.
2. Time lag. This afternoon's stock level and tomorrow morning's posting describe different states of the same business.
3. Missing audit trail. In a Betriebsprüfung, the German tax audit, the question is not whether the figure is correct, but whether it is documented without gaps. A break between two systems is precisely the place at which that completeness has to be explained.

The desktop line is a different product

Fairness calls for a note that often goes unnoticed: with *financial office*, Lexware offers a second, expressly separate product line — a "kaufmännische Komplettlösung", a complete commercial solution, with accounting, payroll, order processing and inventory management (shop.lexware.de, accessed 15 August 2026). The functional scope reaches further there.

The price for that is, however, an architectural one: it is a locally installed Windows application (Windows 10 or 11) and not the same cloud solution. Anyone moving there from Lexware Office is not changing the package but the product — with everything that a change of product entails in terms of data migration, training and operational responsibility.

What Odoo solves structurally differently

The difference can be stated in one sentence: Odoo does not replace the accounting software, but the chain of accounting software plus connections.

Several entities in one database

Odoo documents multi-entity operation as standard behaviour: in a multi-company database, products and contacts are shared between the companies by default, users are assigned to several companies, and counterpart entries for orders and invoices between your own companies are "automatically created and synchronised" (odoo.com/documentation, accessed 15 August 2026).

For the group closing, Odoo describes a consolidation function that brings the financial data of several companies, each with its own bookkeeping, together "in a single view". The monthly spreadsheet does not fall away because someone works harder — it falls away because the data was never separate.

From the receipt to the stock level without an interface

Because inventory, purchasing, sales, projects and manufacturing are applications on the same database in Odoo, the posting arises where the transaction happens. The goods receipt moves the stock and creates the liability in the same step. The billed project hour is the same hour that stands on the invoice.

That is not a gain in convenience but a gain in control: there is no second truth that would have to be reconciled with the first after the fact.

The route there is a migration, not an update

This too belongs in an honest comparison: the move from an accounting package to an ERP is a project. Chart of accounts, master data, open items, permissions and processes have to be carried over and verified. How such an undertaking actually unfolds in the German Mittelstand we have described step by step in our migration guide from DATEV to Odoo — the sequence and the pitfalls are largely the same in a move away from Lexware.

The decision: not better or worse, but fitting

Four questions are as a rule enough to settle the matter:

• Do you run more than one entity? If so, the group view in Lexware Office works outside the software — permanently.
• Do you move physical goods or do you bill projects? If so, the operational core of your business already sits outside your accounting today.
• How many reconciliations between systems does your team carry out at the monthly close? Those hours are the actual cost of your tool landscape.
• Do you want to keep the books yourself — or in collaboration with your Steuerberater? That answer decides DATEV's role in the setup, independently of the software question.

If every answer falls in the direction of "one entity, no goods, little reconciliation", then Lexware Office is a fitting choice and an ERP would be oversized. As soon as two or more answers point in the other direction, you are no longer comparing programmes but perimeters — and then the invoice that counts is not the vendor's.

Frequently asked questions