API Reference
Transactions
Transactions are the individual money movements on a workspace account. Amounts are signed: negative for money out (expense) and positive for money in (income). All references (account, category, vendor, customer, tags) use UUIDs.
Last updated 2026-11-19
Overview
The Transactions API lets your integration list, create, update, categorize, and delete money movements on workspace accounts. Transactions are signed amounts — negative for money out (expenses) and positive for money in (income).
Partner responses expose UUIDs as `id` for the transaction and for linked account, category, vendor, customer, and tag records. Use bulk create to import many transactions in one call (up to 100 per request). Bulk exclude and bulk change-category support up to 100 existing rows with per-row failure reporting.
Key concepts
Categorization
Use change-category to assign or reassign a transaction to a chart-of-accounts category. Category changes may return `_partnerWarnings` when the update is partially applied.
Transfers between accounts
There is no separate transfer endpoint. Create a transaction, or change one transaction's category, with `categoryAccountUuid` set to another bank, cash, credit card or loan account, and COUNT records a transfer: the row becomes type `Transfer` and the other account gets its matching side. On change-category, `linkedTransferTransactionUuid` pairs the row with a transaction that already exists in the other account. List transfers with `transactionTypes=Transfer`. Bulk category change does not create transfers.
Payment assignment
Assign an expense transaction to bills or an income transaction to invoices with assign-to-bills-invoices. Use `matchingType` of `bill` or `invoice` and pass target UUIDs in `records`.
Bulk import
POST /partners/transactions/bulk accepts up to 100 transactions per call. Each object uses the same shape as create transaction.
Bill and invoice picker filters
To mirror the COUNT UI when listing transactions to assign to a bill, filter server-side: `transactionTypes=Expense`, `reviewed=false`, `pending=false`, `excluded=false`, `currency={billCurrency}`, and optionally `status=notAttachedBill` plus `status=notAttachedInvoice`. For vendor memos use `transactionTypes=Income`. Do not rely on client-side null checks alone — use these query params and the read-only `billId` / `invoiceId` fields on each row.
The transaction object
Core fields returned on transaction records.
Attributes
iduuidTransaction identifier (UUID).
typeenumTransaction type.
One of: EXPENSE, INCOME, TRANSFER
descriptionstringShort description of the transaction.
amountnumberSigned amount. Negative for money out, positive for money in.
currencystringISO 4217 currency code.
postedDatedateDate the transaction posted (ISO).
authorizedDatedateAuthorization date when available.
accountIduuidUUID of the account this transaction belongs to.
categoryAccountIduuidUUID of the category account, when categorized.
vendorIduuidUUID of the linked vendor, for expenses.
customerIduuidUUID of the linked customer, when applicable.
billIduuidUUID of the linked bill when this transaction is assigned as a bill payment; null when unassigned.
invoiceIduuidUUID of the linked invoice when this transaction is assigned as an invoice payment; null when unassigned.
reviewedbooleanWhether the transaction has been reviewed.
tagsarrayTags attached to the transaction.
createdAtdatetimeISO 8601 creation timestamp.
updatedAtdatetimeISO 8601 last update timestamp.
{
"id": "b7c8d9e0-f1a2-3456-bcde-678901234567",
"type": "EXPENSE",
"description": "Office supplies from Amazon",
"amount": -150,
"currency": "USD",
"postedDate": "2026-03-01",
"authorizedDate": "2026-03-01",
"notes": "Q1 office supplies",
"paymentChannel": "online",
"reviewed": false,
"excluded": false,
"pending": false,
"split": false,
"accountId": "c8d9e0f1-a2b3-4567-cdef-789012345678",
"categoryAccountId": "c3d4e5f6-a7b8-9012-cdef-123456789012",
"vendorId": "d4e5f6a7-b8c9-0123-defa-234567890123",
"customerId": null,
"billId": null,
"invoiceId": null,
"tags": [
{
"id": "e5f6a7b8-c9d0-1234-efab-345678901234",
"name": "Office"
}
],
"createdAt": "2026-03-13T08:30:00.000Z",
"updatedAt": "2026-03-13T08:30:00.000Z"
}Pay bills and invoices via transactions
Bill and invoice payment is transaction-centric — assign a bank transaction rather than calling a bill-specific pay route. See the Bills API for payment rules.Three ways to send a file
JSON `attachments` entries take a public `url` (COUNT downloads and keeps a copy) or the file inline as `contentBase64` (up to 10 MB). The `/upload` routes take `multipart/form-data`. All three are held to the same per-file cap and file types, at most 10 files a request, and every file is virus-scanned before anything is saved. To read a file back without following a link, call the attachment's `/content` route, which returns it base64-encoded.File links are signed per response
Any `documentUrl`, `receiptUrl`, `pdfUrl` or `bankStatementUrl` on COUNT storage comes back as a short-lived signed link, minted only after COUNT proves the file belongs to this workspace. Use it straight away and call again for a fresh one; do not store it. A file COUNT cannot prove is the workspace's comes back as `null`. A link you attached to an outside file is returned exactly as you sent it.Related
Recent changes
Fixed assets
The asset register is on the Partner API and MCP. /partners/fixed-asset-types lists, gets, creates, updates and deletes asset types (each with its cost, accumulated depreciation and depreciation expense accounts and default depreciation settings). /partners/fixed-assets lists the register (status, type, search, sort, paging), gets one asset with its posted depreciation, updates and deletes drafts, merges two drafts (POST /merge-drafts) and projects depreciation (GET /{uuid}/projected-depreciation-schedule). POST /{uuid}/register, /unregister and /dispose run the lifecycle; a disposal posts its catch-up depreciation and journal together and refuses a sale missing the account its outcome needs. GET and POST /{uuid}/journal-links and DELETE /{uuid}/journal-links/{linkUuid} manage the journal lines behind an asset's cost, GET /{uuid}/audit-log returns its history, and /{uuid}/attachments lists, adds (multipart or URL) and deletes its files. GET /partners/fixed-asset-depreciation-rates returns the country's reference rates. POST /partners/reports/depreciation-schedule, /asset-register and /fixed-asset-reconciliation generate the fixed asset reports. Bill lines and transaction category changes accept `fixedAssetAssignment` with `fixedAssetUuid` / `fixedAssetTypeUuid`. These routes need the new `fixed-assets` scope (a bare `read` / `write` grant includes it; the reports need `reports:read`) plus View Fixed Assets to read and Administer Fixed Assets to change. The same routes work on client workspaces under /firm-partners/workspace. The MCP catalog adds 22 fixed asset tools and 3 report tools.
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.
Line tags, foreign-currency rates, transfers and journal balance checks
Documented behaviour the reference was missing or had wrong. Bill lines take their own tags in `lineItems[].tagUuids`, which code that line's expense and tax postings, and manual journal lines take `lines[].tagUuids`; invoices take `tagUuids` for the whole document, on create and update. Bills and invoices in another currency are booked at the spot rate for their date, and `bookingExchangeRate` with `exchangeRateSource: "user"` sets your own rate; COUNT revalues open foreign AR, AP and accounts at each month end and posts realised gains and losses on payment. A transfer is a transaction categorized to another bank, cash, credit card or loan account, and change-category takes `linkedTransferTransactionUuid` to pair it with an existing row; bulk category change rejects those accounts. Journal entry create accepts unbalanced postings, while update requires debits to equal credits; the reference previously said create rejected them.
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.
Customer sub-resources, merge, GST settings, and the last bulk routes
Closed every remaining gap between the reference and the backend partner routes — 20 endpoints that existed in count-dev but had no documentation. Customers gained its sub-resources: contacts, addresses, and notes each get full list/create/update/delete coverage, plus GET /partners/customers/{uuid}/revenue-overview and the two-step merge flow (POST /partners/customers/merge/preview, then POST /partners/customers/merge), which repoints every record onto a target customer and cannot be undone through the API. Workspace gained GET and PATCH /partners/workspace/gst-settings, including the manage_settings permission the PATCH requires and the 409 that locks the accounting basis after a return is filed. Also documented GET /partners/invoices/generate/number, POST /partners/projects/bulk, and POST /partners/transactions/review-bulk. npm run check:parity now reports 173 documented routes against 173 backend routes.
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.
Connections, reconciliations, opening balance, workspace cutover, and transaction bulk ops
Documented Partner API groups for bank Connections (including Plaid Hosted Link connect/complete/reconnect), Reconciliations (create draft + complete), Opening Balance (get/set conversion balance), and Workspace (PATCH cutoverDate). Added PATCH /partners/transactions/change-category-bulk and exclude-bulk. Removed non-existent POST /partners/bills/bulk and /partners/invoices/bulk from the reference. Extended the MCP tool catalog with the matching COUNT_* tools plus remote-only COUNT_get_bulk_task_status and COUNT_remember/recall/forget.
Transaction split, COA balance, and bill-picker filters
Added PUT /partners/transactions/{uuid}/split for explicit transaction splits. Chart of accounts list now returns systemBalance when includeBalances=true. Documented bill-assignment list filters (reviewed, pending, excluded, currency, status) and exposed read-only billId/invoiceId UUIDs on transaction responses.
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
/partners/transactionsReturns a paginated list of transactions, newest first.
/partners/transactions/{uuid}Retrieves a single transaction by its UUID.
/partners/transactionsRecords a new transaction on an account.
/partners/transactions/bulkCreates many transactions in a single request.
/partners/transactions/{uuid}Updates fields on an existing transaction.
/partners/transactions/{uuid}/change-categoryRe-categorizes a transaction to a different chart-of-accounts category.
/partners/transactions/change-category-bulkCategorizes or uncategorizes up to 100 existing transactions in one call.
/partners/transactions/review-bulkMarks transactions as reviewed, or clears the reviewed flag, by UUID list.
/partners/transactions/exclude-bulkExcludes or un-excludes transactions by UUID list or postedDate range.
/partners/transactions/{uuid}/assign-to-bills-invoicesApplies a transaction as payment against one or more bills or invoices.
/partners/transactions/{uuid}/splitSplits a transaction into a parent row and child rows before bill or invoice assignment.
/partners/transactions/{uuid}Deletes a transaction from the workspace.
/partners/transactions/{uuid}/receiptsLists the receipts attached to a transaction.
/partners/transactions/{uuid}/receiptsAdds one receipt holding every file sent, from public URLs or inline base64 content.
/partners/transactions/{uuid}/receipts/uploadAdds one receipt from multipart files.
/partners/transactions/{uuid}/receipts/{receiptUuid}Changes a receipt's note.
/partners/transactions/{uuid}/receipts/{receiptUuid}Removes a receipt and all of its images from a transaction.
/partners/transactions/{uuid}/receipts/{receiptUuid}/images/{receiptImageUuid}/contentReturns one receipt image's file, base64-encoded.
