Know what is actually overdue
Read invoice amounts, due dates and outstanding balances from your agreed source. See the ageing book and the invoices that need attention.
See overdue balances, previous reminders and account context in one place. Prepare a considered follow-up, with clear ownership and escalation rules.
Try the exampleINV-1048 is £1,200 outstanding and 16 days overdue, but Rachel’s Friday payment promise has not passed in this example. I would hold outreach and check receipts after the payment run.
Do not send another reminder yet. Set the next internal review after Friday’s payment run, then reconcile receipts and any dispute.
Illustrative example. No live connections or actions.
Read invoice amounts, due dates and outstanding balances from your agreed source. See the ageing book and the invoices that need attention.
Look for recorded payments, promises and disputes. Reconcile anything uncertain before another reminder reaches the customer.
Prepare a reminder with the right reference and amount. Hold it for approval and escalate according to the timing your team has agreed.
Agree reminder intervals, high-value thresholds and dispute handling. Reminders are held for approval; this demo never contacts a debtor.
Receivables records with outstanding amounts and due dates.
Account ownership, reminder history, email drafting and team notifications.
Connections, access and available actions are scoped during setup.
No. Your finance source remains the record of payments and balances. Zarco helps organise follow-through around it.
Check and reconcile recent payments before sending. An outstanding balance in one source may not reflect a payment made elsewhere.
Yes. Agree overdue-age and value thresholds, reminder spacing and the people who should handle disputes or broken promises.
We’ll work through the sources, rules and first useful workflow with you.
Arrange a demoOpens an email to luke@zarco.uk. No calendar slot is reserved.