GA
Controls Agent
Tests each transaction for duplicates, anomalies, and policy breaches.
$283K1 (modeled outcome) per year in duplicate payments avoided at one design partner
Finance agent
GAAudit Agent
The Audit Agent is a governed AI agent that collects, labels, and packages audit evidence on request.
How it works
What the Audit Agent does
Reads the auditor's request list, pulls the samples and supporting documents from your systems, and assembles labeled evidence packages with lineage to source.
- 01
Connect the systems of record
Read-only connections to the ERP, subledgers, banking, document management, and email archive. The agent learns your chart of accounts, entities, and document naming.
- 02
Import the request list
Upload the PBC list or connect the audit portal. The agent maps each request to a data source and a retrieval plan, and asks for clarification where a request is ambiguous.
- 03
Collect, hash, label
Samples are pulled with the selection method recorded. Supporting documents are retrieved and hashed. Every file is labeled to the request ID with an index and lineage record.
- 04
Review and release
The controller reviews each package and releases it to the auditor. Follow-ups route back to the agent. The Registry tracks open requests, turnaround, and hours saved.
app.meridian.example/agents/audit/requests
Auditor requests · FY2026 interim
77 items deliveredavg 3.2 h
| Request | Scope | Status | Items |
|---|---|---|---|
| REQ-1187 | Q3 revenue sample · 40 invoices | Delivered | 40 / 40 |
| REQ-1186 | User access review · finance systems | Delivered | 18 / 18 |
| REQ-1184 | Fixed asset additions > $25,000 | In progress | 11 / 14 |
| REQ-1181 | Payroll register tie-out · August | Delivered | 6 / 6 |
| REQ-1179 | Bank confirmations | Waiting on third party | 2 / 5 |
The agent contract
Six terms, applied to this agent
Every Meridian agent runs under the same six terms, enforced at the Gateway below the agent. Here is what each one means for the Audit Agent.
Scoped to one workflow
Retrieves and packages evidence for the PBC list. It does not interpret the accounting.
Reads only permitted data
Read-only on financial systems, scoped to the entities, periods, and accounts in audit scope.
Every action logged
Every retrieval logged with who requested it, what was read, and when. Artifacts hashed at collection.
Consequential actions require human approval
Nothing reaches the auditor until the controller releases the package.
Measurable outcome
Open requests, turnaround, and hours saved reported per request category.
Runs on your chosen model
Model choice per workspace. Hashes and lineage do not depend on the model.
Scope
Data, actions, and approvals
What the Audit Agent reads, what it does on its own, and where a person signs.
Data it reads
- ERP general ledger and subledgers (AP, AR, fixed assets, payroll)
- Journal entry detail with preparer, approver, and support
- Bank statements and reconciliations
- Invoices, purchase orders, receipts, and contracts in document management
- Email archive for approvals and correspondence
- System access logs, control matrices, and prior-year PBC lists
Actions it takes
- Map each PBC request to a system, query, and retrieval plan
- Pull samples with the selection method and population documented
- Retrieve invoices, POs, receipts, approvals, and statements for each sample
- Hash and label every artifact to the request ID with an index
- Assemble the package with a lineage record and release it on controller approval
- Answer auditor follow-ups from the same sources and track request status
What needs approval
- Read-only access to all financial systems; the agent cannot post, edit, or delete
- Evidence is never altered; a hash is recorded at collection and verified at release
- Nothing reaches the auditor until the controller releases the package
- Access is scoped to the entities, periods, and accounts in the audit scope
- Every retrieval is logged with who requested it, what was read, and when
Outcomes
Numbers the Audit Agent is accountable for
Modeled outcomes from design-partner deployments. The Registry reports your actuals from the first week an agent is live.
~900hours
saved per audit year1
Same day
PBC request turnaround, down from a 6-day median1
−70%
auditor follow-up requests1
100%
of artifacts with hash and lineage to source
- 1.Modeled outcome from design-partner deployments. ↩
“The auditors asked for the lineage record on the first package and never asked again. We went through interim fieldwork without pulling anyone off the close.”
3days
shorter close by the second cycle at Castellan Financial1
In production at
Integrations
Systems it works with
Connected through prebuilt connectors and zero-copy warehouse access in Data Fabric. The agent acts as the user and inherits each system’s permissions on every read.
- ERP
- General ledger and subledgers
- Banking and treasury
- Document management
- Audit management and auditor portals
- Email archive
- Snowflake
Credits
What the Audit Agent costs
Included on every plan: Starter with 5,000 credits per month, Growth with 30,000, and Enterprise with custom pools. Credits are consumed per completed action, never per message. Usage beyond the plan is billed at $0.12 per credit.
| Action | Credits |
|---|---|
| Evidence package assembled and indexed | 5 |
| Sample pulled with documentation | 1 |
| Auditor follow-up answered | 1 |
Questions
Questions about the Audit Agent
Answered the way buyers ask them. Each answer is also published as structured data.
It is the use of software to retrieve, label, and package the documents and data an auditor requests, instead of accountants doing it by hand. Meridian's Audit Agent reads the request list, pulls the samples and support from your systems, and assembles packages with an index and lineage. Your controller reviews and releases them.
Design partners' auditors from three of the large firms accepted it, in part because the evidence is better documented than manual collection: every artifact has a hash, a timestamp, a source system, and a selection method. Auditors can request the lineage record. You should confirm with your engagement team before the first cycle.
No. All connections are read-only. The agent cannot post, edit, or delete anything in a financial system. It writes only to its own evidence store and, on release, to the auditor portal.
Yes. The same retrieval and packaging works for control testing evidence and internal audit requests. Paired with the Controls Agent, control test results and their evidence are packaged continuously rather than at quarter-end.
The modeled figure is about 900 hours per audit year for a mid-sized company with one external audit and quarterly reviews. Your number depends on request volume and how scattered your evidence is. The Registry reports actual hours saved per request category once you are live.
Related agents
Agents most often deployed alongside the Audit Agent, on the same data and the same approval policy.
Get started
Put the Audit Agent to work.
Start with one workflow, one approver, and one number to move. Most design partners were live in five weeks.