At closing, the day's cash doesn't go into a safe; it goes home with a man everyone calls Mama ji. Part of it comes back tomorrow, part of it a few days later. He's been doing this for twenty years.
Software has one word for this arrangement: discrepancy.
Cue the eye-roll: bicycle era, allergic to software. Except the cash isn't going anywhere; currency in circulation grew 11.9% this year, the fastest in five years, in the middle of the UPI decade.
The counter pays out as well as takes in. Fuel alone, across the locations, runs into a few crores a year. That is one expense head.
A ₹500-crore-plus auto dealership had asked me for “automation.” I pointed them at the usual ERPs. The owner's review was short: stupid. He invited me to sit with his team instead. So I ended up at cash counters across a string of small towns, including Jhumri Telaiya, a place I'd believed was a punchline from old radio shows.
Jhumri Telaiya
A mica-mining town in eastern India. In the 1950s its listeners flooded Vividh Bharati with film-song requests in such numbers that the name became shorthand on air for “the middle of nowhere” — and stayed a punchline long after most people stopped believing the place existed.
What a “simple” payment looks like
A customer walks up after his car's service, holding a real GST tax invoice, generated by the manufacturer's dealer management system. The carmaker owns it; the dealer merely uses it. There's no API, and its data leaves the building as an end-of-day export.
The cashier takes his payment, writes the UPI reference on the invoice in pen, and waves him through to the gate.
The counter accepted payment for an invoice it didn't create and can't query.
Which vehicle, which bill, how much due, how much collected: every field is a manual entry that can't be verified in real time. A mistake and a theft leave the same trace.
The software has no slot for it
Off the shelf, there are two things you'd reach for, and neither fits.
A POS creates sales, so ringing this up mints a second tax invoice for the same sale.
An accounting package records payments, but a payment needs its invoice in the books first. So someone re-keys every bill into a second system, and the manual-entry gap gets a second address.
Even then, nothing reconciles itself. The bank statement, the UPI and card settlement files, the insurer's share of an accident repair, the carmaker's payout on warranty plans, an owner-approved discount handwritten on a tax invoice. Fifteen people match it all by hand, and five more get the result into Tally. It takes a month. So the owner of a ₹500-crore-plus business sees what his cash did four weeks after it did it.
Where does ERP adoption actually die?
Adoption dies at the counter, in week one, when the cashier can't record what just happened. So she keeps a paper register “just for now.” A year later, everyone agrees the ERP “didn't work here.”
We blame Indian SMBs for poor software adoption. But the business didn't reject the software. The software rejected the business.
The requirements were drawn for a clean world; this dealership grew past ₹500 crore in the messy one, and the mess is how it works.
So we built it ourselves
We built it on one principle: design for the world as you find it. Four rules:
- Record testimony, and make recording it easy. The cashier says what happened; the system doesn't decide what it meant.
- “We don't know yet” is a first-class state, not a workaround. An entry holds there until reconciliation closes it.
- Immutability: nothing recorded is ever edited. Corrections arrive as new entries.
- Reconcile across systems — AI closes most mismatches, people close the rest.
Mama ji still takes the cash home. Nothing about his evening changed. The system finally has the right word for it: custody, with an audit trail.
Next up — “When every source of truth is lying a little”: three systems that never fully agree, and what we do about it.
Get the next post by email.
I publish slowly. You’ll get an email when something new is up.