Trust, but reconciled

Our family shop, Trishakti Stores, has sold readymade garments wholesale and retail in Narayangarh since 1991. Over the years it has built a network reaching around 750 active retail shops across Mid-Nepal as of 2026. I keep the accounts. When my father travels, the whole load lands on me — party balances, cheques, the calls asking why a payment has not been posted yet.

That work is where the name for all of this came from: trust, but reconciled.

It is worth being clear about what that phrase does not mean. It is not a polite way of saying people steal. In my experience the people doing this work are honest and are trying hard. The problem is not their character. It is that a business generates obligations faster than a manual process can confirm them, and the gap between the two is where losses live.

Four problems, none of them about honesty

Everything I have built for accounting traces back to some version of these.

Post-dated cheques. A cheque written today for a date three weeks out is a promise, not money. Between those two dates it has to exist somewhere — as a real obligation, tracked, with somebody knowing what happens on the day it matures. Handle a stack of those manually, across many parties, and the question “what is actually due to us this month” becomes genuinely hard to answer. Not because anyone hid anything. Because the information is sitting in a drawer instead of in a report.

Paper credit notebooks. Credit given from behind the counter, written in a notebook, is real business — and for a long time it works, because the person who wrote it remembers. But a notebook is not queryable. You cannot ask it who is overdue, or which balances have not moved in three months, or whether a party is past the limit you meant to give them. And if the notebook and the books disagree, there is no mechanism that tells you. Somebody has to notice.

Physical stock that is not in the records. Goods move faster than paperwork. Something is delivered before its entry is made, an adjustment happens and is not recorded, a return goes back without a document. Each one is small and each one is explainable. But stock valuation feeds the profit figure, so a shelf that disagrees with the ledger is not a stock problem. It is an accounts problem wearing a different coat, and it usually only surfaces at a physical count, months later, when reconstructing what happened is close to impossible.

Payments posted against the wrong bill or the wrong month. This is the one that fools people most. The money genuinely arrived. The bank balance is correct. But it was applied to the wrong invoice, or landed in a different period than the sale it settles. Every total looks fine. The party statement is wrong, the ageing is wrong, and the period is wrong — and nothing anywhere is flagged, because from the system’s point of view nothing failed.

Why trust still needs reconciliation

Notice what those four have in common. None of them is caught by trusting the person more. Trust is a statement about someone’s intent. Every one of those failures is a mismatch between two records, and no amount of good intent closes a mismatch.

That is the whole argument. Reconciliation is not surveillance and it is not suspicion. It is the routine that makes it safe to delegate — because when someone else can confirm the numbers independently, the person doing the entries is no longer personally carrying the risk of every mistake they might have made. Controls protect the trusted person at least as much as they protect the owner.

The practical version of that is unglamorous:

• Every side of an entry has to reach the reporting on its own, without anyone chasing it.
• Owners need timely visibility, not a monthly summary assembled by the same person who made the entries.
• Edits, cancellations and backdated transactions must leave a trace. Not to catch anyone — so that a wrong figure can be explained instead of argued about.
• Approvals and limits should be enforced by the system, so a rule is a rule rather than something a person has to remember to apply under pressure.
• Anything you cannot query, you cannot verify. That is really an argument against paper.

Where I have got to

I am building SAHARA CORE around exactly this. It is in active development and internal testing — nobody outside our own business is using it, and I am not going to describe a test as a deployment.

I will say what I am aiming at. Any authorised staff member can make an entry. Owners get timely visibility and the ability to verify it. The audit trail is part of the accounting engine rather than something bolted on afterwards. Post-dated cheques, credit limits and outstanding management are core, not features for later, because those are the problems I actually have.

The thing I found while building it is that the ledger is easy and the reconciliation is hard. Debit and credit are arithmetic. Proving that what the system says matches what happened in the world — that is the entire job.

Trust the person. Reconcile the numbers. They were never the same question.