Datatypes
Name | Base Type | Description | Pedigree |
|---|---|---|---|
| Reserved100Plus | Values "100" and above are reserved for bilaterally agreed upon user defined enumerations. | Added EP-1 | |
| String | none | Alpha-numeric free format strings, can include any character or punctuation except the delimiter. All String fields are case sensitive (i.e. morstatt != Morstatt). | Added FIX.4.2 |
| MonthYear | string field representing month of a year. An optional day of the month can be appended or an optional week code. Valid formats: YYYYMM YYYYMMDD YYYYMMWW Valid values: YYYY = 0000-9999; MM = 01-12; DD = 01-31; WW = w1, w2, w3, w4, w5. | Added FIX.4.1 | |
| Price | float field representing a price. Note the number of decimal places may vary. For certain asset classes prices may be negative values. For example, prices for options strategies can be negative under certain market conditions. Refer to Volume 7: FIX Usage by Product for asset classes that support negative price values. | Added FIX.4.2 | |
| char | none | Single character value, can include any alphanumeric character or punctuation except the delimiter. All char fields are case sensitive (i.e. m != M). | Added FIX.2.7 Updated EP206 |
| Exchange | string field representing a market or exchange using ISO 10383 Market Identifier Code (MIC) values (see"Appendix 6-C). | Added FIX.4.2 | |
| Percentage | float field representing a percentage (e.g. 0.05 represents 5% and 0.9525 represents 95.25%). Note the number of decimal places may vary. | Added FIX.4.3 | |
| LocalMktDate | string field representing a Date of Local Market (as opposed to UTC) in YYYYMMDD format. This is the "normal" date field used by the FIX Protocol. Valid values: YYYY = 0000-9999, MM = 01-12, DD = 01-31 | Added FIX.4.2 Updated EP206 | |
| float | none | Sequence of digits with optional decimal point and sign character (ASCII characters "-", "0" - "9" and "."); the absence of the decimal point within the string will be interpreted as the float representation of an integer value. All float fields must accommodate up to fifteen significant digits. The number of decimal places used should be a factor of business/market needs and mutual agreement between counterparties. Note that float values may contain leading zeros (e.g. "00023.23" = "23.23") and may contain or omit trailing zeros after the decimal point (e.g. "23.0" = "23.0000" = "23" = "23."). Note that fields which are derived from float may contain negative values unless explicitly specified otherwise. | Added FIX.2.7 Updated EP206 |
| NumInGroup | int field representing the number of entries in a repeating group. Value must be positive. | Added FIX.4.3 | |
| Country | string field representing a country using ISO 3166 Country code (2 character) values (see Appendix 6-B). | Added FIX.4.4 | |
| Currency | string field representing a currency type using ISO 4217 Currency code (3 character) values (see Appendix 6-A). | Added FIX.4.2 | |
| TZTimeOnly | string field representing the time represented based on ISO 8601. This is the time with a UTC offset to allow identification of local time and timezone of that time. Format is HH:MM[:SS][Z | [ + | - hh[:mm]]] where HH = 00-23 hours, MM = 00-59 minutes, SS = 00-59 seconds, hh = 01-12 offset hours, mm = 00-59 offset minutes. | Added EP-1 Updated EP206 | |
| Qty | float field capable of storing either a whole number (no decimal places) of "shares" (securities denominated in whole units) or a decimal value containing decimal places for non-share quantity asset classes (securities denominated in fractional units). | Added FIX.4.2 | |
| Amt | float field typically representing a Price times a Qty | Added FIX.4.2 | |
| Boolean | char field containing one of two values: 'Y' = True/Yes 'N' = False/No | Added FIX.4.2 | |
| Reserved4000Plus | Values "4000" and above are reserved for bilaterally agreed upon user defined enumerations. | Added EP-1 | |
| int | none | Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). | Added FIX.2.7 Updated EP271 |
| Pattern | none | Used to build on and provide some restrictions on what is allowed as valid values in fields that uses a base FIX data type and a pattern data type. The universe of allowable valid values for the field would then be the union of the base set of valid values and what is defined by the pattern data type. The pattern data type used by the field will retain its base FIX data type (e.g. String, int, char). | Added EP-1 |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy