Creates journal entries in batch. Journal entry numbers are not required to be unique — duplicate numbers are allowed and will create separate records.
Security
The requesting user must have the following permission to create journal entries:
- General Ledger → Journal Entries → Create Journal Entries
Identifies the R365 tenant the request applies to. Required on every request.
Creates journal entries in batch.
Collection of journal entries to create. Required.
Unique journal entry number. Required.
Document date for the journal entry in ISO 8601 format. Required.
Unique identifier (GUID) of the location. Required.
Optional comment or memo for the journal entry header.
Entry type classification. Must be "Standard". Defaults to "Standard" if not specified.
Collection of detail lines. Required; total debits must equal total credits.
Unique identifier (GUID) of the general ledger account. Required.
Debit amount for this detail line. Mutually exclusive with creditAmount; one must be greater than zero.
Credit amount for this detail line. Mutually exclusive with debitAmount; one must be greater than zero.
Optional location override for this detail line. Defaults to the header location if not specified.
Optional comment for this detail line.
Multi-Status – batch operation result containing per-item success or failure.
Collection of results, one per journal entry in the original request, ordered by request index.
Zero-based position of this journal entry in the original request.
Journal entry number from the original request.
Outcome of the create operation.
Machine-readable error code. Present only when status is Failed.
Human-readable error description. Present only when status is Failed.
Unique identifier (GUID) of the created journal entry. Present only when status is Succeeded.
Bad Request — a parameter value is malformed, of the wrong type, or outside its allowed range.
Unauthorized — the bearer token is missing, invalid or expired, or is not valid for the specified tenant.
Forbidden — the caller lacks the permission required for this operation.
Not Found — the requested resource does not exist, or the supplied continuation token is unknown or has expired.
Conflict — the request conflicts with the current state of the resource and cannot be applied.
Unprocessable Entity — a required parameter is missing, or a supplied parameter value is invalid.
Too Many Requests — the caller has exceeded the rate limit; retry after a short delay.
Internal Server Error — an unexpected error occurred while processing the request.