LedgerHQ
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. Partner apps should prefer resource posting endpoints for purchases, deposits, transfers, and bill payments; use journal entries for true journal adjustments.

REST Surface

MethodPathPurpose
GET/api/v1/entriesList journal entries
POST/api/v1/entriesCreate a draft entry
GET/api/v1/entries/:idGet an entry with lines
POST/api/v1/entries/:id/postPost a draft entry
POST/api/v1/entries/:id/voidVoid a posted entry
POST/api/v1/journal-entriesCreate a balanced posted journal 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, LedgerHQ 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_entries
  • get_entry
  • create_entry
  • post_entry
  • void_entry
  • create_journal_entry

Chart of Accounts

Account data used by LedgerHQ classification, reclass, and reports.

Banking & Reconciliation

Manage bank accounts, Plaid-connected bank activity, and reconciliation.

On this page

REST Surface
Reclass Behavior
MCP Tools