Skip to content
Open appBook a five-day pilot

Place asset in service

POST/api/v1/fixed-assets/{asset_id}/place-in-service

Place an asset in service to begin depreciation.

This changes the asset status from 'draft' to 'active' and sets the in-service date from which depreciation will be calculated.

  • capitalization: "purchase" (default) posts DR asset / CR Accounts Payable.
  • capitalization: "opening_balance" is for an asset already on the books at go-live: it posts DR asset / CR accumulated (opening amount) / CR offset_ledger_id, or no journal entry when no offset is given. Only months from go_live_date on are scheduled, so the opening balance is never posted twice.
Operation ID: place_asset_in_service·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Parameters

Path

asset_idstringrequired

Request body

Schema: PlaceInServiceRequest

in_service_datestring · daterequired

Date asset starts depreciating

capitalizationstring

'purchase' (default) posts DR asset / CR Accounts Payable for the full cost. 'opening_balance' is for an asset already on the books at go-live: it posts against offset_ledger_id, or nothing at all when no offset is given.

One of: purchase, opening_balance

offset_ledger_idstring

Opening-balance mode only: the account the opening entry credits (e.g. Opening Balance Equity). Omit to post no journal entry.

opening_accumulated_depreciationinteger

Opening-balance mode only: depreciation/amortization recognised before go-live, in cents (overrides the asset's stored value)

go_live_datestring · date

Opening-balance mode only: first month DayZero posts (overrides the asset's stored value)

Responses

201Successful Response

Schema: SuccessEnvelope_FixedAssetResponse_

successboolean
messagestring
codestring
dataFixedAssetResponse

401Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: ErrorResponse

errorstringrequired

Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.

messagestringrequired

Human-readable explanation, safe to show to end users.

codestringrequired

Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).

request_idstring

Correlation id for support requests. Echoes the x-request-id request header when one was supplied.

errorsobject

Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

403Forbidden - Insufficient permissions

Schema: ErrorResponse

errorstringrequired

Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.

messagestringrequired

Human-readable explanation, safe to show to end users.

codestringrequired

Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).

request_idstring

Correlation id for support requests. Echoes the x-request-id request header when one was supplied.

errorsobject

Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

422Validation Error

Schema: ErrorResponse

errorstringrequired

Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.

messagestringrequired

Human-readable explanation, safe to show to end users.

codestringrequired

Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).

request_idstring

Correlation id for support requests. Echoes the x-request-id request header when one was supplied.

errorsobject

Field-level validation messages keyed by field name. Present on 400/422 validation failures only.