The subscription invoice problem
A one-off order can be checked manually. A subscription store cannot. Every renewal may need the same VAT evidence, PDF delivery, due date, payment status, and customer-download access as the first invoice.
Lattice Invoices is being shaped around that revenue path: make renewal orders invoice-ready, keep failed payments from polluting final invoice numbering, and give the accountant a clean monthly trail.
Recurring invoice readiness checklist
Subscription invoice workflow map
| Stage | What changes | Invoice workflow requirement |
|---|---|---|
| Signup order | The customer starts a subscription | Capture company details, VAT ID, billing country, invoice email, and payment method before the first invoice is generated. |
| Renewal | WooCommerce creates the next recurring order | Reuse verified VAT metadata, generate a renewal invoice PDF, and keep numbering sequential or clearly separated. |
| Failed payment | Card or bank transfer is not paid | Send a payment-request/proforma style document and reminder rather than pretending the invoice is already settled. |
| Plan change | Customer upgrades, downgrades, pauses, or cancels | Record proration lines, credit notes, replacement invoice references, and the reason for the adjustment. |
| Accounting handoff | Bookkeeper reconciles monthly revenue | Export invoice number, renewal status, payment status, PDF URL, VAT evidence, credit-note links, and customer reference. |
Common recurring-invoice blockers
B2B SaaS renewal with reverse charge
Problem: The subscription renews automatically, but the buyer's finance team asks why VAT is 0% and whether the VAT number was still valid for that renewal.
Lattice path: Carry VAT ID, country, exemption reason, and reverse-charge wording into every renewal invoice packet.
Failed renewal before final invoice
Problem: A renewal order exists, but payment failed. Sending a final invoice too early creates accounting cleanup when the customer never pays.
Lattice path: Use payment-request/proforma status until payment is confirmed, then release the final invoice with clean numbering.
Upgrade, downgrade, or prorated refund
Problem: Subscription changes produce messy refunds and manual notes that do not connect to the original invoice.
Lattice path: Tie prorations, credit notes, and replacement invoice PDFs to the renewal order and export them as one audit trail.
Early-access offer: €49 subscription invoice workflow review
Send your store URL, country, current subscription plugin, invoice plugin, VAT/BTW field status, failed-renewal process, credit-note/refund workflow, and accounting export needs. The goal is to convert those recurring billing headaches into the next Lattice Invoices purchase-ready workflow.
Send my recurring invoice requirementsFAQ
Does WooCommerce generate recurring invoice PDFs for subscriptions by default?
WooCommerce can create subscription renewal orders when a subscription extension is installed, but recurring VAT invoice PDFs, sequential renewal numbering, credit-note links, customer download access, and accounting export usually need a dedicated invoice workflow.
Should failed subscription renewals get a final invoice?
Many stores prefer a payment request or proforma-style document until payment is confirmed, then issue the final VAT invoice with stable numbering. Your accountant should confirm the exact treatment for your jurisdiction.
What recurring invoice fields matter most for EU B2B subscriptions?
Track company name, VAT/BTW number, billing country, exemption or reverse-charge reason, renewal date, due date, payment status, invoice number, credit-note references, PDF URL, and invoice recipient email.
How does Lattice Invoices fit subscriptions?
The early-access focus is to make WooCommerce invoice workflows predictable for EU stores: VAT metadata, renewal-ready invoice PDFs, proforma/payment-request states, due dates, credit notes, customer downloads, and accountant-ready export.