Skip to main content
New German e-invoicing mandate from 2027: Kontier issues XRechnung and ZUGFeRD natively German e-invoicing 2027: XRechnung native

Billing software for European SaaS: requirements and test cases

7 min read Kontier editorial team

A billing vendor's demo shows how smoothly a plan change works. Six months after signing, your finance team finds that credit notes for reverse-charge invoices drop the reverse-charge wording, that a returned SEPA debit is visible only at the payment provider, and that the accounting export nets fees against revenue. None of it showed up in the demo, because nobody asked.

This article is a requirements list for buying billing software when you're a B2B SaaS company in the EU selling to customers in several member states. It's grouped by area, and each requirement comes with a way to test it in a demo or sandbox instead of taking the vendor's word for it. How such a system should be built internally is covered in our post on subscription billing architecture for the EU. This one is about what to demand from a vendor.

Must, should, could: weight the list before the first demo

Write down your knock-out criteria before the first call. A SaaS company with 30 business customers in Germany doesn't need OSS return data. A self-service product selling to consumers across the EU needs it from the first sale. The list below marks what's usually a must for a typical European B2B SaaS business. Adjust it to yours before the vendor starts steering the conversation.

Tax: place of supply, reverse charge, OSS

For electronically supplied services to a business in another member state, the customer usually accounts for the VAT under reverse charge. The invoice must say so, and the sale goes on your EC Sales List. For consumers, the place of supply is where the customer lives (Article 58 of the EU VAT Directive) once the EU-wide €10,000 threshold for such cross-border sales has been exceeded in the previous or current calendar year. You then charge the customer's country's VAT, usually declared through OSS. Your software therefore has to know customer type, country and evidence before the invoice exists.

Requirement Priority How to test it
VAT IDs are checked against VIES; result and timestamp are stored Must Enter an invalid number. Does the system charge domestic VAT, and can you retrieve the check later?
Reverse-charge wording appears on invoices and credit notes Must Create a credit note for a reverse-charge invoice and check the PDF
The tax decision is stored per invoice with its reason Must Ask: where do I see why invoice X was zero-rated?
VAT rates for all member states, with effective dates Must for B2C Simulate a rate change in one country on a given date
OSS return data per country and quarter, including credit notes Must for B2C Ask for a quarter's export including a credit note relating to the previous quarter
Location evidence for consumers Must for B2C What is stored, and what happens when two pieces of evidence conflict?

One detail that's often missing: for OSS, foreign-currency amounts are converted at the ECB rate for the last day of the quarter. A system that uses the invoice-date rate instead hands you return data you'll have to recalculate.

Invoices and e-invoicing

Germany has required every business to be able to receive e-invoices since 1 January 2025. Paper and other formats remain allowed for issuing until the end of 2026, and until the end of 2027 for issuers with prior-year turnover up to €800,000 and for EDI. From 2028, e-invoices are mandatory for domestic B2B in Germany. Under ViDA, e-invoicing becomes mandatory EU-wide for cross-border B2B from 1 July 2030. Software you buy today has to produce structured invoices.

Requirement Priority How to test it
XRechnung and ZUGFeRD to EN 16931, or Peppol BIS for other markets Must Generate a test invoice and run it through the KoSIT validator
Sequential invoice numbers without gaps around cancellations Must Delete a draft and check whether a number is lost
Finalised invoices can't be edited Must Try to change a paid invoice through the API
Corrections as cancellation or credit note referencing the original Must Issue a partial credit note against an invoice
Service period per line Should Check a usage line billed for the previous month
Delivery via Peppol Could, depending on your customer base Ask whether an access point is connected or has to be

Payments: SEPA, returned debits, dunning

Recurring B2B invoices in Germany and several neighbouring markets are often paid by SEPA direct debit. Under a SEPA Core debit the payer can reclaim an authorised payment for eight weeks, and up to 13 months if there was no valid mandate. So an invoice isn't finally paid just because the collection went through. The SEPA B2B scheme has no eight-week refund right.

Requirement Priority How to test it
Mandate management with creditor identifier and mandate reference Must Create a mandate and find the reference on the invoice
Pre-notification before collection Must Where is the notice period set, and is the notification logged?
A returned debit reopens the receivable, with its reason code Must Simulate a return in test mode and check the invoice status
SEPA Core and SEPA B2B Should Ask how B2B mandates are captured
Retry rules per return reason Should Have them show the difference between insufficient funds and a revoked mandate
Dunning levels with statutory late-payment interest and fees Should Generate a reminder for an overdue B2B invoice
Access suspension only after a defined dunning level Should Ask which event tells your product

Accounting, data and integration

Software is only as good as what reaches your accountant. For a German entity that nearly always means DATEV.

Requirement Priority How to test it
DATEV export with document number, tax key or automatic account, VAT ID Must for German entities Request a sample month and have your tax adviser review it
Payments and fees as separate postings Must Look for a clearing account in the sample export
Retention of eight years from year end in Germany, deletion only afterwards Must Ask how data is exported and kept after the contract ends
Idempotent API for usage events and invoices Must for usage pricing Send the same event twice
Signed webhooks with retries Should Take your webhook endpoint down for an hour
IFRS 15 revenue schedules Should Create an annual contract with a set-up fee and check the schedule
Data stored in the EU, data processing agreement Must Request the agreement and the list of sub-processors

On data residency, also check where backups and support access sit, not just primary storage.

The test case every vendor must walk through

Feature lists invite a yes. A test case doesn't. Give every vendor the same scenario and have them run it in a sandbox:

  1. A business customer in France with a valid VAT ID, annual plan with 20 seats, billed monthly by SEPA direct debit.
  2. On the 12th of month two, the customer goes to 25 seats.
  3. The debit for month three comes back with reason "mandate revoked".
  4. The customer gets a credit note for part of month three.
  5. Export the quarter in DATEV format.

Afterwards you need answers to these questions. Do all invoices and the credit note carry the reverse-charge wording? How is the upgrade prorated, and can you see the logic? Is the receivable open again after the returned debit, and was no automatic retry fired at a revoked mandate? Does the credit note reference the original invoice? Do invoices, credit note and payments net off in the export?

A vendor who can show this in an hour has most of your list covered. A vendor who calls it "a project" doesn't have it as standard. Kontier handles the product catalogue, usage, EU tax logic, SEPA collection and accounting exports in one system; the European billing page sets out the scope. If you bill on usage, add the evaluation criteria for usage-based billing software to the list.

Not tax or legal advice. This post describes the law and common practice in general terms. For your own case, ask your tax adviser. As of:

Book a demo

A technical demo: 15 minutes with an engineer on your pricing model and tax setup.

How we handle your details: privacy policy.

Prefer email? contact@frontieralgorithmics.com

Message Kontier

Write to us right here. We reply by email, usually within one business day.

How we handle your details: privacy policy.

Personal invitation · 30 days

Try Kontier for 30 days, with a personal invite

We set up a trial account for you and send the invite personally. No credit card, the trial ends on its own.

Your invite arrives within 48 hours at the address you enter, sent by a person, not a script.

Separate from the public 14-day trial, which starts with a card on the pricing page.