3.6 Evaluating, Implementing & Reviewing Information Solutions

Compare Solutions on the Same Basis

Once an information need is understood, evaluate whether a proposed solution will supply decision-useful information at an acceptable cost and risk. The management accountant combines financial appraisal with requirements analysis, professional judgement and stakeholder communication. A positive spreadsheet NPV is insufficient if the solution cannot meet a mandatory control or cannot be operated by its intended users.

Use common assumptions across the options. Specify the reporting period, transaction volumes, implementation dates, useful life, tax treatment and discount-rate basis. Record which costs change relative to the chosen baseline. Licence prices alone omit integration, data cleansing, migration, testing, training, support and eventual exit. Include temporary parallel operation where necessary; avoid counting the old support cost as saved before the contract can actually be ended.

Separate Benefits from Promises

Cash benefits may include reduced contractor payments, eliminated vacancies, lower error losses or additional contribution from productive capacity. Released staff time is initially a capacity benefit. It becomes a cash saving only when payroll or other expenditure changes, or it supports additional revenue with its own incremental costs. Do not count both redeployment value and an eliminated salary for the same employee time.

Non-financial benefits can include better control, faster decisions and more reliable continuity. Explain their causal mechanism and assess their importance without assigning arbitrary monetary values. Some are minimum acceptance conditions. Others can be assessed using transparent weighted criteria whose weights and scores reflect the organisation’s objectives. Test whether modest changes to subjective scores reverse the decision.

Worked Financial Evaluation

A fictional distributor compares a targeted reporting system with its current process. Assume an immediate AUD 180,000 implementation outlay, three years of benefits, no residual value, no tax or working-capital effects, and an 8% annual discount rate. The system avoids AUD 70,000 annual contractor fees and AUD 20,000 expected annual processing errors. Annual support costs AUD 25,000. Net annual cash benefit is therefore 70,000 + 20,000 − 25,000 = AUD 65,000.

The three-year annuity factor at 8% is approximately 2.5771. Present value of benefits is 65,000 × 2.5771 = AUD 167,511.50. NPV is 167,511.50 − 180,000 = negative AUD 12,488.50. The proposal fails the stated financial test, although a separately justified mandatory control requirement might require a different decision or a better alternative.

Suppose the vendor additionally claims AUD 40,000 of annual staff-time savings, but no headcount, recruitment or overtime expenditure will change. Adding that amount to cash flows would overstate NPV. If the sponsor can demonstrate a distinct new contribution from using the time, evaluate that contribution with evidence and avoid double-counting the contractor savings. State uncertainty: the error saving is an expected value and should be stress-tested.

A useful sensitivity asks what recurring benefit is required for NPV zero. Annual net benefit must be approximately 180,000 / 2.5771 = AUD 69,846. Additional verified annual benefit of about AUD 4,846 would close the gap. This calculation identifies the evidence needed; it does not authorise inventing the missing benefit.

Implementation and Acceptance

Create a migration plan stating ownership, mapping rules, reconciliation controls and rollback conditions. Before conversion, resolve duplicate identifiers and retain an authorised record of transformations. Reconcile record counts and balances, but also test whether relationships survive: a total can agree even when transactions are assigned to the wrong customers.

User acceptance should test real decisions and exceptions. Examples include an incomplete supplier record, a returned order, a foreign-currency transaction and an unauthorised access attempt. Test security roles and segregation of duties as well as report arithmetic. Verify how failed interfaces are detected, corrected and reported. A successful demonstration using perfect sample data is not sufficient acceptance evidence.

Plan training and support for the users responsible for the new workflow. State which old reports and processes will cease, when they will cease and who approves the change. Parallel running can reduce transition risk, but an indefinite parallel process adds cost and conflicting versions. A go-live decision needs evidence that essential criteria are met and residual risks are accepted by authorised owners.

Review the Information Solution

After implementation, compare actual costs, adoption and decision performance with the approved case. Assign benefit owners before go-live and schedule reviews when benefits can reasonably be observed. For the distributor, reconcile avoided contractor invoices, measure error frequency and inspect whether managers use the reports in the intended decisions.

Separate implementation success from strategic success. The system may go live on time while failing to improve decisions, or may deliver useful information at a greater cost than expected. Preserve the original assumptions alongside approved changes. Report causes and corrective actions so the organisation learns whether the problem concerned requirements, data, software, adoption or an unsupported business-case assumption.

Decision Summary