01
Ingest the PBC list
Upload spreadsheet, CSV, PDF, Word, or scanned support files. Keel extracts requests, normalizes the list, and identifies the evidence needed.
Audit Ready
Keel ingests auditor request lists, drafts answers from close evidence, flags the gaps, routes controller approval, and releases support through a controlled auditor handoff.
Or explore a live demo workspace.
AI Audit Agent
Internal until approved
PBC list
Ingested
47 requests classified
Auto-drafted
Ready
31 evidence-backed responses
Gaps
Review
8 items need controller input
Auditor release
Gated
Controller approval required
Answerable
66%
Drafts staged
31
Open gaps
8
Workflow
01
Upload spreadsheet, CSV, PDF, Word, or scanned support files. Keel extracts requests, normalizes the list, and identifies the evidence needed.
02
The AI Audit Agent drafts responses from tenant-scoped Keel evidence and keeps unsupported requests in a gap queue.
03
Controllers edit, add context, attach support, and approve packages before anything becomes auditor-facing.
04
Approved evidence can be shared through the auditor portal or exported through the binder, with release events and access logging.
Capabilities
The agent is useful because it is bounded. It works from Keel evidence, preserves uncertainty, and keeps the controller in charge of every release.
Turn a messy request list into categorized support work across revenue, financial statements, reconciliations, controls, and follow-up.
Draft answers where Keel has source evidence, prior close support, revenue schedules, reconciliations, approvals, and binder context.
Identify requests that need controller judgment, missing support, external files, or a manual explanation before release.
Give invited audit-firm users a read-mostly engagement surface for released PBC support, Q&A, drillback, and binder access.
Track audit-prep baselines, cycle outcomes, avoided rework, and board-ready evidence of time returned to the finance team.
Package finalized support, responses, approvals, access history, and close evidence for the audit file.
Control posture
Controller approval is required before auditor release.
AI drafts from available evidence and flags gaps instead of inventing support.
Auditors are engagement-scoped users, not members of the customer tenant.
Released packages keep source links, review events, and handoff history.
Final binders are exported only through controlled close workflows.
Close binder
Evidence package
Export ready
Reviewed financials
P&L, balance sheet, cash flow
Exceptions
Owner, due date, resolution history
Revenue support
Schedules, invoices, tie-outs, JEs
Audit trail
Approvals, reopens, overrides
Audit prep without the scramble