Journals Realtime-enabled
GETPOSTPATCHDELETETable: Gen. Journal Batch
General journal batches with a nested journalLines collection. Lines resolve their account and balancing account polymorphically (G/L or Bank) and support apply-to settlement by integrationId.
Recording payments is handled through dedicated payment endpoints layered on the journals subsystem. See Customer Payments and Vendor Payments.
Sharing a batch with staged documents
A journal batch is shared territory. The journal wrapper endpoints draft their own general journal lines into whatever batch their Journal Wrappers setup names, and out of the box that is the same GENERAL/DEFAULT batch a journals caller reaches for. Those drafted lines belong to a staged document that carries its own approval and processing rules, so this endpoint treats them as someone else's and leaves them alone.
The rule is ownership, not batch reservation: raw journals and staged documents can share one batch without either disturbing the other, so there is nothing to reconfigure.
postskips lines drafted by a staged document and posts only the lines written through this endpoint. If the batch holds nothing but staged lines, the action reports that rather than posting them or silently doing nothing.DELETEon a journal is refused while the batch holds staged lines. Deleting a batch takes its lines with it, so there is no partial delete to fall back on. Post or cancel those documents through the endpoint that created them, then delete the journal.
Staged lines stay readable through journalLines, so the batch reconciles as a whole. They are just not yours to post, change, or delete. To post a staged document, use the endpoint that created it.
Bound actions
Invoke with POST /journals(<id>)/Microsoft.NAV.<action>:
post: posts the batch's own lines through Business Central's Gen. Jnl.-Post, exactly as posting the batch in the client would, minus any lines belonging to a staged document. It errors if the batch has no lines of its own to post; on success the response redirects back to the journal batch, which is now empty apart from any staged lines that were skipped.
shortcutDimension1Code–8Code are writable on the journal lines, not the batch. See Dimensions.