Why receipt vs invoice confusion costs time
WooCommerce can confirm payment quickly, but finance teams often need a different document story: was the customer sent a receipt, a proforma, a final VAT invoice, or a credit note? If that distinction lives in emails and spreadsheets, every refund, B2B invoice request, and export becomes manual.
Lattice Invoices is being shaped around this buyer problem: turning payment evidence into a clean WooCommerce invoice workflow for stores that sell across EU VAT/BTW, B2B, BACS/manual invoice payment, and accounting handoff scenarios.
Receipt vs invoice readiness checklist
1. Separate payment proof from VAT invoice proof
A gateway receipt proves that a payment happened. A VAT invoice usually needs legal seller/buyer details, VAT treatment, invoice number, dates, line items, tax rates, and retention/export evidence.
Buyer question: Can your plugin clearly show customers and accountants which PDF is a receipt, proforma, final VAT invoice, or credit note?
2. Collect B2B invoice fields before the document is generated
If the buyer needs a company invoice, checkout should capture billing entity, VAT ID, country, PO/reference, and reverse-charge decision before the invoice PDF is issued.
Buyer question: Does the checkout flow collect invoice-ready fields, or does support fix receipts manually after purchase?
3. Keep invoice numbers sequential and immutable
Receipts can often use gateway transaction IDs, but VAT invoices need a numbering story that finance can explain. Editing or deleting issued invoice numbers creates audit risk.
Buyer question: Can the plugin prevent accidental gaps, duplicates, and overwritten PDFs when a receipt needs to become an invoice?
4. Map refunds to credit notes, not just order notes
A refunded receipt is not enough for many accounting workflows. The correction should link the original invoice, credit note, VAT amount, customer PDF, and export row.
Buyer question: When a paid order is refunded, does the customer get a linked credit note and does accounting see the relationship?
5. Export the same document story your customer sees
Support, customer downloads, email attachments, and accountant exports should agree. If the customer sees a receipt but the export says invoice, reconciliation becomes manual.
Buyer question: Can you export receipt/invoice status, invoice numbers, VAT evidence, payment reference, and credit-note links together?
Four scenarios to test before choosing a plugin
B2C card payment with simple receipt
Trigger: A consumer buys a low-risk digital product and only needs payment confirmation.
Workflow: Send the payment receipt, but keep the order eligible for a VAT invoice if the customer later requests one. Avoid issuing final invoice numbers before the store policy requires it.
B2B buyer asks for an invoice after payment
Trigger: The customer paid by card or PayPal, then asks support for a company VAT invoice with VAT ID and PO number.
Workflow: Collect missing billing details in a structured way, issue a final VAT invoice with the correct numbering and VAT treatment, and attach/download the PDF without editing old receipt text.
Order starts as proforma, ends as paid final invoice
Trigger: A company buyer needs a document before payment approval but should not receive the final VAT invoice until payment is confirmed.
Workflow: Send a proforma/payment request first, keep the payment link or BACS reference connected, then create the final invoice and customer download after payment.
Receipt payment is later refunded
Trigger: The gateway payment succeeded, the invoice was issued, and the order is partially or fully refunded.
Workflow: Retain the original invoice, issue a linked credit note, expose both PDFs to the customer, and export both documents to the accountant.
Weak receipt workflow vs invoice-ready workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| Gateway receipt email is treated as the invoice, with no VAT invoice number or buyer VAT fields. | Receipt and VAT invoice are separate document states with clear labels, fields, PDFs, and export rows. |
| Support edits billing details manually after the customer requests an invoice. | Structured invoice fields are captured before document generation and retained for audit/export. |
| Refunds only update the WooCommerce order total and the gateway dashboard. | Refunds create linked credit-note evidence that matches customer downloads and accounting exports. |
| Accountant export does not show whether a row came from a receipt, proforma, invoice, or credit note. | Export includes document type, number, VAT treatment, payment reference, customer PDF URL, and correction links. |
Want the receipt/invoice workflow reviewed?
Send your store URL and current payment/invoice plugin. We will review where receipts, invoice PDFs, VAT fields, payment references, refunds, and exports currently break down and map it to the €49 Lattice Invoices early-access workflow.
Request €49 workflow reviewFAQ
Is a WooCommerce receipt the same as an invoice?
No. A receipt generally proves payment. A VAT invoice usually needs more structured legal, VAT, numbering, and retention information. Some stores can use simple receipts for some purchases, but B2B and EU VAT workflows often require invoice PDFs and credit-note handling.
Can WooCommerce generate invoices only after payment?
Yes, but the workflow has to be deliberate. Stores often need a proforma or payment request before payment, then a final invoice PDF after payment, with invoice numbers, VAT evidence, and customer downloads preserved.
What should I ask before buying a WooCommerce invoice plugin?
Ask how it separates receipts, proformas, final invoices, and credit notes; how it handles VAT IDs and reverse charge; whether invoice numbers are immutable; how refunds are documented; and whether accountant exports match customer-facing PDFs.
Where does Lattice Invoices fit?
Lattice Invoices early access is being positioned for WooCommerce stores that need EU VAT/BTW invoice workflows around receipts, payment links, BACS/manual invoice payment, final invoice timing, PDF delivery, credit notes, customer downloads, and accountant exports.