Audit · IIA Standards · COSO · Saudi-built

Internal audit, built around risk.

Plan, execute and report risk-based internal audits aligned with IIA Standards — with connected workflows, centralised evidence, real-time visibility and everything your audit team needs in one place.

From audit planning to remediation, turn every audit into actionable insight.

The dedicated audit product: ControlVista

GRC Vantage audit dashboard — engagements, findings by severity, remediation status and observation lifecycle
The reality in Saudi internal audit

Spreadsheet audits can't keep up with modern board expectations.

60%

Of internal audit time across the region is spent collecting and chasing evidence — not analysing it.

1 in 4

Audit findings are still tracked in standalone Excel logs that lose visibility within 90 days.

Days, not minutes

What audit committee reporting takes when workpapers, controls and findings live in different tools.

Capabilities

The full audit lifecycle, end to end

Everything internal audit needs — without forcing your team out of one tool and into another.

Risk-scored audit universe

Every auditable entity scored 1–5 on weighted risk factors, two of them derived automatically from audit history, rolled into a 0–100 composite with critical / high / medium / low tiers, coverage bands and a one-, three- and five-cycle rotation forecast.

Capacity-based annual plan

A plan suggested from the scores and the team's real man-hours, with mandatory reviews pinned first, every deferral explained, CAE approval, an Audit Committee approval gate before the year starts, and change control on every amendment.

RACM fieldwork & workpapers

Risk-and-control matrix steps from a versioned programme library, one workpaper per step, three signatures with segregation of duties, immutable version snapshots with diff, review notes, tickmarks and cross-references.

Sampling & data analytics

Attribute and monetary-unit sample sizing with reproducible selection and statistical evaluation, plus seven analytics tests over imported populations of up to 100,000 rows, locked behind a completeness gate.

Reports, opinion & remediation

A nineteen-section report, ten sections generated from the evidence, issued as versioned PDF or Word with a four-point opinion; findings then flow to management response, agreed actions, verification with segregation of duties, extensions and escalation.

Quality assurance (QAIP)

The fifteen IIA GIAS 2024 principles as a conformance catalogue, ten engagement quality criteria with a scoring rule, periodic self-assessment and external assessment records, stakeholder surveys and a quality scorecard.

Technical capabilities

What the audit module actually does, module by module

Written for the Head of Internal Audit, the IT reviewer and the external assessor. Every line is a shipped capability checked against the product code; the screens are from the demo environment.

Audit universe & risk scoring

A universe that scores itself from the evidence you already hold

Scores are weighted, two of them are derived from audit history rather than typed, and every extreme score carries a written rationale an inspector can read.

Audit universe screen with risk tiers, coverage bands and per-entity composite scores
Audit universe: tier counts, coverage bands and composite scores per entity.
  • Entity record: bilingual name, category, provisional rating, owner, audit frequency in months, last audited date, estimated hours, and a mandatory flag with its regulatory basis.
  • Composite score = sum of score × weight, divided by 5 × sum of weights, × 100, from 1–5 factor scores per cycle year; unscored factors are skipped, never counted as zero. Tiers: critical at 75 and above, high at 50, medium at 25, low below.
  • Fourteen default risk factors, all editable per organisation: six universal (regulatory exposure 1.5, financial materiality 1.5, prior findings 1.2, strategic importance 1.2, time since last audit 1.0, process complexity 1.0) plus category packs for financial operations, IT and cybersecurity, and supply chain.
  • Two factors are derived automatically: time since last audit from elapsed cycles, and prior findings from a 36-month look-back where any critical or three high findings score 5 and open findings force at least 4. Overriding a derived score, or giving any factor a 1 or a 5, requires a rationale.
  • Composite promotion rule: a real cycle updates the rating; a speculative future cycle can only rate an entity that has no real rating yet.
  • Coverage bands (overdue, due within 90 days, on track, never audited), tier-based frequencies applied with a preview before commit, and a one-, three- and five-cycle rotation forecast.
  • Twenty-six regulatory regimes available for engagement scoping, including NCA ECC, CCC and CSCC, SAMA CSF, ITGF and BCM, PDPL and NDMO, Qatar NIA and PDPPL, UAE and Bahrain regimes, ISO 27001 and 22301, NIST CSF, PCI DSS, COBIT, SOX and the IIA GIAS.
Annual plan, capacity & schedule

A plan the team can actually deliver, approved the way the committee expects

The plan is suggested from the scores and the roster's real hours, and it cannot start the year until the Audit Committee's approval is on record.

Annual audit plan with capacity, readiness checks, amendment note and engagements
Annual plan: capacity against planned hours, readiness checks and the amendment trail.
  • Readiness floor: plan suggestion is refused until at least half the universe is scored for the cycle, and marked confident at ninety percent, with a readiness strip showing universe, factors, scoring, estimates and capacity.
  • Suggestion logic: mandatory entities are pinned first and never deferred, then entities fill by tier and composite score within capacity; default hours by tier of 240, 160, 100 and 60; every deferral carries a reason, and a deferred critical entity or a selected unscored one raises a warning.
  • Capacity calculator per auditor: working days less holidays, leave, training and admin, times availability, summed across the team, less an ad-hoc reserve, at eight hours a day, applied to the plan as man-hours.
  • Approval: CAE approval stamped by the server; a sole builder approving their own plan must record an acknowledgement; moving the plan to in-progress is blocked until the Audit Committee or board approval date is recorded.
  • Change control: approval stores a plan version snapshot; adding, removing, rebudgeting or cancelling an engagement on an approved plan requires an amendment note that is logged and printed in the plan paper; completed and cancelled plans are locked.
  • Plan paper exported as PDF or Word; annual Gantt and board views of engagements and auditor availability; weekly timesheets with an approver who cannot be the submitter.
Engagements, RACM & workpapers

Fieldwork that cannot skip its own controls

Ten milestones, a gate before fieldwork starts, one workpaper per step, three signatures with segregation of duties, and a version snapshot on every signature.

Engagement fieldwork tab with RACM steps, verdicts and sign-off status
RACM fieldwork: steps with verdicts and sign-off state.
  • Engagement types: full audit, follow-up, special investigation, advisory and continuous; lifecycle planned, fieldwork, draft report, management review, final report, closed, with a controlled reopen.
  • Ten bilingual milestones from pre-announcement to closing-meeting minutes, four of them derived from events; the planning memo, RCM approval and final report need an approver who is not the person who completed them.
  • Fieldwork gate: entity, objective and scope, at least one in-scope step, RCM approved, planning memo approved, lead and budget set; a manager may override with a logged reason.
  • RACM steps carry reference, risk, control (from the control library or free text), test procedure, assertion and clause reference; scoping a step out needs a written reason; steps import and export as Excel; programmes come from a versioned library where only approved versions can be applied, and engagements roll forward steps without results.
  • Workpapers: exactly one per step; preparer, reviewer and approver signatures with segregation of duties, collapsible only with a recorded reason; open review notes block sign-off; every signature writes an immutable version with a diff view; a submitted step is locked and edits are protected by optimistic concurrency.
  • Eight bilingual tickmarks (vouched, traced, recalculated, footed, cross-footed, inspected, confirmed, exception) applied to evidence; @WP and @PBC cross-references resolved inline; a review queue lists papers awaiting the caller's signature, oldest first.
  • Prepared-by-client requests with numbered lines, per-line evidence, accept, reject or not-applicable decisions with notes, a derived header status, overdue flips and CSV export; the auditee inbox shows their findings, requests and actions in one place.
  • Engagement binder as a ZIP: issued report versions, per-step PDFs, evidence re-hashed and verified against the stored SHA-256, findings and requests as CSV, a manifest and SHA256SUMS.
Sampling & data analytics

Statistics the external auditor will accept

Sample sizes are computed, selections are reproducible, evaluations follow the textbook, and a population cannot be tested until its completeness is asserted and locked.

Data analytics screen listing imported populations
Imported populations ready for duplicate, gap, Benford, threshold, date and matching tests.
  • Attribute sampling: exact binomial sample size at 90, 95 or 99 percent confidence from tolerable and expected deviation rates with finite-population correction; evaluation by Clopper-Pearson upper deviation limit.
  • Monetary-unit sampling: size and interval from population value, tolerable and expected misstatement; evaluation projects misstatement by tainting with the top stratum handled separately.
  • Selection methods random, systematic, monetary-unit, judgmental (reason required) and full population; selections are seeded so they can be reproduced; an untested item is never counted as clean; results export to CSV with a provenance header and outcomes re-import.
  • Analytics over imported CSV or Excel populations of up to 100,000 rows and 150 columns, hashed with SHA-256 on upload; a completeness assertion (record count, control total or owner confirmation) is recorded before the dataset locks, and only locked datasets can be tested.
  • Seven tests: duplicates (exact or normalised, up to eight columns), sequence gaps, Benford first or second digit with chi-square on 500 rows or more, thresholds including just-below and round amounts, date tests for weekend, holiday, outside-period and backdated entries on an organisation calendar with a Friday-Saturday default, cross-dataset match and anti-match, and stratification.
  • Exceptions are stored up to 10,000 per run with the true count always reported, dispositioned as unexplained, explained, error or raise-finding, and attached to a working paper as evidence; a finding can only be raised from a step whose verdict is exception.
Findings, reports & opinion

A report that is mostly generated, so it cannot drift from the evidence

Ten of the nineteen sections are produced from the engagement data, the opinion is a four-point scale, and issuing freezes a version that pins the exact workpapers behind it.

Issued audit report with version, audit opinion and executive summary
Issued report: version stamp, four-point opinion and executive summary.
  • Finding fields in English and Arabic: title, condition, criteria, cause, effect and recommendation, with severity (critical, high, medium, low, observation), owner, implementor, due date and verifier; stages run draft observation, confirmed, in report, management response, agreed, remediating, verified closed, with dropped and accepted as terminal states.
  • Management response thread with three kinds of entry; an agreed action converts to a tracked audit action; auditees can post responses and nothing else.
  • Nineteen report sections in fixed order: nine narrative (executive summary, key themes, matters for board attention, background, objectives, scope, approach, basis for opinion, conclusion) and ten generated from data (assurance at a glance, scope limitations, risk and control assessment, detailed findings, control strengths, management action plan, criteria and regulatory coverage, status of previous findings, audit steps performed, evidence register).
  • Issuing requires a CAE-level role, an opinion and every workpaper approved, and is refused while any finding is still undecided; issue writes version N and pins the workpaper version IDs; final stamps it; reopening creates N+1. Export as PDF or Word for the live report or any issued version.
  • Four-point opinion scale: satisfactory, generally satisfactory, needs improvement, unsatisfactory.
  • Findings follow the report: issuing moves in-report findings to management response in the same transaction and notifies their owners; closing an engagement requires an issued report unless it is advisory.
  • AI drafting, off by default and consent-gated per organisation: a bilingual finding draft with suggested severity from a working paper, and narrative report sections with a suggested opinion. Generated sections are never touched by the model and drafts are never persisted.
Remediation & follow-up

Actions that close only when someone independent says so

Owners complete, verifiers verify, extensions are decided by a third person, and the daily sweep keeps the overdue list honest.

Remediation tracker with action status counts, owners and extended due dates
Remediation tracker: status counts, owners, extended due dates and ageing.
  • Action record: owner, due date with the original due date kept, evidence as file or link, completion note, verify or reject with a note; the verifier cannot be the owner, and a rejection needs a reason.
  • Due-date discipline: a date can be changed only while the action is open and has never been extended; after that, an extension must be requested and decided by someone who is neither the owner nor the requester.
  • Finding closure: when every action is verified the finding is flagged ready to close and the auditor closes it; the finding owner cannot verify-close their own finding.
  • Daily sweep on a schedule: overdue flips, due-soon reminders at a configurable lead, per-owner overdue digests, and escalation to the engagement lead after a configurable number of days (default seven).
  • Sixteen audit notification events delivered in-app and by bilingual email with per-user channel preferences: finding released, response requested, sent back and ready to close; action assigned, completed, rejected, extension requested, extension decided, due soon, overdue digest and escalated; request assigned, submitted, decided and due soon.
  • Cross-engagement views: the issue repository across years with stage and severity, and a CAE-wide remediation tracker with ageing, overdue and extension status.
Quality (QAIP) & committee reporting

Conformance you can show, not assert

The fifteen principles of the 2024 Standards are a scored catalogue, every engagement gets a ten-criterion quality review, and the committee sees the rollup.

Audit Committee report with KPI tiles, engagement pipeline and opinions issued
Audit Committee report: KPI tiles, pipeline, opinions and findings posture.
  • Fifteen IIA GIAS 2024 principles (domains II to V) seeded as a conformance catalogue rated generally conforms, partially conforms, does not conform or not applicable; organisations can add GCC overlay items.
  • Assessment types: ongoing, periodic self-assessment and external; an external assessment sets the next due date five years out and records assessor independence, and the conformance statement is refused unless the overall rating is generally conforms and the assessor was independent.
  • Ten engagement quality criteria (objective and scope, risk-based programme, supervision, workpaper support, findings evidence, report quality, management responses, action plans, timeliness, budget), scored met 3, partial 2, not met 0 with not-applicable excluded; ninety percent is satisfactory, seventy is needs improvement, one not-met caps the result and two make it unsatisfactory; the band stays provisional until every criterion is rated.
  • Stakeholder surveys from configurable templates after engagements and periodically, a quality scorecard (delivery on time, hours, findings and actions, QA reviews, satisfaction, external assessment due date), and a dedicated quality reviewer role.
  • Audit Committee report: open findings, critical and high, on-time remediation, active engagements, reports issued and QAIP conformance, with engagement pipeline, opinion mix, findings posture and an attention list, printable to PDF from the browser.
Governance, security & operations

Built for a regulated organisation's control environment

Two permission axes, a change log on every transition, hashed evidence, directory login and AI that stays off until you turn it on.

  • Two permission axes: organisation roles (viewer sees, analyst performs fieldwork, manager manages and issues reports, admin administers, plus a quality reviewer) and per-engagement team roles (lead auditor, auditor, reviewer, observer) that cap what a person can sign.
  • Every state transition goes through one function that writes the change log (old and new values, user, IP, user agent) in the same database transaction as the change; each finding shows its activity feed.
  • Evidence integrity: SHA-256 computed on upload for workpaper, action, request and milestone evidence and for analytics datasets; the engagement binder re-hashes and verifies every file when it is built.
  • Sign-in with email and password or your Active Directory and LDAP, with automatic provisioning; password reset and invitations included.
  • AI assistance requires per-organisation consent for the audit module and is off by default; it can run on a local model inside your environment before any external provider, and every call is logged.
  • Arabic and English: the engagement workspace, fieldwork, requests, findings, report tab, remediation, analytics, timesheets and settings are translated; the dashboard, universe, plan builder, quality screens and committee report, and the bodies of exported reports, are English today.
  • Deployable on-premise or in a private cloud; around 650 automated unit and API tests cover the audit module alone.
Audit lifecycle

From audit universe to closed finding — in one platform.

01Universe

Build and risk-rank the audit universe.

02Plan

Generate the annual risk-based plan.

03Execute

Workpapers, sampling, reviewer signoff.

04Report

Findings, recommendations, committee packs.

05Track

Remediate, escalate, close the loop.

Regulatory regimes available for engagement scoping, printed in the report’s coverage section
IIA GIAS 2024NCA ECCNCA CCCNCA CSCCSAMA CSFSAMA ITGFSAMA BCMPDPLNDMOISO 27001ISO 22301NIST CSFPCI DSSCOBITSOX ICFRCOSO
For the Head of Internal Audit

You're not buying a tool. You're buying defensible, audit-committee-grade assurance.

GRC Vantage gives Chief Audit Executives the workflow, evidence trail and reporting their boards expect — without spreadsheets, version chaos or dependence on second-line teams to feed them data.

  • Independent workpapers, separate from first- and second-line
  • Independent control library, programme library and workpapers under third-line permissions
  • Audit Committee report rolled up from live findings, opinions and remediation data
  • Quality assurance reviews tracked against IIA Standards
3×

More engagements completed per fiscal year for the average GRC Vantage audit customer versus spreadsheet-based programmes.

2 hours

Typical time to assemble a full audit committee pack, down from 5 working days.

Two products, one platform

Compliance is not Audit.

Saudi GRC vendors love to blur these. We don't. The CISO and the Head of Internal Audit need different tools, different workflows and different evidence trails — and GRC Vantage gives you both inside the same platform.

Compliance module

For the CISO and second-line teams

Framework conformance against SAMA CSF, NCA ECC, ISO 27001, SOC 2, PCI DSS and PDPL.

Explore Compliance
Audit module · you are here

For the Head of Internal Audit and the third line

Independent assurance over the controls compliance is running. Workpapers, sampling, findings, committee reporting — IIA-aligned and audit-committee defensible.

Reference

Frequently asked questions

Is GRC Vantage's audit module aligned to IIA Standards?
Yes, and the alignment is visible in the product rather than claimed on a slide: the fifteen principles of the IIA Global Internal Audit Standards 2024 are a scored conformance catalogue, every engagement carries a ten-criterion quality review, planning is risk-based from a weighted universe, workpapers take three signatures with segregation of duties, and reports carry a four-point opinion. There is no internal audit charter or competency register in the product.
How is this different from your Compliance module?
Compliance is built for the CISO and second-line teams evidencing framework conformance. Audit Management is built for the third line: an independent universe, plan, workpapers and findings with their own permissions and sign-offs. Regulatory regimes such as NCA ECC, SAMA CSF and PDPL are available for scoping an engagement and are printed in the report's regulatory coverage section; the audit module keeps its own control library and workpapers rather than reading the compliance module's records.
Which audit types does the platform support?
Full audits, follow-up reviews, special investigations, advisory engagements and continuous auditing. Work programmes come from a versioned programme library you build or import from Excel; the demo environment ships with programmes for a SAMA-regulated lender, and twenty-six GCC and international regulatory regimes are available for engagement scoping.
Does it integrate with our existing ERP, GL or operational systems?
Not through connectors or an API today. Populations for data analytics and sampling are imported as CSV or Excel (up to 100,000 rows), hashed on upload and locked behind a completeness assertion before testing. Evidence attaches as files or links. A public API is on the roadmap; ask us for the date.
Is the platform usable outside banking — government, healthcare, energy, telco?
Yes. The universe, factors, programmes, quality criteria and regulatory regimes are all configurable per organisation, and the method (risk-scored universe, capacity-based plan, RACM fieldwork, three-signature workpapers, QAIP) is sector-neutral. The SAMA-specific elements are configuration, not a constraint.
Can we host the platform inside Saudi Arabia?
Deployment on-premise or in a private cloud is available and is confirmed per engagement in writing, including where the data sits. Ask us before the demo and we will answer in the proposal rather than on this page.
Is the audit module available in Arabic?
Partly. The engagement workspace, fieldwork, requests, findings, report tab, remediation, analytics and timesheets are translated, and finding fields are captured in both languages. The dashboard, universe, plan builder, quality screens and Audit Committee report, and the bodies of exported reports, are in English today. Full Arabic coverage is the next tier of work; ask us for the date.
Get started

Bring your internal audit function out of Excel.

See GRC Vantage's audit module live with your audit universe. Demos delivered in English or Arabic by our Riyadh team.