Find the errors before a decision depends on them.
Independent technical assessment of existing financial models with a defined review scope, documented tests, exceptions and limitations.
Confidence should come from testing, not presentation.
A beautiful dashboard tells you little about whether underlying assumptions, formulas and references produce the stated result.
I perform independent technical verification of selected model outputs, tracing numbers back to source assumptions and documenting exceptions where the agreed criteria are not met.
Typical testing procedures
- Input and assumption consistency
- Formula errors and broken links
- Forecast, discount-rate and valuation mechanics
- Selected KPI definitions and arithmetic
- Financial-statement linkages and cash-flow integrity
- Scenario, sensitivity and selected probability models
- Cross-case references and calculation trails
- Exception documentation and decision impact
What happens during the review?
The process is structured so readers can distinguish tested facts from unverified assumptions.
Define the evidence
Agree model version, source files, intended readers, sample strategy, review criteria and reporting limitations.
Independently recalculate
Select tests using risk and materiality, reproduce calculations, reconcile selected outputs and investigate discrepancies.
Explain the findings
Record tested items, procedures carried out, confirmed exceptions, limitations and the work's overall technical conclusions.
Clear deliverables with clear boundaries.
A technical verification report can be useful to management and prospective stakeholders, but it cannot substitute for a statutory audit or a report issued by an authorised assurance practitioner.
Typical deliverables
- A concise technical verification report
- Description of scope and work performed
- Risk-based sampling and recalculation summary
- Discrepancy and exception schedule, if applicable
- Scope limitations and items not tested
- Findings confined to the work actually undertaken
Any intended external reliance, assurance status or professional sign-off requirements must be agreed separately before work begins.
Need an independent second view?
Share the model version, areas of concern and intended use so the verification scope can be agreed.