UBL is a data-quality problem before it is an export problem.
A UBL invoice can only be as reliable as the WooCommerce order data behind it. If VAT numbers live in order notes, buyer references arrive by email, and refunds have no credit-note document, every export becomes a manual finance task.
This guide turns that buyer-intent search into a clear Lattice Invoices qualification path: clean checkout fields, locked invoice metadata, consistent PDF documents, refund credit notes, and accountant-ready handoff.
WooCommerce UBL readiness checklist
Fields to preserve before UBL export
| Area | Data to collect | Revenue impact |
|---|---|---|
| Supplier data | Legal business name, VAT number, address, bank details, invoice prefix | Without stable seller data every invoice export needs manual correction. |
| Customer data | Company name, VAT/BTW number, billing address, invoice email | B2B buyers reject invoices when tax identity is missing or only saved in a note. |
| Buyer references | PO number, department, cost centre, contact person | Many EU business buyers need internal approval references on the invoice. |
| Tax breakdown | VAT rate, VAT amount, reverse-charge or exemption reason, validation evidence | UBL and accountant exports need the tax decision as data, not just a PDF total. |
| Document lifecycle | Proforma, final invoice, payment reminder, refund credit note, customer download | The store needs a controlled flow for every finance document connected to the order. |
High-intent buying signals
The accountant asks for UBL or structured invoice export
This is a strong purchase signal because the store already feels the cost of manual bookkeeping cleanup.
Business customers ask for PO numbers or buyer references
A generic WooCommerce billing form is no longer enough; the order needs invoice-specific checkout fields before payment.
Refunds create mismatched paperwork
A refund note is not the same as a credit note. Finance needs a document tied to the original invoice and VAT amounts.
Setup sequence for a store owner
1. Map required invoice fields
List every value the accountant, buyer, and tax workflow need before adding another PDF plugin.
2. Add checkout fields before payment
Collect VAT/BTW number, PO/reference, invoice email, and company details while the buyer is still completing the order.
3. Lock invoice metadata on paid orders
Save invoice number, date, VAT breakdown, and currency totals when the order becomes invoice-ready.
4. Validate export and credit-note flow
Test one paid order, one refund, one customer download, and one accountant export before relying on the setup.
Early-access CTA: €49 UBL readiness workflow review
Send your store URL, seller country, current invoice/PDF plugin, accounting or UBL tool, VAT-field status, buyer-reference needs, and credit-note requirements. That is enough to qualify whether Lattice Invoices is a fit.
Send my UBL invoice requirementsFAQ
Does WooCommerce create UBL invoices by default?
No. WooCommerce stores order and tax data, but a UBL-ready workflow normally needs extra invoice fields, structured metadata, invoice numbering, PDF generation, credit notes, and accounting export logic.
Is UBL the same as a PDF invoice?
No. A PDF is human-readable. UBL is structured invoice data for accounting/e-invoicing systems. A good WooCommerce invoice workflow keeps the visible PDF and structured export values consistent.
What should I fix first if customers request UBL?
Start with data capture: VAT/BTW number, company details, PO/reference, invoice email, tax breakdown, invoice number, and credit-note relationships. Export format is easier once the order data is clean.
How does Lattice Invoices fit?
The early-access product path focuses on making WooCommerce invoice-ready: VAT fields, invoice PDFs, credit notes, customer downloads, and structured accountant handoff. UBL readiness is a strong qualification signal for that workflow.