AI-assisted internal-audit fieldwork
Keep the evidence beside the decision.
The result, its rule and its source belong together. In the example, Fail describes the configured check; reviewer confirmation is still outstanding.
Book a demoIllustrations explain the product model. Confirm your procedure, formats and review requirements during evaluation.
Inspect the amount, source and rule.
Review DEMO-0042 against the invoice page, Orders!H43 and Policy v3 §4.2. Resolve ambiguous extraction or missing evidence before concluding. Pass, Fail, Insufficient evidence, Needs human review, Not applicable and Processing error remain distinct.
Result / DEMO-0042
The amounts don’t match.
Amount mismatch. The invoice subtotal exceeds the approved purchase order by ₹5,000; tolerance ₹1.
- Expected · approved PO
- ₹1,20,000
- Actual · invoice subtotal
- ₹1,25,000
- Difference
- ₹5,000
Awaiting reviewer confirmation. Selecting an example does not approve a result.
Illustrative invoice
Aranya Office Supplies
DEMO-0042.pdf · Page 1
Invoice date: 15 April 2026 · PO-0042
Trace: page 1 · subtotal region
Original: “1,25,000.00” → normalised: ₹1,25,000
Method: illustrative extraction · confidence: 99%
Corrections: none in this fixture
Rule: Synthetic Procurement Policy v3 · §4.2
P2P amount check · v3 · Allowed tolerance ₹1
Record who decided and why.
The product model separates preparer and reviewer. Confirmations, corrections and overrides need attributable history; an override requires a reason. Selecting a website example cannot approve a result.
Group confirmed exceptions with care.
An exception concerns a record. A finding groups related confirmed exceptions into an issue with criteria, condition, cause, impact, severity, recommendation and sign-offs.
No finding has been raised from the unresolved illustrative Run. Management response, owner and target date are finding fields, not a full remediation or document-request system.
Illustrative relationship · no finding raised
A record issue needs a reviewed conclusion.
- DEMO-0042 / Amount mismatch
Invoice page 1 and PO Orders!H43; Policy v3 §4.2. Awaiting reviewer confirmation. - Preparer and reviewer assess the source.
Confirm, correct or override with an attributable reason. Uncertainty stays visible until resolved. - Only confirmed related exceptions can support a finding.
Document criteria, condition, cause, impact, severity, recommendation, management response, owner, target date and sign-offs. This example has zero confirmed exceptions and no finding.
Illustrative Run snapshot · DEMO-RUN-018
180 of 190 eligible records completed.
One check per record · Q1 FY27. Completion does not resolve human review.
- Received
- 200
- Eligible
- 190
- Execution completed
- 180
- Excluded
- 10
- Awaiting evidence
- 6
- Processing failures
- 4
- Pass157
- Fail17
- Insufficient evidence6
- Needs human review6
- Not applicable0
- Processing error4
Outcomes total 190 eligible records; excluded records are separate. Missing evidence is reported separately unless the configured completeness procedure explicitly defines its absence as a failure.
Recipe v3 · Inputs v1 · illustrative engine demo-1 / model fixture-1. Completed Run history is immutable. A new Recipe version creates new work; it does not rewrite this snapshot.
Draft / review incomplete · Finding: Not raised · 0 confirmed exceptions.
Does this example confirm current availability?
The example explains the product model with synthetic data. Confirm the procedure, formats and review behaviour you need in an evaluation; a labelled illustration does not replace product evidence.
Your next procedure
Start with the work you need to review.
Discuss the sources, rules and output your team needs. Please keep confidential audit evidence out of the enquiry form.