Who is this for?
EU and non-EU transactions, reverse charge, e-invoicing and evidence.
Topics
Reverse charge is common for cross-border B2B services but is not automatic. Business evidence, the service category, place-of-supply rule, fixed establishments and invoice wording must align at the tax point.
For EU B2B services, the place-of-supply rule drives the outcome, not the billing address alone. Keep business-status evidence, check exceptions and make the invoice, recapitulative reporting and accounting entry consistent.
An exempt intra-Community supply requires more than two EU addresses. Actual movement, customer status, VAT number, transport evidence, invoice and reporting must form one consistent evidence chain.
“Outside the EU” is not one VAT rule. Goods and services, business or consumer status, use and enjoyment, export evidence and potential local registrations must be assessed separately.
A non-EU supplier invoice may cover imported goods, imported services or a local supply. Customs evidence, recipient, place of supply, tax debtor and deduction must be documented separately.
An invoice may use one currency while VAT reporting requires another. Jurisdiction, tax point, official rate source, rounding and evidence determine the conversion, not a convenient current market rate.
A business invoice must combine the legal minimum with transaction-specific data needed by the buyer, tax reporting and the e-invoice profile. PDF, structured data and accounting entry should tell the same story.
A VAT number is not universal proof for a tax outcome. The number used, business status, establishment, place of supply and the country where reporting is due must be considered together.
SaaS, software development, licences and consulting may use similar commercial language but the VAT result depends on the actual supply, customer status and place-of-supply rule. Product labels are not tax evidence.
B2C services are not always taxed where the supplier is established. Service type, customer location, evidence, thresholds and OSS can move the tax point to the consumer’s country.
An intra-Community acquisition links the supplier invoice, movement of goods, acquisition VAT and potential deduction. A missing or incorrect supplier tax line should not be hidden by an isolated accounting entry.
Format, profile and transport channel are separate decisions. A syntactically valid XML file may still fail if the recipient profile, mandatory data or network rules do not match.
Not every software-related supply is the same electronic service. Automation, human intervention, licence model, customer status and place of supply drive reverse-charge or OSS consequences.
E-commerce VAT is not determined by the storefront. Seller, possible deemed-supplier platform, stock, dispatch, consignment value, customer status and OSS/IOSS registration must be resolved per fulfilment model.
Retention is more than saving a PDF. Original format, readability, integrity, structured data, tax decision, corrections, access history and the applicable period should remain linked and reproducible.