3.4 Stakeholder Communication, Sources & Information Integration

Start with the Decision and the Stakeholder

Module 2 requires more than recognising information-system names. A management accountant must establish what a stakeholder will decide, which information can change that decision, and how the information should reach them. A beautifully formatted report can be useless if it arrives after a supplier order is committed or answers a question the manager cannot act on.

For each request, document the user, decision, alternatives, time horizon, deadline and materiality. Ask what evidence would cause the user to choose differently. A production supervisor deciding tomorrow’s shift needs detailed availability and quality information. A lender evaluating covenant headroom needs contractual definitions, forecast debt and reliable cash assumptions. The board deciding whether to enter a market needs scenarios, competitor evidence and strategic risks. These requirements can draw on the same underlying data while requiring different aggregation and communication.

Manage Stakeholder Relationships

Stakeholder management includes identifying legitimate interests, understanding influence and involving the right people in requirements and interpretation. A power–interest map is a useful starting tool: engage closely with stakeholders whose decisions materially affect the project, keep others appropriately informed, and provide routes for affected users to challenge assumptions. Low formal power does not remove an employee’s, customer’s or community’s legitimate interest.

Interview users separately before assuming their requests agree. Sales may define success as orders won, operations as accepted units shipped, and finance as revenue recognised. Record the conflict instead of allowing the loudest stakeholder to define everyone’s report. The accountant acts as a translator and constructive challenger, not an advocate for whichever manager requested the analysis. Explain why a definition serves the decision and obtain agreement from the accountable owner.

Source, Aggregate and Integrate

Information may come from the general ledger, transaction records, operational sensors, customer relationship systems, surveys, supplier quotations and external industry publications. Internal records offer detail and control history but may omit competitor changes. External sources widen perspective but introduce differences in coverage, incentives and reliability. A supplier quote is evidence of an offered price under particular terms, not proof of future delivered cost.

Use the following integration sequence:

1. Establish definitions and units: orders, accepted units, revenue and cash are different measures.
2. Check scope: entities, products, geographic markets and excluded transactions.
3. Match timing: order date, dispatch date, acceptance date and accounting period.
4. Reconcile identifiers: customer and product master records, currencies and duplicates.
5. Trace transformations: exclusions, exchange rates, estimates and allocation rules.
6. Reconcile totals to a controlled source and retain a bridge explaining differences.

A shared data dictionary should state each measure’s definition, source, owner and update frequency. Drill-down access should allow authorised reviewers to trace an aggregate to the supporting records. Access controls and confidentiality still apply when the business wants faster information.

Worked Reconciliation: Conflicting Sales Reports

Assume a fictional equipment distributor’s sales dashboard reports 1,200 orders worth AUD 960,000 for September. Finance reports AUD 820,000 revenue. Before claiming an error, the accountant obtains transaction details. Of the dashboard total, AUD 100,000 relates to October deliveries not yet recognised as revenue, and AUD 40,000 relates to cancelled orders. All remaining orders meet the stated recognition assumptions. The bridge is 960,000 − 100,000 − 40,000 = 820,000.

The two reports can both be correct for different purposes. Sales uses gross bookings to monitor its pipeline; finance uses recognised revenue. For a September performance report, define net bookings as AUD 920,000 after cancellations and show AUD 100,000 awaiting delivery separately. For a cash forecast, neither bookings nor revenue is automatically the collection amount: apply invoice terms and collection assumptions.

Suppose an external market report suggests 8% growth but covers consumer devices, while this business sells hospital equipment. Averaging that figure with the distributor’s own growth rate would not reconcile the scope difference. Find a comparable market segment, explain the limitation, or use a transparent sensitivity range. More data do not cure an incompatible definition.

Communicate to Influence Responsibly

A useful recommendation states the decision first, the evidence supporting it, the alternatives considered and the material uncertainty. For the distributor, say that September revenue reconciles to bookings after timing and cancellations; do not merely attach two spreadsheets. Show the bridge in a small table and name the owner responsible for cancelled-order updates. Offer operational users transaction-level exceptions while giving the board aggregate trends and risks.

Choose the delivery channel for the user and urgency. A routine dashboard suits recurring monitoring, a short discussion helps interpret an unfamiliar model, and an exception alert suits an immediate control breach. Confirm understanding through questions about the decision, rather than assuming distribution equals comprehension. Agree a feedback loop so changing decisions lead to revised requirements.

An exam response should identify the stakeholder’s actual decision and trace information quality to its consequence. State whether the evidence is verified, estimated or unavailable. Avoid presenting false certainty to influence acceptance: candid limitations build the trust needed for the accountant to act as a business adviser.