Attestation Reporting Under SSAE: How to Write and Interpret Examination, Review, and AUP Reports

Examination or review engagements

What an attestation engagement is (and why reporting is its “product”)

An attestation engagement is a service in which you (as the practitioner, typically a CPA) report on subject matter or an assertion about subject matter that is the responsibility of another party (usually management). The key idea is that users want confidence about something other than the basic historical financial statements—for example, compliance with a contract, the effectiveness of controls over a system, greenhouse gas emissions data, or a schedule of costs submitted to a regulator.

In the AUD exam, reporting matters because the report is how you communicate (1) the level of assurance you obtained and (2) what exactly you evaluated and under what criteria. Many questions test whether you can match:

  • the type of engagement (examination vs review),
  • the level of assurance (reasonable vs limited), and
  • the required report language and structure.

Attestation standards in the U.S. are issued under the SSAE framework (Statements on Standards for Attestation Engagements) and codified in AT-C sections.

The foundation: subject matter, responsible party, and suitable criteria

Before you can report, the engagement must be “reportable.” Conceptually, that requires three building blocks:

  1. Subject matter / assertion: What is being evaluated or measured (e.g., “Schedule of rental revenue,” “Entity complied with debt covenant,” “Controls were effective”). Sometimes management provides a written assertion; sometimes you report directly on the subject matter.
  2. Responsible party: The party responsible for the subject matter (often management). Your report is not “creating” the subject matter—you’re evaluating it.
  3. Suitable criteria: The yardstick used to measure or evaluate the subject matter (e.g., a contract, a regulation, COSO criteria for controls, an internal policy). Criteria must be objective enough that different practitioners would generally reach similar conclusions.

Reporting problems often trace back to criteria problems. If criteria are missing, vague, or not available to report users, your report may need to describe the criteria more fully, restrict use, or in some cases you may not be able to accept/complete the engagement.

Examination vs review: what they are and why the distinction matters

In attestation engagements:

  • An examination engagement provides reasonable assurance (high, but not absolute). Your report expresses a positive opinion/conclusion—you’re saying the subject matter (or the assertion) is fairly stated / in compliance / effective in all material respects based on the criteria.
  • A review engagement provides limited assurance (meaningful, but lower than examination). Your report expresses negative assurance—you’re saying you are not aware of any material modifications that should be made for the subject matter (or assertion) to be in conformity with the criteria.

Why it matters: the wording in the report must match the assurance level. On the exam, a frequent trap is mixing “in our opinion…” (examination-style) with “we are not aware…” (review-style).

How an examination engagement works (process → report)

An examination is conceptually closest to an audit in rigor, but it is applied to non-financial-statement subject matter or assertions. You plan and perform procedures to reduce attestation risk to an appropriately low level, which supports a reasonable assurance opinion.

Typical steps you should have in mind:

  1. Engagement acceptance/continuance: Confirm ethical requirements (including independence), competence, and that criteria are suitable and available.
  2. Planning: Understand the subject matter and criteria, identify where material misstatements/noncompliance could occur, and design procedures.
  3. Evidence gathering: Use a mix of inspection, observation, confirmation, recalculation, reperformance, analytics, inquiry, etc., depending on the subject matter.
  4. Evaluate results: Consider materiality, aggregate misstatements/deviations, and whether evidence is sufficient and appropriate.
  5. Form an opinion and report: Positive opinion based on the criteria.
What the examination report communicates

An examination report generally includes these ideas (exact phrasing varies by AT-C guidance and the engagement circumstances):

  • Title indicating independence (commonly includes the word “Independent”).
  • Addressee (often specified parties or general users, depending on the engagement).
  • Identification of the subject matter or the assertion and the period/date covered.
  • A statement that the responsible party is responsible for the subject matter/ assertion.
  • A statement that the practitioner’s responsibility is to express an opinion based on the examination.
  • A statement that the engagement was conducted in accordance with attestation standards established by the AICPA (SSAE / AT-C).
  • A description that an examination involves performing procedures to obtain evidence and that the nature/timing/extent depends on judgment.
  • An opinion (positive assurance) tied to the criteria.
  • Signature, city/state (as applicable in practice), and report date.

A good way to internalize the opinion concept is to think: examination = “we tested enough to say it is okay (within materiality).”

Example: mapping facts to an examination conclusion

Suppose management asserts: “The company complied with the debt covenant requiring a current ratio of at least 1.25 at year-end.” Criteria = the debt agreement’s definition of current ratio. You perform procedures on the components of current assets and liabilities per the agreement, evaluate adjustments, and conclude the ratio is 1.31.

  • If evidence supports the calculation and definitions, you can issue an unmodified opinion that management’s assertion is fairly stated, in all material respects, based on the debt agreement.
  • If the ratio is 1.18 and management’s assertion says they complied, that’s a material misstatement of the assertion—your report would be modified (see below).
How a review engagement works (process → report)

A review provides limited assurance. In attestation, that generally means your work is heavily based on:

  • Inquiry of knowledgeable persons, and
  • Analytical procedures (plausibility checks, trend/ratio analysis, reasonableness tests),

with other procedures performed as needed if something seems wrong.

Conceptually, review = “we didn’t test enough to say it is okay, but nothing came to our attention suggesting it’s not okay (materially).”

What the review report communicates

A review report generally includes:

  • Title and addressee.
  • Identification of the subject matter/assertion and applicable criteria.
  • Statements separating responsible party’s responsibility from practitioner’s responsibility.
  • A statement that a review was conducted in accordance with attestation standards.
  • A statement that a review is substantially less in scope than an examination.
  • The limited assurance conclusion using negative assurance wording (for example, “we are not aware of any material modifications…”).
  • Signature and date.

A common exam pitfall is to describe review procedures like an audit (“we obtained an understanding of internal control to plan the engagement,” “we tested supporting documentation extensively”). That language signals a higher level of work than a review is designed to provide.

Comparing examination vs review (attestation)
FeatureExaminationReview
Level of assuranceReasonable assuranceLimited assurance
Report conclusion stylePositive opinion/conclusionNegative assurance (“not aware of…”)
Typical evidenceMore extensive, includes tests beyond inquiry/analyticsPrimarily inquiry and analytical procedures
Risk conceptReduce attestation risk to low levelReduce risk, but not to examination level
Common CPA exam trapUsing review-style wording in an exam reportUsing exam/audit-style wording in a review report
Report modifications: when the standard conclusion changes

Your report must reflect what the evidence supports. In both examinations and reviews, modifications typically arise from one of two root causes:

  1. The subject matter/assertion is materially misstated (departure from criteria).
  2. You can’t get sufficient appropriate evidence (scope limitation).

How that shows up in reporting (high-level logic):

  • If the subject matter/assertion is materially misstated, you modify the conclusion/opinion accordingly (often analogous to qualified/adverse concepts—severity depends on materiality and pervasiveness).
  • If you have a scope limitation, you may qualify or disclaim, depending on how severe the limitation is.

On the exam, you’re often not asked to draft the entire modified report, but you are expected to know which direction the report changes: “misstatement” changes what you conclude about the subject matter; “scope limitation” changes what you can conclude because you lack evidence.

“Suitable criteria” and report wording—where students get tripped up

Two recurring misunderstandings:

  • Forgetting to tie the conclusion to the criteria. Attestation reporting is always “based on [criteria].” If you don’t anchor the conclusion to criteria, the user can’t tell what standard you used.
  • Confusing management’s responsibility with the practitioner’s. Management (or another responsible party) is responsible for the subject matter and (when applicable) the assertion. You are responsible for performing the engagement and expressing a conclusion.
“Show it in action” mini-examples (wording level)

These are illustrative, not meant to be memorized word-for-word.

Examination (reasonable assurance) conclusion example:

  • “In our opinion, management’s assertion that XYZ complied with the specified requirements of the contract for the year ended [date] is fairly stated, in all material respects, based on the contract criteria.”

Review (limited assurance) conclusion example:

  • “Based on our review, we are not aware of any material modifications that should be made to management’s assertion… for it to be fairly stated, in all material respects, based on the criteria.”

Notice how the review conclusion avoids “in our opinion” and instead uses “not aware.”

Exam Focus
  • Typical question patterns:
    • Identify whether a report paragraph describes an examination or a review based on assurance wording (“in our opinion” vs “not aware”).
    • Choose which procedures are consistent with a review (inquiry/analytics) versus an examination (more extensive testing).
    • Determine whether a described issue is a departure from criteria (misstatement) or a scope limitation (insufficient evidence) and what that implies for the report.
  • Common mistakes:
    • Treating an attestation examination as if it were a GAAS audit of financial statements (wrong framework, wrong report assumptions).
    • Using positive assurance language in a review report (or negative assurance language in an examination report).
    • Omitting/ignoring the role of suitable criteria—especially when a question hints that criteria are not available to users.

Agreed-upon procedures engagements

What an agreed-upon procedures (AUP) engagement is

An agreed-upon procedures engagement (AUP) is an attestation service in which you:

  1. Agree with specified parties on exactly which procedures you will perform, and then
  2. Report the procedures and the related findings, without providing an opinion or conclusion.

The defining feature is that the specified parties determine the procedures. That flips the usual assurance model: instead of you designing procedures to support an overall conclusion, the users pick procedures that matter to them, and they interpret the findings for themselves.

Why AUP engagements matter (and when they’re used)

AUP is common when users want transparency over specific facts but don’t need (or can’t define) a single overall assertion to opine on. Examples:

  • A lender wants verification of specific items supporting a borrowing base.
  • A grantor wants you to test a sample of expenditures for allowability.
  • A buyer and seller want certain metrics checked during due diligence.

AUP also helps when an overall assertion would be hard to support with a single set of criteria or when users want to control the cost/scope by selecting narrow procedures.

The most important concept: AUP provides no assurance

In AUP reporting, you do not express:

  • reasonable assurance (no “opinion”),
  • limited assurance (no “we are not aware”), or
  • any conclusion at all.

Instead, you report findings, such as:

  • “We compared X to Y and found no exceptions,” or
  • “We recalculated Z and noted the following differences,” or
  • “Of the 40 items tested, 3 did not agree to supporting documentation.”

On the CPA exam, this is a major discriminator: if the report includes an “opinion” or “not aware” conclusion, it’s not AUP.

How an AUP engagement works (step-by-step)

Even though AUP is narrower, it still requires disciplined execution.

  1. Define the subject matter and the specified parties
    You need clarity about who will use the report and what the procedures relate to (e.g., a schedule, a population of transactions, a compliance requirement).

  2. Agree on precise procedures
    Procedures must be written so that another practitioner could perform them and obtain comparable findings. Vague procedures (“review the schedule for reasonableness”) are a recipe for disputes.

  3. Perform the procedures exactly as agreed
    A key risk is “scope creep”—doing extra work that implies assurance or deviating from the agreed steps. If parties want changes, the procedures should be formally updated.

  4. Report procedures and findings (not interpretations)
    You report what you did and what you found. You do not add evaluative language like “the schedule is fairly stated” or “controls are effective.”

  5. Include required report elements and restrictions (when applicable)
    Because AUP procedures are tailored to specific users’ needs, AUP reports are commonly intended for specified parties.

What the AUP report looks like (and what it must avoid)

An AUP report is structured around transparency. The reader should be able to see:

  • The subject matter (what the procedures were applied to).
  • A statement that procedures were agreed upon by the specified parties.
  • A clear listing of each procedure performed.
  • The finding for each procedure.

What it must avoid:

  • Any form of assurance language (“in our opinion,” “we conclude,” “we are not aware…”).
  • Conclusions about the overall subject matter. Even if all findings show “no exceptions,” you still do not “upgrade” that into assurance.
Restricted use: why it is often (but not conceptually always) emphasized

Because the specified parties chose the procedures, there is an inherent risk that outsiders could misunderstand the sufficiency of the procedures for their own purposes. For that reason, AUP reports are generally intended for use by specified parties who understand the context of the agreement.

In exam questions, if you see language like “restricted to the specified parties,” it strongly suggests AUP (or another situation where limited distribution is appropriate). If a question asks whether an AUP report provides assurance to general users, the answer is no—the report is a presentation of procedures and findings.

“Show it in action” AUP example

Assume a lender asks for an AUP engagement on a company’s accounts receivable aging used to support a borrowing base.

Agreed procedures might include:

  1. Obtain the A/R aging report as of a specific date.
  2. Select 30 customer balances and agree amounts to underlying invoices.
  3. For selected balances, inspect subsequent cash receipts through a specified cutoff date.
  4. Recalculate the aging bucket assignment for the selected items.

Findings might be reported like:

  • “For 28 of 30 items, invoice amounts agreed without exception; for 2 items, invoice amounts differed by $X and $Y.”
  • “Subsequent receipts were noted for 25 of 30 items in the amounts of…; no subsequent receipts were noted for 5 items.”

Notice what is not said:

  • No statement that receivables are “fairly stated.”
  • No statement that collectability is “reasonable.”
  • No “not aware of modifications.”

The lender decides what these findings mean for credit risk.

Common pitfalls in AUP engagements (and how they show up on the exam)
  1. Accidentally providing assurance
    Students sometimes think “no exceptions noted” equals limited assurance. It doesn’t. It’s simply a finding.

  2. Vague procedures
    If procedures aren’t measurable and repeatable, you can’t credibly report findings. Exam questions may present an imprecise procedure and ask what is wrong with it.

  3. Adding interpretation instead of findings
    “Nothing came to our attention…” is a review-style conclusion, not an AUP finding. AUP reporting stays descriptive.

  4. Misunderstanding who determines sufficiency
    In AUP, the specified parties evaluate sufficiency of procedures. You may include a statement that you make no representation regarding sufficiency for the users’ purposes.

AUP vs examination/review: the clean conceptual separation

A helpful mental model:

  • Examination: You choose procedures to support a positive conclusion.
  • Review: You perform limited work to support negative assurance.
  • AUP: Users choose procedures; you report findings only.

If you remember only one line for AUP, make it this: AUP is transparency, not assurance.

Exam Focus
  • Typical question patterns:
    • Identify AUP from report wording: look for “procedures and findings” and absence of any opinion/conclusion.
    • Decide whether a described statement is inappropriate because it implies assurance (e.g., “we conclude,” “fairly stated,” “not aware”).
    • Questions about who evaluates sufficiency of procedures (specified parties, not the practitioner).
  • Common mistakes:
    • Treating “no exceptions found” as a form of assurance—on the exam, it remains a finding, not a conclusion.
    • Forgetting that the practitioner reports what was done and what was found, not what the findings “mean.”
    • Confusing AUP with a review because both may involve limited work—AUP is limited by agreement, while a review is limited by the assurance objective.