3. Audit vs Review vs Compilation — Key Differences
Understanding Key Terms
Businesses often use the terms audit, review, and compilation interchangeably. However, in law and professional practice, these represent:
Audit: Provides the highest level of assurance
Review: Offers moderate assurance
Compilation: Involves no assurance
Each engagement carries a different level of responsibility and consequence.
This article explains how audit, review, and compilation differ, when each applies, and why choosing the wrong engagement can create serious compliance and credibility risks.
1. Introduction — Why This Distinction Matters
Financial statements may be:
Audited
Reviewed
Compiled
Each carries a different degree of reliability for users such as:
Banks
Investors
Regulators
Business partners
Misunderstanding these differences often leads to false confidence or regulatory non-compliance.
Impact: Treating a review or compilation as an audit is a common and costly mistake.
2. Objective of Each Engagement
The objective differs significantly across engagements:
Audit: To express an opinion on whether financial statements give a true and fair view
Review: To provide limited assurance that nothing has come to the practitioner’s attention indicating material misstatement
Compilation: To assist management in preparing financial statements without providing any assurance
Understanding the objective clarifies the level of reliance users can place on the financial statements.
3. Audit — Nature and Assurance Level
Nature of Engagement
An audit is a statutory or voluntary assurance engagement conducted in accordance with auditing standards.
Level of Assurance
Reasonable assurance
Highest level of confidence short of absolute certainty
Key Characteristics
Risk-based planning
Testing of transactions and balances
Evaluation of internal controls
Independent audit opinion
Typical Use Cases
Statutory audit under Companies Act
Lender or investor requirements
Regulatory filings
4. Review — Nature and Assurance Level
Nature of Engagement
A review is a limited assurance engagement, usually governed by review standards.
Level of Assurance
Limited assurance
Negative assurance (nothing has come to attention)
Key Characteristics
Primarily analytical procedures
Inquiry-based
No detailed testing of transactions
Typical Use Cases
Interim financials
Smaller entities where audit is not mandatory
Comfort to limited stakeholders
Impact: A review does not provide the confidence level of an audit.
5. Compilation — Nature and Assurance Level
Nature of Engagement
A compilation is a non-assurance engagement.
Level of Assurance
No assurance at all
Key Characteristics
Financial statements prepared based on management information
No verification or testing
No opinion or conclusion
Typical Use Cases
Internal management reporting
Basic financial statement preparation
Compliance where assurance is not required
6. Comparison — Audit vs Review vs Compilation (Conceptual)
Audit involves:
Verification
Professional judgement
Independent opinion
Review involves:
Inquiry and analytics
Limited conclusion
Compilation involves:
Presentation only
No verification
The responsibility shifts progressively from auditor-led assurance to management responsibility.
7. Legal & Compliance Perspective
Statutory audit is mandated by law for companies
Review or compilation cannot substitute a statutory audit
Submitting reviewed or compiled statements where audit is required leads to non-compliance
Wrong engagement selection can invalidate filings and attract penalties.
8. Common Misconceptions in Practice
“Reviewed statements are almost audited”
“Compilation means CA has verified numbers”
“Bank won’t notice the difference”
In reality, users are increasingly alert to the type of engagement performed.
9. Practical Guidance for Management
Before finalising financial statements, management should clarify:
What engagement is legally required?
What assurance do stakeholders expect?
What level of risk can the business accept?
Choosing the right engagement avoids future disputes.
10. CABTA Insight
“The difference between audit, review, and compilation is not terminology—it is trust.”