Lesson objective
Design an onboarding independence check that surfaces hosting, information systems and tax services issues for an attest client and routes each to a named partner without concluding on it.
Plain-language explanation
Why this matters now
Firms increasingly sell AI-related services: building a model into a client's close process, hosting a client's data in the firm's AI environment, configuring a client's accounting system with AI features. When that client is also an attest client, those services can threaten independence. An onboarding orchestration is well placed to notice the combination, because it sees every new service request against the firm's client list. It is badly placed to decide what the combination means.
Level 4 examined these interpretations in depth. This lesson asks what an automated check should surface, and why it stops at surfacing.
- Professional standard (AICPA Code of Professional Conduct, Hosting Services, 1.295.143; binds AICPA members performing attest engagements under the Independence Rule, 1.200.001): hosting services include acting as sole host of an attest client's information system, taking custody of or storing its data or records, or providing electronic security or back-up services for them (1.295.143.01). Providing hosting services to an attest client impairs independence, and safeguards cannot reduce the threat to an acceptable level (1.295.143.02).
- Professional standard (AICPA Code, Information Systems Services, 1.295.145; same binding scope; revised June 2019 and effective 1 January 2023): it applies to all attest engagements, including those whose subject matter is not financial statements (1.295.145.02). A financial information system includes a tool that calculates results, unless it only performs discrete calculations and the client accepts responsibility for inputs and assumptions and understands the results (1.295.145.03a). Designing or developing an attest client's financial information system impairs independence, and safeguards cannot fix it (1.295.145.05). Some commercial off-the-shelf implementation services may be safeguarded; others create threats that cannot be (1.295.145.08).
- Professional guidance (Journal of Accountancy, 15 July 2026, reporting on the AICPA Professional Ethics Executive Committee): PEEC adopted revisions to the Tax Services interpretation (ET 1.295.160) in May 2026. The revised interpretation is effective 15 January 2027, with early implementation permitted, and keeps a principles-based approach to self-review and advocacy threats when members provide tax services to attest clients. The article does not mention AI.
Three limits frame the whole lesson. The interpretations do not mention AI by name, although AICPA ethics staff have written that developing or hosting an AI system for an attest client can raise independence concerns under these rules. Whether a particular AI engagement impairs independence depends on the facts, so no automation, and no lesson, can give a blanket answer. And PCAOB and SEC independence rules also apply to issuer audits and are not covered here; an issuer audit client needs its own analysis.
A question to sit with
If your onboarding flow had accepted, without a person looking, a request to host an audit client's close data in the firm's AI environment, when would anyone have noticed?
What goes wrong
Services are onboarded one at a time. The advisory team onboards "AI close assistant configuration" for a company. Nobody links it to the audit engagement the firm already has for the same company, because the requests came through different doors.
The check concludes. A rule in the workflow marks a service "independence cleared" because it matched a keyword list. Keyword matching cannot weigh facts, and the Code's answer depends on them.
The check only looks at names. The attest client is "Northgate Holdings"; the advisory request comes from "Northgate Operations LLC", a subsidiary. A name match misses it.
Hosting hides in the service description. "We will keep your documents in our AI workspace so the assistant can answer questions" sounds like convenience. It may be custody or storage of the client's data or records.
The pending change is forgotten. Tax services to attest clients will be assessed under a revised interpretation from 15 January 2027. Engagements accepted now may run past that date.
The practical answer
Check every new service against every attest relationship. The orchestration compares each new service request with the firm's list of attest clients and their related entities, using the entity relationships the firm holds, not names alone. Any overlap raises a flag.
Ask structured questions, not keyword matches. For each flagged service, the orchestration collects answers to questions like these and places them in the partner's queue.
| Question the flow asks | Why a partner needs it | Interpretation it points to |
|---|---|---|
| Will the firm host, store or take custody of the client's data or records, or provide back-up or security for them? | Possible hosting service | 1.295.143 |
| Will the firm design or develop a system or tool that forms part of the client's financial information system? | Possible design or development | 1.295.145.05 |
| Does any tool calculate results the client relies on, and does the client accept responsibility for inputs and assumptions and understand the results? | Whether it is part of an FIS | 1.295.145.03a |
| Is the work implementation of a commercial off-the-shelf product, and which tasks exactly? | Some may be safeguarded, some not | 1.295.145.08 |
| Is the attest engagement on subject matter other than financial statements? | The interpretation still applies | 1.295.145.02 |
| Does the firm also provide tax services, and will the engagement run past 15 January 2027? | Revised Tax Services interpretation | ET 1.295.160 (revised) |
| Is the client an issuer or otherwise subject to PCAOB or SEC rules? | Separate rules apply | Outside this lesson |
Route every flag to a named partner. The partner responsible for the attest relationship, or the firm's independence lead, decides. The decision, the facts relied on and the reasoning are recorded. Level 4's independence conclusion record is the right format.
Hold dependent steps. No engagement letter for the new service goes out, and no portal access for it is granted, until the partner has recorded a decision.
Treat the tax services change as a dated flag. Until 15 January 2027, the flow notes the effective date on every tax service for an attest client whose engagement will extend past it, so the partner can decide whether to apply the revised interpretation early, as permitted, or plan the transition.
Keep the check current. The flow's questions are a firm document with an owner and a review date. When the interpretations change, the questions change first.
Why a keyword list fails here
"Host", "store" and "build" do not appear in every service description that involves those acts, and they appear in many that do not. The Code turns on what the firm will actually do and whether the client takes responsibility for it. Only structured facts, read by a person, can support that judgment.
Remember this
- The orchestration compares every new service with every attest relationship, using entity relationships, not names.
- Hosting services (1.295.143) and designing or developing an FIS (1.295.145.05) impair independence and cannot be safeguarded.
- The interpretations do not name AI, and whether a given AI engagement impairs independence depends on the facts.
- The revised Tax Services interpretation is effective 15 January 2027, with early implementation permitted.
- The flow surfaces facts and questions; a named partner decides and records the conclusion.
Accounting example
Brightwater Advisory LLP is a fictional firm that audits Calder Freight Inc., a private company, and has just been asked by Calder Logistics LLC, a subsidiary, to configure an AI assistant in its accounting system and "keep the monthly close files in your secure AI workspace so the assistant can answer our questions". The request arrives through the advisory team's web form. The onboarding orchestration checks the firm's entity relationship records, finds that Calder Logistics is consolidated into the audited group, and raises a flag. It asks the structured questions and records the answers the advisory manager, Priyanka Holm, supplies: the firm would store the client's close files in its workspace; the assistant would calculate proposed accruals the client's staff would rely on; the configuration involves adding custom logic to a commercial product. It also notes that the firm prepares Calder Freight's tax returns and that the proposed engagement would run to mid-2027, past 15 January 2027. The flow holds the advisory engagement letter and routes the pack to the audit engagement partner, Graham Voss. Graham reads it with the firm's independence lead. They conclude that storing the close files would be a hosting service and that the custom accrual logic raises a design and development question they cannot resolve on the facts provided. Graham declines the storage element outright and asks for more facts on the configuration. He records the decision, the facts and his reasoning. The orchestration marks nothing as cleared; it simply releases the hold on the parts Graham approved when he records them.
Responsible-use warning
Do not let an automated check mark any service "independence cleared". The AICPA interpretations do not name AI, their application depends on facts, and some impairments cannot be safeguarded at all. A keyword list or a name match will miss related entities and hosting described as convenience. Surface facts and questions, hold dependent steps, and let a named partner decide and record the conclusion. For issuer audit clients, remember that PCAOB and SEC rules also apply.
Human-review requirement
The engagement partner for the attest client, a licensed CPA, decides whether a new service impairs independence, usually with the firm's independence lead, and records the facts relied on and the reasoning. The partner offering the new service confirms the facts supplied are complete and accurate. For issuer audit clients, the partner confirms that PCAOB and SEC independence rules have been considered separately. No engagement letter or portal access for the flagged service is released until that record exists.
Practical exercise
Use a fictional firm with fictional attest and advisory clients.
- Describe a fictional attest client, its parent and two subsidiaries.
- Write a fictional advisory request from one subsidiary that involves an AI tool, in the words a client might use.
- Explain how your onboarding flow would link the request to the attest relationship without relying on a name match.
- Answer each structured question from this lesson for the request, marking any you cannot answer from the facts given.
- For each answer, name the interpretation it points to and state what the partner still needs to know.
- Note whether the firm provides tax services to the attest client and whether the engagement would extend past 15 January 2027.
- Describe what the flow holds while the partner decides, and what the requester sees.
- Draft the headings of the independence conclusion record the partner would complete.
- Write one sentence explaining why your check does not mark anything cleared.
- Name the owner of your structured questions and the event that would trigger their next revision.
- State whether your fictional attest client is an issuer. If it is, write the note your flow adds telling the partner that PCAOB and SEC independence rules must also be considered, outside this check.
Knowledge check
-
What does 1.295.143 say about hosting services for an attest client?
Answer guidance: Hosting includes acting as sole host of the client's system, taking custody of or storing its data or records, or providing security or back-up for them, and it impairs independence with no safeguard able to reduce the threat.
-
When is a tool that calculates results not part of a financial information system under 1.295.145.03a?
Answer guidance: When it only performs discrete calculations and the client accepts responsibility for the inputs and assumptions and understands the results.
-
What changed in the Tax Services interpretation, and when does it take effect?
Answer guidance: PEEC adopted revisions to ET 1.295.160 in May 2026, keeping a principles-based approach to self-review and advocacy threats. It is effective 15 January 2027, with early implementation permitted.
-
Why can the automated check not conclude on independence?
Answer guidance: The interpretations do not name AI, and whether a given AI engagement impairs independence depends on the facts, which only a named partner can weigh and record.
Sources and further reading
- American Institute of Certified Public Accountants (AICPA), Professional Ethics Executive Committee — AICPA Code of Professional Conduct: Hosting Services (1.295.143) and Information Systems Services (1.295.145) (2025-03-01). Accessed 2026-09-15.
- Journal of Accountancy (AICPA) — PEEC finalizes revisions to tax services independence guidance (2026-07-15). Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.