| Type Name | Base Type | XML builtin | XML Base | XML Pattern | Min Inclusive | Description | Pedigree |
|---|---|---|---|---|---|---|---|
| int | true | xs:integer | Added FIX.2.7 Updated EP271 | ||||
| Length | int | false | xs:nonNegativeInteger | int field representing the length in bytes. Value must be positive. | Added FIX.4.3 | ||
| TagNum | int | false | xs:nonNegativeInteger | int field representing a tag number. Value must be positive and may not contain leading zeros. | Added FIX.4.3 Updated EP271 | ||
| SeqNum | int | false | xs:positiveInteger | int field representing a message sequence number. Value must be positive. | Added FIX.4.3 | ||
| DayOfMonth | int | false | xs:integer | int field representing a day during a particular month (values 1 to 31). | Added FIX.4.1 Updated EP271 | ||
| float | true | xs:decimal | Sequence of digits with optional decimal point and sign character (ASCII characters -, 0- 9and .); 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 | |||
| Qty | float | false | xs:decimal | 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 | ||
| Price | float | false | xs:decimal | 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 | ||
| PriceOffset | float | false | xs:decimal | float field representing a price offset, which can be mathematically added to a Price. Note the number of decimal places may vary and some fields such as LastForwardPoints may be negative. | Added FIX.4.2 | ||
| Amt | float | false | xs:decimal | float field typically representing a Price times a Qty | Added FIX.4.2 | ||
| Percentage | float | false | xs:decimal | 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 | ||
| char | false | xs:string | 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 | |||
| Boolean | char | false | xs:string | [YN]{1} | char field containing one of two values: 'Y' = True/Yes 'N' = False/No | Added FIX.4.2 | |
| String | true | xs:string | 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 | |||
| MultipleCharValue | String | false | xs:string | [A-Za-z0-9](\s[A-Za-z0-9])* | string field containing one or more space delimited single character values (e.g. |18=2 A F| ). | Added FIX.4.4 | |
| MultipleStringValue | String | false | xs:string | .+(\s.+)* | string field containing one or more space delimited multiple character values (e.g. |277=AV AN A| ). | Added FIX.4.2 | |
| Country | String | false | xs:string | .{2} | string field representing a country using ISO 3166 Country code (2 character) values (see Appendix 6-B). | Added FIX.4.4 | |
| Currency | String | false | xs:string | .{3} | string field representing a currency type using ISO 4217 Currency code (3 character) values (see Appendix 6-A). | Added FIX.4.2 | |
| Exchange | String | false | xs:string | .* | string field representing a market or exchange using ISO 10383 Market Identifier Code (MIC) values (seeAppendix 6-C). | Added FIX.4.2 | |
| MonthYear | String | false | xs:string | \d{4}(0|1)\d([0-3wW]\d)? | 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 | |
| UTCTimestamp | String | false | xs:dateTime | string field representing date and time combination Universal Time Coordinated (UTC), also known as Greenwich Mean Time (GMT). Its value space is described as the combination of date and time of day in the Chapter 5.4 of ISO 8601. Valid values are in the format YYYY-MM-DDTHH:MM:SS.s where YYYY = 0000-9999 year, MM = 01-12 month, DD = 01-31 day, HH = 00-23 hour, MM = 00-59 minute, SS = 00-60 second (60 only if UTC leap second), and optionally one or more digits representing a decimal fraction of a second. The punctuation of -, :and the string value of Tto separate the date and time are required. The .is only required when sub-second time precision is specified. Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read 1998-12-31T23:59:59, 1998-12-31T23:59:60, 1999-01-01T00:00:00. (see http://tycho.usno.navy.mil/leapsec.html) | Added FIX.4.2 Updated EP256 | ||
| UTCTimeOnly | String | false | xs:time | string field representing time-only in Universal Time Coordinated (UTC), also known as Greenwich Mean Time (GMT). Its value space is described as the time of day in the Chapter 5.4 of ISO 8601. Valid values are in the format HH:MM:SS.s where HH = 00-23 hours, MM = 00-59 minutes, SS = 00-60 seconds (60 only if UTC leap second), and optionally s (one or more digits representing a decimal fraction of a second). The punctuation of :between hours minutes and seconds are required. The .is only required when sub-second time precision is specified. This special-purpose field is paired with UTCDateOnly to form a proper UTCTimestamp for bandwidth-sensitive messages. | Added FIX.4.2 Updated EP206 | ||
| UTCDateOnly | String | false | xs:date | string field representing Date represented in UTC (Universal Time Coordinated, also known as GMT) in YYYY-MM-DD format specified in ISO 8601. This special-purpose field is paired with UTCTimeOnly to form a proper UTCTimestamp for bandwidth-sensitive messages. Valid values: YYYY = 0000-9999, MM = 01-12, DD = 01-31. | Added FIX.4.4 Updated EP271 | ||
| LocalMktDate | String | false | xs:date | string field representing a Date of Local Market (as opposed to UTC) in YYYY-MM-DD format. This is the normaldate field used by the FIX Protocol. Valid values: YYYY = 0000-9999, MM = 01-12, DD = 01-31. | Added FIX.4.2 Updated EP206 | ||
| TZTimeOnly | String | true | xs:time | string field representing the time based on ISO 8601. This is the time with a Universal Time Coordinated(UTC) offset to allow identification of local time and timezone. Its value space is described as the combination of date and time of day in the Chapter 5.4 of ISO 8601. Valid values are in the format 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. The punctuation of :are required. The Zor +or -are optional to denote a time zone offset. | Added EP-1 Updated EP206 | ||
| TZTimestamp | String | true | xs:dateTime | string field representing a date and time combination in local time with an optional offset to Univeral Time Coordinated (UTC). Its vaue space is described as the combination of date and time of day in the Chapter 5.4 of based on ISO 8601. Valid values are in the fFormat is YYYY-MM-DD-THH:MM:SS.s*[Z | [ + | - hh[:mm]]] where YYYY = 0000 to 9999 year, MM = 01-12 month, DD = 01-31 day, HH = 00-23 hours, MM = 00-59 minutes, SS = 00-59 seconds, hh = 01-12 offset hours, mm = 00-59 offset minutes, and optionally sss (one or more digits representing a decimal fraction of a second), hh = 01-12 offset hours, mm = 00-59 offset minutes. The punctuation of -, :and the string value of Tto separate the date and time are required. The .is only required when sub-second time precision is specified. The Zor +or -are optional to denote an optional time zone offset. | Added EP-1 Updated EP206 | ||
| data | true | xs:base64Binary | In FIXML, all data type fields are using base64Binary encoding. | Added FIX.2.7 Updated EP294 | |||
| Tenor | Pattern | false | xs:string | [DMWY](\d)+ | used to allow the expression of FX standard tenors in addition to the base valid enumerations defined for the field that uses this pattern data type. This pattern data type is defined as follows: Dx = tenor expression for days, e.g. D5, where xis any integer > 0 Mx = tenor expression for months, e.g. M3, where xis any integer > 0 Wx = tenor expression for weeks, e.g. W13, where xis any integer > 0 Yx = tenor expression for years, e.g. Y1, where xis any integer > 0 | Added EP-1 | |
| Reserved100Plus | Pattern | false | xs:integer | 100 | Values 100and above are reserved for bilaterally agreed upon user defined enumerations. | Added EP-1 | |
| Reserved1000Plus | Pattern | false | xs:integer | 1000 | Values 1000and above are reserved for bilaterally agreed upon user defined enumerations. | Added EP-1 | |
| Reserved4000Plus | Pattern | false | xs:integer | 4000 | Values 4000and above are reserved for bilaterally agreed upon user defined enumerations. | Added EP-1 | |
| XMLData | String | false | xs:string | Added EP-1 | |||
| Language | String | true | xs:language | Added EP90 | |||
| LocalMktTime | String | true | xs:time | string field representing the time local to a particular market center. Used where offset to UTC varies throughout the year and the defining market center is identified in a corresponding field. Format is HH:MM:SS where HH = 00-23 hours, MM = 00-59 minutes, SS = 00-59 seconds. In general only the hour token is non-zero. | Added EP161 | ||
| XID | String | true | xs:ID | The purpose of the XID datatype is to define a unique identifier that is global to a FIX message. An identifier defined using this datatype uniquely identifies its containing element, whatever its type and name is. The constraint added by this datatype is that the values of all the fields that have an ID datatype in a FIX message must be unique. | Added EP161 Updated EP282 | ||
| XIDREF | String | true | xs:IDREF | The XIDREF datatype defines a reference to an identifier defined by the XID datatype. | Added EP161 |
|