Credit control software that chases unpaid invoices with personalized, scheduled email and SMS reminders.
Chaser is accounts receivable and credit control software for small and mid-sized businesses. It connects to the accounting system, watches which invoices are outstanding, and sends polite, personalized payment reminders on schedules you define — before the due date, on it, and at escalating intervals after — by email and SMS, appearing to come from a real person on your team. It adds a payment portal, debtor tracking, and escalation paths for the invoices that reminders alone do not resolve. In the revenue stack it automates the human follow-up layer of collections.
Which of the capability map's modules Chaser covers — each links to the module's own page, with every tool that supports it.
| Module | Phase | Depth | Note |
|---|---|---|---|
| Run Revenue Operations | |||
| Receivables / AR Automation | Collect & Recover | Core | automated invoice chasing with escalation and a payment portal |
| Customer Communication Engine (Transactional) | Collect & Recover | Core | scheduled, personalized email and SMS reminders that read as human-sent |
| Communication Template Management | Collect & Recover | Supported | |
Chaser's craft is making automated chasing feel personal: sender identities, tone, and cadence are tuned so customers rarely realize a machine sent the reminder, which preserves relationships while cutting days sales outstanding. It targets the SMB accounting stack — Xero, QuickBooks, Sage — rather than the enterprise order-to-cash suites, and is correspondingly fast to deploy.
Done properly, no — reminders are personalized, sent from a named colleague, and paced by rules you control per customer. Most late payment is disorganization rather than refusal, and a timely nudge resolves it without friction.
Chaser focuses on the communication and follow-up layer for SMBs on mainstream accounting software, not on cash application, credit decisioning, or AP-portal delivery at enterprise volume. It is the right size when your problem is chasing, not order-to-cash transformation.
By overlap on the capability map — computed, not curated.