> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI for finance teams: get paid faster without losing control

> How finance teams use Hive to catch overdue invoices, failed payments and disputes in Stripe and Xero, draft reminders, and approve every outgoing chase.

Cash leaks through small gaps: a failed card retry nobody noticed, an invoice that went overdue while its owner was on leave, a dispute whose response deadline passed quietly. Hive watches your billing and accounting tools, raises those moments as signals with the evidence attached, and prepares the chase. A person approves it before anything goes out.

## 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

| Signal | Source | What it means |
| - | - | - |
| Automatic invoice collection failing | Stripe | An invoice set to charge automatically hasn't been collected. |
| Sent invoice overdue | Stripe | An invoice you sent for payment is past its due date. |
| Dispute needs a response | Stripe | A payment dispute is open and waiting on you. |
| Invoice needs collection | Xero | An authorised invoice is due or overdue and still has an amount remaining. |
| Unusual movement | Any connected finance tool | A metric Hive monitors, such as outstanding balance, moved well outside its usual range. |
| Client gone quiet | Gmail or Outlook | You chased and the client hasn't replied. |

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.

<Note>
  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](/help/support) to switch them on.
</Note>

## Approve the chase, don't write it

When a signal needs action, choose **Act on this**. Hive prepares a plan: for example, a reminder email in your tone, addressed to the contact on the invoice. The review panel shows:

* **What happens next**: the exact steps, and which ones wait for you.
* **Proposed message**: the email that will be sent.
* **Risk and evidence**: why Hive is asking first, the predicted blast radius, and what happens if you do nothing.

Choose **Approve & run now**, **Decide later** or **Do not run**. Refunds are the highest-risk tier (B4). They always ask first, and they route to an Admin or Owner to approve. See [Review and approve](/approvals/review-and-approve).

## Automate the routine chase

The **Fee Reminder** template runs every morning at 06:00:

```mermaid theme={null}
flowchart LR
  A[Schedule: daily 06:00] --> B[Agent: find overdue invoices in Xero]
  B --> C[Loop: for each overdue fee]
  C --> D[Outlook: send reminder]
```

Each outgoing email passes the approval gate, so you can start with every reminder waiting for review, and loosen that only as trust builds. You can also add a **Condition** step to skip clients on hold, or a **Wait** step to space out follow-ups. See [Workflow templates](/workflows/templates) and [Workflow steps](/workflows/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?*

Hive reads live data where your connector supports it and says so when it couldn't check a live source. See [Ask Hive](/ask/ask-hive).

## 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 can approve lower-risk actions. Refunds and other B4 actions route to Admins and Owners.
* **Kill switch.** Halts every autonomous action and approval, company-wide, instantly.
* **Audit log.** Every action records who approved it, the evidence, and before-and-after state. Reversible actions can be undone.

Read [Safety and control](/admin/safety-and-control) for the full model.

## Connectors for finance

<CardGroup cols={2}>
  <Card title="Finance and payments integrations" icon="building-columns" href="/integrations/finance-and-payments">
    Stripe, Xero, QuickBooks, FreeAgent, Sage and more: what each reads and writes.
  </Card>

  <Card title="Email and calendar" icon="envelope" href="/integrations/email-and-calendar">
    Gmail and Outlook, for sending chases and tracking replies.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Accounting and client services" icon="briefcase" href="/use-cases/accounting-and-client-services">
    For accountancy firms chasing fees across many clients.
  </Card>

  <Card title="Triage signals" icon="filter" href="/signals/triage-signals">
    Act on, snooze or dismiss a signal.
  </Card>
</CardGroup>

<Card title="See your overdue invoices in Hive" icon="arrow-right" href="https://app.get-hive.ai">
  Connect Xero or Stripe read-only and see what needs chasing. The 14-day trial needs no card.
</Card>