Journal Entries

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

Scheduled Journal Entries

Scheduled journal entries are repeatable templates that generate ordinary journal entries on a due schedule. They belong with Journal Entries because the output is still a journal entry with lines, source metadata, and normal report impact.

Use scheduled entries for stable recurring adjustments such as accruals, amortization, allocations, or other balanced entries. A schedule can generate draft or posted entries, can be paused or completed, and carries traceability from each generated entry back to the source schedule.

REST routes for scheduled entries live under /api/v1/scheduled-journal-entries. MCP tools include create, list, update, delete, and post-due operations.

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
• create_scheduled_journal_entry
• list_scheduled_journal_entries
• update_scheduled_journal_entry
• delete_scheduled_journal_entry
• post_due_scheduled_journal_entries