QuickBooks Invoice Chaser with Hermes
One run a morning, around thirty a month, whether you are owed four invoices or four hundred. The work inside a run scales with how many customers are overdue rather than how many invoices exist, since a customer is one draft. Hermes is hosted for you on the open Hermes models, so there is no separate dunning service to pay for or keep alive.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Overdue sweep 12 August
Nine invoices are past due for a total of 38,420.00 GBP. Meridian Property Group holds three of them between 12 and 19 days old for 14,900.00 GBP, Calder Fit Out has a single invoice at 6 days for 2,180.00 GBP, and the remaining five are one invoice each between 3 and 11 days old. Nobody has been emailed about any of them this week.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect QuickBooks
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Dunning policy
Your reminder ladder for overdue invoices - how many days past due before the first nudge, how the tone hardens at each step after that, the smallest balance worth chasing, how long to wait between reminders, and which accounts (payment plans, live disputes, your biggest customers) never get a templated email.
Runs on Hermes
Preselected for this page — connect your Hermes account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Hermes for this agent
Thirty runs, not thirty thousand
The schedule fires once each morning and the sweep handles the whole ledger inside it. Receivables volume changes the length of a run, not the number of them.
One summary for the whole book
The aging split and the per customer lines arrive as a single message. That is the receivables question a founder asks on a Monday, answered before they ask it.
Before you fork
Our biggest customers should never get a templated email. Is that safe on an open model?
It is a list rather than a judgement call, which is the safest kind of instruction to give any model. Name those accounts explicitly in the dunning policy instead of describing them as important, and they are skipped and reported in Slack. Vague protection wording is where this goes wrong, on any harness.
Run it with a different agent
Put QuickBooks Invoice Chaser to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.