What an invoice needs in the US, UK, and EU

Quick Comparison

The US: start with records, contracts, customers, and state tax display

The reviewed official sources did not establish a universal US federal template for ordinary private B2B invoices. The federal layer is mostly about keeping records that support tax returns and business positions. The IRS says businesses should keep records such as receipts, purchases, expenses, assets, employment taxes, and other supporting documents; IRS Publication 583 treats invoices and receipts as supporting records, not as a national invoice format.

That absence is narrow. A US invoice can still be shaped by contract terms, customer procurement rules, state or local tax rules, regulated sectors, or public-sector requirements. For example, covered federal contracts can prescribe invoice content under the Federal Acquisition Regulation prompt payment clause, but that is a customer and contract context, not a general private B2B rule.

For most US freelancers, the practical baseline is a clean business invoice:

• seller legal or business name and contact information;
• customer name and billing address;
• invoice date and stable invoice number;
• description of work, quantity, hours, units, or deliverables;
• rate or unit price, discounts, fees, reimbursed expenses, subtotal, tax where relevant, and total;
• due date, payment terms, payment instructions, purchase order, project, or contract reference;
• exemption, resale, direct-pay, or tax-included notes where relevant.

US sales tax is not VAT

Do not copy VAT logic into US invoices. US sales and use tax is state and local, and some states use different models. Arizona's transaction privilege tax is imposed on the vendor privilege, and the Arizona DOR explains tax factoring when that tax is not separately stated on an invoice or contract. New Mexico's gross receipts tax is also not the same thing as customer VAT; its gross-receipts-tax overview says any gross-receipts-tax pass-through must be separately stated on the invoice.

The reviewed official sources support some high-level state display examples. Texas says sellers must separately state sales tax or clearly indicate that tax is included in the sales price in its sales-tax collection FAQ. Washington says retail sales tax must be separately stated from the selling price on sales slips, contracts, or invoices in its DOR tax topic. Florida guidance similarly says sales tax is shown separately unless a tax-included method is disclosed in the Florida DOR business owner's guide.

Other state examples are useful only with caveats. Alaska has no statewide sales tax, but local sales tax can apply according to the Alaska sales-tax information page. Delaware has no traditional state sales tax, but the Delaware gross receipts tax FAQ explains a seller gross-receipts-tax layer. Montana's local resort tax, New Hampshire's meals and rooms tax, and Oregon's sales-tax guidance show why local, lodging, vehicle, resort, or sector caveats matter.

For states not discussed here, check current official sources instead of inferring a rule from these examples.

The UK: ordinary invoices, VAT invoices, NI goods, records, and policy watchlists

UK invoices start with business identity. Sole traders using a business name, partnerships, companies, and LLPs have different disclosure rules under the Companies Act 2006 business-name provisions and the 2015 trading disclosure regulations. GOV.UK's invoice guidance gives a practical checklist for invoices, including the invoice number, seller and customer details, description, dates, amounts, VAT where applicable, and total.

VAT changes the invoice. The UK VAT Regulations 1995, regulation 14 sets full VAT invoice content, including sequential number, tax point, issue date, supplier name/address/VAT registration number, customer details, supply description, VAT rate, taxable amount, total VAT in sterling, unit price, discount rate, and special references where applicable. HMRC's VAT guide and VAT record-keeping notice explain full, simplified, and modified invoice handling in practice.

Three UK distinctions matter:

• A non-VAT-registered business must not charge UK VAT; GOV.UK's charge, reclaim and record VAT guidance ties charging VAT to VAT registration.
• Zero-rated sales are taxable at 0%; exempt sales are not charged VAT. They should not be described as the same thing.
• Special VAT cases can change visible wording or fields. Reverse charge, domestic construction reverse charge, margin schemes, self-billing, credit/debit notes, continuous supplies, discounts, and foreign-currency VAT totals each need the right mode rather than a generic invoice.

Northern Ireland adds a goods-specific layer. HMRC VAT Notice 725 covers goods movements between Northern Ireland and EU Member States. In those cases, invoice fields and reporting can involve XI prefixes, EU customer VAT numbers, zero-rating or exemption references, EC Sales List, or Intrastat flags. This is not a general UK-wide change for every service invoice.

For retention, UK VAT records, including sales invoices, purchase invoices, credit/debit notes, and VAT account records, are generally retained for 6 years under VAT Notice 700/21. Electronic VAT invoices are currently allowed where the invoice content and authenticity, integrity, legibility, storage, access, and customer-agreement requirements are met; HMRC's electronic invoicing notice treats this current rule as broader than only structured data.

For e-invoicing, separate current law from announced policy. The Procurement Act 2023 section 67 is a current public-contract buyer duty to accept and process undisputed structured electronic invoices in covered contexts. It is not a universal supplier duty for all UK invoices. HMRC and DBT announced mandatory e-invoicing for VAT invoices from 2029 in the consultation response, and HMRC's 2026 transformation roadmap update says from April 2029. As of the 10 July 2026 review, no implementing legislation was identified, so treat April 2029 as announced future policy, not current law.

The EU: start with the VAT Directive, then check the Member State

For EU VAT, the baseline is the VAT Directive consolidated text. Articles 217 to 240 cover the invoice concept, issue, content, paper and electronic invoices, simplified invoices, and special cases; Articles 244 to 249 cover storage and access.

The full VAT invoice baseline includes issue date, sequential number, supplier and customer VAT IDs where required, party names and addresses, quantity and nature of goods or services, supply or payment date where different, taxable amount, VAT rate, VAT amount, and special mentions. Article 226 drives the core field list. Articles 220a, 226b, and 238 cover simplified invoices. Article 222 sets EU timing for some intra-EU goods and reverse-charge service cases, while other timing can be national.

EU VAT invoices can change visibly in common cases:

• exempt supplies need an exemption indication or legal reference;
• reverse-charge invoices need "Reverse charge" where the customer accounts for VAT;
• intra-EU goods can require customer VAT ID, exemption indication, and timing rules;
• self-billing requires prior agreement and acceptance procedure and the "Self-billing" mention;
• invoice amounts can be in any currency, but VAT payable or adjusted is in the national currency;
• Member States can add or release obligations in defined cases.

Business-to-consumer (B2C) is not one EU rule. The VAT Directive does not create a universal domestic B2C invoice duty. For Article 33(a) intra-Community distance sales, Union One Stop Shop can remove the invoice duty while adding 10-year electronic record duties; Import One Stop Shop and platform cases add their own record and liability layers.

EU e-invoicing has several layers

Current EU VAT law defines an electronic invoice broadly as required invoice information issued and received in any electronic format. That is not the same as a structured e-invoice. Article 233 requires authenticity, integrity, and readability from issue through storage, using business controls, audit trails, electronic signatures, EDI, or other methods.

EU public procurement is another layer. Directive 2014/55/EU requires Member States to ensure covered contracting authorities and entities receive and process compliant e-invoices; Implementing Decision 2017/1870 publishes EN 16931 and accepted syntaxes. This is a public-buyer receive/process rule. It does not create a universal EU supplier issue mandate for every B2B or B2C invoice.

ViDA is enacted EU law, but it is staged. The adopted package includes Directive (EU) 2025/516, Regulation (EU) 2025/517, and Implementing Regulation (EU) 2025/518. The key public takeaway is:

Member States still matter. Belgium's official e-invoicing portal says domestic B2B structured e-invoicing has applied since 1 January 2026 for covered VAT-taxable business transactions, and PDF/email is not sufficient for those covered cases. France's government e-invoicing page sets B2B e-invoicing and e-reporting phases from 2026 and 2027. Germany's BMF FAQ distinguishes structured e-invoices from "other invoices" such as PDFs and sets B2B transition periods. Poland's KSeF key-dates page sets 2026 phases. Spain's Royal Decree 238/2026 creates a B2B framework, but operative duties depend on a later ministerial order, so do not publish fixed operative dates without rechecking that order. Italy already has domestic e-invoicing through Agenzia Entrate's electronic invoicing system.

Those examples show the pattern: check the EU baseline, then the country, format, channel, customer type, and effective date.

Tax Display: VAT and US sales tax are different jobs

For VAT, the invoice is part of the tax evidence chain. If UK or EU VAT applies, a VAT invoice usually needs VAT IDs where required, taxable amount, VAT rate, VAT amount, and the right special wording for exemption, reverse charge, self-billing, margin schemes, or corrections. UK VAT totals must be shown in sterling where UK VAT is chargeable. In the EU, VAT payable or adjusted is shown in national currency even if the invoice also uses another currency.

For US sales tax, the invoice is often evidence that state or local tax was separately stated, included, exempt, or supported by customer documentation. Texas and Washington are good examples of separately stated or clearly disclosed tax treatment. But a US sales-tax line does not make the invoice a VAT invoice, and a seller permit does not automatically become an invoice-field requirement.

If you are unsure whether tax applies, do not solve that by adding a tax label. Taxability, nexus, VAT registration, exemptions, reverse charge, One Stop Shop, Import One Stop Shop, marketplace rules, and sector rules depend on facts outside the invoice document.

Retention and e-invoicing highlights

Use three labels:

• Current law: rules in force now, such as UK VAT record retention, current EU VAT invoice/storage rules, EU B2G receive/process obligations, and national systems already in force.
• Enacted future law: adopted legal instruments with future dates, such as ViDA's 2030 structured e-invoicing and digital-reporting rules for covered cross-border transactions, or national laws with future effective dates.
• Announced policy: official policy without identified implementing law, such as the UK's April 2029 VAT e-invoicing policy as checked on 10 July 2026.

For retention, keep the country profile visible. The UK baseline is generally 6 years for VAT records. EU Member States set their own retention periods and may require original form, storage location, online access, or authenticity/integrity data. The US is more records-driven: keep invoices and supporting documents long enough to support tax returns, state tax records, contract obligations, and disputes.

For e-invoicing, do not treat PDF, structured XML, Peppol, clearance platforms, and reporting as the same thing. A PDF can be acceptable in one setting and insufficient in another. Peppol is a network or channel, not a compliance guarantee; country systems such as SdI, KSeF, RO e-Factura, myDATA, SABIS, FE-AP, and eFaktura need fresh source checks and real connector support before product claims.

Before you choose fields

Work through this checklist before deciding what to put on the invoice:

1. Seller location: country, and US state or EU Member State if relevant.
2. Customer location and type: consumer, business, VAT taxable person, non-taxable legal person, public body, federal agency, exempt organization, platform, or marketplace.
3. Seller tax profile: no tax, US sales/use tax, gross receipts tax, general excise tax, transaction privilege tax, UK VAT, EU VAT, exempt, zero-rated, reverse charge, One Stop Shop, Import One Stop Shop, or user-managed.
4. Transaction type: goods or services, domestic or cross-border, intra-EU, Northern Ireland/EU goods, federal/public procurement, regulated sector, recurring supply, advance payment, correction, self-billing, or margin scheme.
5. Document mode: ordinary invoice, full VAT invoice, simplified invoice, modified retail VAT invoice, credit/debit/corrective note, self-billed invoice, pro forma, fiscal receipt, structured e-invoice, or official platform submission.
6. Effective date: current law first, enacted future law when the date arrives, announced policy only as a watchlist.

Before you send

Check the invoice itself:

1. Names and addresses identify the seller and customer.
2. Invoice number is unique and sequential if your tax regime requires it.
3. Issue date, supply date, due date, and payment terms are clear.
4. Line items describe the work or goods well enough for the customer, tax record, and contract.
5. Currency, subtotal, discounts, tax base, tax rate, tax amount, and total reconcile.
6. VAT or sales tax is shown only where the seller is allowed or required to charge it.
7. Special wording is present where needed: exemption, reverse charge, self-billing, margin scheme, tax included, zero-rated, or correction reference.
8. Public-sector or e-invoicing cases use the required structured format, portal, or network where current law requires it.
9. The invoice and source data can be retained, exported, and read later.
10. Anything uncertain is checked against current official sources or a professional adviser before sending.

Update policy

Invoice and e-invoicing rules are changing quickly. Recheck official sources before relying on this article for dated e-invoicing timelines, VAT policy, state sales-tax display, public procurement, or any country-specific compliance wording. The highest-refresh areas are UK VAT e-invoicing policy, EU ViDA implementation, Belgium, France, Germany, Poland, Spain, Italy, Latvia, Estonia, Slovakia, Slovenia, Croatia, Portugal, and Romania.

This article is maintained as a dated public synthesis of official sources. It is not legal, tax, accounting, or regulatory advice; it cannot determine your taxability, nexus, VAT registration, exemption, sourcing, rate, reporting, or sector obligations.