One bot per
finance process.
Not an assistant that helps your team do the work. A bot that does the work, start to finish, and stops at the one point a person should decide.
Twelve of them, finance only — and each one has a name, because a team that runs four of these says “Ada held it” rather than reciting a product description. Each connects to the ledger you already use, posts under your own framework and leaves an audit trail a person can follow.
The whole function
Every other bot on this page does one process. This one does the job — which makes it the only one on the page you would compare to a hire rather than to a piece of software.
Accountant
The end-to-end role, not a step in it. Everything that arrives gets read, coded and posted; the ledger stays clean daily rather than being reconciled at month end; the close runs; the management accounts come out. The work an accountant does, done.
- Reads and posts everything that comes in — supplier bills, receipts, bank lines, expense claims
- Codes against your own chart and your own rules, and proposes the journal for anything it does not recognise
- Keeps the control accounts clean as it goes, so the mis-posting is caught on the day rather than at close
- Runs the month-end close and produces the management accounts
- Prepares the VAT return and the schedules your auditor asks for
- Answers “what is this?” about any transaction, with the document attached
- Escalates anything a rule says a person should decide, naming the rule
Where it stops: it starts draft-only — it prepares everything and posts nothing. Posting rights are a separate grant you give later, per process, revocable in one click.
Priced against a salary, not a process. The other bots are quoted per process once we have seen the volumes. This one replaces a role, so it is quoted against what that role costs you — and it is the only bot here we will talk you out of if your volumes do not justify it.
Transactions
The keying and the matching that fills the month. One process each, for a team that wants the hours back rather than the whole function handed over.
P2P
Procure to pay
Every supplier invoice, from the moment it arrives to the moment it is posted and scheduled — without anyone opening the inbox.
- Takes invoices from the AP mailbox, WhatsApp, or a link you send the supplier
- Reads the document and checks the arithmetic itself — it does not trust the total printed on it
- Matches to the purchase order, the agreement and that supplier’s own history
- Screens for duplicates, changed bank details and prices outside your tolerance
- Posts to the ledger and builds the due-date calendar for the payment run
- Chases the supplier itself for a missing TRN, a missing PO or an illegible page
Where it stops: anything that breaks a rule is held with the rule named. It never releases a payment.
AR
Order to cash
Raises the invoice, chases the money and allocates the receipt — so the aged debt report stops being a list of things nobody has done.
- Raises and sends the invoice from the order, in the format each customer insists on
- Chases on a schedule built from how that customer actually pays, not the terms on the invoice
- Allocates receipts to invoices, including part payments, deductions and short settlements
- Flags the customer whose payment behaviour just changed, before the debt ages
- Builds the aged debt pack with a recommended action against each account
Where it stops: it drafts the chase and proposes the credit hold. It never writes off a debt.
Payroll & Expenses
The run, the file and the journal — plus every expense claim checked against the policy rather than against whoever is reviewing it that month.
- Prepares the payroll run from the approved joiners, leavers and changes
- Builds the bank or WPS salary file ready for upload
- Checks each expense claim against policy and against the receipt attached to it
- Posts the payroll journal split by department, cost centre and project
- Reconciles the payroll control accounts and the end-of-service provision
- Flags the claim that breaks policy, naming the clause it breaks
Where it stops: no salary file is ever submitted by a bot. It prepares; you upload.
Reconciliation
The three ties that decide whether the numbers are real. Daily, not at the end of the quarter.
Bank Reconciliation
Every account, every currency, reconciled before you arrive.
- Takes the statement as MT940, CAMT.053, CSV or a portal download
- Matches many-to-one, part settlements and payments received net of charges
- Posts bank charges, interest and FX differences by your own rule
- Carries unmatched items forward with an age, so nothing quietly disappears
- Leaves one short list: what did not match, and why it did not
Where it stops: an unexplained difference is never forced to balance. It stays open with its age on it.
Inter-Group Reconciliation
The fortnight of archaeology at consolidation, turned into a daily tie.
- Matches every intercompany balance across each entity pair, daily
- Splits every difference into FX, timing or a genuine break — and says which
- Proposes the elimination journal for both sides, in both ledgers
- Handles mismatched functional currencies and in-transit stock and cash
- Tracks each break to closure with an owner and a date against it
Where it stops: journals are proposed in both companies. Neither posts until a person agrees the pair.
Revenue Assurance
From the order to the money in the bank, every step accounted for.
- Ties each order from the shop to the gateway, the bank and the ledger
- Finds the settlement that never arrived and the refund posted twice
- Reconciles platform fees, BNPL instalments and the cash-on-delivery you never see
- Catches the order total that changed after the report was taken
- Reports a percentage tie, so “revenue is right” becomes a number you can quote
Where it stops: it reports the gap. Whether to raise a credit note is yours.
Close & tax
What happens once the transactions are clean, and the filings that follow it.
Close & Financial Statements
Runs the close rather than reminding you to. Day two instead of day nine.
- Works the close checklist and tells you what is actually blocking it
- Posts accruals, prepayments, depreciation and the recurring journals
- Builds the statements under IFRS, US GAAP or your local framework
- Produces the lead schedules and the working papers the auditor will ask for
- Compares this close to the last three, and flags what moved without a reason
Where it stops: the statements come out as a draft for the person who signs them.
Tax & Filing
The return built from the ledger, with every number traceable to the transaction behind it.
- Builds the VAT or GST return from the ledger, not from a spreadsheet
- Tests each transaction’s tax treatment against the rules of your jurisdiction
- Prepares the corporate tax computation with every add-back supported
- Keeps the e-invoicing and filing calendar, and warns you before the date
- Leaves a trail from each box on the return to the entries inside it
Where it stops: it prepares and reconciles. Nothing is submitted to a tax authority by a bot.
Plan & report
The numbers you act on, and the ones you are betting on. Both only work properly once the ledger underneath them is clean — which is the argument for everything above.
FP&A
Planning, forecasting & cash
The budget, the forecast, the cash position and the explanation of why none of them happened — rebuilt from the ledger each month instead of from last month’s spreadsheet.
- Builds the budget from actuals by department, and chases each owner for their inputs
- Rolls the forecast forward every month, actuals replacing budget as they land
- Explains variance by driver — volume, price, mix, rate — not just by the number
- Runs the 13-week cash forecast off open AR, AP, payroll, loans and tax — on how each customer really pays, not the terms on the invoice
- Names the week cash breaks your buffer, while there is still time to act
- Models a scenario on demand: a price change, a hiring plan, a new site, a currency move
- Keeps P&L, balance sheet and cash tied to one another in every version
- Reconciles last period’s forecast to actual, and tracks each KPI against target
Where it stops: it plans, it never commits. No budget is approved, no spend authorised and no payment rescheduled by a bot.
Management Reporting
The same pack, the same definitions, on close day — not reassembled by whoever has time.
- Builds the board and lender pack from the closed ledger
- Drafts first-cut variance commentary against budget, forecast and last year
- Reports by entity, department, branch, project and channel from one source
- Reports actuals against the plan from the same source FP&A built it from, so the two can never disagree
- Produces the covenant calculations your lender asks for each quarter
- Builds a pack per audience — board, lender, investor, department head — from one close
- Flags the figure that moved outside its usual range before anyone has to present it
- Keeps every prior pack reproducible, so a restated figure can be explained
Where it stops: commentary is drafted for your review. Nothing reaches a board unread.
Control
The layer that only becomes possible once transactions flow through software. It is usually where the money turns out to be.
Duplicate & Fraud Screening
Most duplicate payments and payment fraud are caught by a control that runs after the cash has gone. This one runs before.
- Screens every payment run for duplicates — same amount, fuzzy vendor match, near-identical reference
- Blocks any payee whose bank details changed since the last run, until they are re-verified
- Flags employee and vendor bank accounts that match each other
- Catches the vendor created and paid in the same week
- Holds anything that breaks a rule, and names the exact rule that stopped it
Where it stops: a held payment stays held. Only a named approver releases it, and the release is logged.
One subscription per bot.
No licence, no seats.
You are not buying software to operate. You are paying a monthly fee for a process to be done, and it stops when you stop.
Set-up
Once, per bot. We map the process, write your rules down, get them signed off, build it, and run it in parallel with what you do now until it has proved itself on your own data.
- Process mapped and every rule written in accounting language
- Your sign-off on the rule set before a line is built
- Parallel run against your current process, not a switch-over
- Handover documentation and training for your team
The subscription
Per bot, per month. The runs themselves, somebody watching them, and the rule changes your business will need as it changes. Your team is not the bot’s support desk.
- Every scheduled run, monitored, with alerting when one does not finish
- A monthly review of what it held and why
- Rule maintenance as your suppliers, customers and chart change
- First-line support for your finance team, not a ticket queue
- Every version of every rule kept, so an auditor can see what ran when
The Accountant
The one bot on this page priced against a role rather than a process, because it replaces one. Compared to a salary, not to a subscription — and we will say so if your volumes do not justify it.
- Everything the process bots do, under one engagement
- Close, management accounts and the VAT return included
- One monthly fee, not twelve
- Quoted against what the role costs you today
What moves the number
- Volume. Documents or transactions a month — the single biggest driver.
- Entities. One company or a group with intercompany between them.
- Currencies. One, or several with revaluation and translation.
- Systems. A clean API is quicker to connect than a bank portal or a legacy ERP.
What never does
- Seats. Your whole finance team can use it. We do not count people.
- Your own data. No charge for storing it, exporting it or taking it with you.
- A long lock-in. Monthly, with notice. If it is not earning its fee, stop it.
- The session. The roadmap is free and yours to keep whether you buy or not.
We quote once we have seen the volumes and the state of the data — never from a price list, and never before we know whether the thing can actually be automated to the standard we would sign.
What “coming soon”
actually means here.
Two of these run today, on live books. The rest are specified and queued — and the order they get built in is decided by the people who ask for them.
Private beta
Built, running on real ledgers, and being hardened against things only live data does. If you want on it, say so — we take a few at a time so each one gets looked after.
Coming soon
Specified down to the rules and the human gates, not a name on a roadmap. Most of them already exist as the bespoke build we did for somebody’s month-end.
Or sooner
If a bot on this page is the one that would change your month, the working session is where it jumps the queue. We build what the roadmap justifies first.
We do not publish hours-saved figures before we have seen your data. The session gives you the real numbers for your business — volumes, touch time, and the honest limit of what can be automated.