Why public-sector invoice requests create admin work
WooCommerce can collect payment quickly, but procurement teams care about the invoice document: PO number, buyer reference, department, VAT/BTW fields, invoice email, and a PDF that can be filed without edits.
Lattice Invoices is positioned for that gap: keep public-sector buyer fields, WooCommerce payment status, VAT totals, invoice PDFs, customer downloads, and credit-note evidence connected to the order.
A purchase order is mandatory before payment is approved
Public-sector buyers often cannot process a supplier invoice unless the PO number, buyer reference, department, and legal billing entity match procurement records exactly.
The person ordering is not the finance contact
A teacher, clinic manager, or department lead may place the WooCommerce order, while accounts payable needs a separate invoice email, buyer ID, VAT/BTW details, and PDF attachment.
Corrections and refunds need a defensible audit trail
If the PO number, VAT field, delivery address, or buyer reference is wrong, the store needs a replacement workflow and credit-note trail instead of editing old PDFs manually.
Public-sector invoice must-haves
Should a public-sector seller request Lattice Invoices?
| Store signal | Fit | Best next action |
|---|---|---|
| Schools, municipalities, hospitals, NGOs, or government departments buy from the store | Strong fit | Collect public-sector invoice fields before payment so procurement does not reject the invoice later. |
| Orders require PO numbers, buyer references, or separate accounts-payable emails | Strong fit | Treat PO/reference fields as invoice metadata, not as free-text order notes. |
| The store is preparing for e-invoicing, UBL, or Peppol requirements | Strong fit | Start by storing clean invoice data now, then export or map it into e-invoice formats later. |
| Only low-value consumer orders use card payment and no invoice approval | Wait | Use the free setup guide first; request Lattice Invoices when B2B/public-sector invoice requests become recurring. |
Copy this into the early-access email
A specific public-sector invoice request is easier to qualify than a generic plugin question. Send these details so the €49 Lattice Invoices path can be matched to the real procurement friction.
- •Store URL and country
- •Buyer type: school, municipality, hospital, NGO, public agency, or mixed B2B
- •Invoice fields required today: PO number, buyer reference, cost centre, department, invoice email, VAT ID
- •Payment method: card, bank transfer, net terms, purchase order, or invoice approval
- •Whether UBL, Peppol, or e-invoicing is required now or expected soon
- •Monthly public-sector orders and monthly invoice correction volume
Public-sector invoice FAQ
Why do public-sector WooCommerce buyers need a different invoice workflow?
Public-sector finance teams often require PO numbers, buyer references, legal billing names, VAT/BTW fields, and invoice PDFs that match procurement systems. A normal WooCommerce receipt can be rejected if those details are missing.
Does this replace a Peppol access point or accounting system?
No. Lattice Invoices is positioned as the WooCommerce order-level invoice workflow. The first goal is clean VAT and buyer-reference data, PDF delivery, credit notes, and accountant handoff. Peppol/UBL export readiness depends on storing the right fields first.
Can this help before e-invoicing is mandatory?
Yes. Even before mandatory e-invoicing, storing PO numbers, buyer IDs, VAT metadata, and PDF links in WooCommerce reduces support work and makes future UBL/Peppol mapping easier.
When should a store request early access?
Request early access when public-sector buyers already ask for corrected PO numbers, invoice email changes, VAT IDs, PDF resends, or credit notes. That is where a €49 workflow can pay back quickly.