← Glossary

Devancore Post-Trade Glossary

Classification of Financial Instruments (CFI)

The ISO 10962 six-character code that classifies an instrument’s type and attributes for settlement, tax, corporate actions, controls, and reporting.

Definition

What is Classification of Financial Instruments?

The Classification of Financial Instruments code, usually called CFI, is the ISO 10962 classification code for financial instruments. It is a six-character code that describes the broad category, more specific group, and instrument attributes that help systems understand what kind of financial instrument they are processing.

CFI is not the same thing as an identifier. An ISIN or CUSIP points to a specific security. A FIGI can help map instruments across venues and sources. A legal entity identifier identifies an issuer, counterparty, or legal entity. A MIC identifies a market or venue. CFI does something different: it classifies the instrument’s structure.

That distinction matters. A post-trade platform does not only need to know which instrument a trade references. It also needs to know how that instrument behaves. Does it pay dividends or coupons? Does it mature? Does it have an exercise event? Does it create proxy-voting rights? Does it have fund distribution character? Does it require derivative margin logic? Does it need corporate action processing? Does it need special tax handling?

CFI gives the instrument master a structured starting point for those decisions.

CFI structure

CFI is a six-character classification code, not a unique instrument identifier.

Position Meaning Operational use
1 Category Routes to broad family such as equity, debt, fund, option, future, swap, right, or other
2 Group Refines the category into a more specific instrument group
3 Attribute 1 Category-specific attribute used for operational classification
4 Attribute 2 Category-specific attribute used for settlement, control, or reporting logic
5 Attribute 3 Category-specific attribute used for lifecycle or eligibility logic
6 Attribute 4 Category-specific attribute used for final routing or review context

The first character of a CFI code identifies the broad category. Public examples commonly include equity, debt, collective investment vehicles, options, futures, swaps, rights, and other categories. The second character identifies the group inside that category. The remaining four characters are attributes whose meaning depends on the category and group.

The exact production meanings of CFI group and attribute values should come from an approved and current CFI table. The full ISO value tables are licensed material. A public implementation should avoid copying licensed tables and should instead define parser structure, validation rules, routing concepts, and approved internal mappings.

CFI versus instrument identifiers

CFI classifies the instrument. Identifiers point to the instrument.

Data type Example Primary role
CFI ISO 10962 classification Classifies structure and attributes
ISIN ISO 6166 identifier Identifies a security for global reporting and settlement
CUSIP North American security identifier Identifies US and Canadian securities
FIGI Open financial instrument identifier Maps cross-asset instruments and listings
MIC ISO 10383 market identifier Identifies venue or market segment
LEI ISO 17442 legal entity identifier Identifies issuer, counterparty, or legal entity

CFI is powerful because it is compact, structured, and machine-readable. But it should never be used alone. It should be joined with the instrument master, issuer LEI, country, currency, MIC, market master data, tax source evidence, and lifecycle terms before the platform makes production decisions.

The right mental model is simple: CFI is a routing signal. It is not the whole record.

How it works

How CFI works in post-trade systems

The first step is intake. CFI may arrive from a numbering agency, reference-data vendor, exchange source, issuer file, instrument master feed, or internal enrichment process. The system should normalize the value by trimming whitespace, uppercasing it, and confirming that the value is six alphabetic characters.

The second step is validation. A missing CFI may be acceptable for some instruments if the source does not provide one, but the instrument should be marked as classification-incomplete. A malformed value should not silently flow into tax, settlement, or reporting logic. It should be quarantined or routed to instrument master data exception review.

The third step is parsing. The parser separates the value into category, group, and four attribute positions. This is deterministic. The parser does not need to understand every official attribute meaning to preserve the code and classify the high-level category where safe.

The fourth step is resolution. The category, group, and attributes should be resolved against an approved table. If only a public-safe high-level category map is available, the system can route to a broad family with lower confidence. It should not claim exact official attribute meanings without a licensed, approved, and current table.

CFI-driven routing examples

CFI is useful because it changes the workflow a system should expect.

CFI category signal Likely family Workflow impact
Equity Common stock, preferred stock, depositary receipt, REIT Dividend processing, proxy voting, corporate actions, capital gains, transaction taxes
Debt Bond, note, treasury bill, commercial paper Coupon processing, accrued interest, maturity redemption, interest withholding
Collective investment vehicle Mutual fund, ETF, ETP Fund distributions, NAV cycle, creation/redemption, mixed tax character review
Option Listed or OTC option Premium settlement, exercise, assignment, expiry, derivative gain/loss treatment
Future Listed future Margin, variation settlement, expiry, physical or cash delivery
Swap Swap or credit default swap Cash-flow settlement, collateral, valuation, credit-event processing
Right or entitlement Warrant or subscription right Exercise, expiry, corporate action adjustment, eligibility review

The fifth step is routing. Equity-like instruments can route to dividend, proxy-voting, and corporate-action workflows. Debt instruments can route to coupon, accrued-interest, maturity, and interest-withholding workflows. Collective investment vehicles can route to fund-distribution and tax-character workflows. Options, futures, swaps, and rights can route to derivative lifecycle workflows.

The sixth step is joining. CFI becomes production-useful when it is joined to other governed data: ISIN, CUSIP, FIGI, issuer LEI, MIC, country, currency, settlement infrastructure, tax source evidence, and market master data. This join prevents overreach. A CFI category may tell the system that an instrument is debt-like, but withholding treatment depends on country, treaty, issuer, investor, documentation, and instrument terms.

This is where CFI becomes a control. It helps the system detect mismatches. If an instrument is classified as equity but the income workflow is routing it to coupon interest, that is a review event. If a security is classified as a collective investment vehicle but the system treats every distribution as a simple dividend, that is a review event. If a derivative category appears in a workflow that expects cash equity settlement, that is a review event.

CFI is not only about classification. It is about preventing the wrong operating model from attaching to the wrong instrument.

In Devancore™

CFI in Devancore

Devancore treats CFI as a governed routing signal inside the broader instrument and market intelligence layer. The code is parsed, validated, mapped to a Devancore instrument family, and joined with the full operating record before it drives settlement, tax, control, or reporting behavior.

In the instrument master, CFI helps classify the economic structure of the instrument. An equity category can route the record toward dividend, proxy, corporate-action, and capital-gains workflows. A debt category can route the record toward coupon, accrued-interest, maturity, and redemption workflows. A collective-investment-vehicle category can route the record toward fund-distribution and tax-character review. A derivative category can route the record toward premium, margin, exercise, expiry, collateral, or cash-flow logic.

In trade enrichment, CFI helps detect whether the incoming trade has the right downstream operating path. A trade may arrive with an ISIN, CUSIP, FIGI, venue, counterparty, and price. Devancore can enrich the trade by joining those identifiers to the instrument master and then using CFI as one signal for settlement and lifecycle routing. This supports trade enrichment automation without relying on ticker text, manual asset-class labels, or free-form descriptions.

In tax and income processing, CFI helps select the first workflow but does not decide the final answer. Equity distributions, debt coupons, fund distributions, and derivative payments can have materially different tax treatment. CFI can route the item to the correct review path. Final treatment still depends on issuer country, investor country, treaty position, documentation, distribution character, beneficial-owner status, and firm policy.

In controls and supervision, CFI creates useful exception logic. If a record has a malformed CFI, unknown category, category-source conflict, or mismatch against instrument terms, Devancore can route it to review before downstream processes consume it. If a debt category appears in a sanctions-sensitive context, the system can trigger debt-specific maturity, issuance-date, or sectoral-restriction checks where applicable. If a fund classification appears, the system can trigger domicile, fund type, distribution character, and investor eligibility review.

In reporting and books, CFI helps keep accounting book of record, IBOR, regulatory reporting, and operational controls aligned. The same instrument family should not be treated as equity in one system, debt in another, and unknown in a third. Devancore’s goal is not to make CFI the sole truth. The goal is to make CFI part of a traceable, reviewable classification stack.

The conservative rule is the right rule: parse deterministically, resolve from approved tables, preserve source evidence, flag uncertainty, and never let a classification code override the full instrument record.