In brief: the direct answer
The data that supports an intra-EU supply treatment, and the evidence to keep with the invoice. Intra-eu supplies and invoice data is clearest when approached through treatment supported by data. For intra-eu supplies and invoice data, the supply evidence on the record settles the outcome. For intra-eu supplies and invoice data, the supply evidence on the record absent means rejection. For intra-eu supplies and invoice data, the supply evidence on the record mapped wrongly means the wrong meaning. This guide keeps coming back to one check for intra-eu supplies and invoice data: keep supply evidence with the record.
The route stage of intra-eu supplies and invoice data is Route. At Route, the supply evidence on the record is what comes next. For intra-eu supplies and invoice data, a Route decision cannot be fixed later. For intra-eu supplies and invoice data, a Route decision cannot be fixed cheaply. Check the supply evidence on the record for intra-eu supplies and invoice data before going further.
The record at this stage
Trace the invoice as a record through intra-eu supplies and invoice data. At Route, the record for intra-eu supplies and invoice data holds the supply evidence on the record. Answer the supply evidence on the record for intra-eu supplies and invoice data supported by evidence. Then the rest of cross-border, currency and language gets easier. Then the rest of intra-eu supplies and invoice data gets easier to check.
Name the record before the system for intra-eu supplies and invoice data. Systems change, yet the supply evidence on the record for intra-eu supplies and invoice data stays. Providers change, yet the supply evidence on the record for intra-eu supplies and invoice data stays. Formats change, yet the supply evidence on the record for intra-eu supplies and invoice data stays. For intra-eu supplies and invoice data, ask which record a system produces. For intra-eu supplies and invoice data, ask which record a system accepts. For intra-eu supplies and invoice data, ask which status evidence it returns.
What the data must carry
The data that counts most for intra-eu supplies and invoice data is the supply evidence on the record. That is no slogan for intra-eu supplies and invoice data. It is the thing the next intra-eu supplies and invoice data check examines. If the supply evidence on the record for intra-eu supplies and invoice data is absent, expect rejection. If the supply evidence on the record for intra-eu supplies and invoice data is unclear, expect rejection. If the supply evidence on the record for intra-eu supplies and invoice data is badly formatted, expect rejection.
Check the supply evidence on the record as the receiver will read intra-eu supplies and invoice data. For intra-eu supplies and invoice data, screen correctness alone is not enough. For intra-eu supplies and invoice data, file correctness alone is not enough. For intra-eu supplies and invoice data, mapping correctness matters as well. Start with the mapping table for intra-eu supplies and invoice data at the start. Then use the receiver test for intra-eu supplies and invoice data next. Then use a sample invoice for intra-eu supplies and invoice data last.
Validation and evidence
For intra-eu supplies and invoice data, validation runs through three separate gates. Intra-eu supplies and invoice data the structure gate comes at the start. Intra-eu supplies and invoice data the business rule gate comes next. Intra-eu supplies and invoice data the receiver rule gate comes last. Each intra-eu supplies and invoice data gate produces its own failure message.
A intra-eu supplies and invoice data rejection must state its rule. A intra-eu supplies and invoice data rejection must state its field. A intra-eu supplies and invoice data rejection must state the value sent. A intra-eu supplies and invoice data rejection must state the value expected. Lacking those facts, a intra-eu supplies and invoice data rejection is only a delay. Send back a intra-eu supplies and invoice data rejection with that request attached.
The evidence for intra-eu supplies and invoice data is what survives afterwards. Keep the intra-eu supplies and invoice data invoice exactly as exchanged. Keep intra-eu supplies and invoice data status messages beside it. Keep any intra-eu supplies and invoice data correction attached to it. An auditor for intra-eu supplies and invoice data will request that set.
Where it breaks, and the check to make first
The usual intra-eu supplies and invoice data failure is simple. For intra-eu supplies and invoice data, keep supply evidence with the record was left out. For intra-eu supplies and invoice data, the receiver discovered the problem. For intra-eu supplies and invoice data, the sender now has to correct it. For intra-eu supplies and invoice data, the sender now has to resend it. For intra-eu supplies and invoice data, the sender now has to explain it.
An illustration, using round numbers only, for intra-eu supplies and invoice data: A seller sends 20 invoices for intra-eu supplies and invoice data. 1 fail on the supply evidence on the record for intra-eu supplies and invoice data. Checking the supply evidence on the record first for intra-eu supplies and invoice data takes minutes. A intra-eu supplies and invoice data receiver rejection takes days. Sometimes a intra-eu supplies and invoice data rejection can take a payment cycle. That is why intra-eu supplies and invoice data keeps repeating one check: keep supply evidence with the record.
What to verify before acting
Three checks come before acting on intra-eu supplies and invoice data, check three things at the start. First, the jurisdiction and transaction for intra-eu supplies and invoice data. First, the buyer and country for intra-eu supplies and invoice data. Next, European Commission: eInvoicing country factsheets for intra-eu supplies and invoice data today. Finally, the intra-eu supplies and invoice data buyer requirement set down in writing.
A guide on intra-eu supplies and invoice data sets out those questions. A guide on intra-eu supplies and invoice data will not settle a specific transaction. This guide on intra-eu supplies and invoice data offers general information, nothing more. This guide on intra-eu supplies and invoice data is no advice about one invoice. For one specific invoice about intra-eu supplies and invoice data, check European Commission: eInvoicing country factsheets. For one specific question about intra-eu supplies and invoice data, consult a qualified adviser.
How this guide is layered
Every guide on this site is read through the same twelve layers, in the order that fits its topic: obligation, data, format, network, validation, tax, accounting, lifecycle, evidence, direct intent, transaction, jurisdiction. The layers are a reading method, not a claim about any single system.
Evidence basis: Primary sources named in the sources section, checked 2026-10-27; country guides are dated research routes, not mandate calendars. Scope: General educational information only; no individual legal, tax, accounting or compliance advice; jurisdiction and transaction specific checks remain with the reader.
Related guides
- Cross-border, currency and language explained - Multi-country trade: tax identifiers, currency, language of the readable view, and routing across borders.
- Export supplies and invoice data - Export data, evidence and the invoice fields that support an export treatment.
- Exchange rates and rounding on an invoice - Rate source, rate date and rounding rule, stated on the record so totals reconcile.
Back to the pillar guide: Cross-border, currency and language explained.
In this topic
- Cross-border, currency and language explained
- Cross-border checklist before sending
- Cross-border disputes and corrections
- Currency on an invoice and in payment
- Exchange rates and rounding on an invoice
- Export supplies and invoice data
- Language of the readable view
- Multi-entity groups and invoicing
- Routing an invoice across borders
- Tax identifiers across borders
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- European Commission: eInvoicing country factsheets - Country-level research starting point
- OpenPeppol: Peppol BIS Billing 3.0 - Billing profile, information elements and validation