Which invoices are overdue, and what has been chased?
Chaser runs your credit control. Memtro reads customers with payer rating and average days to pay, invoices with amount due, due date and promised payment date, and each invoice's chasing history with reminders, notes and any open dispute. When asked and once an administrator has granted the action by name, it can add notes, manage credit-control tasks, add or change customers and contacts, assign chasing schedules, and pause or resume chasing. Resuming chasing means customers are emailed or texted reminders again, and a new contact receives them. Deleting a note or contact is permanent. Paid invoices archive after six months.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Chaser tool, reads what it needs, and answers with the source cited.
These tools change something in Chaser. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Chaser is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Chaser + MemtroWhich invoices are overdue and what has been chased?
Has BigCo promised a payment date on their open invoice?
Which customers take longest to pay?
Pause chasing on invoice INV-3381 while the dispute is open.
Add a note to Northwind's record that their finance contact is away until Monday.
Sarah Chen, Finance Director at Acme Ltd, asked which invoices were overdue and what had been done about them. Memtro listed the overdue invoices with totals per currency and read the chasing history on the largest. It showed the reminders sent, a promised payment date and an open dispute.
Dan Fletcher, Credit Controller at Acme Ltd, said BigCo was disputing invoice INV-3381 and asked Memtro to stop the reminders and remind him to check on Friday. Memtro paused chasing on that invoice and created a follow-up task assigned to Dan. Chaser sent BigCo nothing further on it until chasing was resumed.
The teams that lean on Chaser most, a question each of them asks, and what they connect beside it.
A record in Chaser is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
NetSuite
Ramp
FreeAgent
Holded
Mollie
QuickFile
Recurly
Airwallex
Maxio
Pennylane
Charity Commission (England and Wales)
Checkout.com
FCA Register
Soldo
Spendesk
Lago
Recharge
Katana
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn Chaser, open Organisation Settings → Integrations → Get API keys and generate a key pair.
Copy the API key and the API secret from the same dialog.
In Memtro, open Connections → Chaser and paste the API key and the API secret.
Ask: Which invoices are overdue and what has been chased?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Chaser tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a Chaser customer, edit it or delete it; create a credit-control task, or complete, cancel, reschedule or reassign one; pause chasing of an invoice, a customer or the whole organisation, or resume it (resuming emails customers reminders again); add a customer, or change its name, main contact or status (archive or reactivate); add, change, archive or remove a contact person who receives a customer's reminders; put up to 50 customers on a chasing schedule. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key and API secret. In Chaser, open Organisation Settings → Integrations → Get API keys and generate a key pair.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time