# Finance

Source: https://routineos.org/use-cases/finance

> Catch the invoice that should not be paid. A Claude routine for finance teams, built from a real template. It starts report-only and never pays.

Use case: finance

# Finance routines for Claude: flag the invoice before anyone pays it

One template reads incoming invoices and flags the ones a person should check: possible duplicates, amounts over a limit you set, and vendors it has not seen. It writes a report and never pays, approves or replies. It starts report-only. Free (MIT). Needs a paid Claude plan.

[Get started](https://routineos.org/#start)[See invoice exceptions](https://routineos.org/templates/invoice-exceptions)

invoice-exceptions: unpilotedexample scenario

The job

## The job: invoice exceptions, checked before payment

Someone in finance reads each incoming invoice and asks three questions: have we seen this before, is the amount unusual, and do we know this vendor.

It is repetitive reading with a few clear rules, which suits a routine that flags and leaves the decision to a person. The scenario below is an example built only from what the template does.

An example week

## An example week with invoice exceptions

This is an example built from the real templates, not a customer story. It carries no results, numbers or quotes. Say a small finance team points the template at the mailbox or folder where invoices arrive.

1. **Weekdays, 22:00 UTC: the routine runs**It lists invoices from the last seven days (the default look-back) and reads each into structured fields. It leaves out anything unclear instead of guessing.
2. **Plain code does the checks**A script, not the model, flags duplicates, amounts over your threshold (1000 by default) and vendors not on your known-vendors list. Duplicate checks look back 90 days of recorded invoices.
3. **You open the Desk**The few flagged invoices land in your Inbox, up to ten per run by default. You decide what to do outside the routine. The routine itself never pays, approves, schedules, replies to or marks anything.
4. **You teach it your vendors**You open the Desk and keep, edit or drop what you see. The routine learns from those choices and suggests setting changes. Nothing applies until you say yes. For example, adding a vendor domain to known_vendors stops it being flagged as new.

Source: template READMEs and catalog schedules in the [RoutineOS repository](https://github.com/devkindhq/routineos). Schedules are the template defaults, in UTC.

Templates

## The finance template

 [

### Invoice exceptions

Reads incoming invoices and flags duplicates, large amounts and new vendors for a person to check. It never pays.

unpilotedwatch
Open ](https://routineos.org/templates/invoice-exceptions)

**Needs**An invoice mailbox or folder connector with read access

**Default schedule**Weekdays, 22:00 UTC

**First run**Report-only

Maturity is from the catalog. This template has not had a real run yet, so read the first report-only run before you rely on it.

Safety

## What it never does

These come from the template prompts. They are rules the prompt forbids and the checks around it. They are not a promise about every possible run.

- The prompt forbids paying, approving, scheduling, replying to or marking any invoice.
- Every flag is a prompt for a person to check, not a decision.
- Reading a PDF can misread an amount or number, so the routine leaves out unclear values.
- An older duplicate than 90 days of recorded invoices is not caught.

**Heads up**The prompt always flags changed bank details. but this routine is not a fraud control. Keep your own payment checks.

Next

## Where to go from here

Read the [invoice exceptions page](https://routineos.org/templates/invoice-exceptions) for install steps and settings. See the other teams on [all use cases](https://routineos.org/use-cases), read how [approvals](https://routineos.org/concepts/approvals) and [learning](https://routineos.org/concepts/learning) work, or check the [honest limits](https://routineos.org/honest-limits).

## Install invoice exceptions

Run it report-only, check the first flags against invoices you already know, then tune the threshold.

[Get started](https://routineos.org/#start)[Install invoice exceptions](https://routineos.org/templates/invoice-exceptions)