API Reference
Journal Entries
Journal entries are manual double-entry postings to the general ledger. Each posting has a memo, date, optional reference number, and balanced debit/credit lines that reference chart-of-accounts UUIDs.
Last updated 2026-11-18
Overview
The Journal Entries API lets your integration list, read, create, bulk-create, update, and delete manual journal postings in a workspace. Each posting must balance: every line carries exactly one of `amountDebit` or `amountCredit`, never both and never neither.
Partner mutation bodies use `accountUuid` on each line (the `id` from chart of accounts). System-generated entries from invoices, bills, payroll, and other integrations are read-only — update and delete return 400 for those sources.
Key concepts
Balance checks
Each line requires `accountUuid` plus exactly one of `amountDebit` or `amountCredit`. Create and bulk create accept a posting whose debits do not equal its credits, for period-close accruals, payroll clearing and imports, so check balance yourself if you need it. Update rejects an unbalanced `lines` array with 400. Postings COUNT builds for bills, invoices and transactions are always balanced.
Account UUID resolution
Copy account UUIDs from chart of accounts (`id`, `accUuid`, or `accountUuid` fields — any UUID-shaped value from list accounts works). Do not pass numeric internal account ids.
Manual entries only
Only manually-created entries (and Square integration entries) can be updated or deleted. System-generated entries return 400.
Bulk partial success
Bulk create processes up to 100 postings independently. Response: `{ successCount, errorCount, results: [{ index, success, journalEntry? | error? }] }` with HTTP 201 even when some rows fail.
The journal entry line object
List and mutation responses return an array of lines sharing the same `journalLinkUuid`. Each line represents one debit or credit leg.
Attributes
iduuidLine identifier (UUID). Pass in the path to update or delete the posting group anchor line.
descriptionEntrystringPosting memo shared across all lines in the entry.
descriptionLinestringOptional per-line description.
datedatePosting date (ISO YYYY-MM-DD).
refNumberstringOptional reference number.
amountDebitstringDebit amount as a decimal string, or null when this line is a credit.
amountCreditstringCredit amount as a decimal string, or null when this line is a debit.
accountUuiduuidChart-of-accounts UUID for this line.
accountobjectEmbedded account summary when included on list responses.
journalLinkUuiduuidShared link id grouping all lines in the same posting.
createdAtdatetimeISO 8601 creation timestamp.
updatedAtdatetimeISO 8601 last update timestamp.
{
"id": "f1a2b3c4-d5e6-7890-abcd-ef1234567890",
"descriptionEntry": "Accrue March rent",
"descriptionLine": "Rent expense",
"date": "2026-03-01",
"refNumber": "JE-2026-003",
"amountDebit": "2500.00",
"amountCredit": null,
"accountUuid": "c8d9e0f1-a2b3-4567-cdef-789012345678",
"account": {
"id": "c8d9e0f1-a2b3-4567-cdef-789012345678",
"name": "Rent Expense",
"type": "Expenses"
},
"journalLinkUuid": "a9b8c7d6-e5f4-3210-abcd-ef9876543210",
"createdAt": "2026-01-15T10:30:00.000Z",
"updatedAt": "2026-01-28T14:22:30.000Z"
}withCaution bypasses period checks
Pass `withCaution: true` on create (sparingly) to skip book-closeness checks. Manual entries can still fail when a line posts into a reconciled period for that account.Bulk performance
Bulk create resolves all account UUIDs in a single batched lookup across the whole batch — prefer bulk over repeated single creates for large imports (~25 postings per batch recommended).Update replaces all lines
PATCH sends the full replacement `lines` array with the same shape as create. Partial line patches are not supported.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
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.
Cash flow forecast, GST return and audit report, tax codes, workspace events, and 17 MCP tools
Documented the six partner routes the reference was missing. POST /partners/reports/cash-flow-forecast forecasts cash for the next 13 weeks, with an optional what-if scenario (customer payment delays, bill payment dates and one-off or repeating adjustments) returned as scenarioForecast. GET /partners/reports/gst-return calculates an NZ GST return without filing it, including the reconciliation that decides whether COUNT would let it file, and GET /partners/reports/gst-audit-report lists the transactions behind it, flags the ones with a GST issue, and pages 200 rows at a time. GET /partners/taxes lists the workspace tax codes and their UUIDs. GET /partners/workspace-events returns what changed since the user last checked: invoices paid, failed invoice payments, new bills and bank feed syncs. GET /partners/journal-entries/{uuid} returns one posting with every line. Taxes and workspace events are also reachable through the Practice Manager client-workspace routes. npm run check:parity now reports 186 documented routes against 186 backend routes. The MCP catalog adds COUNT_list_taxes, COUNT_list_workspace_events, COUNT_get_journal_entry, COUNT_generate_cash_flow_forecast, COUNT_get_gst_return, COUNT_get_gst_audit_report, COUNT_propose_transaction_categories, four position tools (COUNT_get_all_positions, COUNT_create_position, COUNT_update_position, COUNT_delete_position), and five firm tools for client status and client questionnaires. COUNT_delete_project is now COUNT_archive_project, and DELETE /partners/projects/{uuid} is documented as the archive it is, with its real response (result.success). Also, COUNT_get_bulk_task_status, which the server no longer registers, is removed.
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.
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/journal-entriesReturns a paginated list of journal entry lines.
/partners/journal-entries/{uuid}Returns one posting with every line, in entry order.
/partners/journal-entriesCreates a manual journal entry posting.
/partners/journal-entries/bulkCreates up to 100 journal entry postings in one request with partial-success semantics.
/partners/journal-entries/{uuid}Updates a manually-created journal entry by UUID.
/partners/journal-entries/{uuid}Deletes a journal entry posting by UUID.
/partners/journal-entries/{uuid}/attachmentsLists the files attached to a manual journal entry.
/partners/journal-entries/{uuid}/attachmentsAdds files to a manual journal entry from public URLs or inline base64 content.
/partners/journal-entries/{uuid}/attachments/uploadAdds files to a manual journal entry via multipart form data.
/partners/journal-entries/{uuid}/attachments/{attachmentUuid}Removes one attachment from a manual journal entry.
/partners/journal-entries/{uuid}/attachments/{attachmentUuid}/contentReturns a journal entry attachment's file, base64-encoded, with its note.
