RA Bill Guide for Indian Contractors (2026 Guide)

You submitted the RA bill on the 2nd. It came back on the 19th with one line scribbled on the covering page: "JMS not attached for Wing B plaster." Seventeen days lost to a missing sheet — while your cement supplier tightens credit and the bar benders ask, politely for now, about last month's wages.

If you are a contractor, billing engineer or site engineer on Indian projects, Running Account Bills are how you get paid. This guide covers the whole cycle: what RA bills are, how to prepare them so they do not bounce, the deductions that confuse everyone, how disputes start and how to keep them from starting, and where digital tools genuinely shorten the cycle.

What is an RA bill (Running Account Bill)?#

An RA bill — Running Account Bill — is a periodic payment claim submitted by a contractor for work completed during a billing period. On most Indian construction contracts, that period is monthly.

The logic is simple: the contractor is not paid in one lump when the project finishes. Payments are released in stages as work progresses. Each RA bill captures the cumulative work done up to that point, deducts what has already been paid, and claims the net balance.

Key characteristics of RA bills:

• They are interim, not final
• They are cumulative — each bill covers all work from project start, not just the current month
• Payments carry deductions (retention, TDS, advances and so on)
• They stand on verified measurements as supporting evidence
• The final bill at completion replaces all RA bills with a final settlement

RA bills run across every kind of Indian construction: residential buildings, infrastructure (roads, bridges, drainage), commercial fit-outs, government works (CPWD, PWD, NHAI) and private developments.

Why RA bills matter: the cash flow reality#

For Indian contractors — SMBs especially — RA bills are the cash flow. The cycle looks like this:

1. You spend on materials, labour and equipment through the month
2. At month end, the billing engineer compiles quantities and submits the RA bill
3. The client or PMC verifies measurements through joint measurement
4. After verification, the bill is certified for payment
5. Payment is released, minus deductions

The submission, certification and payment periods are contract-specific. Map every promised date and approval step before work starts, because you are financing the gap between site expenditure and certified payment. A complete bill — one that does not come back for missing measurements or documents — is what protects that cycle.

A delayed or disputed RA bill costs more than interest. Subcontractor payments slip and site friction builds. Material suppliers cut credit limits or quietly hike rates. Labour walks out when wages are late. And your negotiating position with the client weakens with every month you are the one asking.

The RA bill process: step by step#

Here is the standard sequence on Indian projects.

Step 1: Site measurements#

Every RA bill starts at the tape. The billing engineer or site engineer records quantities of work completed during the period.

How measurements are taken:

• Physical measurement at site (length, breadth, height or depth)
• Quantities calculated per contract specifications and IS Code 1200 (Method of Measurement of Building and Civil Engineering Works)
• Entries recorded in the Measurement Book (MB)
• Location reference included every time — wing, floor, grid, chainage

What gets measured: earthwork (excavation, filling, levelling); concrete by grade, from foundations to slabs; reinforcement steel by diameter and location; blockwork and brickwork by type and thickness; plastering by type, thickness and location; waterproofing, flooring, painting and MEP items — in short, anything with a line in the Bill of Quantities.

Step 2: Joint measurement and verification#

Your measurements must be verified by the client's representative — joint measurement — and the agreed quantities recorded on a joint measurement sheet (JMS).

Do it properly: schedule joint measurement 2 to 3 days before bill submission, walk the work together and agree quantities on the spot, record them in the MB with signatures, note disputed or pending items separately, and photograph completed work as evidence.

Joint measurement is where most billing disputes are born. Skip it, or do it casually from the site office, and expect the bill to be contested.

Step 3: Prepare the RA bill#

Using verified measurements, the billing engineer compiles the bill. The standard structure:

RA Bill Components:

Calculation formula:

Net Payable = Cumulative Work Value - Retention - TDS - GST TDS - Advance Recovery - Material Charges - Penalties - Amount Already Paid

Step 4: Bill submission and certification#

The bill goes to the client or PMC with its supporting documents. The client's QS reviews it, checks measurements against site records, and certifies the payable amount.

Standard supporting documents: measurement sheets from the MB, the joint measurement certificate signed by both parties, photographs of completed work, concrete cube test reports for RCC items, material test certificates where required, variation order approvals for extra items, and updated progress photographs. Compile this set completely, every month — an incomplete pack is the most common reason a bill sits unread.

Step 5: Payment release#

Once certified, the bill moves to accounts for processing. Payment typically comes by RTGS, NEFT or cheque.

Understanding deductions in RA bills#

Deductions cause more confusion and dispute than anything else on an RA bill. Here is the honest breakdown.

1. Retention money and contract security#

Do not assume a universal percentage, cap or 50:50 release — those are habits, not rules. Private and public contracts use the labels retention, security deposit and performance guarantee differently. Read the signed conditions, the amendments and the release milestones, and keep each withheld amount in its own ledger.

CPWD's current structure uses contract-specific performance guarantee and security-deposit provisions rather than the generic "10 percent retention capped at 5 percent" shortcut still repeated in older articles. The retention money and defect-liability guide explains the distinction and provides a tracker.

Illustrative example only: if a private contract expressly withholds 5 percent from a Rs 25,00,000 certified amount, the current deduction is Rs 1,25,000. The bill should also show cumulative withholding, releases, balance and the contractual release trigger.

2. TDS (Tax Deducted at Source) under Income Tax#

Under Section 194C of the Income-tax Act, 1961, the client must deduct TDS on contractor payments. For any payment or credit on or after 1 April 2026 the same obligation moves to Section 393(1), Table Sl. No. 6(i) of the Income-tax Act, 2025 — the section number changes, the rates and thresholds below do not.

• Rate for individuals/HUF: 1% of payment amount (excluding GST)
• Rate for companies/firms: 2% of payment amount (excluding GST)
• Threshold: TDS applies when a single payment exceeds Rs 30,000 or aggregate payments in a financial year exceed Rs 1,00,000
• Important: TDS is deducted on the base amount, not on the GST component

Example: Certified amount (excluding GST): Rs 20,00,000 GST at 18%: Rs 3,60,000 Total invoice: Rs 23,60,000 TDS at 2% (on Rs 20,00,000): Rs 40,000

3. GST TDS (for government contracts)#

For government departments and specified entities, TDS under GST applies at 2% (1% CGST + 1% SGST) on taxable value exceeding Rs 2,50,000. This is separate from Income Tax TDS and applies only to notified government bodies.

4. Advance recovery#

If the client gave you a mobilization advance at the start, it is recovered proportionally from each RA bill.

• Typical advance: 10 to 20% of contract value
• Recovery: usually at the same percentage from each RA bill until fully adjusted
• Security: usually backed by a bank guarantee

Example: Contract value: Rs 1,00,00,000 Mobilization advance (10%): Rs 10,00,000 Recovery rate: 10% of each RA bill RA Bill 3 gross: Rs 25,00,000 Advance recovery: Rs 2,50,000

5. Material recovery#

Where the client supplies materials free-issue, the cost may be recovered from your bills when actual usage exceeds the estimated allowance. The classic case: client-supplied cement and steel, deducted when consumption crosses BOQ norms.

6. Liquidated damages and other disputed recoveries#

The rate, cap, trigger, notice and right to deduct liquidated damages come from the contract and the governing law — there is no safe universal weekly percentage. Show a proposed or disputed recovery separately from an accepted deduction, preserve the notice and the delay analysis, and never let it get silently netted into the certified quantity.

The Measurement Book (MB): your billing foundation#

The Measurement Book is the primary evidence behind every RA bill. On government projects (CPWD, PWD, MES) it has a prescribed format; on private projects the format varies but the principles do not.

What goes in a Measurement Book#

Every entry should carry:

1. Date of measurement
2. Description of work — matching the BOQ item description word for word
3. Location (wing, floor, grid line, chainage, room number)
4. Dimensions (length, breadth, height or depth, in metres)
5. Quantity calculation (number x L x B x H, in the correct unit)
6. Deductions for openings, voids, or portions already measured
7. Running total — cumulative quantity for the item
8. Signatures — measured by, checked by, verified by

CPWD Measurement Book format#

For CPWD and government projects, the MB is standardised: books are serially numbered with an eight-digit code; entries are in ink, never pencil; no overwriting — corrections are scored through with a single line and initialled; each page is signed by the Junior Engineer and countersigned by the Section Officer; and the Abstract of Measurements is prepared from MB entries to compile the RA bill.

The digital e-Measurement Book (e-MB) is now mandatory across CPWD field offices, enabling online progress reporting and cutting the paperwork.

Common MB mistakes that delay RA bills#

1. Vague locations: "plastering done" instead of "internal plastering 12mm thick, Wing A, Floor 2, Flat 201, bedroom 1"
2. Missing deductions: window and door openings not deducted in plaster or blockwork
3. Wrong units: steel recorded in running metres instead of kilograms
4. Unsigned entries: measurements with no verification signature
5. BOQ mismatch: descriptions that differ from the BOQ wording
6. No photographs: fatal for concealed work — waterproofing, reinforcement — that can never be re-measured

RA bill format: practical example#

A simplified RA bill for a residential building project:

Project: G+5 Residential Building, Wakad, Pune Contractor: XYZ Construction RA Bill No.: 4 Period: 1 March 2026 to 31 March 2026

Part A: Work Done Summary#

Gross amount (cumulative): Rs 1,22,50,500

Part B: Deductions#

Total deductions: Rs 11,16,585

Part C: Net Payable#

Common RA bill disputes and how to avoid them#

Billing disputes are the most common cause of payment delay on Indian sites. Here are the ones you will meet, and how to stay out of them.

1. Measurement disputes#

The problem: the client's QS measures less than you claimed.

How to avoid it: always hold joint measurement before submission. Photograph everything before it gets covered — reinforcement, waterproofing, concealed piping. Measure by standard IS 1200 methods. Keep MB entries specific, with exact locations. And get the joint measurement certificate signed on site, that day, not "next week in office."

2. Rate disputes on variation items#

The problem: the extra work is done, the rate was never agreed.

How to avoid it: never start extra work without a written variation order. Agree the rate basis — contractual rate, market rate, or cost plus — and get the order signed before executing. Keep separate measurement records for variation items.

3. Quality-based deductions#

The problem: the client deducts for alleged deficiencies — poor finish, a failed cube test.

How to avoid it: complete quality checklists before claiming any item. Attach test reports (cube test, slump test) with the bill. Clear snags before billing, not after. Keep a defect resolution log.

4. Delay in bill processing#

The problem: you submitted on time; certification drifted, pushing payment beyond 45 to 60 days.

How to avoid it: submit complete bills with every supporting document on the first attempt. Run a bill tracking register — submitted, under review, certified, payment processed. Escalate early when processing exceeds the contractual timeline. Better still, write the billing timeline into the contract itself (say, certification within 14 days, payment within 30 days of certification).

5. Back-to-back payment issues (the subcontractor's view)#

The problem: the main contractor delays your payment citing non-receipt from the client.

How to avoid it: separate your payment terms from the client's terms where you can, and maintain your running bills independently. Indian courts have ruled that back-to-back clauses cannot be used to defer subcontractor payments indefinitely.

RA bill vs other bill types in construction#

Where RA bills sit among the rest:

Set contract-specific billing service levels#

Replace industry averages with dates taken from your signed contract and approval matrix. Track at least these timestamps:

Report median days at each stage, and the value held up in queries. A single end-to-end average hides the thing you most need to know — whether the delay sits with measurement, your own documentation, consultant certification, client approval or payment processing.

How digital tools improve RA billing#

Traditional RA billing runs on physical Measurement Books, Excel calculations and manual document compilation. Delays, errors and disputes are baked in.

Digital construction management tools shorten each stage:

Measurement recording: measurements captured on mobile with location tags and photos, quantities calculated automatically from the dimensions entered, each measurement linked directly to its BOQ item.

Bill generation: cumulative quantities and amounts auto-calculated; standard deductions (retention, TDS, advance recovery) applied consistently; the bill produced in the same format every month; status tracked from submitted through certified to paid.

Dispute prevention: joint measurement records carry timestamps and signatures, photo evidence is tied to specific BOQ items and locations, a full audit trail shows who measured what and when, and BOQ quantities and rates are under version control.

Cash flow visibility: a dashboard of certified versus paid amounts, a retention tracker across all projects, ageing analysis for overdue bills, and cash-inflow forecasts built from planned billing.

30-day plan to improve your RA billing process#

Week 1: Standardize your BOQ and measurement format#

• Make BOQ item wording match contract descriptions exactly
• Create a standard measurement sheet template with location fields
• Train site engineers on IS 1200 measurement methods
• Fix one naming convention for locations and stick to it

Week 2: Implement joint measurement discipline#

• Schedule joint measurement 3 days before bill submission
• Create a joint measurement certificate template
• Start photographing all work before it gets concealed
• Open a dispute log for contested measurements

Week 3: Streamline bill compilation#

• Build a standard RA bill template covering every deduction type
• Set up the bill tracking register (submitted, reviewed, certified, paid)
• Compile a checklist of supporting documents required with each bill
• Review past disputed bills and look for the pattern — there usually is one

Week 4: Move to digital tracking#

• Digitize measurement records (mobile entry replacing the paper MB)
• Link measurements to BOQ items for automatic quantity summaries
• Set up deduction calculations (retention, TDS, advance recovery)
• Create a billing calendar with reminders for submission dates

Reconcile five balances before the next RA bill#

An RA bill can be arithmetically perfect and still breed a dispute six months later. Reconcile these five balances at every cut-off.

1. Quantity balance#

For each BOQ and approved extra item, show previous cumulative quantity, current-period quantity and current cumulative quantity. Tie the cumulative figure to its measurement-book reference and the latest approved drawing or field instruction. Rejected or deferred quantities stay outside the certified total, each with a reason and an owner.

2. Value balance#

Multiply only certified quantities by the applicable contract rate or approved derived rate. Show price adjustment, part rate and tax as separate lines — never buried in a revised unit rate. A reviewer should be able to walk from any measured line to its value line without a manual lookup.

3. Withholding and recovery balance#

Keep a roll-forward for retention or security, mobilisation advance, secured advance, free-issue material recovery, statutory deductions and any other contractual recovery. Every line needs an opening balance, the current deduction or release, the closing balance and the release condition. Never merge a disputed recovery with an accepted deduction just to make the net payable reconcile.

4. Invoice and tax balance#

Reconcile certified base value, applicable tax, TDS, credit notes and the tax invoice accounts actually used. For credits or payments on or after 1 April 2026, the Income Tax Department's TDS transition FAQ says the Income-tax Act, 2025 provisions apply and old section numbers should not be used in the return. Take tax advice for the exact payer, payee, threshold and transaction.

5. Payment and ageing balance#

Match the certified payable amount with the bank value date and remittance details. Keep unpaid certified value, uncertified claims and disputed claims in separate ageing buckets. That separation is what tells management whether cash is stuck on documentation, technical certification, a commercial disagreement or plain payment processing.

Close the billing period only when all five roll-forwards agree. Preserve the signed or digitally approved snapshot used for submission, so later corrections cannot rewrite the historical claim. And record every reopening with its reason, approver and financial effect before it is approved.

2026 update: treat running account bills in Indian construction as a controlled process#

The biggest improvement since this article was first published is not a new dashboard. It is a clearer standard for evidence. A reliable running account bills in Indian construction process must show what was expected, what actually happened, who verified it, what exception arose and how it was closed. If your team cannot reconstruct that chain later, the record is incomplete — however green the status looks on screen.

Billing procedure is not static. CPWD's Works Manual 2024 circular register includes later amendments dealing with bills and other works procedures, so public-works teams should verify the current manual, GCC, SOP and project circulars instead of quoting a historical clause from memory. Private contracts need the same discipline: the signed agreement and its amendments remain the authority.

Payment timing has a second dimension when an eligible micro or small enterprise supplies goods or services. The Ministry of MSME's delayed-payment guidance explains that an agreed payment period cannot exceed 45 days from acceptance or deemed acceptance, and describes the statutory interest mechanism. Eligibility and the date of acceptance need evidence — a vendor name alone proves nothing.

The billing control chain runs: measurement, joint verification where required, applicable item and rate, calculation, recoveries, tax document, certification, payment, retention release. If any stage uses a different quantity or revision, the reconciliation should be visible — not hidden inside the net payable amount.

A field-ready workflow for running account bills in Indian construction#

Use one workflow from the first site event to final review:

Ownership sits with the billing engineer, backed by authorised contract certification. Configure a substitute and an escalation route before leave, shift change or package handover forces the issue — shared passwords and retrospective signatures destroy accountability.

Data design before software configuration#

Design the record before you pick the screens:

• Identity: unique number, project, zone, floor or chainage, package and responsible contractor
• Basis: drawing, specification, contract clause, rule, method statement or approved request — with revision
• Event: date and time, creator, quantity or status, source document and contemporaneous evidence
• Decision: reviewer, approval state, comment, due date and reason for rejection or change
• Closure: action taken, final evidence, verifier and closure time
• Audit: revision history, exported attachments, permission changes and any manual correction

Use controlled pick-lists for project, location, contractor, item and activity, but keep a comment field for genuine exceptions. Do not let free-text spelling create five identities for the same floor, vendor or material. Equally, do not force a wrong list value just to submit the form — route master-data corrections to a named owner.

Metrics that reveal process health#

Track a small, balanced set: completion on time, median approval cycle, missing-evidence rate, aged exceptions, reopen or reversal rate, and certification cycle time with quantity differences. Compare rates on a fair denominator — inspections performed, worker-hours, equipment-hours, quantity installed or purchase value. Raw counts reward busy projects and let a weak smaller site hide.

The critical red flag on this topic: rolling forward a disputed quantity without showing its status separately. Add a monthly sample audit comparing the digital record with the site condition and the original evidence. If the dashboard and the sample disagree, fix the process and master data before adding more automation.

A 30-day implementation plan#

Week 1: define and sample#

Pick one project and one work package. Map the current process, identify the authoritative documents, agree the minimum fields, and collect ten recent examples — including two failures or disputes. The failures teach you more.

Week 2: configure and rehearse#

Configure roles, statuses, required evidence, due dates and escalation. Run the workflow on real historical examples, then simulate a rejection, an offline capture, a changed requirement, an incorrect entry and a reassignment.

Week 3: controlled live pilot#

Run the new process on one shift or package, keeping a named fallback. Review incomplete and returned records daily. Do not expand until field users can complete the record without a coordinator repairing it afterward.

Week 4: reconcile and decide#

Compare the system against physical conditions and source documents. Measure cycle time, exceptions and user corrections. Approve the next rollout only after owners have accepted the data-quality gaps and corrective actions.

Connect the record to adjacent workflows#

Do not run this as an isolated register. Connect your construction billing workflow with the measurement book guide so the originating need and its approval stay visible. Then link the joint measurement sheet guide to the retention money guide so field evidence and the latest controlled information agree.

Governance gets easier when your billing templates use the same project, location and responsibility codes as your expense records. Use the project-controls workflow for the rollout aids, but give every downloaded format an owner and a revision — an uncontrolled template quickly becomes one more conflicting record.

This connected design prevents a familiar failure: one module says an item is complete while the evidence, commercial record or downstream action says otherwise. The same identifiers should survive from request through verification to closure.

Questions for the monthly control review#

A useful monthly review is short enough to actually run and specific enough to change behaviour. Ask these against a sample of live records, not only a dashboard:

1. Can the team trace a certified measurement-to-payment record from the originating event through approval and closure?
2. Does the sampled record contain measurement reference, item, quantity, rate, recovery, tax, retention and payment?
3. Can the owner — the billing engineer with authorised contract certification — explain every manual correction and late approval in the sample?
4. Are the current drawing, specification, rate, rule or method references visible at the point of work?
5. Which location, subcontractor, material or work package contributes most to certification cycle time and quantity differences?
6. Were high-risk exceptions escalated before work, payment or handover proceeded?
7. Do physical conditions and source documents agree with the system status?
8. Are permissions limited to people who need to view, edit, approve or export the record?
9. Has superseded or duplicate information been withdrawn from field use?
10. Did last month's corrective action reduce recurrence, or merely close old entries?

Record the sample size, exceptions and actions from this review. For running account bills in Indian construction, the most dangerous assurance is a clean summary built on untested source records — and the failure mode to challenge first is a disputed quantity rolled forward without its status shown separately.

Run a worked verification drill#

Before wider rollout, pick three records: one normal, one corrected, one disputed or rejected. Hand them to a reviewer who did not create them and ask for the status — using only the retained evidence. The reviewer should be able to identify the governing requirement, follow every approval and correction, recalculate the important quantity or value, and explain why closure was accepted.

Write down every question that needed a phone call or someone's memory. Each one marks a missing field, attachment or responsibility rule. Fix the record design and repeat the drill — adding a dashboard before this test passes only makes an unreliable answer easier to display.

Repeat after a month, with a different reviewer and a record from another work front. Consistent results across people and locations are far stronger evidence of a controlled process than one polished demonstration prepared by the implementation team.

FAQs#

What is the minimum record needed for running account bills in Indian construction?#

Start with a certified measurement-to-payment record. It should identify the project and location, state what happened, preserve measurement reference, item, quantity, rate, recovery, tax, retention and payment, and show who created, checked and approved it. Add fields only when they support a decision, a compliance duty or a recurring analysis.

Who should own running account bills in Indian construction on a construction project?#

The billing engineer, with authorised contract certification behind them. The system administrator can configure permissions and reports, but cannot substitute for the person accountable for verifying site conditions and commercial facts.

Can Excel or WhatsApp be used for this process?#

For a small pilot, yes — provided there is one controlled version, named owners, protected approvals and a dependable archive. They turn risky the moment records are copied across groups, corrections overwrite history, or nobody can prove which version governed the work.

Which KPI should the team review first?#

Certification cycle time, alongside quantity differences. Review it by project, location and responsible package, and always inspect the source records behind an unusual result. A KPI is a signal for investigation, not proof of good or bad performance on its own.

How long should these construction records be retained?#

Use the longest applicable period across law, state rules, contract, warranty or defect-liability obligations, tax requirements and your organisation's approved retention schedule. Keep the record readable with its attachments and approvals — a database row whose evidence links have expired is not meaningful retention.

Does software make the process legally compliant?#

No. Software makes records timely, searchable and harder to alter silently, but compliance depends on the applicable rule, the correct procedure, competent people and truthful evidence. Take project-specific legal, tax, labour or engineering advice wherever the interpretation affects rights or safety.