SOC 2Nov 17, 202614 min read

SOC 2 IPE: Why Auditors Reject Your Compliance Platform Screenshots

SOC 2 IPE explained by an auditor: why screenshots and platform exports get rejected, how completeness and accuracy are tested, and how to prepare evidence.

On this page · 15 sections
Key takeaways
  • IPE, or information produced by the entity, is any report, listing, log, export, or screenshot your organization generates and gives the auditor as evidence.
  • Under AICPA attestation standards, a SOC 2 auditor using IPE must evaluate whether it is sufficiently reliable, including obtaining evidence about its completeness and accuracy.
  • Screenshots and platform exports get rejected when they lack timestamps, parameters, or a traceable link to the system of record, or when they show a point in time instead of a period.
  • Incomplete populations are the most damaging IPE failure, because every sample the auditor selects from them is unreliable.
  • Compliance automation platforms help collect evidence, but they do not remove the auditor's obligation to evaluate it.

SOC 2 IPE (information produced by the entity) is the reports, lists, logs, exports, and screenshots your organization produces and gives your auditor to support testing. Because the auditor did not generate this information, the attestation standards require the auditor to evaluate whether it is reliable, which means obtaining evidence that it is complete and accurate. When the auditor cannot do that, the evidence is not usable, no matter how polished it looks.

That requirement explains most of the friction teams feel during SOC 2 fieldwork. The control may have operated perfectly, but if the evidence cannot be shown to be complete and accurate, the auditor cannot conclude that it did. This guide explains how auditors think about IPE, why compliance platform screenshots are a frequent problem, and how to prepare evidence that holds up.

What is IPE in a SOC 2 audit?

IPE in a SOC 2 audit is any information created by the service organization that the auditor uses as evidence or to select samples. It includes system-generated reports, manual lists, exports from tools, configuration screenshots, and dashboards. SOC examinations rely heavily on information produced by management rather than direct observation by the auditor (Forvis Mazars).

Common SOC 2 IPE examples:

IPE Typical source What the auditor uses it for
List of active users Identity provider, application admin console Population for access review and least privilege testing
List of terminated employees HR information system Population for timely access removal testing
List of new hires HR information system Population for onboarding, training, and background check testing
List of production changes Version control, ticketing system, deployment logs Population for change approval and testing
Access review export Identity governance tool, spreadsheet Evidence that reviews occurred and decisions were acted on
Vulnerability scan report Scanning tool Evidence that scanning occurred and findings were tracked
Configuration screenshot Cloud console, application settings Evidence that a setting, such as encryption or MFA, was enforced
Incident log Ticketing or incident management tool Population for incident response testing

A useful distinction: some IPE is the evidence itself, such as a screenshot of an MFA policy. Other IPE is the population the auditor samples from, such as the list of terminated employees. Both must be reliable, but population failures do more damage.

Why does IPE matter more in 2026?

IPE matters more in 2026 because expectations around evidence reliability have risen while compliance automation has made evidence look more complete than it sometimes is. Three trends are pushing in the same direction:

  1. Higher examiner expectations. Forvis Mazars observes that what has changed is not the definition of IPE but examiner expectations around completeness, accuracy, and reliability (Forvis Mazars).
  2. Peer review pressure on SOC 2 quality. The AICPA Peer Review Board's May 2026 alert directed reviewers to look for SOC 2 engagements that were not designed around each client's risks. Engagement-specific testing means more questions about the specific evidence each client provides.
  3. Proposed attestation standard changes. The AICPA Auditing Standards Board has proposed revisions to the attestation standards, including changes to AT-C 205 that address the relevance and reliability of information used as evidence. Under the exposure-draft timetable, those changes would take effect for engagements beginning on or after June 15, 2029, and remain subject to final approval (Bright Defense).

The direction is clear: auditors will be asked to show more work on the evidence you give them, so you will be asked for more support behind it.

What do completeness and accuracy mean for SOC 2 evidence?

Completeness means the information includes every item it should. Accuracy means each item correctly reflects what the system actually recorded. Together, they determine whether the auditor can rely on the information.

  • Completeness example. A list of terminated employees for the period must include every termination, not just those processed through the standard workflow. If one contractor's termination was handled outside the HR system, the list is incomplete.
  • Accuracy example. Termination dates on the list must match the dates in the HR system of record. If the export used the date the record was last edited rather than the termination effective date, the list is inaccurate.

An auditor needs evidence of both. That evidence can come from observing how the report was generated, inspecting the query and its parameters, reconciling the report to another independent source, or testing controls over the system that produces the report.

Why do auditors reject compliance platform screenshots?

Auditors reject compliance platform screenshots when the screenshot cannot be shown to be complete, accurate, and relevant to the period being tested. A screenshot proves what a screen displayed at one moment. It rarely proves what the underlying system contained across a period.

The most common reasons:

  • No date or time. A screenshot without a visible timestamp, or with a timestamp outside the period, does not support a period-of-time conclusion. Providing screenshots only with no supporting detail, or underlying data without date and time stamps, is a common pitfall (Schneider Downs).
  • No parameters. A filtered list without visible filters could have excluded records. The auditor cannot tell what was left out.
  • Cropped or partial view. A screenshot of the first page of a list is not the list.
  • No link to the system of record. A platform's view of your identity provider is not the identity provider. If the integration only covers some accounts, the platform's list is incomplete by design.
  • Point in time, not period. A screenshot showing that MFA is enforced today does not show it was enforced throughout the observation period.
  • "Test passing" is not control evidence. A green check in a compliance platform shows that the platform's automated test passed when it ran. It does not by itself show that a person performed a review, approved a change, or acted on a finding.

None of this means platform evidence is useless. It means platform evidence often needs supporting detail before an auditor can rely on it.

Why are incomplete populations the most damaging IPE failure?

Incomplete populations are the most damaging IPE failure because the auditor selects samples from them. If the population is missing items, every conclusion drawn from the sample is unsupported, and the problem may not surface until late in fieldwork when the auditor reconciles the population to another source.

Common population failures:

Control area Population How it goes wrong
Offboarding Terminated employees HRIS list excludes contractors, or identity provider list excludes accounts deleted mid-period
Onboarding New hires List includes only employees, not contractors with system access
Change management Production changes Ticketing list excludes changes deployed outside the standard pipeline, such as hotfixes or infrastructure changes
Access reviews Accounts in scope Review covers the identity provider but not database users, API keys, or service accounts
Incident response Security incidents Only incidents formally declared are listed, not alerts that were triaged and closed
Vulnerability management Vulnerabilities Report covers one scanner or one environment, not all in-scope assets

Our guide to SOC 2 sample sizes explains how populations drive sampling. The short version: a sample is only as good as the population it came from.

How do SOC 2 auditors test IPE?

SOC 2 auditors test IPE using one or more procedures that establish completeness and accuracy. Which procedures they choose depends on the risk, the source system, and what controls exist over the report.

  1. Observe generation. The auditor watches someone generate the report from the source system, noting the query, filters, and date range.
  2. Inspect parameters. The auditor reviews the saved query, report definition, or script used to produce the list.
  3. Reconcile to another source. The auditor compares the list to an independent source, such as termination dates in the HR system against account disable dates in the identity provider, or total commits in version control against change tickets.
  4. Reperform. The auditor independently runs the same query and compares results.
  5. Test controls over the report. For standard reports from well-controlled systems, the auditor may rely on testing of controls over the system itself.
  6. Evaluate precision. The auditor checks that the information is detailed enough for the purpose, for example that a change list includes approver and deployment date, not just a ticket title.

You can make every one of these faster by documenting how each key report is generated before the auditor asks.

SOC 2 IPE documentation template

For each key report or population, record the following. This turns a fieldwork scramble into a lookup.

Field What to record Example
Report name A clear, stable name Terminated users, Q1 to Q4
Control supported The control ID and description Access removed within one business day of termination
Source system The system of record HRIS (production instance)
Generation method How the report is produced Standard termination report, exported to CSV
Parameters Filters, date range, fields Effective termination date from period start to period end; all worker types
Generated by and when Person and timestamp People operations lead, date of export
Completeness check How you know nothing is missing Count reconciled to identity provider deactivation events for the same period
Accuracy check How you know values are right Ten records spot-checked against HRIS employee records
Known limitations Anything the auditor should know Contractors managed in a separate system, provided as a second list
File reference Where the export is stored Evidence repository path

This is the same logic Forvis Mazars describes as a standard IPE "logic and retrieval" template: capture the source system, parameters, and retrieval steps, and include the clearest tie-out that demonstrates completeness and accuracy (Forvis Mazars).

Worked example: reconciling a termination population

The example below is illustrative, with fictional numbers, to show how a simple reconciliation catches an incomplete population before the auditor does.

The control: Access to production systems is removed within one business day of termination.

Step 1. Generate the population. The people operations lead exports all terminations with an effective date inside the twelve-month period from the HR system. The export returns 42 records.

Step 2. Generate a second source. The IT lead exports all user deactivation events for the same period from the identity provider. The export returns 51 deactivations.

Step 3. Compare. Matching by email address shows:

Result Count Explanation
Matched: terminated in HR and deactivated in identity provider 40 Expected
Deactivated in identity provider, not in HR export 11 6 contractors managed outside the HR system; 3 role changes; 2 test accounts
Terminated in HR, no deactivation found 2 1 employee never had an identity provider account; 1 deactivation missed

Step 4. Resolve. The six contractors were terminated users, so the true population is 48, not 42. The HR export was incomplete because contractors live in a separate system. The one missed deactivation is a real control failure.

Step 5. Document. Record both exports, the matching logic, the explanations, and the corrected population of 48, with the contractor list attached as a second source.

The company now knows two things the auditor would otherwise have discovered during fieldwork: the population was incomplete, and one control failure exists. It can provide a complete population with its reconciliation, and prepare a management response for the failure. Our guide to SOC 2 exceptions explains how such a failure is typically reported.

How does IPE differ for automated and manual controls?

IPE differs for automated and manual controls because the evidence comes from different places and fails in different ways. Knowing which kind of control you are evidencing tells you what the auditor will need.

Automated control Manual control
Example MFA enforced by identity provider policy Quarterly user access review
Primary evidence System configuration and change history Review records, sign-offs, and resulting actions
Key IPE risk Configuration changed during the period without detection Review performed on an incomplete user list
What auditors often test Configuration at points in time, change logs, and controls over changes to the setting The population reviewed, the reviewer's decisions, and follow-through on removals
Common evidence gap A single screenshot taken at fieldwork Sign-off with no evidence of what was actually reviewed

For automated controls, the strongest evidence often comes from change history showing the setting was not altered during the period. For manual controls, the strongest evidence shows the complete population the reviewer saw and the actions that followed.

Does a compliance automation platform solve IPE?

A compliance automation platform helps with IPE but does not solve it. Platforms such as Vanta, Drata, and Sprinto collect evidence automatically, map it to controls, and flag failing tests, which reduces manual work. The auditor still has to evaluate whether the evidence is reliable.

Where platforms help:

  • Consistent, timestamped collection on a schedule.
  • Direct integrations with identity providers, cloud accounts, and HR systems.
  • Central storage that reduces lost evidence.
  • Continuous monitoring that surfaces failures during the period instead of at fieldwork.

Where gaps remain:

  • Integration coverage. The platform only sees systems that are connected and accounts that are in scope of the integration.
  • Manual controls. Reviews, approvals, and decisions made outside connected tools still need human-generated evidence.
  • Configuration drift. An integration that broke for two months leaves a two-month hole that the platform may not make obvious.
  • Auditor access. Auditors may need to see the source system, not only the platform's representation of it.

Treat the platform as your evidence system, not your evidence. The source systems behind it remain what the auditor ultimately relies on.

How do you prepare IPE before SOC 2 fieldwork?

Prepare IPE by identifying the reports your key controls depend on, documenting how each is produced, and testing completeness and accuracy yourself before the auditor does. A practical sequence:

  1. List key populations. Start with the six that drive most sampling: users, terminations, new hires, changes, access reviews, and incidents.
  2. Name the system of record for each. Decide which system is authoritative when two disagree.
  3. Document generation steps. Use the template above.
  4. Run a reconciliation. Compare each population to a second source and resolve differences.
  5. Check period coverage. Confirm evidence exists for the first and last months of the period, not just the middle.
  6. Check integration health. Review compliance platform integration logs for outages during the period.
  7. Fix retention. Make sure logs you will need are not deleted before fieldwork ends.
  8. Run a mock request. Have someone outside the compliance team request three populations and three samples, and time how long it takes.

Teams that do this once usually find the second year far easier, because the documentation carries forward.

What happens if IPE problems are found during fieldwork?

If IPE problems are found during fieldwork, the auditor will typically ask for corrected or supplementary information and may expand testing. If reliable information cannot be produced, the auditor may be unable to conclude on the affected control, which can lead to an exception or, where the effect is significant, a modified opinion. Our guide to SOC 2 exceptions vs. a qualified opinion explains how those outcomes are decided.

The best outcome is to find IPE problems yourself, during the period, when they can still be fixed.

Prepare evidence that holds up

Ledger Audits' Evidence Engine is a monthly retainer that monitors operating effectiveness across the full audit window, maintains an evidence repository with chain of custody, runs a mock fieldwork dry run before your auditor arrives, and liaises directly with your auditor. IPE documentation and population reconciliations are built into the monthly cycle, so evidence questions are answered before fieldwork starts. Talk to us about Evidence Engine.

Frequently asked questions

What is IPE in SOC 2?

IPE, or information produced by the entity, is any report, list, log, export, or screenshot a service organization generates and provides to its SOC 2 auditor as evidence or as a population for sampling. Because the auditor did not generate it, the auditor must evaluate whether it is reliable, including its completeness and accuracy.

Why does my SOC 2 auditor want more than a screenshot?

A screenshot shows what a screen displayed at one moment. Your auditor needs to know the information is complete, accurate, and relevant to the full observation period. That usually requires timestamps, visible parameters, a link to the system of record, or a reconciliation to another source.

What does completeness and accuracy mean in a SOC 2 audit?

Completeness means a report or list includes every item it should, such as every termination during the period. Accuracy means each item correctly reflects the system of record, such as correct termination dates. Auditors need evidence of both before relying on information you produce.

Is compliance platform evidence accepted for SOC 2?

Compliance platform evidence can be accepted, but the auditor still evaluates its reliability. Gaps in integration coverage, manual controls outside connected tools, and integration outages can all limit what the platform's evidence supports.

What is a population in a SOC 2 audit?

A population is the complete set of items a control applies to during the period, such as all production changes or all terminated employees. The auditor selects samples from the population, so an incomplete population undermines every conclusion drawn from it.

How do auditors test IPE?

Auditors test IPE by observing report generation, inspecting queries and parameters, reconciling to independent sources, reperforming queries, testing controls over the source system, and evaluating whether the information is detailed enough for the test.

Can IPE problems cause a SOC 2 exception?

Yes. If reliable information cannot be produced for a control, the auditor may be unable to conclude that the control operated, which can result in an exception. Where the effect is significant, it can contribute to a modified opinion.

How do I make IPE easier for my auditor?

Document how each key report is generated, name the system of record, reconcile populations to a second source, confirm coverage for the full period, and fix log retention before fieldwork. A short IPE documentation template for each key report saves the most time.

Get independent eyes on it before your auditor or buyer does.

Ledger Audits provides readiness and internal audit work only. We never issue SOC 2 reports or ISO certificates, which keeps our review independent of your examination.

Talk to us about Evidence Engine
Get started

Book a discovery call

Tell us where you are in your SOC 2 or ISO 27001 journey and what you need to pass. We will tell you, honestly, what it takes.

01A 30‑minute call with a lead auditor, not a sales rep.
02An honest read on your framework, scope, and timeline.
03A fixed, written figure within one business day.

Prefer email? [email protected]

Discovery requestConfidential

We reply within one business day. Your details stay confidential.