Nothing Paid Until It’s Approved: How a North 24 Parganas Fine Arts College Brought Control to Its Spending

At a glance: A small fine arts college in North 24 Parganas, West Bengal, wanted to digitise how it managed expenses. Using Vawsum’s Expense and Purchase Voucher Management module, it set up a strict sequence: the cashier records each expense in the system, an approval request goes to higher management, management approves it inside the system, and only then can a payment be recorded against it. Category budgets now cap spending, the approver sees how much of each budget is already used along with automatic flags, and reports by category, vendor and period generate themselves. The college says it has transformed how this process runs.

The problem

This is a small college, but not an informal one. It already ran its administration by process, and it wanted its spending to work the same way. The difficulty was that expense management lived outside any system. Entries, approvals and payments were separate steps that depended on people following the sequence correctly, and nothing enforced the order in which they happened.

For an institution that cares about process, that gap shows up in predictable ways:

• Approval could not be proven before payment. Management could intend that every expense be approved first, but on paper there is no way to guarantee a payment did not go out ahead of the sign-off.
• Budgets were a number, not a control. A budget for a category could be agreed at the start of the year, but nothing stopped spending from running past it. An overrun became visible only after it had happened.
• Approvers decided without context. When a request reached management, the question that mattered was how much of that category’s budget had already gone. Answering it meant going back to the registers.
• Reports were assembled by hand. Spending by category, by vendor or for a given period had to be compiled every time someone asked.

The college did not want more paperwork. It wanted the process it already believed in to be one the system enforced.

What changed

The college’s expense process was rebuilt inside Vawsum as a fixed sequence, so that each step can only happen once the one before it is complete:

• The cashier records the expense. Every expense starts as an entry in the system, raised against a vendor and an item category. Categories cannot be skipped, so every rupee is classified from the moment it is recorded.
• An approval request goes to higher management. Recording the expense does not authorise it. The entry automatically becomes a request waiting for management’s decision.
• Management approves inside the system. The approval itself happens in Vawsum, not on a separate note or over the phone, so the record of who approved what, and when, sits alongside the expense.
• Payment is locked until approval exists. Payment entries can only be recorded against an approved expense. There is no route for a payment to be made first and justified afterwards.
• Budget controls sit underneath. Budgets are set against expense categories for a defined period, so spending is checked against the limit at the point of commitment rather than discovered as an overrun later.
• The approver sees the full picture. At the approval step, the request carries automatic flags and shows how much of the relevant budget has already been used. Management decides with context in front of it instead of signing blind.

The result

The college now has genuine control over its spending, built into the process instead of depending on everyone remembering it. Nothing is paid without an approval on record, and every approval was made with the budget position visible. When a request needs a closer look, the flags put it in front of management at the moment the decision is being made, not weeks later in a review.

Reporting stopped being a task. Spending by category, by vendor and by period is generated automatically from the same entries the cashier records, so the management can see where money is going, who it is going to and how it is moving over time without anyone compiling a sheet.

The college has been very happy with the change, and says it has transformed how it runs expense management. For a small institution, the result is the discipline of a much larger one’s finance office without having to build that office.

It pairs naturally with how a Burdwan school made every rupee traceable on the income side. That school put controls on how fees come in; this college put them on how money goes out. Both sit in the same platform, so income recorded through the Fee Management System and expenditure recorded here give management one financial picture.

FAQs

Can a payment be recorded before an expense is approved?
No, not in the way this college configured it. The cashier records the expense, an approval request goes to higher management, and payment entries can only be made once management has approved it in the system.

What does the approver see when a request comes in?
The request shows automatic flags and how much of the relevant category budget has already been used, so the approver has the budget position in front of them when deciding.

How do budget controls work?
A budget is set against an expense category for a defined date range. Spending is checked against it at the point of commitment, so the institution sees the limit before money is committed rather than an overrun after the term has ended.

Can approval route to different people depending on the amount?
Not at present. Approval follows a single workflow regardless of value. Where an institution wants tighter control over larger spend, category budgets cap what can be committed in the first place, and the approval-step flags draw attention to requests that need it.

What reports are available?
Expense reports are generated automatically at category level, vendor level and for any period, from the same entries the cashier records, so nobody compiles them by hand.

Is this only for schools, or can colleges use it?
Colleges use it too. This case study is a fine arts college, and the same module works for any institution that wants a controlled expense process. See the College App for Vawsum’s broader offering for colleges.

Running an institution in Kolkata or anywhere in West Bengal and want the same control over spending? See how Vawsum pricing works or send us an enquiry.

See all case studies

See related case studies: how a Kolkata school cut counter billing to a few clicks with editable sales voucher templates, how a CBSE school in South 24 Parganas ran class-wise admission kits from purchase to dispatch with item-level profitability, how a 1,000+ student Burdwan school replaced cash and screenshot-based collection with an auditor-ready fee system, how a trust-run South 24 Parganas school moved fee collection 100% online in three months with zero gateway charges, how a CBSE school in Siliguri fixed chronic late fee payment by linking admit card downloads to a fee-clearance cutoff, how one 8-branch school group cut its payroll cycle from a week to under a day, how a residential school in Siliguri turned leave policy into a configurable rules engine, how a reputed ICSE school ran 1,000+ annual admissions through one auditable pipeline, how a Kolkata residential school made hostel attendance verifiable with four daily checkpoints, how a multi-branch Kolkata school tracked transport with QR codes alone, how a Bengali-medium school with zero computers went digital using nothing but phones, how a Jalpaiguri school rebuilt its annual ID card renewal in two days, and how a school with 100+ teachers replaced its daily substitute scramble with rule-based, auditable allocation.