SOC 2 Processing Integrity for SaaS: When to Include It
Decide whether SOC 2 Processing Integrity belongs in your SaaS report, then map inputs, processing, outputs, exceptions, and evidence for one customer workflow.

SOC 2 Processing Integrity is an optional report category for controls over the results your service produces. Consider it when customers rely on your system to accept, transform, store, or deliver information as promised and the report user wants those controls examined. A working API or a high uptime number does not prove its processing results are complete, valid, accurate, timely, and authorized. Trace one customer workflow and review the proposed category with your CPA firm before planning the evidence period.
What does SOC 2 Processing Integrity cover?
The AICPA Trust Services Criteria describe Processing Integrity in terms of complete, valid, accurate, timely, and authorized processing that meets the entity’s objectives. Security’s Common Criteria form the SOC 2 baseline; Processing Integrity adds criteria only when the category is included in the report. The five-category guide explains the broader choice.
For a SaaS product, write down the result the service actually promises. Suppose an API accepts an authorized customer’s order, calculates a total, and sends a receipt. The report question is not whether every number a customer submits is true. It is whether the scoped system has controls that support the promised handling of accepted orders, calculations, timing, and delivery. The CPA firm decides which controls and evidence to test.
| Processing question | Example check for the order API |
|---|---|
| Complete | Did every accepted order reach a recorded outcome, or a visible exception? |
| Valid | Did the API reject input outside its stated rules? |
| Accurate | Did the calculation follow the approved rules and preserve the correct result? |
| Timely | Did the system meet the stated processing or delivery window? |
| Authorized | Did the right account or service initiate and approve the action? |
These checks are examples of management’s control design, not a list of required tests or a promise that one report will verify each order.
When should a SaaS team propose the category?
Start with the scoped service, then ask the person who will use the report what decision it needs to make. A data pipeline whose outputs drive a customer’s billing or operating decisions may raise a different question from a document viewer that merely stores and displays customer content. The distinction depends on what the service does, what the company promises, and what the report user needs examined. Do not select the category from an industry label alone.
Record these facts before discussing the scope with the CPA firm:
- The customer workflow and the output the customer relies on.
- The written service commitment or system requirement for that output.
- The boundary of your processing and any provider or customer step it depends on.
- The control owner, source systems, and exception route.
- The buyer’s exact report request and any open question about the category.
If the customer only says “SOC 2,” ask whether it expects Processing Integrity in the report. A Security-only report may be what it needs, but do not say it examined the extra Processing Integrity criteria. If management proposes the category later, ask the CPA firm how the added criteria affect controls, evidence coverage, and the intended Type 2 period.
How can engineering test one processing flow?
Pick a real transaction or job, not a generic architecture diagram. For a batch import, write down the accepted input, its source count and identifiers, the transformation rules, the output count, and where rejected or retried items appear. Test normal, duplicate, invalid, late, and interrupted runs in an authorized test environment. Keep the expected result beside the actual result, the software revision, the time, and the reviewer who assessed it.
Then check the production path. A test proves a design can work; the Type 2 question also reaches how the control operated during the specified period. Choose evidence sources that can show accepted jobs, failures, retries, reconciliation, and resolution across that period. The audit populations guide explains how to produce a complete set before the CPA firm selects samples. A successful job dashboard cannot by itself show that failed jobs were found and resolved.
Use the SOC 2 evidence collection guide to record the source, covered period, retrieval steps, collector, and review. Keep raw customer inputs and outputs in approved source systems. Preserve a safe reference or redacted test artifact when the question can be answered without copying sensitive data into Git.
How is Processing Integrity different from other categories?
Availability asks whether a system is available for operation and use as committed. A service can meet its uptime target while silently dropping orders. Security addresses protection and the broader control environment; a secure API can still calculate a wrong total. Processing Integrity focuses the examination on controls over the service’s processing objectives. The same control may support several categories, but the report only addresses the categories in its stated scope.
The AICPA’s description criteria also guide management’s description of the system. If management proposes Processing Integrity, describe the actual service, data flow, commitments, requirements, providers, and boundaries accurately. Do not write a broad claim about “accurate data” when your service only validates and transforms inputs supplied by customers.
You can keep the proposed category decision, workflow map, controls, and safe evidence references in FileGRC’s Git-native GRC workspace. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. Starter records are proposals, not compliance claims. FileGRC does not run your application, verify its outputs, perform the SOC 2 examination, or decide whether evidence is sufficient. Management operates the controls, and the CPA firm makes the examination judgments.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Is Processing Integrity required for every SOC 2 report?
No. Security's Common Criteria are the baseline. Processing Integrity is an optional category that management may propose when report users need the service's processing results examined. Confirm the selected criteria with the CPA firm.
What does SOC 2 Processing Integrity mean?
It concerns whether the scoped system's processing is complete, valid, accurate, timely, and authorized to meet the service's objectives. Define those terms against the service's actual commitments and system requirements rather than a generic software checklist.
Does Processing Integrity mean a CPA firm checks every output?
No. The CPA firm examines controls for the described system and selected criteria. It sets its testing procedures and evaluates evidence; a SOC 2 report does not independently verify every customer input, transaction, or output.
Do SaaS APIs or batch jobs need Processing Integrity?
An API or batch job alone does not settle the report scope. Ask whether customers rely on its processing results, what the service promises about those results, and whether report users need that category. Map the input, processing, output, exceptions, and source evidence before deciding with the CPA firm.
How is Processing Integrity different from Availability?
Availability concerns whether a system is available for operation and use as committed. Processing Integrity concerns whether the processing that occurs meets the service's objectives for completeness, validity, accuracy, timeliness, and authorization. A service can be up while producing wrong or missing results.
Can FileGRC verify my application's processing results?
No. FileGRC can organize management's proposed criteria, controls, source systems, evidence references, and review records in JSON and Markdown with Git history. The application and its source systems perform and log the processing; the CPA firm performs the examination.