What does MIC stand for?
| Full form | Market Identifier Code |
|---|---|
| Category | Finance & economics |
| Type | Initialism |
The initialism MIC stands for Market Identifier Code in financial-market data. ISO 10383 codes identify exchanges, trading platforms and other covered market or reporting facilities.
A market-data record can contain several identifiers with different roles. The MIC identifies the named market; its operating MIC identifies the operating parent when the record describes a market segment. The registration authority’s factsheet distinguishes OPRT and SGMT as record types and keeps MIC, legal entity name, LEI, status and dates in separate fields. A code is therefore not a substitute for every identifier of a company or financial instrument. Its four-character uppercase-letter/digit format is a structural rule, not proof that an invented string is registered. Read the actual parent field too: two visually similar codes do not establish a parent relationship. In an original fictional dataset, suppose C0D1 is labelled SGMT with operating MIC C0DA. A summary should retain C0D1 as the segment and C0DA as its stated parent; it should not replace the segment identifier with the parent or invent a second parent from a matching prefix. Also retain the date and status attached to the record. A publication date and a modification’s implementation date are distinct fields in the authority’s release material. This guide explains how to read those relationships; it does not supply a current registry lookup or decide which identifier a particular regulatory filing requires. In a fictional snapshot dated 6 May2028, a segment marked expired should remain described as expired in that snapshot. Its operating-parent identifier does not supply a second, independent status record for the parent.
Meaning in context
- Market
- The exchange, platform, market or reporting facility identified in the relevant record.
- Identifier Code
- The MIC field is distinct from its operating-parent relationship, an LEI or an instrument identifier.
Practical examples
Retain the parent relationship
- Before
Invented row: MIC C0D1; type SGMT; operating MIC C0DA. Draft: C0D1 is the parent because its code looks similar.
- After
The fictional row identifies C0D1 as the segment and C0DA as its operating parent.
The type and explicit operating-parent fields establish the roles in this invented dataset; the appearance of the strings does not.
Keep dates with their roles
- Before
Invented release note: publication 4 April 2028; modification implementation 18 April 2028. Draft: The change took effect on publication.
- After
The fictional note lists publication on 4 April and implementation on 18 April 2028.
The two supplied dates describe different events. The example does not promise a real registration-authority release date.
Original illustrative examples, not quotations or reports of actual events.
Read the market identifier fields
Which MIC identifies a segment, which identifies its operating parent, and what does a valid-looking code actually prove?
See all guidance
Read a segment row
Keep the MIC and operating MIC together.
The fictional SGMT row C0D1 names operating parent C0DA.
Check a string
Separate structural format from registration evidence.
Four allowed characters alone do not establish an active registry record.
Record a change
Retain status and each date label.
Publication and implementation are separately supplied dates.
Read the code, record type, explicit operating parent, status and dates as separate fields; valid-looking syntax does not confirm a registered market.
Help improve this entry
Spot a mistake or have a clearer example? Suggest a change.
By AcronymIndex Editorial Team · Editorial policy