Skip to Content
SaaSFlow
Integrations

Billomat

Connect a Billomat account to import recurring invoices as subscriptions, with MRR and CMRR, into SaaSFlow.

The Billomat integration reads your Billomat account through the Billomat API. Every recurring invoice (Abo-Rechnung) becomes a subscription in SaaSFlow, with its history built from the invoices it created. SaaSFlow only reads; it never changes anything in billomat.

What gets imported

Billomat objectSaaSFlow object
ClientCustomer, one per client with a recurring invoice.
Article, or the title of an item without oneProduct. Dates and month names are taken out of the title, so "Hosting November 2026" and "Hosting December 2026" are one product.
Recurring invoiceSubscription, billed in the recurring's cycle (daily, weekly, monthly or yearly, every n cycles).
Invoice created by a recurringThe subscription's history: one period per invoice item.
Next invoice of an active recurringWhat the subscription is worth from the next period on, and a planned transaction per item for the cash flow forecast.

When a recurring is deleted, Billomat forgets which invoices it created. SaaSFlow keeps that link from the moment you connect, so later deletions are fine, but a recurring deleted before you connected has no history in SaaSFlow.

Invoices that no recurring created are not imported. They can be one-off sales, and SaaSFlow does not guess a subscription from them. Drafts and canceled invoices are skipped. Payments are not imported either: they show up in your bank account, which you connect on its own.

Service periods

A period starts on the invoice date and runs one billing cycle. If the invoice names its service period as two dates (for example "01.11.2026 - 30.11.2026"), the period starts on the first of them. A period never runs past the start of the next invoice's period. If you bill in advance (the invoice is created before the period it names), the next invoice's period starts where the last one ends.

Billomat does not keep a recurring's earlier cycles. When you change the cycle of a recurring, invoices SaaSFlow has already read keep the cycle they were created on. Invoices from before you connected get the cycle the recurring has on that day, unless they name their service period, so MRR from before a cycle change is an estimate.

Revenue and MRR

MRR uses the net amounts of the invoice items. A discount on the whole invoice reduces every item by the same share. Credit notes do not change MRR. Amounts in currencies SaaSFlow does not support are skipped, and so is an invoice in another currency than its recurring. If you change the currency of a recurring, SaaSFlow keeps the subscription as it was imported and stops updating it.

CMRR

Billomat does not record when a change was agreed. SaaSFlow uses the first time it sees a change:

  • A new price or a new item on a recurring counts as committed when SaaSFlow first reads it, and as MRR when the next invoice period starts.
  • An end date on a recurring counts as committed churn when SaaSFlow first reads it, and as MRR churn after the last period before that date.
  • A recurring that stops creating invoices without an end date counts as committed churn when SaaSFlow first sees it stopped, and as MRR churn after its last invoice period.
  • A deleted recurring counts as committed churn when SaaSFlow first misses it (or earlier, if it already had an end date then), and as MRR churn after its last invoice period.

History from before you connect has no such signal, so CMRR equals MRR there.

Connect

Copy the API key in Billomat

In Billomat, open Settings → Administration → Users (Einstellungen → Administration → Nutzer). Open the user SaaSFlow should read as, turn on API access and copy the API key. Billomat only shows that switch to the user itself, so sign in as that user to do it.

We recommend a read-only user for SaaSFlow. A key of your own user works too, but it can change everything you can.

Add the integration

Integrations → Add integration. Pick Billomat. Enter your Billomat ID, the first part of your Billomat address (mycompany for mycompany.billomat.net), and the API key. SaaSFlow checks the key before it saves it.

Wait for the first import

The navigation bar shows the progress. Billomat allows 100 requests per 15 minutes on the Business plan, so a large account can take a while on the first import.

Use a read-only user

Billomat applies a user's role to its API key. SaaSFlow needs read access to clients and invoices (recurring invoices are part of invoices), nothing else. With such a role, Billomat refuses every write made with the key.

  1. Under Settings → Administration → Users, choose Manage roles (Rollen verwalten). Add a role with read access to Clients (Kunden) and Invoices (Rechnungen), and for now edit access to Administration. Leave every other area without access.
  2. Add a user with this role, for example "SaaSFlow" with an alias of your own email address. Billomat sends that address an email to set the password.
  3. Sign in as the new user, open its own entry under Users, turn on API access and copy the key.
  4. Sign in as yourself again and take Administration out of the role. The user needed it only to turn on its own API access; the key keeps working without it.

Keeping it in sync

SaaSFlow reads the account every night at 03:30 (Berlin time). Use Sync now on the integration for an immediate update.

Each sync reads the whole account, 100 records per request, and counts against your Billomat API limit. A sync stops after about 100 minutes. On the Business plan that is enough for roughly 60,000 records in total (clients, recurring invoices, invoices and their items). If your account is larger, contact us before you connect it.

Reconnecting

If the key stops working, the integration shows an error. Open it, choose Reconnect and paste a new API key. The Billomat ID stays the same; to import a different Billomat account, add a second integration.

Disconnecting

Integrations → ⋯ → Remove. Customers and subscription history stay. In Billomat, delete the SaaSFlow user, or turn off its API access, if you no longer need the key.

On this page