Use case

RA bills and claims

General Inference reads your contract, BOQ, drawings, measurement records, site diaries and correspondence, and drafts the running-account bill or the claim: variations, extra items, extension of time, delay, demurrage or warranty. Each line points to the clause, drawing or letter behind it, and notice deadlines are tracked. Your contracts lead reviews and approves before anything is issued.

Talk to us about thisAll use cases

Who it is for

EPC and civil contractors

Roads, water, power and building contractors who raise RA bills every month and argue variations and time extensions with the client's engineer.

Subcontractors and package vendors

Electrical, piping, HVAC and structural firms who bill the main contractor against measurements and chase extra items and held-back retention.

Equipment and material suppliers

Valve, pump, cable and steel suppliers on project orders who claim for delayed dispatch clearance, idle stock, demurrage or warranty disputes.

How it is done today

The bill is built from scattered paper

Measurements sit in the MB and site registers, rates in the BOQ, approvals in letters and drawing revisions in someone's mail. The QS stitches them into an RA bill every month, by hand.

Notice periods slip by

A hindrance, a drawing issued late or an instruction to do extra work needs written notice within the contract's time. Site is busy, the letter goes late, and the right to claim is weakened or lost.

Claims are rejected for weak backing

The client's engineer sends a claim back because the clause is not cited, the hindrance register does not match, or the rate analysis for an extra item is missing. Money stays stuck for months.

What you get

  • A draft RA bill: measured quantities against BOQ items, cumulative and this-period amounts, deductions and the abstract
  • A deviation statement: quantities beyond the BOQ limit and extra items, each with the instruction or drawing behind it
  • An extension-of-time claim with a delay table built from the hindrance register, letters and drawing dates
  • A variation, demurrage or warranty claim letter in your format, every figure linked to its source page
  • A notice tracker: each event, the clause, the deadline and whether a notice went out
  • A list of gaps: missing measurements, unsigned instructions, rate analysis not on file

How it works

1. Share the contract and the site record

Upload or connect the contract, BOQ, drawings, measurement sheets, site diaries, hindrance register and correspondence, including scans.

2. It reads and checks the record

Quantities are matched to BOQ items, events to contract clauses, and dates to notice periods. Mismatches between the MB, drawings and letters are flagged.

3. It drafts the bill or the claim

The RA bill, deviation statement or claim is drafted in your format or the client's, with each line pointing to the page it came from.

4. Your contracts lead approves

Gaps and near deadlines are flagged first, and a person still reviews every line. The contracts lead approves, and your team issues it.

An example

Example: a civil contractor in Nagpur on a ₹180 crore water supply project prepares RA bill 14 and an extension-of-time claim after a 5-month pipeline delay.

BOQ items measured this period212 of 230, 18 with no measurement this month
Beyond BOQ quantity6 items, including DI pipe 600 mm at 118% of the BOQ quantity
Extra items3, one without a signed site instruction on file
Hindrances found11 in the register; 9 matched to letters, 2 with no notice on file
EOT claim drafted142 days, with the clause, a delay table and 38 linked letters
Deadline flaggedNotice for the latest road-cutting permission delay due in 4 days

Illustration with a made-up company, not customer data.

What it reads, and what you decide

It works from

  • The contract: general and special conditions, price variation clause, schedule of rates
  • BOQ, drawings and drawing revision lists
  • Measurement books and measurement sheets, past RA bills
  • Site diaries, hindrance registers and site instructions
  • Letters, emails and minutes with the client and the engineer
  • Dispatch, delivery and warranty records for supply orders

You still decide

  • Whether to raise a claim at all, and how much to ask for
  • The commercial position: what to concede and what to hold
  • The final RA bill figures and the rates for extra items
  • When and how the bill or claim is issued to the client

Worth knowing

Questions

Who approves the bill or the claim?

Your contracts lead, QS or project manager, as you set it. The workspace drafts and flags. A named person approves, and the activity trail records who prepared and who approved.

Does it send the bill or claim to the client?

No. Nothing is sent or uploaded by the system. Your team issues the approved bill or claim on your letterhead, by mail or on the client's portal, as you do today.

Does it replace our ERP or billing software?

No. It reads exports and reports from your ERP or billing tool alongside the contract and site files. Your existing system stays the record for accounts.

Can it work with CPWD, MoRTH, FIDIC or our client's own conditions?

Yes. It reads the conditions in your contract, whichever form they take, and tracks the notice periods and clauses written there. It does not assume one standard form.

What if a measurement or a letter is missing?

It says so. A missing measurement, unsigned instruction or late notice is flagged as a gap for your team to fix. It does not fill in a number it cannot find.

Related

Track the approvals

See who has to sign what, by when, and what is stuck, under your own approval rules. Reminders go to the person holding it up. Your people still decide.

Find it in the file

Ask a question of years of correspondence, drawings, contracts, specs and past bids. Every answer points to the page it came from. Owners confirm what sticks.

Brief me before the meeting

A one-page brief on a customer, tender or project before you walk into the meeting, drawn from your mail, orders and files, with the source for every line.

All use cases

Talk to us

Tell us about one job your team still does by hand.

Email us

Or write to anirudh@generalinference.co