Connect Shopware to Lexware Office
Shopware 6 creates invoices itself. Plugins such as Shopware Fibu by Shopsy or the shopqueue service transfer these documents, including the PDF, to Lexware Office, formerly called lexoffice. For a single shop, that is usually enough. A custom integration pays off when old invoices need to be backfilled, sales channels separated, or payments and warehouse processes included.
Which data flows from Shopware to Lexware Office
- Invoice document becomes an income voucher with the Shopware number and PDF on creation
- Credit note and cancellation become a revenue reduction with the original PDF on creation
- Line items become voucher lines with tax rate and posting category with every voucher
- Business customer becomes a contact with VAT ID, private customer a collective contact if you wish with the first voucher
- Payment method is noted on the voucher, for the later bank matching with every voucher
- Open amount from Lexware becomes visible in Shopware as payment status on change
What already exists for Shopware and Lexware Office
Lexware's partner page lists two solutions for Shopware. According to the partner page, Shopware Fibu by Shopsy transfers invoices and credit notes with the PDF generated in Shopware, automatically after creation or manually from the document list. Customers are created from the order, and according to the Store listing, PayPal transactions get a note for bank matching. Shopware 6.4.0 or later is required. shopqueue is a web service that, according to its provider, transfers customers, invoices, credit notes and cancellations with PDF and payment method every 15 minutes.
The Shopware Store has further plugins for Lexware Office. If you have one sales channel and generate Shopware invoices, check these solutions first.
Where the standard stops
Backfilling old invoices
In the Shopware forum, a merchant asked how the invoices of recent months get into Lexware Office after reinstalling the plugin. According to the post, support could not help. Backfills need a date range and protection against duplicate vouchers.
Sales channels into separate accounts
In a 2022 review, a user wished to assign individual subshops to separate Lexware accounts and export only from a certain date. The plugin can now choose which shops are transferred. The listing does not mention separate accounts per channel.
Warehouse and ERP extensions
A user reported in 2021 that automatic transfer with Pickware WMS initially did not work. The provider has since added support. Extensions that generate invoices differently therefore need their own adjustments.
Invoice or voucher
If Shopware creates the invoice, it arrives in Lexware as a voucher. If Lexware creates it, Lexware's number sequence applies. If both routes are mixed, two number sequences exist for the same sales.
How we build the integration
Shopware side: Through the Admin API, we read orders, documents and transactions. Authentication runs through a dedicated integration with client credentials and read-only permissions wherever writing is not needed. A webhook reports new documents. For backfills, there is a run per period and sales channel.
Lexware side: We create income vouchers through the vouchers endpoint of the Public API and attach the Shopware PDF. Every voucher line needs a posting category. We read the matching categories from your Lexware account instead of hard-coding them. Private customers go through the collective contact if you wish, and business customers get their own contact. Before creating, the integration queries the voucher list for the number. This way no voucher is created twice, not even during a backfill.
Operation: According to the documentation, the Lexware API allows two requests per second. Backfills therefore run throttled and with a progress display. Errors such as a missing category or a rejected tax rate appear in the log with order number and reason. After the correction in Shopware, one click is enough to send the voucher again. We test new Shopware versions in advance in a staging environment.
Process and price range
We begin with a free 30-minute check on sales channels, invoice route and backfills. The fixed-price offer is ready after 3 working days. Simple connections between two systems cost from €1,900 net, and implementation usually takes 2 to 4 weeks. More under Process and pricing.
Frequently asked questions
Should the invoice be created in Shopware or in Lexware Office?
If your customers already receive the invoice from Shopware, it stays there and goes to Lexware as a voucher. What matters is that there is only one number sequence for the same sales.
Can invoices from recent months be transferred retroactively?
Yes. We transfer per period and first check which voucher numbers already exist in Lexware Office.
Can several sales channels be transferred separately?
Yes, including into separate Lexware Office accounts. Each channel gets its own credentials and its own rules.
Are payments from Shopware marked as paid in Lexware?
No, the Public API does not create payments. We note the payment method on the voucher so bank matching in Lexware goes faster, and show the open amount in Shopware.
Does this also work for orders with 7 and 19 percent VAT?
Yes. Every voucher line in Lexware Office has amount, tax amount and tax rate. We split mixed orders across several lines, and shipping costs follow the rule your tax advisor specifies.
Sources
- Lexware Partner: Shopware Fibu by Shopsy, retrieved on 20 Oct 2026
- Lexware Partner: Shopware by shopqueue, retrieved on 20 Oct 2026
- Shopware Forum: Lexoffice FiBu reinstalled, transferring old invoices, retrieved on 20 Oct 2026
- Shopware Store: Lexware Office (lexoffice) FiBu, with reviews, retrieved on 20 Oct 2026
- Lexware API Documentation (Vouchers, Voucherlist, Posting Categories, Payments), retrieved on 20 Oct 2026
- Shopware Developer: Admin API Authentication, retrieved on 20 Oct 2026
Related
Shopware 6
Admin API, Store API, Sync API and webhooks: what Shopware 6 offers technically and where plugins stop.
Lexware Office (lexoffice)
lexoffice is now Lexware Office: Public API, webhooks, e-invoicing and limits at a glance.
Shopify → Lexware Office
Shopify orders as invoices in Lexware Office (formerly lexoffice): what the app does, where payments and e-invoicing fall short, what custom code looks like.
Shopware → DATEV
Invoices, credit notes and payments from Shopware 6 to DATEV automatically. What plugins can do, where they stop and what a custom integration looks like.
Shopware → JTL-Wawi
Shopware 6 and JTL-Wawi: what the JTL-Connector syncs, why the sync gets stuck and when custom code makes sense for parts of it.
