Futures Contract Month Codes Explained: How to Read Futures Symbols

In a common display convention, the root identifies the futures product, the next letter identifies the contract's month code, and a number identifies the year. CME's educational E-mini S&P 500 example uses ESF9 for a January 2019 contract: ES is the example product code, F is January, and 9 identifies the year in that example.

This pattern is useful for decoding a display, but it is not a universal ticker grammar. CME notes that product codes and display formats can vary by asset class and trading platform, and a year suffix can be shown differently by a broker or data vendor. Treat a familiar root-plus-letter string as a prompt to verify the venue's exact symbol rather than as proof that another platform will accept it.

Futures contract roll mechanics explains why both named months must be identified before a roll. A month letter helps distinguish those contracts; it does not decide which one to trade or when to roll.

CME's month-code list maps January to F, February to G, March to H, April to J, May to K, June to M, July to N, August to Q, September to U, October to V, November to X, and December to Z.

The mapping decodes the letter, not the product's listing schedule. Some products list only selected quarterly or serial months, while others can have a different set of available months. A correct reading of Z as December does not establish that a December contract is currently listed, liquid, or the next active contract.

Futures calendar spreads uses two separately named contract months. Decode each leg independently before assuming a spread's near and far dates, multiplier, or liquidity are the same as another product's.

The letter is an identifier in a contract code. It is not a promise that trading continues through the last calendar day of that month, nor does it reveal a first notice day, final settlement method, or delivery obligation. Those events come from the exact product specification and calendar.

For a physically delivered contract, notice and delivery dates can matter before or around the final trading process. For a cash-settled contract, a product-defined final calculation and time can matter instead. First notice day and last trading day separates these lifecycle dates from the shorthand used to name a month.

The same distinction matters after an option event. Options on futures expiration versus futures expiration shows why an option's deadline and the specifically named futures contract's lifecycle are separate questions.

Contract names are product-defined. CME's Three-Month SOFR futures provide a useful reason not to turn a month letter into a universal expiry date: the contract name uses the month in which its reference period begins, while trading terminates and cash settlement follows later in its delivery month. CME's September 2026 example is named SR3U6 because the reference period begins in September, even though its described trading termination and final settlement occur in December.

That example does not make all month letters ambiguous. It shows why the code must be read with the product specification. Before entering, rolling, or comparing a contract, record the exchange and platform symbol, product root, named month and year, current listed series, last-trading time, notice or delivery path where relevant, final-settlement method, and broker cutoff.

This is a symbol-reading guide, not an instruction to trade or roll a futures contract. Current exchange specifications and broker procedures govern an actual order.