Skip to main content
Audact
See the offer

Integration · lexoffice

Chase the invoice without chasing the rules.

Planned · no date set

Read the outstanding invoices, place the payment-reminder call, write the outcome back as an activity. The part that is easy to get wrong is not the call but the permission to make it: outbound in Germany runs into § 7(2) UWG, and the eligibility check answers that question before the dialler does.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "payment_promised",
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "eligibility": { "decision": "allow", "reasons": [], "checked_at": "2026-08-15T09:58:12Z" },
  "write_back": {
    "system": "lexoffice",
    "invoice_ref": "RE-2026-00841",
    "promised_on": "2026-08-22",
    "activity": "Zahlungserinnerung telefonisch"
  }
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

The eligibility block is the one to read first. It is the record that the dial was permitted, and it exists whether the call connected or not.

What applies to the call

Telephone advertising without prior express consent is an unacceptable nuisance; the standard is stricter towards consumers than towards businesses, and neither is free.
Gesetz gegen den unlauteren Wettbewerb (DE), § 7(2)
The person must be told they are speaking to an AI system, at the latest at the first interaction.
Regulation (EU) 2024/1689, Art. 50(1) and 50(5)
Consent must be demonstrable by the controller.
Regulation (EU) 2016/679 (GDPR), Art. 7(1)

What Audact governs in the call

Outbound eligibility before every dial: consent state, registries, quiet hours, frequency caps.
In controlled testing · Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
Article 50 disclosure at the top of the call, recorded.
In controlled testing
A receipt for the calls you did not make, with the reason code.
In controlled testing
Write-back of activities and payment promises into lexoffice.
Planned

Sector

The Mittelstand runs on lexoffice, and on late payments.

Handwerksbetriebe, freie Berufe and small trading companies keep their invoicing here. Receivables get chased by whoever has time, which usually means late and inconsistently. And a reminder call at the wrong hour to the wrong number is worse than no call at all.

A governed agent makes the timing and the permission a property of the system rather than of whoever picked up the list. That is what this integration sells: not more calls, but calls you can account for.

Setup

Four steps, once the integration ships.

  1. Connect lexoffice from your Audact tenant.
  2. Choose which invoice states trigger a call, and after how many days.
  3. Configure the disclosure wording and the frequency cap per contact.
  4. Run in shadow mode, read the eligibility receipts, then switch to active.

Questions

Is a payment reminder advertising under § 7 UWG?
A pure reminder about an existing contract is generally not advertising, but the line moves as soon as the call also offers something. The eligibility pack is configured per campaign type for exactly that reason, and the receipt records which type applied.
What if the contact says stop?
The opt-out is written into the consent record, not just the CRM, and the next eligibility check blocks the dial. That is what makes the promise survive a change of tooling.

Do not wait for the integration

Every integration will be built on the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots. Where a sector system exposes an API, the shorter route is to call it from your side and let Audact govern the conversation.

See the API

Related