Idempotent usage events: keys, dedupe windows and late arrivals
What a usage event's idempotency key should be made of, how long to keep it, and what to do with events that arrive after the billing period has closed.
Expert articles on EU billing, compliance and SaaS invoicing in the European market.
What a usage event's idempotency key should be made of, how long to keep it, and what to do with events that arrive after the billing period has closed.
How the One Stop Shop works for digital services, and which fields your billing system should store per invoice line so the quarterly return builds itself.
Why a plan shouldn't just have a price: plan versions, sales and contract periods, pricing snapshots on the invoice line, and meter versions.
What goes into the DATEV posting batch, how postings link to invoices, and which three balances must agree at month end, with a worked Stripe clearing example.
What to demand from billing software for the EU market, weighted must and should, and how to test each requirement yourself in a vendor demo.
20 seats added on 16 April, 10 removed in May, 30 more on an annual contract: three seat cases worked through, with the rules your contract should state.
Sandbox, idempotency keys, RFC 9457 error format, webhook outages, data export: a concrete two-week test plan for choosing a billing API.
A validation workflow for EU VAT IDs in SaaS billing: normalisation, statuses for outages, retry rules, the German BZSt option and proof that matches each invoice.
From €99 to €119 per seat: what a new price means for monthly customers, annual contracts, grandfathered accounts and open quotes, and what breaks on the day.
Mandatory details and their typical mistakes, the exact wording, an annotated sample invoice, VAT category AE in the XML and the EC Sales List check.
Three validation layers, one validator, five recurring rule failures: how SaaS teams check XRechnung before sending instead of after the customer complains.
Receiving since 2025, issuing from 2027 or 2028: which capabilities e-invoicing software for SaaS needs, when, and what to test in the vendor demo.
A failure catalogue for EU VAT in billing: how each error shows up, where it comes from, how to correct it and which query catches it early next time.
Signature checks per Standard Webhooks, deduplication by message ID, ordering by object version, and a reconciliation job for missed events.
Tax profile, invoice snapshot, credit note, selling entity: the data objects where generic billing APIs break down in European B2B.
Germany's GoBD principles applied to a SaaS billing stack: locking, versioned master data, deletion dates from year end, and process documentation that keeps up with releases.
One SaaS contract with a licence, a migration fee and API usage, run through the five IFRS 15 steps: allocation, January revenue and a mid-year upgrade.
One price table, two invoice totals: volume and graduated tiers worked through, with the boundary cliff, the counting scope and the rounding rule.
A plan with 5,000 included documents, worked through: what happens to the allowance on a mid-month upgrade and when the overage gets invoiced.
A scorecard for usage-based billing: idempotency, late events, pricing models, traceability and EU tax, tested on your own data rather than vendor slides.
Peppol is a delivery network, not a format. When SaaS vendors need it, how access points and participant IDs work, and what your billing system has to store.
Seats, prorated add-on seats and API usage as an XRechnung: the fields your billing data model has to supply, and where the Leitweg-ID comes from.
When a business customer is in default, what you can then charge, a dunning sequence day by day, and six cases where the automation has to stop.
What matters before, during and after collection: creditor ID, mandate evidence, refund windows, the B2B scheme, pre-notification and return codes.
A decision table, a state model for VAT numbers, one decision record per invoice line, and what must happen on status changes and credit notes.
Five tax questions, one fixed order and a stored decision object per invoice line: how to build EU tax logic you can test and explain line by line.
An architecture for EU subscription billing: data model, immutable events, the tax decision at invoice creation, and returned debits that actually reach the product.
What to check between quarter end and filing the OSS return, and how credit notes and late VAT IDs should land in quarters you've already closed.