Modules
Journal Entries
Posted accounting entries behind reports and transaction reclass.
Journal entries are documented here only as the accounting spine behind the LedgerHQ workflow. They matter because financial reports are built from posted entries, and transaction reclass may update a linked non-bank journal line.
REST Surface
| Method | Path | Purpose |
|---|---|---|
GET | /api/v1/entries | List journal entries |
POST | /api/v1/entries | Create a draft entry |
GET | /api/v1/entries/:id | Get an entry with lines |
POST | /api/v1/entries/:id/post | Post a draft entry |
POST | /api/v1/entries/:id/void | Void a posted entry |
Reclass Behavior
POST /api/v1/bank-transactions/:id/reclassify updates the bank transaction's
classification fields first. If the transaction has a linked journal entry,
DollarBooks can also update the selected non-bank journal line.
Rules:
- Period-locked entries return a validation error.
- Void entries cannot be reclassified.
- Multi-line entries require
journalLineId. - Debit and credit amounts are preserved; only the target account changes.
MCP Tools
list_entriesget_entrycreate_entrypost_entryvoid_entry