Study guide

3.5 Assessing Information-System Deficiencies & Replacement Needs

CPA Program — Strategic Management Accounting Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Role of Strategic Management Accounting & Value Creation

1.1 Evolution & Role of the Strategic Management Accountant 1.2 Defining & Creating Multi-Stakeholder Value 1.3 The Strategic Management Process & Strategy Formation

2 Chapter 2: Strategic Analysis, Environmental Scanning & Professional Ethics

2.1 External Environmental Scanning: PESTEL & Porter's Five Forces 2.2 Internal Capability Analysis, VRIO & Core Competencies 2.3 Professional Ethics, Governance & Risk in Strategic Management Accounting

3 Chapter 3: Information Architecture, Systems & Behavioral Biases

3.1 Data, Information & Knowledge Architecture 3.2 Management Information Systems, ERP & Digital Technologies 3.3 Decision-Making Needs & Cognitive Biases 3.4 Stakeholder Communication, Sources & Information Integration 3.5 Assessing Information-System Deficiencies & Replacement Needs 3.6 Evaluating, Implementing & Reviewing Information Solutions

4 Chapter 4: Relevant Information, Tactical Decisions & Limiting Factors

4.1 Relevant Cost Analysis & Differential Decision-Making 4.2 Short-Term Tactical Decision Scenarios 4.3 Limiting Factors, Theory of Constraints & Throughput Accounting

5 Chapter 5: Strategic Planning, Master Budgets & Budgetary Control

5.1 Master Budget Architecture & Process 5.2 Financial Budgets & Cash Flow Forecasting 5.3 Budgetary Control & Flexible Budgeting 5.4 Service, Not-for-Profit & Departmental Budgets

6 Chapter 6: Modern Budgeting Methodologies & Behavioral Dynamics

6.1 Alternative Budgeting Systems: ZBB, ABB & Rolling Budgets 6.2 Beyond Budgeting Principles & Dynamic Forecasting 6.3 Behavioral Dimensions of Budgeting

7 Chapter 7: Standard Costing & Comprehensive Variance Analysis

7.1 Standard Cost Setting & Direct Cost Variances 7.2 Overhead Variance Analysis 7.3 Sales Variances: Price, Volume, Mix & Quantity 7.4 Planning vs Operational Variances & Variance Investigation

8 Chapter 8: Project Selection, Governance & Financial Appraisal

8.1 Project Fundamentals, Governance & Life Cycle 8.2 Project Selection & Strategic Alignment 8.3 Capital Investment Appraisal Techniques 8.4 Project Structures, Teams, Supplier Contracts & Probity

9 Chapter 9: Project Scheduling, Earned Value Management & Risk

9.1 Project Scheduling, Network Analysis & Resource Management 9.2 Earned Value Management (EVM) & Project Control 9.3 Project Risk Management, Methodologies & Post-Completion Review 9.4 Completion Decisions, Acceptance, Financial Closure & Knowledge

10 Chapter 10: Performance Management Systems & Responsibility Centers

10.1 Management Control Systems & Simons' Levers of Control 10.2 Responsibility Accounting & Organizational Design 10.3 Designing Effective Key Performance Indicators (KPIs)

11 Chapter 11: Divisional Financial Performance & Transfer Pricing

11.1 Return on Investment (ROI) & Residual Income (RI) 11.2 Economic Value Added (EVA) 11.3 Transfer Pricing in Decentralized Organizations

12 Chapter 12: Strategic Performance Frameworks & Executive Incentives

12.1 The Balanced Scorecard Framework 12.2 Strategy Maps & Causal Linkages 12.3 Multidimensional Performance Frameworks 12.4 Executive Compensation, Incentive Systems & Agency Theory

13 Chapter 13: Strategic Cost Management, Value Chains & Activity-Based Costing

13.1 Strategic Cost Management & Value Chain Analysis 13.2 Activity-Based Costing (ABC) Mechanics 13.3 Activity-Based Management (ABM) & Time-Driven ABC

14 Chapter 14: Strategic Pricing, Target Costing & Life-Cycle Costing

14.1 Strategic Pricing Decisions & Policies 14.2 Target Costing & Kaizen Costing 14.3 Life-Cycle Costing & Environmental Management Accounting

15 Chapter 15: Customer Profitability, Lean Supply Chains & Quality Costs

15.1 Customer Profitability Analysis & Cost-to-Serve 15.2 Supply Chain Management & Lean Operations 15.3 Cost of Quality (COQ) Framework & Total Quality Management 15.4 Outsourcing, Offshoring & Downsizing Decisions

3.5 Assessing Information-System Deficiencies & Replacement Needs

Key Takeaways Explain This Topic AI

Diagnose whether the gap arises from data, process, skills, controls or system capability before proposing replacement.

Translate stakeholder needs into measurable requirements and acceptance criteria.

Compare improving the current system, adding a targeted solution and replacing the system against the same baseline.

A preliminary assessment scopes feasibility and risks; it does not prove the final business case.

Last updated: October 2026

Diagnose Before Buying

The official Module 2 outline includes upgrading or replacing information systems. The starting question is what information is missing or unreliable and why that matters to a decision. Buying a new system before diagnosing the problem can automate poor definitions, preserve redundant approval steps and make inconsistent data move faster.

Replacement triggers include unsupported software, persistent control weaknesses, inability to integrate a new business, slow reporting, missing strategic measures and unacceptable continuity risk. These are reasons to investigate, not automatic proof that replacement is best. A late monthly margin report could reflect slow system processing, unapproved time sheets, unclear cost ownership or unresolved master-data errors. Each cause requires a different remedy.

Interview report users, observe actual workflows and inspect evidence of delays or errors. Trace a sample from source transaction to decision report. Record where data are created, transformed, approved and reconciled. Separate the symptom, its operational consequence and the proposed cause. This prevents a vendor’s feature list from becoming the organisation’s requirements by default.

A Preliminary Assessment

A preliminary assessment defines the problem and asks whether potential solutions deserve detailed evaluation. It should cover the affected processes and stakeholders, the strategic objective, current performance, essential controls, constraints and the resources required for investigation. Identify the sponsor, decision authority, process owner and users who must accept the result.

A requirements register can make a vague request assessable:

Request Decision requirement Illustrative acceptance criterion

Faster inventory reporting Avoid promising unavailable stock Accepted warehouse movements reflected within the specified reporting window

Better customer profit Identify excessive service demand Orders, deliveries and support hours traceable to the same customer identifier

Stronger payment control Prevent unauthorised supplier changes Changes independently approved and retained in an audit trail

More reliable forecasting Evaluate near-term liquidity Controlled assumptions, version history and reconciliation to opening balances

The numerical thresholds belong to the particular business case. Do not invent a universal response time or accuracy percentage. Distinguish essential legal or control conditions from desirable features and optional conveniences. A solution failing an essential requirement should not win because it has a visually attractive dashboard.

Analyse the Existing System

Document current interfaces, manual spreadsheets, data ownership, access rights, reconciliations, failure history and support arrangements. A process map should expose duplicate entry and hand-offs. An information map should show the definition and source of important fields. Together they help distinguish inadequate technology from ineffective use of adequate technology.

Review both formal reports and the unofficial workarounds people actually use. A spreadsheet maintained by an experienced employee may contain critical logic missing from the official process. Capture that knowledge before replacing anything. Examine whether migration can preserve necessary history and whether statutory retention and access requirements can still be met.

Compare at least three credible options where available: improve the existing process and controls, add a targeted reporting or integration layer, and replace the core system. Include a do-minimum alternative with the genuine consequences of postponing action. Its forecast need not stay flat, but deterioration must have evidence. Do not exaggerate future failures to make replacement appear attractive.

Worked Preliminary Decision

Assume a fictional wholesaler takes ten working days to produce customer margins. Investigation finds three days spent extracting files, four days reconciling inconsistent customer identifiers and three days obtaining approval. A proposed new dashboard can reduce extraction to one day but does not repair identifiers or change approvals. The realistic result is eight days, not one.

The accountant proposes a preliminary trial: clean customer identifiers, assign an accountable data owner and simplify approval for routine reconciliations. Assume this cuts reconciliation to one day and approval to one day. With the existing three-day extraction, reporting would take five days. A later dashboard could reduce that to three days. These are testable process assumptions, not guaranteed benefits.

For the trial, measure reporting time, unresolved exceptions and user acceptance over comparable reporting cycles. If data errors remain, the business should understand them before selecting a replacement. The trial may show that a smaller integration project meets the need at lower transition risk, or it may establish a genuine requirement for core replacement.

Common Assessment Pitfalls

A frequent failure is asking users which software they want instead of which decisions they need to make. Others include accepting senior managers’ requests without observing operations, collecting every conceivable requirement without prioritisation, ignoring external stakeholders and assuming all current reports should be reproduced. Redundant reports can be retired when their decision purpose no longer exists.

The accountant should also challenge optimism about implementation capacity. Staff still have ordinary work during migration, testing and training. Record dependencies on scarce people, contractual exit constraints and data quality. Present unresolved matters as investigation tasks with owners. The preliminary recommendation should say which option proceeds to detailed evaluation, what evidence is still needed and what would cause the sponsor to stop or change direction.