ConFlowIO
Enquire

Accounting

Lexware Office

Orders from the Commerce Bundle become invoices in Lexware Office, either as drafts or finalised with a PDF. The PDF moves on as a file — to email sending, say.

On top, customers and suppliers are read and maintained, vouchers are read with status and open amount, and invoices from suppliers, marketplaces and carriers are recorded as bookkeeping vouchers.

Demo on your own data

An order that already has an invoice is skipped.

  1. Lexware OfficeAccounting
  2. ConFlowIOintegration platformRun active
  3. Shopware 6
  4. Shopify
  5. WooCommerce
  • 7ready-made building blocks
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Seven building blocks for Lexware Office

  • Create invoicesWrite

    Creates invoices from orders, as drafts or finalised with a PDF — to the collective customer or to a contact of its own per buyer. An order already invoiced is skipped.

  • Read contactsRead

    Reads customers and suppliers.

  • Write contactsWrite

    Finds customers and suppliers by identifier, customer or supplier number or email address and creates or changes them.

  • Read vouchersRead

    Reads invoices, down-payment invoices, credit notes, order confirmations, quotations, delivery notes and bookkeeping vouchers with status, total and open amount — also only those changed since the last run or only the overdue ones, with the PDF, line items and uploaded receipt files if wanted.

  • Record bookkeeping vouchersWrite

    Records supplier, marketplace and shipping invoices as well as fees with their receipt file. An existing voucher is recognised by its voucher number and never booked twice.

  • Read paymentsRead

    Reads the payments for vouchers.

  • Free request

    For anything without a ready-made building block: a request to the API, using the stored credentials.

In practice

Two workflows with Lexware Office

  1. Invoice for an order

    Every order invoiced exactly once, the PDF where it is needed.

    1. Triggera schedule
    2. Readorders from shop or marketplace
    3. Createinvoice in Lexware Office, draft or finalised
    4. Sendstore the PDF or send it by email

    A second run creates no second invoice.

  2. Report paid invoices back

    Shop or ERP should learn which invoice has been paid — without anyone matching bank statements.

    1. Triggera schedule
    2. Readvouchers from Lexware Office, only those changed since the last run
    3. Checkstatus and open amount
    4. Reportpaid invoices to the shop or ERP

    The payment status is where it is needed and is not copied over by hand.

Good to know

What to know about Lexware Office

  • PrerequisitesWhat has to be set up on your side.
    • The Public API extension in Lexware Office
    • The credentials are stored encrypted in ConFlowIO
  • Not coveredLimits of the integration and of Lexware's API.
    • Invoices in euros with German VAT
    • Credit notes and tax-exempt deliveries abroad are not created
    • Payments are read; Lexware's API does not allow booking them
  • DurabilityApplies to this integration as to every workflow in ConFlowIO.
    • Failed steps retry themselves
    • Large reads are processed page by page, each page a step of its own
    • A failed run is continued rather than started over
    • Live logs per step, with credentials removed

Works well with

What works with Lexware Office

Frequent partners

Orders from every shop and marketplace come out in the same order model.

Contact

See Lexware Office on your own data

We are glad to show ConFlowIO on your own data. Bring a real slice of your orders or vouchers.

The difference shows at real volumes — not at five sample records.

Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.

Rather write directly?info@conflowio.com