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.
Working notes for the moments that matter.
Practical guidance on cadence, tone and payer commitments.
A cadence that works for relationship-led billing
Why the first reminder should arrive before the due date, and what changes at day 18 versus day 45.Playbook · 5 minWriting a reminder your client does not resent
Four openings that work, three that reliably cost you goodwill, and where the amount belongs in the message.Reference · 4 minRecording a promise to pay so it holds
What to capture when a payer names a date, and how to resume follow-up without starting the conversation over.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.
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 centreRather see it than read it?
A Receivables Leak Audit applies all of this to your own open invoices.
Book a demo