Why expenses leak in small businesses
Sales gets a system; spending gets a drawer. In most SMEs, expenses are recorded late (a pile of slips at month-end), classified casually (the same electricity bill under three different heads in three months), and reviewed never (the first person to look hard at them is the auditor). None of this is fraud, usually — it is friction. But the effects compound: the expense summary stops meaning anything, budgets cannot be compared to actuals, and the year-end cleanup costs real accountant hours.
The fix is not a finance department. It is three small structures, applied consistently: classification decided once (expense types mapped to account heads), a review gate before posting (maker-checker approval), and no re-keying (approved entries flow to the books). All three are standard features of billing software with light accounts — the operational layer described in our pillar guide to GST billing software.
Step 1 — define expense types, map them to account heads
Start with a short list of expense types that matches how you actually spend: freight inward, vehicle and fuel, office rent, electricity, staff welfare, repairs and maintenance, printing and stationery, professional fees. Fifteen to twenty-five types cover most SMEs; a hundred types means nobody will classify anything correctly.
Then map each type to its account head — once. This is the load-bearing decision: after it, every recorded expense lands in the right ledger automatically, because the classification travels with the type rather than depending on whoever is typing. The mapping lives in the chart of accounts of your accounts and vouchers setup, and it is what makes expense reports comparable across months. When a genuinely new kind of spend appears, add a type deliberately — with your accountant — rather than letting operators improvise heads. GST treatment of specific expense categories (what input credit applies, what is blocked) is a separate question: settle it with your CA when you define the types, not invoice by invoice.
Step 2 — the approval gate: maker-checker without bureaucracy
The single most valuable expense control costs one click: the person who records an expense is not the person who approves it. The maker enters the expense — amount, type, date, supporting reference. The checker (owner, manager or accountant, depending on size) reviews pending entries and approves, queries or rejects. Only approved entries post to the accounts.
What the checker is actually checking, in seconds per entry: Is it genuine (reference attached)? Is it classified under the right type? Is it within policy for this category and this person? The gate's value is only partly in what it catches — it is mostly in what it prevents. Spending behaves differently when everyone knows entries are read. Keep the gate fast (a daily or twice-weekly approval sitting, not a committee) and it will not slow anyone down; let entries queue for weeks and people will route around it.
Expenses vs supplier bills — two documents, two controls
A frequent SME confusion: treating vendor invoices and expenses as the same thing. They are different documents with different control questions:
| Aspect | Supplier bill | Expense entry |
|---|---|---|
| Sits behind it | A purchase order and goods receipt | No PO — utilities, rent, travel, small services |
| The control question | Does the bill match what was ordered and received? | Is it genuine, classified right, within policy? |
| Approval gate | Yes — before it posts as a purchase voucher | Yes — before it posts to the expense head |
| Posts to books as | Purchase voucher | Expense entry under its mapped account head |
| Where it is reported | Supplier bill report — approval status, payables | Expense summary by type and period |
Keeping the two streams separate keeps both reports honest: the payables position is not polluted by petty expenses, and the expense summary is not distorted by inventory purchases. Both gates follow the same maker-checker principle; both post cleanly to the books. The supplier-bill side is covered in the essential billing reports.
Want the approval gate running by next week?
A 30-minute Fast Billing Software demo shows expense types, account-head mapping, the approval screen and posting to your books — configured live for your categories.
Step 3 — vouchers for everything else
Not every entry is an invoice or a typed expense. Manual vouchers — journal, payment, receipt — handle the remainder: a correction between heads, a payment not tied to a bill, an opening adjustment. Two disciplines keep vouchers from becoming the new leak: every voucher carries a narration a stranger could understand a year later, and voucher entry respects the same account heads as everything else — no new ledgers invented at the keyboard. In a light-accounts setup, vouchers are deliberately simple; the statutory heavy lifting stays in your accounting package.
Step 4 — budgets that get compared, not just written
A budget is only a control if someone compares it to actuals while the period is running. Set budget figures for the expense categories that matter (and item purchase budgets where procurement is the risk), then put the comparison where decisions happen: the monthly review, and ideally the approval moment itself — an approver who can see that this entry takes "Repairs" to 80% of budget with four months left will have the conversation now, when it can still change behaviour. Budget-vs-actual by expense type, per period, is a five-minute monthly read that quietly ends the year-end surprise.
Step 5 — posting to the books without re-keying
Everything above happens in the operational system — where the people who spend and approve actually work. The books remain the book of record: approved expenses and vouchers post to accounting the same way invoices post as sales vouchers and receipts as receipt vouchers — mapped ledgers, no re-typing. This is the same no-re-keying principle that runs through the whole billing stack via the Tally integration: enter once, approve once, and let the ledger agree with the operational system by construction rather than by month-end reconciliation.
A one-page expense policy that works
Controls need a policy people can remember. One page is enough:
- Every expense is entered within 48 hours, under a defined type, with a bill or reference attached. No month-end piles.
- Nothing posts unapproved. The maker never approves their own entry; the checker clears the queue at least twice a week.
- Vendor invoices go through supplier-bill approval, matched to their PO and receipt — never through the expense stream.
- New expense types are created by the accountant, mapped to a head, with GST treatment confirmed with the CA — not improvised.
- Budget vs actual is read monthly, and any category past 80% mid-period triggers a conversation, not a freeze.
What the gate changes in one quarter
A workshop moves from slips-in-a-drawer to typed expenses with approval. The first effect is boring and immediate: entries arrive within days, classified consistently, because the type list makes the choice obvious. The second effect appears in the approval queue: duplicate fuel claims and a "miscellaneous" habit surface in week two — not as confrontations, but as queries on entries. The third effect lands at quarter end: budget vs actual by type is read in one sitting, "Repairs" is visibly trending 30% over, and the decision to service rather than patch a machine is made in month three instead of month thirteen. Nothing dramatic happened — which is the point.
How Fast Billing Software implements this
Fast Billing Software ships the whole chain as part of its light-accounting profile:
Frequently asked questions
What is an expense approval workflow?
A maker-checker control: one person records an expense, and a different, authorised person reviews and approves it before it posts to the accounts. The approver checks the entry is genuine, correctly classified and within policy. Only approved expenses reach the books. A lightweight gate applied consistently beats a heavyweight process applied occasionally.
Why should expense types be mapped to account heads?
So classification is decided once, by structure, rather than every time by whoever is typing. With each type — freight, rent, welfare, repairs — mapped to its ledger in advance, every expense lands in the right head automatically. Reports by type become trustworthy, month-to-month comparisons mean something, and the accountant stops reclassifying entries at year-end.
What is the difference between an expense entry and a supplier bill?
A supplier bill is a vendor invoice against a purchase order and goods receipt — matched, approved and posted as a purchase voucher. An expense entry covers spending with no PO behind it: utilities, rent, travel, small services. Both pass an approval gate, but the controls differ — matching for supplier bills, classification and policy checks for expenses. Keeping the streams separate keeps both the payables position and the expense summary honest.
How do budgets help control expenses?
A budget states in advance what a category should consume; its value is the live comparison against actuals. Checked at approval time and in a monthly review, it turns "Repairs is 30% over" from a year-end surprise into a mid-year decision. A budget nobody compares against actuals is a wish, not a control.
Do approved expenses flow to Tally automatically?
In a properly integrated system, yes — approved expenses and vouchers post to the book of record without re-keying, the same way invoices post as sales vouchers and receipts as receipt vouchers. Tally stays the statutory ledger; the billing system is where entry, classification and approval happen. No month-end pile of slips to type in.