Skip to content

FIX MESSAGE 35=BQ

SettlementObligationReport

MsgType (35) = BQSettlementInstructionAdded FIX.5.0

Definition

The Settlement Obligation Report message provides a central counterparty, institution, or individual counterparty with a capacity for reporting the final details of a currency settlement obligation.

Message structure 192 distinct fields

Source order, including nested components and groups. Group counts precede the repeated entries. “Required here” is relative to the enclosing component or group, not unconditional in the message. A dash means not marked required; conditional requirements remain in the source notes. This is a reference, not a counterparty-specific validator.

  1. StandardHeaderComponentRequired

    MsgType = BQ

    1. 8 BeginStringStringRequired here

      FIXT.1.1 (Always unencrypted, must be first field in message)

    2. 9 BodyLengthLengthRequired here

      (Always unencrypted, must be second field in message)

    3. 35 MsgTypeStringRequired here

      (Always unencrypted, must be third field in message)

    4. Indicates application version using a service pack identifier. The ApplVerID applies to a specific message occurrence.

    5. Used to support bilaterally agreed custom functionality

    6. 49 SenderCompIDStringRequired here

      (Always unencrypted)

    7. 56 TargetCompIDStringRequired here

      (Always unencrypted)

    8. Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    9. Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    10. 90 SecureDataLenDeprecated FIXT.1.1Length

      Required to identify length of encrypted section of message. (Always unencrypted)

    11. 91 SecureDataDeprecated FIXT.1.1data

      Required when message body is encrypted. Always immediately follows SecureDataLen field.

    12. 34 MsgSeqNumSeqNumRequired here

      (Can be embedded within encrypted data section.)

    13. (Can be embedded within encrypted data section.)

    14. Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    15. "ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)

    16. Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    17. Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    18. Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    19. Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    20. Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    21. 43 PossDupFlagBoolean

      Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)

    22. 97 PossResendBoolean

      Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)

    23. 52 SendingTimeUTCTimestampRequired here

      (Can be embedded within encrypted data section.)

    24. 122 OrigSendingTimeUTCTimestamp

      Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)

    25. Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)

    26. Can contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) See Volume 1: FIXML Support

    27. Type of message encoding (non-ASCII characters) used in a message's "Encoded" fields. Required if any "Encoding" fields are used.

    28. The last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.

    29. HopGrpRepeating groupCount tag 627

      Number of repeating groups of historical "hop" information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops.

      1. 627 NoHopsGroup count
      2. 628 HopCompIDString
      3. 629 HopSendingTimeUTCTimestamp
      4. 630 HopRefIDSeqNum
  2. ApplicationSequenceControlComponent
    1. 1180 ApplIDString

      Identifies the application with which a message is associated. Used only if application sequencing is in effect.

    2. Application sequence number assigned to the message by the application generating the message. Used only if application sequencing is in effect. Conditionally required if ApplID has been specified.

    3. The previous sequence number in the application sequence stream. Permits an application to publish messages with sequence gaps where it cannot be avoided. Used only if application sequencing is in effect. Conditionally required if ApplID has been specified

    4. Used to indicate that a message is being sent in response to an Application Message Request. Used only if application sequencing is in effect. It is possible for both ApplResendFlag and PossDupFlag to be set on the same message if the Sender's cache size is greater than zero and the message is being resent due to a session level resend request.

  3. Settlement cycle in which the settlement obligation was generated

  4. 1160 SettlObligMsgIDStringRequired

    Unique identifier for this message

  5. Used to identify the reporting mode of the settlement obligation which is either preliminary or final

  6. 58 TextString

    Can be used to provide any additional rejection text where rejecting a Settlement Instruction Request message.

  7. 60 TransactTimeUTCTimestamp

    Time when the Settlemnt Obligation Report was created.

  8. SettlObligationInstructionsRepeating groupCount tag 1165Required
    1. 1165 NoSettlObligGroup countRequired here

      Number of Settlement Obligations

    2. Unique ID for this settlement instruction

    3. New, Replace, Cancel, or Restate

    4. Required where SettlObligTransType(1162) is Cancel or Replace. The SettlObligID(1161) of the settlement obligation being canceled or replaced.

    5. Net flow of currency 1

    6. Net flow of currency 2

    7. 15 CurrencyCurrency

      Currency 1 in the stated currency pair, the dealt currency

    8. Currency 2 in the stated currency pair, the contra currency

    9. Derived rate of Ccy2 per Ccy1 based on netting

    10. 64 SettlDateLocalMktDate

      Value Date

    11. InstrumentComponent

      Used to express the instrument in which settlement is taking place

      1. 55 SymbolString

        Common, "human understood" representation of the security. SecurityID value can be specified if no symbol exists (e.g. non-exchange traded Collective Investment Vehicles) Use "[N/A]" for products which do not have a symbol.

      2. 65 SymbolSfxString

        Used in Fixed Income with a value of "WI" to indicate "When Issued" for a security to be reissued under an old CUSIP or ISIN or with a value of "CD" to indicate a EUCP with lump-sum interest rather than discount price.

      3. 48 SecurityIDString

        Takes precedence in identifying security to counterparty over SecurityAltID block. Requires SecurityIDSource if specified.

      4. Required if SecurityID is specified.

      5. SecAltIDGrpRepeating groupCount tag 454

        Number of alternate Security Identifiers

        1. 454 NoSecurityAltIDGroup count
      6. Indicates the type of product the security is associated with (high-level category)

      7. Identifies an entire suite of products for a given market. In Futures this may be "interest rates", "agricultural", "equity indexes", etc

      8. An exchange specific name assigned to a group of related securities which may be concurrently affected by market events and actions.

      9. 461 CFICodeString

        Indicates the type of security using ISO 10962 standard, Classification of Financial Instruments (CFI code) values. It is recommended that CFICode be used instead of SecurityType for non-Fixed Income instruments.

      10. It is recommended that CFICode be used instead of SecurityType for non-Fixed Income instruments. Required for Fixed Income. Refer to Volume 7 - Fixed Income Futures and Options should be specified using the CFICode[461] field instead of SecurityType[167] (Refer to Volume 7 - Recommendations and Guidelines for Futures and Options Markets.)

      11. Sub-type qualification/identification of the SecurityType (e.g. for SecurityType="MLEG"). If specified, SecurityType is required.

      12. Specifies the month and year of maturity. Applicable for standardized derivatives which are typically only referenced by month and year (e.g. S&P futures). Note MaturityDate (a full date) can also be specified.

      13. 541 MaturityDateLocalMktDate

        Specifies date of maturity (a full date). Note that standardized derivatives which are typically only referenced by month and year (e.g. S&P futures).may use MaturityMonthYear and/or this field. When using MaturityMonthYear, it is recommended that markets and sell sides report the MaturityDate on all outbound messages as a means of data enrichment. For NDFs this represents the fixing date of the contract.

      14. 1079 MaturityTimeTZTimeOnly

        For NDFs this represents the fixing time of the contract. It is optional to specify the fixing time.

      15. Indicator to determine if Instrument is Settle on Open.

      16. Gives the current state of the instrument

      17. 224 CouponPaymentDateLocalMktDate

        Date interest is to be paid. Used in identifying Corporate Bond issues.

      18. 225 IssueDateLocalMktDate

        Date instrument was issued. For Fixed Income IOIs for new issues, specifies the issue date.

      19. 239 RepoCollateralSecurityTypeDeprecated FIX.4.4String
      20. 226 RepurchaseTermDeprecated FIX.4.4int
      21. 227 RepurchaseRateDeprecated FIX.4.4Percentage
      22. 228 Factorfloat

        For Fixed Income: Amortization Factor for deriving Current face from Original face for ABS or MBS securities, note the fraction may be greater than, equal to or less than 1. In TIPS securities this is the Inflation index. Qty * Factor * Price = Gross Trade Amount For Derivatives: Contract Value Factor by which price must be adjusted to determine the true nominal value of one futures/options contract. (Qty * Price) * Factor = Nominal Value

      23. The location at which records of ownership are maintained for this instrument, and at which ownership changes must be recorded. Can be used in conjunction with ISIN to address ISIN uniqueness issues.

      24. ISO Country code of instrument issue (e.g. the country portion typically used in ISIN). Can be used in conjunction with non-ISIN SecurityID (e.g. CUSIP for Municipal Bonds without ISIN) to provide uniqueness.

      25. A two-character state or province abbreviation.

      26. The three-character IATA code for a locale (e.g. airport code for Municipal Bonds).

      27. 240 RedemptionDateDeprecated FIX.4.4LocalMktDate
      28. Used for derivatives, such as options and covered warrants

      29. Used for derivatives

      30. Used for derivatives. Multiplier applied to the strike price for the purpose of calculating the settlement value.

      31. Used for derivatives. The number of shares/units for the financial instrument involved in the option trade.

      32. Used for derivatives, such as options and covered warrants to indicate a versioning of the contract when required due to corporate actions to the underlying. Should not be used to indicate type of option - use the CFICode[461] for this purpose.

      33. For Fixed Income, Convertible Bonds, Derivatives, etc. Note: If used, quantities should be expressed in the "nominal" (e.g. contracts vs. shares) amount.

      34. Minimum price increment for the instrument. Could also be used to represent tick value.

      35. Minimum price increment amount associated with the MinPriceIncrement [969]. For listed derivatives, the value can be calculated by multiplying MinPriceIncrement by ContractValueFactor [231]

      36. 0

      37. Settlement method for a contract. Can be used as an alternative to CFI Code value

      38. Type of exercise of a derivatives security

      39. Cash amount indicating the pay out associated with an option. For binary options this is a fixed amount

      40. Method for price quotation

      41. Indicates type of valuation method used.

      42. Indicates whether the instruments are pre-listed only or can also be defined via user request

      43. Used to express the ceiling price of a capped call

      44. Used to express the floor price of a capped put

      45. Used to express option right

      46. Used to indicate if a security has been defined as flexible according to "non-standard" means. Analog to CFICode Standard/Non-standard indicator

      47. Used to indicate if a product or group of product supports the creation of flexible securities

      48. 997 TimeUnitString

        Used to indicate a time unit for the contract (e.g., days, weeks, months, etc.)

      49. 223 CouponRatePercentage

        For Fixed Income.

      50. Can be used to identify the security.

      51. Position Limit for the instrument.

      52. Near-term Position Limit for the instrument.

      53. 106 IssuerString
      54. Must be set if EncodedIssuer field is specified and must immediately precede it.

      55. Encoded (non-ASCII characters) representation of the Issuer field in the encoded format specified via the MessageEncoding field.

      56. Must be set if EncodedSecurityDesc field is specified and must immediately precede it.

      57. Encoded (non-ASCII characters) representation of the SecurityDesc field in the encoded format specified via the MessageEncoding field.

      58. SecurityXMLComponent

        Embedded XML document describing security.

        1. Must be set if SecurityXML field is specified and must immediately precede it.

        2. XML payload or content describing the Security information.

        3. XML Schema used to validate the XML used to describe the Security.

      59. 691 PoolString

        Identifies MBS / ABS pool

      60. Must be present for MBS/TBA

      61. The program under which a commercial paper is issued

      62. 876 CPRegTypeString

        The registration type of a commercial paper issuance

      63. EvntGrpRepeating groupCount tag 864

        Number of repeating EventType group entries.

        1. 864 NoEventsGroup count
        2. 866 EventDateLocalMktDate
        3. 1145 EventTimeUTCTimestamp

          Specific time of event. To be used in combination with EventDate [866]

        4. 867 EventPxPrice
        5. 868 EventTextString
      64. 873 DatedDateLocalMktDate

        If different from IssueDate

      65. If different from IssueDate and DatedDate

      66. InstrumentPartiesRepeating groupCount tag 1018

        Used to identify the parties listing a specific instrument

        1. Repeating group below should contain unique combinations of InstrumentPartyID, InstrumentPartyIDSource, and InstrumentPartyRole

        2. Used to identify party id related to instrument

        3. Used to identify source of instrument party id

        4. Used to identify the role of instrument party id

        5. InstrumentPtysSubGrpRepeating groupCount tag 1052

          Repeating group of InstrumentParty sub-identifiers.

      67. ComplexEventsRepeating groupCount tag 1483
        1. 1483 NoComplexEventsGroup count

          Number of complex events

        2. Identifies the type of complex event. Required if NoComplexEvents > 0.

        3. ComplexEventCondition is conditionally required when there are more than one ComplexEvent occurrences. A chain of ComplexEvents must be linked together through use of the ComplexEventCondition in which the relationship between any two events is described. For any two ComplexEvents the first occurrence will specify the ComplexEventCondition which links it with the second event.

        4. ComplexEventDatesRepeating groupCount tag 1491

          Used to specify the dates and time ranges when a complex event is in effect.

          1. Number of complex event date occurrences for a given complex event.

          2. Required if NoComplexEventDates(1491) > 0.

          3. Required if NoComplexEventDates(1491) > 0.

          4. ComplexEventTimesRepeating groupCount tag 1494
            1. Required if NoComplexEventTimes(1494) > 0.

            2. Required if NoComplexEventTimes(1494) > 0.

    12. PartiesRepeating groupCount tag 453
      1. 453 NoPartyIDsGroup count

        Repeating group below should contain unique combinations of PartyID, PartyIDSource, and PartyRole

      2. 448 PartyIDString

        Used to identify source of PartyID. Required if PartyIDSource is specified. Required if NoPartyIDs > 0.

      3. Used to identify class source of PartyID value (e.g. BIC). Required if PartyID is specified. Required if NoPartyIDs > 0.

      4. Identifies the type of PartyID (e.g. Executing Broker). Required if NoPartyIDs > 0.

      5. PtysSubGrpRepeating groupCount tag 802

        Repeating group of Party sub-identifiers.

        1. 802 NoPartySubIDsGroup count
    13. 168 EffectiveTimeUTCTimestamp

      Effective (start) date/time for this settlement instruction

    14. 126 ExpireTimeUTCTimestamp

      Termination date/time for this settlement instruction.

    15. 779 LastUpdateTimeUTCTimestamp

      Date/time this settlement instruction was last updated (or created if not updated since creation).

    16. SettlDetailsRepeating groupCount tag 1158

      Conveys settlement account details reported as part of obligation

      1. 1158 NoSettlDetailsGroup count

        Number of settlement parties

      2. Indicates the Source of the Settlement Instructions

      3. SettlPartiesRepeating groupCount tag 781

        Carries settlement account information

        1. 781 NoSettlPartyIDsGroup count

          Repeating group below should contain unique combinations of SettlPartyID, SettlPartyIDSource, and SettlPartyRole

        2. Used to identify source of SettlPartyID. Required if SettlPartyIDSource is specified. Required if NoSettlPartyIDs > 0.

        3. Used to identify class source of SettlPartyID value (e.g. BIC). Required if SettlPartyID is specified. Required if NoSettlPartyIDs > 0.

        4. Identifies the type of SettlPartyID (e.g. Executing Broker). Required if NoSettlPartyIDs > 0.

        5. SettlPtysSubGrpRepeating groupCount tag 801

          Repeating group of SettlParty sub-identifiers.

  9. StandardTrailerComponentRequired
    1. 93 SignatureLengthDeprecated FIXT.1.1Length

      Required when trailer contains signature. Note: Not to be included within SecureData field

    2. 89 SignatureDeprecated FIXT.1.1data

      Note: Not to be included within SecureData field

    3. 10 CheckSumStringRequired here

      (Always unencrypted, always last field in message)