Niches · Accounting & invoicing
Categorise bank lines and match payments to invoices and bills
Two or three companies' docs show a full fit.
What counts as done
Each bank line in the period is either matched to an invoice, bill or payment or coded to an account, a payment recorded against an invoice changes its status to paid, and the ledger bank balance equals the statement balance at period end, all through the API.
Measured, for our own tests: 100 transactions in under 30 calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: categorise last month's transactions
, reconcile the bank account
, mark this invoice as paid
, why does the bank balance not match the books
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Pennylane B Pennylane SAS | Match and unmatch a transaction to a customer or supplier invoice, categorise a bank transaction, create transactions, mark invoices paid, and read the trial balance for the period, all by documented endpoints. The 100-line call bar is the suite's to measure. source |
| Zoho Books C Zoho Corporation Private Limited | Bank transactions have Get matching transactions, Match, Unmatch, and Categorise as expense, customer payment, vendor payment, refunds or a new transaction, so each feed line is matched or coded and a customer payment marks the invoice paid. The 30-call bar is the suite's. source |
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| FreeAgent API C FreeAgent Central Limited | Statements upload as a transaction array or file, and bank_transaction_explanations take paid_invoice, paid_bill, category or a transfer, which marks the invoice paid. One explanation per call, so 100 lines need about 100 calls, past the 30-call bar. source |
| Invoice Ninja API D Invoice Ninja LLC | bank_transactions/match links a line to invoice ids, a payment, an existing expense or a new vendor expense, in bulk, and rules auto-match. Bank sync is an Enterprise or self-host feature, and there is no ledger bank balance to check against a statement. source |
| Odoo External API C Odoo SA | Bank statement lines and reconciliation are model methods, so reachable in principle, but no documented matching call exists, and acc-54 shows a bank statement created through JSON-2 losing its journal reference (open issue). source |
| Puzzle API and MCP D Puzzle Financial Inc. | Transactions create up to 500 per request and update (categorise) under write:transaction, and categorisation metrics exist, but no endpoint matches a bank line to an invoice or bill; the MCP's reconciliation claim has no published tool behind it. source |
Doesn't do this job 8
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Apideck Accounting API + MCP BB Apideck Inc. and Apideck NV/BV | bank-feed-statements pushes a platform's own transactions into a ledger for the customer to reconcile there; there is no endpoint to match or categorise existing bank lines. Payments allocated to invoices do mark them paid. source |
| Codat B Codat Limited | bankTransactions can be created (pushed into a ledger) but not updated, matched or categorised; payments create against invoices. No route codes or matches existing feed lines. source |
| FreshBooks API D 2NDSITE Inc. | Payments record against invoices and mark them paid, but the API has no bank transaction, feed or reconciliation endpoint; bank reconciliation stays in the web app. source |
| Merge Accounting API BB Merge API, Inc. | bank-feed-transactions POST pushes lines into a platform's feed and payments can be applied to invoices, but nothing categorises or matches existing feed lines; transactions are read-only. source |
| QuickBooks Online API + MCP D Intuit Inc. | Intuit's maintainer closed the categorisation request (acc-42, issue 121) saying bank feed transactions are not exposed by the Accounting API. Payments against invoices work, but feed lines cannot be matched or coded. source |
| rotki MCP server D Rotki Solutions GmbH | No bank lines or matching; writes and DDL are rejected by query_sql. source |
| Rutter Accounting API C Rutter | bank_feeds/transactions pushes lines into a platform's feed and bank deposits can be created, but there is no endpoint to match or categorise existing feed lines. source |
| Xero API + MCP B Xero Limited | The Accounting API has BankTransactions (spend and receive money, with IsReconciled) and Payments that mark invoices paid, but no bank statement line or match endpoint, so feed lines cannot be matched or coded; MCP update-bank-transaction also fails every call (acc-27, open). source |
What stops agents finishing
- no API route to categorise or match bank-feed lines, so the agent drives the web UI
- reconciled transactions cannot be edited through the API
- payment taken through a redirect method is never recorded against the invoice
Around it
Before: banking-data.find-transactions, mailbox-access.find-and-read. After: accounting.read-reports, accounting.close-period.
Where this comes from
Weight 19 of 100 in Accounting & invoicing: 13 of 69 use-case citations across 60 accounts, scaled to 100
The same as data: /api/v1/use-cases/accounting.reconcile-bank.json, or the MCP tool get_use_case with id accounting.reconcile-bank. Other jobs in this category: /api/v1/niches?category=accounting.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.