Create journal entry batch
Posts two or more journal entries as one batch, with a memo saying what the batch is for.
On each date, total debits must equal total credits. Every entry is checked before
anything is saved, and either the whole batch is saved or none of it is. The entries show
in reports like any other journal entries, with source_type manual_batch; no
transaction is created. Requires Transactions: Manage.
Errors name the entry they’re about, such as entries[3].category_id. A batch whose
dates don’t balance returns 400 journal_entries_unbalanced, naming each date with its
debit and credit totals. Only an entry in an expense category can have a department. An
entry in a reconciled account can’t be dated on or before that account’s last
reconciliation: 409 journal_entries_reconciled, naming the entry.
Authorizations
An API key prefixed with finta_, or the access token from a Finta CLI browser login (finta login), prefixed with finta_oat_. A CLI login's access token lasts one hour and the CLI renews it itself.
Body
Response
The created batch and its entries, in the order they were sent
Unique identifier with jmb_ prefix.
"jmb_a1b2c3d4e5f6g7"
journal_entry_batch What the batch is for. Null for batches made in Finta before memos existed.
"Accrue the last week of October payroll, paid November 3."
Where the batch was made. Any batch can be deleted through the API, whatever its source.
ui, api, mcp 2
Total of the batch's debits, in cents.
1800000
Total of the batch's credits, in cents.
1800000
The earliest entry date. Null for a batch without entries.
"2026-10-31"
The latest entry date. Null for a batch without entries.
"2026-10-31"
When the batch was created, as a Unix timestamp.
1793404800
The batch's journal entries, in the order they were sent.