Tenant-scoped workspaces
Customer workspaces are isolated so customer ledger and workflow data stays scoped to the right company.
Security and controls
Built for accounting data that auditors will test.
Keel is designed around controlled access, tenant-scoped workspaces, engagement-scoped auditor access, approval-gated evidence release, controlled ledger write-back, audit history, and AI that assists controllers without bypassing human approval.
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
Control model
Practical controls for close, revenue, and audit workflows.
WorkOS authentication
Signup and login run through WorkOS, with customer app and internal support surfaces separated by domain.
Engagement-scoped auditor access
External audit-firm users see released engagement evidence only. They are not added as members of the customer tenant.
Approval-gated release
PBC drafts, manual edits, support packages, and binder outputs stay internal until a controller approves the release.
Audit history
Review actions, mappings, approvals, reopens, adjustments, policy overrides, and close decisions are recorded for later review, binder support, and audit evidence.
Controlled QBO posture
Keel mirrors QBO data and only writes approved close entries through explicit controller workflows.
Watermarked handoff
Auditor-facing binder handoff, drillback, and download history are tracked so the finance team can see what was shared.
Human-approved AI
AI assists controllers with evidence-backed drafts, classifications, and suggestions. Accounting outcomes stay under human approval.
Evidence-backed close
Close binder outputs gather reviewed financials, exceptions, revenue support, approvals, and audit trail context.
Trust posture
Keel is careful about what it claims.
Keel should be evaluated as a close and consolidation system for QBO finance teams and the advisors who support them. Security and compliance claims should be reviewed against the current customer agreement, implementation, and operational controls. We do not claim autonomous accounting decisions or unsupported compliance certifications.