Who is this for?
Multi-client validation, evidence and structured hand-off workflows.
Topics
Accounting-firm validation should separate formal errors, tax risks and uncertain extraction. Every finding needs evidence, severity, a correction path and an auditable approval decision.
Correction, cancellation and a customer-issued credit note are not interchangeable. The document must match the business event, reference the original and show the change in net, VAT and gross amounts.
An expense may be business-related while the document is insufficient for input-VAT recovery. Accounting acceptance, income-tax treatment, VAT deduction and evidence should therefore be assessed separately.
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.
Production automation separates reliable extraction, deterministic rules, labelled AI suggestions and human decisions. Every stage needs confidence, error codes, idempotency and a traceable hand-off.
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.
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.
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.
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.
The obligation to receive can start earlier or apply more broadly than the obligation to issue. Readiness means accepting, validating, routing and retaining structured invoice data, not merely opening an email attachment.
Issuing obligations depend on the jurisdiction, invoice date, B2B/B2G/B2C scope, company criteria and transitional rules. A PDF is not automatically a compliant structured e-invoice.
E-invoicing reforms usually contain several timelines. Receiving capability, structured issue, government reporting, company size and temporary relief must not be collapsed into one date.
Advance and final invoices must use one consistent contract and tax logic. Deposits, tax timing, prior invoice references and the remaining balance must not be duplicated or omitted.
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.
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.