Who knows what in financial performance management, and where it breaks

Accountants know how a number was booked and adjusted. The people selling and making things know why it happened. Customer and product profitability goes wrong where those two kinds of knowledge never meet. Cost improvement stalls when savings cannot be traced back to the ledger.

The management accountant

This role builds the profitability views, the activity-based measures and the cost models behind new product cases. It knows which allocation keys were chosen and why. It also knows which ones were a compromise made under deadline and never revisited.

What it often lacks is a feel for the work itself. An allocation based on order lines looks sensible until someone explains that one customer's orders take an afternoon of manual checking while another's flow straight through. The accountant sees the driver. It rarely sees the exceptions.

The general ledger team

The ledger team knows things nobody else does about the timing and shape of the numbers. It knows which accruals were estimates, which manual journals moved cost between cost centres after the fact, and which depreciation charges sit in a department that no longer uses the asset. It knows whether the account attributes needed to report by product or channel were ever set up, or whether analysts rebuild that split by hand every period.

This matters because a profitability report is only as clean as the postings underneath it. A late reclass can make a product line look worse in one period and better in the next. Analysts who never see the journal detail will explain that swing with a story about the market.

Sales and account management

Commercial staff know what was actually agreed with each customer. That includes free freight, extended payment terms, volume rebates settled as credit notes months later, and service promises that never reach a contract. Much of this lands in finance as payment adjustments or deductions with thin descriptions.

So the margin a salesperson believes in and the margin finance reports can differ sharply. Neither side is lying. Each is missing half the picture.

Operations and supply

Operations knows where effort really goes. It knows which products need special setups, which customers trigger expediting, and where rework hides inside standard labour. This is the raw material for activity-based costing. It is seldom written down, and it shifts whenever a line is rebalanced or a supplier changes.

Operations also knows the end of a product's life in practical terms: obsolete stock, tooling that must be scrapped, warranty work that drags on. Life cycle costing that ignores this view tends to stop at launch and steady state.

Product management

Product owners hold the assumptions behind each launch case. Those include expected volume, price position and cannibalisation of older lines. They also know which assumptions were optimistic to get approval. Once the product is live, those assumptions are rarely compared with actuals, because the tracking codes needed to isolate the new product were not set up in time.

Where the gaps cause real damage

Mix decisions are the most exposed. A customer or product can be dropped because it looks unprofitable, only for its share of fixed cost to land on everything else. The accountant may suspect this. Operations knows it. The decision is often taken in a meeting where neither is present.

Cost improvement programmes suffer a quieter problem. Operations reports a saving, finance cannot find it in the ledger, and trust erodes on both sides. Usually the saving was real. It sat in a cost centre nobody tracked, or an accrual reversal masked it.

New strategy tracking fails at setup. If general ledger attributes for a new segment or product are not in place before transactions start posting, history cannot be rebuilt cleanly. Every later report becomes an estimate.

Finally, reports sent to business owners are rarely tied back to ledger balances in a way the recipient can see. When a manager finds a number that looks wrong, there is no easy path to check it. The report gets ignored.

Questions to ask the people who run it

Written procedures describe the intended flow. These questions tend to surface the real one.

• Which allocation keys would be changed tomorrow if there were time, and why have they stayed?
• Which manual journals recur every period, and who asks for them?
• How do rebates, credits and deductions reach customer margin, and how late do they arrive?
• Which customers or products take far more handling than the cost model assumes?
• When a new product launched, was a code or attribute created for it before the first sale posted?
• Who last compared a launch case with what actually happened?
• When operations claims a saving, how does finance confirm it, and what happens when it cannot?
• Which profitability figures can be traced to ledger balances, and which are rebuilt in spreadsheets?
• Who is in the room when a decision to drop a customer or product is made?
• What does each team believe the others already know?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.