SIGNALS Docs
Reader View

Asset Ledger

The append-only ledger that records every stock movement and keeps quantity on hand accurate.

Overview

The asset ledger records each movement against an asset and adjusts its quantity on hand. Entries cannot be edited or deleted; a correction appends a reversal so the movement history remains available.

View movements from the asset detail page (/assets/{id}). Each entry belongs to one asset.

Movement types

A movement type determines whether the quantity adds to or reduces held stock. Manual adjustments can use the following types:

Type Direction
purchased Adds
found Adds
written_off Reduces
sold Reduces
built Adds

The system records opening, increase, decrease, returned, transfer_out, transfer_in, stock_check_increase, and stock_check_decrease for operations such as opening balances, reversals, transfers, and counts.

Quantities and adjustments

Each entry records a positive quantity. The type determines its signed movement, which changes the asset's quantity on hand. Adjustments accept up to eight whole digits and two decimal places, matching quantity on hand; a barcoded asset can move only one unit at a time. Quantities and signed movements are returned as exact two-decimal strings. The quantity update and ledger entry are written together.

From the asset detail page, choose Add Adjustment, then choose a type, quantity, date, and optional description. The held quantity updates immediately.

An unreversed manual adjustment can be reversed from the asset detail page. Reversal appends an opposite movement for the same quantity and links it to the entry being corrected. System-generated movements and adjustments that have already been reversed cannot be reversed. A reversal is refused if it would make held stock negative.

API access

The asset in each path determines the ledger being accessed:

GET  /api/v1/assets/{asset}/ledger
GET  /api/v1/assets/{asset}/ledger/{entry}
POST /api/v1/assets/{asset}/adjustments
POST /api/v1/assets/{asset}/ledger/{entry}/reverse

Both POST operations require an idempotency key. The adjustment body supplies the movement type and quantity; it does not need an asset identifier. See the API reference for request and response details.