Invest1 publisher3 min readPublished
Section 10.37 turns an AI tool's untraceable logic into a cost tax firms pay twice
The commentary on IRS Alert 2026-19 went to fees under section 10.27(a). Kevin Boeckholt argues the provision that should reshape vendor vetting is 10.37, where reliance on output no one can trace may be unreasonable.
The Investor · Invest desk

What happened
- The IRS Office of Professional Responsibility issued Alert 2026-19, its introductory guidelines for responsible AI use in federal tax practice, on June 24, 2026.
- Most of the commentary landed on section 10.27(a), which the alert reads to mean that billing a client for manual research time AI actually replaced can be an unconscionable fee.
- Section 10.37 governs written advice, and the alert says reliance on an AI system's output may be unreasonable when that system's logic cannot be traced to a verifiable source.
- The alert also applies section 10.22's due diligence duty to mean practitioners must verify facts, citations and calculations before AI-assisted work reaches a client or the IRS.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- exposure With no trail in the tool, the error stays invisible until someone outside pulls a cited source, and by then the work is in a client file or with the IRS.
- decision Vendor selection now needs the tool to answer, for one specific piece of work, where each factual and legal claim came from and whether that source is still good law.
- constraint A firm that keeps an opaque tool has to staff the second pass, so the preparer time the licence was meant to free stays committed to re-deriving citations.
- contradiction The column says the alert adds nothing new in substance while also saying firms have not reckoned with 10.37, which means the duty they are behind on is one they already had.
The cost of an untraceable tool shows up twice in the same engagement. Kevin Boeckholt, a CPA at Accordance, wrote in CPA Practice Advisor that when a tool cannot produce a source trail, the firm builds one by hand [10][12]. That means re-deriving citations, re-checking calculations, and cross-referencing regulations the AI already claimed to have relied on [10]. He described a preparer using an opaque tool as "paying twice for the same research: once to generate it, and once to confirm it actually happened the way the output implies" [16]. Those verification hours are real hours, so a firm can bill them, while the alert reads 10.27(a) to mean it cannot bill the manual research time the tool replaced [2]. So either the client's bill does not fall, or the licence comes out of the firm's margin [2][10].
Sort the alert by provision and the weight sits on verification. Of the four sections the column works through, three go to what the practitioner can independently confirm: 10.37 on written advice, 10.22 on due diligence, 10.35 on competence. The fourth, 10.27(a), is about the invoice [14]. On competence, Boeckholt wrote that understanding how a system generates content "cannot mean reading a vendor's marketing page or trusting a benchmark score" [13].
Deloitte Australia's 237-page report for the Australian government, published in July 2025, contained invented quotes attributed to a judge and citations to academic works that did not exist, apparently generated by AI and unreviewed before delivery [5]. An outside academic checked the citations against the sources and found that some of them did not exist at all [7]. Deloitte Australia refunded part of its fee, and the column does not state the amount [6]. OPR's alert came about eleven months after the report [15].
The case for the fee provision being the live risk is about what an examiner can see. Hours not incurred sit in a firm's own time records, whereas unreasonable reliance on written advice under 10.37 needs a wrong answer plus someone motivated to trace it back to a source [3][7]. That asymmetry is why I would expect the first enforcement noise to be about invoices even if the durable exposure is the citation trail.
In my view the fee debate is downstream. Boeckholt put the standard this way: "Opacity, not cost and not billing model, is the standard tax practitioners now need to apply when they evaluate an AI tool" [11]. He argues the billing question cannot actually be answered until the traceability question is resolved [17]. Evidence against that reading would be OPR's first published AI matters arriving as fee disputes under 10.27(a), with the traceability language left as guidance nobody has to price.
What to watch
- Whether OPR's first published AI-related actions cite 10.37 reliance or 10.27(a) fees.
- Whether tax software vendors start shipping per-claim source exports that a preparer can re-check against primary law.
- Whether a US return position or tax memo surfaces with fabricated citations, and who finds it first.