Commercial teams on Pakistani sites still lose days reconciling bills in Excel, WhatsApp threads, and handwritten IPC registers. When retention, variations, and subcontractor offsets live in different files, leadership sees cash late and disputes grow.
What good PKR billing looks like on site
- One bill record tied to the project, client, and approval chain
- Retention and deductions calculated consistently, not retyped each month
- Branded PDF output your client recognises as professional
- Subcontractor and supplier payments visible next to client billing
Smart Construction keeps commercial workflows in PKR end to end. Site and office teams work from the same numbers, so certified amounts, collections, and outstanding retention do not drift between modules.
Practical rollout for contractors
Start with one active project: define bill templates, approval roles, and retention rules. Run two billing cycles in parallel with Excel before switching fully. Most merchants in Lahore and Karachi complete this in two to four weeks.
Ready to see PKR billing on your projects? Book a demo at https://smartconstruction.pk/book-demo or view transparent plans at https://smartconstruction.pk/pricing.
Retention: the largest number nobody tracks properly
On a contract certifying monthly at 10 percent retention, a contractor turning over a modest annual figure can have a very large sum held by clients at any moment. That money is on your balance sheet in principle and nowhere in practice if the only record is a column in a workbook maintained by one person.
Retention goes wrong in three predictable ways. It gets released twice, because two people were tracking it separately. It never gets released, because the event that triggered release passed without anyone noticing. Or it becomes unstateable, because four years of certificates across three phases have to be reconstructed from PDFs before anyone can even open the conversation.
The fix is to hold retention as a rule on the bill rather than as a note beside it. Every certificate deducts the configured percentage automatically. Release is recorded against the event that triggered it. The total held per client and per project is a report rather than a reconstruction, which means it can be chased when it becomes due instead of when somebody remembers.
Variations: work you did and did not get paid for
Ask any Pakistani contractor where their margin went on a difficult job and variations will come up before anything else. The pattern is always the same. Additional work is instructed on site, usually verbally, often by someone with the authority to instruct it and no authority to price it. The work gets done because refusing would stop the job. Months later, at final account, the claim cannot be substantiated because nothing was recorded at the time.
The recovery point is the moment of instruction, not the moment of billing. If extra work is recorded against the project on the day it is agreed, with what was asked for and who asked, then it enters the next certificate as a normal line. If it is not, you are attempting to reconstruct an agreement from memory against a client who has every incentive to remember it differently.
Deductions, withholding, and the net receivable
A gross certificate value is not what you will receive. Clients withhold tax at source, apply contractual deductions, and sometimes net off back-charges. If your receivables ledger tracks gross amounts, it will consistently overstate what is owed, and your collection team will spend part of every month chasing amounts that were legitimately withheld.
Record deductions against the bill when payment is received. The outstanding balance then reflects what is genuinely still due, which changes both the accuracy of your cash forecast and the credibility of your collection calls.
What the client actually receives
This matters more than it should. A certificate arriving as a spreadsheet screenshot in a WhatsApp message gets treated differently from a branded PDF on a letterhead, by the same person, for the same amount. It is not fair, and it is entirely real.
- One letterhead for a pending invoice, another for a paid receipt, so the document matches its state
- Sequential, traceable numbering that an accounts department can file
- The same layout on every project, so a client learns to read your documents
- Supporting measurement and site evidence attached rather than promised
A practical sequence for moving off spreadsheets
- Load opening balances: what each client owes, and how much retention is held against every contract
- Configure retention percentages, standard deductions, and approval limits once, at company level
- Set up invoice and receipt letterheads before the first bill goes out
- Run one full certification cycle alongside your existing method and reconcile the two
- Move receivables tracking across, and turn on automated overdue reminders
- Stop maintaining the workbook. Half-migrations produce two wrong answers instead of one right one
The last step is the one teams skip, and it is the one that decides whether any of this works. A billing system running in parallel with a spreadsheet is worse than either alone, because now nobody knows which is authoritative.