The management representation letter: SOC 2 wording to expect before you sign

The CPA firm sends its own wording at the end of fieldwork. This is what it usually says, so management can check every line against its records before signing.

A SOC 2 management representation letter is the written confirmation management gives the CPA firm at the end of fieldwork. Management is responsible for the system and its description. The description is fair. The controls were designed and operated as described. Every deviation, incident and other matter it knows of has been disclosed. The letter is dated the same day as the firm’s report.

The firm sends its own wording, and that is the letter you sign. This template shows what it usually says, so you can gather the records behind each line before it arrives.

Why the firm asks for it

A SOC 2 examination is an attestation engagement performed under the AICPA attestation standards. Those standards require the practitioner to ask the responsible party for written representations before reporting.1 Some facts only management can confirm: whether it disclosed every incident, whether anything happened after the period ended, whether it gave the firm every record it asked for. The letter puts those statements in writing. The AICPA guide that practitioners work from for SOC 2 covers what the firm asks for in this engagement.2 Polara Labs is not a CPA firm. SOC 2 examinations are performed by independent licensed U.S. CPA firms.

It is not the management assertion. The assertion is Section 2 of the report and every reader sees it. The representation letter goes to the firm alone and stays in its working papers. Customers never see it.

SOC 2 management representation letter template, full text

Every bracketed field is a detail to fill in, and the last section lists them. Section 4 is the table of changes and matters disclosed, with a worked example for Moonrake, a fictional ten person company on AWS at the end of its first Type 2 period.

[Company name]

SOC 2 Management Representation Letter

Also called
Rep letter or written representations
Requested by
[CPA firm], at the end of fieldwork
Signed by
[Company name] management, on company letterhead
Dated
[Report date], the same date as the CPA firm report

1. How to use this template

At the end of fieldwork the CPA firm asks management to confirm in writing the things only management can confirm: that it is responsible for the system and its description, that the description is fair, that the controls were designed and operated as described, and that it has told the firm everything relevant. The firm supplies its own wording, and that is the letter management signs.

This template shows what that letter usually contains, so management can prepare before it arrives: gather the incident log, the change records and the list of exceptions, and check each representation against them. It is not a replacement for the letter the firm sends. When the firm letter arrives, read every line of it, not this one, before signing.

The representation letter is different from the management assertion. The assertion is printed in Section 2 of the SOC 2 report and is read by everyone who receives the report. The representation letter is addressed to [CPA firm] only, stays in the firm working papers, and is not part of the report.

This version is for a Type 2 report. For a Type 1, replace "throughout the period [Period start] to [Period end]" with "as of [As-of date]" and delete representation 5.

2. Who writes it, who signs it, and when

QuestionAnswer
Who asks for it[CPA firm], the independent licensed CPA firm performing the examination, near the end of fieldwork.
Who writes itThe firm usually supplies the wording. Management puts it on company letterhead.
Who signs itMembers of management responsible for the system and with knowledge of the matters in it, for example the chief executive officer and the officer who owns the controls. Here: [Signer name], [Signer title].
When it is datedThe same date as the CPA firm report. The firm does not issue its report until it has the signed letter.
Who it goes toThe CPA firm only. It is not sent to customers.

3. The letter

[Company letterhead]

[Report date]

To [CPA firm]

We are providing this letter in connection with your examination of the description of [Company name]'s [System name] system for the period [Period start] to [Period end], and of the suitability of the design and operating effectiveness of the controls stated in the description to provide reasonable assurance that our service commitments and system requirements were achieved based on the trust services criteria relevant to [Categories in scope].

We confirm, to the best of our knowledge and belief, having made the inquiries we considered necessary, the following representations made to you during your examination:

  1. We are responsible for the description of [Company name]'s [System name] system (the description) and for preparing and presenting it fairly in accordance with the description criteria. We are also responsible for our assertion, which accompanies the description, and we confirm it as of the date of this letter.
  2. We are responsible for designing, implementing and operating controls within the system to provide reasonable assurance that [Company name]'s service commitments and system requirements were achieved based on the trust services criteria relevant to [Categories in scope], for selecting those criteria, and for identifying the risks that threaten the achievement of those commitments and requirements.
  3. The description fairly presents the [System name] system that was designed and implemented throughout the period [Period start] to [Period end].
  4. The controls stated in the description were suitably designed throughout the period to provide reasonable assurance that our service commitments and system requirements would be achieved if the controls operated effectively.
  5. The controls stated in the description operated effectively throughout the period to provide reasonable assurance that our service commitments and system requirements were achieved.
  6. We have disclosed to you all deviations in the operation of controls, all security incidents and system incidents, all instances of non-compliance with laws, regulations or contracts, and all fraud or suspected fraud of which we are aware that could affect the description or the controls.
  7. We have given you access to all information, records and people you asked for, and we have disclosed all matters relevant to the description and the controls of which we are aware.
  8. We have disclosed to you any event after the end of the period, up to the date of this letter, that could have a significant effect on the description or on our assertion.
  9. The description identifies each subservice organization the system uses, states whether it is presented using the carve out or the inclusive method, and describes the complementary subservice organization controls and the complementary user entity controls that the controls assume.
  10. The changes to the system and its controls during the period, and the matters disclosed to you, are listed in the table attached to this letter, and the list is complete.

[Signer name], [Signer title], [Company name]

[Second signer name and title], [Company name]

Sign-off. Name, signature and date for: Officer signing for management, Second officer.

4. Attached: changes and matters disclosed

List every change to the system or its controls during the period, and every matter in representation 6 that you disclosed to the firm. If there is nothing to list in a row, write None. A matter disclosed in conversation still goes in the table.

ItemDateWhat happenedControl or criterion affectedDisclosed to the firm on
Change to the system or controls
Deviation in a control
Security or system incident
Non-compliance with a law, regulation or contract
Fraud or suspected fraud
Event after the period end

4.1 Worked example

Moonrake, a fictional ten person company on AWS, at the end of its first Type 2 period, would fill the table like this:

ItemDateWhat happenedControl or criterion affectedDisclosed to the firm on
Change to the system or controls7 AprilThe deployment pipeline moved from a long lived AWS key to short lived credentialsCC6.1, CC8.1At the walkthrough
Deviation in a control3 MayOne quarterly access review was finished nine days after its due dateCC6.2, CC6.3When the firm tested the review
Security or system incident7 AprilAn AWS key flagged in a pull request, deactivated in 25 minutes, no use foundCC7.3, CC7.4At the walkthrough, with the incident log
Non-compliance with a law, regulation or contractNone
Fraud or suspected fraudNone
Event after the period end12 AugustA breach at the help desk vendor exposed four support ticketsCC9.2, CC7.4Before the letter was signed

5. What the letter is not

  • It is not evidence that a control operated. The firm tests the controls itself, and a representation does not stand in for a record the firm asked for.
  • It does not change the opinion. The opinion rests on the evidence the firm obtained, and the letter confirms what management told the firm along the way.
  • It is not the management assertion, which is Section 2 of the report and is read by its users.
  • It is not a document to send to customers, and it says nothing about the months after the date it is signed.

6. Before you sign

  1. Read each representation in the firm letter against the incident log, the change records, the exceptions the firm raised and the list of subservice organizations.
  2. Fill in the attached table, and check that every item in it was told to the firm before the letter date.
  3. If you cannot make one of the representations as written, tell the firm before signing and let it decide what follows. Do not edit the wording yourself.
  4. Sign on the date the firm gives you, which is the date of its report, never earlier.
  5. Keep a signed copy with the audit records.

7. Fields to complete

Replace every bracketed field in this document with your own detail, then delete this section.

FieldWhat to enter
[Company name]Your legal company name.
[System name]The product or service the report covers.
[Period start]For a Type 2 report, the first day of the period.
[Period end]For a Type 2 report, the last day of the period.
[Signer name]The officer signing for management.
[Signer title]Their title, printed under the name.
[Categories in scope]For example the Security category.
[CPA firm]The firm that issued, or is performing, the examination, named exactly as on its engagement letter or opinion.
[Report date]The date the CPA firm gives its report. The letter carries the same date.
[Second signer name and title]A second officer who knows the matters in the letter, if the CPA firm asks for one. Delete the line if not.

Preparing before the firm’s letter arrives

  1. Pull the incident log. Every incident in the period, and anything since the period ended, belongs in representations 6 and 8. The security incident log is the list to read from.
  2. List the changes. New systems, new vendors, a control that changed or lapsed. If the firm has not heard about one yet, tell it before the letter date, not in the letter.
  3. Decide who signs. The firm names whose signatures it needs. Both people should be able to answer for every line. Who can sign for management covers the question for the assertion, and the same people usually sign here.
  4. Read the firm’s wording, not this one. Compare it with the template. Ask about anything unfamiliar. Sign on the date the firm gives you.

After the report is issued, the letter is done and it says nothing about later months. For those, a bridge letter is management’s statement to customers about the months since the period ended.

Questions

What is a management representation letter in a SOC 2 audit?
A letter in which management confirms to the CPA firm, in writing, the things only management can confirm: that it is responsible for the system and its description, that the description is fairly presented, that the controls were designed and operated as described, and that it has disclosed every deviation, incident and other relevant matter it knows of. The firm asks for it at the end of fieldwork.
Who signs the management representation letter?
Members of management who are responsible for the system and know the matters in the letter, usually the chief executive officer and the officer who owns the controls, such as the chief technology officer. The CPA firm says whose signatures it needs.
When is the representation letter signed?
At the end of fieldwork, and it is dated the same date as the CPA firm report. The firm does not issue its report without the signed letter, so it is one of the last documents in the engagement.
What is the difference between the management assertion and the representation letter?
The management assertion is printed in Section 2 of the SOC 2 report and every reader of the report sees it. The representation letter is addressed to the CPA firm only, stays in the firm working papers, and is not part of the report. The letter confirms the assertion among other things, but the two are separate documents.
What happens if management cannot make one of the representations?
Tell the CPA firm before signing. The firm decides what follows, and it can affect the opinion.
Does the auditor write the representation letter?
The CPA firm usually supplies the wording. Management puts it on company letterhead, reads it against its own records and signs it. The representations are management statements, so management is the party that makes them.

Sources

  1. Statements on Standards for Attestation Engagements AICPA. The attestation standards a SOC 2 examination is performed under.
  2. SOC 2: Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy AICPA. The implementation guide practitioners work from, including sampling and the assertion.

Get audit-ready without a compliance team.

The readiness assessment is free, with no payment and no card. Star is $2,000 one time to get on the platform and close your gaps. Orbit is $7,800 a year, and your SOC 2 Type 2 audit is included in every contract year. You can be audit-ready starting at about a week.

Take the free assessment

Polara Labs is not a CPA firm. SOC 2 examinations are performed by independent licensed U.S. CPA firms.