Due dates are a sales feature and an accounting control.
If a B2B customer cannot see when an invoice is due, they forward the WooCommerce order email to finance and wait. If your reminder emails only know the order date, follow-up becomes noisy and imprecise.
Lattice Invoices is being positioned for the missing invoice layer: payment terms on the correct document, due-date-aware reminders, protected downloads, and a clear proforma-to-final-invoice path for bank transfers.
Due-date workflow checklist
Payment terms WooCommerce stores commonly need
| Term | Best fit | Invoice workflow note |
|---|---|---|
| Due on receipt | Low-ticket plugins, digital downloads, urgent B2B orders | Payment request/proforma immediately, final invoice after payment |
| Net 7 | Small agencies and repeat business customers | Reminder 2 days before due date, overdue note on day 8 |
| Net 14 | EU B2B stores selling setup services or annual licenses | Clear due date on proforma and first reminder after 14 days |
| Net 30 | Enterprise procurement and reseller invoices | PO/reference field, finance contact, staged reminders before overdue |
| Custom due date | Manual quote-to-invoice or negotiated terms | Admin override with audit trail so support does not edit PDF text by hand |
Where due dates protect revenue
Bank transfer orders need a deadline
Problem: WooCommerce BACS orders can stay unpaid while the customer believes the invoice is already final.
Lattice path: Send a payment request with a due date, then issue the final VAT invoice when payment clears.
Finance teams need payment terms on the PDF
Problem: A buyer forwards an order email to finance, but the PDF lacks Net 14/Net 30 language and PO/reference data.
Lattice path: Collect invoice fields at checkout and render payment terms directly on the invoice/proforma document.
Overdue reminders need invoice context
Problem: Generic WooCommerce emails say an order is pending, but finance needs the invoice number, due date, and bank details.
Lattice path: Drive reminders from invoice due dates and include consistent document links for the customer.
Early-access offer: €49 due-date workflow review
If unpaid invoices or bank-transfer orders are slowing payment, send your payment terms, current order emails, reminder timing, and invoice PDF requirements. Lattice will use that to prioritize the due-date workflow inside Lattice Invoices.
Send my payment-term workflowFAQ
Can WooCommerce show invoice due dates?
WooCommerce can store order dates, but invoice due dates usually need a dedicated invoice workflow. EU B2B stores often need payment terms, due dates, VAT metadata, and reminder timing that are separate from the basic order-created date.
Should a bank-transfer order receive a final invoice before payment?
Many stores prefer a proforma or payment request before payment, then a final VAT invoice after payment is received. The exact accounting treatment depends on country and business policy, so the plugin should make the document state explicit.
What payment terms should a WooCommerce invoice support?
Common terms are Due on receipt, Net 7, Net 14, Net 30, and custom due dates. B2B stores also often need a PO/reference field and bank-transfer details on the invoice or proforma.
How does Lattice Invoices plan to handle due dates?
Lattice Invoices is being shaped around invoice-ready checkout fields, proforma/payment request workflows, final invoice PDFs, due-date-aware reminders, credit notes, and protected customer downloads for EU WooCommerce stores.