IMA CMA Part 1 Course Notes

This 20% domain is formula- and sequence-heavy. Strategy sets direction; budgets translate strategy into quantified plans; forecasts update expectations as information changes. Know the master-budget flow, production/material/cash formulas, flexible versus static budgets, and when a forecasting method fits the data.

• Treating a forecast as the same thing as a target.

• For every budget formula remember: NEEDS + desired ending − beginning.

This 20% domain is a major calculation target. Always compare actual performance with the correct benchmark—often a flexible budget or standard quantity/hours allowed for actual output. Then ask whether the variance is price/rate, quantity/efficiency, volume, or spending. Performance measures must match controllability and should not encourage decisions that hurt the company overall.

• Using budgeted output instead of actual output to determine SQ or SH allowed.

• Price/rate variance: actual quantity/hours × price/rate difference.

This 15% domain tests financial-reporting logic more than bookkeeping trivia. Know how one transaction changes multiple statements, the core recognition/measurement rules, consolidation eliminations, and the few GAAP/IFRS differences that are consistently testable. Do NOT use the shortcut 'GAAP = cost, IFRS = fair value'—both frameworks use multiple measurement bases.

• Using 'cash received' as the trigger for all revenue.

• First identify the reporting framework.

Cost management is about matching the cost concept to the decision. Know what changes with volume, what is traceable, what is relevant, and how a costing system assigns resources. For process improvement, remove non-value-added work and constraints while protecting quality, controls, and customer value.

• Calling every fixed cost irrelevant.

• Ask first: What decision is this cost being used for?

Internal controls ask one core question: what risk threatens the objective, and which control most directly reduces that risk to an acceptable level? Know COSO, segregation of duties, preventive/detective/corrective controls, design versus operating effectiveness, and the difference between IT general controls and application controls.

• Choosing a control because it sounds strong but does not address the stated risk.

• Start every scenario with OBJECTIVE → RISK → CONTROL.

Technology and analytics is not an IT trivia section—it tests whether finance can select, govern, control, analyze, and communicate information. Know system scope, data quality/governance, SDLC/change controls, appropriate automation candidates, the four analytics types, and visualization choices.

• Treating AIS and ERP as synonyms.

• System question? Ask scope: accounting only, enterprise integration, or performance management.