You Were Sold a Chatbot and Told It Was an Auditor
DataSnipper just did us a favor. Thanks, friends. :)
Their new 2026 AI Report found that 87% of audit and finance professionals rank knowledge of accounting standards as the most important capability in an AI tool. General language capability came last. Two in three said the audit-specific tools they need still do not exist.
We reached this conclusion by researching the market, working alongside audit teams, and watching where general-purpose AI breaks under real engagement conditions. DataSnipper's latest survey is valuable confirmation: after four additional years of market data, the finding still holds. Audit professionals do not need a better generic writer. They need systems built around accounting standards, firm methodology, evidence, and review.
Firms are experiencing three predictable challenges with the current wave of AI agents:
1. Work appears complete before it is defensible. A chatbot can write directly into a workpaper, but it cannot reliably determine what belongs there, why it belongs there, which evidence supports it, or whether the conclusion conforms to the firm's methodology. The artifact looks finished. The test is not.
2. Review has become an expensive fact-checking exercise. When an agent cannot see risk, assertions, evidence conflicts, prior decisions, or workflow state, managers must reconstruct the reasoning after the work is done. The time saved in drafting is repurchased in review, usually at a higher billing rate.
3. Firms inherit risk without gaining real leverage. The vendor delivers fluent output, while the firm remains responsible for unsupported conclusions, missing provenance, inconsistent methodology, and decisions no one can trace. That does not reduce risk. It simply moves the risk behind a polished interface.
These failures share one cause: most so-called audit agents are wrappers around a general-purpose model, with none of the standards, methodology, engagement state, or evidence relationships required to do real testing and engagement work. The hard part was never putting words into Excel. The hard part is making those words survive review.
Deepak explained the business side in Part 1: margin disappears in the distance between doing the work and finding out the work was wrong. This is the technical side of the same problem.
Superficial Access, Superficial Work
A senior asks an agent to complete a revenue cutoff workpaper. It reads the worksheet, confirms the invoice and posting dates, and writes a clean conclusion.
On Monday, the manager asks about the shipping terms. The agent never checked the bill of lading or resolved the contradictory evidence. It completed the visible task without understanding the engagement behind it.
Access to a file is not access to methodology, risk, evidence lineage, or review authority. A polished workpaper can still be an incomplete test.
The conclusion is not the test. The traceable chain from risk to procedure to evidence to conclusion is.
The Missing System Is Context
When AI teams talk about context, they often mean how much text a model can read. That is capacity. Audit context is architecture.
A testing agent needs the firm’s methodology, the engagement’s risks and scope, the evidence behind each claim, and the workflow that governs review. Those facts must connect so the system knows what procedure is required, why the sample was selected, which source supports the result, what conflicts remain, and who can clear the conclusion.
That structure turns binder content into explicit relationships between risk, procedure, evidence, conclusion, and review status.
Without it, the agent sees a spreadsheet. With it, the system sees the engagement.
Context Isn’t Capacity. It’s Architecture.
A context-aware system compiles only the current, authorized facts needed for the decision at hand.
It uses deterministic checks for exact questions and model reasoning where judgment is required. Every claim carries its source, and every exception, change, and sign-off remains in the decision trail.
That is the difference between a model that can write about auditing and a system that can support audit procedures safely.
Context Is How Tellen Moves Review Upstream
This is where the architecture connects back to Deepak's margin argument. Read Part 1: Everyone Is Trying to Speed Up Audit. That’s Exactly the Wrong Fix.
You cannot place a manager beside every senior. Tellen moves the manager's review logic to the point of work by giving each agent the methodology, engagement state, evidence relationships, and prior decisions required to ask a narrow question at the right time.
In our revenue example, a Tellen agent assembles the risk, assertion, shipping terms, conflicting evidence, and reviewer requirements before reaching a conclusion. It flags the bill of lading conflict while the context is fresh, so the senior resolves it immediately and the manager reviews the judgment on Monday instead of reconstructing Friday’s work.
That is the margin mechanism. It only exists when context, controls, and workflow are part of the product rather than material pasted into a prompt.
Models will keep getting faster, cheaper, and more capable. Writing text into Excel will become a commodity. The durable advantage is the system surrounding the model.
DataSnipper’s survey tells us what auditors value most: knowledge of accounting standards, not general language capability. That is exactly the problem Tellen solves. Our agents combine the firm’s encoded methodology with engagement context, evidence lineage, workflow state, and prior human decisions. They separate deterministic verification from judgment, surface contradictions, preserve provenance, respect reviewer authority, and keep human sign-off exactly where it belongs.
The result is not another copilot waiting for a better prompt. It is a governed audit system that gives every procedure more context, makes every exception traceable, and shows every reviewer not only what the agent concluded, but why.
Firms were sold chatbots and told they were auditors. The distinction is now impossible to ignore.
A wrapper puts words into a workpaper. Tellen gives those words the methodology, evidence, controls, and accountability required to survive review.
That is what an audit agent is supposed to deliver.