API Reference

Expense Receipts

Expense receipts (pending receipts) capture out-of-pocket expenses before they are matched to bank transactions. Send the receipt image as multipart form data or as JSON (a URL or inline base64); read it back through the image content route.

Last updated 2026-11-18

Overview

The Expense Receipts API lets your integration list, upload, update, delete, and match pending receipts. Receipts can be linked to accounts, categories, vendors, projects, tags, and taxes using UUID fields.

Create and update take the receipt image as a multipart `receipt` file field, or in a JSON body as `receipt: { url }` or `receipt: { fileName, contentBase64, contentType? }`, so MCP tools can attach images too. Matched receipts cannot be updated or deleted until unmatched.

Key concepts

Multipart upload

POST and PATCH accept multipart/form-data with optional field `receipt` (image file, max 10 MB). Other fields are sent as form text fields with UUID values (accountUuid, categoryAccountUuid, vendorUuid, projectUuid, tagUuids, taxUuids).

Matching

POST /{uuid}/match-manually links an unmatched receipt to an expense transaction using `transactionUuid`. DELETE /{uuid}/unmatch removes the link.

Unmatched list

GET /unmatched returns only receipts where matched is false — useful for reconciliation workflows.

Split receipts

Pass `receiptSplited: true` with a `splits` array to allocate amounts across multiple category accounts. Split validation runs on create and update.

The expense receipt object

Fields returned on expense receipt records. receiptUrl is intentionally omitted from partner responses.

Attributes

iduuid

Expense receipt identifier (UUID).

amountnumber

Receipt amount (positive magnitude).

currencystring

ISO 4217 currency code.

datedate

Receipt date (ISO).

descriptionstring

Notes or memo for the receipt.

matchedboolean

Whether the receipt is linked to a transaction.

receiptSplitedboolean

Whether the receipt is split across multiple categories.

accountobject

Payment account for reimbursement.

categoryAccountobject

Expense category account.

vendorobject

Linked vendor, or null.

projectobject

Linked project, or null.

customerobject

Linked customer, or null.

tagsarray

Tags attached to the receipt.

taxesarray

Tax rates applied to the receipt.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "id": "44556677-8899-aabb-ccdd-eeff00112233",
  "amount": 45.99,
  "currency": "USD",
  "date": "2026-03-01",
  "description": "Team lunch",
  "matched": false,
  "receiptSplited": false,
  "account": {
    "uuid": "c8d9e0f1-a2b3-4567-cdef-789012345678",
    "name": "Business Checking"
  },
  "categoryAccount": {
    "uuid": "c3d4e5f6-a7b8-9012-cdef-123456789012",
    "name": "Meals & Entertainment"
  },
  "vendor": null,
  "project": {
    "uuid": "11223344-5566-7788-99aa-bbccddeeff00",
    "name": "Website Redesign"
  },
  "customer": {
    "uuid": "dfa3219e-6af8-4c53-997a-037534f63a35",
    "customer": "Acme Corporation"
  },
  "tags": [],
  "taxes": [],
  "createdAt": "2026-01-15T10:30:00.000Z",
  "updatedAt": "2026-01-28T14:22:30.000Z"
}

Matched receipts are locked

Update and delete return 400 when matched is true. Unmatch first, then edit or delete.

No receiptUrl in responses

Partner JSON omits receiptUrl, because the image sits in storage that anyone holding the URL can read. Read the image with GET /partners/expense-receipts/{uuid}/receipt/content, which returns it base64-encoded.

Recent changes

2026-11-18

Incremental sync: updatedSince on every list endpoint, includeDeleted, and the deleted-records feed

Every Partner API list endpoint now takes updatedSince, so an integration can pull only what changed instead of re-reading whole lists. Pass an ISO 8601 date-time and the list returns the records created or changed at or after it, oldest change first, with nextUpdatedSince and hasMore beside the rows; pass nextUpdatedSince back as updatedSince to read the next page, and keep it for the next poll once hasMore is false. Paging by cursor means a record changed mid-walk can no longer move between pages and be skipped, so updatedSince cannot be combined with page above 1 or a sort. includeDeleted=true returns deleted records with isDeleted: true on vendors, customers, products, people, taxes, projects, project tasks, tasks, time entries, recurring invoice templates, the chart of accounts, transactions, invoices, and bills. The chart of accounts returns a flat list of changed accounts in this mode, each naming its parent in parentAccountUuid. Records removed outright — tags, tag groups, journal entry lines, expense receipts, customer contacts, addresses and notes, budgets, and any other hard delete — are listed by the new GET /partners/deleted-records, which keeps 90 days. updatedFrom and updatedTo stay on transactions, invoices, and bills, now read as UTC when they carry no offset. The new Keeping in Sync guide (/guides/keeping-in-sync) puts the pieces together into a 15-minute poll with a sync-now button. The MCP catalog adds COUNT_list_deleted_records, and every list tool takes updatedSince (and includeDeleted where it applies) under query.

2026-11-18Breaking

Every attachment in COUNT through the API and MCP

Attachments can now be listed, added, read back and removed through the Partner API on bills, invoices, recurring invoice templates, transaction receipts, manual journal entries, tasks, expense receipts, Documents and reconciliation bank statements. Each record type gains an `attachments` (or `receipts` / `bank-statement`) route that takes JSON entries, either `{ url }` (COUNT downloads and keeps its own copy) or `{ fileName, contentBase64, contentType? }`, plus an `/upload` route for multipart files. Files are capped per route (5 MB for invoices, templates, transaction receipts and Documents, 10 MB for expense receipts, 20 MB for bills, journal entries and tasks, 25 MB for bank statements), at most 10 per request, virus-scanned, and saved together or not at all. A new `/content` route on each returns one file base64-encoded (up to 10 MB), and GET /partners/documents/{uuid}/download-links returns signed view and download links. Breaking: `documentUrl`, `receiptUrl`, `pdfUrl` and `bankStatementUrl` in responses are now short-lived signed links, and `null` when COUNT cannot prove the file is the workspace's. POST /partners/invoices/{uuid}/attachments now stores a copy of each file and answers 201 with `data.attachments` instead of 200 with `data.invoice`. Invoice upload responses no longer include internal ids (`invoiceId`, `defaultInvoiceAttachmentId`, `recurringInvoiceTemplateId`, `uploadedBy`). Bill create and update accept inline content in `attachments`, and an empty list adds nothing. Attachment adds and content reads are limited to 40 a minute per client and workspace. The MCP catalog adds 35 tools, including a Documents category, and content tools deliver the file as an embedded resource rather than as text.

2026-09-07

Accounting Playbooks and Ledger Semantics published as documentation

The workflows and behaviour rules the MCP server serves to agents through COUNT_playbooks and COUNT_knowledge are now readable documentation. Accounting Playbooks (/guides/playbooks) covers nine ordered workflows across 54 steps — invoicing, credit memos, recurring templates, vendor bill payment, chart-of-accounts setup, migration imports, budget planning and round-trip, and month-end review — each naming the exact tool per step. Ledger Semantics & Lifecycles (/guides/ledger-semantics) documents 33 confirmed behaviours across twelve resources: the state each operation is valid in, the fields accepted and then ignored, and the calls that cannot be undone, with every irreversible behaviour collected in one table at the top of the page. Both pages carry the COUNT_playbooks and COUNT_knowledge ids they were ported from so the agent-facing and human-facing copies stay in step. Playbooks, lifecycle sections, and individual behaviour rules are indexed into site search.

2026-06-21

Complete Partner API reference

Documented all remaining API reference groups: Chart of Accounts, Vendors, Products & Services, Recurring Invoice Templates, Credit Memos, Bills, Journal Entries, Tags, People, Projects, Tasks, Time Entries, Expense Receipts, Reports, and Workspace Stats. Added missing invoice endpoints (audit log, attachments, credit application, remove transaction) and group overviews for Invoices and Transactions.

Endpoints