Cross-Domain Capstones
"The engagement partner who signs the audit opinion carries the professional liability for every judgment in the file. AI produces the evidence. The CA/CPA forms the conclusion."
In Lessons 11 through 14, you worked through domain-specific practice labs — building workflows for accounting and reporting, tax and advisory, assurance, management accounting, and GRC. Each lab exercised capabilities within a single domain. Real CA/CPA practice does not operate in silos. A new client engagement touches every domain simultaneously: you assess risk (assurance), review the financials (accounting), scope tax advisory, evaluate governance, and plan management reporting — all before the engagement letter is signed.
These two capstone exercises test your ability to integrate across all five domains. Exercise 22 tests breadth — connecting every domain in a single new client onboarding workflow. Exercise 23 tests depth — running the complete annual audit cycle from planning through to the signed opinion across three study sessions. Together, they represent the culmination of every capability you have built in this chapter.
New client onboarding workflow recipe: A reusable workflow specification for Exercise 22: workflow-recipes/ in the companion repository.
Audit cycle working paper pack: Templates for audit planning memoranda, test documentation, misstatement schedules, and management letters: working-papers/ in the companion repository.
Exercise 22: New Client Onboarding — Full Engagement Setup (60 min)
What you will build: A complete new client engagement file — from raw documents through to a client meeting agenda — for a textile exporter seeking its first bank-required audit.
Requirements: Cowork with finance@knowledge-work-plugins and financial-analysis@financial-services-plugins installed. 60 minutes.
New client profile: Alpha Textiles (Pvt) Ltd — a Pakistani private limited company. Textile exporter, 3 years operating, PKR 320M revenue. The company requires its first external audit because its bank is demanding audited financial statements before approving a working capital facility. The client has provided: three years of management accounts, the Memorandum and Articles of Association, the shareholder register, and a brief business overview from the CEO.
Step 1 — Document Intake and Classification
Place all client documents in /inputs/new-client-alpha/. Then ask your AI assistant:
Review all documents provided for this new client. Produce a client
profile covering:
(a) Entity type and ownership structure
(b) Industry and principal business activities
(c) Key financial metrics for each year — revenue, gross margin,
EBITDA, net profit
(d) Key customers and suppliers if identifiable
(e) Any immediate risks or issues visible from the documents
What this draws on: The accounting and financial reporting domain (Lesson 2) — financial statement analysis and metric extraction.
Step 2 — Engagement Risk Assessment
Perform an engagement acceptance risk assessment for this client
under ISA 220 (Quality Management for an Audit of Financial
Statements). Assess:
(a) Client integrity — any risk factors from the available information?
(b) Audit risk — industry complexity, transaction types, related
party risk
(c) Resource risk — does the firm have the competence and capacity
to perform this engagement?
(d) Independence risk — any potential threats to independence?
Produce an engagement risk rating: Low / Moderate / High.
What this draws on: The assurance domain (Lesson 4) — ISA-based risk assessment methodology.
Step 3 — Financial Analytical Review
Run the plugin commands to generate structured financial analysis:
/income-statement three-year-trend
/variance-analysis year-on-year
Then ask:
Perform an analytical review of the three years of management
accounts. Identify:
(a) Any significant trends in revenue, margin, or profitability
(b) Any year where the numbers look unusual relative to trend
(c) The ratio that most needs explanation before audit planning
can proceed
What this draws on: The management accounting domain (Lesson 5) and the Cowork plugin commands (Lesson 7).
Step 4 — Engagement Scope and Fee Proposal
Based on the client profile, risk assessment, and analytical review,
propose:
(a) The scope of services — which CA/CPA domains from this chapter
are relevant? What services should we propose for Year 1?
(b) The audit approach — key audit areas and why
(c) A fee estimate — using a standard rate card (provide notional
rates for Partner, Manager, Senior, and Staff levels in PKR)
and estimated hours by seniority level
(d) Key engagement conditions — any non-standard matters to include
in the engagement letter
What this draws on: Cross-domain integration — combining risk assessment (assurance), financial analysis (accounting), and advisory scoping (tax and advisory).
Step 5 — Draft the Engagement Letter
Draft the engagement letter for the audit of financial statements
for the year ending 30 June 2026. Include:
- Scope of the audit
- Management's responsibilities
- Auditor's responsibilities
- Fee arrangements and billing schedule
- Limitation of liability clause
Follow the standard format required under ISA 210 and adapt for
Pakistani professional standards (ICAP requirements).
Step 6 — Build Client-Specific SKILL.md Extensions
Using the information gathered in Steps 1-4:
Draft the following SKILL.md extensions for this client:
(1) Client entity knowledge — encode the business model, revenue
recognition method applicable (IFRS 15 for export sales with
specific incoterms), seasonal patterns visible in the management
accounts, and the key audit risk areas
(2) Jurisdiction specifics — Pakistan textile export sector:
applicable tax exemptions (SRO provisions for exporters),
DLTL (Duty and Tax Remission for Exports) claims, and WHT
rates applicable to export proceeds
What this draws on: The extension-building methodology (Lessons 9-10) and domain knowledge from Lessons 2-6.
Step 7 — Create the Engagement File Structure
Create the standard engagement file folder structure at
/client-alpha-audit/:
- Permanent file (entity documents, engagement letter, prior year files)
- Current year working file (planning, fieldwork sections by audit
area, conclusions)
- Output folder (draft accounts, management letters, signed opinions)
Populate the permanent file with the documents provided.
Step 8 — Produce the Client Meeting Agenda
Produce a 90-minute client kick-off meeting agenda. The meeting is
with the CEO and Finance Manager. Sections:
(1) Engagement scope and timeline
(2) Information required from the client and by when
(3) Key audit areas and why
(4) The client's responsibilities under the audit
(5) Fee and billing
(6) Our AI-augmented audit approach — how Cowork and our finance
plugins will be used, what this means for the client, and how
professional judgment is maintained throughout
The professional narrative: Section 6 of the client meeting agenda is increasingly important. Clients will ask how AI is used in your engagement. The CA/CPA who can explain clearly that AI handles execution while the CA/CPA maintains professional responsibility for every judgment call, opinion, and deliverable is demonstrating both innovation and professional integrity. This is the narrative that allows you to price AI-augmented services appropriately rather than competing on cost reduction alone.
Check your work: You should have produced eight deliverables: client profile, risk assessment, analytical review, engagement scope and fee proposal, engagement letter, two SKILL.md extensions, an engagement file structure, and a client meeting agenda. Each deliverable should reference or build upon the preceding ones.
IFRS: The engagement letter format follows ISA 210, which applies in IFRS jurisdictions worldwide. The revenue recognition analysis uses IFRS 15. US GAAP / IRC: US engagements follow AU-C 210 (AICPA standards). Revenue recognition follows ASC 606. Tax exemptions vary by state and federal provisions. UK FRS / HMRC: UK engagements follow ISA (UK) 210 with FRC adaptations. Export incentives operate through HMRC trade facilitation rather than SRO-type provisions.
Exercise 23: The Annual Audit Cycle — Planning to Completion (75 min across 3 sessions)
What you will build: The complete annual audit cycle for a manufacturing company — from planning analytical procedures through to the independent auditor's report.
Requirements: Cowork with all plugins installed. This exercise runs across three sessions of 25 minutes each. Sessions can be spread across different study periods.
Audit client: Use the same manufacturing company from Exercise 9 (or substitute your own client). Assume it is now year-end and the financial statements from Exercise 9 are the draft accounts.
Session 1 — Audit Planning (25 min)
Goal: Produce an audit planning memorandum with analytical procedures, materiality calculation, significant accounts, and audit strategy.
Step 1 — Planning Analytical Procedures
I am planning the external audit of [entity] for the year ended
[date]. Using the financial statements produced in Exercise 9 as
context, perform the planning analytical procedures required by
ISA 315.
Calculate year-on-year changes for all income statement and balance
sheet lines. Identify any change greater than 10% or PKR 5M that
requires an explanation before testing begins.
Step 2 — Calculate Materiality
Calculate planning materiality for this entity using three
benchmarks:
(a) 5% of pre-tax profit
(b) 1% of revenue
(c) 1% of total assets
Which benchmark is most appropriate and why? Set performance
materiality at 75% of planning materiality. Set a clearly trivial
threshold at 5% of planning materiality.
Step 3 — Identify Significant Accounts
Based on the financial statements, identify the accounts that are
both quantitatively significant (balance or transactions greater
than performance materiality) and qualitatively significant (subject
to management judgment or estimation). These are the accounts that
require substantive audit procedures.
Step 4 — Produce the Audit Plan
Produce an audit planning memorandum at
/working-papers/audit-plan.docx:
- Overall audit strategy (controls reliance vs purely substantive)
- Significant accounts requiring detailed testing
- Identified significant risks (ISA 315)
- Assessment of fraud risk (ISA 240)
- Audit procedures for each significant account
- Staffing plan with seniority levels and estimated hours
Save your working papers. You have produced a complete audit planning memorandum. Close Cowork and resume when you are ready for fieldwork.
What you have: An audit plan with analytical procedures, materiality thresholds, significant accounts, and procedures for each. This is a self-contained deliverable — it stands on its own as the planning phase record.
When you resume: Open your working papers from /working-papers/ and proceed to Session 2.
Session 2 — Audit Fieldwork (25 min)
Goal: Execute substantive testing on revenue and PPE, and document results with conclusions.
Step 5 — Revenue Testing
Apply the revenue audit procedures from Exercise 15 to the specific revenue lines in the Exercise 9 financial statements. Run the sampling and vouching procedures, testing revenue transactions against supporting documentation.
Step 6 — Property, Plant and Equipment Testing
Produce the audit procedures for property, plant and equipment:
- Test the additions schedule (agree to invoices)
- Test the disposals (confirm gain/loss calculation)
- Re-perform the depreciation calculation for a sample of assets
(verify rates, opening NBV, and calculation)
- Agree the closing net book value to the trial balance
Step 7 — Document the Results
For each area tested, produce the audit conclusion working paper:
- The procedure performed
- The sample selected
- The results
- Any exceptions identified
- The auditor's conclusion on whether the balance is fairly stated
Save your test documentation. You have completed fieldwork for revenue and PPE — the two substantive testing areas.
What you have: Completed working papers with test procedures, sample selections, results, exceptions (if any), and conclusions for each audit area. This is a self-contained deliverable.
When you resume: Open your test documentation from /working-papers/ and proceed to Session 3.
Session 3 — Audit Completion (25 min)
Goal: Evaluate misstatements, draft the management letter, and form the audit opinion.
Step 8 — Evaluate Misstatements
Compile the schedule of identified misstatements from all audit
areas. Classify each as:
- Known misstatement (specific amount)
- Likely misstatement (estimated)
Determine whether the aggregate of all misstatements — individually
and in combination — is material to the financial statements.
Professional judgment moment: This is the step where the CA/CPA's judgment matters most. The AI compiles and calculates. The CA/CPA decides whether the aggregate effect of misstatements is such that the financial statements are no longer true and fair. This decision determines the audit opinion.
Step 9 — Draft the Management Letter
Based on the audit findings, draft a management letter at
/outputs/management-letter.docx identifying:
(a) Any internal control weaknesses identified during the audit
(b) Recommendations for improvement
(c) Any other observations of significance to management
Use the 5-C format from Exercise 17 (Condition, Criteria, Cause,
Consequence, Corrective action).
Step 10 — Draft the Audit Opinion
Draft the Independent Auditor's Report for these financial
statements following the ISA 700 format. Include:
- Basis of opinion (IFRS and ISAs)
- Key audit matter (revenue recognition)
- Management's responsibilities
- Auditor's responsibilities
- The audit opinion
Assume the financial statements give a true and fair view with no
material misstatements.
The professional boundary: The audit opinion is the most legally significant document a CA/CPA signs in professional practice. No AI agent writes the audit opinion — the CA/CPA forms it. The agent produces the draft language following the prescribed ISA 700 format. The professional judgment is in Step 8: deciding whether identified misstatements are material, and whether their aggregate effect is such that the accounts are no longer true and fair. This is the judgment for which the CA/CPA holds professional liability. Every other step in this exercise exists to support and inform that judgment.
Check your work: Across three sessions you should have produced: an audit planning memorandum (Session 1), test documentation with conclusions for revenue and PPE (Session 2), a misstatement schedule, a management letter, and a draft audit opinion (Session 3). The opinion should flow logically from the evidence gathered in Sessions 1 and 2 and the evaluation performed in Session 3.
IFRS / ISA: The audit report format follows ISA 700 (Forming an Opinion and Reporting on Financial Statements), used in 130+ jurisdictions. Key audit matters follow ISA 701. US GAAP / PCAOB: US listed company audits follow PCAOB AS 3101 (The Auditor's Report on an Audit of Financial Statements). The format differs from ISA 700 — notably the critical audit matters section replaces key audit matters. UK FRS / FRC: UK audits follow ISA (UK) 700 with FRC-specific modifications, including the viability statement review and the Section 172 statement assessment required for qualifying companies.
Try With AI
Use these prompts in Cowork or your preferred AI assistant to explore the integration patterns from these capstone exercises.
Prompt 1: Cross-Domain Workflow Design
I am a CA/CPA planning a new client onboarding process. The client
is a [DESCRIBE YOUR CLIENT — industry, size, jurisdiction, reason
for engagement].
Design a cross-domain onboarding workflow that touches all relevant
CA/CPA practice areas. For each step:
1. Identify which domain it belongs to (Accounting, Tax, Assurance,
Management Accounting, or GRC)
2. Specify what information flows into this step from previous steps
3. Identify the professional judgment decision at this step
4. Suggest the Cowork plugin command or SKILL.md that supports it
Produce the workflow as a numbered sequence showing how the domains
connect.
What you are learning: Cross-domain integration is not about doing five things separately — it is about designing the information flow between domains so each step builds on the previous. The workflow design forces you to think about dependencies: the risk assessment (assurance) requires the client profile (accounting), and the fee proposal requires both.
Prompt 2: Session Boundary Design
I need to design a multi-session exercise for [DESCRIBE YOUR
PROFESSIONAL WORKFLOW — e.g., year-end tax compliance, internal
audit programme, quarterly board reporting].
Break the workflow into 3-4 sessions of 20-30 minutes each. For
each session:
1. Define the goal (one sentence)
2. List the specific deliverable produced
3. Explain what state must be saved for the next session
4. Identify the professional judgment decision in this session
Ensure each session produces a self-contained deliverable that
stands on its own — a student should be able to stop after any
session and have something complete.
What you are learning: Multi-session exercise design teaches you to identify natural stopping points in professional workflows. The constraint that each session must produce a self-contained deliverable mirrors real practice — audit planning files, fieldwork papers, and completion files are each reviewed independently. Designing your own session boundaries develops your ability to decompose complex professional workflows into manageable, reviewable stages.
Prompt 3: Professional Judgment Boundary Analysis
Analyse the following AI-augmented CA/CPA workflow:
[PASTE ONE OF YOUR EXERCISE OUTPUTS — e.g., the audit plan from
Exercise 23 Step 4 or the risk assessment from Exercise 22 Step 2]
For each step or section in this output:
1. Classify it as "AI execution" (data extraction, calculation,
formatting, drafting) or "Professional judgment" (risk
assessment, materiality decision, opinion formation, client
acceptance)
2. For the professional judgment items, explain what could go wrong
if the CA/CPA accepted the AI output without exercising
independent judgment
3. Identify the single most critical judgment point — the one where
getting it wrong carries the highest professional liability
This analysis should help me understand where I add value that AI
cannot replace.
What you are learning: The professional judgment boundary is not abstract — it is specific to each workflow. By analysing your own exercise output, you map exactly where AI execution ends and professional responsibility begins. The critical insight is that professional liability attaches to judgment decisions, not execution steps. Understanding this boundary is how you articulate your value proposition in an AI-augmented practice.
Flashcards Study Aid
Continue to Lesson 16: Full Practice Deployment and Reflection →