Document the Rules Before Accounting AI Agents

An agent can’t follow rules your firm hasn’t written down

An accounting firm’s rules are rarely all in one place. Some live in the engagement letter. Some are in a client’s accounting file, a checklist, or an email from a partner. Others exist because a senior bookkeeper remembers how the firm handled a similar situation three years ago.

That works, up to a point, when a person can pause, ask a colleague, and use judgment. It gets risky when an AI agent is asked to work through bookkeeping tasks or answer client questions at speed. If the firm hasn’t documented what counts as an exception, what the agent can do, and when it must stop, the agent may fill in the gaps with a plausible answer.

Plausible isn’t the same as correct. A client asking whether a payment can be classified as a business expense needs an answer grounded in the firm’s policy and the client’s situation. A close process that treats an unusual bank transaction like a routine recurring charge can create rework or a misleading set of books. An agent should not improvise where inconsistent answers can create financial or client-service liability.

The practical starting point is not a larger prompt. It’s a working record of the firm’s business rules, exceptions, and escalation steps.

Where undocumented rules show up in the work

Consider month-end close. One client’s books may require accruals for payroll and card expenses. Another may use cash-basis reporting. A third has a recurring transfer between accounts that should not be categorized as income. A bookkeeper may know all of this from experience, but an agent needs the details in a form it can check before it acts.

The same problem comes up with client queries. A client asks whether they can pay a family member through the business, how to treat a late receipt, or whether a particular expense belongs in a specific account. A firm may have a standard response, but the right next step can depend on the engagement scope, the client’s records, and whether a partner needs to review the issue.

Onboarding has its own set of judgment calls. Which documents are required before work can start? What happens if the prior accountant’s trial balance doesn’t match the tax return? Which chart-of-accounts structure is the firm’s default, and which clients need an exception? Without written rules, staff can make different choices for similar clients, or spend days waiting for someone senior to resolve a question.

This kind of inconsistency costs time even when nobody makes a serious mistake. A staff member pauses to ask a partner. The partner searches old messages. A client gets one answer from the onboarding team and another from the bookkeeper. Someone corrects the work later, often during the busiest part of the month.

For firms, those interruptions compete with client work and advisory conversations. Month-end and year-end workload spikes are predictable, but they can still crowd out higher-value work. When the rules aren’t clear, peak periods bring more questions, more rework, and more pressure on experienced staff.

Document the decision, not just the task

A useful rule is more specific than “reconcile the bank account” or “respond to client questions.” It describes what the agent should check, what it may do, and what it should do when something doesn’t fit.

For a bank reconciliation, that might mean:

• Match transactions using the firm’s approved rules for date, amount, and description.
• Apply a known mapping only when the client, account, and transaction pattern match the documented criteria.
• Don’t post an unfamiliar transaction just because its description resembles an existing one.
• Flag duplicates, missing support, and unexplained differences for staff review.
• Record the evidence used and the reason for each suggested classification.

For a client query, the rules may say the agent can confirm receipt of a document or explain a standard deadline. It can’t offer tax, legal, or financial advice outside the agreed scope. If a question depends on an individual client’s facts, a partner’s judgment, or a change in law, the agent should collect the relevant details and route the question to a named person or role.

A strong rule set also covers permissions. Can the agent draft a journal entry, or post one? Can it send a client message, or only prepare a draft? Can it update a chart of accounts? Does a threshold amount require review? A clear boundary prevents a workflow from quietly expanding beyond what the firm intended.

These decisions connect to a wider control system. The audit trail accounting firms need before agents handle client work helps show what the agent saw, what it proposed, and who approved the result. Firms should also decide how to stop an agent’s activity if a workflow behaves unexpectedly. That’s part of planning for a kill switch for accounting agents, not an admission that automation can’t work.

Build a rulebook around exceptions

Start with a workflow that already has a clear owner and a repeatable outcome. Month-end close is often a sensible choice because the tasks happen regularly and the exceptions are visible. Don’t try to write every rule in the firm at once. Capture what staff actually need to decide in one workflow, then test whether someone outside the process can follow it.

For each step, record:

1. The trigger: What starts the task, and what information must be available?
2. The standard path: What should happen when the inputs are complete and match expectations?
3. The exceptions: Which conditions require a different treatment or a pause?
4. The authority boundary: What can the agent prepare, change, or send?
5. The escalation path: Who reviews the issue, and what evidence should accompany it?
6. The record: What should be saved so the firm can understand the decision later?

Use examples from recent work. If staff repeatedly ask whether a transaction belongs in a particular account, document the client-specific mapping and its limits. If a payroll feed arrives late, record whether the close can proceed with an estimate, who approves it, and how the estimate gets replaced. If a client uploads an incomplete receipt, spell out whether the task can wait, whether the client should be contacted, and what happens if the deadline is close.

The exceptions matter as much as the standard path. If the documented process only describes the cleanest cases, the agent will reach a dead end as soon as it sees an unfamiliar transaction, a missing document, or an inconsistency between systems. The right response should usually be to stop, explain what it found, and route the issue with enough context for a person to decide.

Rules also need an owner. Assign a person or role to approve changes and review them when the firm changes its service scope, software, or internal policy. Otherwise, an agent can keep following an old process after the business has moved on.

What an agent-led close looks like

A Month-End Close Agent can pull bank, accounts payable, accounts receivable, and payroll feeds, then compare them against the firm’s documented rules for that client. It can reconcile routine items, flag variances, draft journal entries, and prepare a partner-ready close pack.

The agent doesn’t get to decide what “routine” means on its own. The firm defines which transactions it can match, what variance thresholds require review, what supporting evidence is required, and which journal entries need approval. If a payroll amount changes outside the agreed tolerance or a transaction has no reliable match, the agent records the issue and sends it to the right reviewer rather than guessing.

A person reviews the flagged items and drafts. Once approved, the close pack can show reconciliations, unresolved differences, proposed entries, and the source evidence behind the work. The partner gets a concise review queue instead of having to reconstruct the process from chat messages and spreadsheet notes.

That doesn’t mean every part of the close becomes automatic. It means the repeatable work follows a consistent path, and exceptions arrive with context. If the underlying records are inconsistent, the workflow needs a data-cleanup step before an agent can reliably act. The same principle is covered in why accounting firms should fix data before deploying agents.

A Client Onboarding Agent can use the same approach. It collects documents through a guided workflow, checks what has arrived against the client’s requirements, and identifies gaps. With the firm’s chart-of-accounts rules and prior-period information in hand, it can prepare the account structure and produce a clean opening trial balance for review.

If the prior books don’t reconcile, the agent should not hide the difference or force the balances to fit. It should show what’s missing, what doesn’t tie, and which person needs to resolve it. The onboarding team can then address the issue early, rather than discovering it when the first close is already underway.

An Advisory Insights Agent can read monthly numbers, surface three topics for discussion, and draft talking points before a partner meeting. But its rules should define what counts as a meaningful change, which data sources it can rely on, and when a question needs human interpretation. The agent prepares the conversation. The partner owns the advice.

If you want to map those boundaries to your firm’s work, Book a 60-min Omni Audit. We’ll use the session to identify a workflow, find the decisions that need documenting, and set out practical next steps.

Make the controls part of the cost case

The business case isn’t just hours saved. It’s also the cost of inconsistent work, avoidable review, and senior staff being pulled into decisions that could have been resolved through clear rules.

Rework, slow handoffs, and capacity that never reaches billable work can carry an operational cost. It isn’t a promise that an agent will recover a set amount. The result depends on where the firm spends time today and whether the workflow is suitable for automation.

A practical estimate starts with a few questions. How many staff hours go into routine close preparation each month? How often does a partner have to answer the same operational question? How much time is spent correcting inconsistent categorization or chasing missing documents? Which of those tasks can be handled under written rules, and which should stay with a person?

There’s a second cost to consider: agent usage and review. A poorly scoped workflow can create unnecessary processing, repeat work, and extra human checks. That’s why usage limits, approval points, and cost ownership belong in the design. Our guide to cost controls for agents in accounting firms covers the questions to settle before usage grows.

Capacity also changes what the firm can sell. Onboarding delays can push billable work back, and compliance work can fill the calendar before partners reach advisory conversations. Advisory work may be priced differently from compliance work, depending on the service and client. Getting routine work through a consistent process can make room for that higher-value conversation, as long as the firm has rules that preserve the partner’s role.

Use a worksheet to make the first rules concrete

The Month-End AI Close Map for Accounting Firms is a practical worksheet for listing close steps, inputs, decision points, and escalation owners. Use it with a recent month-end file. Mark which decisions staff make repeatedly, which exceptions cause delays, and where the agent would need to stop for review. You can download the close map directly.

Treat the map as a starting point, not a policy document that nobody revisits. Ask the people doing the work to test it against real examples. If two experienced staff members interpret a rule differently, clarify it before giving that step to an agent. If a rule depends on the client’s engagement terms, link it to the client record or make the workflow check those terms before proceeding.

Then trial the workflow with a limited set of clients. Review its proposed actions and escalations, note where the rulebook was unclear, and update the process. Keep a record of approvals and changes so staff can tell which rules are current. A controlled trial shows whether the workflow reduces handoffs without shifting hidden review work onto partners.

Start with the workflow that creates the most friction

Don’t begin by asking how many tasks an agent can take over. Ask which recurring decisions consume staff attention, where exceptions tend to pile up, and what the agent must never do without approval. That gives you a practical boundary for automation and a way to judge whether the work is improving.

If your firm needs help choosing that first workflow, see Omni for accounting and bookkeeping. In an Omni Audit, we map the process, identify the rules and escalation points that need to be explicit, and recommend a first step.

Before an agent handles close work or client queries, give it a process it can follow and a clear route for everything it can’t. That’s how you reduce improvisation, keep accountable people in control, and make automation useful to the firm rather than another source of exceptions. Book my Omni Audit, or review the accounting and bookkeeping audit details.