Skip to content
DueHello
Resources

How to chase an invoice without losing the client.

Working notes on receivables: cadence, tone, escalation routes, and what to do when your invoice disappears into someone else's finance system.

The 30/45/60 route, and why suppliers miss it.

Large payers publish what a supplier should do when an invoice is not paid. The steps are real, the deadlines are real, and almost nobody follows them, because following them requires remembering the exact day.

Day 30 Invoice should be paid under standard terms. Check it was received, matched and approved, not merely sent.
Day 45 Contact the payer's creditor administration directly, with the invoice reference and proof of delivery.
Day 60 A further route opens, including formal collection. Everything you did in the previous 30 days is now evidence.

Sourced from a large Dutch municipality's own published supplier guidance. Routes differ per payer, which is exactly why they belong in a playbook rather than in someone's memory.

Help centre

Product documentation

Connector setup, playbook configuration, permissions, exception routing and audit export. Available to every workspace from day one.

Open the help centre

Rather see it than read it?

A Receivables Leak Audit applies all of this to your own open invoices.

Book a demo