{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/accounting.capture-bill/",
    "json": "https://www.anchorterminal.com/niches/accounting.capture-bill/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/accounting.capture-bill/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/accounting.capture-bill/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 13 | 13 | 13 | 9 |\n\n## What counts as done\n\nA 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.\n\nMeasured, for our own tests: a batch of 20 bills completes without an unhandled 429.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Apideck Accounting API + MCP (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.\n- **Codat (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.\n- **FreeAgent API (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.\n- **FreshBooks API (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.\n- **Invoice Ninja API (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.\n- **Merge Accounting API (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.\n- **Odoo External API (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.\n- **Pennylane (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.\n- **Puzzle API and MCP (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.\n- **QuickBooks Online API + MCP (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.\n- **Rutter Accounting API (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.\n- **Xero API + MCP (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.\n- **Zoho Books (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.\n\n- not this job: rotki MCP server (Rotki Solutions GmbH): No bills, suppliers or attachments; SQL is read-only.\n\n## What stops agents finishing\n\n- no attachment tool, so the bill has no source document for the accountant\n- bill schema in the MCP does not match the ledger, so creates fail or drop fields\n- per-user rate limit hit part way through a batch with no retry\n\n## Around it\n\nBefore: mailbox-access.find-and-read, document-extraction.extract. After: accounting.reconcile-bank, banking-data.sync-ledger.\n\n## Where this comes from\n\nWeight 13 of 100 in Accounting \u0026 invoicing: 9 of 69 use-case citations across 60 accounts, scaled to 100\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/accounting.capture-bill.json, or the MCP tool get_use_case with id accounting.capture-bill. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Turn a supplier invoice or receipt into a posted bill or expense",
        "url": ""
      }
    ],
    "description": "Turn a supplier invoice or receipt into a posted bill or expense: 0 companies fully do it, 13 with a limit, 13 carry the tag. Every listing in Accounting \u0026 invoicing with the reason and a source.",
    "facts": null,
    "h1": "Turn a supplier invoice or receipt into a posted bill or expense",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/accounting.capture-bill/",
    "published": "",
    "section": "agents",
    "title": "Turn a supplier invoice or receipt into a posted bill or expense |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/accounting.capture-bill/"
  },
  "tokens": {
    "markdown": 1550,
    "slim": 330
  },
  "version": 1
}
