lexoffice

Connect AI agents to lexoffice, the German SMB accounting platform. Agents manage contacts, create invoices, quotations, credit notes, and dunnings, render document PDFs, record bookkeeping vouchers with file attachments, and register webhook event subscriptions.

38 actions API key available

lexoffice website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

An order marked paid arrives from the storefront

List Contacts resolves the customer by email against the lexoffice address book

Create Contact registers the buyer as a customer when no match exists

The agent assembles line items, tax type, and payment condition and validates them against the order

The bookkeeper approves the assembled invoice, because once finalized it can no longer be edited

Create Invoice writes the invoice with Finalize on

Render Invoice PDF produces the document and stores it in FlowRunner file storage

The PDF link posts to the accounting channel and goes out to the customer with the receipt

What This Integration Enables

lexoffice is where German small businesses keep their books in order, and German bookkeeping is unforgiving about order: documents follow a sequence, finalized invoices are immutable, and every income and expense entry wants its original receipt attached. That discipline is exactly why the work suits agents. The rules are explicit, the sequence is knowable, and the platform's optimistic locking and finalization model make sloppy automation fail loudly instead of corrupting the books. FlowRunner agents run the full document chain: they sync customers and vendors as contacts, create quotations, order confirmations, delivery notes, invoices, credit notes, and dunnings, render any of them to PDF for delivery, and record supplier documents as bookkeeping vouchers with the original file attached. - One contact record feeds the entire document sequence, so nothing is retyped between stages - Rendered PDFs land in FlowRunner file storage with downloadable URLs, ready for email or archive - Vouchers carry their scanned originals, keeping the audit trail intact from day one - Event subscriptions can point lexoffice callbacks at an inbound endpoint, so changes made inside the accounting tool can start flows elsewhere - Writes that reach a customer wait for [human-in-the-loop](/concepts/human-in-the-loop) approval

Without FlowRunner

The document chain is manual choreography Quotation, order confirmation, delivery note, invoice: each one retyped from the last, each a chance to drift

Supplier paperwork piles up Incoming invoices sit in a mailbox until month end, then get keyed in from memory under deadline

Chasing payment is nobody's favorite job Overdue invoices wait until someone works up the energy to send reminders, so they wait weeks

With FlowRunner

Documents flow from one source of truth Agents carry the same contact and line items through the whole chain, from quotation to dunning

Vouchers land with their evidence attached Every supplier invoice becomes a bookkeeping voucher with the original scan attached the day it arrives

Dunning runs on a schedule, with a person deciding The agent surfaces every overdue invoice weekly; a human picks who gets reminded, and the paperwork writes itself

Use Case Scenarios

Paid order to finalized invoice, without the Friday backlog

Orders flow in from [Shopify](/integrations/shopify) and payments from [Stripe](/integrations/stripe). For each paid order the agent resolves the buyer with List Contacts, creates the contact if needed, and assembles the invoice with the right tax type and the payment condition pulled from List Payment Conditions. The bookkeeper approves the batch each morning. The agent then calls Create Invoice with Finalize on, renders each PDF, and sends it to the customer through [Brevo](/integrations/brevo), posting the day's run to [Slack](/integrations/slack). Invoicing stops being a backlog and becomes a review.

Supplier invoices become compliant vouchers the day they arrive

Supplier PDFs arrive in a shared mailbox. The agent extracts vendor, amounts, and tax lines, matches the vendor with List Contacts, picks the ledger account from List Posting Categories, and calls Create Voucher followed by Upload Voucher File so the original scan is attached to the entry. Anything with an unfamiliar vendor or an amount outside the usual range goes to the controller for a look before posting. At month end the books are already current, and every entry carries its evidence.

A dunning run with a human choosing who gets chased

Every Monday the agent calls List Vouchers filtered to open invoices past their payment terms and posts the list to the finance channel: customer, amount, days overdue, payment history. The owner strikes the accounts under active negotiation and approves the rest. For each approved invoice the agent calls Create Dunning, renders the PDF with Render Dunning PDF, and emails it to the customer. Receivables get chased every week, and no good relationship gets a form letter by accident.

Human-in-Loop Highlight

Create Dunning is the write on this page that reaches a customer and cannot be unsent. A payment reminder is a legal escalation in German commercial practice and a relationship event everywhere: send one to a customer whose payment is already in transit, or one who negotiated an extension with your sales lead last week, and the apology costs more than the receivable. So the dunning agent never selects its own targets. It assembles the overdue list with amounts, ages, and payment history, and asks: "Twelve invoices past terms. Three belong to accounts flagged by sales. Approve the other nine?" The owner answers, and only then do Create Dunning and Render Dunning PDF fire. The sweep runs at machine speed; the decision about who gets a formal reminder stays human.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

38 actions

Contacts

Create Contact Creates a customer or vendor contact as either a company or a person, with email, phone, and billing address details.
Update Contact Updates an existing contact by ID using lexoffice's optimistic locking: the current version from Get Contact is required, and a stale version is rejected.
Get Contact Retrieves a single contact with roles, details, addresses, and the current version needed for updates.
List Contacts Retrieves a paginated contact list, filterable by name, email, customer or vendor number, or role. The lookup behind every match step.

Invoices

Create Invoice Creates a sales invoice with line items, as an editable draft or immediately finalized. Finalized invoices can be rendered to PDF and are no longer editable.
Get Invoice Retrieves an invoice with address, line items, totals, tax breakdown, payment status, and version.
Render Invoice PDF Renders a finalized invoice to PDF and stores it in FlowRunner file storage with a downloadable URL.

Quotations

Create Quotation Creates a sales quotation with line items and an optional expiration date, as a draft or finalized to open status.
Get Quotation Retrieves a quotation with line items, totals, expiration date, and status.
Render Quotation PDF Renders a quotation to PDF and stores it with a downloadable URL.

Order Confirmations

Create Order Confirmation Creates an order confirmation with line items, always in open status and ready for rendering.
Get Order Confirmation Retrieves an order confirmation with line items, totals, status, and version.
Render Order Confirmation PDF Renders an order confirmation to PDF and stores it with a downloadable URL.

Credit Notes

Create Credit Note Creates a credit note with line items, as a draft or finalized to open status.
Get Credit Note Retrieves a credit note with line items, totals, status, and version.
Render Credit Note PDF Renders a credit note to PDF and stores it with a downloadable URL.

Delivery Notes

Create Delivery Note Creates a delivery note with line items, as a draft or finalized. Quantities matter here; prices are accepted but optional in many workflows.
Get Delivery Note Retrieves a delivery note with line items, status, and version.
Render Delivery Note PDF Renders a delivery note to PDF and stores it with a downloadable URL.

Dunnings

Create Dunning Creates a payment reminder referencing an open invoice, inheriting its recipient and amounts. The action this page's human gate exists for.
Get Dunning Retrieves a dunning with its referenced invoice, line items, status, and version.
Render Dunning PDF Renders a dunning to PDF and stores it with a downloadable URL.

Down Payment Invoices

Get Down Payment Invoice Retrieves a down payment invoice with line items, totals, and status. These are created inside lexoffice and read-only via the API.

Vouchers and Files

Create Voucher Creates a bookkeeping voucher with tax line items, recording an income or expense entry for a sales or purchase document.
Get Voucher Retrieves a voucher with type, amounts, tax items, associated files, and version.
Upload Voucher File Attaches a PDF, JPG, or PNG scan of the original document to an existing voucher. The step that keeps the audit trail complete.
List Vouchers Lists all documents across the account in one paginated feed, filtered by type and status. The discovery step behind reporting and dunning sweeps.
Upload File Uploads a standalone voucher scan to lexoffice and returns its file ID for later reference.
Download File Downloads a file from lexoffice by ID and stores it in FlowRunner file storage with a downloadable URL.

Reference Data

Get Profile Retrieves the account profile behind the API key, including organization ID, company name, and tax type. The sanity check that a flow is talking to the right books.
List Countries Retrieves supported countries with ISO codes and tax classification, EU member state or third country.
List Payment Conditions Retrieves the payment conditions configured in the account, with durations and discount terms, for setting terms on documents.
List Posting Categories Retrieves the income and expense posting categories with default tax rates, for assigning voucher items to the right ledger account.
List Print Layouts Retrieves the document templates configured in the account, referenced when creating documents to control appearance.

Event Subscriptions

Create Event Subscription Registers a webhook so lexoffice calls a URL when a chosen event occurs, such as an invoice status change or a new contact.
List Event Subscriptions Retrieves all registered webhook subscriptions with event types and callback URLs.
Get Event Subscription Retrieves a single subscription by ID with its event type and callback URL.
Delete Event Subscription Deletes a subscription by ID, stopping further callbacks for that event.

Frequently Asked Questions

What can FlowRunner do with lexoffice?

FlowRunner agents can run Create Contact, Update Contact, and Get Contact in lexoffice, plus 35 more actions.

Does connecting lexoffice to FlowRunner require OAuth?

No. lexoffice connects to FlowRunner with an API key, no OAuth flow required.

Can lexoffice trigger a FlowRunner workflow automatically?

lexoffice doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with lexoffice

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us