Record depreciation

Operation ID: recordDepreciation

Group: Accounting › Fixed Assets › Depreciation Schedules

Open in the interactive reference

POST /fixed-assets/depreciation-schedules/record

Retry-safe: A write that accepts Idempotency-Key: repeating a request with the same key replays the stored answer instead of executing twice.

Records depreciation for the depreciation schedule lines you send. It creates one journal entry for each schedule. Each journal entry is dated postingDate. It debits the depreciation expense account and credits the accumulated depreciation account of the fixed asset's depreciation policy.

This endpoint records only the lines you send, whatever their dates. It does not find the lines that are due.

If you send 35 line ids or fewer, the response comes back after the recording is finished. Either all the lines are recorded, or none are, and the response explains why.

If you send more than 35 line ids, the response comes back straight away, with asyncExecution set to true, and the lines are recorded afterwards. The response cannot tell you about errors, such as a line that is already recorded or a closed accounting period. A very large recording is saved in parts. If it stops because of an error, the parts saved before the error stay recorded. To check how much was recorded, read depreciatedAmount on the schedules, or list journal entries with the type 'depreciation' on GET accounting/journal-entries.

The request fails with TASK_ALREADY_RUNNING while another depreciation recording is running for the same legal entity and book. This includes recordings started in Lensing.

Parameters

Name In Type Required Description
Api-Version header string · 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.

Request body

Required, application/json: recordDepreciationInput.

Field Type Required Description
lineIds array<number> yes The internal numbers of the depreciation schedule lines to record. Send at least one. An id that matches no line is skipped, as long as at least one id matches. A line that is already recorded cannot be recorded again, and sending one fails the request. Example: [101,102,103].
postingDate date yes The posting date of the journal entries that recording creates. Format: YYYY-MM-DD. The date must fall in an accounting period of the legal entity's book that is open for posting. It does not have to fall in the period the lines belong to. Example: "2026-09-30". 
{
  "lineIds": [
    101,
    102,
    103
  ],
  "postingDate": "2026-09-30"
}

Response

200 Success

Under data (recordDepreciationOutput):

Field Type Required Description
asyncExecution boolean yes Whether the recording was queued to run in the background. True when you sent more than 35 line ids. When true, the journal entries do not exist yet, and a problem with the lines is not reported in the response. Example: false.
lineCount number yes The number of line ids you sent, including duplicates and ids that match no line. It can be more than the number of lines recorded. Example: 3. 
{
  "data": {
    "asyncExecution": false,
    "lineCount": 3
  },
  "diagnostics": [
    {
      "code": "<code>",
      "message": "<message>",
      "severity": "error",
      "path": [
        "<path>"
      ],
      "details": "<details>"
    }
  ]
}

Response headers

Errors

Code Status
NO_LINES 400
LINES_NOT_FOUND 400
INVALID_SCHEDULE_STATE 400
TASK_ALREADY_RUNNING 400
IDEMPOTENCY_KEY_CONFLICT 409
IDEMPOTENCY_PAYLOAD_MISMATCH 422

Statuses