Why VIES validation belongs in the invoice workflow
A simple VAT-number field can capture useful data, but it does not prove that the number was validated, which rule was applied, or why reverse-charge wording appeared on the invoice. That gap becomes painful during refunds, customer disputes, and accountant reviews.
Lattice Invoices is being positioned around that workflow gap: collect VAT data at checkout, preserve validation evidence, generate the right PDF state, and make the customer/accountant view consistent.
VIES validation readiness checklist
1. Capture VAT ID before payment, not after support tickets
The VAT/BTW number needs to be collected during checkout, normalized with the buyer country, stored on the order, and reused on the invoice PDF, credit note, customer download, and export row.
Buyer question: Can the plugin store the exact VAT ID and country pair used for invoice decisions?
2. Treat VIES as evidence, not a single brittle checkout dependency
VIES can be slow or unavailable. A sales-ready workflow needs timeout handling, manual review states, and clear logs instead of silently blocking good B2B buyers or accepting every failed lookup.
Buyer question: What happens when VIES is unavailable, times out, or returns an ambiguous result?
3. Link validation state to reverse-charge wording
A valid EU B2B VAT ID usually changes the invoice wording and VAT treatment. The plugin should make that decision traceable instead of relying on a hidden checkout field.
Buyer question: Does a valid VAT ID automatically feed reverse-charge invoice text and VAT metadata?
4. Preserve evidence when refunds or corrections happen
If a VAT number was validated for the original invoice, the linked credit note or correction invoice should retain the same evidence trail and explain any manual override.
Buyer question: Do credit notes and corrected invoices reference the original VAT validation result?
5. Make accountant exports match customer PDFs
The accountant should receive the same VAT ID, validation status, reverse-charge flag, invoice number, customer country, and PDF link that the customer sees.
Buyer question: Can the export prove which invoices were validated, manually reviewed, reverse charged, or rejected?
Three VAT validation scenarios to test before buying
Valid intra-EU B2B buyer
Trigger: A German company enters a valid DE VAT ID while buying from a Dutch WooCommerce store.
Workflow: Normalize the VAT ID, store the VIES response, apply the correct reverse-charge invoice wording if store policy allows it, attach the PDF to the order email, and export the validation evidence for the accountant.
VIES service unavailable during checkout
Trigger: The buyer enters a plausible VAT ID but VIES is temporarily unreachable or slow.
Workflow: Do not lose the order intent. Put the invoice into manual review or proforma state, keep the entered VAT ID, notify finance, and issue the final VAT invoice after validation or override.
Invalid VAT ID after invoice generation
Trigger: Support discovers a wrong VAT number, customer typo, or country mismatch after a PDF already exists.
Workflow: Retain the original document, generate a correction or credit note where required, store the validation failure reason, and keep the export trail clean for accounting review.
Weak VAT field vs invoice-ready validation workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| A checkout field only checks that the VAT number box is not empty. | VAT ID, country, validation status, timestamp, response outcome, and manual review state are stored as invoice evidence. |
| The checkout fails hard whenever VIES times out, losing qualified B2B orders. | Timeouts route to proforma/manual review so revenue is captured without faking validation success. |
| Reverse-charge text is added manually to PDFs after the order is placed. | Reverse-charge wording is generated from the validation state and preserved on customer PDFs and exports. |
| Refunds and credit notes ignore the original VAT validation decision. | Corrections, credit notes, retained PDFs, and accounting exports reference the original validation trail. |
FAQ
Does WooCommerce include VIES VAT validation by default?
No. WooCommerce can store billing fields, but EU B2B VAT validation, reverse-charge invoice wording, evidence retention, credit-note linkage, and accountant-ready export usually require a dedicated workflow or plugin.
Should checkout block the order if VIES is down?
Not always. For B2B stores, a safer workflow is to keep the order or proforma, flag it for manual review, then issue the final invoice once validation succeeds or finance approves an override.
What should be stored after a successful VAT validation?
At minimum: VAT ID, buyer country, validation status, validation timestamp, source/response outcome, invoice decision, reverse-charge flag, and any manual override note.
Where does Lattice Invoices fit in VIES validation workflows?
Lattice Invoices early access is positioned around WooCommerce EU invoice evidence: VAT/BTW checkout fields, VIES-ready validation states, reverse-charge wording, invoice PDFs, credit notes, customer downloads, and accountant export readiness.