App catalogue People and compliance

Audit finding remediation

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.

HIERARCHY · AUDIT FINDING REMEDIATIONAction ownersL1: action ownerscreen · usersControl ownersL1: control ownerscreen · usersL2: process leadscreen · usersInternal auditL1: auditorscreen · usersL2: head of internal auditscreen · usersExternal auditL1: external auditorscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaInternal audit enters a finding on S01 at the end of an audit, or imports the findings of an audit report.
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
6 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
Action ownersLevel 1: action ownercompletes the action and attaches the evidence
Control ownersLevel 1: control ownerconfirms the action closes the finding
Control ownersLevel 2: process leadsigns findings rated high
Internal auditLevel 1: auditorretests and closes the finding
Internal auditLevel 2: head of internal auditsigns the quarterly report to the audit committee
External auditLevel 1: external auditorreads findings, status and evidence on the self-service view
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Findingsgrid of findings by risk, owner, due date and status; exception count from the live test; filter by entity and process; open button
S02 Finding detailcontrol, condition, cause, risk rating, actions with owner and date, evidence uploads, comment thread; the live test and its trend chart
S03 Action updateprogress note, percent complete, evidence upload, request a date change; submit
S04 Retestauditor view: evidence, test result over the last 30 days, sample of records; close, keep open or reopen
S05 Auditor viewportal screen for the external auditor: findings, status, evidence and test results, read-only; export
S06 Committee boardopen findings by risk and age, overdue actions by function, findings closed this quarter, repeat findings
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Journal linejournal lines by user, period and posting date, for journal controlsS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order linepurchase order dates and values, for ordering controlsS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier invoicesupplier invoices, their order reference and block, for payment controlsS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier mastersupplier records and bank detail changes, for master data controlsS/4HANA · Oracle Fusion · Snowflake · Databricks
Employeeaction owners, control owners and their managersS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Supplier masterblock 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
The flow

From the trigger to the last write

THE FLOW · AUDIT FINDING REMEDIATION1Finding enteredcontrol, risk and ownersset; actions with datesagreed; live testconfigured where the dataallows2Actions in progressowners update monthly;evidence attached peraction3Fix confirmedcontrol owner confirms; thelive test shows 0exceptions for 30 dayswhere a test exists4Retestedauditor samples theevidence and the test;closes or keeps the findingopen with a note5Reportedhead of internal auditsigns the quarterly view;committee board updated
Each step and the criterion that moves it.

Start: Internal audit enters a finding on S01 at the end of an audit, or imports the findings of an audit report.

StepMoves when
Finding enteredcontrol, risk and owners set; actions with dates agreed; live test configured where the data allows
Actions in progressowners update monthly; evidence attached per action
Fix confirmedcontrol owner confirms; the live test shows 0 exceptions for 30 days where a test exists
Retestedauditor samples the evidence and the test; closes or keeps the finding open with a note
Reportedhead of internal audit signs the quarterly view; committee board updated
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
tst_live_controlon schedule daily → run the finding's test on the live records → store the exception count, draw the trend on S02
btn_submit_updateon click → save progress and evidence → notify the control owner when percent complete reaches 100
btn_confirm_fixon 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_findingon click → record the retest result and the sample → close the finding, update S05 and S06

Clocks

StepTime limit and escalation
Action due datethe agreed date, then the owner is reminded and the control owner is copied; a second miss reaches the process lead
Monthly updatethe last working day of each month, then findings with stale updates are marked on the board
Retest10 working days after the fix is confirmed, then the head of internal audit is told

Measures

open findings by risk and ageactions completed on timefindings closed at first retestexception count on live testsrepeat findings
A day with the app

Illustrative

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.

illustrative scenario · Audit finding remediation
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

FindingA weakness an audit reports, with the control it relates to, a risk rating and the actions agreed to fix it.
Control ownerThe person responsible for the control working; the action owner does the fixing.
Live testA criterion on live records that counts the exceptions a control is there to catch, run daily.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.