Skip to main content
← Back to Blog
Billing18 min read

Construction Site Petty Cash Management in India: Imprest System, Voucher Format and Cash Limits

A practitioner guide to the site cash box: how the imprest float self-audits, the nine-field voucher format that survives scrutiny, the Rs 10,000/day cash limit (old Section 40A(3), now Section 36(4) of the Income-tax Act 2025), the GST credit petty purchases silently lose, and the four fraud patterns a monthly reconciliation catches. With a free Excel voucher and imprest register.

Y

Civil Engineer | IIT Bombay | ex-IOCL

By Yogesh Dhaker Published

Every construction site in India runs on a cash box. The tempo driver who moved eight bags of cement across town wants Rs 400 now, not after a three-day approval cycle. The loading gang wants Rs 50 per head before they leave the gate. The electrician needs a Rs 180 MCB from the hardware shop because the slab pour cannot wait for a purchase order. None of this is optional — a site that cannot spend small money fast is a site that stalls.

What is optional is whether that cash box is a controlled system or a hole in the project's pocket. The difference is not honesty; it is structure. A site with an unstructured cash advance — "here is Rs 30,000, we will settle later" — has no way of knowing what "later" should look like. A site running a proper imprest system with pre-numbered vouchers knows, at any moment, exactly how much cash should be in the box, and the arithmetic itself exposes the leaks.

This guide covers the whole system: how a site imprest works, the voucher format that stands up to an audit, the income-tax cash limits that changed names on 1 April 2026, the GST money most contractors lose without noticing, and the fraud patterns a reconciliation catches. There is a free petty cash voucher and imprest register template (Excel) built to match this guide, and more formats on our templates page.

What is the imprest system for site petty cash?#

An imprest is a fixed float. The office gives the site a fixed sum — say Rs 20,000 — and that number never changes. The custodian (usually the site engineer, supervisor, or site accountant) pays small expenses from it and collects a voucher for every payment. At any moment:

Cash in the box + vouchers on hand = the fixed float. Always.

That single equation is the whole control. If the float is Rs 20,000 and the box holds Rs 7,350, there must be exactly Rs 12,650 of signed vouchers. If there are not, somebody has taken money without documenting it, and you know the same day — not at year-end.

Replenishment works the same way: the office reimburses exactly the amount of the vouchers submitted, which restores the float to Rs 20,000. The vouchers move to the office, get booked to their expense heads, and the cycle restarts. The expenses hit your books at replenishment, head by head, which is why the voucher's expense-head column matters as much as the amount.

Contrast this with the way most small contractors actually operate: the open advance. The owner transfers Rs 30,000 to the supervisor's personal account, then another Rs 15,000 ten days later when he says it is finished, then Rs 20,000 more. Nobody can say what the balance should be, so nobody can prove what is missing. An open advance is not a petty cash system; it is a trust exercise with the project's money.

Two practical calibrations, from how Indian sites actually run:

  • Float size. There is no published benchmark, so treat this as practitioner guidance: most single-project sites run well on Rs 10,000–30,000, sized so the float covers roughly two weeks of routine small expenses. If you are replenishing twice a week, the float is too small and the site will start "borrowing" from labour payments; if a month passes untouched, it is too large and is quietly becoming someone's working capital.
  • Replenishment trigger. Refill when 20–30% of the float remains, against submitted vouchers — not on a fixed calendar. A fixed weekly top-up regardless of vouchers is an open advance wearing an imprest's clothes.

What are the cash payment limits for construction expenses?#

This is the part of petty cash management that most site teams learn about only after a tax notice, and it changed its address recently. The Income-tax Act, 1961 stands repealed from 1 April 2026, replaced by the Income-tax Act, 2025 and the Income-tax Rules, 2026 (notified 20 March 2026, effective 1 April 2026 — the official rules are on incometaxindia.gov.in). The substance of the cash-payment rules carried over almost unchanged, but every section your CA quotes now has a new number:

Article table: What the rule does Old (ITA 1961) New (ITA 2025,
What the rule doesOld (ITA 1961)New (ITA 2025, from 1 Apr 2026)
Cash payment above Rs 10,000/day/person — expense disallowedSection 40A(3)Section 36(4)
The limit is Rs 35,000 for goods-carriage transporters40A(3) provisoSection 36(6)
Prescribed exceptions (banking access, expediency)Rule 6DDSection 36(7) + rules
Receiving Rs 2 lakh or more in cash — penalty on the receiverSection 269STSection 186
That penalty = 100% of the amount receivedSection 271DASection 451

The mechanics of the Rs 10,000 rule, which have been stable since 2017 (ClearTax has a clear explainer):

  • The limit applies to the aggregate of all cash payments to one person in one day. Paying the same supplier Rs 6,000 in the morning and Rs 6,000 in the evening is one Rs 12,000 payment in the law's eyes. Splitting a bill across the day does not work and never has.
  • Breach the limit and the entire expenditure is disallowed as a business deduction — not just the amount above Rs 10,000. A Rs 12,000 cash payment for sand costs you the deduction on all Rs 12,000. At a 30% marginal rate, that "convenient" cash payment just added Rs 3,600 of tax.
  • For payments to transporters plying, hiring or leasing goods carriages — your tippers, tempos and trailers — the limit is Rs 35,000 per day per transporter.
  • The safe modes are account-payee cheque or draft, and every prescribed electronic mode: NEFT, RTGS, IMPS, net banking, cards — and UPI, which has been an approved mode since CBDT Notification 8/2020. A Rs 25,000 UPI payment to a vendor is fully deductible; the same payment in notes is not. This is the single strongest argument for moving site payments to UPI: it converts a tax problem into a payment-mode choice.

There are genuine exceptions, formerly listed in Rule 6DD and now prescribed under Section 36(7) (TaxGuru's Rule 6DD guide still maps them well), and two of them are tailor-made for construction:

  • Sites in unbanked villages. Cash payments made in a village or town not served by any bank on the date of payment, to a person who resides or does business there, are exempt. A rural road or canal project can rely on this — but the burden of proof is yours, so keep evidence that the location was unbanked.
  • Site-posted staff salaries. Salary paid in cash to an employee posted for a continuous period of 15 days or more away from their normal place of duty is exempt, provided tax was deducted and the employee has no bank account at that place. This covers the classic deployment of a crew to a remote site.
  • Payments to primary producers — a farmer selling you earth-fill, a local producer of bricks made without power — are also covered.

One warning: older articles still claim cash payments on bank holidays or strike days are exempt. That exception was deleted in 2020. If your site's practice relies on it, the practice is five years out of date.

The receiving side matters too. Under Section 186 (old 269ST), no one may receive Rs 2 lakh or more in cash in a day from one person, per transaction, or per event — and the penalty is 100% of the amount, on the receiver (Tax2win's guide covers the cases). A contractor who lets a client "settle the RA bill in cash" is volunteering for that penalty. The Supreme Court flagged exactly this in an April 2025 judgment involving a Rs 75 lakh cash advance on a property deal: the transaction was a plain violation even though the underlying contract survived.

Why petty cash purchases quietly lose you GST credit#

The income-tax rules punish cash payments above a threshold. GST punishes cash purchases of any size — silently, through input tax credit you never get.

ITC needs a proper tax invoice from a GST-registered supplier, with your GSTIN on it. Site petty purchases fail this test almost by design: the hardware shop gives a kaccha bill, the tempo operator gives nothing, the tea stall is not registered. Every such purchase carries embedded GST you paid but can never claim. On Rs 30,000 a month of petty purchases at 18%, that is roughly Rs 4,600 of credit leaking monthly — per site. The fix costs nothing: for any petty purchase from a registered vendor, have the custodian insist on a proper invoice with your GSTIN, and record the vendor's GSTIN on the voucher. (Our GST on construction materials guide covers the rate structure in detail.)

Two clarifications, because site teams get both wrong:

  • There is no general reverse charge on unregistered purchases. The old rule that taxed every purchase from an unregistered dealer above Rs 5,000/day was suspended in 2017 and formally replaced in 2019 with a notified-categories regime. For an ordinary contractor, routine petty purchases from unregistered vendors attract no RCM today.
  • Unless you are a real-estate promoter on the concessional scheme. Promoters paying 1%/5% GST must buy at least 80% of inputs and input services from registered suppliers, project by project, financial year by financial year. Any shortfall attracts 18% RCM — and any cement bought from an unregistered supplier attracts 28% RCM in the month of purchase, with no ITC under the scheme. Every "urgent" unregistered petty purchase erodes that 80% ratio. If you build for promoters, expect them to start asking where your site cash goes; if you are one, your own site imprest is part of your GST compliance.

What should a petty cash voucher format include?#

A voucher is the receipt's chaperone. Bills from local vendors are thin, thermal, and frequently missing; the voucher is the document that says who was paid, why, from which head, and on whose authority. The format that survives audits has nine fields:

  1. Voucher number — pre-printed and serial. Numbering is the anti-fraud feature: a missing number in the sequence is a destroyed voucher, and an auditor will find the gap in minutes. Numbered pads cost almost nothing; software numbers them automatically.
  2. Date of payment.
  3. Paid to — the person's or firm's name, not "labour" or "vendor".
  4. Purpose — one specific line. "Tempo for cement, Godown to Site B" is a purpose; "site expense" is not.
  5. Expense head — from a fixed list (next section), so replenishment posting is mechanical.
  6. Amount in figures and in words. The words are the Indian convention for a reason: "Rs 1,400" becomes "Rs 11,400" with one digit; "one thousand four hundred" does not.
  7. Receiver's signature (or thumb impression) — and for any cash payment above Rs 5,000, a Re 1 revenue stamp signed across. That requirement comes from the Indian Stamp Act, 1899 and has applied at the Rs 5,000 threshold since September 2004; a stamped, signed receipt has real evidentiary weight if the payment is ever disputed.
  8. Approved by — whoever holds approval authority for that amount, and for approvals above a threshold, a second signature.
  9. Supporting bill attached — yes or no. Staple what exists. Where a receipt is genuinely impossible, a signed no-receipt memo from the custodian, countersigned by the approver, is the documented exception. If those memos become frequent, that is a finding in itself.

The free Excel template bundles this voucher format with a running imprest register that computes the float balance after every entry — the reconciliation, automated.

Standard expense heads for an Indian site#

A fixed list of heads makes vouchers postable and comparable across sites. These eight cover nearly everything a site legitimately buys with petty cash:

  • Loading and unloading labour (the gate-side gangs, paid per trip)
  • Local transport — tempo, auto, tractor trips
  • Urgent small materials (binding wire, blades, an MCB — purchases too small or too urgent for the indent-to-PO cycle)
  • Consumables and site supplies (gloves, chalk, marking paint)
  • Small repairs and sharpening
  • Site office and utilities (printing, recharge)
  • Refreshments and hospitality — the chai-pani head, best kept with a per-day cap
  • Statutory and miscellaneous small fees

Anything that does not fit these heads probably should not be paid from petty cash at all. A Rs 9,000 "urgent material" voucher every second day is not petty cash; it is procurement dodging the comparative statement and the purchase order.

How site petty cash gets stolen — and what catches it#

The fraud research is blunt about scale. The ACFE's 2024 Report to the Nations — 1,921 investigated cases worldwide — puts the construction industry's median fraud loss at US$250,000, the fourth highest of any industry, estimates the typical organisation loses about 5% of revenue to fraud, and finds the median scheme runs a full 12 months before detection. A third of cases were enabled by a simple lack of internal controls. Petty cash is rarely the biggest leak on a site — material theft and ghost labour compete hard — but it is the leak with the cheapest fix.

The four patterns that account for most site petty cash loss:

  1. Inflated vouchers. The expense is real; the amount is not. The Rs 300 tempo trip becomes Rs 500, and the difference is invisible because no one prices tempo trips. Caught by: per-head norms (a tempo trip in your city costs a knowable amount) and an approver who reviews before signing, not after.
  2. Ghost expenses. A voucher for a payment that never happened, often with a blank-bill receipt from a friendly vendor. Caught by: insisting on named payees and bills, then occasionally calling the payee. One call, made visibly, changes behaviour for months.
  3. Split vouchers. A Rs 9,000 spend becomes three Rs 3,000 vouchers to duck an approval threshold — the same instinct as splitting a cash payment to duck Section 36(4), and just as detectable. Caught by: reviewing the register by day and payee, not voucher by voucher. Clusters just under the limit glow in the dark.
  4. Recycled bills. The same genuine bill reimbursed twice, weeks apart, sometimes photocopied. Caught by: recording bill number and vendor on the voucher and checking duplicates at replenishment — a thirty-second filter in Excel, automatic in software.

The control stack that makes these hard is short: a written policy with per-voucher and per-day limits; dual approval above a threshold; separation of the three roles (the custodian who pays is not the person who replenishes, who is not the person who reviews — on a small site where one person wears two hats, the third role must sit in the office); monthly reconciliation where cash plus vouchers is counted against the float; and one or two surprise counts a quarter, done by someone other than the custodian, ideally the same visit as a wage register check. None of this requires software. All of it gets easier with it.

Should you replace the cash box with UPI?#

Mostly, yes — and faster than most contractors think. The case is not just convenience:

  • Tax. UPI is a prescribed electronic mode, so the Rs 10,000 disallowance simply does not apply to UPI payments. The tempo owner who is paid Rs 12,000 by UPI costs you nothing extra; in cash he costs you the whole deduction.
  • Evidence. Every UPI payment carries a timestamp, a payee, and an amount you did not handwrite. Half the voucher fills itself, and a recycled bill cannot recycle a transaction ID.
  • Float logistics. No cash in a drawer at a site that floods, burns, and employs strangers. Replenishment becomes a transfer, not an envelope on a bus.

What stands in the way, honestly: some vendors still demand cash (fewer each year, and mostly the ones avoiding tax visibility — which should tell you something about their invoices); connectivity at remote sites can be patchy; and a UPI trail through a supervisor's personal account creates its own mess — his statement becomes your books. The workable pattern for small contractors is a dedicated account or an employer-funded UPI wallet with per-staff limits, kept strictly for site expenses, with the voucher register running exactly as before. The register is still what ties each payment to a project, a head, and an approval — a bank statement alone answers "how much" but never "why". Expense tracking in SiteSetu follows this pattern: site staff record expenses with photos of bills against project and head, approvals happen on the phone, and the register builds itself while the money moves by UPI.

Keep a small cash residue — Rs 3,000–5,000 — for the genuinely cash-only edges, run it on the same imprest arithmetic, and let it shrink.

FAQs#

What is the maximum cash payment allowed per day in construction? Rs 10,000 per person per day, aggregated across all payments to that person, if you want the expense deducted — under Section 36(4) of the Income-tax Act, 2025 (the rule everyone still calls Section 40A(3)). For goods-carriage transporters the limit is Rs 35,000. Pay by UPI, bank transfer or account-payee cheque and no limit applies.

Is a revenue stamp required on petty cash vouchers? On cash payments above Rs 5,000, yes — a Re 1 revenue stamp on the receipt, signed across by the receiver, under the Indian Stamp Act, 1899. Not required for UPI or bank payments.

What is the ideal petty cash float for a construction site? There is no statutory figure. In practice Rs 10,000–30,000 suits most single-project sites — enough for about two weeks of routine small expenses. Replenish against vouchers when 20–30% of the float remains.

Can I claim GST input credit on petty cash purchases? Only with a proper tax invoice from a GST-registered supplier showing your GSTIN — which most petty purchases lack, so the embedded GST is lost. There is no reverse charge on routine unregistered purchases for ordinary contractors, but real-estate promoters on the concessional scheme must watch the 80/20 registered-procurement rule, and unregistered cement triggers 28% RCM.

Who should hold petty cash on site? One named custodian — usually the site engineer or site accountant — who pays and documents. The person who replenishes the float and the person who reviews the register should both be different people. The custodian should never approve their own vouchers.

Petty cash voucher in Excel or software? Start with the free Excel register — it enforces the imprest arithmetic and the voucher fields. Move to an app when you run multiple sites or want photo-backed digital vouchers and UPI trails in one place; a register that reconciles itself daily beats one that reconciles monthly.

References and Further Reading

Primary and supporting sources cited in this article.

Tags:

construction site petty cash managementpetty cash voucher formatimprest system constructionsite imprest registerpetty cash register excelsection 40A(3) cash payment limitsection 36(4) income tax act 2025revenue stamp on vouchersite expense tracking Indiaconstruction expense fraudpetty cash reconciliationUPI site payments

Ready to digitize your construction site?

Site Setu keeps tasks, materials, drawings, and daily progress in one mobile-first record your site team can update from the field.

Start with one project