/

Invoice Compliance

What is Invoice Compliance?

Arnon Shimoni

Written by Arnon Shimoni

Written by Arnon Shimoni

Expert opinion

Invoice compliance means every invoice you issue is legally valid in the country where the supply is taxed: it contains the mandatory information, carries the right tax treatment and wording, is numbered and dated correctly, goes out within the deadline, in the required format, and is stored for as long as the law says.

At ten invoices a month a careful person does this by hand. At ten thousand invoices a month across six countries and three legal entities, the only way to be compliant is for the billing system to be compliant, because nobody is reading them before they go.

At a glance

Invoice compliance

Content

The mandatory items of Article 226 VAT Directive, or the national equivalent outside the EU

Tax treatment

Correct rate, exemption or reverse charge, with the prescribed wording and a validated customer VAT number

Numbering and dates

Unique sequential numbers, invoice date within the issuance deadline, supply period stated

Format

Structured e-invoice where mandated (Italy, Belgium, Poland, Romania, Hungary, Germany from 2027, France from 2026, all intra-EU B2B from 2030)

Corrections

Credit notes referencing the original. Never edits

Storage

7 to 10 years depending on country, with authenticity, integrity and legibility guaranteed

Cost of failure

Fines per invoice, customer's VAT deduction denied, invoices rejected and paid late

The seven things an invoice has to get right

1. Mandatory content. In the EU, Article 226 of the VAT Directive lists fifteen items for a full invoice and Article 226b five for a simplified invoice. Member States can't add VAT requirements beyond these, but they can and do require extra items under other laws: company registration numbers, share capital in France, the words "Invoice" in the national language. The EU invoice requirements page has the full list.

Invoice with PO number, supplier ID, custom fields and two VAT rates

Beyond the legal minimum: PO number, supplier ID, custom fields and a per-rate VAT breakdown, which is what the customer's accounts payable team actually checks.

2. Tax treatment. The right VAT rate for the product and country, the exemption reference where the supply is exempt, and the reverse charge wording with a validated customer VAT number where the customer accounts for the tax. Getting the rate wrong costs you the difference. Getting the reverse charge wrong without a valid VAT number costs you the whole VAT.

3. Identity. The correct legal entity on both sides. A group with entities in several countries has to invoice from the entity that made the supply, with that entity's VAT number, address and bank details, and bill the customer entity that actually contracted. A trading name is not a legal name.

4. Numbering and dates. A unique sequential invoice number assigned at finalisation, an issue date within the deadline, and the supply date or period when it differs from the issue date.

5. Format and channel. Where structured e-invoicing is mandatory, a PDF is not an invoice. The document has to be in the required syntax (EN 16931 UBL or CII, FatturaPA, KSeF, Factur-X and so on) and delivered through the required network (Peppol, SDI, KSeF, the French PA platforms), often with the tax authority receiving a copy or a report in real time. The e-invoicing page tracks the mandates.

6. Corrections. An issued invoice is never edited. Errors are fixed with a credit note that refers to the original, and if necessary a new invoice.

7. Storage. Articles 244 to 248 require you to store every invoice issued and received, for the national period (Belgium 10 years, Germany 8, Netherlands 7, France 10 commercial), with the authenticity of origin, integrity of content and legibility guaranteed throughout, and accessible to your tax authority on request.

Why this is hard at scale

Each of the seven is simple on its own. The difficulty is that they interact, they change, and they have to be right on every invoice without review.

  • The treatment is per invoice, not per customer. A customer's VAT number can be deregistered. A customer can move from Ireland to the US. A product can be reclassified from standard to reduced rate. The correct result has to be computed each time from current facts.

  • Rules change on fixed dates. Belgium's mandate started 1 January 2026, Germany's issuing obligation starts 1 January 2027, France phases in from 1 September 2026, the intra-EU rules change on 1 July 2030. A compliant invoice on 31 December can be non-compliant on 1 January with no change to the data.

  • Usage billing multiplies lines. A metered invoice has dozens of lines, each needing a description, quantity, unit price, net amount and rate. Line-level errors are invisible in a total.

  • Multiple entities mean multiple sequences, templates, currencies and tax authorities, and a group ERP that wants one consolidated feed.

What non-compliance costs

Three things go wrong, in order of how fast you notice.

The customer rejects the invoice. Enterprise accounts payable teams check for PO numbers, legal entity names and VAT numbers, and bounce anything that doesn't match. Each bounce resets payment terms. This is where invoice compliance turns into days sales outstanding and cash.

The customer's deduction is challenged. An invoice missing a mandatory item doesn't support the customer's input VAT claim. The tax authority challenges the customer, the customer comes back to you, and you issue a credit note and a corrected invoice months after the fact.

You are fined. Penalties are national and per invoice. Belgium's e-invoicing fines run €1,500, €3,000 and €5,000 for successive infractions. Italy and Hungary fine per document for late or missing e-invoice transmission. Several countries fine per missing mandatory item. At volume these compound.

Compliance as a system property

The teams that stay compliant at scale treat it as something the billing system guarantees rather than something finance checks. In practice that means:

  1. Tax treatment computed at invoice time from the billing entity, customer and product, with VAT numbers validated against VIES.

  2. Mandatory wording added automatically as a function of the treatment.

  3. Numbers and dates assigned at finalisation by rule, one series per entity.

  4. Finalised invoices immutable, with corrections only through linked credit notes.

  5. Structured e-invoice generation and transmission built into the invoice lifecycle, with the status from the network or tax authority tracked on the invoice.

  6. A review step (hold) for the invoices that need a human, without delaying the ones that don't.

  7. Every version of every document retained.

When those seven are properties of the system, compliance stops being a month-end task and becomes a configuration question when you enter a new country.

Where Solvimon fits

This is how Solvimon is built. Tax is computed per invoice from the billing entity's and customer's countries with VIES validation and automatic reverse-charge and exemption notes. Each billing entity has its own unbroken invoice number series, the invoice date follows a rule you set, and finalised invoices are immutable with credit notes as the only correction path. Structured e-invoices are generated and submitted through country mandates or the Avalara integration, with submission status on the invoice and a resubmit path for rejections. Solvimon powers invoicing for some of Europe's largest fintechs, where getting this wrong isn't an option. If compliance is the thing slowing down your expansion into new countries, talk to one of our experts.

FAQ

Is a PDF invoice compliant?

In countries without a structured e-invoicing mandate, yes, if it contains the mandatory items and the customer has agreed to receive invoices electronically. In Italy, Belgium, Poland, Romania, Hungary and, from 2027, Germany, a PDF is not a valid B2B invoice.

Which country's rules do I follow for a cross-border invoice?

The country where the supply is taxed, except for reverse-charge supplies by a non-established supplier, where your own country's rules apply. For B2B SaaS across the EU that means your own country's rules plus the reverse charge wording.

Can I be fined for an invoice the customer never complained about?

Yes. Compliance is checked by tax authorities in audits and, increasingly, in real time through e-invoicing platforms, not by customers.

Do I need a tax engine as well as a billing system?

You need correct rates and treatment per country. Whether that lives inside the billing system or in a connected tax engine is an architecture choice. What matters is that it's applied at invoice time, per invoice.

How long do I keep invoices?

The longest national period that applies to you. 10 years covers most of the EU.

This page was checked against the VAT Directive and national guidance in October 2026. It is a general explanation and doesn't replace advice from your tax adviser.

Related

SIGN UP TODAY

Ready to grow your revenue?

Start now. First $3M free for AI startups.

SIGN UP TODAY

Ready to grow your revenue?

Start now. First $3M free for AI startups.

SIGN UP TODAY

Ready to grow your revenue?

Start now. First $3M free for AI startups.

SIGN UP TODAY

Ready to grow your revenue?

Start now. First $3M free for AI startups.