Commit Inventory Revaluation

POST /inventory/inventory-revaluations/{id}/commit

Group: Inventory › Inventory Revaluations · Operation ID: commitInventoryRevaluation

Posts an inventory revaluation, so the stock value is restated and the difference moves to the balance sheet.

Posts the revaluation, so the cost adjustments are written, the inventory levels revalue, and a journal entry moves the difference on the balance sheet. The document becomes committed.

The platform's own checks run first and report every reason at once. A revaluation that cannot post answers VALIDATION_FAILED with errors, every reason and not just the first, so a caller with four things to fix is told all four. Nothing is written when it does.

The checks cover that the document is still a draft and has lines, that every cost is in the legal entity's functional currency, that batch quantities and serial entries match their lines, and that a costing element type is named.

totalRevaluationAmount on the response is what moved, negative for a write-down.

Open in the interactive reference

Parameters

Name	In	Type	Required	Description
`Api-Version`	header	`"v1"`	yes	The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`.
`Idempotency-Key`	header	string	no	An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored.
`id`	path	string	yes	The unique identifier for the revaluation to post.

Response

200 Success

Under data (commitInventoryRevaluationOutput):

Field	Type	Required	Description
`id`	string	yes	The unique identifier for the revaluation.
`documentStatus`	string	yes	The status the revaluation is now in, read back from the document. Possible values: 'DRAFT', 'COMMITTED', 'CANCELLED'.
`journalEntryId`	string	no	The unique identifier for the journal entry the commit wrote. Absent when the posting reported none. See id on GET accounting/journal-entries/:id.
`totalRevaluationAmount`	string (decimal)	no	What the document moved on the balance sheet, in the revaluation's currency. Negative for a write-down.
`warnings`	array of string	yes	Non-fatal advisories from the posting. An empty array on a clean run. The commit succeeded regardless of what is listed here.

Response headers

Idempotency-Replayed — Present and true only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as false.

Errors

Code	Status
`NOT_FOUND`	400
`WRONG_STATUS`	400
`VALIDATION_FAILED`	400
`POSTING_REJECTED`	400
`IDEMPOTENCY_KEY_CONFLICT`	409
`IDEMPOTENCY_PAYLOAD_MISMATCH`	422

Statuses

400 — Invalid request or business failure. Codes: NOT_FOUND, WRONG_STATUS, VALIDATION_FAILED, POSTING_REJECTED
401 — Missing or invalid access token
403 — Not authorized
404 — Not found
409 — The Idempotency-Key is still being processed by another request.
422 — The Idempotency-Key was already used with a different request payload.
429 — Too many requests
500 — Internal server error