Invoicing used to be simple. You sent a PDF, the brand paid, you moved on. In 2026, that’s still mostly true — but the bar for what a “legal invoice” looks like is rising, especially in the EU.
If you’re a content creator based in Europe and you invoice brands, here’s what you actually need to know.
What every EU invoice must include
Regardless of your country, EU VAT Directive 2006/112/EC defines the minimum fields for a valid invoice:
- Your legal name (or business name if you’re a sole trader / company)
- Your address — full street, city, country
- Your VAT number — if you’re VAT-registered. If you’re below the threshold (varies by country), you can invoice without one, but note “VAT not applicable – Art. 293B CGI” or your country’s equivalent
- The buyer’s full name and address — the brand or agency you’re invoicing
- The buyer’s VAT number — required for B2B invoices where the buyer handles reverse charge
- Invoice number — sequential, no gaps
- Invoice date
- Description of services — “Sponsored YouTube video – Campaign: [name]” is fine
- Amount excl. VAT, VAT rate (or exempt reason), total incl. VAT
- Payment terms — e.g., “Net 30 days”
- Your bank details — IBAN + BIC if requesting SEPA transfer
That’s the baseline. Countries add requirements on top of this (Belgium requires a sequential invoice number starting from 1 per calendar year; France has specific rules for micro-entreprises).
Why Word documents are a liability
Most creators generate invoices in Word or Google Docs. Here’s what goes wrong:
Sequential numbers are manual. If you accidentally send two invoices with the same number, or skip a number, a tax auditor will notice. It’s the first thing they look at.
No audit trail. A PDF you generated and a PDF you edited both look identical. There’s no integrity protection.
No structured data. Your accountant has to retype every line item. Your brand’s AP team has to enter it manually. This is why brands sometimes pay late — your invoice landed in someone’s inbox and required manual processing.
What is UBL 2.1 and should you care?
UBL 2.1 (Universal Business Language) is an XML standard for electronic invoices. It’s the format behind the EU’s Peppol network — the B2B e-invoicing infrastructure that large companies and governments are increasingly requiring.
Peppol is the network layer. If a company says “send invoices via Peppol,” they mean: send a UBL 2.1 XML file through the Peppol routing network, so it lands directly in their accounting system without human intervention.
Do you need to care today? Probably not for most brand deals. Most brands still accept PDFs. But:
- EU member states are progressively mandating e-invoicing for B2B (France: mandatory from 2026 for large companies; Belgium planning 2026–2028 rollout)
- If you invoice large media companies, publishers, or agencies, they may start requiring structured invoices
- Having EU-compliant invoices from day one means you never have to retrofit
Belgium-specific: the micro-enterprise exemption
If you’re a Belgian creator operating as a freelancer (indépendant en personne physique) with annual revenue below €25,000, you benefit from the franchise TVA (BTW-vrijstelling). Your invoices must include:
“Régime particulier de franchise de la taxe — Article 56bis du Code TVA”
You do not charge TVA. But you still need all the other fields above.
Once you cross €25,000, you must register for TVA and start charging 21% on your services to Belgian clients (services to EU business clients in other countries typically use reverse charge — 0% on your invoice, buyer accounts for it).
France-specific: auto-entrepreneur
If you’re a French creator under the micro-entreprise regime, your invoices must include:
“TVA non applicable — article 293B du CGI”
You issue invoices without charging TVA until you exceed the threshold (€36,800 for services in 2026). Beyond that, you must transition to a normal VAT regime.
IBAN vs. other payment methods
PayPal, Stripe, and other payment processors are fine for small amounts, but for professional B2B invoicing, IBAN transfers are standard in Europe. Your invoice should include:
- IBAN
- BIC/SWIFT
- Account holder name (must match your legal name)
If you don’t have a business account, most banks (and neobanks like Qonto, Revolut Business, N26 Business) allow you to use your personal IBAN for freelance income — check with your accountant for your specific situation.
What Sponstra generates
When you create an invoice in Sponstra, you get two files:
PDF — formatted with all required fields (your legal info from Settings → Billing, the brand’s details from your CRM, sequential invoice number, VAT treatment, payment terms). On the free plan, the PDF has a small watermark; on Creator+, it’s clean.
UBL 2.1 XML — a structured file that meets EN 16931 (the European standard for e-invoicing). This is the file your accountant can import directly, and what you’d send through the Peppol network if needed.
Your billing info (legal name, address, VAT number, IBAN) is set once in Settings → Billing Info and auto-fills on every invoice.
The short checklist
Before you send your next invoice, verify:
- Your legal name and full address
- Buyer’s full name and address (not just “NordVPN” — the legal entity)
- Sequential invoice number
- Clear description of the service
- Amount HT + VAT rate (or exemption notice)
- Payment terms (Net 30 is standard)
- Your IBAN
Get this right once, save it as a template, and you’ll never have to think about it again.
Sponstra generates EU-compliant PDF + UBL 2.1 invoices automatically. Your billing details are saved once and applied to every deal.