See how teams replace 4-5 tools with one platform and save $37K per 500 users.
Stay VAT-compliant across EU, UK, and beyond. Learn which invoice fields are legally required, which trigger rejections, and how to automate your template so no VAT detail ever gets missed.
Tyler Hayes11 August 202610 min read1,214 viewsTL;DR: Most guides on how to create a VAT invoice template hand you a blank layout and leave the compliance work to you. This one builds the template from the legal requirements outward, covering EU, UK, and APAC rules, the specific fields that trigger rejections, and how IT company owners can automate the whole process so no VAT field ever gets missed or miscalculated.
Before you design a single cell in your template, you need to know which fields are legally required — not just conventional. Getting this wrong means your invoices fail VAT reclaim checks, trigger audits, or get rejected by enterprise clients whose AP teams validate against local tax law.
EU VAT Directive 2006/112/EC Article 226 sets the compliance floor for all 27 member states. A full VAT invoice must include:
A unique sequential invoice number
The invoice date and the tax point date (if different)
Your full business name, address, and VAT registration number
The customer's name, address, and VAT number (for B2B transactions)
A description of the goods or services supplied
The quantity and unit price, net of VAT
The VAT rate applied and the total VAT amount charged
The gross total payable
UK HMRC VAT Notice 700 mirrors most of these fields post-Brexit, with one practical difference: UK invoices require your GB VAT registration number, not an EU VAT number. Simplified invoices (under £250 gross) can omit the customer's details and show a VAT-inclusive total instead.
These aren't formatting preferences — they are the VAT invoice mandatory fields that determine whether your customer can reclaim input tax. A missing VAT number or an absent tax point date is enough to invalidate the claim.
If you are working from a blank invoice template structure, map every mandatory field against this list before adding any branding or optional line items. The next section extends this into a four-region checklist covering EU, UK, US, and APAC requirements.
Not every jurisdiction uses the same compliance floor. Before you build or audit any template, map your required fields to the regions where you actually invoice.
EU (VAT Directive 2006/112/EC, Article 226)
EU member states follow a shared mandatory field list, though individual states can add requirements on top. Every full VAT invoice must include: sequential invoice number, issue date, supplier name and address, supplier VAT registration number, customer name and address, description of goods or services, quantity, unit price, taxable amount, VAT rate applied, and total VAT charged. If you supply to a VAT-registered buyer in another member state, you also need the customer's VAT number and a reference to the zero-rate or reverse-charge rule applied.
UK (HMRC VAT Notice 700)
Post-Brexit, the UK runs its own VAT regime. A full UK VAT invoice requires the same core fields as the EU list, plus your VAT registration number prefixed "GB." Simplified invoices (for supplies under £250 including VAT) can drop the customer name and address, but you still need the supplier VAT number, the tax point date, and a description sufficient to identify the supply. Retailers issuing high volumes often use simplified invoices, but B2B clients almost always need the full version.
US (state-level sales tax only)
The US has no federal VAT equivalent. Sales tax is administered at the state level, and requirements vary: some states require the seller's sales tax permit number on the invoice, others only require the tax amount and rate. If you invoice across multiple states, review each state's rules individually. A blank invoice template structure built for EU compliance will need state-specific tax fields added before it works in the US.
APAC (mixed regimes)
Australia's GST invoices (called tax invoices) require the supplier's ABN, a statement that the document is a tax invoice, and GST amount shown separately. Singapore's GST invoices follow a similar structure. Japan's Qualified Invoice System, introduced in October 2023, added a new registration number requirement for all invoices.
For industry-specific invoice template requirements — construction, professional services, or SaaS — layer these jurisdiction rules on top of any sector-specific line items your contracts require.
Start with your format choice, because it shapes everything downstream. A spreadsheet works for low volume; a purpose-built template in your invoicing tool is better once you're billing more than 10 clients a month. Either way, the structure is the same.
Here's the sequence to follow:
Lock in your header block. Add your business name, address, VAT registration number, and contact details. For EU invoices, EU VAT Directive 2006/112/EC Article 226 requires the supplier's full name and address as a mandatory field — not optional, not conditional.
Add the recipient block. Customer name, address, and VAT number if they're VAT-registered. For B2B transactions inside the EU, the customer's VAT number is required to apply zero-rate treatment correctly.
Assign a unique sequential invoice number. This is a legal requirement in most jurisdictions. Leave a placeholder field that auto-increments — never reuse or skip numbers.
Set your date fields. You need the invoice date and, separately, the supply date (the date goods or services were actually delivered). These can differ, and tax authorities treat them as distinct fields.
Build the line-item block. Each line needs a description, quantity, unit price, applicable VAT rate, and VAT amount. Grouping items under a single VAT rate is acceptable; mixing rates on one line is not. Review industry-specific invoice template requirements if your sector has additional field rules.
Add totals. Net amount, total VAT broken out by rate, and gross amount payable. This is where most DIY templates fail — they show a final number without separating the VAT component.
Test before you send. Run one draft invoice against the VAT invoice mandatory fields checklist from the previous section. Check it against a blank invoice template structure to confirm nothing is missing.
That seven-step sequence is how to create a VAT invoice template that holds up under audit, not just one that looks right at a glance.
Four formatting rules trip up most DIY templates, and all four are legally required under EU VAT invoice rules in most jurisdictions.
Sequential invoice numbering must follow an unbroken, unique sequence. Gaps in numbering — caused by deleted drafts or reused numbers — can trigger audits in Germany, France, and the Netherlands. The sequence can include letters and numbers (INV-2025-001), but it must be continuous and traceable.
Issue date and tax point date are separate fields under EU VAT Directive 2006/112/EC Article 226. Most templates show only one. The tax point date determines which VAT period the transaction falls into — getting it wrong misaligns your filing.
VAT rate and VAT amount must appear as distinct line items, not merged into a total. If you supply goods at multiple rates (say, 20% standard and 5% reduced in the UK), each rate needs its own subtotal line.
Currency display should include the ISO code (GBP, EUR, USD) alongside the symbol, especially on cross-border invoices. Symbol-only display is ambiguous when the buyer operates in a different currency.
Inzo enforces these fields automatically, so numbering gaps and missing tax point dates don't reach the client. For industry-specific invoice template requirements, the rules can tighten further.
Five errors show up repeatedly when IT company owners build VAT templates by hand.
Missing the supplier's VAT registration number. EU VAT Directive 2006/112/EC Article 226 lists this as a mandatory field, not optional. Add it to your header block.
Omitting the customer's VAT number on B2B invoices. For cross-border EU transactions, the buyer's VAT ID is required. Most DIY templates skip it entirely.
Displaying the wrong VAT rate for the jurisdiction. A template hardcoded to 20% UK VAT will produce non-compliant invoices the moment you bill a German client at 19%. Your VAT invoice mandatory fields should reference the applicable rate dynamically, not as a static label.
No sequential invoice numbering. A gap in your number sequence flags an audit risk in most EU member states. If you're still numbering manually, check what are the best invoice template designs for Word for structured starting points.
Missing the supply date when it differs from the invoice date. Both dates are legally required under Article 226 when they don't match.
Run your existing template against this VAT invoice compliance checklist before your next billing cycle. Each fix above takes under five minutes to apply.
Manual VAT invoice creation means someone on your team is checking fields before every send. That works until you're billing 20+ clients across different jurisdictions, and one missed VAT number or wrong tax rate creates a compliance problem that takes longer to fix than the invoice was worth.
Automated VAT invoice creation removes that dependency. The logic lives in the template itself: tax rates calculate from the client's jurisdiction, mandatory fields under EU VAT Directive Article 226 populate automatically, and the PDF generates in a consistent format every time. No manual field-checking before send.
Inzo handles this at the template level. When a project closes in Taro or a contract signs through Revo, Inzo can trigger invoice creation automatically, with tax fields already mapped to the client record. The invoice isn't a blank form someone fills in — it's a pre-configured output with the right fields enforced.
For IT companies billing across the EU and UK, that distinction matters. A tool that generates invoices isn't the same as one that enforces which fields are required by region. If you want a full breakdown of what to look for before committing to any automation setup, the invoice automation features IT companies actually need covers the criteria worth checking.
Run three checks before your template goes live.
Jurisdiction spot-check: Pull the mandatory field list for each region you invoice into. EU templates must satisfy Article 226 of VAT Directive 2006/112/EC — sequential invoice number, supplier VAT number, net amount, tax rate, and VAT amount are all required. UK full VAT invoices follow HMRC VAT Notice 700, which adds the customer's VAT number for B2B transactions. Cross each field against your template output, not just your template design.
Calculation test: Enter a multi-line order with mixed VAT rates and confirm the per-line and total figures match manual arithmetic.
PDF render check: Export a real PDF and verify no fields truncate. Your blank invoice template structure affects how fields display under real data — test with long company names and multi-word line items before deploying.
Building a VAT-compliant invoice template is a one-time investment that pays dividends every time an invoice goes out. Once your template locks in the mandatory fields — supplier details, customer VAT number, sequential numbering, separate tax point date, and VAT broken out by rate — compliance stops being a manual review cycle and becomes automatic. The real efficiency gain comes when you wire this template into your invoicing workflow, so every invoice enforces the checklist at creation, not after the fact. Start by auditing your current template against the four-region checklist in this article, then move it into a tool that automates the calculations and numbering. Inzo's template builder does exactly this — it lets you set the compliance rules once at setup, then ensures every invoice that leaves your system meets them without a second pass. What region do you invoice most heavily, and are you currently catching compliance gaps before or after your customer's AP team rejects them?
Start with your header block (business name, VAT number, address), add a recipient block with customer details, assign sequential numbering, set separate invoice and supply dates, build line items with VAT rates, and add totals broken out by rate. Test against the mandatory fields checklist before sending.
EU VAT Directive 2006/112/EC requires: unique sequential number, issue date, tax point date, supplier name/address/VAT number, customer name/address/VAT number, description of goods/services, quantity, unit price, VAT rate, VAT amount, and gross total. Missing any one field can invalidate VAT reclaims.
Both require the same core fields, but UK invoices must show your VAT number prefixed 'GB' post-Brexit. UK simplified invoices under £250 can omit customer details; EU simplified invoices have stricter rules. The tax point date requirement is identical in both.
Free templates often miss jurisdiction-specific fields or don't auto-enforce sequential numbering and VAT calculations. They work for low volume, but once you invoice 10+ clients monthly, gaps in compliance become audit risk. A purpose-built invoicing tool is safer.
Add your logo, color scheme, and custom fields in the header and footer areas. Never modify the mandatory compliance fields — supplier VAT number, customer VAT number, sequential numbering, tax point date, or VAT breakdown. Branding goes around compliance, not through it.
Your customer cannot reclaim input tax, triggering audit risk for them and potential rejection by their AP team. Missing VAT numbers, tax point dates, or sequential numbering are the most common failures. The invoice becomes legally invalid for VAT purposes.
Expert advice, key updates, and practical guides on team productivity, project management, and the future of work. Written by operators who run the business.
One email, every Tuesday. Tactical playbooks for B2B operators. No fluff, no filler.
