E-Invoicing Rules for Freelancers Billing EU Clients

Most pages ranking for this topic cover a single country. This one is for the developer with clients in several. It covers what a structured e-invoice is, a country-by-country timeline, how cross-border invoices fit in, and what a solo freelancer can actually do. This is general information, not tax or legal advice. Dates below come from the sources linked in each section as checked on 2026-11-04, and national rules change. Confirm anything you rely on with the tax authority or an accountant in the client's country.

What counts as an e-invoice, and is a PDF one?

A PDF is not an e-invoice in the regulatory sense. A PDF is an image of an invoice. A person can read it, but accounting software has to guess where the total, the VAT line and the invoice number are.

A structured e-invoice carries the same information as data fields in a machine-readable format, so the client's system can import it with no retyping. One explainer describes it as an invoice "designed for software to read," and notes that in Germany and France the common formats are ZUGFeRD and Factur-X, both built on the EN 16931 European standard. A hybrid file looks like a normal PDF but has the structured data embedded inside it. Belgium's national page points to the Peppol BIS Billing 3.0 format, also EN 16931 compliant.

Here is how the formats compare:

Format	What it is	Readable by software?	Counts as a structured e-invoice?
Plain PDF from an invoice generator	A picture of the invoice	No, it needs OCR or retyping	No
Word or Excel file	Editable document	No	No
Hybrid PDF (ZUGFeRD, Factur-X)	PDF with XML data embedded	Yes	Yes, when it follows EN 16931
Pure XML (XRechnung and similar)	Data file, no visual layout	Yes	Yes
Peppol BIS Billing 3.0	EN 16931 invoice sent over the Peppol network	Yes	Yes

The honest summary about tooling: a typical invoice generator, including billable.dev, produces a PDF. That PDF is a correct invoice for clients and countries that still accept PDFs, which is a lot of them for now. It is not a structured e-invoice, and it should not be described as one.

Which EU countries require e-invoicing, and from when?

The mandates differ in start date, in whether they cover receiving or issuing, and in who is in scope. This table reflects what the sources listed under it state. Where a source did not confirm a detail, the cell says so.

Country	Receive obligation	Issue obligation	Who is in scope
Germany	From 1 January 2025	1 January 2027 for businesses with prior-year turnover above EUR 800,000; 1 January 2028 for all other businesses	Transactions between domestic businesses
France	From 1 September 2026, all businesses established in France, micro-entrepreneurs included	1 September 2026 for large and mid-sized companies; 1 September 2027 for micro-companies and SMEs	Issuing obligation described as covering domestic B2B sales
Spain	Not separately stated in the source checked	B2B e-invoicing: 6 October 2027 for businesses with prior-year turnover above EUR 8 million; 6 October 2028 for everyone else. Separate Verifactu invoicing-software rules: 1 July 2027 for self-employed, 1 January 2027 for companies	Invoices between businesses and professionals; self-employed are covered
Belgium	In force from 1 January 2026	In force from 1 January 2026	Belgian VAT taxpayers on local B2B VAT transactions; cross-border supplies excluded
Poland (KSeF)	Not separately stated in the source checked	1 February 2026 for large businesses (2024 gross sales above PLN 200 million); 1 April 2026 for all other companies	Scope details not confirmed in the source checked

Sources for the table: the European Commission's eInvoicing page for Belgium and its Germany page, plus country explainers from QuickBilling (France), Renn (Spain) and TaxCoach (Poland). I could not reach the primary national tax authority pages for France, Spain and Poland when writing, so treat those rows as second-hand and check them before acting.

A few details worth knowing about each row:

Germany. The Commission page describes the rule as covering transactions between domestic businesses, and says other formats such as PDF require the recipient's consent during the transition. It also says an ordinary email address is enough to receive an e-invoice; no special mailbox is needed. The Commission page I read is an archived 2024 revision, so check the current German Finance Ministry guidance for the latest transition detail.

France. One source states that micro-entrepreneurs are not exempt from the receive obligation, and that they may still send PDFs to clients who accept them until their issuing date of 1 September 2027. Invoices are exchanged through an accredited platform (a PDP) or the state portal (the PPF). E-reporting runs alongside e-invoicing on a schedule based on company size, which that source does not date.

Spain. The Spanish picture has two layers: the B2B e-invoicing law and Verifactu, which governs invoicing software. The same source says a postponement of Verifactu to October 2028 has been announced but was not yet published in the official gazette, so check the official bulletin before relying on either date.

Belgium. The Commission page says Belgian B2B e-invoicing became mandatory on 1 January 2026, using Peppol as the primary format and transmission method, and that e-reporting is planned for 2028.

Poland. A source notes that microbusinesses with monthly gross sales of PLN 10,000 or less may be exempt during the April to December 2026 transition, and that penalty provisions start in 2027. Confirm both against official guidance.

Does the mandate apply to cross-border freelance invoices?

For the national mandates in the table, mostly not yet. The sources describe them as domestic: Germany's covers transactions between domestic businesses, France's issuing obligation covers domestic B2B sales, and Belgium's page says explicitly that intra-community supplies and services taxed in another EU country are outside the e-invoicing scope.

That is the current picture, not the permanent one. The EU's VAT in the Digital Age package (ViDA) is the cross-border piece. According to the European Commission's ViDA page, from its entry into force on 14 April 2025 member states can introduce mandatory e-invoicing under specific conditions, and digital reporting requirements affect cross-border B2B transactions from 1 July 2030. A freelancer in one EU country billing a company in another should expect structured invoicing to arrive on that timeline, not on a 2026 deadline.

Two things matter here regardless of the mandates:

• Receiving is the first obligation. Your EU clients that must be able to receive e-invoices are already in that position in Germany and are about to be in France. A client that has rebuilt its accounts-payable process around structured invoices may ask you for one, whatever the law technically requires of you.
• VAT treatment is a separate question. Whether you charge VAT or apply the reverse charge does not change with the invoice format. See invoicing EU clients: VAT and the reverse charge for that.

What does a non-EU developer billing EU clients need to do?

The sources I checked describe the German, French and Belgian rules in terms of domestic or locally established businesses. None of them states that a developer outside the EU invoicing an EU client is required to issue a structured e-invoice. I did not find a source that settles the question for every country, so do not read this section as a guarantee. The practical steps, in order:

1. Ask the client. Send one line before your first invoice: "Does your accounts-payable team need invoices in a structured format such as Peppol, ZUGFeRD or Factur-X, or is a PDF by email fine?" Most small clients will answer in one sentence.
2. Keep the invoice data clean. Every structured format needs the same fields: your legal name and address, your tax ID, the client's legal name, address and VAT number, a unique invoice number, issue date, line items, currency and totals. A clean PDF built from the same fields converts later. A sloppy one does not. The international invoicing checklist lists the fields foreign clients tend to need.
3. Use consistent invoice numbers and the currency code on every amount. Software matching depends on predictable data. Numbering advice is in the invoice numbering post.
4. Get paid through a rail that fits. E-invoicing does not change how money moves. If you are weighing payout options for EU clients, see Payoneer vs Wise for freelancers.
5. If you are an EU-resident freelancer, treat your own country's date as the one that matters. A German freelancer faces the 2027 or 2028 issuing date for domestic B2B invoices depending on prior-year turnover. A French micro-entrepreneur needs to be able to receive from 1 September 2026 and issue from 1 September 2027. Check with your national tax office or accountant.

How does a solo freelancer issue a structured e-invoice?

There are four realistic routes, from least to most effort:

• Use a platform that produces the format. Accounting and invoicing products in France and Germany are adding Factur-X, ZUGFeRD or Peppol output as the deadlines approach. This is the path most solo freelancers will take, and the cost is a subscription.
• Use an accredited service provider. France routes invoices through accredited platforms called PDPs, and Belgium uses the Peppol network, which freelancers typically reach through an access-point provider rather than directly.
• Convert a PDF-based workflow. Some services take invoice data and produce a hybrid PDF. You still need the underlying fields to be correct.
• Ask the client for what they accept. In the transition years, many clients accept a PDF, and some German rules explicitly allow other formats with the recipient's consent.

The tool question is where it is easy to overpromise, so to be plain about it: billable.dev generates a PDF and a JSON export of your invoice data in the browser. It does not create ZUGFeRD, Factur-X, XRechnung or Peppol files. Where a PDF is still accepted, it does the job. Where a structured invoice is required, you need one of the routes above.

FAQ

Is a PDF invoice still valid in Germany?

For now, in many cases yes, during the transition. The Commission page says that from 1 January 2025 e-invoicing becomes the standard, paper invoices may still be sent for two years, and other formats such as PDF require the recipient's consent. Businesses with prior-year turnover above EUR 800,000 must issue structured e-invoices from 1 January 2027, and all remaining businesses from 1 January 2028. That page is an archived revision, so check current German Finance Ministry guidance.

Does France's mandate apply to micro-entrepreneurs?

Yes for receiving. A source says all businesses established in France, micro-entrepreneurs included, must be able to receive structured e-invoices from 1 September 2026. For issuing, it gives micro-companies and SMEs a start date of 1 September 2027, with PDFs still sendable to clients who accept them until then. Ask your accountant which e-reporting rules apply to your regime.

What is Peppol?

Peppol is a network and set of formats for exchanging structured e-invoices between businesses. The Commission page on Belgium says Peppol BIS Billing 3.0 is the primary format and transmission method for Belgian B2B e-invoicing. You normally connect through an access-point provider rather than building anything yourself.

Do US freelancers need to send e-invoices to EU clients?

The sources I checked describe the national mandates as covering domestic or locally established businesses, and none says a US freelancer must issue a structured e-invoice to an EU client. That is not a guarantee for every country, and the ViDA rules phase in cross-border reporting from 1 July 2030. The practical move is to ask each client what their accounts-payable team accepts, and keep your invoice data complete and consistent.

Next step

If your EU client still accepts PDFs, generate the invoice free in EUR at billable.dev. Your saved invoices stay in your browser, and the JSON export gives you the structured data for your own records.