Evaluating and managing financial performance: what to automate, what to keep human, and what the data needs

Software can already run cost allocations, refresh customer and product profitability, and flag new strategies drifting off plan. People still decide what the results mean and what to change. Neither works until the ledger carries customer, product and activity attributes, and cost drivers are captured consistently.

Where software and AI earn their place

The heavy arithmetic is the safest place to start. Allocating overhead to activities, pushing activity cost down to products and customers, and producing a margin by account are rule-based once the rules are agreed. A well-configured costing engine does this every close without anyone rebuilding spreadsheets.

Tracking new customer and product strategies also suits automation. Set the baseline and the expected trajectory once. After that, a system can compare actuals against both and raise an alert when a launch or a pricing change departs from what was promised.

AI adds something different. It is good at spotting patterns a fixed report misses: customers whose cost to serve climbs quietly through returns and small orders, products whose discounts creep up at quarter end, cost lines that move together in ways nobody expected. It can draft variance commentary for an analyst to edit. It can also sort a long tail of accounts into groups worth looking at.

Life cycle costing benefits too. Asset records already hold value, depreciation and impairment. A tool can roll those up with maintenance and running costs to show what a product line or a piece of equipment really costs across its life.

Where a person has to decide

Evaluating a new product rests on assumptions about volume, price, cannibalisation and how competitors respond. A model can test them. It cannot own them. Someone has to sign their name to the case and revisit it when reality arrives.

Optimising the customer and product mix is the clearest example. An optimiser will happily recommend dropping an unprofitable customer who happens to anchor a market, or a low-margin product that pulls through high-margin ones. Contracts, relationships and strategy sit outside the data. A commercial lead has to weigh them.

Choosing cost drivers is also a human call. The driver chosen decides who looks profitable. That choice is political as much as technical, and operations managers need to accept it or they will ignore the output.

Continuous cost improvement ends in conversations: with a plant manager about scrap, with procurement about a supplier, with sales about order minimums. Software points at the cost. People remove it.

What has to be true about the data

Most failed automation here traces back to the ledger. Before any tool goes live, check these conditions:

• Profitability attributes on transactions. General ledger accounts and transactions must carry the attributes profitability needs, such as customer, product, channel and, where used, activity. If those are added afterwards in a spreadsheet, the automation inherits every manual fix.
• Reconciliation to the ledger. Performance reports should trace back to general ledger balances. A profitability view that does not reconcile to the ledger loses the room the first time someone checks.
• Revenue at the right grain. Rebates, credit notes and freight need to land at line level against the right customer and product, not as a lump journal at period end.
• Stable master data. Product and customer hierarchies must stay stable, with a clear owner for changes. A reorganised hierarchy mid-year breaks trend analysis silently.
• Driver data captured consistently. Driver volumes, such as machine hours, order lines or support tickets, need a defined source system and a consistent definition across sites.
• Asset records that match. Values in the asset register must agree with the ledger before life cycle costs are trusted.

Where one of these is missing, fix it first. Automating on top of it only produces wrong answers faster.

Questions to ask the people who run it

The documented method and the working method usually part ways somewhere. These questions find where:

• Which numbers do you adjust by hand before the profitability pack goes out, and why?
• When a customer looks unprofitable, what happens next? Has anyone ever acted on it?
• Who chose the current cost drivers, and do the operations teams believe them?
• Where do rebates and credit notes actually get recorded, and how late?
• Which spreadsheet would you refuse to give up, and what does it do that the system does not?
• How do you know a new product is underperforming before the formal review says so?
• When a hierarchy changes, who tells finance, and how do you restate history?
• Which cost improvement ideas came from this analysis, and which came from someone walking the floor?

The answers to the hand-adjustment and spreadsheet questions usually show where automation will break. The answers about acting on results show whether better analysis will change anything at all.

Order of work

Start with data structure and reconciliation. Then automate allocations and the profitability refresh. Add tracking of new strategies once baselines are agreed. Bring in AI pattern detection only after the core figures are trusted. Keep mix decisions and cost improvement firmly with named owners, supported by the outputs but not replaced by them.

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.