The template is where invoice trust is won or lost.
Most WooCommerce PDF invoice plugins can output a document. The harder revenue problem is whether that document contains the fields EU B2B buyers and accounting teams expect before they approve payment or accept a download.
Lattice Invoices is being shaped around this practical workflow: collect invoice-ready checkout data, render it in clean PDF templates, attach the right file to emails, and keep customer downloads, proformas, final invoices, and credit notes consistent.
EU-ready invoice PDF checklist
What each PDF template section should do
| Section | Fields to include | Template note |
|---|---|---|
| Header | Seller legal name, logo, VAT number, company registration, contact email | Avoid making the logo the only identity element; finance teams need legal data. |
| Buyer block | Company name, VAT/BTW number, billing country, PO/reference | Collect this before checkout payment, not after the order is already placed. |
| Invoice metadata | Invoice number, order number, invoice date, due date, payment method | Do not rely on WooCommerce order IDs as formal invoice numbers. |
| Line items | Product, quantity, subtotal, VAT rate, VAT amount, discounts | Digital products and subscriptions need especially clear tax treatment. |
| Footer | Reverse-charge text, bank details, refund/credit-note references, support link | This is where manual templates often miss EU compliance wording. |
Where generic PDF templates break
EU B2B buyer needs reverse-charge wording
Problem: A generic PDF invoice shows totals but no VAT/BTW number or reverse-charge sentence, so finance rejects it.
Lattice path: Render VAT metadata, buyer country, and reverse-charge wording from checkout fields into the PDF template automatically.
Bank-transfer buyers need payment terms
Problem: The WooCommerce order email says 'on hold', but the PDF does not show Net 14/30, IBAN, due date, or payment reference.
Lattice path: Treat the PDF as a payment request/proforma first, then produce a final invoice once paid if your accounting workflow requires it.
Refunds need matching credit-note templates
Problem: Refund emails are sent, but customers cannot download a clean credit note that references the original invoice number.
Lattice path: Keep invoice and credit-note template fields consistent so My Account downloads and email attachments remain traceable.
Early-access offer: €49 invoice-template workflow review
Send your current invoice PDF, checkout fields, payment methods, and refund process. Lattice will use that to prioritize the PDF-template workflow and tell you which fields should be collected before checkout.
Send my PDF template requirementsFAQ
What should a WooCommerce invoice PDF template include for EU VAT?
At minimum: seller legal details, buyer company/VAT fields, sequential invoice number, invoice date, VAT rates, VAT totals, reverse-charge wording when relevant, payment method, due date for bank transfer, and clear links to refunds or credit notes.
Can I use the WooCommerce order ID as the invoice number?
Many stores start there, but EU accounting workflows usually need a separate sequential invoice-number series plus credit-note numbering. A dedicated invoice workflow makes gaps, refunds, and proformas easier to audit.
Do bank-transfer orders need a different PDF template?
They often need extra fields: bank details, payment reference, payment terms, due date, proforma/payment-request wording, and a clear final-invoice step after payment. Card-paid consumer invoices can usually be simpler.
How does Lattice Invoices help with invoice PDF templates?
The early-access direction is focused on invoice-ready checkout fields, EU VAT metadata, proformas, final invoice PDFs, credit notes, customer downloads, email attachments, due dates, and bank-transfer invoice workflows for WooCommerce.