The sale risk: finance requirements arrive after checkout.
A normal WooCommerce checkout collects enough data to ship a product. It often does not collect enough data to satisfy public-sector, enterprise, or cross-border B2B finance teams that expect e-invoice-ready fields.
Lattice Invoices is being shaped around that gap: collect buyer references before payment, store EU VAT decisions on the order, create clean PDF invoices and credit notes, and make the data easier to pass to an accountant, ERP, or Peppol access point.
Peppol/e-invoice readiness checklist
Structured invoice data WooCommerce should preserve
| Area | Data to capture | Why it matters |
|---|---|---|
| Seller identity | Legal name, VAT number, address, invoice prefix | Missing seller metadata causes Peppol/access-point rejection. |
| Buyer identity | Company name, VAT/BTW number, country, Peppol/GLN ID if available | B2B buyers often need more than the normal billing address. |
| Buyer reference | Purchase order, contact person, cost center, department | Public-sector and enterprise buyers may reject invoices without a reference. |
| Tax evidence | VAT rate, exemption reason, reverse-charge wording, validation timestamp | Zero-VAT and cross-border B2B invoices need proof, not just a total. |
| Document lifecycle | Proforma, final invoice, reminders, credit notes, customer downloads | The same order may produce multiple finance documents. |
Common Peppol/e-invoice scenarios
Public-sector buyer asks for Peppol
Problem: A government, school, or healthcare buyer wants an electronic invoice through its Peppol access point instead of a normal WooCommerce email PDF.
Lattice path: Capture buyer references and structured metadata now, then hand the data to the accountant/access point without retyping the order.
Enterprise buyer needs PO fields
Problem: A B2B customer can pay by card or bank transfer, but the invoice must include PO number, department, and buyer VAT ID.
Lattice path: Add invoice-ready checkout fields before payment and print the same fields on the PDF invoice and export.
Refund creates e-invoice mismatch
Problem: The original invoice was exported, but the refund only exists as a WooCommerce refund note without a matching credit note number.
Lattice path: Create credit notes with references to the original invoice and keep VAT/exemption logic aligned.
Early-access offer: €49 Peppol readiness workflow review
Send your store URL, current invoice plugin, buyer types, VAT-field status, accounting tool, Peppol/access-point plan, and whether PO/reference fields or credit notes are already a sales blocker.
Send my Peppol invoice requirementsFAQ
Can WooCommerce send Peppol e-invoices by default?
WooCommerce does not ship with a complete Peppol/e-invoicing workflow. Most stores need additional invoice metadata, structured exports, PDF templates, credit notes, and often a separate Peppol access point or accounting integration.
Do I need Peppol support before I sell to EU B2B buyers?
Not always. Many B2B buyers still accept PDF invoices, but public-sector and larger enterprise buyers increasingly ask for structured e-invoices, buyer references, and clean VAT metadata. Preparing the WooCommerce order data early reduces manual finance work later.
What fields should I collect for Peppol-ready WooCommerce invoices?
At minimum: company name, VAT number, billing country, buyer reference or PO number, invoice email, seller VAT details, tax/exemption reason, invoice number, and line-item VAT data. Some buyers also need Peppol participant ID, GLN, department, or cost center.
How does Lattice Invoices fit into Peppol workflows?
The early-access focus is not replacing every Peppol access point. It is making WooCommerce orders invoice-ready: checkout fields, VAT metadata, PDF invoices, sequential numbering, credit notes, customer downloads, and structured data handoff for accountants or e-invoicing tools.