The moments OrgExp is built for
Each of these started as something that went wrong in a real organisation — more than sixty companies, schools and colleges among them, approving spend on paper. Here is what the same moment looks like when something is allowed to say no.
An advance, an invoice, and the difference that is actually owed.
A capital project, line by line, from the first bill to the one that does not fit.
Two institutions, the same group budget, the same week.
Who is waiting on whom, and what happens when they are away.
Answering last month's question in a minute, not a week.
Paying a vendor you have already paid
Large vendors are often paid before the work is done. The invoice comes weeks later, to a different desk, and looks exactly like a bill that has not been paid. In one group we work with, that invoice was for ₹60 lakh — and it was one step from being paid a second time.
The situation
A contractor is building new classrooms for one of the group's colleges. To start work they need money up front, so the college's project lead raises an advance of ₹60,00,000 against the construction budget. Two months later the contractor's invoice arrives — at the accounts office, not at the project lead's desk. On paper, nothing connects the two.
Step by step
The project lead raises a request against the construction line of the college's budget, marked as an advance. It is checked against what the line has left and routed to its approvers.
On approval, ₹60,00,000 is recorded against the line. From this moment it counts as spent.
Accounts registers the payment — bank transfer, date, reference, the bank slip attached. A second person, with the right to approve payments, approves it. The advance now shows as Paid.
It is raised as a settlement, and a settlement has to name the advance it draws down: an approved advance, on the same budget line, raised by the same person. The ₹60,00,000 already paid is on the screen of whoever settles it.
A settlement charges the budget the invoice amount minus the advance. The invoice is ₹60,00,000, the advance was ₹60,00,000 — there is nothing more to pay, and nothing is released.
Had the invoice been ₹64,00,000, the settlement would charge ₹4,00,000 — checked against the line like any other request, and paid like any other request.
What the approver sees
Not an invoice on its own. An invoice next to the advance it settles, the amount already paid, and the difference actually owed. The question stops being “is this bill genuine?” and becomes “is the difference right?” — which is a question someone can answer.
The figures in the walk-through are illustrative. OrgExp does not read or compare invoice numbers; it ties a settlement to the advance it draws down.
Keeping a building to its budget
A building is never one bill. It is hundreds — cement, steel, labour, electrical, “while we are at it” — each one reasonable on its own. In one group we work with, a building budgeted at ₹1 crore cost more than ₹13 crore over about a year, and every one of those bills had been signed.
The situation
A school is adding a new block. The group approves ₹1,00,00,000 for it. The site engineer, the purchase team and the school's administrator will all raise spend against it over the next year, and none of them sees what the others have raised.
Step by step
The block is a budget with categories and line items, each with its own figure and dates — structure ₹55 lakh, electrical ₹15 lakh, plumbing ₹10 lakh, finishing and furniture ₹20 lakh. It goes through its own approval before anyone can spend from it, and if the group builds often, it starts from a template.
The site engineer raises ₹8 lakh for steel against Structure. There is no way to raise spend against “the building” in general, and no way to raise it against nothing.
Before approving, OrgExp works out what Structure has left — after taking off what is already spent and what other people have asked for and are still waiting on.
Approval steps depend on the amount: ₹50,000 of sand stops with the administrator; ₹25 lakh of structural steel goes on to the group.
In month four, Structure has ₹3 lakh left and a request arrives for ₹11 lakh. It is refused, and the refusal says so in numbers: ₹11 lakh asked, ₹3 lakh available.
If the ₹11 lakh had been split into four lines on one request, the check runs line by line — line two sees what line one just took — and the request is refused on the line that breaks the limit.
What happens after a no
The building still needs its structure. But now going over is a decision, not a drift. Either more money is found and approved for the block — as its own budget, through the same approvers — or money is recorded as coming in, such as a donation for the building, which raises what is available without rewriting the ₹1 crore the block was approved at. Either way, the original plan and the real cost stay side by side.
The line items and figures in the walk-through are illustrative.
A hundred approvals a day, without paper
One group we work with was approving more than a hundred requests a day on paper, across sixty offices. A request waited on the desk of whoever was supposed to sign it — including when they were on leave — and nobody could say where it was.
The situation
It is Monday. The principal of one of the schools is at a conference until Thursday. Twelve requests are waiting on them, three of them urgent. The finance head at the parent needs to know what is stuck across the group, and has sixty offices to ask.
Step by step
The approval path is set up once: who approves at each step, in what order, and which steps apply above which amounts. Each request finds its own approvers from the budget it spends from.
Weekends and public holidays do not count against it.
The principal is on leave, so their steps go to the backup named for them — the vice-principal — instead of sitting on an empty desk.
A step that passes its deadline escalates to the next person in the chain. Chains can differ by amount: a ₹20,000 request and a ₹20 lakh request escalate to different people. The person it reaches is told that it is an escalation.
Approvers are notified with a link and can approve or refuse from the email itself, with a reason for a refusal.
A daily or weekly summary tells each person what is waiting on them, what was decided and what is overdue.
Reporting shows how many days requests take to complete, how many steps they go through, and how often they are escalated — so a bottleneck is visible, not rumoured.
Why it matters
At a hundred a day, paper does not fail loudly. It fails as a pile on one desk, a request walked round by hand, a signature collected after the money was already committed. Moving the same approvals onto rules that route, remind and escalate is what makes the other controls — the budget check, the settlement — happen on every request instead of most of them.
“Who approved this, and when?”
With approvals on paper, a question about last month is a search through filing cabinets in sixty offices. In OrgExp it is a search.
The situation
It is the end of the quarter. The group's auditor asks three questions about the construction budget at one of the colleges: who approved the largest payments, whether any request was refused and then raised again, and why the budget shows more available than was originally planned.
Step by step
Filter by budget, by who raised them, by status — draft, waiting, approved, refused — without knowing which office handled them.
Every step: who it was waiting on, whether it was approved or refused, when, and the reason for a refusal. If it was escalated, who it was originally with and who decided it.
The budget shows what was planned, what was spent and what is available, and every amount spent is one entry, numbered and dated, tied to the request that caused it.
Each payment shows its method, date, bank reference and the slip itself, who registered it and who approved it — and the request shows whether it is Not Paid, Partially Paid, Paid or Overpaid.
Money that came in against the budget is recorded separately from the plan, with its own approvers — so “why is there more available than planned?” has an answer on the screen, and the planned figure is still the one that was approved.
Entries cannot be deleted. A mistake is corrected with a correcting entry, so the mistake and the fix are both still there for the auditor to read.
Why it matters
The questions do not change when approvals move off paper. What changes is that answering them takes a minute instead of a week, and that the answer does not depend on who still remembers.
Each one started with something that happened to a group of more than sixty companies — ₹60 lakh nearly paid twice, a ₹1 crore building that cost ₹13 crore, a hundred approvals a day on paper.
Bring us your version of this
Tell us the moment that went wrong in your organisation, and we will walk through what OrgExp would have done.