How the SSARSs are organized and what AR-C 60 requires on every engagement

The structure of the AR-C sections, the SSARSs now in force, and the AR-C 60 rules on ethics, acceptance and preconditions that apply to every engagement.

5 min read · CORAA Team
Lesson 1 of 13 · 0 of 13 complete
In this lesson you will
  • Identify the AR-C sections and which engagement each one governs
  • Distinguish unconditional and presumptively mandatory requirements under AR-C 60
  • Apply the AR-C 60 acceptance conditions and preconditions before signing an engagement
  • Determine which SSARS amendments apply to a given reporting period

Where the SSARSs sit

Statements on Standards for Accounting and Review Services (SSARSs) are issued by the AICPA Accounting and Review Services Committee (ARSC), the senior committee designated to issue pronouncements on preparation, compilation and review engagements for nonissuers. Council has designated ARSC under the Compliance With Standards Rule (ET sec. 1.310.001), so a member who performs a preparation, compilation or review engagement and departs from the SSARSs has a Code problem, not just a quality problem.

SSARS No. 21 (October 2014) clarified and recodified the standards into AR-C 60, 70, 80 and 90. Later statements added AR-C 100 and AR-C 120:

Section Covers
AR-C 60 General principles for every SSARS engagement
AR-C 70 Preparation of financial statements
AR-C 80 Compilation engagements
AR-C 90 Review of financial statements
AR-C 100 International reporting issues
AR-C 120 Compilation of pro forma financial information

Later standards amend those sections rather than adding new ones. SSARS No. 25 (issued February 2020) added explicit materiality and adverse conclusions to reviews, effective for periods ending on or after December 15, 2021. SSARS No. 26 (June 2022) aligned the AR-C sections with the quality management standards, effective for engagements for periods ending on or after December 15, 2025. SSARS No. 27 (2025) clarified when AR-C 70 applies to financial statements prepared in a consulting engagement, effective for periods ending on or after December 15, 2026. SSARS No. 26 renumbered paragraphs in AR-C 60 (the acceptance paragraph moved from .25 to .30 and the preconditions from .26 to .31), and the earlier text still governs earlier periods, so check the period before you cite a paragraph number. The SSARS update guide walks through each change.

The language of requirements

AR-C 60 uses two categories. "Must" is an unconditional requirement. "Should" is presumptively mandatory: you comply unless, in rare circumstances, the specific procedure would be ineffective, and then AR-C 60 requires alternative procedures that achieve the intent. You must document the justification for the departure and how the alternative procedures were sufficient. AR-C 60 bars you from stating in a compilation or review report that you complied with SSARSs unless you complied with AR-C 60 and every other relevant AR-C section.

AR-C 60 says you must perform a review, compilation or preparation engagement in accordance with SSARSs. The one carve-out is a review of interim financial information that meets the AR-C 90 conditions; that review follows AU-C 930 instead.

Acceptance and preconditions

Under the current text, AR-C 60.30 bars acceptance when you have reason to believe relevant ethical requirements (including independence, where it applies) will not be met, when the information you need is likely to be unavailable or unreliable, or when you doubt management's integrity enough that it is likely to affect the engagement.

AR-C 60.31 then sets the preconditions. You determine that the financial reporting framework management selected is acceptable, and you obtain management's agreement that it acknowledges and understands its responsibility for:

  • selecting the framework
  • internal control over preparation and fair presentation, unless you accept responsibility for that control
  • preventing and detecting fraud
  • compliance with laws and regulations
  • the accuracy and completeness of records, documents and explanations, including significant judgments
  • giving you access to information, additional information you request, and unrestricted access to people you need to question

AR-C 70, 80 and 90 each cross-reference these preconditions and add their own. If management will not agree, you do not accept the engagement.

File mistakes peer reviewers flag

  • Engagement letters missing one of the management responsibilities listed above.
  • Reports that claim SSARS compliance when a required procedure was skipped and no departure was documented.
  • Citing paragraph numbers from the wrong version of a section for the period under report.
  • No evidence that the engagement partner considered acceptance and continuance under the firm's policies.

The peer review findings guide lists the recurring deficiencies in SSARS engagements.

Worked example

Which text applies: Cedar Row Landscaping, LLC

Cedar Row Landscaping, LLC has a fiscal year ending June 30. Your firm is engaged to review its financial statements for the year ended June 30, 2026, and its year ended June 30, 2027.

Step 1, SSARS No. 25: effective for periods ending on or after December 15, 2021. Both years end after that date, so the materiality requirement and the adverse conclusion apply to both.

Step 2, SSARS No. 26: effective for periods ending on or after December 15, 2025. The fiscal 2026 period ends June 30, 2026, which is after December 15, 2025, so the 2026 review follows the amended AR-C 60 and AR-C 90, including the engagement partner responsibilities in AR-C 60.21 through 60.29. A review of the year ended June 30, 2025 would have followed the pre-SSARS 26 text.

Step 3, SSARS No. 27: it amends AR-C 70 only and does not change the review.

Conclusion: both files cite the current text. A prior-year file for the year ended June 30, 2025 cites the pre-SSARS 26 paragraph numbers, so your engagement letter template and checklist need a version for each.

Self-check

Answer each question before you open the answer.

  1. What is the difference between "must" and "should" in the SSARSs?

    Show answer

    "Must" is an unconditional requirement that applies in every case where it is relevant. "Should" is presumptively mandatory: you comply unless, in rare circumstances, the procedure would be ineffective, and then you perform alternative procedures and document the justification under AR-C 60.

  2. A calendar-year client asks for a review of its December 31, 2025 financial statements. Does SSARS No. 26 apply?

    Show answer

    Yes. SSARS No. 26 is effective for periods ending on or after December 15, 2025, and the period ends December 31, 2025. The amended AR-C 60 and AR-C 90 apply to that review.

  3. Management refuses to acknowledge responsibility for preventing and detecting fraud. What do you do?

    Show answer

    Do not accept the engagement. Management acknowledgment of fraud responsibility is one of the AR-C 60 preconditions, and the AR-C 70, 80 and 90 acceptance paragraphs require you to decline when the preconditions cannot be satisfied.

  4. When can you state in a review report that you performed the engagement in accordance with SSARSs?

    Show answer

    Only when you complied with AR-C 60 and every other AR-C section relevant to the engagement. A skipped procedure with no documented, justified departure means the compliance statement is false.

Sources

Back to the syllabus

Standards are paraphrased from the primary sources listed above; read the source before relying on a requirement. This lesson is training material, not professional advice. Report an error

For US CPA firms

Join the CORAA waitlist

CORAA AI drafts audit working papers from your client’s QuickBooks books and does the first pass: lead schedules, tie-out, memos, draft notes and letters. CORAA Network reviewers clear every finding. Your firm reviews and signs.

  • First audit free, so you can judge the quality on a real file
  • Flat fee by entity size; messy books included
  • We work only with CPA firms, never their clients
See how it works →

* required