Niches · Accounting & invoicing
Turn a supplier invoice or receipt into a posted bill or expense
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A bill (or expense) exists against the right supplier, account and tax code, with the source file attached and a due date set, and a repeat run does not create a second bill for the same supplier invoice number.
Measured, for our own tests: a batch of 20 bills completes without an unhandled 429. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: find the invoices in my email and enter them
, record this receipt
, post these supplier bills
, add the bill and attach the PDF
Does the job, with a limit 13
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 |
|---|---|
| Apideck Accounting API + MCP BB Apideck Inc. and Apideck NV/BV | Bills and suppliers create on 48 of 57 connectors and an attachments endpoint covers 31, but an Idempotency-Key on bill creates works only on Xero (6-minute window), so repeat runs need the duplicate-bill guide's own check. No Apideck rate limit published, only downstream headers. source |
| Codat B Codat Limited | Bills and suppliers create, with a push attachment endpoint per bill and a 90-minute idempotency cache that releases the key on 429. Only the cached window guards repeats, so a rerun next day needs its own supplier-invoice-number check; new clients are steered to Bill Pay. source |
| FreeAgent API C FreeAgent Central Limited | Bills take contact, category, due_on, reference and an attachment of up to 5MB in one create. Limits are 120 requests a minute per user, and a bills run hit the 429 twice and failed part way (acc-56); no duplicate check on reference is documented. source |
| FreshBooks API D 2NDSITE Inc. | Bills take a vendorid, lines with category, due offset and an attachment field, and expenses have an attachments endpoint. No duplicate check on the supplier's number and no documented rate-limit numbers or 429 behaviour for a batch. source |
| Invoice Ninja API D Invoice Ninja LLC | No bills resource: a supplier invoice becomes an expense against a vendor and category, with a file via /expenses/{id}/upload. Expenses have no due date or payable status, and no duplicate check on the supplier's number. source |
| Merge Accounting API BB Merge API, Inc. | Bills are invoices with type ACCOUNTS_PAYABLE, and attachments POST separately with their own meta/post. No duplicate guard on retries, and acc-49 shows the Python SDK ignoring retry-after-ms on 429. source |
| Odoo External API C Odoo SA | Bills are account.move records with move_type in_invoice, reachable through the generic method call, but the JSON-2 page documents no bill fields, attachment route or duplicate guard; field names come from the per-database /doc, which needs a login. source |
| Pennylane B Pennylane SAS | Supplier invoices import with an uploaded file_attachment_id and a deadline, and categorise afterwards. The upload can answer 409 until the file is ready, and 25 requests per 5 seconds with retry-after means a 20-bill batch must pace itself. source |
| Puzzle API and MCP D Puzzle Financial Inc. | Create Bill, Update Bill Status, Create Vendor and Create Attachment for a bill exist under write:bill scopes, but REST access is by request and no duplicate guard or rate limit is published. source |
| QuickBooks Online API + MCP D Intuit Inc. | create_bill, create_vendor and create_attachable cover the bill and its PDF; the create-bill schema mismatch (acc-43, issue 36) is closed as completed. No documented duplicate check, and rate limits are behind the JavaScript-only portal. source |
| Rutter Accounting API C Rutter | Bills and vendors create, bills take attachments, and Idempotency-Key covers retries; 452 separates platform throttling from Rutter's own 429. Duplicate protection lasts only as long as the key, so a later rerun needs a document_number lookup. source |
| Xero API + MCP B Xero Limited | Bills are ACCPAY invoices with attachments and Idempotency-Key in the API, and acc-10 set up an email-to-bills flow quickly. The MCP has no attachment tool (acc-30, issue 156 open), and per-minute limits sit on a JavaScript-only page. source |
| Zoho Books C Zoho Corporation Private Limited | Bills create with bill_number and due date, take an attachment, and move to open through status/open. No documented duplicate check on bill_number for creates, and the plan's daily cap (1,000 on Free) can end a batch. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| rotki MCP server D Rotki Solutions GmbH | No bills, suppliers or attachments; SQL is read-only. source |
What stops agents finishing
- no attachment tool, so the bill has no source document for the accountant
- bill schema in the MCP does not match the ledger, so creates fail or drop fields
- per-user rate limit hit part way through a batch with no retry
Around it
Before: mailbox-access.find-and-read, document-extraction.extract. After: accounting.reconcile-bank, banking-data.sync-ledger.
Where this comes from
Weight 13 of 100 in Accounting & invoicing: 9 of 69 use-case citations across 60 accounts, scaled to 100
The same as data: /api/v1/use-cases/accounting.capture-bill.json, or the MCP tool get_use_case with id accounting.capture-bill. 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.