Billing & Invoicing

The SaaS Founder v1.0

Runs a twelve-person SaaS that sells to companies in nine EU countries and is about to add a usage-based tier. Wants plans, trials and price changes without a developer sprint, reverse charge that is right without thinking about it, failed cards retried before they turn into churn, and a billing bill that does not grow faster than revenue.

The Finance Lead v1.0

Closes the month for a software company with eight million euros of recurring revenue. Wants MRR that reconciles with the ledger, deferred revenue scheduled rather than estimated in a spreadsheet, a journal or DATEV export the accountants can book without retyping, and dunning that stops before it reaches a key account.

The Billing Engineer v1.0

Wires billing into the product and gets paged when a webhook goes missing. Wants a documented API for usage events, idempotent webhooks, entitlements the app can read, a sandbox that behaves like production, and a migration path that moves subscriptions and payment tokens out again if the company outgrows the tool.

The Service-Business Owner v1.0

Runs an IT service company with two hundred maintenance contracts, hosting packages and monthly retainers, all billed to German businesses. Wants contract terms and price increases handled by the system, SEPA direct debit with mandates, e-invoices that public-sector customers accept, a DATEV export for the tax adviser, and customer data kept in Europe.

The Tax Adviser v1.0

Advises software and subscription businesses and sees what their billing tools get wrong at the year-end audit. Wants sequential numbering and credit notes instead of edited invoices, XRechnung and ZUGFeRD now that the B2B e-invoice is mandatory, VAT IDs checked before reverse charge is applied, and a merchant of record that says in writing which tax it owes.

The Skeptic v1.0

Has seen "automated recurring revenue" turn into a tool that takes a percentage of every euro billed and keeps the payment tokens when the customer leaves. Reads "e-invoicing ready" that means a PDF, "global tax compliance" with no word on who is liable, merchant-of-record terms that let the vendor change fees at will, and subprocessor lists that stop at the hosting provider — and asks what leaving would cost.