Overdue payment reminders without spreadsheet chasing

why overdue invoices still live in chase spreadsheets

Open receivables hide in exported ageing sheets that go stale by lunch. Someone filters red rows, copies emails, and pastes a polite reminder that still cites the wrong remaining balance because a partial payment landed this morning. Customers get duplicate nags from sales and finance. Disputed invoices keep receiving threats while the credit note sits unapplied in Comarch Optima or enova. WooCommerce store invoices and ERP direct invoices age in different tools, so a client with two accounts gets two tones of voice. Collections under NDA for B2B shops usually fail first on data freshness, not on reminder copy. Automation should read live open items, suppress paid and disputed documents, apply a stage calendar, and log every send against the invoice. It should also hand off hard cases to a human with context rather than denser email. Cash application must close the loop the same day a bank match posts, otherwise you apologise for reminders that should never have gone out. Multi-entity groups need per-company letterhead and bank details in the template. Tone must escalate by stage without becoming abusive or legally careless. Link each reminder to the PDF and a payment URL when one exists. Keep a do-not-contact flag for accounts in formal restructuring. Promise-to-pay dates deserve their own field so automation freezes politely until the promised morning. Public sector segments should start later. Interest fee language must be counsel-approved. Align subscription cut-offs with AR only under one written policy.

when an open invoice crosses its due date

Nightly ageing job marks invoices past due that are not on dispute hold, not in legal hand-off, and not fully paid. Intraday bank application can clear a stage immediately. Manual trigger lets credit control force stage one after a broken promise-to-pay date. New invoices never enter the flow before due date plus grace hours. Public holiday calendars per billing country shift send windows.

how to run staged overdue payment reminders

1. Pull open invoices from ERP and optionally WooCommerce with balance, due date, customer contacts, language, and dispute flags.
2. Compute stage from days overdue and customer segment rules, skipping weekends if policy says so.
3. Render the stage template with live balance, payment references, and PDF link; pick email and optional SMS only when consent and channel rules allow.
4. Send via ESP or transactional mail, store message id on the invoice, and notify the account owner on stage three and above.
5. On full or partial payment webhook, recompute balance and cancel queued sends for that document.
6. On dispute flag, freeze reminders and create a task for credit control with the last customer reply attached when available.
7. Escalate to human call list when stage max is reached without payment, including call script fields and last touch timestamps.

invoice ageing data into reminder channels

n8n reads Optima or enova open-item APIs and WooCommerce unpaid orders marked as invoiced. A small rules table maps days overdue to stages. Brevo or another transactional provider sends mail; SMS is optional and consent-gated. Make can work for a single entity; n8n handles multi-company credentials cleanly. Payment webhooks from the PSP or bank-matching tool call a cancel endpoint. Store GDPR-sensitive contacts with purpose limitation; DE deployments need an AVV with the ESP, NB follows Datatilsynet guidance, ES AEPD expectations, PT-PT CNPD. Never write reminder body into public order notes. Link reminder events into multi-source finance reports as collection activity counts, not as revenue. Overdue: Document owners for each queue so alerts land on a named role rather than a shared inbox that nobody reads during holiday cover. Overdue: Keep runbooks beside the workflow with the exact API fields you map, because tribal knowledge disappears when the integrator changes. Overdue: Test the happy path and the three most common exceptions in a staging company database before touching production periods. Overdue: Measure baseline minutes per document for two weeks so the ROI calculator uses your numbers rather than a generic industry guess. Overdue: Prefer idempotent writes and explicit status enums over clever silent retries that hide poison messages from operators. Overdue: When legal templates are required, store them versioned and reference the version id on every outbound message or booking annotation. Overdue: Separate sandbox credentials from production credentials even if the ERP vendor makes that inconvenient for smaller licences. Overdue: Review failed jobs weekly in a short finance operations meeting so exceptions do not silently age past the point of easy recovery. Overdue: Write acceptance tests for amount thresholds and holiday calendars, because those two settings cause most production surprises. Overdue: Expose a read-only status page to requesters so finance stops answering the same where-is-my-document messages by chat. Overdue: Document owners for each queue so alerts land on a named role rather than a shared inbox that nobody reads during holiday cover. Overdue: Keep runbooks beside the workflow with the exact API fields you map, because tribal knowledge disappears when the integrator changes. Overdue: Test the happy path and the three most common exceptions in a staging company database before touching production periods. Overdue: Measure baseline minutes per document for two weeks so the ROI calculator uses your numbers rather than a generic industry guess. Overdue: Prefer idempotent writes and explicit status enums over clever silent retries that hide poison messages from operators. Overdue: When legal templates are required, store them versioned and reference the version id on every outbound message or booking annotation. Overdue: Separate sandbox credentials from production credentials even if the ERP vendor makes that inconvenient for smaller licences.

how to stop reminder loops after payment or dispute

Bounce handling marks bad emails and routes to the account owner for a fresh contact within forty-eight hours. Soft fails retry twice. If balance becomes zero between queue and send, abort. Template render errors dead-letter the job with invoice id. Rate limits on the ESP spread large portfolios across the morning window. Dual-source invoices with conflicting paid flags prefer ERP truth and log the Woo mismatch. Bundle stage one statements when policy allows while logging per-invoice touches.

when automated dunning is not worth enabling

You have fewer than roughly twenty open customer invoices a month and one person already calls every debtor. Or your terms are prepaid only. Or legal forbids any automated chase without counsel-approved templates you do not have yet. If ageing is wrong because credit notes never auto-apply, fix application first.

kpis for overdue payment collection automation

• Days sales outstanding trend by segment
• Share of overdue invoices with a logged touch inside SLA
• Reminders cancelled due to same-day payment
• Dispute freezes opened versus wrongly sent nags
• Cash collected within seven days of stage two