Module

Stock Valuation

What the stock on hand is worth, on the method your auditor signed off.

Running in production₹20,000 / month

Watch demo

The auditor asks what the stock is worth. Two people give two answers, both defensible.

The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.

What it produces

  • Closing value per material at a plant, on the method this organization stated
  • The whole walk: every movement in order with the position after each, so the number can be checked
  • FIFO layers still open, and ageing from them — a fact on file rather than an estimate
  • A refusal, and no number at all, until a costing method is stated

A worked example

Identical movements, two lawful answers — which is why the method is stated
1 Jan receipt 100 @ ₹10 · 5 Jan receipt 100 @ ₹14 · 10 Jan issue 150 · 15 Jan receipt 50 @ ₹20 · 20 Jan issue 60
weighted average: (100×10 + 100×14) ÷ 200 = ₹12, then ₹16 after the third receipt → 40 on hand at ₹640
FIFO: the issues consume the ₹10s then the ₹14s, leaving the newest layer → 40 on hand at ₹800
₹640 against ₹800 on the same five rows: SIAARU will not pick one for your auditor

Illustrative numbers. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

Every inventory movement recorded here carries a unit cost, which is the input a costing method consumes — but nothing consumes it, and no method is declared anywhere in the product. LandedCost is sometimes read as this and is not: it spreads charges that were actually recorded across the lines of one shipment, which is a cost per unit landed, not a closing value on a balance sheet. Reading one as the other would overstate what this software does, so the difference is written here rather than left to be assumed.

Opened by the finance director and WAREHOUSE_MANAGER — what each of them sees first.

Said before you ask

What we don’t do.

SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.

Released, and three things it deliberately does not do. It computes no number until this organization states a costing method, because weighted average and FIFO give legitimately different answers on identical movements. It reports no ageing under weighted average — the average has already destroyed the age of what is on hand. And standard costing, with its price and usage variances, is not implemented: the two methods above are what is built.

Where this sits

One of 36 modules, on one engine.

Stock Valuation reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.