Categorise bank transactions on a schedule
Uncategorised transactions pile up until someone spends days sorting them. A scheduled agent clears the backlog, then runs weekly: it drafts a category for each line, flags the uncertain ones and sums spend by category. Its department head reviews the run, then you approve.
How it runs
One agent does the work. Its department head reviews it, then you approve.
- 1Business analyst agent
Runs every Monday at 08:00 and prepares the report from your connected sources.
- 2COO agent · Review
The department head reviews the report before it reaches you.
- 3You
You approve before anything goes out.
What you get
Sample, not live data. The business, payees and amounts are invented.
Week of 12 January: 41 transactions, 37 drafted, 4 flagged (excerpt: 3 rows shown)
| Date | Payee | Amount | Draft category | Status |
|---|---|---|---|---|
| 12 Jan | Harbor Office Lease | -$1,800 | Rent | Ready |
| 13 Jan | CloudDesk | -$49 | Software | Ready |
| 14 Jan | J. Ortiz | -$650 | ? | Flagged: over your $500 threshold, payee not in your examples |
Spend by category (sample): Rent $1,800 · Payroll $6,200 · Software $310 · Other $940
Why categorisation falls behind
Every business transaction needs a category before you can see profit, prepare a tax return or answer a simple question such as what you spent on software last quarter. The IRS notes that for most small businesses the business checking account is the main source for entries in the business books. HMRC asks self-employed people to keep records of all sales and income and all business expenses, and to make sure they can identify business transactions. The work is easy but repetitive: read the payee, recall what it was, pick a category. That is why it slips, and why a catch-up of a few months turns into days of clicking.
How the scheduled job works
You add the job and give it read access to the accounting tool or bank feed that holds your transactions, plus your category list, a review threshold and the date to catch up from. Organ builds the connection with read access; until it is in place the job waits, paused. A scheduled business analyst agent then runs every week. Each run covers transactions since the last run, starting from your catch-up date, so the earliest run carries the backlog. It drafts one category per line, using your category list and any example payees you add to it. Anything it is unsure about, anything above your threshold and anything unusual, such as a new payee or a likely duplicate, is flagged rather than guessed. The run ends with a short summary of spend by category. Its department head reviews the run before it reaches you, and you approve, edit or skip each draft.
A worked example
Say a design studio has 420 uncategorised lines from the last three months and uses eight categories. The catch-up run drafts categories for the lines it can match with confidence and flags the rest: an unfamiliar payee, a transfer that could be owner drawings or a loan repayment, and anything over $500. The owner reviews the drafts, spends most of the attention on the flagged lines, and corrects a handful. Adding those payees to the category list as examples helps later weekly runs. These figures are illustrative, not measured results.
What stays with you
The job reads; it does not change your books or your bank. You keep the final say on every category and on anything that looks like a personal expense or a tax question, which belongs with your accountant. If you would rather not connect anything yet, attach a CSV export to a one-off task in Organ to clear the backlog, then add the weekly job once a connection with read access is in place. If unpaid invoices are the other cash task on your list, see the overdue invoice follow-up job linked below.
Questions
Read access to the accounting tool or bank feed that holds your transactions, your category list, a review threshold and a catch-up date. Organ can work with any API or MCP server, built for you. The job waits, paused, until that connection is in place.