The retention problem appears after the first audit question
A WooCommerce store can look compliant while orders are fresh. The problems appear months later: the invoice template changed, VAT settings changed, the customer updated billing details, a refund happened, or the accountant asks for the original PDF and evidence behind a reverse-charge order.
Before buying an invoice plugin, verify that it retains the data finance actually needs — not just the ability to generate a new PDF from the current order state.
Invoice data retention checklist
Final invoice PDF
Retain: Invoice number, order ID, billing details, VAT treatment, payment status, PDF file URL, and sent/download timestamps.
Risk if missing: If a PDF is regenerated later with different data, finance loses the original document trail.
VAT / BTW evidence
Retain: VAT number, validation result, billing country, reverse-charge reason, exemption reason, tax rate, and customer type.
Risk if missing: A zero-VAT invoice without stored evidence creates accountant follow-up and audit risk.
Credit notes and refunds
Retain: Credit-note number, original invoice link, refunded line items, VAT correction, refund date, and PDF delivery status.
Risk if missing: Editing or deleting the original invoice hides the real refund history.
BACS / proforma workflow
Retain: Payment request date, due date, bank-transfer reference, proforma PDF, payment reconciliation date, and final invoice issue date.
Risk if missing: Issuing final invoices before payment can create unpaid invoice clutter and messy month-end exports.
Customer access
Retain: Protected My Account download links, email attachment status, customer resend events, and PDF version references.
Risk if missing: If customers cannot retrieve old invoices, support becomes the archive system.
Questions to ask before choosing a plugin
- ✓Can the plugin preserve original invoice PDFs instead of only regenerating them from current order data?
- ✓Does it store VAT/BTW number evidence and reverse-charge wording with the order and invoice?
- ✓Are credit notes separate documents with their own numbers and export rows?
- ✓Can BACS/proforma workflows avoid final invoice creation until payment is reconciled?
- ✓Do customer downloads, email attachments, and accounting exports point to the same retained document trail?
- ✓Can the store owner export invoice metadata without asking a developer to query the database?
Early-access offer: €49 invoice retention review
Send your current invoice plugin, payment methods, VAT countries, refund workflow, and accounting software. Lattice will map what invoice data should be retained, where PDFs should be exposed, and which retention gaps are blocking a safe EU VAT workflow.
Send my retention workflowFAQ
How long should WooCommerce invoice data be retained?
Retention periods depend on local accounting rules, but EU VAT stores usually need a reliable multi-year archive for invoice numbers, PDFs, VAT evidence, credit notes, payment status, and accounting exports. The practical requirement is that documents remain reproducible and traceable without changing old invoice data.
Is regenerating WooCommerce invoice PDFs enough?
Regeneration is risky if customer details, tax settings, templates, or plugins changed after the invoice was issued. A safer workflow stores the issued PDF reference, the invoice metadata, and the event history that explains why the invoice or credit note exists.
What invoice retention features should a WooCommerce EU VAT plugin include?
Look for sequential invoice numbers, stored VAT evidence, reverse-charge wording, retained PDFs, credit-note links, customer download access, audit trail, BACS/proforma timing, and accountant-ready exports.
Where does Lattice Invoices fit?
Lattice Invoices is the early-access WooCommerce EU invoicing product path for stores that need VAT-ready invoice data capture, retained PDF delivery, credit notes, BACS/proforma control, customer downloads, audit trail, and accounting handoff.