All or nothing: product control goes global or local

Balance Sheet

ISSN: 0965-7967

Article publication date: 1 September 2004



Mainelli, M. (2004), "All or nothing: product control goes global or local", Balance Sheet, Vol. 12 No. 4.



Emerald Group Publishing Limited

Copyright © 2004, Emerald Group Publishing Limited

All or nothing: product control goes global or local

Michael MainelliExecutive Chairman, Z/Yen Limited ( Z/Yen Limited is a risk/reward management firm helping organizations make better choices. Z/Yen undertakes strategy, finance, systems, marketing and intelligence projects in a wide variety of fields (, such as developing a risk/reward prediction engine, helping a global charity win a good governance award or benchmarking transaction costs across global investment banks.

Front, back and sideways

Between the front and back offices of investment banks lie the "middle offices". Middle office functions vary from bank to bank, as does the importance and size of the middle office, but they typically include administration and support for the front office. Increasingly, the middle office is home to control functions, such as product control and risk management, that need close liaison with the front office in order to determine the accuracy of profit and loss figures or risk exposures initially provided by the front office. Product control typically provides independent price verification, position reconciliation and daily profit validation.

Investment banks have a variety of different product control or product accounting structures. Product control ranges from reporting to a single, global product control head through to being combined with other middle office functions or allocated to product lines. Research about product control is sparse. While functions defined as "product control" all exist within investment banks, the grouping of functions varies widely.

  • "We want a standardized P&L process globally. We're not there yet, but definitely moving towards it" (Global COO Product Control).

During 2003, Z/Yen conducted a survey of product control functions within nine investment banks. The survey consisted of 20 structured interviews with the heads of product control at a global or European level whose departments were called product control, business unit/area controlling or middle office, as well as an additional six other interviews with relevant experts.

The 2003 survey found a wide variety of organizational approaches to product control:

  • highly segregated product control, with an emphasis on "control", reporting to a senior head (vertical) and then through the finance function, sometimes via internal audit (four of the nine investment banks);

  • operationally integrated product control, with an emphasis on trade support, reporting to an operations head or head of finance within operations, as opposed to reporting through the finance function (two of the nine investment banks);

  • mixed, three of the nine investment banks, either segregated with trade support roles (two of the nine) or operational but largely separate at lower levels (one of the nine)

  • "There are three potential organization models of product control and market risk: (1) have all four functions separate, daily P&L, price verification, accounting, and market risk; (2) have market risk and P&L production together, and price verification and accounting together; and (3) have daily P&L, prices and accounting together, with market risk separate" (Head of Capital Markets Product Control).

Like it is

Despite the variety of organizational structures, there was relative unanimity on the "core" functions of product control and things which were definitely outside product control (see Figure 1 ). Ratios of product control staff to front-office staff ranged from 1:1 in areas such as derivatives to 1:20 for vanilla and exchange-traded products. Most organizations did not perform daily balance sheet calculations. Month-ends are a "bump" for product control, requiring extra staff overtime for periods extending from two to eight days, and typically with overtime of between two and five hours. Organizations had a variety of ways of handling 24 hour reporting, either living with different time zone data or systems of "flash" reports with later "finals" and variance explanations. A number of banks seemed to be trying to increase the skills of staff, e.g. bringing in more technical accounting expertise, while reducing the drudge through automation.

Figure 1 Agreed scope of product control

Operationally integrated organizations judged product control largely by its ability to satisfy front-office and other operational department expectations. Decisions tended to be pragmatic – "what gets the job done". Segregated organizations were clear about product control principles and had the clearest roles with clear ownership of reconciliation systems. Segregated organizations seemed to be more efficient, although efficiency observations need to be treated with caution as in mixed organizations product control tends to be "doing" more, i.e. control functions with trade support. There was little correlation between the amount of proprietary trading and structure. More than half of participants were looking seriously at major restructuring of product control with some segregated organizations looking at moving operational and vice versa.

  • "If you organize horizontally then your main concern is in supporting the business, if you organize vertically then you are more concerned with controlling the business" (Head of Equity Product Control).

  • "You can be organized functionally or business aligned, both structures have their benefits and in our opinion you should cycle between the two, probably every two to three years" (Head of Fixed Income Product Control).

Everyone had a strong emphasis on product control management by headcount. Few organizations manage product control operations with key performance indicators (KPIs). Only one organization was managing product control based on quality measures. Bonuses for product control staff seem to be largely discretionary, rather than based on quantitative measures. Measuring product control's success was widely seen as difficult, although everyone seemed to have given this much thought, for instance the number of late P&L's, the number of unexplained items, reconciliation breaks, price testing differences, etc. Organizations did not feel that cost was strongly related to trading volumes or currencies or locations, but did feel that costs were driven by some factors almost wholly outside their control, such as the number of product types traded, the complexity of products (especially derivatives), the number of legal entities or the number of regulators.

There seemed to be great interest in attempting to benchmark product control by some common numerators such as headcount or cost, if it were possible to agree on some common denominators, but there seemed to be problems with most suggestions for a denominator, e.g. cost or headcount per book, per P&L, per trader, per unit revenue, per transaction, per system interface or per legal entity? According to one interviewee "if you want to reduce headcount, then reduce the number of businesses you are in". Organizations did feel that they could reduce costs if they could automate P&L production and decomposition, otherwise most savings would be "merely better management". Re-engineering product control ultimately depends on automation.

Product control systems were highly customized or bespoke, although naturally popular database packages or semi-customized general ledger packages underlay them. Some participants felt that an efficient product control system provided competitive edge. Technology had produced the most savings in product control when it either increased automation, particularly having a global product control reporting and decomposition system, or increased the use of straight through processing (STP) – "I don't see how anyone can make real reductions in product control costs without a global product control system".

Get a grip on the big picture details

The stepping-stones to successful product control appear to be:

  • Clear decisions on segregated versus operational model: the clearer the choice of model, the less likely product control is going to be divided both in operations but also loyalties.

  • Commitment to lines of business: product control performs better where the business realizes that essential product control is a significant, unavoidable fixed cost for operating a business line rather than something that can be skimped on at early stages. Product control cost savings are best realized by exiting a business line – volume reductions have much less effect.

  • Clear responsibility and reporting lines: shared functions, e.g. a bit of P&L production, as well as unclear reporting lines, e.g. head of operations but dotted lines to X and Y, impede effective performance of product control.

  • Standardization: leading product control functions emphasize the importance of a single approach to P&L production, standardized processes, standardized relationships with trading and operations colleagues, and increasing the inter-operability of product control staff. Standardization leads to simplification.

  • Automation: the biggest differentiator among participants was the presence (or absence) of a global product control system producing all P&Ls in a standardized manner. With a global product control system, inter-operability was high, product control could do more advisory analysis and efficiencies were greatly increased.

  • "Previously only at an extremely senior level of management did the full life cycle from trade capture through to reporting come under one umbrella, this has now moved down to VP level within the Bank. This has led to a significant improvement in communication and a large decrease in duplication of effort" (Global Head of Equity Product Control).

Longer-term however, the structure of product control may be determined more by outsiders than management. In the future, regulatory trends indicate that product control is likely to be split decisively between the front-office support functions and imposed controls, typically those undertaken within risk management or internal audit. If this is the case, then the views of one interviewee ring true – "We don't see ourselves as trade support; our first and foremost role is as controllers; product control's decision is final". Whatever the final outcome, the message is that clarity matters – either product control is a global control function or it is a local trade support function. Where a clear decision is made, performance is enhanced.

Related articles