Multi-Branch Operations: Keeping Stock and Cash in Sync

Opening a second location is a milestone. Opening a third is usually when the numbers start to argue with each other. The stockroom says it holds forty units, the consolidated report says twenty-two, and nobody can say which one is wrong without sending someone to count. The same thing happens with cash: one branch reports collections daily, another submits a summary at the end of the week, and the difference looks like a discrepancy when it is really a delay.

Why branch numbers drift

Divergence is rarely dishonesty. It is almost always latency and translation. Each branch keeps its own working record — a spreadsheet, a notebook, a point-of-sale export — and head office assembles those records into one report on a schedule. Between the moment something happens in a branch and the moment it reaches the consolidated view, the two versions of reality are legitimately different.

Translation adds the second layer. One branch calls an item "1L cooking oil," another calls it "Oil 1000ml," and a third uses the supplier's code. One books a delivery charge as freight, the next books it as miscellaneous expense. When those records meet, someone has to decide which label wins, and that decision is made from memory rather than from a rule.

The drift compounds quietly. A small mismatch this month becomes the opening balance next month, and by quarter-end the correction is large enough that nobody wants to be the one to book it. The fix is structural: shorten the delay, and remove the translation step entirely.

Transfers are where stock records break

A branch-to-branch transfer is not one event. It is a release at the origin and a receipt at the destination, usually done by different people, on different days, from different pieces of paper. When each site keeps its own book, the two halves are separate entries that someone must match later. If the origin releases ten units and the destination receives nine, both records are internally consistent and the company is short one unit with no obvious owner.

Goods in transit are the second gap. For the days a shipment is on the road, it has left one count and not yet entered another, so a report run in that window is understated by design. The Inventory module tracks stock levels, transfers and adjustments across every location, which turns a transfer into a single record with two ends rather than two records that need reconciling.

Adjustments deserve the same treatment. Breakage, spoilage, recount corrections and write-offs should be recorded as adjustments with a reason attached, not absorbed silently into the next delivery. A count that is "fixed" without explanation teaches everyone that the count does not matter.

Cash needs the same discipline as stock

Cash suffers from the identical problem with higher stakes. Each branch collects, spends petty cash, pays small suppliers and deposits — and each of those four things can be recorded at a different moment, in a different format, by a different person. The classic multi-branch symptom is a bank deposit that does not tie to any single day's recorded collections, because the branch banked two days together and paid a supplier out of the drawer in between.

The Finance module covers accounts, expenses, payments, loans and reconciliation with automated tax calculations and dynamic reports, which means branch activity can be posted against one set of accounts as it happens rather than summarised and forwarded. What that changes in practice is the question you can ask. Instead of "what did the branches send us," you can ask "what does this branch owe, hold and have spent as of right now," and expect the answer to be current.

Deposits still have to be matched against recorded collections by a person. Automation shortens the list of items to check; it does not remove the checking.

One item list, one chart of accounts

Before any of this is worth configuring, two lists have to be settled and locked: the item master and the chart of accounts. If branches can each create their own items, you will end up with three entries for one product and a stock report that undercounts all three. If branches can each invent expense categories, your consolidated profit and loss becomes an essay rather than a statement.

Decide who is allowed to create a new item or a new account — usually one person at head office — and make everyone else request it. This feels bureaucratic for about two weeks and then it disappears into the routine. Agree on unit of measure conventions at the same time, because selling by piece while receiving by case is the second most common source of phantom stock after unrecorded transfers.

Standardisation is also what makes comparison possible. Branch performance only means something when the branches are measured with the same ruler.

Branches, or separate companies

There is a real structural question underneath all of this: are your locations branches of one legal entity, or separate registered companies that happen to share an owner? The answer changes the design. Branches of one entity belong in one set of books with location tagging, so stock and cash consolidate naturally and inter-branch transfers stay internal movements. Separate entities need separate books, because their filings, registrations and financial statements are separate.

The Tenancy module supports the second case — multiple separate tenant instances run from a single ERPat deployment — which keeps distinct companies genuinely distinct while remaining one thing to administer. Getting this decision wrong in either direction is expensive to undo, so confirm it with your accountant before configuration rather than after.

Reconcile on a rhythm, not at year-end

The habit that actually keeps multi-branch numbers trustworthy is frequency. Cash is counted and matched daily at each branch, against that day's recorded collections and payouts. Fast-moving stock is cycle-counted weekly, a small section at a time, so no single count is a whole-day shutdown. Everything else is counted on a rolling schedule that covers the full catalogue over a quarter.

Set a variance threshold and say in advance who investigates what. Small differences get recorded and moved past; anything above the threshold gets a named person and a deadline. Without that rule, every variance is either ignored or escalated, and both outcomes are bad. Keep the investigation itself short — the point is to find the missing transfer or the unposted expense while people still remember the week it happened.

Regular reconciliation also protects your statutory position. Books that are reconciled monthly are books that can be presented to the BIR, to a lender, or to an auditor without a scramble.

Where to start

If your branch numbers currently disagree, do not begin with software. Begin by picking a single date, counting everything at every location, and agreeing that those figures are the opening balances. That count is the last time you will have to reconstruct history rather than maintain it.

From there, work in order: settle the item list and the chart of accounts, define how transfers are released and received, set the reconciliation rhythm, and only then configure the system to carry it. Tools shorten the distance between what happened in a branch and what the owner can see. The discipline of recording it accurately is still yours to set, and it is what makes any of the reporting worth reading.