Skip to main content

Get Inventory Reconciliation Period Inventory

GET 
/api/ledger/reconciliation/inventory/period-inventory

The inventory side of one transaction-type concept for a period, amount-paired against that concept's ledger postings — the evidence behind Check A (SKU ledger minus SKU inventory).

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Check A is deliberately NOT reported per journal entry. Inventory movements are keyed by product, warehouse and date and attributed to a concept, not to an entry: a monthly batch consolidates thousands of movements into a single posting, and a cost revaluation recognises against a movement dated in an earlier period. So instead of a fabricated per-entry figure, both sides are listed and paired by signed amount. Matched pairs net to zero, which makes the unmatched remainder the whole of Check A.

match_group correlates a movement with the ledger posting of the same amount; null means unmatched. Unmatched rows are returned first — the matched pairs are definitionally not the finding.

Not every stream has rows to list. Amazon FBA stock is valued in its own subledger and stock in transit has no warehouse, so both move sku_moved without recording an inventory movement. itemised_total is what the listed rows sum to and unitemised_total is that remainder, so an empty list under a large sku_moved explains itself.

displaced_value is value whose stock had moved by the period end but whose posting an accounting lock date pushed later. The inventory side is already stated on the accounting calendar so both sides sit on the same dates — it is reported so a legitimately shifted posting is not read as a break.

meta.periods splits the SAME check_a across the accounting periods the window covers — one row per month, each with the inventory value that moved in it, what the ledger posted for it, and the difference. The rows are a partition of the window and sum back to meta.check_a exactly. This is the only evidence available for a stream valued in its own subledger: Amazon FBA records no inventory movement, so its data array is empty however large check_a is, and the period split is what localises the gap to a month. It is empty when the window is a single period (there is nothing further to split) or when the inventory side cannot be bucketed per period.

sku_moved and check_a are null — never 0 — when the scope's inventory side cannot be asked at all. A zero would claim the two sides agree.

Authenticate with a Personal Access Token. Reads cached data only.

Request​

Responses​

OK

Response Headers
    Content-Type