Practice Manager API

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 /firm-partners/workspace/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

iduuid

Transaction identifier (UUID).

typeenum

Transaction type.

One of: EXPENSE, INCOME, TRANSFER

descriptionstring

Short description of the transaction.

amountnumber

Signed amount. Negative for money out, positive for money in.

currencystring

ISO 4217 currency code.

postedDatedate

Date the transaction posted (ISO).

authorizedDatedate

Authorization date when available.

accountIduuid

UUID of the account this transaction belongs to.

categoryAccountIduuid

UUID of the category account, when categorized.

vendorIduuid

UUID of the linked vendor, for expenses.

customerIduuid

UUID of the linked customer, when applicable.

billIduuid

UUID of the linked bill when this transaction is assigned as a bill payment; null when unassigned.

invoiceIduuid

UUID of the linked invoice when this transaction is assigned as an invoice payment; null when unassigned.

reviewedboolean

Whether the transaction has been reviewed.

tagsarray

Tags attached to the transaction.

createdAtdatetime

ISO 8601 creation timestamp.

updatedAtdatetime

ISO 8601 last update timestamp.

Example
{
  "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.

Endpoints

GET
List transactions/firm-partners/workspace/transactions

Returns a paginated list of transactions, newest first.

GET
Get a transaction/firm-partners/workspace/transactions/{uuid}

Retrieves a single transaction by its UUID.

POST
Create a transaction/firm-partners/workspace/transactions

Records a new transaction on an account.

POST
Bulk create transactions/firm-partners/workspace/transactions/bulk

Creates many transactions in a single request.

PATCH
Update a transaction/firm-partners/workspace/transactions/{uuid}

Updates fields on an existing transaction.

PATCH
Change transaction category/firm-partners/workspace/transactions/{uuid}/change-category

Re-categorizes a transaction to a different chart-of-accounts category.

PATCH
Bulk change transaction category/firm-partners/workspace/transactions/change-category-bulk

Categorizes or uncategorizes up to 100 existing transactions in one call.

POST
Bulk review transactions/firm-partners/workspace/transactions/review-bulk

Marks transactions as reviewed, or clears the reviewed flag, by UUID list.

PATCH
Bulk exclude transactions/firm-partners/workspace/transactions/exclude-bulk

Excludes or un-excludes transactions by UUID list or postedDate range.

POST
Assign to bills or invoices/firm-partners/workspace/transactions/{uuid}/assign-to-bills-invoices

Applies a transaction as payment against one or more bills or invoices.

PUT
Split a transaction/firm-partners/workspace/transactions/{uuid}/split

Splits a transaction into a parent row and child rows before bill or invoice assignment.

DELETE
Delete a transaction/firm-partners/workspace/transactions/{uuid}

Deletes a transaction from the workspace.

GET
List transaction receipts/firm-partners/workspace/transactions/{uuid}/receipts

Lists the receipts attached to a transaction.

POST
Add a transaction receipt/firm-partners/workspace/transactions/{uuid}/receipts

Adds one receipt holding every file sent, from public URLs or inline base64 content.

POST
Upload a transaction receipt/firm-partners/workspace/transactions/{uuid}/receipts/upload

Adds one receipt from multipart files.

PATCH
Update a receipt note/firm-partners/workspace/transactions/{uuid}/receipts/{receiptUuid}

Changes a receipt's note.

DELETE
Delete a receipt/firm-partners/workspace/transactions/{uuid}/receipts/{receiptUuid}

Removes a receipt and all of its images from a transaction.

GET
Get receipt image content/firm-partners/workspace/transactions/{uuid}/receipts/{receiptUuid}/images/{receiptImageUuid}/content

Returns one receipt image's file, base64-encoded.