In short
A defensible supplier ledger separates order, delivery, bill and payment as four dated events per purchase, so a disputed balance is answered from records rather than from recollection.
Material is usually the largest line in a project and the one with the most moving parts. A single order can be delivered in three trips, billed once, part-paid twice and disputed a month later, and by then the only complete account of it is in two people’s heads, which do not agree.
Four events, not one transaction
The mistake almost everyone makes is treating a purchase as a single row. It is four events, and they happen on different days:
- Ordered is what was asked for, at what rate, for which site. This is where the rate is fixed, and where a later dispute usually originates.
- Delivered is what actually arrived, when, and who received it. Frequently less than ordered, occasionally more.
- Billed is what the supplier has invoiced. Should match delivered; the gap between them is the thing to check while the driver is still there.
- Paid is what has left your account against that bill, in one payment or several.
Record all four and the outstanding balance with each supplier is arithmetic. Record only payments and it is an opinion.
The ledger a supplier actually respects
When a supplier calls about a balance, the conversation goes one of two ways. Either you can read back the deliveries and the payments with dates, or you cannot. If you can, the call takes two minutes and the number is agreed. If you cannot, you pay to end the argument, and you will pay again the next time.
A per-supplier ledger needs nothing exotic: every purchase from them, every delivery against it, every payment made, and a running balance. What makes it usable is that it is one list, in date order, that anyone in the office can open without asking a colleague where the file is.
Keep the rate history, not just the current rate
Cement at ₹360 last quarter and ₹385 this quarter is ordinary. What is not ordinary is not knowing which of your sites absorbed the increase, or discovering in March that one supplier’s rate moved twice and nobody renegotiated after the second one.
Because the rate lives on the order and the order lives on the site, the history is a by-product of ordinary entry rather than a separate register somebody has to maintain.
You cannot negotiate from memory. You can negotiate from a list of dates.
And keep the trail
Purchases are where the most hands touch the record: a site manager receives, an office clerk enters the bill, a partner approves the payment. That is not a problem (it is how the work gets done) but it does mean every change needs to carry an author and a timestamp.
Not because anyone is suspected. Because six weeks later, when a figure looks wrong, the useful question is never "who did this?". It is "what did it say before, and when did it change?" A trail answers that in seconds. Memory does not answer it at all.
Sitegride puts sites, sales, purchases, labour and money in one place, in English and Gujarati.