The defaults are illustrative. Replace the sample entity, references, evidence and responses before including the export in an internal audit file.
| Ref | Cycle | Process area | Gap type | Gap title | Condition | Risk / impact | Evidence seen | Evidence strength | Severity | RCM action | Owner | Target date | Status | Management response | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
3 control gap item(s) were captured for ABC Private Limited for FY 2026-27.
1 high-severity gap(s) and 3 open item(s) require management attention.
3 gap(s) have an RCM handoff action; 1 item(s) need stronger evidence before final reporting.
Use this after the walkthrough memo and before finalising the RCM builder. Confirm testing coverage through the sampling plan.
A control design gap exists when the control, as designed, is not capable of preventing or detecting the relevant risk at the right point in the process. It should be separated from an operating-effectiveness failure, where the design may be adequate but execution failed.
The register should connect the gap to evidence seen during walkthrough or fieldwork, record why the design is insufficient, identify whether the RCM needs a new or revised control, and assign ownership for remediation.
This generator creates a gap register, RCM handoff, management action plan and audit committee summary. It is useful for P2P, O2C, R2R, H2R, cash, inventory, treasury, compliance, ITGC and continuous monitoring reviews.
During a P2P walkthrough, the auditor finds that bank portal approvers are not periodically reconciled to the ERP approval matrix.