What it looked like before somebody could say no

Before: an advance was a payment, and then it was forgotten

Large vendors — builders, suppliers, contractors — are often paid in advance, and the invoice arrives later. In between, the advance lives in a bank statement and somebody's memory. When the invoice turns up, it looks like a bill that needs paying. Nothing on it says it already has been.

In a group of more than sixty companies, the person who arranged the advance and the person holding the invoice are often not the same person, and not in the same office.

What happened

The vendor had received ₹60 lakh as an advance. When the invoice came in, it was raised as a settlement against that advance, with the ₹60 lakh expected to go out again.

In OrgExp, a settlement names the advance it draws down, and only the difference is charged — because the advance already was. A ₹60 lakh settlement against a ₹60 lakh advance comes to nothing. So nothing was released.

The complaint arrived quickly: the money could not be got out, and the software was bad. Finance went to check, put the invoice number and PO number next to the advance, and found the same bill. It had been paid once. It was one step from being paid twice.

Why it held

The lesson

A control that never says no is not a control, and one that says no will be called bad software at least once. The complaint was the system working. What mattered was that the refusal came with a reason someone could follow back to the invoice.

OrgExp does not read or compare invoice or PO numbers. It ties a settlement to the advance it draws down and charges only the difference.

Before: a budget is approved once, and then it is a file

The building had a budget. It was approved at the start and then kept in a spreadsheet, while the approvals were signed on paper. Construction does not arrive as one bill. It arrives as hundreds: materials, labour, contractors, changes, “while we are at it”. Each one went to someone who checked whether it was reasonable — not whether there was money left, because at the moment they were asked, nobody could tell them.

So each payment was sensible, and the total was not. For close to a year the building went on costing money, one approved bill at a time, and the number that mattered sat in a file nobody opened before signing. Nobody overspent on purpose. Nobody was in a position to see it.

After: the budget answers back

In OrgExp there is no request without a budget line. A capital project is a budget with its own lines — structure, electrical, fittings, whatever the plan was approved on — and every request names the line it spends from. The approval is checked against what that line has left after other pending requests are held back, so two people are never told there is room for the same money.

What it would have looked like

At ₹1 crore, the first request that did not fit would have been refused. Somebody would have had to go back and ask for more money, in writing, with a reason — at the first crore, not the thirteenth. The building might still have cost more than planned. But it would have been a decision, made once, by someone who could see the number.

Before: a signature, and then a filing cabinet

A request was written up, carried from desk to desk and signed. If the approver was away, it waited on their desk. If it was urgent, someone walked it round. Once signed, it went into a file in one of sixty offices. By the end of a month that was thousands of sheets.

Nobody could answer the simple questions. Where is my request right now? Who approved this payment last month? Was it refused before, and why? Has this invoice been through already? Answering any of them meant finding the right file in the right office and reading through it by hand. It is how a ₹60 lakh advance could be forgotten by the time its invoice arrived, and why the ₹13 crore building took a year to add up.

And paper could not say whose money it was. Some spend belongs to one institution. Some is a group project that one company carries out for the others — a new building, a shared bus fleet. On paper both looked the same: a request and a signature, with nothing to say whose budget it came from, or whether the person signing was the right one.

After: every decision can be found

A group is a tree, not a list

A company may spend against its own budget, or a budget of any company above it — an institution carrying out a group project charges the group's budget, legitimately. It can never spend a sibling's. And an approver at the parent can sign off a subsidiary's request, so oversight from the top does not need a login per company.

Start where the money leaks

Nobody needs all of it on day one. Budgets, spend requests and approvals are the part that says no — that is what would have stopped the building at its first crore. Payments, income and the rest switch on when you are ready, and turning one on later does not mean redoing your setup.

One customer, anonymised at their request. The figures are theirs; the institutions and vendors are not named.