Enterprise DNA

Omni by Enterprise DNA

Enterprise DNA Resources

Thought leadership & research. Practical AI operating-system thinking for owners, operators, and teams doing real work.

220k+

Data professionals

Omni

AI agents and apps

Audit

Map the manual work

Key Findings

Lower AI agent token costs can make client follow-ups, document collection, and close preparation viable for accounting firms.

AI Agent Costs Fell 52% for Accounting
Insight ai

AI Agent Costs Fell 52% for Accounting

Sam McKay

A lower cost changes what is practical

The headline that Writer’s Palmyra X6 model can cut AI agent costs by 52% matters to accounting and bookkeeping firms for one reason.

It changes the economics of work that happens hundreds of times a month.

Most partners don’t need another tool that writes a polite email or summarizes a meeting. The real opportunity is using AI agents for work that is repetitive, rules-based, and attached to a client workflow. Think chasing a missing bank statement, checking whether payroll data arrived, asking a client to clarify an uncategorised transaction, or building the first draft of a month-end close pack.

Those jobs involve many small interactions. An agent may need to read an email thread, look up a client status, inspect a document folder, ask one targeted question, wait for a reply, then update a workflow. That means token use can add up quickly when the work runs across 50, 200, or 800 clients.

That is why falling model costs are important. A task that was technically possible but too expensive to run repeatedly can become a sensible operating decision.

The original VentureBeat report is about a vendor’s stated model performance and cost reduction. Firms shouldn’t assume every model or workflow will produce the same 52% result. But the direction is clear. Models are getting cheaper to operate, and that opens up a much larger set of back-office and client-service tasks for accounting firms.

The firms that benefit won’t be the ones that throw a chatbot at every process. They’ll identify the work that costs real staff hours, build controlled agent workflows around it, and keep a human accountable for the final financial output.

The manual work that becomes viable first

Accounting firms already know where the friction sits. It isn’t usually in one giant task. It sits in the dozens of small handoffs that surround core compliance work.

A bookkeeper sends a reminder for missing receipts. A client replies with an attachment that needs checking. Someone logs the document. Another person sees that a bank feed has stopped. A manager notices it only after the reconciliation is late. Then the team races at month-end because no one wants to tell the partner that three clients are still waiting on basic source documents.

Each individual action takes a few minutes. Across a client base, it becomes a material staffing problem.

For a firm doing $1 million to $25 million in revenue, we often see the avoidable leakage from rework, chasing, poor handoffs, and delayed billing fall somewhere in the $60,000 to $180,000 annual range. That isn’t all a direct labour saving. Part of it is capacity that can be redirected into better client conversations, faster onboarding, and work that earns a higher rate.

Three areas are especially suited to lower-cost AI agents.

Client communications that require context

Generic reminder emails aren’t hard. Contextual follow-up is.

A useful agent needs to know which documents are missing, when the client was last contacted, which deadline is approaching, whether the client has a payroll run due, and whether there is a relationship issue that means the team should step in personally.

Without an agent, staff often choose between two poor options. They send a broad reminder that gets ignored, or they manually research the client status before every follow-up. The first option produces delays. The second burns time.

An AI agent can read the workflow state, draft a targeted message, create the next task, and escalate when a client has not responded after defined checkpoints. It can do that at 8:00 a.m. every day without asking a senior bookkeeper to spend their morning in inbox triage.

Data gathering before the close

Month-end is rarely held up by complex accounting logic. It is held up by missing data.

Bank feeds disconnect. Accounts payable reports arrive in the wrong format. A director uses a personal card. Payroll journals are delayed. A client uploads a statement with no supporting receipts. The team can reconcile around some of this, but each exception needs a decision and often a question.

An agent can watch for these exceptions before the final week of the close. It can identify missing inputs, ask for the right document, capture the response, and route unresolved items to the correct person. This creates a more orderly close without pretending that AI should make accounting judgments on its own.

Onboarding work that delays billable value

New client onboarding is often a slow leak in a firm’s margins.

The engagement is signed. Then the team waits for access to accounting software, last year’s financials, bank statements, payroll records, and a usable chart of accounts. Historical clean-up expands. The client feels frustrated because they expected progress immediately. The firm has already committed staff time but cannot yet deliver predictable monthly work.

It is common for 20% to 30% of new clients to delay useful billable work by a quarter when onboarding is unstructured. The fix isn’t just another onboarding checklist. It is a workflow that actively drives the collection, checks completeness, and tells the team what is still blocking setup.

This is the kind of work where lower token costs matter. An agent can have many short exchanges with a client during onboarding. It can inspect what arrives, explain what is missing in plain language, and keep the engagement moving without requiring a staff member to recreate the same email every day.

What an accounting agent actually does

The phrase “AI agent” gets used too loosely. For an accounting firm, an agent is not a black box that takes control of the ledger.

It is a bounded operating workflow. It has a defined trigger, access to selected systems, clear tasks, approval rules, an escalation path, and an audit trail.

Our Omni ops approach is built around that practical definition. The agent does the repeatable coordination and preparation. Your team retains control over judgments, approvals, client commitments, and financial reporting.

Take the Month-End Close Agent as an example.

It starts with a schedule. At the agreed point after month-end, the agent checks that bank, AP, AR, payroll, and relevant operational feeds have arrived. It compares the actual inputs against a client-specific close checklist.

If something is missing, it sends a targeted request. If the item arrives, it logs the receipt and validates the basic format. It can flag that an AP aging report has a different column structure than normal, or that a bank feed has not refreshed for two days. That is not a final accounting conclusion. It is an early warning that stops surprises landing on the team at the end of the week.

Once data is available, the agent can support reconciliation preparation, identify unusual movements against prior periods, draft potential journal entries for review, and prepare a partner-ready close pack. The pack can show outstanding items, material variances, suggested discussion points, and links back to source evidence.

A qualified accountant still reviews and approves the result. They should. The purpose is not to remove professional oversight. It is to remove the clerical navigation that keeps qualified people away from the work clients actually value.

The Client Onboarding Agent works in a similar way. It sends a guided document request rather than a generic list. If a client says they do not have a document, the agent can explain an alternative source or flag the issue. It tracks access to the bookkeeping platform, identifies missing opening-balance information, supports chart-of-accounts setup, and produces a clean opening trial balance for review.

A client sees a clear, responsive onboarding process. Your team sees a live view of what is complete, what is blocked, and where human intervention is needed.

The Advisory Insights Agent is the next layer. After the close is reviewed, it reads the monthly numbers and surfaces three matters worth discussing. These may include gross margin movement, a rising debtor balance, cash pressure, unexpected expense patterns, or a tax-related issue that needs early attention. It drafts talking points before the partner meeting.

That work matters because advisory billable rates are commonly two to three times compliance rates. A partner doesn’t need AI to invent financial advice. They need the client context and financial signals prepared early enough to have a useful conversation.

You can see how these workflows fit together in Omni advisory. The objective is a cleaner path from transaction data to an informed client discussion.

Cheaper tokens do not mean uncontrolled automation

A 52% reduction in model cost is attractive. It isn’t a reason to hand over sensitive client data to an untested workflow.

The operating model matters more than the model name.

First, decide where the agent is allowed to act. It may be allowed to request documents, update a task status, and create a draft message. It may not be allowed to post a journal, send a client an advisory recommendation, change a payroll setting, or move a matter to completed status without approval.

Second, give it structured sources of truth. A firm should not ask an agent to infer a client’s close status from scattered email threads alone. Connect it to the workflow system, client profile, document repository, and approved data sources. Good agent performance starts with process design.

Third, build exception handling. A client who has a missing receipt is routine. A client who says they are disputing an invoice, considering a sale, or unable to make payroll is not routine. The workflow must recognise the difference and alert the right person.

Fourth, measure unit economics. Track the cost per completed onboarding task, per clean close pack, or per resolved document request. Compare it with the staff time, delay, and rework it replaces. Lower model costs make this easier, but firms still need to see the numbers in their own environment.

If you want to assess where this is realistic in your practice, Book a 60-min Omni Audit. We will look at the actual workflow, not just discuss AI in general.

Start with one workflow that repeats

The mistake I see is trying to automate the entire firm at once.

Choose one workflow with a high volume of repeated steps, clear inputs, and visible friction. Month-end document chasing is often a good first candidate. Client onboarding can be even better if the firm is growing and new engagements are regularly stuck in setup.

Map the workflow from trigger to outcome.

Write down who starts it. List every system touched. Record the information that is needed at each stage. Identify where a staff member makes a real professional judgment, and where they are simply looking up a status, sending a reminder, moving a file, or copying information between systems.

Then estimate volume. If 120 clients each require two or three document follow-ups per month, that is 240 to 360 interactions before anyone begins the close work. Even if the agent only handles the first layer and escalates exceptions, the capacity impact can be meaningful.

For a practical starting point, download the Month-End AI Close Map for Accounting Firms. It is a worksheet for mapping the close cycle, identifying bottlenecks, and separating tasks an agent can prepare from tasks your team must approve. You can also access the direct worksheet here.

The goal is not to produce a perfect process map. It is to find the first point where automation can reduce waiting time without creating risk.

The dollar case is about capacity and timing

The cost of an agent is only one number.

A stronger business case includes staff time recovered, reduced rework, faster client onboarding, fewer late closes, improved retention, and advisory opportunities that no longer get pushed out by compliance work.

Consider a 15-person bookkeeping and accounting firm with a close process that repeatedly compresses into the final week. If the team spends even 10 to 15 hours each week on status checks, follow-ups, document routing, and basic preparation across the client base, that is more than 500 hours a year. The fully loaded cost is real, but the opportunity cost is often larger.

What could a manager do with those hours instead?

They could improve review quality. They could bring forward client discussions. They could identify a client whose cash position is deteriorating before it becomes a crisis. They could onboard more clients without adding the same level of coordination overhead.

That is why the AI audit for accounting and bookkeeping should begin with operating friction and economics, not a list of AI features. A lower-cost model gives you more room to automate. It does not tell you which workflow deserves to be automated first.

A sensible next step for your firm

If your team is still handling the same document requests, inbox checks, and close-status updates manually every month, the economics are shifting in your favour.

Start with the work that is predictable and high volume. Keep financial judgment with qualified staff. Put approval gates around client-facing and ledger-changing actions. Measure what the workflow costs before and after implementation.

An Omni Audit takes 60 minutes and produces three useful outputs: a map of the operational leakage, a prioritised agent opportunity list, and a practical implementation path. No slide deck. No vague transformation roadmap.

See Omni for accounting and bookkeeping to understand the process, then Book my Omni Audit when you are ready to put real workflows and numbers on the table.