RA billing software holds the money side of a construction contract after the quantities are agreed. It carries the contract BOQ and rates, the cumulative abstract for each running account bill, the deduction heads that client applies, mobilisation and secured advance recovery, retention held and when it becomes releasable, and the three different values every bill passes through: submitted, certified and received. With Pentoggle, a contractor can describe its deduction heads, abstract format and certification cycle and generate the starting application around them, instead of adapting to a system built for someone else's client.
Most construction companies in India already run Tally or a comparable system for accounting, and larger groups run SAP or a construction ERP. Those systems handle purchase, sales, GST, the books and job costing. This is not a proposal to replace them. The RA bill is prepared, submitted and certified as part of the commercial billing process, and the resulting amounts then flow into accounting and payment. That preparation and follow-up is the part that lives in Excel today.
RA billing is often treated as one workflow with measurement, and the two answer different questions. Measurement establishes what quantity was executed and gets it agreed with the client's engineer. Billing takes those agreed quantities and turns them into money: the abstract, what is deducted from it, what is recovered against it, what is held back, and what eventually arrives in the bank. A contractor with excellent measurement discipline can still lose margin at the billing stage, and usually does.
Key takeaways
- Under the common running account structure, each bill restates the position up to date and subtracts what came before, so an error in bill three is still present in bill nine.
- The submitted value, the certified value and the received value are three different numbers, and the middle one is often not tracked separately.
- Certification disputes can arise from variations executed without the required approval, as well as from measurement, rates, incomplete work, deductions and other contractual issues.
- Retention can become a significant receivable that is overlooked after the project team moves on, particularly where its release depends on contractual milestones or the expiry of a specified period.
- One of the most useful numbers for managing RA billing is the value submitted and not yet certified, aged by days since submission.
What Excel does well, and where it stops
Billing engineers are very good at Excel, and the abstract is a table. Item, unit, BOQ quantity, rate, quantity up to date, quantity previous, quantity this bill, amount. Excel handles that natively, the formats can be matched to whatever the client asks for, and the file can be emailed to anybody. Any argument for software has to start by admitting that Excel is doing a real job here.
Where it stops is specific.
The cumulative chain is maintained by hand
Each bill is a new file that copies forward the previous bill's up to date figures. When a quantity is corrected or an item is disallowed, somebody has to carry that correction into every file that follows. Usually they do. Occasionally they do not, and the error is discovered at final bill stage when the client's total and yours differ by a number nobody can explain.
The certified figures overwrite the submitted figures
When the bill comes back certified at a lower value, the natural thing is to update the file. That can leave no record of what was submitted, what was disallowed and why. A year later the contractor may be unable to show a pattern, which is exactly what would have been useful in the claim.
Retention is a formula, not a receivable
In the file, retention is a deduction line that reduces this bill. Nowhere in the file is there a date on which that money becomes payable, a person responsible for asking for it, or a total across projects.
No question can be asked across projects
Total retention outstanding, total submitted and uncertified, average days from submission to certification by client. Each answer requires opening every file for every project, so the answer is produced once a year for the auditor and never used to run the business.
What RA billing software holds
Contract and BOQ with rates
The awarded BOQ item by item with agreed rates, the contract type, and the ceiling quantity each item was awarded against.
The cumulative abstract
Quantity and value executed up to date, less what was billed in previous bills, giving the value of the current bill, with the chain maintained by the system rather than by copy-forward.
Deduction heads for that client
Retention or security deposit, water and electricity charges, hire charges, insurance, quality holds, penalties, TDS, GST-related adjustments, labour cess and other statutory or contractual deductions that apply under the contract and applicable rules. Clients commonly apply different sets, so the application should hold each client's set rather than one standard template.
Advance recovery
Mobilisation advance and secured advance against material at site, with the recovery schedule, how much has been recovered up to date and how much remains outstanding under the contract.
Submitted, certified and received
Three values on every bill, with the date of each, the certified amount when it differs from the submitted amount, and the reason recorded against the item that was cut.
Retention as a tracked receivable
Amount held per project, the event that makes each part releasable, the date that event is expected, and who is responsible for asking.
Quantity against BOQ ceiling
Executed quantity compared to awarded quantity item by item, so an item approaching or crossing its BOQ quantity is visible before the bill is prepared rather than after it is cut.
Subcontractor bills on the same structure
The bills you receive back to back against the bills you raise, with material issued and recovered, retention you hold and the same certification cycle running in the opposite direction.
Submitted, certified, received
Cash forecasts are often run on submitted value. It is the number the billing engineer produces, it arrives on time, and it feels like the answer. It is also the least certain of the three.
The certified value is the amount certified for payment by the person or authority designated under the contract, after applying the contract's measurement, approval, valuation and deduction requirements. Differences from the submitted amount may arise from disputed quantities, unapproved variations, rates, incomplete or unaccepted work, deductions or other contractual matters. On a first RA bill for a new client, the gap between submitted and certified can be substantial. On a mature contract with a familiar client it narrows, which is itself useful information about who you are working with.
The received value is what arrives, on a date determined by the client's payment terms. Depending on the contract, the payment period may run from certification, submission, receipt of a valid bill, or another defined milestone, so the applicable contract should be checked before assuming when the payment clock starts.
Holding all three on the same record makes several things visible that are otherwise invisible. How long each client takes to certify. Which clients cut consistently and on what grounds. Whether a specific site engineer's bills get cut more than others, which is usually a measurement discipline problem rather than a billing one. And the total value of work that has been executed, submitted and is currently sitting with somebody else, which for many contractors is the single largest number on their balance sheet that they cannot state without a week of work.
Your billing dispute is usually a variation that was never approved
When a bill is cut, the instinct is to treat it as a billing problem and push back at the billing stage. That is usually the wrong place to fight.
The common pattern runs like this. Site executes something the drawing showed but the BOQ did not contain, or executes more quantity of an item than was awarded because the actual site condition required it. Nobody raises a variation at the time, because the site team is executing and the commercial team is not standing there. The quantity goes into the measurement, the measurement goes into the abstract, and the client's engineer disallows it because there is no approved item or no approved excess quantity to bill it against.
By the time this surfaces, the work is built. The negotiating position is gone. The client has no incentive to approve something that already exists and the contractor has no leverage.
The fix is upstream. Executed quantity has to be visible against awarded quantity while the work is in progress, so that an item crossing its BOQ ceiling triggers a variation request rather than a disallowed line four weeks later. That is a link between the billing record and the site record, and it is one of the strongest arguments for holding both in the same application. The change orders and variations guide covers the approval side, and the measurement guide covers getting quantities agreed in the first place.
Retention is the receivable nobody owns
Retention is deducted at a small percentage of each bill, which is why it never feels like a decision. At 5% on a ₹5 crore contract that is ₹25 lakh, sitting with the client, earning the contractor nothing.
Depending on the contract, retention may be released in stages, and depending on the contract those stages may be tied to events such as completion, a completion certificate or the end of the defect liability period. Whatever the arrangement, release is tied to events, and events need somebody to notice them.
The reason retention leaks is organisational rather than financial. By the time the defect liability period ends, the project team has demobilised and moved to other sites. The project manager who would have known the client contact is on another project or at another company. Nobody in accounts has a trigger, because in the accounting system, retention can end up appearing as a reduction in the amount received rather than as an actively managed receivable with a release date and owner. The client has no obligation to volunteer it. So it sits, and after two or three years it can become overdue to the point of being treated as unrecoverable, without anybody ever having decided to abandon it.
An application that holds retention as its own record with a release event, an expected date and a named owner turns this from memory into a task. The mechanics are simple and the discipline is what is missing, which is exactly the sort of problem that software solves well. For contractors with significant retention outstanding across multiple projects, a dedicated retention register can be one of the highest-value parts of the application.
Bill formats vary by client, which is the argument for building rather than buying
A packaged billing product has to pick a set of deduction heads, an abstract layout and a certification flow. Indian construction contracts do not share those. A government department applies a security deposit, labour cess, TDS and other statutory or contractual deductions, and expects the abstract in a departmental format. A private developer applies retention, a debit note for cement and steel issued from their stores, water and electricity charges at a percentage, and wants the bill in their own template. A main contractor deducting from an MEP subcontractor applies its own retention and passes down whatever its client did to it.
A billing engineer working across four clients maintains four different Excel templates and knows which is which. A packaged system forces those four into one shape, and the output has to be reformatted before it can be submitted anyway, which means the system is being maintained in parallel with the work rather than doing it.
With Pentoggle you describe the contracts you actually have, including the deduction heads each client applies, the abstract format each expects and the certification cycle each runs. When you win work with a new client whose bill looks different again, you describe the difference and the application updates. A practical starting point is one client's format and the retention register, adding the rest as bills come up.
Tax treatment differs by contract type and is revised periodically, so confirm the deductions and rates that apply to your contracts with your CA and build the application to hold what they specify.
Where RA billing looks different by business type
- Infrastructure and Road Contractor Software, where billing runs against chainage, departmental formats apply and price escalation clauses add a computed component to each bill.
- MEP Contractor Software, where the bill goes to a main contractor whose own certification has to happen first, so the payment cycle is stacked.
- Interior Fit-Out Contractor Software, where projects are short enough that there may be only two or three bills and a disputed final bill is most of the risk.
- Home Builder Software, where billing is stage-linked against an individual owner rather than measured, and collection is a relationship problem.
- Labour Contractor Software, where the bill is rate against executed unit and has to reconcile against wages already paid out.
- PMC Software, where the firm sits on the certifying side and needs the same record from the opposite direction.
Why construction companies choose Pentoggle for RA billing
Your client's deduction heads
Each client's set held separately, so the bill that goes out is already in the shape that client accepts.
Works alongside Tally
Pentoggle handles bill preparation, certification tracking and retention. Your accounting stays where your CA already works.
The cumulative chain is maintained
Up to date figures carry forward and corrections propagate, instead of being copied by hand into the next file.
Retention with a due date
Held amounts become tracked receivables with release events and owners, across every project at once.
Changes in days
A new client with a different bill format does not become a three month project.
A useful number for RA billing
Value submitted and not yet certified, aged by days since submission.
Turnover describes what you have earned. Receivables describe what you are owed. Neither shows the money that is currently sitting in somebody else's inbox, which is work you have already paid for in material and wages and cannot yet invoice against.
Sort submitted bills by days since submission every week and work from the top. Bills sitting past the certification period in the contract are the ones to chase, and in most companies the same two or three clients appear at the top of that list every month, which tells you something worth knowing before you bid for their next project.
One caveat comes with the number. It is only as honest as the submission date, and a submission date entered a week late produces an ageing figure that is wrong in a way that looks precise. If the ageing looks better than the cash position feels, the dates are the problem.
Ready to build RA billing software?
A contractor generally knows what it has built. Knowing exactly what it has been paid for is often harder.