Audit Support Agent
Gathers evidence for internal and external audits.
- Industry
- IT Company
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Assistant
- Approver
- Finance Controller
- Code
- FIN-14
It works through the request lists of the financial auditors and the SOC 2 and ISO 27001 auditors, and the audit requests enterprise clients send under their contracts, collecting the evidence for each item: revenue recognition samples, SOW and acceptance documents, access reviews, change records and policies. It tracks each request and shares evidence only as approved, redacting other clients' data.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the professional services automation (PSA) system: SOWs, acceptance records and revenue samples, with ledger postings and control evidence from the ticketing system..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Finance Controller with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates the audit request tracker and shares approved evidence. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The audit support procedure: request list formats, evidence sources per control, revenue recognition sample rules, client audit rights in contracts and redaction rules.
Reads from
the professional services automation (PSA) system: SOWs, acceptance records and revenue samples, with ledger postings and control evidence from the ticketing system.
Acts in
the project management tool: it updates the audit request tracker and shares approved evidence.
Hands back
A list of requests, each with id, description, owner, status (collected, in_progress or missing), evidence_refs (a list), redactions and due.
Asks a person when
Evidence is to be shared with an auditor or a client.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Personal data in evidence | redacted | How personal data appears in shared evidence. |
| Redact other clients' data | On | When on, evidence for one client's audit never shows another client's names or data. |
| Due soon (days) | 3 | Requests due within this are chased. |
| External sharing needs approval | On | When on, nothing goes to an auditor or client without the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Collect original evidence from the system of record for each request.
- Show personal data as redacted, and when on is true remove every other client's data.
- A client audit covers only what the contract's audit clause allows.
- Chase owners when a request is due within 3 days.
- When on is true, nothing leaves without the Finance Controller.
See the Audit Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.