Custom app for signing off on-site controls
In a type II audit, the auditor picks a random day from the period under review and asks for evidence that the control was carried out that day. You can't create that evidence afterwards. It has to have been produced on the day itself, by the person who carried out the action, and that rarely happens at a desk.
Why a period is different from a moment
A type I audit looks at design and existence at a single point in time: is it in place and does it work as described. A type II audit looks at operating effectiveness over a period of at least six months. The difference seems gradual but is fundamental: with type I you show what exists, with type II you show what happened, every time it needed to happen.
The testing works on a sample. The auditor picks dates from the period and asks for evidence of each control on those days. Was the access check on the server room carried out every month? Show us the rounds for March, July and October. If one is missing, that is a finding for the whole period, not just for that one day.
In practice, things go wrong with controls that a person carries out in a physical location. Access checks, verifying a backup, reviewing a change, checking the visitor log. These are done, but the evidence only exists if someone remembers to record it afterwards. And in busy months, that doesn't happen.
How we build this
The evidence has to be created during the action itself. Anything that comes afterwards is reconstruction, and that is exactly what an auditor will not accept.
Whatever runs automatically leaves a trail by itself. The risk lies in the actions people perform that only exist if they are recorded.
Scan at the server room door, sign off at the backup check. An action that has to be confirmed two screens away gets skipped.
A monthly control that was skipped in July should stand out in July. In January it is a finding.
We pick random dates from the past period and check whether the evidence is there. What is missing then will be missing at the auditor's too.
What the app actually does
Recording at the moment of execution carries everything else. What you add on top depends on how many of your controls are manual work.
Signing off at the location of the control
A code at the server room, the archive cabinet or the control panel opens the right control. That is faster than searching, and it records the location straight away.
The execution, with its outcome
Not just that it was done, but what was observed. A tick-box record without an outcome is weak evidence in a type II examination.
The rhythm is monitored during the period
Monthly, quarterly, on every change. A missed execution surfaces within that month itself, not during preparation for the audit.
Photos where they carry the evidence
A sealed cabinet, a visitor list, a screen showing a successful restore test. For some controls, a timestamped image is the only usable evidence.
Evidence retrievable per day
The auditor asks for 14 March. The system delivers what was recorded that day, by whom and when. That is the question on which most files fall apart.
Connection to your register of controls
The controls, the objectives and the report stay in your existing environment. We retrieve them through integrations rather than creating a second list.
Who we build for
Which controls are manual work differs greatly from one organisation to another. Four situations.
Payroll and accounting firms
Here the report touches your clients' financial reporting. The controls revolve around data entry, authorisation and the four-eyes principle, and these are carried out by people. The client due diligence around it is covered under KYC and AML software.
Hosting and managed service providers
Physical access, backup checks and change management. The physical side is precisely the part that does not leave a trail by itself. The controls themselves come in through integrations with your registers.
Logistics service providers
Stock and shipments belonging to clients, which they account for in their own annual accounts. Counts and handovers take place in a warehouse, not in an office. See also the field service app.
Processors of sensitive data
Alongside the financial side there is the security side, for which SOC 2 is the usual framework. See also ISAE and SOC software.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Controls change between reporting periods. Everything to do with controls, frequencies and forms of evidence should be configurable and retained per period.
Why Appfront
Evidence is created during the action itself
We build the recording into the action itself. Anything added afterwards is reconstruction, and an auditor will see that.
A missed month stands out in that month
We monitor the rhythm during the period. By the time you are preparing for the audit, it is too late to do anything about it.
The question is about a date
We build the evidence so that it can be retrieved per day, because that is exactly how a sample works.
We rehearse the sample
Random dates from the past period, and then we see what is on file. That is the only way to know whether your file holds up.
Security and privacy
This app contains the evidence your report relies on, and that report goes to your clients' auditors. Anyone who can access it can influence your assurance. We set access per role, separate performing from reviewing, and log every access.
For this subject, tamper-proofing is not an extra but the core. A record that can be changed afterwards is not evidence; an auditor who discovers that entries were updated retroactively has found a bigger problem than a missed control. We record every execution with time and person, even when synchronisation happens later, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the ISAE app
Type I covers design and existence at a single point in time: are the controls in place and well designed. Type II covers operating effectiveness over a period of at least six months, tested with a sample from that period. Type II therefore requires evidence per execution, not one piece of evidence per control.
Because the auditor asks about a specific day. A list you compile in December about the checks in March is not evidence that those checks were carried out in March. If the reliability of the records is in doubt, the objection also becomes bigger than the original finding.
The ISAE software is about the report itself: the control objectives, the controls beneath them and the controls you assume at your clients. This app is about execution: the moment someone actually performs the control. Both rely on the same register.
Yes, with a different subject. ISAE 3402 concerns your clients' financial reporting, SOC 2 concerns information security. The audit approach with Type I and Type II is comparable, so the problem of evidence per execution applies just as much there.
It can schedule, remind and escalate, but it cannot force someone to walk to the server room. What it does prevent is a completed check going unrecorded and a missed check only being noticed at the audit.
Yes. Server rooms and archive rooms often have no coverage, and those are precisely the places where physical controls are carried out. Everything is recorded locally and synchronised later, retaining the original time.
In fact, it has to. A control that was changed in June must still be justifiable in its old form for the months before. That is why, for each execution, we record which version of the control it was performed against, rather than overwriting the control.
That depends on how many controls are manual work, the number of locations and whether there is a control register to connect to. Sign-off with rhythm monitoring is usually quick to put to use and removes the biggest risk; integrations cost more. We give a substantiated estimate after the discovery phase.
Want to run the sample check yourself?
Pick three random days from your current reporting period and request the evidence for the controls that should have been running on those days. What you can't find, your auditor won't find either. We build this as a standalone app and as part of a broader app development project.