Futures Month Codes: Decode the Contract Without Guessing Its Expiry

The complete letter table

CME publishes the following contract month codes. Their sequence is not a set of calendar initials, so decoding a letter from memory is an avoidable source of mistakes.

Standard futures contract month letters

Month	Code	Month	Code
January	F	July	N
February	G	August	Q
March	H	September	U
April	J	October	V
May	K	November	X
June	M	December	Z

The table identifies months, not the months available for every product. A contract can list monthly, quarterly or other cycles. Check the exchange's listing schedule for the precise product and year rather than assuming that all twelve letters correspond to active contracts.

Decode a symbol in three parts

In an illustrative format that uses the product root MES, the month code Z and a two-digit year 26, “MESZ26” describes the December 2026 named MES contract. The exact spelling accepted by a trading platform may contain different separators or a one-digit or four-digit year. Treat this example as a decoding exercise, not a universal symbol string.

A one-digit year such as 6 is ambiguous outside its listing context. An archived dataset can contain several decades, so resolve and store the full year. Matching only the last character can combine contracts that are years apart.

Record exchange, product, named month, full year and the platform's instrument identifier. The product root matters as much as the suffix: ES and MES are different contracts even when their month and year match.

The named month is not an expiry formula

CME's Three-Month SOFR documentation gives a useful counterexample. Its named month identifies the start of the three-month reference period; the contract reaches final settlement after that period. Reading the letter correctly therefore does not by itself identify the month in which trading ends.

Use the product calendar for last trade, notice and settlement dates. CME's calendar field definitions distinguish these events. The companion notice and last-trade reference turns them into an operational worksheet.

Prevent a rollover mismatch

Suppose a source moves from its September contract to December while a destination still points at September. Both symbols can share the same market root, but they represent different prices, expiration rules and positions. Selling December does not simply close a September long; it can create a calendar spread.

A continuous chart adds another layer because it may splice several contracts and adjust historical prices. Do not use its label as proof of a current orderable instrument. Before a roll, reconcile open positions, pending orders and destination mappings using full identifiers. After the roll, verify actual fills and residual positions rather than inferring success from the chart's new month label.

For archived orders, preserve the original symbol string alongside its resolved fields. That makes later reconciliation possible if a vendor changes its naming format, or if the same abbreviated year is encountered in a dataset spanning multiple decades.