How evaluating and managing financial performance runs, step by step

Financial performance evaluation runs as a loop. Finance first makes the ledger capable of carrying cost and revenue by customer and product. Analysts then measure profitability and test new offerings. They cost those offerings over their whole life, adjust the mix and track results. Proven savings feed the next round.

The steps in order

1. Set up the ledger to hold the right attributes. A general ledger accountant maintains the account structure and the attributes that tag each transaction to a product line, customer segment or activity. The controller approves changes. If the tags are missing or applied loosely, every later step inherits the gap.

1. Post transactions and allocations. Ledger accountants post what flows in from billing, payables, payroll and inventory. Shared costs, such as facilities or support teams, need a different route. Cost accountants prepare manual journal entries to spread those costs and send them to the controller for sign-off before posting.

1. Bring in asset and capacity costs. The fixed asset accountant supplies asset values, depreciation and any impairment, split by the product line or site that uses each asset. This matters more than it looks. Life cycle costing and activity rates both depend on knowing what equipment really costs to own.

1. Assess customer and product profitability. An FP&A analyst or cost accountant builds the margin view. Revenue, direct cost and allocated overhead line up against each customer and each product. Before anyone sees it, the analyst ties the totals back to ledger balances. Unreconciled profitability reports lose credibility fast.

1. Evaluate new product proposals. A product manager brings the business case. A finance analyst challenges the volume, price and cost assumptions and adds the overhead the proposer usually leaves out. The finance lead signs off on the numbers. The final go or no-go normally sits with an executive or investment committee.

1. Perform life cycle costing. For products that pass, a cost accountant works with engineering or operations to estimate spending from design through launch, support and eventual retirement. Warranty, spare parts and disposal often surface here for the first time.

1. Optimize the customer and product mix. Commercial leaders own this decision. Finance supplies scenarios showing what happens if a weak product is repriced, a small account is moved to a cheaper service model, or a line is dropped entirely. Sales input is essential, since a loss-making product sometimes anchors a profitable relationship.

1. Track new customer and product strategies. At agreed review points, the analyst compares actual results with the original case. The product owner explains the variances. Where results fall well short, the case goes back to the committee that approved it.

1. Prepare activity-based performance measures. Cost accountants calculate cost per driver, such as cost per order handled or per machine hour. Operations managers confirm the drivers reflect how work really happens on the floor. Without that confirmation, the rates look precise and mislead.

1. Report to business leaders. FP&A distributes profitability, activity cost and strategy tracking reports to department heads and product owners. Every figure should trace to a ledger balance. Many teams also offer a self-service view where managers can cut the data their own way.

1. Manage continuous cost improvement. Operations owners run the improvement actions: process redesign, supplier changes, automation. Finance verifies the claimed savings in posted results before they count. Confirmed savings update the cost base, and the loop starts again at profitability.

Where practice drifts from the documented version

The written process usually shows finance driving everything. In reality, steps 7 and 11 depend on commercial and operations staff who may not see themselves as part of a finance process at all. Handoffs between the analyst and those owners are where work stalls.

Allocation logic is another weak spot. It often lives in a spreadsheet maintained by one person, with rules that nobody has reviewed since they were written.

Strategy tracking also tends to fade. Once a launch happens, attention moves on, and the comparison to the original case quietly stops.

Questions to ask the people who run it

• Which attributes on a transaction are actually reliable, and which ones get filled with a default value?
• Where do the allocation rules live, and who last changed them?
• When a profitability report does not tie to the ledger, what happens? Does it go out anyway?
• Who really decides to approve a new product, and does the finance view change that decision?
• Are life cycle costs estimated for every launch, or only the large ones?
• When a mix change is proposed, who in sales gets consulted, and at what point?
• Has any approved product case ever been formally revisited after launch?
• Do operations managers trust the activity drivers, or do they keep their own numbers?
• How are cost savings confirmed, and who has the authority to reject a claimed saving?
• Which reports do managers actually open, and which ones go unread?
• What workaround would break first if this process changed?

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.