Connect HubSpot to Lexware Office

When a deal is won in HubSpot, the invoice should be created in Lexware Office, formerly lexoffice. Apps such as the integration from APIUP or Pipey exist for this and create invoices or drafts from deals. To get started, that is often enough. A custom integration pays off when the payment status should flow back into the CRM, or when line items, discounts and contacts follow their own rules.

Which data flows between HubSpot and Lexware Office

1. Deal in the “won” stage becomes an invoice or invoice draft on stage change
2. Line items of the deal become invoice lines with quantity, price, discount and tax rate with the invoice
3. Company and contact become a Lexware contact with billing address and VAT ID before the first invoice
4. Product from the product library becomes an article in Lexware Office on change
5. Invoice number and link go back to the deal immediately
6. Payment status from Lexware becomes a deal property, such as “open” or “paid” on every change

What already exists for HubSpot and Lexware Office

On Lexware's partner page, APIUP describes an integration that creates closed deals from HubSpot as invoice drafts in Lexware Office. Line items from the deal or quote are carried over, and it first checks whether the customer already exists. A return path to HubSpot is listed there as a future feature.

The HubSpot Marketplace lists the Pipey Lexoffice Integration from zimmer7. According to its listing, a configurable deal stage triggers the invoice, optionally with automatic payment reminders. There are also automation services such as tray.ai with templates for “deal won, create invoice”. If you review invoices after closing anyway, one of these solutions is a good start.

Where the standard stops

• No return path into the CRM

  The apps described work mainly in the direction of Lexware. Whether an invoice has been paid is then visible to sales only in accounting. Lexware Office reports payment changes through event subscriptions, but someone has to process them.

• Webhooks in HubSpot workflows

  According to the HubSpot developer documentation, the “Send a webhook” action in HubSpot workflows is available only with Operations Hub Professional or Enterprise. Without that plan, you need an app with its own webhook subscriptions.

• Notifications contain only identifiers

  HubSpot webhooks deliver the ID and the changed property, not the whole deal. According to the documentation, order and uniqueness are not guaranteed. Without checks, duplicate invoices result.

• Contact or company

  HubSpot separates contacts and companies. Lexware Office wants one invoice recipient, either a company or a person. If a deal has several associated companies, a fixed rule is needed.

How we build the integration

HubSpot side: A custom HubSpot app for your portal subscribes to changes of the deal stage. When it receives a notification, it reads the deal with line items, companies and contacts through the CRM API. Every notification has an event ID, which we store. This way, the same notification is never processed twice. We write invoice number, link and payment status into custom deal properties.

Lexware side: Through the Public API, we search for the contact by name or email and create it only if it is missing. Then the invoice is created, as a draft or directly finalized, as you prefer. For companies and public authorities with a Leitweg-ID (routing ID for e-invoices to public bodies), we set the e-invoice profile. An event subscription on payment changes reports when an invoice has been paid. We verify the signature of every notification.

Mapping: Which HubSpot property goes into which invoice field is defined in a table that we agree on with you. This includes payment term, service date, the customer's order number and the text above the line items. Products without a counterpart in Lexware Office are created as articles by the integration or reported, depending on the setting.

Operation: According to the documentation, Lexware allows two requests per second, and HubSpot retries failed notifications up to ten times. A queue balances both. Anything that cannot be transferred appears as a note on the deal and in the log.

Process and price range

We start with a free integration check (30 minutes) on deal stages, products and invoice approval. After 3 working days, you have a fixed-price offer. A simple connection from HubSpot to Lexware Office starts at €1,900 net, and operation at €149 per month. See Process and pricing and CRM integration.

Updated: 10/20/2026