A contractor running five active projects is typically dealing with fifty to a hundred vendors at once, each with different terms, advances, retention clauses and tax treatment — and many supplying more than one site. Tracked manually, this is where money quietly leaves the business. This guide covers how to keep vendor payments under control across projects.
Key takeaways
- One consolidated ledger per vendor, broken down by project — not one file per vendor per site.
- Three-way matching before payment is the highest-value control you can add.
- Advances and retention are balance-sheet items, not adjustments to remember.
- Most payment fraud starts with a bank-detail change, not a fake invoice.
Why vendor payments are complex in construction
A typical Indian construction company with five active projects deals with fifty to a hundred vendors simultaneously — cement suppliers, steel traders, sand and aggregate dealers, electrical and plumbing sub-contractors, labour contractors, plant and machinery rentals, and specialists for waterproofing, fire safety and lifts.
Each has a different payment cycle, advance terms, retention clause and GST treatment. A single vendor may supply several projects, with separate orders, rates and credit terms for each. The recurring failures are consistent:
- Duplicate payments because an advance adjustment was missed
- Vendors paid for deliveries nobody verified
- TDS deduction errors that surface later as notices
- Retention never tracked, leading to overpayment at project close
- Cheques issued but not recorded, making bank reconciliation painful
None of these is exotic. They persist because the information needed to prevent them sits in different places — the order with procurement, the receipt at the site, the invoice with accounts.
The consolidated vendor ledger
The foundation is a vendor ledger that is genuinely consolidated. For construction this is not a simple accounts-payable ledger; it has to carry:
- Project-wise breakup — how much you owe this vendor, per project, within one total
- Advances — given, linked to specific orders, and adjusted automatically against later invoices
- Retention — held per bill, with its release date
- Debit and credit notes — material returns, quality deductions, rate revisions
- Payment instrument — cheque number, NEFT/RTGS reference, UPI transaction ID
The specific failure a consolidated ledger prevents: a vendor supplying three of your sites treats you as one account, while you treat them as three. When they claim a balance you cannot verify it, because your figures live in three files maintained by three people. You end up negotiating from a weaker position than your own records should allow.
It also prevents the awkward inverse — chasing a vendor for delivery on one project while owing them a substantial balance on another. See how BuilderXPro manages vendor ledgers.
Three-way matching: PO, GRN, invoice
The most powerful control in construction procurement is comparing three documents before releasing payment:
- Purchase order — what you ordered: item, quantity, rate, delivery schedule, terms
- Goods receipt note — what actually arrived: quantity, quality, photographs, store sign-off
- Vendor invoice — what is being billed: quantity, rate, taxes
Mismatches to flag automatically:
- Invoice quantity exceeds GRN quantity — billing for undelivered material
- Invoice rate exceeds PO rate — an unauthorised increase
- GRN quantity exceeds PO quantity — over-delivery accepted without authorisation
- GST rate on the invoice inconsistent with the HSN in the order
Where matching usually breaks
In practice the difficulty is not the matching logic — it is that construction deliveries rarely arrive in one clean event. Eighty bags today against an order for a hundred, the balance next week, both on one invoice. If your system forces the GRN to equal the PO, staff will record fiction to get past the screen, and the matching becomes theatre.
Ask specifically how partial receipts, excess deliveries and quality rejections are handled. See construction purchase order software for the questions worth putting to a vendor.
Advances and retention
These two mechanics cause most reconciliation pain, and both are ledger problems rather than accounting problems.
Advances
Advances are ordinary in Indian construction — cement and steel suppliers often want a substantial proportion up front, labour contractors take weekly advances, plant hirers charge mobilisation. The discipline that matters:
- Record every advance with date, amount, instrument and the order it belongs to
- Adjust proportionally against each invoice on a schedule agreed up front, not ad hoc
- Never let the unadjusted advance exceed the remaining order value — this is the point at which an advance becomes an unsecured loan
An advance is not an expense. It is money the vendor owes you in goods or work, and it belongs on the balance sheet until delivered against. Treated as a payment, it disappears, and you pay again for the same material.
Retention
Commonly 5–10% of certified value, released partly at completion and the balance after the defect liability period. Two things must be recorded at the moment of deduction: the amount, and the date it falls due. Untracked retention is the most common unpleasant surprise at project close — the vendor remembers it precisely, and the vendor is usually right.
Approval workflows
Payment approvals should follow a structured hierarchy. A workable shape for a mid-sized contractor, to be calibrated to your own scale:
- Smaller routine payments — site verifies the GRN, project manager approves
- Mid-value — project manager recommends, finance head approves
- High value — finance head recommends, director approves
- Exceptional — dual director approval
Set the bands where they change a decision. Thresholds set too low make approval a reflex: the approver stops reading, the queue becomes a bottleneck, and urgent payments get pushed through informally. That is worse than no control, because it produces an audit trail that looks like governance and is not.
Digital approvals create an immutable record of who approved what, when, and with what note — which matters for internal control and for any external audit. Learn about approval workflows and audit logs.
Running a weekly payment cycle
Ad-hoc payment — paying whoever calls loudest — is expensive in a way that never shows on any report. It destroys your negotiating position, makes cash forecasting impossible, and quietly rewards the vendors who chase hardest rather than the ones who perform best.
A fixed weekly cycle fixes more than it sounds:
- Cut-off day — invoices received after it go into next week’s run
- Matching pass — everything three-way matched; exceptions listed, not silently held
- Exception review — a named person clears or rejects each mismatch
- Approval — one batch through the hierarchy rather than one-by-one interruptions
- Payment and posting — instrument reference recorded against the ledger immediately
Tell vendors the cycle. A supplier who knows payments run every Thursday stops calling on Tuesday, and will often give better terms for predictability than for speed.
The controls that stop payment fraud
Payment fraud in construction is rarely an elaborate fake invoice. It is usually mundane, and it usually begins in one of three places.
- Bank-detail changes. A request arrives by email or WhatsApp saying the vendor’s account has changed. This is the single most common route, and the fix is a five-minute policy: bank detail changes require verification on a known phone number and a second approver. Never action one from an email alone.
- Invoices with no matching order. Services in particular — testing, transport, security — often arrive with no PO, which means no rate was ever agreed. Require an order for services too, even a simple one.
- Duplicate invoices. The same invoice submitted twice, weeks apart, sometimes with a different reference. Systems should reject a duplicate invoice number per vendor automatically.
Of these, the bank-detail change is the one worth acting on today. It requires no software, costs nothing, and closes the route that causes the largest single losses.
GST and TDS compliance
Every vendor payment carries tax implications:
- GST input credit — invoices need correct GSTIN, HSN and rate before payment. More importantly, your credit depends on the vendor actually filing; reconciling purchases against GSTR-2B monthly is part of vendor management, not just accounting.
- TDS — Section 194C applies to contractor payments, broadly 1% for individuals and HUFs and 2% otherwise, subject to prevailing per-transaction and annual thresholds.
- TDS certificates — issued to vendors on the prescribed cycle; delays attract penalties.
- Reverse charge — applicable on certain supplies, including from unregistered vendors.
Rates, thresholds and applicability change and depend on how your contracts are structured. Treat the above as orientation and confirm the current position with your CA — the value software adds is producing accurate, complete inputs on time, not deciding what is owed. Our construction accounting guide covers the wider picture.
Key takeaways
- Keep one consolidated vendor ledger with project-wise breakup, advances, retention and instrument references.
- Three-way matching prevents overpayment — but only if partial and excess deliveries can be recorded honestly.
- Advances are receivables and retention is a liability; both need dates, not memory.
- Approval bands should be set where they change a decision, not where they create a reflex.
- A fixed weekly payment cycle buys better terms than fast ad-hoc payment does.
- Verify bank-detail changes on a known number, with a second approver.
See how BuilderXPro connects procurement and finance so orders, receipts and payments stay linked to one vendor record, or book a demo.