Why payment links create invoice workflow risk
A payment link looks simple: create an order, send a link, wait for payment. The invoice risk appears when finance asks which document was sent before payment, when the final invoice number was issued, what VAT evidence was captured, and how refunds or reminders were documented.
Lattice Invoices is being shaped around this problem: keeping payment requests, final invoice PDFs, credit notes, resend history, customer downloads, and accountant exports connected to the WooCommerce order instead of scattered across notes and gateway dashboards.
Payment-link invoice readiness checklist
1. Do not issue final invoice numbers too early
A payment link often starts as a request for payment, not proof that VAT invoice revenue is final. The workflow should distinguish quote, proforma, payment request, paid final invoice, and credit note states.
Buyer question: Can the plugin delay or clearly label final invoice creation until your finance rule says it is safe?
2. Keep the payment reference visible everywhere
If the customer receives a Stripe, PayPal, Mollie, SEPA, or bank-transfer link, the invoice workflow should retain the reference on the order, email, PDF, reminder, and accountant export.
Buyer question: Can support and accounting match the payment link, transaction, invoice number, and order without spreadsheet work?
3. Preserve VAT and buyer evidence before payment
B2B buyers often need VAT ID, PO number, billing entity, reverse-charge decision, and payment terms before accounts payable will click the link. That evidence should be collected before the request goes out.
Buyer question: Does the checkout or manual-order flow collect invoice-ready VAT and PO fields before payment?
4. Make reminders reference the same invoice story
Payment-link reminders should not create duplicate documents. They should reference the same proforma or final invoice record, show due dates, expose the pay link, and log resend history.
Buyer question: Can the store resend a payment link with invoice context while keeping an audit trail?
5. Handle refunds and failed payments as documents, not notes
If a payment link is paid and later refunded, the credit note should link to the original invoice. If payment fails, the request should remain unpaid instead of creating a misleading paid invoice trail.
Buyer question: What happens to invoice PDFs, credit notes, and customer downloads after failed or refunded pay-by-link orders?
Three payment-link scenarios to test before buying
B2B customer asks for a pay-by-link invoice
Trigger: Sales creates a manual WooCommerce order for a company buyer and sends a payment link before the order is paid.
Workflow: Collect VAT ID, PO number, billing entity, due date, and payment method. Send a proforma or payment request with the link, then create the final invoice PDF after payment according to the store policy.
Customer needs a reminder with the same payment link
Trigger: The first email was ignored, but the finance team needs one clear invoice/payment trail.
Workflow: Resend the payment link with the same invoice reference, due date, amount due, and document link. Log the resend so support can prove follow-up without editing the PDF manually.
Pay-by-link order is refunded later
Trigger: The invoice was paid by link, fulfilled, then partially or fully refunded.
Workflow: Keep the original invoice immutable, issue a linked credit note with VAT evidence, expose both PDFs to the customer, and export the relationship for the accountant.
Weak pay-by-link admin vs invoice-ready workflow
| Weak workflow | Lattice Invoices direction |
|---|---|
| A payment link is pasted into an order note and the invoice PDF has no payment reference. | Payment link, gateway reference, invoice number, order ID, and customer email remain connected. |
| The store sends a final invoice before payment, then deletes or edits it when the customer never pays. | The workflow labels the pre-payment document as a proforma/payment request and creates the final invoice at the correct moment. |
| Reminder emails are manual free-text messages with no resend log or PDF/customer-download fallback. | Payment reminders reuse the same document story and preserve due-date, resend, and download evidence. |
| Refunds only change the WooCommerce order total, leaving accounting to infer the correction. | Refunds produce linked credit-note evidence with retained VAT, transaction, and customer document history. |
FAQ
Can WooCommerce send invoice payment links by default?
WooCommerce can support payment links through gateways, manual orders, or customer payment pages, but a complete invoice workflow still needs VAT fields, document labels, final invoice timing, reminder history, credit notes, and accountant export evidence.
Should a payment link email include a final VAT invoice?
Not always. Many B2B stores should send a proforma or payment request before payment, then issue the final VAT invoice after payment. The exact rule depends on the store's tax/accounting policy, so the plugin should support clear document states.
What fields matter most for pay-by-link B2B invoices?
At minimum: buyer legal name, VAT ID, PO/reference, billing country, payment terms, payment-link reference, invoice or proforma number, due date, transaction status, PDF document URL, and refund/credit-note relationship.
Where does Lattice Invoices fit?
Lattice Invoices early access is positioned for WooCommerce stores that need EU VAT/BTW invoice workflows around payment links, BACS/manual invoice payment, PDF delivery, credit notes, reminders, customer downloads, and accountant exports.