Levels 2 through 4 kept AI in a drafting role: a person read every output, decided every step, and signed everything. Level 5 is where a firm lets software act. An agent receives a new client enquiry, runs the conflict and independence screen against the firm database, assembles the engagement-letter draft and the prepared-by-client request list, and queues them. An orchestration reads the bank feed, matches transactions to the ledger, drafts the reconciliation and the flux narrative, and puts the exceptions in a review queue with the manager named on each one. An integration drafts a recurring journal entry from a signed schedule and waits for the person who is allowed to post it. Each of these touches the firm's systems of record, its clients, and its taxpayer data, and each is built so that the actions it may take are narrow, the actions it may not take are impossible rather than discouraged, a named person approves anything that matters, and every action lands in the engagement file.
The course has five modules. Agents and orchestration in an accounting firm defines what an agent may do, must never do, and may do only with approval, then builds two orchestrations end to end: client onboarding through engagement letter and PBC request, and the month-end close from bank feed to reviewed flux narrative. APIs and integrations with the systems of record designs the integration map and data contracts across the general ledger and ERP, practice management, document management, tax preparation and e-file, payroll, and payments, read-only first and write only with approval, with journal-entry controls treated as the highest-risk write in the firm. Approval gates and role-based access designs the gate for every action that posts to a ledger, reaches a client, or lands on a return, the role model across partners, managers, staff, seasonal preparers, outsourced teams, and service accounts, with Internal Revenue Code section 7216 consent and Circular 230 supervision as hard constraints, and the override and kill switch that work in the middle of busy season. Prompt-injection defence, logging, and monitoring treats client PDFs, bank statements, portal uploads, vendor invoices, and inbound email as hostile input, logs every agent action into the engagement file so the documentation standards are satisfied, and monitors for drift, cost, and silent failure across a year whose volume swings by a factor of five. Incident response, return, and the implementation project adapts the NIST incident-response structure to automation failures, measures return honestly in a business whose seasonality will otherwise claim the credit, and sets out the seven-stage method the capstone follows.
The capstone is a working automation, built and run on fictional or de-identified data, with its scope statement, integration map, approval gates, role model, injection defences, logs, monitoring plan, incident runbook, and return measurement, reviewed against a published rubric.
Nothing in Level 5 lets an agent do professional work. Signing or electronically filing a return, taking a tax position, forming or issuing an audit opinion or conclusion, posting a journal entry without a named approver, changing an engagement's scope or fee, and reading data outside its contract are not automated at any maturity level. They remain with the licensed practitioner and the person of record, and the agents built here prepare and wait.
This is an independent educational course offered by AI Coalition Network. It does not replace a CPA licence, state board rules, Circular 230 obligations, the AICPA Code of Professional Conduct, the Statements on Standards for Tax Services, or any federal or state law.