Insights / Construction

How to automate CVR reporting without losing control of your margin

20 October 2026 · 6 min read · EYRA Advisory

The monthly cost value reconciliation is the report every commercial team depends on and almost nobody enjoys producing. At cut-off the QS pulls the ledger, chases late timesheets and unallocated invoices, lines up subbie applications against the client certificate, then rebuilds the forecast final cost in a workbook that only they fully understand. By the time the CVR reaches the board, the numbers are a fortnight old and any margin fade is already locked in.

That delay matters more in 2026 than it did a few years ago. Construction is still the sector with the most company insolvencies in England and Wales, at around 17% of all cases, and most of those firms had work booked. A CVR that lands late is a cash and margin risk, because it tells you about a problem after the window to recover it has closed.

This guide sets out which parts of the CVR can be automated safely, which parts should stay with the quantity surveyor, and the order to do it in.

Why CVRs still live in spreadsheets

Most main contractors still run the CVR in Excel, and there are good reasons for it. Every project has its own packages and quirks, the accounts system holds transactions rather than a margin view, and the QS needs room to apply judgement on accruals, provisions and over-measurement. A spreadsheet gives them that room.

The cost is that the workbook becomes the process. Data is re-keyed from the purchase ledger, the subcontract register and the valuation schedule every month, formulas drift as rows are inserted, and the logic lives in one person's head. When that person is on leave in the last week of the month, the CVR slips.

Buying a construction ERP or a CVR module can help, but software alone does not fix the most common cause of a bad CVR: invoices that were never coded to the right job and cost code. If accounts payable codes inconsistently, the QS spends cut-off week chasing miscodings instead of reading margin, whatever tool sits on top.

What to automate and what to keep with the QS

The split that works is simple. Automate the gathering, matching and checking. Keep the judgement with the surveyor who signs the report.

CVR step Automate? How it works in practice
Cumulative cost by job and cost code at cut-off Yes Scheduled export from the accounts system into a reporting model
Subcontract cost (cumulative assessed AfPs) Yes Pulled from the subcontract register, not from payments made
Gross certified value Yes Pulled from the valuation register for each interim certificate
Invoice coding to job and cost code Mostly Rules plus an AI suggestion, with a person approving the exceptions
Accruals for late timesheets, plant and materials Partly The system flags what is missing; the QS sets the accrual
Variations and compensation events No QS judgement, recorded in a register the report reads from
Forecast final cost and margin Partly The system rolls up cost to complete; the QS adjusts and signs off
Period movement commentary Draft only AI drafts from the movement table; the QS edits and approves

One principle sits under every row: the numbers come from formulas you can audit, and AI never produces a figure. It can read a movement table and draft a paragraph, or suggest which job an invoice belongs to, but the margin on the page should trace back to a ledger line or a certificate in a couple of clicks. That also lines up with the RICS professional standard on responsible use of AI, in force since March 2026, which keeps responsibility for AI-assisted work with a named surveyor.

A six-step route to an automated CVR

  1. Fix the coding before you build anything. Agree one cost code structure across jobs, make job and cost code mandatory on every purchase order, and give AP a short list of rules for the awkward cases such as plant, prelims and shared costs. Two months of clean coding is worth more than any dashboard.
  2. Set one cut-off calendar. Cost, value and accruals should all be taken at the same date every month. Decide whether you report against the client certificate or your internal valuation, write it down, and keep it consistent so the trend lines mean something.
  3. Build the reconciliation as a model, not a pasted workbook. Connect the ledger, subcontract register and valuation register into one data model, with period and cumulative columns calculated by formula. Next month's CVR then refreshes rather than being rebuilt.
  4. Turn the usual cut-off chasing into automatic flags. Costs without a purchase order, invoices sitting unallocated, variations not yet raised, value running ahead of certificate, and labour missing for the period are all things a system can list for the QS on day one of the close.
  5. Add a margin fade view. Track forecast final margin for every project month by month and highlight any job where it moves by more than a threshold you set. Fade becomes a conversation in month three instead of a surprise at final account.
  6. Let AI draft the commentary, then edit it. Once the movement table is reliable, a model can write the first pass of the period narrative, for example noting that a groundworks package moved £40k in cost against £15k in value and that a variation for the same work has not yet been raised. The QS corrects it, adds what only they know, and signs.

Mistakes that undo the benefit

The most expensive mistake is automating a broken process. If the coding is inconsistent, automation simply produces the wrong CVR faster. Map the current close first, from cut-off to board pack, and fix the steps where data enters the business.

The second is letting a tool decide the numbers. Accruals, provisions and the value of disputed variations are commercial judgements, and a board will rightly ask who made them. Keep that decision with the QS and keep a record of it.

The third is building something only one person can maintain. If the logic sits in a macro nobody else understands, you have swapped one key-person risk for another. Document the model and make sure the finance team can follow it.

Where EYRA fits

EYRA starts with a review of your CVR process, from cut-off to board pack. It shows where the days are lost and gives you a costed plan for automating the feeds and checks in the tools you already use. We then build the reporting model and the exception flags, with formulas your team can audit, and keep them accurate on a monthly retainer as projects and cost codes change. Your surveyors keep the judgement; the gathering and reconciling stops eating their month.

Frequently asked questions

What is CVR in construction?

A cost value reconciliation compares the value of work done on a contract with the cost incurred to deliver it, at project and package level, to show current and forecast margin.

How often should a CVR be produced?

Monthly is standard across UK construction, aligned to the interim valuation cycle so that certified value and cost are both current at cut-off.

Can AI produce a CVR?

AI can gather data, suggest invoice coding, flag exceptions and draft the commentary. The accruals, provisions, variation values and sign-off should stay with a named quantity surveyor.

Do we need new software to automate CVR reporting?

Not always. Many contractors can automate most of the gathering and checking by connecting their existing accounts system, subcontract register and valuation schedule to a reporting model.

What is the difference between a CVR and a WIP report?

The CVR shows margin by comparing cost with value. A WIP report shows work done that has not yet turned into cash, which matters for cash flow and revenue recognition.

Related reading

Sources

Book a review

Find out where your numbers are getting stuck.

Tell us a little about your firm and what's taking up your team's time. We'll reply within two working days to set up a 20-minute call. If we're not the right fit, we'll say so.