Which description best characterises an embedded audit module used to support engagement findings?
- AA standalone data-analytics tool that auditors run periodically against a copy of production data extracted after each reporting period has closed.
- BA dashboard that visualises key risk indicators for senior management using transaction data that the audit team manually re-keys into a spreadsheet each month.
- CProgram code built into an application that continuously captures or flags transactions meeting audit-defined criteria as they are processed by the system. Correct
- DA robotic process automation bot that management deploys to perform and then approve routine journal entries without any independent human oversight.
Why A is wrong: Tempting because it is a genuine CAAT approach, but it operates on extracted data after the fact rather than being embedded to capture transactions as they process.
Why B is wrong: Tempting as a monitoring aid, but it is a reporting visualisation fed by manual data entry, not code embedded in the application capturing transactions automatically.
Why C is correct: Correct: an embedded audit module lives inside the production application and selects or logs transactions in real time against criteria the auditor has defined.
Why D is wrong: Tempting because it names an automation technology, but it describes an RPA control that both performs and approves work, which is a segregation weakness, not an audit module.