ERP with Lexware Integration

Lexware, part of the Haufe Group and based in Freiburg, occupies a distinctive position in the German market: its products serve the small-business and lower-Mid-Market segment with accounting (Accountant), invoicing-and-finance (lexoffice, financial office), payroll (Lohn+Gehalt) and warehouse management (Inventory Management). The integration question for Lexware is therefore twofold: connections within the Lexware family, and connections between Lexware components and the wider e-commerce or industry-specific stack. This page describes both, with attention to the lexware-api as the modern integration substrate replacing older CSV-based exchanges, and to the DATEV-compatible flows that allow Lexware-Accountant users to operate as primary bookkeeping while still working with a DATEV-using tax adviser.

The Lexware product ecosystem

The Lexware product family has evolved into two tracks. The legacy desktop products — Lexware Inventory Management, Lexware Accountant, Lexware Lohn+Gehalt, Lexware financial office — remain widely used in small businesses with installed-software preferences. The cloud track is anchored by lexoffice, a SaaS bookkeeping and invoicing platform that has displaced some of the desktop Accountant footprint and is the primary growth product. Lexware Inventory Management remains the warehouse and order-management component, sitting alongside Accountant on the desktop side. The two tracks interoperate but not seamlessly: customers operating Inventory Management alongside lexoffice typically use a documented import-export flow rather than real-time sync, and Lexware has been progressively closing this gap with the lexware-api.

lexware-api as integration substrate

The lexware-api (formally the lexoffice public API) is the modern integration entry point for the cloud track. It exposes vouchers, invoices, contacts, articles and files via REST with OAuth 2.0 authentication, and is documented in a developer portal with sandbox access. The desktop Inventory Management product offers a separate API layer accessible via the Lexware Inventory Management pro interface. Both APIs make programmatic integration substantially smarter than the legacy CSV exchange that older Lexware setups still rely on; CSV remains supported for compatibility but is operationally fragile when document volumes grow or when timing matters. Buyers integrating Lexware should plan to use the API as the primary path and treat CSV as a fallback only.

DATEV compatibility and tax-adviser flow

Although Lexware competes with DATEV in some segments, the German tax-adviser landscape is dominated by DATEV, and Lexware products therefore implement DATEV-compatible export formats. Accountant and lexoffice both produce DATEV pro exports that the tax adviser imports without manual re-entry. This positions Lexware as a viable choice for small businesses that handle primary bookkeeping in-house but rely on a DATEV-using Steuerberater for year-end statements, tax returns and OSS filings. The GoBD-Verfahrensdokumentation should describe both the in-house bookkeeping process in Lexware and the DATEV export flow; Lexware ships template Verfahrensdokumentation material as part of its product support.

E-commerce and third-system integration

For e-commerce businesses, lexoffice integrates with Shopify, Shopware, WooCommerce, JTL-Shop, billbee and several payment providers (PayPal, Stripe, Klarna) via either native connectors or middleware. Lexware Inventory Management has a more limited but functional set of e-commerce connectors, typically operated through partner middleware. For organisations whose volumes outgrow Lexware — usually around the EUR 5-10 million revenue threshold, depending on transaction count and complexity — migration paths commonly lead to Xentral, weclapp, JTL-Wawi or Microsoft Dynamics 365 Business Central. The migration is non-trivial because Lexware's data model is simpler than that of the upper-tier ERPs and the mapping must add structure that did not previously exist; planning this migration before pain forces it produces cleaner outcomes.

Frequently Asked Questions

Is lexoffice a replacement for Lexware Buchhalter?

For many small businesses, yes. lexoffice covers invoicing, banking, voucher recognition and DATEV export and has become Lexware's primary growth product. Buchhalter remains preferred where the customer needs full double-entry bookkeeping in-house, fixed-asset accounting, more complex cost-centre structures or where the customer simply prefers a desktop client. Lexware is unlikely to retire Buchhalter in the near term, but new investment is concentrated in lexoffice.

Can lexoffice handle OSS VAT reporting?

It can flag intra-EU distance sales and produce the data needed for the OSS quarterly return, but the return itself is typically filed via the German Federal Central Tax Office (BZSt) portal by the tax adviser. lexoffice generates the underlying transaction data with country-of-consumption tags; the tax adviser uses it to compile the OSS return. For sellers operating substantial volumes across multiple EU member states, a specialist tax-tech provider (Hellotax, Taxdoo, Avalara) is often added alongside lexoffice rather than replacing it.

Which ERPs replace Lexware as a business outgrows it?

The common upgrade paths in the German Mittelstand are Xentral (cloud-native, similar SMB orientation), weclapp (cloud, broader CRM-plus-ERP scope), JTL-Wawi (for e-commerce-heavy businesses) and Microsoft Dynamics 365 Business Central (for businesses needing broader functional scope and international rollout). The migration should be planned with explicit data-mapping work; the simpler Lexware data model rarely maps one-to-one onto the target ERP.

Does Lexware support the German KassenSichV for retail?

Lexware does not ship a point-of-sale module with native TSE support, so retailers using Lexware for bookkeeping typically pair it with a separate KassenSichV-compliant POS system (orderbird, ready2order, vectron, TSE-cloud from fiskaly) that exports to Lexware via API or DATEV-format file. The Verfahrensdokumentation should cover the POS-to-Lexware flow as well as the Lexware-to-DATEV flow.