Audit evidence survives when its source, timestamp, completeness and population can be shown, and screenshots rarely do | Compliance Automation Tools

[Skip to content](#main)
[Compliance Automation Tools](https://complianceautomationtools.com/)
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Menu
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Guide, read 13 Nov 2026

# Audit evidence survives when its source, timestamp, completeness and population can be shown, and screenshots rarely do

**The short answer:** Audit evidence survives when the auditor can see its source, capture time, completeness and accuracy, and the full population behind any sample. PCAOB AS 1105 paragraph.10 requires testing accuracy and completeness of company-produced information, which is why system exports with parameters usually beat screenshots.

[Framework Coverage Matrix](https://complianceautomationtools.com/matrix/) | [All guides](https://complianceautomationtools.com/guides/)

## Auditors judge evidence by relevance and reliability

PCAOB Auditing Standard 1105, Audit Evidence, defines audit evidence in paragraph.02 as all the information, whether obtained from audit procedures or other sources, that is used by the auditor in arriving at the conclusions on which the opinion is based. Paragraph.06 says appropriateness has two parts, relevance and reliability, and that evidence must be both. Paragraph.05 adds that obtaining more of the same type of evidence cannot compensate for the poor quality of that evidence.

That last point decides most disputes. Fifty screenshots of the same weak kind do not add up to one strong export. AS 1105 is written for audits of financial statements and internal control over financial reporting, and the SOC 2 attestation standards are separate, so treat it as the clearest public statement of the reasoning and not as the SOC 2 rule. The AICPA publishes the 2017 Trust Services Criteria (with revised points of focus, 2022), dated September 30, 2023 on its resource page, as the criteria for SOC 2 work. See [evidence](https://complianceautomationtools.com/glossary/evidence/) for the term.

## Reliability depends on the source and the controls over it

Paragraph.08 lists what makes evidence more reliable. Evidence from a knowledgeable source outside the company is more reliable than evidence from internal sources alone. Evidence obtained directly by the auditor is more reliable than evidence obtained indirectly. Original documents are more reliable than photocopies or digitized conversions, and the reliability of the converted kind depends on the controls over the conversion. It also says the reliability of information generated internally increases when the company's controls over that information are effective.

For a platform user, the last sentence matters most. Your exports come from your systems, so an auditor will ask how you know the report is complete. Photocopies, scans and exports all pass through a conversion step, which is why the control over that step matters. Keep a short note on each recurring export: the system, the report name or query, the parameters, who ran it, and what controls stop someone editing the output. Paragraph.16 also warns that observation is limited to the point in time it takes place, which is the same weakness a single screenshot has.

## Company-produced reports need accuracy and completeness shown

Paragraph.10 is the one to memorize. When using information produced by the company as audit evidence, the auditor should evaluate whether it is sufficient and appropriate by testing the accuracy and completeness of the information, or testing the controls over them, and by evaluating whether it is sufficiently precise and detailed for the audit's purpose.

In practice, show the query and the filter. A list of 212 users with the filter hidden proves nothing about the 240th user. Show the row count, the date range, and the system that produced it, and add a second count from a different view when you can. NIST SP 800-53 AU-3 gives the minimum record content: what type of event occurred, when, where, the source, the outcome, and the identity of anyone associated. AU-8 asks for time stamps in UTC or with a fixed offset. A good export carries the same fields.

Timing is part of relevance. Paragraph.07 says relevance depends on the design of the procedure and on the timing of the audit procedure used to test the control. For a period-based test, an export from the last day of the period shows the state on that day only. Evidence for a quarter needs the rows that show the control operating through the quarter, such as the review tickets with dates, or the log of the approval workflow.

| Evidence attribute | What to show | Where it comes from |
|---|---|---|
| Source | System name, report or API endpoint, run by whom | AS 1105.08 |
| Timestamp | Capture time in UTC or with a fixed offset | SP 800-53 AU-8 |
| Completeness | Row count, filters, date range, query text | AS 1105.10 |
| Accuracy | Spot check against a second source | AS 1105.10 |
| Integrity | Who can edit the output, and a hash or locked storage | SP 800-53 AU-9 |
| Retention | Kept for the longest period any framework asks | HIPAA 164.316(b)(2)(i): 6 years |

## Population and sample decide what the evidence proves

Paragraph.22 gives the three ways to pick items to test: all items, specific items, or audit sampling. Paragraph.24 says 100 percent examination fits when the procedure can be automated effectively and applied to the entire population. That is the case for most connector tests, and it is why a full-population export is stronger than a sample.

Paragraph.27 states a limit worth knowing: results from specifically selected items are not audit sampling and cannot be projected to the entire population. If you hand an auditor 10 hand-picked good examples, they prove those 10. Give the full list and let the auditor draw the sample, and keep the list intact as evidence of the population. SP 800-53 AU-11 ties retention to need: it asks that audit records be kept for an organization-defined period to support after-the-fact investigations and to meet regulatory and organizational retention requirements. Set that period to the longest any framework needs. Paragraph.29 adds that if evidence from one source is inconsistent with another, the auditor must resolve it, so reconcile your own sources first.

## Screenshots versus system exports

A screenshot shows one view at one moment, with the filter, the user and the time often cropped out. An export shows rows, parameters and a generation time that can be checked. Evidence in an inquiry-only form is the weakest kind: the note to paragraph.17 says inquiry of company personnel, by itself, does not provide sufficient audit evidence to support a conclusion about the effectiveness of a control. An email saying yes, we do this is inquiry. Use screenshots for settings that exist only in a UI, and then include the full window with the clock and the user, and the URL. For anything with a population, export.

HIPAA gives a plain example of why logs beat pictures. 45 CFR 164.312(b) requires hardware, software, and/or procedural mechanisms that record and examine activity in information systems containing electronic protected health information, and 164.308(a)(1)(ii)(D) requires regularly reviewing those records. A screenshot of a log viewer shows neither the record nor the review. A dated review ticket with a link to the export shows both. See [audit trail](https://complianceautomationtools.com/glossary/audit-trail/) and [the monitoring guide](https://complianceautomationtools.com/guides/continuous-monitoring-explained/).

## Where this shows up in the index

16 of 16 tools have a record of audit management in the product among the facts read on 12 Nov 2026. The [continuous monitoring criterion](https://complianceautomationtools.com/method/monitoring/) scores how each tool tests and keeps evidence current.

## Sources

- [web.archive.org/web/2025/https://pcaobus.org/oversight/standards/auditing-standards/details/AS1105](https://web.archive.org/web/2025/https://pcaobus.org/oversight/standards/auditing-standards/details/AS1105), read 12 Nov 2026
- [ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&subpart=C](https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&subpart=C), read 12 Nov 2026
- [raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json](https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json), read 12 Nov 2026
- [aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022](https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022), read 12 Nov 2026
Last reviewed 13 Nov 2026.

- [Matrix](https://complianceautomationtools.com/matrix/)
- [Integrations](https://complianceautomationtools.com/integrations/)
- [Datasets](https://complianceautomationtools.com/datasets/)
- [News](https://complianceautomationtools.com/news/)
- [FAQ](https://complianceautomationtools.com/faq/)
- [About](https://complianceautomationtools.com/about/)
- [Editorial policy](https://complianceautomationtools.com/editorial-policy/)
- [Corrections](https://complianceautomationtools.com/corrections/)
- [Contact](https://complianceautomationtools.com/contact/)
- [Privacy](https://complianceautomationtools.com/privacy/)
- [Terms](https://complianceautomationtools.com/terms/)
- [llms.txt](https://complianceautomationtools.com/llms.txt)
- [llms-full.txt](https://complianceautomationtools.com/llms-full.txt)
- [Sitemap](https://complianceautomationtools.com/sitemap.xml)
- [RSS](https://complianceautomationtools.com/feed.xml)

Compliance Automation Tools. Every platform fact carries its source and read date. Read 13 Nov 2026.

Canonical: https://complianceautomationtools.com/guides/evidence-that-survives-an-audit/
