EU VAT & Invoice Compliance Guides

Table of Contents

⚖️ Professional Tax Disclaimer

Last Updated: November 14, 2025

This article provides general information about EU VAT compliance and invoice requirements and should not be considered legal, tax, or financial advice. VAT regulations are complex and subject to change. EU member state interpretations may vary based on your specific circumstances.

Always consult with a qualified tax advisor or accountant before making compliance decisions. Incorrect VAT treatment can result in compliance issues, penalties, audits, and unnecessary costs.

3AM SaaS OÜ provides invoice automation software and is not responsible for your VAT compliance decisions.

If you sell digital services, physical goods, or subscriptions to customers in the European Union, you face a complex web of VAT (Value Added Tax) compliance requirements that vary by country, business type, and transaction value. Payment processors like Stripe, PayPal, and Shopify provide excellent transaction data, but their raw CSV exports are not legally valid invoices under EU law.

This creates a critical compliance gap: you have the transaction data, but you don't have the legally required documentation to prove those transactions to tax authorities. Manual invoice creation is time-consuming, error-prone, and doesn't scale. CSV2Invoice bridges this gap by automatically transforming your payment processor CSV files into fully compliant, audit-ready PDF invoices.

TL;DR - EU Compliance Made Simple

  • Sequential Numbering Required: EU law mandates gap-free, chronological invoice numbers
  • Four VAT Schemes: OSS, IOSS, Reverse Charge, and standard VAT have different rules
  • Platform CSVs Are Not Invoices: Transaction logs lack legal formatting and required fields
  • Retention Requirements: Keep invoices for 4-10 years depending on country
  • 200+ Platforms Supported: Transform any CSV into compliant invoices automatically

Why EU Invoice Compliance Matters

The European Union has some of the strictest invoice and VAT compliance requirements in the world. Unlike the United States where invoice formatting is largely unregulated, EU member states require specific data points, legal text, and structural formatting for every B2B and B2C transaction.

The Core Problem: Payment processors are built for US markets where receipts and transaction summaries are sufficient. Their CSV exports contain the raw data, but they don't format it according to EU legal requirements. This leaves EU businesses in a difficult position: they have proof of payment, but not proof that meets tax authority standards.

What Makes an Invoice "EU Compliant"?

A compliant EU invoice must include:

  • Sequential Numbering: Unique, gap-free, chronological invoice numbers (not random transaction IDs)
  • Supplier Details: Your company name, address, VAT number (if registered), and registration number
  • Customer Details: Customer name, address, and VAT number (for B2B transactions)
  • Invoice Date and Due Date: Clear payment terms and timing
  • Itemized Products/Services: Description, quantity, unit price, and total
  • VAT Breakdown: VAT rate, VAT amount, net amount, and gross amount
  • Payment Method: How the transaction was settled
  • Currency: Clear currency denomination
  • Legal Notation: Appropriate VAT scheme text (e.g., "VAT Reverse Charge" or "OSS VAT included")

Payment processor CSVs contain most of this data, but in unstructured formats with inconsistent field names. CSV2Invoice solves this by guiding you through a one-time field mapping process, then automatically applying that mapping to every future CSV upload.

The Four Compliance Pillars

EU VAT compliance for cross-border sales revolves around four distinct mechanisms, each designed for specific business scenarios. Understanding which applies to your transactions is crucial for proper invoice generation.

Quick Decision Tree: Which Scheme Do You Need?

  1. Selling digital services to EU consumers? → Use OSS (One Stop Shop)
  2. Importing physical goods under €150 to EU? → Use IOSS (Import One Stop Shop)
  3. Selling to EU businesses with VAT numbers? → Use Reverse Charge
  4. Any EU sales? → Use Sequential Numbering (mandatory for all)

Most businesses selling across borders will use multiple schemes simultaneously. For example, a SaaS company might use OSS for consumer sales, Reverse Charge for business sales, and Sequential Numbering for all invoices. CSV2Invoice handles this complexity automatically by detecting which scheme applies based on your field mapping.

Explore Comprehensive VAT Compliance Guides

Select your VAT scheme to access detailed compliance guides for 200+ payment platforms:

OSS Compliance

One Stop Shop

For: B2C digital services across EU

Filing: Quarterly VAT returns

Threshold: €10,000 per country

  • ✓ SaaS & subscription businesses
  • ✓ Digital products & courses
  • ✓ Single EU registration
View All OSS Guides (213 Platforms) →

IOSS Compliance

Import One Stop Shop

For: Imported goods under €150

Filing: Monthly VAT returns

Threshold: €150 per consignment

  • ✓ E-commerce shipments to EU
  • ✓ Eliminates customs delays
  • ✓ VAT at point of sale
View All IOSS Guides (213 Platforms) →

Reverse Charge

B2B Mechanism

For: B2B cross-border sales

Filing: Standard VAT return

Threshold: Valid customer VAT ID

  • ✓ 0% VAT on invoice
  • ✓ Customer self-accounts VAT
  • ✓ VIES validation required
View All Reverse Charge Guides (213 Platforms) →

Sequential Numbering

Universal Requirement

For: All EU invoices (mandatory)

Filing: Every invoice

Threshold: No exceptions

  • ✓ Gap-free numbering
  • ✓ Chronological order
  • ✓ Audit trail compliance
View All Sequential Numbering Guides (213 Platforms) →

OSS (One Stop Shop) Compliance

The One Stop Shop (OSS) scheme simplifies VAT reporting for businesses selling digital services to consumers across the EU. Instead of registering for VAT in every EU country where you have customers, OSS allows you to register once in your home country and report all EU sales through a single quarterly VAT return.

Who Needs OSS?

  • SaaS companies selling subscriptions to EU consumers
  • Digital product creators (courses, ebooks, software downloads)
  • Online service providers (consulting, freelancing platforms)
  • Any B2C digital service provider with customers across multiple EU countries

OSS Invoice Requirements

OSS invoices must clearly indicate:

  • The customer's country of consumption
  • The applicable VAT rate for that country (ranging from 17% to 27%)
  • The VAT amount calculated at the customer's country rate
  • A notation indicating the sale was made under the OSS scheme

The €10,000 Threshold: If your total B2C sales to a single EU country remain under €10,000 per year, you can use your home country VAT rate instead. Once you exceed this threshold in any country, you must use that country's VAT rate. OSS registration simplifies this complexity significantly.

Platform-Specific OSS Guides

We've created detailed guides for transforming platform CSV files into OSS-compliant invoices:

IOSS (Import One Stop Shop) Compliance

The Import One Stop Shop (IOSS) scheme was introduced in July 2021 to simplify VAT collection on low-value goods (under €150) imported into the EU from non-EU countries. IOSS allows sellers to collect VAT at the point of sale, eliminating customs VAT collection and speeding up delivery.

Who Needs IOSS?

  • E-commerce sellers shipping physical goods from outside the EU
  • Marketplaces facilitating sales of imported goods under €150
  • Fulfillment services handling cross-border shipments to EU customers
  • Any seller wanting to avoid customs delays for low-value consignments

IOSS Invoice Requirements

IOSS invoices must include:

  • Your IOSS VAT identification number (format: IM + country code + identifier)
  • Customer's destination country within the EU
  • Total value under the €150 threshold
  • VAT collected at the customer's country rate
  • Clear notation that VAT was collected under IOSS

Critical Note: IOSS only applies to goods valued at €150 or less. Goods above this threshold must go through standard customs procedures with VAT collected at import. Accurate value declaration on IOSS invoices is essential for customs clearance.

Reverse Charge Mechanism

The Reverse Charge mechanism is a cornerstone of B2B VAT compliance within the EU. When you sell to a business customer in another EU country, and that customer has a valid VAT number, you charge 0% VAT and shift the VAT accounting responsibility to the customer. This prevents double taxation and simplifies cross-border B2B transactions.

When to Use Reverse Charge

Reverse Charge applies when all of the following conditions are met:

  • Your customer is a business (not a consumer)
  • Your customer has a valid VAT number in their EU country
  • The transaction is cross-border (you and the customer are in different EU countries)
  • You have verified the customer's VAT number through VIES (VAT Information Exchange System)

Reverse Charge Invoice Requirements

Reverse Charge invoices must clearly show:

  • Your VAT number and the customer's VAT number
  • 0% VAT rate applied to the transaction
  • The exact legal text: "VAT reverse charge applies" or "Reverse charge - Article 196 of Council Directive 2006/112/EC"
  • Net amount (which is also the gross amount since VAT is 0%)

Critical Compliance Point: You must retain proof that you verified the customer's VAT number. VIES validation records should be kept alongside invoices. If a VAT number is invalid, you must charge standard VAT rates instead of applying Reverse Charge.

Common Reverse Charge Mistakes

  • Using transaction IDs as invoice numbers: Not compliant - must use sequential numbering
  • Missing the "Reverse Charge" notation: Tax authorities may reject the invoice
  • Not verifying VAT numbers: You bear liability if the VAT number is invalid
  • Applying Reverse Charge to B2C sales: Only valid for B2B transactions

Sequential Invoice Numbering

Sequential invoice numbering is the most fundamental—and most commonly violated—compliance requirement in EU invoicing. Every EU member state requires invoices to have unique, gap-free, chronological invoice numbers. This applies to all transactions, regardless of VAT scheme.

What Makes Numbering "Sequential"?

Sequential numbering means:

  • Unique: No two invoices can have the same number
  • Gap-Free: Numbers must be consecutive with no skipped numbers
  • Chronological: Newer invoices have higher numbers than older ones
  • Predictable: The numbering system follows a clear, logical pattern

Why Payment Processor IDs Don't Qualify

Payment platforms like Stripe, PayPal, and Square assign transaction IDs that seem unique, but they fail EU sequential numbering requirements in critical ways:

  • Random or Hash-Based: IDs like "ch_3NHxRa2eZvKYlo2C1234" are not chronological
  • Gaps in Sequence: Refunds, failed transactions, and testing create gaps in the number series
  • Multiple Numbering Systems: Charges, subscriptions, and invoices have separate ID formats
  • Not Human-Readable: Tax auditors expect simple, readable invoice numbers

Acceptable Numbering Formats

EU tax authorities accept various sequential formats:

  • Simple Sequential: 0001, 0002, 0003... (most common)
  • Year-Based: 2025-0001, 2025-0002, 2025-0003...
  • Month-Based: 2025-01-001, 2025-01-002, 2025-02-001...
  • Prefix-Based: INV-0001, INV-0002, INV-0003...

All formats must maintain the core requirement: consecutive, gap-free numbering within each series. If you start a new series (e.g., new year, new legal entity), this must be clearly documented in your accounting records.

Penalties for Non-Sequential Numbering

Using non-compliant invoice numbers can result in:

  • Rejected VAT Deductions: Your customers may lose their VAT deduction rights
  • Administrative Penalties: Fines starting at €50 per violation in most countries
  • Audit Complications: Tax authorities may flag your entire invoice ledger
  • Increased Audit Frequency: Non-compliance triggers closer scrutiny
  • Loss of Good Standing: May affect VAT registration and refund processing

Platform-Specific Compliance Guides

Every payment processor, e-commerce platform, and SaaS billing tool exports CSV data in a slightly different format. Field names, date formats, currency notations, and data structure vary significantly across platforms. This makes generic invoice generators ineffective for EU compliance.

CSV2Invoice solves this through intelligent field mapping that adapts to your specific platform's CSV structure. Once you map your fields during the initial setup, the system remembers your configuration for all future uploads.

Supported Platform Categories

Payment Processors

Stripe, PayPal, Square, Braintree, Adyen, Authorize.Net, and 50+ more

View Stripe compliance guides →

E-Commerce Platforms

Shopify, WooCommerce, BigCommerce, Magento, PrestaShop, and 40+ more

View Shopify compliance guides →

SaaS Billing & Subscriptions

Paddle, Chargebee, Recurly, Zuora, FastSpring, and 30+ more

View Paddle compliance guides →

Course Platforms & Digital Products

Kajabi, Teachable, Podia, Gumroad, Lemon Squeezy, and 25+ more

Freelance & Service Marketplaces

Upwork, Fiverr, Toptal, PeoplePerHour, and 15+ more

Don't see your platform? If your platform can export transaction data to CSV format, CSV2Invoice can transform it into compliant invoices. The field mapping system is flexible enough to handle any CSV structure.

Compliance Risks and Penalties

EU tax authorities take invoice compliance seriously. Non-compliant invoices aren't just an administrative nuisance—they can result in significant financial penalties, rejected VAT deductions, and increased audit scrutiny.

Common Compliance Violations

Violation Risk Level Typical Penalty
Non-sequential invoice numbers High €50-€5,000 per audit
Missing VAT notation (OSS/IOSS/Reverse Charge) High Rejected deductions + penalties
Using payment processor receipts as invoices Critical €500-€50,000 depending on severity
Missing customer VAT number (B2B) Medium Reverse Charge rejected, standard VAT owed
Incorrect VAT rates (wrong country rate) High VAT difference + interest + penalties
Missing invoice retention (lost invoices) Critical Transactions deemed invalid, VAT reclaimed

Country-Specific Penalties

Penalties vary significantly by EU member state:

  • Germany (GoBD): Up to €50,000 for systematic non-compliance with digital bookkeeping standards
  • France: 5% of invoice amount for missing invoices, up to €15,000 per offense
  • Italy: 90-180% of VAT amount for missing or incorrect e-invoices
  • Spain: €150-€6,000 per violation depending on severity
  • Netherlands: €5,200 maximum fine for bookkeeping violations

Beyond direct penalties, non-compliance can trigger more frequent audits, delayed VAT refunds, and damaged business relationships when your customers can't claim VAT deductions on your invoices.

Frequently Asked Questions

What is EU VAT compliance for invoices?

EU VAT compliance for invoices means your invoices meet all legal requirements set by EU tax authorities, including sequential numbering, proper VAT calculations, customer identification, and appropriate VAT scheme notation (OSS, IOSS, or Reverse Charge). Non-compliant invoices can result in penalties, rejected deductions, and audit complications.

Do I need to use sequential invoice numbering in the EU?

Yes, sequential invoice numbering is legally required across all EU member states. Invoice numbers must be unique, chronological, and gap-free. Using payment processor transaction IDs (like Stripe charges or PayPal transaction IDs) is not compliant and can result in penalties during tax audits.

What is the difference between OSS and IOSS?

OSS (One Stop Shop) is for B2C digital services and allows you to report VAT in one country for all EU sales. IOSS (Import One Stop Shop) is for imported goods valued under €150, allowing you to collect VAT at checkout and avoid customs delays. Both simplify EU VAT reporting but apply to different business types.

When should I use Reverse Charge on invoices?

Use Reverse Charge for B2B transactions within the EU when your customer has a valid VAT number. In this case, you charge 0% VAT and add the notation "VAT reverse charge applies" to the invoice. The customer is responsible for accounting for VAT in their country. This prevents double taxation across EU borders.

Can CSV files from payment processors serve as compliant invoices?

No, raw CSV exports from payment processors like Stripe, PayPal, or Shopify are not legally compliant invoices. They lack sequential numbering, proper VAT calculations, mandatory legal text, and audit trail formatting. CSV2Invoice transforms these CSV files into fully compliant PDF invoices that meet EU tax authority requirements.

How long must I retain invoices in the EU?

Invoice retention periods vary by EU country, ranging from 4 years (Spain) to 10 years (Germany for accounting books, Italy, Czech Republic, Portugal). Most countries require 6-7 years. Invoices must be stored in an unalterable digital format and remain accessible for tax audits throughout the retention period.

What happens if my invoices are not EU compliant?

Non-compliant invoices can result in: rejected VAT deductions for your customers, penalties ranging from €50 to €50,000 depending on severity and country, tax audit complications, inability to prove transactions, and potential criminal liability in cases of intentional tax evasion. Compliance is not optional.

Does CSV2Invoice work with my payment processor?

CSV2Invoice supports 200+ payment processors, e-commerce platforms, and SaaS billing tools including Stripe, PayPal, Shopify, WooCommerce, Paddle, Square, Chargebee, and many more. If your platform can export transaction data to CSV format, CSV2Invoice can transform it into compliant invoices.

Ready to Master Your EU Compliance?

Transform your payment processor CSV files into fully compliant, audit-ready PDF invoices in minutes. One-time field mapping, permanent automation.

Start Generating Compliant Invoices →