Why Mollie stores still need an invoice workflow
A Mollie transaction proves that a payment method was attempted or settled. It does not prove that the WooCommerce order has the right VAT/BTW number, that the final invoice number was issued at the right moment, or that reversals and refunds created accountant-ready correction evidence.
For Dutch and 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, Mollie payment/refund references, credit-note links, and customer download access without spreadsheet reconciliation.
Mollie invoice readiness checklist
1. Collect VAT/BTW data before the Mollie payment starts
Mollie can process iDEAL, Bancontact, cards, and SEPA flows, but EU invoice quality still depends on WooCommerce order metadata: company name, VAT/BTW number, billing country, invoice email, PO/reference, and exemption status before the customer leaves checkout.
Buyer question: Does the checkout store invoice-ready business fields before redirecting to Mollie?
2. Trigger final invoice numbering only after payment confirmation
Redirect-based payment methods can create pending orders before money is confirmed. Final invoice numbers should start when WooCommerce receives a reliable paid status, not when the customer merely clicks Pay.
Buyer question: Which WooCommerce status creates the final invoice for iDEAL, Bancontact, card, and SEPA orders?
3. Keep Mollie transaction evidence next to the invoice
Support and accounting need one order view that links invoice number, Mollie payment ID, payment method, VAT totals, payment date, customer VAT number, PDF state, and refund references.
Buyer question: Can exports include invoice number, Mollie payment ID, VAT totals, and refund references in one row?
4. Handle SEPA and delayed payment states cleanly
SEPA direct debit and some local methods can move through pending, paid, failed, reversed, or charged-back states. Your invoice workflow needs rules for proforma requests, final invoices, reminders, reversals, and credit notes.
Buyer question: How does the plugin behave when a Mollie payment is delayed, failed, reversed, or refunded?
5. Give B2B customers a download fallback
Even if the invoice PDF is attached to the paid order email, Dutch and EU B2B customers often need it later for finance teams. My Account downloads reduce support emails and speed repeat purchases.
Buyer question: Can customers download invoices and credit notes without opening a support ticket?
Three Mollie invoice scenarios to test
iDEAL or Bancontact payment succeeds after redirect
Trigger: The customer returns from Mollie and WooCommerce receives a paid status.
Workflow: Generate the final invoice number, attach the PDF, store the Mollie payment ID, and expose the invoice in My Account.
SEPA direct debit starts as pending
Trigger: The order exists, but payment can still settle, fail, or reverse later.
Workflow: Use a proforma or payment request until the configured paid status is reached, then issue the final VAT invoice and keep mandate/payment evidence linked.
Refund or chargeback happens in Mollie
Trigger: A paid order is partially or fully refunded, reversed, or disputed.
Workflow: Retain the original invoice, create linked credit-note evidence, store Mollie refund/reversal references, and export both documents for accounting.
Manual workaround vs invoice-ready workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| Mollie dashboard shows the payment, WooCommerce shows the order, and invoice PDFs are created manually later. | WooCommerce order links invoice number, PDF, Mollie transaction/refund references, VAT fields, and customer download status. |
| Final invoice number is created when the buyer clicks Pay, causing gaps for abandoned or failed redirect payments. | Final invoice numbering waits for the configured paid order status and keeps pending flows as proforma/payment-request evidence. |
| SEPA reversals and refunds are tracked in Mollie but not represented as retained credit-note evidence in WooCommerce. | Refund and reversal workflows create traceable credit notes linked to the original invoice, order, and Mollie payment event. |
| Dutch B2B customers email support for BTW invoices after iDEAL payments. | VAT/BTW metadata is captured before payment, PDFs are attached to emails, and customer downloads stay available later. |
FAQ
Does Mollie automatically create EU VAT invoices for WooCommerce?
No. Mollie handles payment methods and transaction 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 Mollie-paid WooCommerce invoice be created?
Usually after WooCommerce receives the configured paid status from the Mollie payment flow. Creating final invoice numbers before redirect payments settle can create gaps, duplicates, and correction work.
What is different about SEPA direct debit invoices?
SEPA can have delayed settlement and reversals. Many stores should use a proforma or payment request first, then issue the final VAT invoice after the order reaches a reliable paid state.
Where does Lattice fit if I already use Mollie?
Mollie remains the payment gateway. The Lattice Invoices early-access workflow focuses on VAT/BTW checkout evidence, invoice PDFs, customer downloads, credit notes, and accounting handoff around the WooCommerce order.