A builder or contractor rarely has just one job running. The same thekedar may be pouring a slab in one colony, finishing plaster in another and starting foundations on a third plot. If all of that sits in one running account, nobody can say which site owes what. Site wise billing solves this: one customer, but a separate ledger, statement and credit limit for each project.
This guide explains how to set it up, how to share statements that builders actually accept, and how to control credit project by project.
Why one big running account causes trouble
A single running account looks simple, but it creates three common problems:
- Payment disputes. The builder's accountant pays against Site A's bills, but your ledger knocks it off the oldest bill, which belongs to Site B. Now both sides have different balances.
- Hidden risk. A site that has stalled, perhaps because the plot owner stopped paying the contractor, keeps building up dues inside the total. You only notice when the whole account looks too big.
- Owner-wise billing. Many contractors work for different house owners. Each owner may want bills in his own name, or the contractor may need a statement per site to recover money from that owner.
Keeping each project separate fixes all three without losing the overall view of the customer.
Two ways to set up site wise billing
Option 1: one party, with site tagged on every bill
Keep the builder as one customer and record the site name or delivery address on each invoice and challan. Statements are then filtered by site. This suits smaller contractors with two or three sites and one person handling payments.
Option 2: a separate ledger per site
Create a separate account for each project, for example "Sharma Construction – Danapur Site". Each has its own opening balance, credit limit and statement. This suits builders with several projects running at once, or where different owners pay for different sites.
| Point | Site tag on one party | Separate ledger per site |
|---|---|---|
| Setup effort | Low | Medium |
| Credit limit per site | Harder | Easy |
| Statement per site | By filter | Direct |
| Overall view of the builder | Direct | Add up the site ledgers |
| Best for | 2–3 sites, single payer | Many sites, different payers |
Whichever you choose, be consistent. Mixing both for the same customer is where confusion starts.
What the bill should show
On each GST invoice, show the customer (bill-to) details and the site (ship-to) delivery address. If the builder is registered, use his GSTIN so he can claim input tax credit. If the bill is in the house owner's name instead, the owner becomes the recipient; agree this before the first delivery, not after. Where the billing party and delivery address are in different places, place-of-supply rules can affect whether CGST/SGST or IGST applies, so ask your CA. Get the GSTIN and addresses right on the first bill; correcting them later means credit notes and fresh invoices.
Each truck to a site should carry a delivery challan or invoice with the vehicle number and site address. For consignments over ₹50,000, an e-way bill is generally needed; check your state's limit for movement within the state.
Worked example: one builder, three sites
Example figures for a fictional contractor, used only to show the method.
| Site | Billed so far | Received | Outstanding | Site credit limit |
|---|---|---|---|---|
| Site A – Kankarbagh | ₹4,12,000 | ₹3,00,000 | ₹1,12,000 | ₹1,00,000 |
| Site B – Danapur | ₹2,68,500 | ₹1,50,000 | ₹1,18,500 | ₹1,00,000 |
| Site C – Phulwari | ₹95,000 | ₹95,000 | ₹0 | ₹1,00,000 |
| Total | ₹7,75,500 | ₹5,45,000 | ₹2,30,500 |
In one running account, you would see ₹2,30,500 due and think, "He is a good customer, Site C is fully paid." Split by site, the picture is sharper:
- Site A is ₹12,000 over its limit.
- Site B is ₹18,500 over its limit.
- Site C is clear and can keep getting material.
So you can keep supplying Site C while asking for payment on A and B, rather than stopping the whole account or, worse, letting all three grow.
Recording payments against the right site
When the builder pays ₹50,000, ask which site it is for and note it on the receipt. If you use separate ledgers, post it there. If you use site tags, link the receipt to that site's invoices. A short WhatsApp message like "Received ₹50,000 against Danapur site, balance ₹68,500" closes the loop immediately.
Statements that builders actually accept
Builders and their accountants reconcile your statement with their own site records. Make it easy for them:
- One statement per site, with site name and period in the heading.
- Bill-wise detail: date, bill number, challan number, items in short, amount.
- Payments with date, mode and reference.
- Running balance after every entry.
- Ageing summary at the bottom: 0–30, 31–60, 61–90 and 90+ days.
Send it on a fixed day every month, so the builder's accountant expects it. A party statement shared as PDF on WhatsApp usually gets a faster response than a phone call.
Credit control project by project
Each site carries its own risk. A few rules many dealers find useful:
- Set a limit per site based on the stage of work and the builder's payment record, not just his total size.
- Watch for stalled sites. If deliveries to a site stop but dues remain, treat it as a warning sign and follow up quickly.
- Tie big supplies to milestones. Before a slab pour, which needs a large cement and steel lot, clear the previous dues on that site.
- Use ageing, not just totals. ₹1 lakh that is 20 days old is very different from ₹1 lakh that is 100 days old.
Our guides on building a credit policy and payment recovery go deeper into setting limits and following up.
Quotations, rate agreements and running accounts
Builders often fix rates for a project at the start, for example for a set quantity of TMT or cement over a period. Record the agreed rate against that site, with validity dates. When market rates move, you will know which site is on a locked rate and which is on daily rates. If the rate agreement is site-specific, a quotation linked to that site makes later billing simpler.
For running accounts across many sites, also keep a short note per site: site in-charge name and phone number, owner name, and who approves payments. Staff change; notes stay.
How software makes site wise billing practical
Doing this on paper is possible but slow. In MaterialBill, you can keep party-wise agreed rates, issue challans with site and vehicle details, and track udhaar with ageing, credit limits and WhatsApp reminders through udhaar management. If you work mostly with contractors, the contractor billing software page shows how these features fit together.
Frequently asked questions
Should I make a separate GST invoice for each site?
Yes, a separate invoice per delivery to each site is the cleanest approach. It keeps the ship-to address, challan and e-way bill clear, and makes site-wise statements accurate.
Can one builder have different GSTINs on different sites?
A business normally has one GSTIN per state. If the builder works in two states, he may have a different GSTIN in each. Use the GSTIN he gives you for that billing, and confirm it before the first bill.
What if the builder pays a lump sum without saying which site?
Ask before posting it. If he does not say, agree a rule in advance, such as adjusting against the oldest bill across all sites, and mention it on the receipt you send him.
How do I handle a site that has stopped work?
Stop fresh credit to that site, send a site-wise statement with ageing, and follow up for payment. Keep supplying active, paying sites if the builder's overall record is fine.
Is a running account bad for builders?
No. A running account is normal in this trade. The problem is only when many projects are mixed into one balance. Site-wise ledgers keep the running account but make each project visible.
Builders value suppliers who send clear, site-wise statements. If you want separate ledgers, challans and reminders for every project without extra paperwork, you can start free with MaterialBill and set up your biggest builder first.