Why SEPA payments create invoice friction
SEPA direct debit looks simple at checkout, but the invoice workflow often breaks later: mandate references sit in gateway logs, payment status changes after the PDF is sent, and failed debits create manual reminder work.
The safer workflow treats SEPA evidence as invoice metadata. The invoice number, VAT details, mandate reference, settlement status, reminder history, credit-note relationship, and customer downloads should remain connected to the WooCommerce order.
SEPA invoice readiness checklist
1. Capture mandate context before the invoice is issued
SEPA direct debit payments need more than a paid/unpaid status. Store the mandate reference, billing company, VAT/BTW number, invoice email, and payment method context before the invoice PDF becomes customer-facing.
Buyer question: Can the invoice plugin print and export the SEPA mandate reference without copying it into notes?
2. Separate payment collection from invoice evidence
A SEPA collection can be pending, settled, reversed, or failed. The invoice workflow should show when the invoice was issued, when the debit was attempted, and whether a final paid invoice, reminder, or credit note is now needed.
Buyer question: Does the workflow distinguish issued invoice, collection attempt, settlement, reversal, and refund evidence?
3. Keep failed-debit follow-up attached to the invoice
When a debit fails, support needs the invoice number, due date, mandate reference, customer VAT data, reminder email history, and next payment action in one place — not spread across payment logs and inbox threads.
Buyer question: Can unpaid SEPA invoices trigger reminders while keeping the original VAT PDF retained?
4. Handle reversals and refunds with credit notes
A returned debit or refund should not silently overwrite the original invoice. The safer path retains the issued invoice, creates a credit-note or correction record when needed, and exports both sides for accounting reconciliation.
Buyer question: Does the plugin link SEPA reversals, credit notes, and original invoice PDFs for your accountant?
5. Export the fields finance teams actually ask for
Useful exports include invoice number, mandate reference, SEPA status, VAT totals, reverse-charge status, due date, reminder state, credit-note links, and customer invoice download status.
Buyer question: Can accountant exports include SEPA and VAT evidence together instead of requiring manual matching?
Three SEPA invoice scenarios to test
B2B subscription renewal paid by SEPA
Trigger: A customer renews monthly and expects the invoice PDF to include VAT details while finance tracks the debit mandate.
Workflow: Issue the renewal invoice with VAT metadata, attach it to the renewal email, store mandate reference, and export settlement status after collection clears.
Direct debit fails after invoice issue
Trigger: The invoice PDF was already sent, but the SEPA collection fails or is reversed.
Workflow: Keep the original invoice retained, mark the payment evidence as failed, send a reminder with invoice link, and avoid changing historical invoice totals.
Customer cancels after debit collection
Trigger: A paid SEPA order is refunded or partially refunded and accounting needs the VAT trail.
Workflow: Generate a credit note linked to the original invoice and export invoice, credit-note, VAT, mandate, and refund references together.
Manual workaround vs invoice-ready workflow
| Manual workaround | Lattice Invoices direction |
|---|---|
| Mandate reference sits in payment gateway logs only | Mandate reference is visible on invoice metadata, export rows, and support workflow. |
| Failed debit creates a support inbox thread | Failed debit status stays attached to invoice reminders, due date, and payment follow-up. |
| Refund or reversal edits the order without invoice context | Credit-note path preserves original invoice PDF and links reversal/refund evidence. |
Early-access offer: €49 SEPA invoice workflow review
Send your SEPA provider, mandate reference source, current invoice plugin, failed-payment process, and accounting export needs. Lattice will map the invoice workflow buyers expect before you automate it.
Send my SEPA invoice workflowFAQ
Does WooCommerce handle SEPA invoice evidence by default?
WooCommerce and payment gateways can process payment events, but invoice-safe SEPA workflows usually need mandate references, PDF invoice retention, reminder history, credit-note links, and accountant exports tied together.
Should the invoice be created before or after SEPA collection clears?
That depends on the store's accounting process, but the workflow should record invoice issue date separately from collection attempt and settlement status so finance can reconcile the order later.
What happens when a direct debit is reversed?
Do not silently rewrite the issued invoice. Keep the original PDF, record the failed or reversed payment evidence, and use a reminder, correction, or credit-note workflow depending on the real transaction.
Where does Lattice Invoices fit?
Lattice Invoices is the early-access WooCommerce EU invoicing path for stores that need VAT invoice PDFs, SEPA mandate context, failed-payment follow-up, credit notes, customer downloads, and accountant-ready exports.