Where billing leaks
Every one of these was completed. Every one still slipped.
Capture the work, match it to scope, substantiate the bill — three jobs, held together by someone doing it by hand.
Capturing work done
Six updates in ten minutes. One never reached the record.
End of shift, the site group lights up: a pour, a delivery, two hindrances, a labour count, and "kerb laying done, 12+400 to 12+650". The evening DPR picks up five.
The kerb laying never reaches the progress record, so there's nothing to bill. The work was done; the bill never saw it.
Matching to project scope
Delineators installed at Ch. 18+100–18+400. Never billed.
"Delineators fixed, 18+100 to 18+400, both sides" — one line in the site group, between a pour update and a delivery. The BOQ has an item for it; nobody tied the message to it.
Working through hundreds of updates at month-end, the billing engineer missed it — along with the other small items that only ever appeared in chat.
Substantiating the bill
9 lines short of proof. Retention goes from 5% to 20%.
The quantities reconcile against scope. But every line needs its supporting documents behind it: a signed checklist, a level survey, a lab result. On 9 lines, one is missing.
Without them, the client holds 20% retention instead of 5% — an extra 15% of the bill's value, until the documents arrive.
Reconciling small jobs
Hundreds of patch repairs. One BOQ item.
Every pothole filled is reported as a photo captioned with chainage, length and width — often with no unit, often in a burst of photos of the same patch. At month-end, someone collates hundreds of them into one quantity.
Miss a patch and it's never billed. Count a burst twice and the engineer starts checking every line. And every patch needs its photo before the bill is certified.
The Fix
Work done captured, matched to project scope and substantiated — before the bill goes out, for your team to review and finalise.
One photo. Buried by the next billing cycle.
Filed, matched and flagged for your review.
How it works
One WhatsApp QR Scan. Zero Change for Your Teams.
Add Velora to your existing WhatsApp groups. Your teams keep working as they do, whether there's one record to chase or a hundred.
Captures work done as your teams report it
Quantities, photos, checklists, level surveys and lab results are captured from your site, QC and billing groups as they're posted. Work nobody planned to bill this month goes to your billing engineer to confirm.
Matched to project scope
Each update is matched to its BOQ item or billing break-up line, executed quantity against scoped. Anything unclear is held for your billing engineer, not guessed. Velora tracks quantities; your team adds rates.
Checked for what each bill line still needs
Matched work becomes suggested bill lines, each checked for the supporting documents it needs, such as quality checklists, level surveys, lab results and site photos: received or still missing.
Ready for this month's bill, not next month's
Missing documents are followed up on WhatsApp with whoever holds them. Your billing team reviews the lines and finalises the bill.
Data Sources
Involved Parties
Velora AI
What You Get
What Velora Delivers
Billing intelligence — without changing how bills get compiled.
Work Capture
Work done picked up from site updates, by work front, including work nobody planned to bill.
Quantities, progress and photos come from the WhatsApp updates your site teams already send. Unplanned work goes to your billing engineer to confirm, so its supporting documents are gathered from the start instead of it being left out.
Scope Matching
Work done matched to each scope line, from a BOQ, work order or EPC billing break-up, feeding the suggested bill lines.
Reported quantities are tracked against the scoped quantity. Updates without one are still matched by activity, with work front, date and photos. Anything unclear is held for your billing engineer. Import scope from your BOQ, break-up, work order or contract; Velora tracks quantities, your team adds rates.
Bill Substantiation
The supporting documents your client asks for, gathered against each bill line: quality checklists, level surveys, lab results, site photos and whatever else your contract needs.
Quality checklists, RFIs, level surveys, lab results and site photos shared on site are filed against the work they cover, and missing ones are followed up on WhatsApp with whoever holds them. Documents kept off WhatsApp, such as the measurement book, are uploaded once for the bill. Your billing engineer reviews each line and finalises it.
The impact
The operational shifts that happen from the first bill.
Work done captured. Matched to project scope before the bill goes out. Every line substantiated. These are the shifts billing teams notice first.
What changes when nothing has to be reconstructed, chased, or rediscovered later.
Work done billed this month, not next
Work done captured and matched to project scope, ready to review
Field-reported quantities are matched to their scope item directly. Where no quantity was given, the progress record — work front, date, photos — is still matched by activity, so review starts from what was actually reported, not a guess.
Supporting documents, chased for you
Missing documents followed up on WhatsApp until they're in
Velora messages whoever holds the outstanding checklist, level survey or lab result directly on WhatsApp, and follows up until it’s received. Less end-of-cycle scramble.
Bills certified faster
Suggested bill line items with supporting documents attached
Executed quantities matched to scope sit with their quality checklists, level surveys, lab results and site photos, filed under the bill line each belongs to. Your billing team reviews and finalises, instead of reconstructing it at month-end.
A record you can defend: every update traces back to the WhatsApp message and site photo it came from.
See it assist your next bill claim.
Talk to us about your billing process and we'll set up a pilot against your live sites and existing WhatsApp groups.
Frequently Asked Questions
Common questions from billing and cost heads, billing engineers and project managers evaluating Velora.
No. Your teams keep using WhatsApp exactly as they do today. Velora reads the same groups you already use — progress updates, checklist sign-offs, lab results — and files each update against the scope item it likely belongs to, for your billing engineer to confirm. No new app, no forms.
Messages are matched against your project scope (imported from your BOQ, billing break-up, work order or contract) using the work front, activity, and context in the message — the same way a billing engineer would read it manually. Velora raises what it detects, and the billing engineer makes the final call — never a silent guess.
No. Velora works on scope versus executed, not on rates, and every contract has scoped quantities. On an item-rate contract they're in the BOQ. On an EPC or lump-sum contract, the price is often broken into line items with quantities (a billing break-up) that each monthly bill is raised against. Either way, work done has to be matched to those lines to raise the monthly bill. Import scope from whichever document holds it.
Yes, where repairs and jobs are paid against BOQ or work order items. On a highway maintenance contract, for example, each pothole or patch repair reported in the group with its chainage and size is recorded against its location, its area worked out for your billing engineer to confirm, matched to the repair item and kept with its photos, so the month's quantity for that item builds up as the work is reported, with the proof behind every patch. On an HVAC, electrical or plumbing rate contract, each repair is billed against its rate item and attendance alone rarely substantiates it: the job photos and signed checklists your technicians share from each site are filed against the line they belong to, so the bill carries proof of the work.
Guide: how to reconcile and substantiate a road maintenance bill →
No. Velora tracks quantities, not rates: what's scoped for each line, what's been executed on site, and what's still to be claimed. Your billing engineer keys rates into the bill as they do today.
Right now, Velora follows up with QC or the PM on WhatsApp for any checklist, level survey or lab result still outstanding, and they coordinate with the subcontractor from there.
Bill line items, built from work done matched to each scope line (BOQ item or billing break-up line), with supporting documents. Your team keys in rates, adds anything missing and finalises the bill, whether that's an RA bill, an interim payment application or a progress claim.
Whatever your client needs to certify the bill, such as quality checklists, level surveys, lab results, site photos and the measurement book. Documents shared on site are filed against the line they belong to, each traced back to the WhatsApp message it came from; documents like the measurement book are uploaded once per bill by your billing engineer.
The list is set for each project, so a contract that needs less, or something extra such as labour compliance records, gets exactly that. Your billing engineer reviews what each line carries before the bill goes out.
Every site update is matched to a scope line. Work reported on site that nobody planned to bill this month is flagged to your billing engineer to confirm. Nothing is added without confirmation.
No. It's a partnership: AI suggests bill line items and gathers the supporting documents; your billing team reviews, adds anything missing and finalises the bill.
Both, and your own EPC billing cycle too — the contract format doesn't change how quantities are checked or evidence is filed.
We run a discounted pilot for the first three months — full product, no long-term commitment. See what it surfaces on your own sites before committing to a subscription.
Yes. Data is stored securely with role based access control, and privacy data is encrypted at rest using AES-256 standard.
What we keep hearing
The more bills you compile, the easier something slips.
Payment held until every checklist is in.
A 210-day working capital cycle.
Quantities missed. Bills come up short.
100 projects. Every document collated by hand.