Skip to content
Request Demo

Audit Evidence Model Review

Product Guide • Beginner • 2 min read

Audience
Advisory Firms • Boards • CFOs
Last Reviewed
July 2026
Updated
Version 1.0

Executive Summary

The Audit Evidence Model Review packages the same deterministic structural review used elsewhere in the suite as evidence formatted for inclusion in a statutory audit file. It supports auditors testing management's models behind estimates, impairments, and going-concern assessments, expressing coverage as scope-limitation language and provenance as a reperformance statement an audit reviewer can rely on. It is delivered to the auditor's specification, never as an audit opinion in its own right, and never as an assessment of the estimates or judgments the auditor is responsible for testing.

Key Takeaways

  • The Audit Evidence Model Review renders the same underlying structural pipeline in audit language, with procedures, exceptions, and scope limitations rather than a general structural report format.
  • It is delivered to audit firms as a specialist input into their own audit file, never as the audit opinion itself.
  • Findings are expressed against a firm-specific exception taxonomy, configured and versioned per audit firm.
  • Provenance is expressed as a reperformance statement, meaning an audit reviewer can reproduce the underlying run byte for byte, a claim a manual review memo cannot make.
  • It explicitly excludes any assessment of accounting estimates, judgments, or treatment, which remain the auditor's own responsibility throughout.

Purpose

The Audit Evidence Model Review packages the structural review as audit evidence: work-paper-grade output supporting statutory auditors' testing of management's models behind estimates, impairments, and going-concern assessments. It renders the same deterministic structural facts produced elsewhere in the suite in the language and format an audit file requires, without ever taking on the role of the auditor itself.

Who It Is For

The customer base is audit firms, with second-tier firms as the primary near-term market, applied to the models of their own audit clients. The buyer is the engagement partner's specialist testing budget, an existing and recurring line within statutory audit fees, procured through firm panel processes.

Problems Solved

  • Statutory auditors testing a management model behind an estimate or impairment often rely on internal specialist teams or manually written review memos, at higher cost and with no independent reproducibility.
  • Audit files need evidence that a reviewer can reperform byte for byte, which a manually authored memo cannot offer.
  • Findings need to be expressed in the audit's own language, procedures, exceptions, and scope limitations, rather than a generic structural report format.
  • Auditors need a specialist they can rely on for the structural layer of their testing, without that specialist becoming, or appearing to become, the source of the audit opinion itself.

Workflow

The same structural pipeline used across the wider product suite is run against the management model under audit, and the resulting facts are rendered through an audit-language template. Each executed rule family is mapped to procedure language reviewed and agreed with the audit firm's own methodology team, and findings are expressed against that firm's own exception taxonomy, configured and versioned per firm. Coverage is expressed as scope-limitation language auditors recognise, and provenance is expressed as a reperformance statement confirming the underlying run can be reproduced exactly. The deliverable is issued for inclusion inside the audit firm's own engagement file, never as an audit opinion in its own right.

Outputs

The deliverable is the AEV report: an engagement cover carrying an independence statement, a procedures-performed table mapping each executed structural check to reviewed procedure language, an exceptions register presented in audit voice against the firm's agreed severity taxonomy, a scope and limitations section drawn from the engine's coverage output, a reperformance statement grounded in the engine's determinism, and a work-paper reference index formatted to the firm's own conventions.

Continue Reading

How OXXON tests thisRun a free structural check with FMAE

Frequently Asked Questions

What is the Audit Evidence Model Review?

A product that packages Oxxon's deterministic structural review as work-paper-grade evidence, supporting statutory auditors testing management's models behind estimates, impairments, and going-concern assessments.

Who buys the Audit Evidence Model Review?

Audit firms, particularly second-tier firms, purchasing it within an engagement partner's specialist testing budget for a specific statutory audit.

Does the Audit Evidence Model Review give an audit opinion?

No. It is a specialist input the auditor uses in their own file; Oxxon is never the opinion-giver, and the deliverable makes no claim to audit-standard compliance beyond language reviewed and approved by counsel and the firm's own methodology team.

Does it assess whether management's accounting estimates are reasonable?

No. Assessing estimates, judgments, and accounting treatment is the auditor's own responsibility and is explicitly and doubly excluded from this product's scope.

What does the deliverable actually contain?

An engagement cover with an independence statement, a procedures-performed table mapping executed structural checks to procedure language, an exceptions register in audit voice, scope and limitations drawn from coverage, a reperformance statement, and a work-paper reference index in the firm's own format.

What is a reperformance statement?

A statement, grounded in the engine's determinism, that an audit reviewer can reproduce the underlying structural run byte for byte, a claim a manual specialist review memo is not able to make.

How is this different from the standard Independent Structural Model Review?

It runs the same underlying structural pipeline, but renders the output in audit-specific language, procedures mapping, and a firm's own exception taxonomy, formatted for direct inclusion in a statutory audit file.

How long does it take to bring a new audit firm onto this product?

Adoption runs on a longer methodology-adoption cycle than most other products in the suite, since the firm's own methodology team typically reviews and accepts the work-paper format before volume delivery begins.

Related Articles

What Is a Financial Model Audit?

A financial model audit is an independent, structured examination of an Excel based financial model to confirm that its mechanics, logic, and outputs are reliable enough to support a decision. It is not a check of whether the assumptions are optimistic or conservative. It is a check of whether the model actually calculates what its author believes it calculates. Every year, lenders extend debt, investment committees approve capital, and boards sign off on transactions using numbers that came out of a spreadsheet nobody outside the immediate deal team has independently verified. A financial model audit exists to close that gap before it becomes expensive.

Audit vs Validation — What's the Difference?

Financial model audit and model validation are frequently used as interchangeable terms, and specifying the wrong one in a lender requirement or an internal policy leads to real confusion about what has actually been checked. They test different things. An audit tests whether a model's mechanics are correct. Validation tests whether the model's methodology and assumptions are appropriate for its intended purpose. Both are legitimate, useful exercises. They are not substitutes for each other.

What Is Model Risk?

Model risk is the risk that a decision is wrong not because the underlying business or investment case was flawed, but because the model used to evaluate it was. It is a distinct category of risk from market risk, credit risk, or operational risk, and it applies to any organisation that relies on a financial model, spreadsheet or otherwise, to support a material decision. Most published model risk content addresses statistical and regulatory capital models used inside banks. This page defines model risk specifically as it applies to Excel based financial models, the kind used every day for investment decisions, lending, and transaction evaluation, which is a related but distinct problem from the quantitative model risk literature most search results return.

Request Demo