The New Product Approval Process

The New Product Approval Process (NPAP) — sometimes called the New Business Committee, New Product Committee, or Product Launch Committee — is the governance mechanism through which a bank formally evaluates and approves the commencement of activity in a new product, market, or legal entity. It exists because trading a product that the bank is not fully prepared to handle — from a legal, risk, operational, and financial perspective — creates risks that can far outweigh any commercial benefit.

The NPAP is not an internal bureaucracy created to slow down traders. It is a genuine risk management tool, and the consequences of bypassing it can be severe. Several major losses in banking history have been attributed in part to inadequate product approval processes — where complex instruments were traded without the operations teams, risk models, or legal documentation being properly in place.

A new product approval is required in any of the following circumstances:

• New instrument type: trading a financial instrument that the bank has not previously traded. This could be a new derivative structure (a new type of exotic option, a new index product, a new CLO structure), a new asset class (a bank's rates desk beginning to trade commodity derivatives), or a variation on an existing instrument that introduces meaningfully different risks or legal terms.
• New market or jurisdiction: entering a market in a new country where the bank has not previously operated. This introduces new legal frameworks, regulatory requirements, tax treatments, and potentially new settlement systems that must all be assessed before trading begins.
• New legal entity: using a new legal entity — a newly established subsidiary, a branch in a new jurisdiction, or a special purpose vehicle — to transact in products that are already traded elsewhere in the group. The legal entity's regulatory permissions, capital adequacy, and operational connectivity must all be established before it can trade.
• New counterparty type: in some banks, trading with a new category of counterparty (for example, beginning to trade directly with retail investors, sovereign wealth funds, or municipal entities) also requires a review, particularly of the regulatory obligations that apply to the client relationship.

The NPAP committee brings together senior representatives from every function that must approve the new activity. Typical committee members include:

• Front office sponsor: the trading desk head or business manager sponsoring the new product. Presents the commercial case — why the bank should trade this product, what the expected revenue is, what clients have expressed demand, and what the competitive landscape looks like.
• Market risk: confirms that the bank's risk models can capture and measure the new product's risk. For a standard vanilla swap, this is trivial — the risk is well-understood and models are established. For a complex exotic option, market risk must confirm that it has a calibrated pricing model, validated risk sensitivities, and appropriate limit frameworks. If the risk cannot be modelled adequately, the product cannot be approved.
• Credit risk: confirms that counterparty credit exposure can be measured (PFE — potential future exposure), that credit limits can be allocated, and that the appropriate legal documentation is in place (ISDA Master Agreement, CSA, clearing agreements where mandatory).
• Legal: confirms that the bank has the legal authority and appropriate documentation to enter into the transaction. For derivatives, this means ISDA documentation. For securities, appropriate custody arrangements. For new jurisdictions, legal opinions on the enforceability of netting and close-out provisions.
• Compliance: confirms that the product meets all applicable regulatory requirements. Is it subject to mandatory clearing? Is it subject to mandatory trading venue requirements (MiFID II)? Are there reporting obligations? What licensing does the bank need to sell this product to clients in this jurisdiction?
• Operations: this is often the most time-consuming part of the NPAP. Operations must confirm that it can confirm, settle, and manage the lifecycle of the new product. This includes: the product must be bookable in the trading system; confirmation must be possible (via MarkitWire, a bespoke template, or some other means); settlement instructions must be available; lifecycle events must be processable. If the operations team cannot handle the product, it cannot be approved — and "we'll deal with it manually" is not a satisfactory answer.
• Finance/Product Control: confirms that the P&L can be independently priced and attributed, that the relevant accounting treatment under IFRS 9 has been determined, and that regulatory reporting (both for trading book capital and for trade repository reporting) is in place.
• Technology: confirms that the systems changes needed to support the new product have been scoped, budgeted, and scheduled. If new system configurations or interfaces are needed, technology confirms the timeline.

Operational readiness is the most critical gate in the NPAP for complex or novel products. The operations function must demonstrate, before the first trade is done, that it has the processes and systems in place to handle the product through its entire lifecycle — from trade capture through confirmation, clearing (if applicable), settlement, lifecycle events, and eventual termination.

For established products, this is straightforward — the infrastructure already exists. For new products, achieving operational readiness may require:

• New product configurations in MUREX or the relevant trading system
• Development of bespoke confirmation templates (if electronic confirmation is not available)
• Training for settlement and lifecycle management teams
• Testing of system interfaces — particularly between the front-office booking system and the back-office settlement system
• Establishing SSIs with new counterparties or settlement agents

Operational readiness sign-off is binary: either operations can handle the product, or it cannot. Conditional approvals — "we can trade up to a limited volume while we build the infrastructure" — are sometimes granted for lower-complexity products but are avoided for complex structures where manual handling creates unacceptable operational risk.

Many NPAP approvals include a sunset clause — a provision that the approval lapses after a defined period (typically 12 or 24 months) if the bank has not actually begun trading the product, or if trading has been at negligible volumes. The sunset clause ensures that the NPAP database does not accumulate a large number of theoretical approvals for products that are never actually traded, and that if a product is revisited after a significant gap, it is re-reviewed to ensure the regulatory and operational environment has not changed in the interim.

Sunset clauses also serve a portfolio management function: they force the front office to prioritise which products they genuinely intend to pursue and encourage the bank to sunset product lines that are no longer commercially viable rather than maintaining the overhead of keeping their infrastructure current.

The importance of a robust NPAP was illustrated by several pre-2008 losses where banks began trading complex structured products without fully understanding the risk or having the infrastructure to manage them. Collateralised Debt Obligations (CDOs), synthetic CDOs, and correlation products were in some cases approved and traded without adequate risk models, without operations teams that understood the product's lifecycle events, and without legal teams that had reviewed the full documentation framework. The resulting losses — both from risk miscalculation and from operational failures — contributed to the view that NPAP governance must be genuinely rigorous, not a rubber-stamping exercise.