Study guide
4.3 Finance and Accounting Concepts for the Activity Under Review
CIA Part 2 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CIA Part 2 Exam Orientation
1.1 Current CIA Part 2 Exam Facts 1.2 Eligibility, Fees, and Pearson VUE Scheduling 1.3 Scoring, Results Timing, and the 2025 Syllabus Map
2 Chapter 2: Engagement Objectives and Scope
2.1 Topical Requirements in Objectives and Scope 2.2 Elements Used to Build Engagement Objectives 2.3 Scope Limitations, Stakeholder Requests, and Scope Changes
3 Chapter 3: Evaluation Criteria and Planning Context
3.1 Selecting and Testing Evaluation Criteria 3.2 Applying Topical Requirements When Planning 3.3 Strategy, Risk Management, and Performance of the Activity Under Review
4 Chapter 4: Technology, Continuity, and Finance in Planning
4.1 Cybersecurity, IT General Controls, Privacy, and Data Security 4.2 Business Continuity, Disaster Recovery, and Resilience 4.3 Finance and Accounting Concepts for the Activity Under Review
5 Chapter 5: Business Process and System Risks in Planning
5.1 Asset, Supply Chain, Inventory, Payables, Procurement, and Compliance Processes 5.2 Third-Party Process Risks 5.3 CRM, ERP, and GRC System Risks
6 Chapter 6: Engagement Approach and Project Management
6.1 Agile, Traditional, Integrated, and Remote Approaches 6.2 Project Management While Planning and Conducting Engagements
7 Chapter 7: Engagement Risk Assessment
7.1 Topical Requirements and Pervasive Financial, Operational, IT, Cyber, and Regulatory Risks 7.2 Emerging Risks and the Impact of Change 7.3 Methods to Evaluate and Prioritize Risks and Controls
8 Chapter 8: Structure, Environment, and Culture
8.1 Centralized vs Decentralized, Flat vs Traditional, In-Person vs Remote 8.2 Culture, Group Behavior, and Tone at the Top
9 Chapter 9: Control Design, Effectiveness, and Efficiency Procedures
9.1 Procedures to Evaluate Control Design 9.2 Procedures to Test Operating Effectiveness 9.3 Procedures to Test Control Efficiency
10 Chapter 10: Work Programs, Testing Methodologies, and Resources
10.1 Evaluating Adequacy of the Engagement Work Program 10.2 Testing Methodologies for Accounting, Finance, IT, Operations, and Cybersecurity 10.3 Financial, Human, and Technological Resources and Limitation Implications
11 Chapter 11: Information Sources and Preliminary Survey
11.1 Interviews, Observations, and Walk-Throughs 11.2 Data Analysis as an Information Source 11.3 Policies, Checklists, Risk-and-Control Questionnaires, and Self-Assessments
12 Chapter 12: Evidence Relevance, Sufficiency, and Reliability
12.1 Criteria for Evidence Quality 12.2 Independence, Corroboration, and the Control Environment 12.3 Evidence an Informed, Competent Person Could Rely On
13 Chapter 13: Technology Options for Findings and Conclusions
13.1 Artificial Intelligence, Machine Learning, and Robotic Process Automation 13.2 Continuous Monitoring, Dashboards, and Embedded Audit Modules
14 Chapter 14: Process Mapping and Data Analytics
14.1 Workflow Segments, Process Maps, Walk-Throughs, and RACI 14.2 Structured vs Unstructured Data and the Analytics Process 14.3 Diagnostic, Prescriptive, Predictive, Anomaly, and Text Analysis
15 Chapter 15: Analytical Review and Finding Evaluation
15.1 Ratios, Variances, Trends, and Benchmarking 15.2 Selecting Analytical Techniques for Engagement Objectives 15.3 Comparing Existing Conditions to Evaluation Criteria 15.4 Root Causes, Effects, and Significance of Findings
16 Chapter 16: Workpapers and Engagement Conclusions
16.1 Organizing Complete Workpapers with Sufficient Evidence 16.2 Linking Workpapers to Results; Retention, Regulation, and Policy 16.3 Aggregating Findings and Concluding on Governance, Risk, and Control
17 Chapter 17: Engagement Supervision
17.1 Supervision Throughout Planning and Fieldwork 17.2 Coordinating Assignments and Reviewing Workpapers and Conclusions 17.3 Evaluating Auditors' Performance
18 Chapter 18: Communication During the Engagement
18.1 Formal and Informal Communication Across Planning, Fieldwork, and Reporting 18.2 Situations That Require Escalation 18.3 Selecting Appropriate Stakeholders for Engagement Communication
19 Chapter 19: Final Review and Test Day
19.1 2025 vs 2019 Traps and Part 2 vs Part 3 Boundaries 19.2 Pacing, Test-Center Rules, and Official Results
4.3 Finance and Accounting Concepts for the Activity Under Review
Key Takeaways Explain This Topic AI
Use the activity's balance-sheet and flow profile — what it holds, what moves, who can move it, and how it is measured — to identify key risks; this is not a FAR exam.
Current versus fixed assets and short-term versus long-term liabilities change the risk picture: turnover and cutoff versus existence, valuation, impairment, and classification.
Existence, valuation, cutoff, authorization, and reconciliation are the assertions and control activities that should drive objectives for treasury and fixed-asset engagements.
Planning treasury means wires, investment valuation, bank and custody reconciliation, and payment-system access — not only a walk-through of cash-handling procedures.
Ignoring accounting assertions produces a work program that tests whether a policy exists while missing the risks that actually misstate the activity.
Last updated: August 2026
A3e asks you to recognize finance and accounting concepts related to the activity under review: current and fixed assets, short-term and long-term liabilities, capital, and investments. This is not a financial accounting and reporting exam. You will not be asked to compute diluted earnings per share or book a complex hedge. You will be asked to use the activity's balance-sheet and cash-flow profile so the engagement risk assessment hits the risks that actually misstate or mismanage that activity. The trap is to plan procedures around whether a policy exists while ignoring the assertions that should drive control objectives.
Start from what the activity holds and what it moves
Before you write objectives, sketch the activity in accounting language. What assets does it hold (cash, receivables, inventory, equipment, investments)? What liabilities does it create (payables, accruals, customer deposits, debt, lease obligations)? Does it spend capital (projects, acquisitions) or manage investments (treasury, surplus cash, endowments)? What flows through it each day?
That sketch tells you which assertions matter. A payroll activity is mostly completeness and cutoff of expense and liability, plus existence of the cash outflow. A fixed-asset activity is existence, valuation, rights, authorization of disposals, and cutoff between capital and expense. A treasury activity is existence of cash and securities, valuation of investments, authorization of transfers, completeness of recorded deals, cutoff of wires, and reconciliation to banks and custodians.
Standard 13.2 wants those risks named. Standard 13.3 wants objectives and scope that follow them. The work program (Chapter 10) will later specify tests. Here, if the sketch is missing, the program will test the wrong things.
Current assets, fixed assets, and why the distinction changes the plan
Current assets are expected to be realized within the operating cycle: cash, short-term investments, receivables, inventory, and prepaids. They tend to emphasize existence, completeness, cutoff, valuation (allowances, lower of cost or net realizable value), and custody. Turnover is high, so a week of missing reconciliations or a bad cutoff around period-end can be material to the activity.
Fixed (noncurrent) assets — property, plant, equipment, and often intangibles the activity owns — turn slowly. Existence (is the asset there?), rights (owned versus leased), valuation (cost, depreciation, impairment, idle assets), and authorization of additions, transfers, and retirements dominate. Cutoff still matters at the capital-versus-expense boundary. If you plan a fixed-asset engagement as if it were a cash count, you will under-test impairment, useful lives, and construction-in-progress that should have been placed in service.
Short-term versus long-term liabilities, capital, and investments
Short-term liabilities (trade payables, accruals, short-term borrowings, unearned revenue due soon) emphasize completeness of unrecorded obligations, cutoff, and authorization of disbursements. Long-term liabilities (bonds, notes, finance leases, long-dated customer obligations) emphasize completeness of the obligation, valuation, and authorization of new borrowing or modifications. Classification itself is a risk: a covenant breach can make a long-term balance current overnight — relevant if the activity under review is treasury or a business unit that holds the debt.
Capital, for the planner, usually means capital projects and capital expenditures of the activity, not the group's entire equity section. Risks include expenditure recorded in the wrong period or as expense versus asset, unauthorized project overruns, idle construction-in-progress, and failure to place assets in service. Investments — securities, term deposits, surplus-cash portfolios — bring valuation (pricing source, fair value versus amortized cost), existence (custodial confirmation), authorization (policy limits, approved counterparties), and segregation of dealing from recording and from reconciliation.
Do not drag accounts-payable invoice processing, procurement vendor setup, or CRM/ERP/GRC landscapes into this section. Those process and system risks are the next chapter. Stay with the accounting profile of the activity you are actually planning.
Element Typical activity Key risks the planner should name Assertions / controls that should drive objectives
Current assets — cash Treasury, collections Unauthorized wires; incomplete recording; unreconciled items Existence, completeness, cutoff, authorization, bank reconciliation
Current assets — short-term investments Treasury Wrong valuation; deals outside policy; custody gaps Valuation, existence, authorization, independent pricing
Fixed assets Plant, fleet, equipment-heavy operations Ghost assets; idle CIP; capital vs expense; unauthorized disposals Existence, valuation, rights, cutoff, authorization, subledger-to-GL
Short-term liabilities Accruals, short-term debt in treasury Unrecorded obligations; period-end cutoff Completeness, cutoff, authorization
Long-term liabilities Debt held in treasury or a business unit Missing modifications; classification/covenant risk Completeness, valuation, authorization, classification
Capital expenditures Project-heavy activity Overruns; wrong period; not placed in service Authorization, cutoff, valuation, existence
Investments Treasury, endowment, surplus cash Pricing conflict; incomplete trade capture Valuation, existence, completeness, segregation
Assertions that should drive control objectives
Translate each significant balance or flow into control objectives:
Existence / occurrence: recorded cash, assets, investments, and transactions are real.
Completeness: all cash movements, assets, liabilities, and investment deals are recorded.
Valuation: amounts are appropriate — foreign exchange, accrued interest, impairment, depreciation, fair value.
Cutoff: recorded in the correct period; wires, receiving, and capital invoices near period-end are the usual flashpoints.
Authorization: only permitted people and amounts; dual control on payments; approved capital and disposal requests.
Reconciliation: bank, custody, subledger-to-general-ledger, and clearing accounts that make the other assertions credible.
Reconciliation is a control activity rather than a financial-statement assertion, but CIA items often treat independent reconciliation with follow-up of reconciling items as the control that makes existence and completeness believable. Aging reconciling items is a planning red flag: a reconciliation that always "ties" because differences sit in a suspense account for months is not operating.
The exam trap is to ignore these assertions. If you plan a fixed-asset engagement around "obtain the capitalization policy and confirm it was approved," you have not addressed whether trucks on the lot exist, whether construction-in-progress was placed in service, or whether a sale of equipment was authorized and removed from the subledger. Policy existence is documentation. Assertions are why the controls exist.
Scenario: planning a treasury engagement
Treasury typically holds cash, short-term investments, and sometimes debt. Daily flows include collections, disbursements, investment purchases and sales, and foreign exchange. Key risks: unauthorized or directed wires, payment-system access (Chapter 4.1 joins 4.3 here), incomplete recording of trades, stale signatories, unreconciled suspense, valuation of securities using a conflicted source, and cutoff of period-end transfers.
Control objectives should therefore include dual authorization of payments, independent bank and custody reconciliations, access to the payment network limited to current staff, investment transactions within policy limits, and an independent pricing source. Continuity belongs too: if treasury's RTO is four hours, untested backup of the payment system is a finance risk, not a side IT topic (Chapter 4.2). You would not, in this chapter's scope, dive into accounts-payable invoice processing or procurement. You would include IT access to the treasury workstation because unauthorized access is how an authorization control fails.
Scenario: planning a fixed-asset engagement
Walk the same logic. Existence: book-to-floor and floor-to-book for a sample of locations and asset classes. Valuation: useful lives, residual values, impairment triggers for idle or damaged assets, and construction-in-progress that should have been placed in service. Cutoff: invoices near period-end coded to expense that should have been capitalized, and vice versa. Authorization: acquisitions above threshold, transfers between departments, and disposals or write-offs. Reconciliation: asset subledger to the general ledger, with investigation of unposted additions.
IT still belongs: who can change depreciation parameters, who can delete an asset record, and whether the asset system restores within the RTO if operations depend on it for regulatory equipment tracking. Accounting assertions without system integrity are incomplete. System integrity without assertions is an IT tour that never asks whether the trucks exist.
The planning sequence is the same for any activity with a balance-sheet footprint: sketch holdings and flows, name the assertions, identify the controls that address those assertions, then set objectives and scope. That is A3e. It is how a Part 2 planner uses accounting, not how a candidate sits FAR.