The SOC 2 Processing Integrity Default Findings Engine is a requirement-aware template layer for AICPA Trust Services Criteria - Processing Integrity. It helps a team define consistent starting language for recurring findings while the normal project remains the source of truth for scope, evidence, ownership, remediation progress, validation, and reports.
Library and standards scope
Processing Integrity concerns whether system processing is complete, valid, accurate, timely, and authorized in line with the entity objectives. It is especially relevant to transaction, billing, reporting, data-pipeline, and other services whose commitments include the quality of processing results.
Global, local, and project layers
- Global defaults are standards-based templates published by voiqq platform owners for a system Library.
- Local defaults belong to the signed-in workspace administrator and can override editable wording without changing the global source.
- A project finding receives copied template values and then becomes an independent record.
- Later global changes do not silently rewrite a local override or a finding already created in a project.
- Status is Open and validation is Pending when the reusable default is applied, unless an authorized project workflow later changes them.
Fields and canonical mapping
Each template is owned by a canonical processing-integrity criterion in the SOC 2 Processing Integrity Library. The reusable record contains a stable identifier, summary, description, remediation guidance, severity key, mapped values, source Library, and display order. The visible wording can be edited locally, while the background requirement identity continues to support filters, reports, imports, and New Finding suggestions.
Create or customize a default
- Define the processing objectives and service commitments before authoring defaults.
- Choose the exact Processing Integrity criterion in the local engine.
- Describe the recurring failure in terms of completeness, validity, accuracy, timeliness, or authorization.
- Add evidence expectations for populations, samples, reconciliations, or exception handling.
- Write remediation around the control outcome and review responsibility.
- Add transaction samples, dates, systems, and exception results only to the project record.
Writing rules for reusable findings
Write the summary as a concise statement of the recurring failure. Use the description to explain the expected behavior, likely impact, or control concern in neutral language. Use remediation to describe the desired outcome rather than a patch tied to one framework or customer. Store actual results, reproduction steps, affected assets, evidence, people, dates, measurements, samples, and environment details in the project finding.
Suitable template subjects
- Reconciliation exceptions remain unresolved beyond the defined processing target.
- Input validation does not prevent incomplete or invalid transactions from entering processing.
- Manual adjustments lack authorization or an independent review record.
- Failed or duplicate processing is not detected and corrected promptly.
- Output completeness and accuracy checks are not evidenced for the in-scope period.
Use a default in a project
Open New Finding inside a project configured with SOC 2 Processing Integrity. Choose Template mode or select a prepared template after choosing the applicable processing-integrity criterion. voiqq prefills the reusable values. Review every field, add the real evidence and context, and save the finding. Comments, attachments, assignments, history, validation, sharing, exports, and reports then use the same normal project workflow.
Accuracy and safety checks
- Do not put transaction data or customer identifiers in a default.
- Separate one processing exception from a control-pattern finding.
- Keep the evidence period and sample in the project.
- Check that remediation addresses the processing objective.
- Validate with a new sample when appropriate.