Reading a variation register before you trust the cost report
What project cost auditors look for first in a variation register — sequence gaps, late entries, and amounts already paid.
A tidy cost report can still hide a messy variation register. Before sampling invoices, we sort the register by approval date and by the date the amount entered the forecast.
Sequence and status
Gaps in variation numbers are not automatically fraud — they often mean cancelled drafts. What matters is whether paid amounts appear against lines still marked “pending approval.” That mismatch is one of the fastest routes to an exception.
Timing relative to certificates
Variations that arrive in the register after the related payment certificate has already been certified deserve a second look. Sometimes commercial agreement truly lagged paperwork; sometimes the cost was absorbed quietly into another code.
What we ask clients to prepare
Export the register with columns for description, value, approval status, linked contract clause, and the certificate or journal that booked the cost. PDF screenshots alone slow the audit and increase clarification rounds.
If your team is preparing for a project cost audit, cleaning the register two weeks early usually shortens fieldwork more than any other single step.