AWRA OpsHub Search

Stock Value and the Branch on the Ledger

Ask our stock reports what the Christchurch warehouse is holding and you get an answer. Ask the ledger and you now get half of one: a journal entry carries a branch, so the income statement splits by site, while the balance sheet stays one figure for the organisation. Two views of the same goods, and the line between them has moved.

Inventory Insights AWRA OpsHub Team 10 min read

A New Zealand business with a North Island and a South Island operation is one company that behaves like two, and every reporting question it asks eventually runs into the same wall: can this number be split?

For stock, yes. For the ledger, partly — and where it stops is easy to state and expensive to discover late.

The two views

Physical stock is held per warehouse and per bin location. Every movement records where it happened. Valuation, counting, transfers and reporting all work at that granularity, and a per-site stock report is an ordinary thing to ask for.

The ledger underneath is a different shape. A journal entry carries an account, an amount, a reference, a description, and a link to the adjustment or item that produced it — and a branch, a department and a project wherever the flow that produced it knows them: a till sale its branch, a stock adjustment its warehouse, payroll its department, a supplier bill all three.

So the income statement can be cut by branch, department or project, with an Unassigned column for anything untagged. The balance sheet is not, deliberately: it balances only if every leg of every entry carries the same tag, so the inventory asset account still has one balance for the organisation. The two views are consistent with each other, and the stock view is still the only one that cuts every figure by site.

The stock knows where it is. The profit knows where it was earned. The balance is still one number.

Where the wall is actually hit

The question Where the answer comes from Available?
What is on hand in Christchurch? Stock reports, per warehouse Yes
What is Christchurch stock worth? Stock valuation, per warehouse Yes
What did Christchurch consume this month? Movement history, per warehouse Yes
What did Christchurch earn this month? The income statement, by branch Yes, for postings that carry a branch
What is the inventory asset balance for Christchurch? The ledger No — the balance sheet is one figure for the organisation
What is the trial balance for the South Island? The ledger No — the trial balance reads the ledger whole
Do stock and ledger agree overall? The internal integrity check Yes, and this is genuinely built

The last row deserves its place. There is an integrity check that compares the ledger against stock, against open purchase orders, and debits against credits, and it works. What it cannot do is tell you which site a discrepancy came from.

The distinction that gets blurred in demonstrations

A vendor showing you per-warehouse stock reports is showing you something real. It is easy — for everybody in the room, including the vendor — to take that as evidence that the financial side is dimensioned too. It is a reasonable inference, and here it is half right: the income statement is dimensioned, the balance sheet is not.

The test is not whether stock can be filtered by site. It is whether an account balance can. Ask for the inventory asset account for one branch, not for the stock on hand at one branch. Those sound like the same question and they come from different halves of the system.

What to do about it

  1. Decide early whether you need a branch balance sheet

    A branch profit-and-loss is the income statement filtered by branch. A branch balance sheet is a different matter: if it is a real business requirement rather than a preference, the shape that works is one organisation per branch, with consolidation outside. That is a significant decision with real costs — separate logins, separate masters — and it is far cheaper before go-live than after.

  2. If you do not, use the stock side and stop asking the ledger

    Most operational management is answerable from the physical view: what is where, what moved, what it is worth. The ledger question is usually a reporting habit rather than a requirement, and it is worth checking which one it is.

  3. Use departments where they do reach

    A purchase order carries a department, budgets are held per department, and a supplier bill carries its department, branch and project onto the journal, so spending is dimensioned in the ledger as well as in the budget. That covers more management questions than people expect.

  4. Do the balance-sheet split in your reporting layer

    Export by warehouse, tag it yourself, and consolidate. Unromantic, and the standard answer for the balance sheet until it can be cut the way the income statement now is.

The dimension ledger, precisely

What AWRA OpsHub does today

  • Stock held, valued, counted, moved and reported per warehouse and per bin location.
  • Departments on purchase orders, and budgets held per department and category.
  • Projects on stock issues and on purchase orders, with issued material costing into a job.
  • One cost basis shared by the till, the journal, margin analytics and the stock-integrity check, so those four cannot disagree with each other.
  • An internal integrity check reconciling the ledger against stock, against open orders, and debits against credits.
  • A branch, a department and a project on journal entries wherever the source flow knows them — till sales, stock adjustments, payroll, supplier bills — and line by line on a manual journal.
  • An income statement for any date range, broken down by branch, department or project, with an Unassigned column.
  • Manual journal entries, so a dimension can also be introduced by an adjusting entry.
  • A period posting lock — a closed month refuses a backdated posting.

More we can add to your workspace

  • A trial balance cut by branch, department or project. The dimensions are on the journal; the trial balance reads it whole. Commission it
  • A per-branch balance sheet. The per-branch profit and loss is the income statement filtered by branch. Commission it
  • Consolidation across organisations, which is the shape you would use to get full branch accounts. Commission it

Where we point you to a specialist

  • The physical view genuinely is dimensioned, and it answers most operational questions. This page is about the financial view only, and the difference between them is easy to miss.
  • One organisation per branch is a real option with real costs. It is the right answer when branch accounts are a requirement and the wrong one when they are a preference.
  • This is market-neutral. It is what happens to any two-site business; New Zealand is where the two sites are most likely to be run as two operations.

More we can add for you

What we can build for your market on top of the standard product

Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a local payroll engine, a rate with a date on it, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.

Dated rates and the periods your obligations actually use

Effective-dated tax rates, so a document raised about a past period is computed against the rate that applied then rather than the rate that applies now, and a credit note that carries the tax split of the supply it reverses. Where a jurisdiction operates a sales-monitoring or fiscalisation scheme, data produced in the published format alongside the approved equipment rather than in place of it.

Banks, payments and pay periods that are not months

Bank statement feeds and local payment rails wired into the Payments Register, and a payroll period that matches your statutory pay cycle rather than the calendar month our schema assumes today. The second is a data-model change and we would quote it as one.

The operational work, which is what most commissions actually are

An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.

Payroll and statutory returns

Income tax, superannuation or provident fund contributions computed on live employee records against your own pay cycle, with the returns produced in the layout your authority expects.

Systems you already run

The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.

How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.

Tell us what you need integrated

Our position

Decide the branch-accounts question before you configure anything, because it decides how many organisations you set up and that is not a decision you revisit. If you need a branch balance sheet, run one organisation per branch and consolidate outside; if a branch profit and loss is enough, one organisation with its postings tagged by branch gives you it. If you need branch operations, the stock side already gives you everything and the ledger question was never the one you meant.

Three questions that separate a stock filter from a real dimension

Show me the inventory asset account balance for one branch.

A good answer sounds like

A filtered account balance, not a stock report.

What it actually means

This is the question. Per-warehouse stock reporting is not evidence that the ledger is dimensioned, and the two are easy to conflate in a demonstration.

What dimensions does a journal entry carry?

A good answer sounds like

A named list.

What it actually means

Ours carries a branch, a department and a project. Ask next which flows fill them in, because a dimension nobody tags is a column of Unassigned.

Can I post a manual journal to correct a dimension?

A good answer sounds like

Yes, with dimensions on it.

What it actually means

Ours does: a manual journal can tag each line with its own branch, department or project — which is also why the balance sheet is not filtered by dimension.

How would you give me branch accounts?

A good answer sounds like

An honest architecture answer.

What it actually means

If the answer is "a filter", ask them to show it. If it is "separate entities", that is the same answer we give, and it is the honest one.

Answer the branch question once

One organisation or several is the decision everything else follows from, and it is nearly free before go-live. Tell us how your sites report and we will tell you which shape fits.

Decide the shape

Frequently asked questions

Could a custom field on the journal give me a branch?

It does not need to. A journal entry carries a branch, a department and a project as real fields, and the income statement filters and breaks down by them. A custom field would be the wrong tool anyway: a dimension has to be understood by the reporting engine to be worth anything, not merely stored.

Does the stock-versus-ledger integrity check still work with multiple warehouses?

Yes — it reconciles the organisation as a whole, which is the level the ledger operates at. What it cannot do is attribute a discrepancy to a site, so investigating one is a manual comparison against per-warehouse stock reports.

Is one organisation per branch really the recommendation?

Only where branch accounts are a genuine requirement — a separate legal entity, a local filing, or a partner who owns part of one site. For internal management reporting the stock view and the income statement by branch usually carry it, and splitting into several organisations costs you cross-site visibility you will miss immediately.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center