Lesson objective

Produce a workflow map of a close, tax or engagement process that records the steps people actually perform, including undocumented workarounds and exception paths, rather than the steps the written procedure describes.

Plain-language explanation

Why this matters now

Most AI projects in accounting start with a tool and look for a process to put it in. The better order is the reverse: understand the process, then decide where, if anywhere, a tool belongs. You cannot control a step you do not know exists, and many of the steps that hold a close or a tax season together are written down nowhere.

Adoption is moving faster than the discipline around it. Vendor research: the Thomson Reuters Institute's 2026 AI in Professional Services Report (February 9, 2026), with more than 1,500 respondents across legal, tax and accounting, corporate functions and government in 27 countries, reports that organisation-wide generative AI use "almost doubled to 40% in 2026, compared to 22% in 2025." It also reports that "Only 18% of respondents said they knew their organization was tracking return-on-investment (ROI) of AI tools in some manner." The report comes from the research arm of a company that sells AI tax and accounting products. Its figures combine all professional-services respondents, not accounting firms alone, and the pages fetched did not state fieldwork dates or sampling method. Read together, the two figures suggest many organisations are adding AI without a way to tell whether it helped. A map is where that way begins.

Professional guidance (voluntary framework): NIST's AI Risk Management Framework (AI RMF 1.0, January 2023) says that, after instituting GOVERN outcomes, "most users of the AI RMF would start with the MAP function." It is voluntary, binds no firm or CPA, and NIST has said 1.0 is being revised. Its sequence fits accounting operations well.

No regulator, standard-setter or state board prescribes a method for mapping an accounting workflow before adding AI. The method in this module is this programme's recommendation.

A question to sit with

Your close checklist has 42 steps. If you sat beside the senior accountant for the whole close, how many steps would you see that are not on it, and which of them is the one that actually catches errors?

What goes wrong

Mapping the procedure instead of the practice. The written procedure is an input to the map, not the map. Procedures drift. People add checks after a bad month, drop steps that seem redundant, and build workarounds for systems that do not quite fit.

Missing the invisible steps. Some of the most important steps leave no trace in the procedure: the senior who scans the bank feed for the last business day because it sometimes arrives late, the manager who emails a client's controller to confirm an unusual accrual, the spreadsheet that re-keys figures between two systems.

Mapping only the happy path. An item that matches, posts and reconciles is easy to draw. The work lives in exceptions: unmatched items, missing documents, late client responses, prior-year adjustments. An AI tool that handles the normal path well but routes exceptions badly can make the process worse.

Interviewing managers, not doers. Managers describe how work should run. The people doing it describe how it does. Both views are needed, and where they differ is exactly what the map must capture.

Stopping at the team boundary. The tax team's map ends where the client's bookkeeper begins, and the close team's map ends where the audit request list starts. Many errors happen at those edges.

Drawing at the wrong level of detail. "Prepare return" is too coarse to place a control. "Click field 14" is too fine to maintain. The useful level is a step that has one owner, one main input and one output.

The practical answer

Build the map in four passes. AI Coalition Network recommendation: keep each pass on the same document so differences stay visible.

Pass What you do What you capture
1. Document review Read the written procedure, checklist and any prior walk-through notes The official steps, owners and systems
2. Walk-through Follow one real item, fictionalised for training, from arrival to final use, asking the person at each step what they do and why Actual steps, workarounds, spreadsheets, emails and re-keying
3. Exception trace Pick three items that did not go smoothly last cycle and follow each Exception paths, who decides, how long they take
4. Reconcile Mark every difference between passes 1, 2 and 3 Undocumented steps, dropped steps and informal controls

Record each step in a consistent row. The workflow map resource uses these columns.

Column What to record
Step ID and name A short verb phrase, such as "Match bank lines to ledger"
Lane The role that performs it (not a person's name, though the register names the person)
Input What arrives, from where, in what form
Action What the person does, including judgement
Output What leaves, to whom, in what form
System Where it happens: ledger, tax software, spreadsheet, email
Check or review Any control performed at this step, and by whom
Exception path What happens when the step cannot complete normally
Documented? Yes, partly, or no
Volume and time Items per cycle and typical minutes per item (Lesson 4)

Mark three kinds of informal step. They need decisions before automation.

  • Informal controls: checks nobody wrote down but that catch real errors. These must be kept, written down, or deliberately replaced.
  • Workarounds: steps that exist because a system does not fit. These may disappear with a redesign, but only if the reason disappears too.
  • Re-keying: figures copied by hand between systems. These are both error sources and candidates for automation, and each needs a tie-out.

Map across the boundary. Include at least one step on each side of every handoff to a client, another team or an outside system, even if the other side is drawn in less detail.

Keep AI out of the first draft of the map. Do not ask a tool to draw the workflow from the procedure document. It will produce a tidy version of the official steps, which is the thing the walk-through exists to test. AI can help format notes you have already gathered, and those notes must be checked against what people told you.

Connect the map to the control framework you already use. Professional guidance (voluntary framework): COSO's Internal Control — Integrated Framework (2013), which superseded the 1992 framework on December 15, 2014, has five components: Control Environment, Risk Assessment, Control Activities, Information and Communication, and Monitoring Activities. A workflow map is mostly evidence about control activities and information flows. It is voluntary, and many public companies use it as their ICFR framework.

For CPA firms, the map is also a resource question. Professional standard: the AICPA's Statement on Quality Management Standards No. 1, which binds CPA firms performing engagements under AICPA auditing, attestation or accounting and review standards and took effect December 15, 2025, includes a quality objective (paragraph 33f) that "Appropriate technological resources are obtained or developed, implemented, maintained, and used" for the firm's system of quality management and the performance of engagements. SQMS No. 1 does not mention AI in the requirements quoted. Knowing where a tool will sit in engagement work is part of judging whether it is appropriate.

Remember this

  • Map what people actually do; the written procedure is only the first pass.
  • Walk one item end to end, then trace three exceptions.
  • Mark informal controls, workarounds and re-keying; each needs a decision before automation.
  • Map at least one step on each side of every handoff.
  • No regulator prescribes a mapping method; this one is the programme's recommendation.

Accounting example

Wexford Pryce LLP is a fictional firm whose client accounting services team runs month-end close for Halvern Dental Group, a fictional practice with four clinics. The team wants AI to draft bank reconciliations and variance commentary. Manager Carla Benz first maps the close. The written checklist has 31 steps. In the walk-through, senior accountant Owen Reyes follows the September close with a fictionalised copy of the records. Carla records 38 steps. Seven are not on the checklist, including three that matter. First, Owen downloads the clinic payment processor report on the second business day because the bank feed shows card deposits net of fees, and he re-keys gross sales and fees into a spreadsheet to post them separately. Second, he emails the practice administrator about any refund above $500, because refunds often relate to insurance adjustments that belong in a different account. Third, he compares each clinic's supply expense to the prior three months and asks about any swing over 25%, a check that has caught duplicate vendor invoices twice this year. Carla then traces three exceptions from the last two closes: a missing statement for a new clinic account, a card deposit split across two days, and a refund the administrator could not explain for nine days. The reconciled map marks the re-keying as an error source needing a tie-out, the refund email and the supply-expense comparison as informal controls to be written into the procedure, and the new-account problem as an exception path with no owner. Carla's note to the operation owner says any AI drafting must keep the supply-expense comparison, cannot rely on the bank feed alone for card sales, and must route refunds above $500 to Owen.

Responsible-use warning

Do not map the checklist and call it the workflow. The written procedure is the one version of the process you already have; the walk-through exists to find what it leaves out. The steps most likely to be missing are the informal checks that actually catch errors. If a redesign removes a step nobody knew was a control, the first sign may be an error that used to be caught and now reaches the client or the financial statements.

Human-review requirement

The operation owner approves the reconciled map before AI use is designed. The responsible professional for the work, the controller for a company's own books, the signing preparer for returns or the licensed CPA for attest work, confirms that the map shows every review point they rely on and every informal control they know of. They check that exception paths have owners, that re-keying steps have tie-outs, and that the map was built from a walk-through rather than from the procedure alone.

Practical exercise

Use a fictional or fully anonymised process only.

  1. Choose one process you know well: a month-end close for a fictional entity, a fictional individual return from intake to filing, or an audit request list from issue to tick-off.
  2. Pass 1: list the steps as your written procedure or checklist describes them.
  3. Pass 2: walk one fictional item through the process from arrival to final use, and list the steps as they are actually done. Use the column headings from this lesson.
  4. Pass 3: choose three fictional exceptions typical of the process, such as a missing document or a figure that will not tie, and trace what happens to each.
  5. Pass 4: mark every step as documented, partly documented or undocumented.
  6. Label each undocumented step as an informal control, a workaround or re-keying, and write one sentence on why it exists.
  7. For each handoff to a client, another team or another system, add one step on the other side.
  8. Identify the single informal control whose loss would do the most harm, and explain what error it catches.
  9. Write a short note to the operation owner listing three conditions any AI redesign must respect, based on your map.

Knowledge check

  1. What are the four passes in building a workflow map?

    Answer guidance: Document review of the written procedure; a walk-through following one item end to end; an exception trace of three items that did not go smoothly; and reconciliation, marking every difference between the passes.

  2. What three kinds of informal step should a map mark, and why?

    Answer guidance: Informal controls, which catch real errors and must be kept, written down or deliberately replaced; workarounds, which exist because a system does not fit; and re-keying, which is an error source and a candidate for automation that needs a tie-out.

  3. Why should you not ask an AI tool to draw the workflow from the procedure document?

    Answer guidance: It would produce a tidy version of the official steps, which is exactly what the walk-through is meant to test. The undocumented steps and exception paths would be missing. AI may help format notes already gathered, checked against what people said.

  4. What do the Thomson Reuters Institute figures on adoption and ROI tracking suggest, and what are their limits?

    Answer guidance: Organisation-wide generative AI use rose to 40% in 2026 from 22% in 2025, while only 18% knew their organisation tracked ROI of AI tools, suggesting many add AI without measuring it. It is vendor research combining all professional-services respondents, with fieldwork dates and sampling not stated.

Sources and further reading