Tracks every audit finding to closure with its owner, actions and evidence, and shows the control test result on live data so audit can see the fix working.
Today findings live in the audit report, actions in a tracker spreadsheet, and evidence in email attachments that are asked for again at retest. The external auditor asks for status by email each quarter, and the answer is assembled over a weekend.
Internal audit enters each finding with its control, its risk rating and the owners: the action owner who fixes it and the control owner who is responsible for the control. Where the finding can be expressed as a test on live data, for example manual journals posted by their preparer, purchase orders dated after their invoice or supplier bank details changed twice in a month, the app runs the test daily and shows the exception count on the finding. Action owners record progress and attach evidence, control owners confirm the fix, and audit retests and closes. The external auditor sees a read-only view of the findings, their status and their evidence, and the audit committee sees the open findings by risk and age.
| Function | Level | Does |
|---|---|---|
| Action owners | Level 1: action owner | completes the action and attaches the evidence |
| Control owners | Level 1: control owner | confirms the action closes the finding |
| Control owners | Level 2: process lead | signs findings rated high |
| Internal audit | Level 1: auditor | retests and closes the finding |
| Internal audit | Level 2: head of internal audit | signs the quarterly report to the audit committee |
| External audit | Level 1: external auditor | reads findings, status and evidence on the self-service view |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Findings | grid of findings by risk, owner, due date and status; exception count from the live test; filter by entity and process; open button |
| S02 Finding detail | control, condition, cause, risk rating, actions with owner and date, evidence uploads, comment thread; the live test and its trend chart |
| S03 Action update | progress note, percent complete, evidence upload, request a date change; submit |
| S04 Retest | auditor view: evidence, test result over the last 30 days, sample of records; close, keep open or reopen |
| S05 Auditor view | portal screen for the external auditor: findings, status, evidence and test results, read-only; export |
| S06 Committee board | open findings by risk and age, overdue actions by function, findings closed this quarter, repeat findings |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Journal line | journal lines by user, period and posting date, for journal controls | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | purchase order dates and values, for ordering controls | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier invoice | supplier invoices, their order reference and block, for payment controls | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | supplier records and bank detail changes, for master data controls | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Employee | action owners, control owners and their managers | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Supplier master | block set on duplicate supplier records, or on records whose bank details still wait for verification, when an action calls for it; the change recorded as evidence on the finding |
Start: Internal audit enters a finding on S01 at the end of an audit, or imports the findings of an audit report.
| Step | Moves when |
|---|---|
| Finding entered | control, risk and owners set; actions with dates agreed; live test configured where the data allows |
| Actions in progress | owners update monthly; evidence attached per action |
| Fix confirmed | control owner confirms; the live test shows 0 exceptions for 30 days where a test exists |
| Retested | auditor samples the evidence and the test; closes or keeps the finding open with a note |
| Reported | head of internal audit signs the quarterly view; committee board updated |
| Component | Trigger → action → outcome |
|---|---|
| tst_live_control | on schedule daily → run the finding's test on the live records → store the exception count, draw the trend on S02 |
| btn_submit_update | on click → save progress and evidence → notify the control owner when percent complete reaches 100 |
| btn_confirm_fix | on click → check that every action is complete and the test has shown 0 exceptions for 30 days → move the finding to retest, notify the auditor |
| btn_close_finding | on click → record the retest result and the sample → close the finding, update S05 and S06 |
| Step | Time limit and escalation |
|---|---|
| Action due date | the agreed date, then the owner is reminded and the control owner is copied; a second miss reaches the process lead |
| Monthly update | the last working day of each month, then findings with stale updates are marked on the board |
| Retest | 10 working days after the fix is confirmed, then the head of internal audit is told |
Names, places and figures are illustrative; the pattern is the catalogue's.
In May the internal audit team in Singapore entered 23 findings from the procure-to-pay audit, and set a live test on the one rated high: purchase orders created after the invoice date. The test showed 41 exceptions on day 1; Wei, the procurement lead and action owner, switched on the order check at 3 sites in June, and by 14 July the trend on the finding read 0 for 31 days. The control owner confirmed the fix at 16:00 that day, the auditor retested the sample the following Tuesday and closed the finding, and the external auditor read the evidence on the self-service view the same week.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Journal line read from ACDOCA (universal journal); also on SAP ECC.
Open the S/4HANA page →Journal line read from General Ledger REST: journals · BICC GL journal lines extract; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Journal line read from CONFORMED.JOURNAL_LINE · HISTORY.JOURNAL_LINES; lakehouse.
Open the Snowflake page →Journal line read from silver.journal_line · gold.journal_lines; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 6 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.