Why subscription invoices need renewal context
A subscription order can be a first purchase, renewal, manual payment, failed retry, yearly prepayment, prorated upgrade, downgrade credit, or cancellation adjustment. The invoice has to explain the billing period and payment state without support manually rewriting PDFs.
The safer workflow is to collect B2B billing and VAT fields before checkout or renewal, generate PDFs from structured WooCommerce subscription data, and use linked credit notes for plan changes, duplicate renewals, refunds, and VAT corrections.
Subscription stores issue invoices after many different events
A recurring WooCommerce order may be a first payment, renewal, failed retry, plan upgrade, downgrade, pause, reactivation, manual renewal, or annual prepayment. Generic PDF plugins often treat every order like a one-off receipt.
Better workflow: Capture subscription ID, renewal period, plan name, VAT/BTW number, invoice email, billing country, payment status, and customer download permissions before the invoice PDF is finalized.
Failed renewals and payment retries create finance questions
Finance teams need to know whether a renewal invoice is paid, pending, cancelled, retried, written off, or replaced. If the PDF does not reflect the subscription state, support has to explain every edge case manually.
Better workflow: Keep renewal status, due date, payment method, retry attempts, and paid/unpaid evidence as structured order data that flows into invoice emails and customer downloads.
Upgrades, downgrades, and refunds need credit-note control
Mid-cycle plan changes, partial refunds, VAT corrections, cancellation credits, and duplicate renewals should not be solved by editing an issued invoice.
Better workflow: Create linked credit notes for refunds and corrections, keep the original invoice retained, and show the corrected subscription period, VAT totals, and reason for the adjustment.
Feature checklist before choosing a subscription invoice plugin
| Requirement | Why it matters for subscription and membership stores |
|---|---|
| Subscription and renewal metadata | Subscription ID, renewal number, billing period, plan, seat count, renewal date, payment retry status, and cancellation context should be invoice-ready. |
| VAT/BTW and B2B billing fields | Company name, VAT/BTW number, invoice email, PO reference, billing country, and reverse-charge data must be collected before recurring invoices are generated. |
| Paid and unpaid invoice states | Renewal PDFs should make it clear whether the invoice is paid, pending bank transfer, failed, retried, cancelled, or replaced. |
| Credit notes for subscription changes | Downgrades, cancellation credits, duplicate renewals, VAT corrections, and partial refunds need separate credit notes linked to the original invoice. |
| Customer invoice downloads | Subscribers should be able to download current and historical invoice PDFs from My Account instead of asking support after every renewal. |
| Accountant handoff | Export invoice numbers, VAT totals, billing countries, renewal periods, credit-note links, and payment evidence in a way bookkeeping can reconcile. |
Subscription invoice scenarios
Monthly SaaS or membership renewal
Risk: The order renews automatically, but the customer later asks for a VAT ID, company name, invoice email, or renewal period on the PDF.
Better workflow: Collect business billing and VAT fields before renewal, then generate a renewal invoice with subscription ID, period, payment status, invoice number, and customer download link.
Annual plan upgrade or downgrade
Risk: A mid-cycle change creates prorated charges or credits that are hard to explain on a generic invoice PDF.
Better workflow: Keep old plan, new plan, proration, credit amount, VAT totals, and correction reason attached to the order and issue a credit note where needed.
Failed payment retry
Risk: The customer sees an invoice email but the payment failed, or finance asks if the invoice is payable, paid, cancelled, or replaced.
Better workflow: Store due date, retry status, payment method, reminder history, and final payment state so the invoice and follow-up email do not conflict.
B2B subscription with PO or cost-centre requirements
Risk: Accounts payable refuses the renewal invoice because it lacks PO number, department, cost centre, buyer reference, or invoice email routing.
Better workflow: Collect PO/reference fields and invoice email routing at checkout or account level before recurring PDFs are generated.
Fastest path to a purchase decision
If renewal invoices, failed payments, VAT fields, subscription upgrades, downgrades, customer downloads, and credit notes already create support work, send one structured fit-check email. Lattice can confirm whether the €49 early-access workflow fits before you buy another generic PDF add-on.
FAQ
Do WooCommerce subscriptions need a different invoice workflow?
Usually yes. Renewal invoices need subscription ID, billing period, payment status, VAT/BTW fields, customer downloads, failed-payment context, and credit-note handling for upgrades, downgrades, cancellations, and refunds.
Should renewal invoices be generated before or after payment?
It depends on the payment method. Card renewals often need final paid invoices after capture, while bank-transfer or net-terms workflows may need proforma or payable invoice timing before payment. The important part is to keep status, due date, and final invoice evidence consistent.
What makes Lattice Invoices relevant for subscription stores?
The €49 early-access workflow focuses on WooCommerce-native VAT fields, renewal metadata, paid/unpaid invoice state, PDF delivery, My Account downloads, accountant handoff, and linked credit notes rather than only styling a receipt PDF.
What should a subscription business send before requesting early access?
Send the store URL, country, subscription plugin, payment methods, renewal frequency, B2B/B2C mix, VAT/BTW fields, invoice-number format, failed-payment workflow, refund/credit-note needs, and accounting export requirements.