Why Stripe stores still need an invoice workflow
A Stripe charge proves that money moved. It does not automatically prove that the customer entered the right VAT/BTW number, that the invoice number was issued at the right moment, or that a refund created accountant-ready credit-note evidence.
For EU WooCommerce stores, the payment gateway and invoice workflow should meet at the order record. The order should show customer VAT metadata, invoice PDF state, Stripe charge or refund references, credit-note links, and customer download access without manual spreadsheet reconciliation.
Stripe invoice readiness checklist
1. Capture VAT/BTW data before Stripe payment
Stripe can collect money cleanly, but EU invoice quality depends on WooCommerce order metadata: company name, VAT/BTW number, billing country, invoice email, PO/reference, and tax exemption status before the payment succeeds.
Buyer question: Does the invoice workflow store VAT fields on the order before Stripe confirms payment?
2. Issue the invoice from a reliable paid-order event
The invoice number should be created when the WooCommerce order reaches the correct paid status, not when a customer merely lands on checkout. That prevents gaps, duplicates, and draft invoices for failed card attempts.
Buyer question: Which order status triggers final invoice numbering for card, Apple Pay, and Google Pay payments?
3. Keep Stripe charge and invoice evidence together
Support and accounting need one place to see invoice number, Stripe charge ID, payment method, VAT totals, payment date, customer VAT number, and PDF delivery status.
Buyer question: Can the export include invoice number and Stripe payment reference in the same row?
4. Handle refunds with credit notes instead of rewritten invoices
A Stripe refund should not silently overwrite the original invoice. The safer workflow retains the issued PDF and creates a credit note or correction record linked to the original WooCommerce order and Stripe refund.
Buyer question: Does a refund create a traceable credit-note workflow for your accountant?
5. Give customers a download fallback
Even when the invoice PDF is attached to the order email, customers often need it weeks later. A My Account download link reduces support tickets and makes B2B repeat purchases smoother.
Buyer question: Can customers download paid invoices and credit notes without contacting support?
Three Stripe invoice scenarios to test
Card payment succeeds immediately
Trigger: Stripe confirms payment and WooCommerce marks the order as processing or completed.
Workflow: Generate the final invoice number, attach the PDF to the customer email, store the Stripe charge ID, and expose the invoice in My Account.
Apple Pay / Google Pay checkout
Trigger: A wallet payment completes quickly, but business billing fields may be skipped if the checkout is too minimal.
Workflow: Require invoice-ready business metadata before payment confirmation and keep wallet payment evidence beside VAT totals and invoice PDF status.
Partial or full Stripe refund
Trigger: A paid order is refunded in WooCommerce or Stripe and accounting asks for the VAT correction trail.
Workflow: Retain the original invoice, create a linked credit note, store the Stripe refund reference, and export both documents together.
Manual workaround vs invoice-ready workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| Stripe dashboard has the payment, WooCommerce has the order, invoice PDF is a separate manual step. | WooCommerce order links invoice number, PDF, Stripe charge/refund references, VAT fields, and customer download status. |
| Invoice number created too early during checkout attempts, causing gaps and corrections. | Final invoice numbering starts only after the configured paid order status is reached. |
| Refund emails mention money returned but no credit note is attached or retained. | Refund workflow creates credit-note evidence linked to the original invoice and Stripe refund. |
| Customers email support for missing invoices after card payments. | Invoice PDFs are attached to emails and available from My Account downloads. |
What to send for a Stripe invoice review
Send your store URL, country, Stripe gateway/plugin name, current invoice plugin, VAT/BTW fields, refund workflow, and accounting export needs. That is enough to identify whether the main issue is checkout data capture, invoice timing, credit notes, or export evidence.
Request workflow reviewFAQ
Does Stripe automatically solve WooCommerce VAT invoicing?
No. Stripe handles payment collection and payment evidence. EU VAT invoices still need WooCommerce order metadata, invoice numbers, VAT fields, PDF delivery, refund credit notes, and accountant-ready exports.
When should a Stripe-paid WooCommerce invoice be created?
Usually when the order reaches the store's paid status, such as processing or completed. Creating the final invoice before payment succeeds can create invoice-number gaps and support confusion.
How should Stripe refunds appear in invoice records?
The original invoice should remain retained. Refunds should create credit-note or correction evidence linked to the WooCommerce order, Stripe refund reference, VAT totals, and customer-facing PDF history.
Where does Lattice fit if I already use a Stripe gateway?
Lattice Stripe Payments focuses on the payment path, while the Lattice Invoices early-access workflow focuses on VAT/BTW invoice evidence, PDF delivery, credit notes, and accounting handoff after payment.