API Reference
Reconciliations
Start a bank reconciliation draft for an account statement period, correct or delete it while it is a draft, then complete it to mark reviewed journal entries as reconciled.
Last updated 2026-10-03
Overview
The Reconciliations API creates a draft reconciliation for a bank/cash account statement period, lets you correct or delete the draft, and completes it once the ending balance is verified.
Completing a reconciliation is the only Partner API way to set `reconciled: true` on transactions/journal entries — there is no direct writable field for it.
Key concepts
Create then complete
POST /partners/reconciliations creates a DRAFT. PATCH /partners/reconciliations/{uuid}/complete locks it and stamps reviewed journal entries in the period as reconciled.
Opening balance is automatic
The earliest open draft opens on the account’s last completed reconciliation, and each later draft opens on the ending balance of the draft before it. You only supply endingBalanceDate and endingBalanceAmount; updating or deleting a draft re-derives the opening balance of every later draft.
Correcting a draft
PATCH /partners/reconciliations/{uuid} changes the ending date and/or amount of a draft. DELETE /partners/reconciliations/{uuid} removes a draft so you can create the right one; a draft has reconciled nothing, so no transactions or journal entries change. Completed reconciliations are undone in COUNT, not through the API.
Date ordering
Reconciliations must complete in date order. Create and update reject if a draft/completed reconciliation already exists for that date, or if a later completed reconciliation already exists for the account.
autoReconcile
On complete, `autoReconcile: true` also marks unreviewed entries in the period as reviewed and reconciles them. Defaults to false — only what a human already reviewed.
The reconciliation object
Draft or completed reconciliation for one account and statement ending date.
Attributes
iduuidReconciliation UUID. Pass to update, delete, or complete.
accountUuiduuidAccount UUID from the chart of accounts (bank/cash account).
endingBalanceDatedateStatement ending date (YYYY-MM-DD).
endingBalanceAmountnumberStatement ending balance.
statusstringTypically draft until completed.
{
"id": "778899aa-bbcc-ddee-ff00-112233445566",
"accountUuid": "c8d9e0f1-a2b3-4567-cdef-789012345678",
"endingBalanceDate": "2026-03-31",
"endingBalanceAmount": 12500.45,
"status": "draft"
}Closed books
Complete rejects with 400 if the ending balance date falls in a book-closed sealed period.MCP equivalents
COUNT_create_reconciliation, COUNT_update_reconciliation, COUNT_delete_reconciliation, and COUNT_complete_reconciliation.Bank statements
Attach a statement to a draft with POST /{uuid}/bank-statement (URL or inline base64) or POST /{uuid}/bank-statement/upload (multipart), up to 25 MB. It is filed in Documents under Bank Statements/{account name}, named for the statement period, and read back with GET /{uuid}/bank-statement/content. `bankStatementUrl` on a reconciliation is a signed link to use straight away.Related
Recent changes
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.
Bill submit and refunds, reconciliation drafts, report filters, 30 MCP tools, and the Claude plugin
Documented the five partner routes the reference was missing: POST /partners/bills/{uuid}/submit, POST /partners/bills/{uuid}/assign-transaction (pay a bill, or refund a vendor memo with an income transaction), PATCH /partners/invoices/{uuid}/add-transactions (including credit memo refunds), and PATCH and DELETE /partners/reconciliations/{uuid} for correcting or discarding a draft. The account transactions report gains a reference-number range (checkNumberFrom/checkNumberTo) and the unknown-counterparty drill-down (unknownCustomerAr/unknownVendorAp), both accrual-only. Invoice and credit memo lines accept free-text Custom lines with categoryAccountUuid and name. Corrected the reference where it disagreed with the backend: dueDate is required on invoices and estimates, bills move through submitted and rejected as well as draft and approved, and a bill does have its own assign-transaction route. npm run check:parity now reports 178 documented routes against 178 backend routes. The MCP catalog adds 30 tools — customer contacts, addresses, notes, merge and revenue overview, GST settings, bill submit and memo refunds, reconciliation draft update/delete, COUNT_find_tool, COUNT_report_problem, and saved AI skills — moving the advertised count from 180 to 210. New pages cover the COUNT Claude plugin (/tools/claude-plugin) and the MCP brain, workspace memory and problem reports (/guides/mcp-brain-and-memory), and the FAQ gains the connector and API topics COUNT_knowledge serves to agents.
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.
Endpoints
/partners/reconciliationsCreates a draft reconciliation for an account statement period.
/partners/reconciliations/{uuid}Corrects the ending date and/or ending balance of a draft reconciliation.
/partners/reconciliations/{uuid}Deletes a draft reconciliation.
/partners/reconciliations/{uuid}/completeLocks a draft reconciliation and marks reviewed journal entries reconciled.
/partners/reconciliations/{uuid}/bank-statementAttaches one bank statement to a draft reconciliation, from a public URL or inline base64 content.
/partners/reconciliations/{uuid}/bank-statement/uploadAttaches one bank statement to a draft reconciliation via multipart form data.
/partners/reconciliations/{uuid}/bank-statement/contentReturns a reconciliation's bank statement, base64-encoded.
