A decade ago, an invoice was an invoice: a document with your details, the client's details, and an amount. In 2026, what counts as a valid invoice depends heavily on where you and your customer are. The United States still treats invoices as ordinary business records, the UK and EU attach strict content rules to VAT invoices, and Saudi Arabia has moved to full e-invoicing, where invoices are structured electronic documents cleared through or reported to the tax authority itself. If you bill across borders, or you are a business inside one of these systems, here is what actually applies this year.
United States: No Federal Invoice Law, But Real Record-Keeping Duties
The US has no federal statute dictating what an invoice must contain, and no VAT system. An invoice is a commercial document between you and your customer, so the "requirements" are practical: identify both parties, number the invoice uniquely, date it, itemize the goods or services with amounts, state the total and the payment terms. Where obligations do exist, they come from the edges of the system. Sales tax is a state and local matter, and if you are required to collect it, showing it as a separate line is standard practice and required in many states. The IRS expects you to keep records that support your reported income, generally for at least three years and longer in some situations, and invoices are a core part of that trail. Clients who pay you $600 or more in a year for services will typically report it on a 1099-NEC, so your invoices should match the name and taxpayer details you gave on your W-9.
E-invoicing in the US remains voluntary. A business-to-business exchange network exists and adoption is growing, but no mandate requires structured invoices, which makes the US the lightest-touch jurisdiction on this list.
United Kingdom: HMRC VAT Invoice Rules
If you are not VAT-registered, UK invoicing looks much like the US: a clear, numbered, dated commercial document. Once you are VAT-registered, HMRC prescribes the content of a full VAT invoice, and the fields stop being optional.
- A unique, sequential invoice number.
- Your business name, address, and VAT registration number.
- The invoice date and, if different, the time of supply (tax point).
- The customer's name and address.
- A description of the goods or services, with quantity and unit price for each.
- The rate of VAT and the amount payable excluding VAT for each item.
- The total VAT amount and, where amounts are in a foreign currency, the VAT in sterling.
For retail supplies up to 250 pounds including VAT, a simplified VAT invoice with fewer fields is permitted. UK VAT-registered businesses also live under Making Tax Digital, meaning VAT records and returns flow through compatible software, and from April 2026 Making Tax Digital extends to income tax for sole traders and landlords with qualifying income over 50,000 pounds, which pulls even unregistered freelancers toward digital record-keeping. The UK has consulted on broader e-invoicing but, unlike the EU and Saudi Arabia, has no general B2B e-invoicing mandate in force in 2026.
European Union: VAT Invoice Content Plus a Rising Tide of E-Invoicing Mandates
The EU VAT Directive sets the baseline content for VAT invoices across all member states, and it is the strictest content list so far: sequential invoice number, supplier and customer VAT identification numbers where applicable, full names and addresses of both parties, date of issue and date of supply if different, description and quantity of goods or services, taxable amount per rate, the VAT rate and amount, and explicit references for special cases such as reverse charge or exemptions. Member states may allow simplified invoices for small amounts, typically under 100 euros.
The bigger 2026 story is the shift from paper and PDF to structured e-invoices. Italy has required domestic e-invoicing through its national platform since 2019. Germany has required businesses to be able to receive structured e-invoices since January 2025, with issuing obligations phasing in afterward. Belgium made structured B2B e-invoices mandatory from January 2026, and Poland's national KSeF system reaches mandatory status for businesses in 2026 as well. France follows with obligations beginning in September 2026, starting with the requirement for all businesses to be able to receive e-invoices. Above the national mandates sits the EU's ViDA (VAT in the Digital Age) package, which commits the bloc to structured e-invoicing and digital reporting for cross-border transactions by 2030. The practical takeaway for a small business selling into the EU: a PDF is still fine in many situations today, but the direction is one-way, and every year another market requires structured formats.
Saudi Arabia: ZATCA E-Invoicing, Fully Enforced in 2026
Saudi Arabia has gone further than any market on this list. Under the Zakat, Tax and Customs Authority (ZATCA), all VAT-registered businesses in the Kingdom must issue electronic invoices; handwritten invoices and unstructured documents like plain Word or scanned PDFs do not qualify. The program, known as FATOORA, arrived in two phases.
Phase 1: Generation
Since December 2021, invoices must be generated electronically through a compliant e-invoicing system, with required fields including a QR code on simplified invoices. This phase changed how invoices are created but did not yet connect businesses to ZATCA's systems.
Phase 2: Integration, Rolled Out in Waves
Phase 2 requires businesses to integrate their invoicing systems directly with ZATCA's platform, generating invoices in a prescribed XML format with a cryptographic stamp and a unique identifier. Rather than a single deadline, ZATCA has enrolled taxpayers in waves based on annual revenue, starting with the largest businesses in January 2023 and working down. The waves announced through mid-2026 reach essentially all VAT-registered businesses: Wave 24 covers businesses with annual VAT-liable revenue above 375,000 riyals, the VAT registration threshold itself, with an integration deadline of June 30, 2026. In other words, as of July 2026, integration is no longer something coming for Saudi businesses; enforcement is active, and operating outside the system is a compliance failure, not a delay.
Standard vs. Simplified Invoices
ZATCA distinguishes two invoice types with different flows. Standard tax invoices, used for B2B and B2G transactions, go through real-time clearance: the invoice is submitted to ZATCA and cryptographically cleared before it is shared with the buyer. Simplified tax invoices, used for B2C sales, are issued to the customer at the point of sale with a QR code and must be reported to ZATCA within 24 hours of issuance. If you sell to Saudi businesses from abroad you are not inside this system, but your Saudi customers' accounting departments are, which is why they may ask for specific invoice details that feed their own compliance.
Penalties
ZATCA pairs the mandate with enforcement. Fines for failing to issue e-invoices can start around 5,000 riyals, and penalties escalate for repeated violations such as continued failure to integrate. ZATCA has periodically favored warnings and grace periods for first offenses, but the framework is real and audits happen.
The Fields That Are Required Everywhere
Strip away the jurisdiction-specific rules and a stable core remains, which is worth internalizing because it satisfies the overlap of every regime above: a unique sequential invoice number, the issue date, the legal names and addresses of both supplier and customer, tax identification numbers where either party has them, an itemized description of goods or services with quantities and unit prices, the taxable amount and tax per rate where tax applies, the total, and the currency. An invoice built to that standard is valid in the US by default, satisfies the content layer of UK and EU VAT rules once registration numbers are added, and maps directly onto the data fields that e-invoicing systems like ZATCA's require in structured form.
What This Means for Freelancers and Small Businesses
If you are a US or UK freelancer billing domestic clients, the bar in 2026 remains a clear, complete, numbered invoice, with VAT fields if you are registered. If you sell into the EU, expect structured e-invoicing requirements to reach you market by market, and prefer tools that can output compliant formats rather than only PDFs. If you operate in Saudi Arabia, e-invoicing is not optional at any business size above the VAT threshold, and your invoicing tool must be part of a ZATCA-compliant setup. Wherever you are, the common core never changes: unique sequential numbers, both parties identified, itemized lines, correct tax treatment, and records you can produce years later.
For everyday billing, a tool like InvoiceFold's free invoice generator at invoicefold.com/free-invoice-generator covers the universal fields correctly, including tax lines, sequential numbering, and clean itemization, which is the foundation every jurisdiction builds on. If you bill in a niche, templates such as invoice-templates/consultant or invoice-templates/contractor structure those line items the way clients and auditors expect to read them.
Key Takeaways
- The US has no invoice content law; sales tax rules and IRS record-keeping create the real obligations.
- UK VAT invoices have prescribed fields, with simplified invoices allowed up to 250 pounds, and Making Tax Digital expands in April 2026.
- EU VAT invoice content is harmonized, and national e-invoicing mandates (Italy, Germany, Belgium, Poland, France) are converging toward ViDA's 2030 requirements.
- Saudi Arabia's ZATCA Phase 2 waves through mid-2026 cover essentially all VAT-registered businesses, with Wave 24 (revenue above SAR 375,000) due by June 30, 2026, and enforcement active.
- ZATCA fines can start around SAR 5,000 for failing to issue e-invoices and escalate for repeat violations.
Compliance sounds abstract until an invoice is rejected or a deduction is disallowed. Learn the rules of the markets you bill, use tooling that gets the fields right by default, and the paperwork will stay boring, which is exactly what paperwork should be.