The automation trap: issuing the PDF is the easy part
Many stores turn on automatic invoice PDFs and assume the job is done. Then finance discovers edge cases: unpaid BACS orders already have final invoices, refund corrections overwrite old documents, VAT IDs are missing from exports, or customers ask support for download links.
A better WooCommerce invoice automation workflow starts by deciding when an invoice should be issued, what evidence must be stored, and what downstream systems need at month end.
Five automation rules before you buy another plugin
Rule 1
Capture invoice data before payment
Company name, VAT/BTW number, billing country, PO reference, payment method, exemption reason, and customer email should be saved before any invoice number is consumed.
Rule 2
Separate proforma from final invoice
Bank-transfer and B2B approval workflows often need a payment request first, then a final paid invoice only after reconciliation.
Rule 3
Automate credit notes without editing old invoices
Refunds should create a linked credit note with its own number, VAT correction, PDF, customer delivery status, and export row.
Rule 4
Attach and expose PDFs in the right places
The customer should receive invoice PDFs by email and be able to download them from My Account without asking support.
Rule 5
Export accountant-ready invoice evidence
Month-end exports should include invoice number, order ID, VAT treatment, paid status, credit-note links, customer VAT ID, currency, due date, and PDF URL.
Automation trigger matrix
| Trigger | Automation rule | Caution |
|---|---|---|
| Order placed with card payment | Generate final invoice after payment succeeds; attach PDF to processing/completed email. | Do not issue a final invoice for failed or abandoned payment attempts. |
| Order placed with BACS/bank transfer | Send proforma or payment request first; issue final invoice when the order is marked paid. | A final invoice at order creation can create unpaid invoice clutter for finance. |
| Refund or partial refund | Generate a separate credit note and link it to the original invoice in export and customer downloads. | Editing the original invoice after it was sent weakens the audit trail. |
| EU B2B reverse-charge order | Store VAT evidence and print reverse-charge wording on the invoice PDF and export. | A zero-VAT line without explanation creates accountant follow-up work. |
Early-access offer: €49 invoice automation review
Send your payment methods, current PDF invoice plugin, VAT countries, refund workflow, and accounting software. Lattice will map when invoices should be issued, where credit notes and proformas belong, and what is missing before automation is safe.
Send my automation workflowFAQ
What should WooCommerce invoice automation include?
A useful automation workflow should handle invoice data capture, sequential invoice numbers, PDF delivery, BACS/proforma timing, credit notes, VAT evidence, customer downloads, reminders, audit trail, and accountant exports.
Should WooCommerce generate invoices automatically when an order is created?
Not always. Paid card orders can usually receive a final invoice after successful payment, but BACS and approval workflows often need a proforma first and a final invoice only after payment is reconciled.
How do refunds fit into invoice automation?
Refunds should create credit notes rather than rewriting the original invoice. The credit note needs a number, PDF, VAT correction, customer delivery path, and export link back to the original invoice.
Where does Lattice Invoices fit?
Lattice Invoices is the early-access product path for WooCommerce EU VAT and B2B invoice automation: VAT fields, proforma/final invoice timing, credit notes, PDF delivery, customer downloads, audit trail, and accounting handoff.