An AI-generated workpaper should arrive with proof, not polish

The last 10-20% can erase the drafting gain

A current r/Accounting discussion captured the new review problem unusually well. One practitioner said an AI drafted most of an audit workpaper and was “80-90% on point.” A reply argued that cleaning the remaining 10-20% can take longer than reviewing work prepared by someone who understood the surrounding context. The thread is practitioner evidence, not a representative survey, but the failure mechanism is concrete: plausibility is distributed across the page while consequential errors are sparse.

A reviewer who prepared a schedule knows where the difficult joins, estimates, policy choices, and manual overrides live. A reviewer who receives an AI-generated workbook sees the result but not the path taken. Smooth formatting can conceal a wrong population, a stale source, a copied formula with one broken reference, an explanation that restates a variance, or a procedure the model described but nobody performed. The work may look more complete precisely when the reviewer has less process knowledge.

That changes the control objective. “Have a human review it” is not enough. The organization needs a packet that tells the reviewer what changed, where every material number came from, which checks actually ran, what the AI inferred, which exceptions remain, and which exact artifact is being approved. Review must be designed around consequence and defect discovery, not around reading every cell with equal attention.

PCAOB AS 1215 provides a useful documentation baseline for audit contexts: purpose, source, procedures, evidence, conclusions, preparer, reviewer, and dates must be understandable to an experienced auditor. AICPA's October AI guidance adds firm approval, planned use, competence, supervision, review, and continued professional skepticism. ACRA emphasizes integrity, judgment, accountability, transparency, confidentiality, and security. These authorities have different scopes; none converts a generated workbook into evidence merely because it is polished.

Make the draft disclose how it was built

Begin with a frozen manifest. Identify the entity, period, purpose, affected accounts and assertions, workpaper hash, AI-generated version, source files and system extracts, extraction parameters, row counts, control totals, policy versions, formulas, scripts, model/tool version, prompt or workflow version, user, and timestamps. Preserve the untouched original and every later correction as a distinct version.

The AI-use record is not a confession or an automatic defect. It is provenance. It lets the reviewer identify what the model could see, whether sensitive data entered an approved environment, which transformations were generated, and whether a model or prompt change could explain a different result. Do not retain unnecessary secrets inside prompts merely to create an audit trail; use secure source references and hashes where content retention would increase risk.

Keep factual statements, calculations, management representations, assumptions, AI inferences, professional judgments, and reviewer conclusions in separate fields. A contract clause is a source fact. A calculation produced by an executed formula is an executed result. An explanation from a business owner is a representation. Whether revenue recognition criteria are met is a professional judgment. Collapsing those categories lets fluent narrative masquerade as authority.

Trace every material output and reperform outside model prose

Source-to-cell lineage should run in both directions. From an output cell, the reviewer should reach its formula, mapping, source record IDs, extraction, assumption, policy, and owner. From a source item, the reviewer should see every workpaper output it affects. Lineage must include hidden sheets, queries, external links, named ranges, manual overrides, copied formulas, and macros. Formatting is not lineage.

Use deterministic tools for footing, cross-footing, duplicates, missing keys, date boundaries, joins, currency and unit conversion, roll-forwards, aging, allocation, amortization, accrual, and control-total reconciliation. AI may draft formulas or Python, but a qualified person must inspect and execute them against authoritative inputs. Store the code or formula version, parameters, environment, input hashes, outputs, and exceptions.

assert workpaper_hash == review_manifest.workpaper_hash
assert source.row_count == source_control.row_count
assert round(source.amount.sum(), 2) == source_control.amount_total
assert population.keys.is_unique

for output in material_outputs:
    assert output.source_ids
    assert output.formula_or_rule
    recomputed = execute_approved_rule(output, frozen_sources)
    record(output.id, recomputed, output.value, recomputed - output.value)

assert all(blocking_exception.owner for blocking_exception in exceptions)
assert reviewed_artifact_hash == release_candidate_hash

These checks prove narrow things. A tie-out proves arithmetic and population agreement under the declared extraction; it does not prove the source is economically complete. A recalculation proves the formula; it does not decide whether the accounting treatment is appropriate. A hash proves artifact identity; it does not prove the artifact is correct. The packet should state each control's claim so reviewers do not promote mechanical evidence into professional judgment.

Search for counterevidence. Compare supporting records with credits, reversals, cancellations, later adjustments, alternative systems, and out-of-period events. Inspect both matched and unmatched records. Challenge a variance explanation that merely says sales increased because revenue increased. Ask which price, volume, mix, timing, acquisition, foreign-exchange, reclassification, or one-time event caused the movement and which record supports it.

Worked example: an AI-drafted bank reconciliation

Assume the AI receives a bank statement, general-ledger cash detail, prior reconciliation, mapping table, and close instructions. It produces a polished workpaper with book balance, bank balance, outstanding checks, deposits in transit, fees, reconciling items, and a conclusion that the account is reconciled. The totals foot. That is not yet enough.

The manifest first proves the statement account, entity, currency, period end, extraction times, opening balance, ledger account, source hashes, and completeness controls. The reviewer confirms that the statement is final, all pages are present, the ledger extract includes the full period and subsequent clearing window, and the prior reconciliation's unresolved items were carried forward rather than dropped.

Lineage then maps every outstanding check and deposit to source transaction IDs, dates, amounts, payees or counterparties, ledger entries, statement status, and subsequent clearing evidence. A formula copied down one row short may omit the final check while the totals still appear plausible because a different hard-coded adjustment offsets it. The review packet highlights changed formulas, hard-coded cells, unmatched records, duplicate amounts, old reconciling items, boundary dates, and items that cleared after period end.

Next, deterministic checks reperform balances, unmatched sets, age buckets, cutoff, duplicate matching, currency conversion, and subsequent clearance. The reviewer inspects every material or old item plus a targeted sample of zero, negative, round-dollar, near-duplicate, first/last-row, and AI-modified records. The reviewer also tests a random sample because the known risk list cannot anticipate every failure.

If the AI describes an old outstanding check as “timing,” that is an inference. Evidence may instead show a void, duplicate payment, stale check, posting error, or missing reversal. The exception stays open until an authorized owner supplies evidence and the reviewer records the disposition. After a correction, the system creates a new workpaper hash and reruns every affected check. Approval attaches to that exact version, not to the filename.

Sample by consequence, change, and uncertainty

Review effort should not be uniform. Inspect every output that can change a ledger, filing, tax position, regulatory report, estimate, control conclusion, management communication, or audit conclusion. Inspect all formula changes, manual overrides, new data sources, new entities, new accounts, judgmental mappings, contradictory evidence, and blocking exceptions. These are consequence-based selections, not statistical samples unless a qualified methodology says otherwise.

Add boundary and adversarial cases: first and last rows, period-end transactions, null keys, duplicates, negative and zero values, currency changes, new vendors, stale dates, large round amounts, unusual account combinations, unmatched joins, and items just below thresholds. Then add a documented random sample to look for defects outside the team's expected pattern. Do not extrapolate beyond what the selection design supports.

The reviewer should record what was re-performed and what remained outside scope. A workpaper can be approved with a disclosed limitation only when policy permits it, the limitation is understood, affected decisions are constrained, and a named authority accepts it. “AI checked the rest” is not a limitation statement.

Measure total review economics

Drafting time alone invites false productivity claims. Measure total preparer time, reviewer time, specialist time, rework cycles, material defects found, irrelevant flags, escaped defects, post-review changes, late-close impact, and control exceptions. Compare with a human-prepared baseline of similar complexity. If the AI saves two hours of preparation but adds three hours of reconstruction and exception cleanup, the workflow did not save time.

Also measure learning. Ask the preparer to explain the population, formulas, accounting treatment, and unresolved risks without reading the AI narrative. If staff can produce workpapers they cannot defend, the process has traded current speed for future control weakness. Use the tool to make provenance and review questions stronger, not to erase the apprenticeship through which accountants learn judgment.

Failure modes and release controls

A 30-day bounded pilot

1. Select one completed, medium-complexity workpaper with authoritative sources, known review notes, and no live posting authority.
2. Obtain Accounting, methodology, privacy, security, records, and system-owner approval for the exact tool, data, and retention.
3. Freeze a human-prepared baseline and an AI-assisted candidate from the same source package.
4. Build the manifest, population reconciliation, lineage map, formula inventory, AI-use record, and exception register.
5. Have an independent reviewer inspect both versions without being told which drafting method was used.
6. Require full review of high-consequence outputs plus targeted boundary, change, contradiction, and random samples.
7. Record every material defect, false alarm, missing source, broken formula, unsupported explanation, rework cycle, and escaped issue.
8. Measure total preparer, reviewer, specialist, and rework time rather than draft time alone.
9. Require preparers to explain methods, policies, and conclusions without relying on generated narrative.
10. Expand only if total effort, defect escape, documentation quality, confidentiality, and staff competence meet predeclared thresholds.

Stop the pilot if the population cannot be proven, the review packet omits lineage, sensitive data leaves approved custody, reviewers cannot reconstruct material outputs, or workflow pressure encourages approval of unresolved exceptions. A negative pilot result is useful evidence. It identifies which workpaper classes or tool permissions should remain out of scope.

Frequently asked questions

Can AI prepare an accounting workpaper?

It can draft, organize, map, and calculate in an approved environment. The result is not ready for release until authoritative inputs, formulas, source lineage, exceptions, judgments, and review evidence have been independently verified.

Why can an AI-generated workpaper take longer to review?

The reviewer did not observe how it was built. Sparse contextual errors can hide inside a mostly plausible draft, so the reviewer must reconstruct lineage, execute material checks, search for contradictions, and resolve exceptions.

Must every cell be re-performed?

Not necessarily. Review every high-consequence output and exception, then target changes, boundaries, manual overrides, new sources, judgments, unusual records, and a random sample. Applicable methodology and qualified judgment determine whether more testing is required.

Can an AI-generated formula count as evidence?

The text of a formula proves only what was proposed. A qualified person must inspect and execute it against frozen authoritative inputs, reconcile the result, retain the environment and outputs, and evaluate the accounting consequence.

Does this workflow satisfy audit standards?

No workflow page can determine compliance. PCAOB, AICPA, IAASB or other applicable standards, firm methodology, engagement facts, law, and qualified auditors control audit work. The packet is designed to make evidence and review more visible.

Sources and further reading

Sources were accessed October 28, 2026. Practitioner posts are bounded pain signals, vendor material is identified as such, and research benchmarks are not treated as production audit evidence.

• PCAOB AS 1215: Audit Documentation - purpose, source, procedures, evidence, conclusions, preparer, reviewer, and review dates.
• PCAOB: technology-assisted analysis implementation resources - sufficient appropriate evidence boundary.
• AICPA & CIMA: AI in financial reporting and auditing - October 13 public guidance scope, quality management, supervision, review, and judgment.
• ACRA Audit Practice Guidance No. 1 of 2026 - integrity, judgment, accountability, transparency, confidentiality, and security.
• r/Accounting: AI workpaper drafting and review-cost discussion - 485+ point practitioner thread at research time; not survey evidence.
• r/AustralianAccounting: current workplace use discussion - bounded practitioner signal on workpaper preparation and manual verification.
• FinancialAuditBench - preprint with synthetic workpaper completion and review tasks; task-coverage research, not production-quality proof.
• Ledge: review checklist for AI-generated accounting work - disclosed vendor perspective on workpapers, reconciliations, flux analysis, and journal entries.
• Related: AI audit risk and evidence workflow.
• Related: journal-entry review workflow.
• Related: source-document verification workflow.