The problems Hive solves
- Overdue invoices go unchased because nobody owns the list every morning.
- Failed payments in Stripe retry silently until the subscription lapses.
- Disputes sit waiting for a response while the evidence deadline approaches.
- Reminders are inconsistent: the tone, timing and follow-up depend on who happens to send them.
- Leadership has no single view of cash at risk across tools.
What Hive catches
Each signal shows the amount at risk, the customer, the invoice and a link back to the source record. Hive raises a signal only when the evidence holds up. A single spike in a metric doesn’t fire, and repeat detections update the existing signal instead of creating a new one.
Overdue invoices on your matters
Where Signals keeps your matters, each overdue Xero, QuickBooks or FreeAgent invoice becomes its own Invoice to chase on the matter it belongs to, visible only to the member who connected the account:- Picked up on time. An open invoice Hive has already read is read again within about a day of its due date passing, even if nothing about it changed: on the first read after the due date has ended in every time zone, and only while it is still open with an amount due. Paid, voided, draft and awaiting-approval invoices, and Stripe invoices charged automatically, are never chased. Xero invoices are read oldest due first, about 200 per read; in QuickBooks and FreeAgent, an account with more than 50 open invoices may not have its oldest ones re-read.
- In its own currency. The card shows the amount in the invoice’s own currency, taken from the connected record, never from Hive’s AI.
- The chase ends on its own when the invoice is paid, voided, credited or closed in the system of record. Only a Xero invoice paid with money received reads Paid. Voided (Voided in Xero), credited (for example written off with a credit note) and FreeAgent-closed invoices end the chase without claiming payment, and Hive never chases again on an invoice it read as closed. A send already in progress is not cancelled.
- Bills too. The bills you owe in Xero and QuickBooks are tracked as matters, earliest due first. Hive never pays one.
- Card disputes. Each open Stripe dispute gets a Dispute evidence due card 48 hours before Stripe’s deadline. Hive never submits evidence.
The Stripe and Xero invoice-collection detectors are switched on per workspace. When a Xero invoice detector is first switched on, it opens one item per invoice that is currently authorised and unpaid, so expect a burst at the start. Ask support to switch them on.
Approve the chase, don’t write it
If you hold a Max seat, choose Act on this when a signal needs action (members on a Pro seat don’t get the button). Hive prepares a plan: for example, a reminder email in your tone, addressed to the contact on the invoice. It comes back to you as an approval card on the Signals page, even when the account it would use is on Act; if that account is on Read, Hive only tells you what it found. The review panel shows:- What happens next: the exact steps, and which ones wait for you.
- Reply that will be sent: when the plan sends or saves one email you can edit, the text of that email exactly as it goes out. Otherwise Proposed message shows the plan’s summary.
- Risk and evidence: why Hive is asking first, the predicted blast radius, and what happens if you do nothing.
Automate the routine chase
The Fee Reminder template runs every morning at 6:00 AM: The run pauses at Approve the reminders and shows you exactly who would be emailed. Approve and every reminder on that list is sent from the Outlook account selected for the step, with no further card while that account is on Act: the addresses come from your own Xero records, read by an AI step that only reads Xero, so the workflow treats them as its own (see What agents and workflows do by themselves). Reject and the run stops. A morning with nothing overdue never asks. A test run sends nothing, so try it first. The approval sits before the loop because an approval can’t sit inside one. You can also add a Condition step to skip clients on hold, or a Wait step to space out follow-ups. See Workflow templates and Workflow steps.Ask Hive about cash
Ask questions across your connected tools and get answers with citations:- Which invoices over £5,000 are more than 30 days overdue in Xero?
- Show me this month’s failed Stripe payments and which customers they belong to.
- Summarise our profit and loss for last quarter and flag anything unusual.
- Which clients have I chased twice without a reply?
Guardrails finance teams care about
- Spend caps. Set a per-action cap and a daily cap on money actions in Policy & autonomy. The defaults are £5,000 per action and £25,000 per day.
- Role limits. Operators approve lower-risk actions and every card they hold themselves, at any risk; other refunds and B4 actions need an Admin or Owner. An agent or workflow carries out the actions selected for it by itself on an Act account (on Draft each waits for approval), unless where an action sends did not come from you; your role decides which actions you can put in a workflow you deploy (see Workflow steps).
- Kill switch. Halts every autonomous action and approval, company-wide, instantly.
- Audit log. Every action records who or what decided it, the evidence, and before-and-after state. Reversible actions can be undone.
Connectors for finance
Finance and payments integrations
Stripe, Xero, QuickBooks, FreeAgent, Sage and more: what each reads and writes.
Email and calendar
Gmail and Outlook, for sending chases and tracking replies.
Related
Accounting and client services
For accountancy firms chasing fees across many clients.
Triage signals
Act on, snooze or dismiss a signal.
See your overdue invoices in Hive
Connect Xero or Stripe and see what needs chasing. The 7-day trial needs no card.