Accounting firm field guide

Human review vs. autonomous AI bookkeeping.

The useful question is not whether AI should be autonomous or supervised everywhere. It is which bookkeeping actions have enough evidence, narrow enough scope, safe enough reversibility, and clear enough proof to run routinely—and which must stop for judgment.

By LedgerHQ Editorial TeamReviewed by LedgerHQ Product Team11 min read
Practical takeaway

Grant authority by action and condition, not by broad confidence in the model. Keep missing evidence, warnings, destructive changes, external sends, and policy decisions on a human path.

Think in levels of authority

AI bookkeeping can range from read-only explanation to suggestions, prepared actions, confirmed execution, and bounded routine execution. A firm can use different levels for different duties and companies.

For example, the agent may freely identify missing statements, prepare coding with evidence, require review before posting warnings, and require explicit confirmation before sending a company-owner message.

  • Explain
  • Suggest
  • Prepare
  • Execute after confirmation
  • Execute within bounded standing authority

Evaluate evidence, scope, reversibility, and impact

A repeat software subscription with a narrow rule and stable history has stronger evidence than a new five-figure transfer with an ambiguous memo. Correcting a draft is safer than voiding a posted entry. An internal preparation is safer than an external message or billing change.

These characteristics should drive the authority floor. The model's self-reported confidence is not enough.

  • Evidence completeness
  • Number of records and companies
  • Reversibility
  • External or financial impact
  • Period and policy sensitivity

Keep humans on judgment and accountability

People should remain responsible for firm policy, unusual economic substance, incomplete business purpose, material estimates, fraud concerns, owner disputes, sensitive documents, and final assurance about the books.

Human review should be designed, not symbolic. The reviewer needs the source evidence, proposed action, explanation, warning, and expected accounting effect.

  • Policy and materiality
  • Incomplete or conflicting evidence
  • Fraud and unusual activity
  • Final close and delivery judgment

Use bounded autonomy for repeatable work

Bounded autonomy works when the duty is explicit, the inputs are observable, the conditions are validated, the scope is narrow, and the result is recorded. Rules are one form of bounded automation; an AI agent can add context gathering while remaining inside the same safeguards.

The firm should be able to pause the agent, review recent actions, and reduce authority without rebuilding the workflow.

  • Defined duty
  • Typed tool inputs
  • Hard validation and warning stops
  • Durable activity evidence
  • Pause and authority controls

Review authority as the system changes

Authority is not a one-time setup. New companies, changed staff, model changes, new tools, unusual transaction periods, and prior errors can all change the appropriate boundary.

Review outcomes and near misses. Expand authority only when the clean path has evidence; narrow it when exceptions reveal that a condition is not captured.

  • Periodic permission review
  • Exception and override analysis
  • Model and tool change review
  • Company-specific overrides

Related reading

Put the workflow into practice

LedgerHQ keeps the accounting system and AI bookkeeper in one supervised workspace.