Message Confirmation Scenario base

SYNOPSIS: The Confirmation messages are used to provide individual trade level confirmations from the sell side to the buy side. In versions of FIX prior to version 4.4, this role was performed by the allocation message. Unlike the allocation message, the confirmation message operates at an allocation account (trade) level rather than block level, allowing for the affirmation or rejection of individual confirmations.

ID MsgType Abbr Flow
70AKCnfm

Pedigree

Added EP Updated EP Deprecated EP
FIX.4.4

Responses

None

Members

Confirmation base members
ID Name Abbr Presence Description
1024StandardHeaderBaseHeaderrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
664ConfirmIDCnfmID required SYNOPSIS: Message reference for Confirmation
772ConfirmRefIDCnfmRefID optional SYNOPSIS: Reference identifier to be used with ConfirmTransType (666) = Replace or Cancel
859ConfirmReqIDCnfmReqID optional SYNOPSIS: Unique identifier for a Confirmation Request message
666ConfirmTransTypeCnfmTransTyp required SYNOPSIS: Identifies the Confirmation transaction type.
773ConfirmTypeCnfmTyp required SYNOPSIS: Identifies the type of Confirmation message being sent.
797CopyMsgIndicatorCopyMsgInd optional SYNOPSIS: Indicates whether or not this message is a drop copy of another message.
650LegalConfirmLegalCnfm optional SYNOPSIS: Indicates that this message is to serve as the final and legal confirmation.
665ConfirmStatusCnfmStat required SYNOPSIS: Identifies the status of the Confirmation.
573MatchStatusMtchStat optional SYNOPSIS: The status of this trade with respect to matching or comparison.
940AffirmStatusAffirmStat optional SYNOPSIS: Specifies the affirmation status of the confirmation.
2390TradeConfirmationReferenceIDTrdCnfmRefID optional SYNOPSIS: A reference or control identifier or number used as a trade confirmation key.
ELABORATION: An example of a control identifier is the DTC ID Control Number.
1832ClearedIndicatorClrd optional SYNOPSIS: Indicates whether the trade or position being reported was cleared through a clearing organization.
1012PartiesPtyoptionalSYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION:
2036OrdAllocGrpOrdAllocoptionalSYNOPSIS:
ELABORATION:
2014ExecAllocGrpAllExcoptionalSYNOPSIS:
ELABORATION:
70AllocIDAllocID optional SYNOPSIS: Unique identifier for allocation message. (Prior to FIX 4.1 this field was of type int)
793SecondaryAllocIDAllocID2 optional SYNOPSIS: Secondary allocation identifier. Unlike the AllocID (70), this can be shared across a number of allocation instruction or allocation report messages, thereby making it possible to pass an identifier for an original allocation message on multiple messages (e.g. from one party to a second to a third, across cancel and replace messages etc.).
467IndividualAllocIDIndAllocID optional SYNOPSIS: Unique identifier for a specific NoAllocs (78) repeating group instance (e.g. for an AllocAccount).
828TrdTypeTrdTyp optional SYNOPSIS: Type of trade assigned to a trade.
ELABORATION: Note: several enumerations of this field duplicate the enumerations in TradePriceConditions(1839) field. These may be deprecated from TrdType(828) in the future. TradePriceConditions(1839) is preferred in messages that support it.
829TrdSubTypeTrdSubTyp optional SYNOPSIS: Further qualification to the trade type
855SecondaryTrdTypeTrdTyp2 optional SYNOPSIS: Type of trade assigned to a trade. Used in addition to TrdType(828). Must not be used when only one trade type needs to be assigned.
1937TradeContinuationTrdContntn optional SYNOPSIS: Specifies the post-execution trade continuation or lifecycle event. Additional values may be used by mutual agreement of the counterparties.
2374TradeContinuationTextTrdContntnTxt optional SYNOPSIS: Free form text to specify additional trade continuation information or data.
2372EncodedTradeContinuationTextLenEncTrdContntnTextLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedTradeContinuationText(2371) field.
2371EncodedTradeContinuationTextEncTrdContntnText optional SYNOPSIS: Encoded (non-ASCII characters) representation of the TradeContinuationText(2374) field in the encoded format specified via the MessageEncoding(347) field. If used, the ASCII (English) representation should also be specified in the TradeContinuationText(2374) field.
574MatchTypeMtchTyp optional SYNOPSIS: The point in the matching process at which this trade was matched.
60TransactTimeTxnTm required SYNOPSIS: Timestamp when the business transaction represented by the message occurred.
75TradeDateTrdDt required SYNOPSIS: Indicates date of trading day. Absence of this field indicates current day (expressed in local time at place of trade).
1020TrdRegTimestampsTrdRegTSoptionalSYNOPSIS: The TrdRegTimestamps component block is used to express timestamps for an order or trade that are required by regulatory agencies These timesteamps are used to identify the timeframes for when an order or trade is received on the floor, received and executed by the broker, etc.
ELABORATION:
1003InstrumentInstrmtrequiredSYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION:
1004InstrumentExtensionInstrmtExtoptionalSYNOPSIS: The InstrumentExtension component block identifies additional security attributes that are more commonly found for Fixed Income securities.
ELABORATION:
1002FinancingDetailsFinDetlsoptionalSYNOPSIS: Component block is optionally used for financial transaction where legal contracts, master agreements or master confirmations is to be referenced. This component identifies the legal agreement under which the deal was made and other unique characteristics of the transaction. For example, the AgreementDesc(913) field refers to base standard documents such as MRA 1996 Repurchase Agreement, GMRA 2000 Bills Transaction (U.K.), MSLA 1993 Securities Loan – Amended 1998, for example.
ELABORATION:
2066UndInstrmtGrpUndlyoptionalSYNOPSIS:
ELABORATION:
2019InstrmtLegGrpLegoptionalSYNOPSIS:
ELABORATION:
1022YieldDataYieldoptionalSYNOPSIS: The YieldData component block conveys yield information for a given Fixed Income security.
ELABORATION:
80AllocQtyQty required SYNOPSIS: Quantity to be allocated to specific sub-account (Prior to FIX 4.2 this field was of type int)
854QtyTypeQtyTyp optional SYNOPSIS: Type of quantity specified in quantity field. ContractMultiplier (tag 231) is required when QtyType = 1 (Contracts). UnitOfMeasure (tag 996) and TimeUnit (tag 997) are required when QtyType = 2 (Units of Measure per Time Unit).
54SideSide required SYNOPSIS: Side of order (see Volume : "Glossary" for value definitions)
15CurrencyCcy optional SYNOPSIS: Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See "Appendix 6-A: Valid Currency Codes" for information on obtaining valid values.
30LastMktLastMkt optional SYNOPSIS: Market of execution for last fill, or an indication of the market where an order was routed Valid values: See "Appendix 6-C"
ELABORATION: In the context of ESMA RTS 1 Annex I, Table 3, Field 6 "Venue of Execution" it is required that the "venue where the transaction was executed" be identified using ISO 10383 (MIC). Additionally, ESMA requires the use of "MIC code 'XOFF' for financial instruments admitted to trading or traded on a trading venue, where the transaction on that financial instrument is not executed on a trading venue, systematic internaliser or organized trading platform outside of the Union. Use 'SINT' for financial instruments admitted to trading or traded on a trading venue, where the transaction is executed on a systematic internaliser."
2013CpctyConfGrpCpctyrequiredSYNOPSIS:
ELABORATION:
79AllocAccountAcct required SYNOPSIS: Sub-account mnemonic
661AllocAcctIDSourceActIDSrc optional SYNOPSIS: Used to identify the source of the AllocAccount (79) code. See AcctIDSource (660) for valid values.
798AllocAccountTypeAcctTyp optional SYNOPSIS: Type of account associated with a confirmation or other trade-level message
6AvgPxAvgPx required SYNOPSIS: Calculated average price of all fills on this order. For Fixed Income trades AvgPx is always expressed as percent-of-par, regardless of the PriceType (423) of LastPx (31). I.e., AvgPx will contain an average of percent-of-par values (see LastParPx (669)) for issues traded in Yield, Spread or Discount.
74AvgPxPrecisionAvgPxPrcsn optional SYNOPSIS: Indicates number of decimal places to be used for average pricing. Absence of this field indicates that default precision arranged by the broker/institution is to be used.
423PriceTypePxTyp optional SYNOPSIS: Code to represent the price type.
ELABORATION: For Financing transactions PriceType(423) implies the "repo type" - Fixed or Floating - 9 (Yield) or 6 (Spread) respectively - and Price(44) gives the corresponding "repo rate". See Volume 1 "Glossary" for further value definitions.
1074PriceQualifierGrpPxQualoptionalSYNOPSIS: The PriceQualifierGrp component clarifies the composition of the price when standard market practice for the security calls for a price that is atypical when traded in other markets, or when a price can be expressed in more than one way.
ELABORATION:
860AvgParPxAvgParPx optional SYNOPSIS: Used to express average price as percent of par (used where AvgPx field is expressed in some other way)
1018SpreadOrBenchmarkCurveDataSprdBnchmkCurveoptionalSYNOPSIS: The SpreadOrBenchmarkCurveData component block is primarily used for Fixed Income to convey spread to a benchmark security or curve.
ELABORATION:
861ReportedPxRptedPx optional SYNOPSIS: Reported price (used to differentiate from AvgPx on a confirmation of a marked-up or marked-down principal trade)
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text(58) field.
81ProcessCodeProcCode optional SYNOPSIS: Processing code for sub-account. Absence of this field in AllocAccount (79) / AllocPrice (366) /AllocQty (80) / ProcessCode instance indicates regular trade.
381GrossTradeAmtGrossTrdAmt required SYNOPSIS: Total amount traded expressed in units of currency - usually quantity * price. For FX Futures this is used to express the notional value of a fill when quantity fields are expressed in terms of contract size (i.e. quantity * price * contract size).
157NumDaysInterestNumDaysInt optional SYNOPSIS: Number of Days of Interest for convertible bonds and fixed income. Note value may be negative.
230ExDateExDt optional SYNOPSIS: The date when a distribution of interest is deducted from a securities assets or set aside for payment to bondholders. On the ex-date, the securities price drops by the amount of the distribution (plus or minus any market activity). (Note tag # was reserved in FIX 4.1, added in FIX 4.3) (prior to FIX 4.4 field was of type UTCDate)
158AccruedInterestRateAcrdIntRt optional SYNOPSIS: The amount the buyer compensates the seller for the portion of the next coupon interest payment the seller has earned but will not receive from the issuer because the issuer will send the next coupon payment to the buyer. Accrued Interest Rate is the annualized Accrued Interest amount divided by the purchase price of the bond.
159AccruedInterestAmtAcrdIntAmt optional SYNOPSIS: Amount of Accrued Interest for convertible bonds and fixed income
738InterestAtMaturityIntAtMat optional SYNOPSIS: Amount of interest (i.e. lump-sum) at maturity.
920EndAccruedInterestAmtEndAcrdIntAmt optional SYNOPSIS: Accrued Interest Amount applicable to a financing transaction on the End Date.
921StartCashStartCsh optional SYNOPSIS: Starting dirty cash consideration of a financing deal, i.e. paid to the seller on the Start Date.
922EndCashEndCsh optional SYNOPSIS: Ending dirty cash consideration of a financing deal. i.e. reimbursed to the buyer on the End Date.
238ConcessionConcession optional SYNOPSIS: Provides the reduction in price for the secondary market in Muncipals. (Note tag # was reserved in FIX 4.1, added in FIX 4.3)
237TotalTakedownTotTakedown optional SYNOPSIS: The price at which the securities are distributed to the different members of an underwriting group for the primary market in Municipals, total gross underwriter's spread. (Note tag # was reserved in FIX 4.1, added in FIX 4.3)
118NetMoneyNetMny required SYNOPSIS: Total amount due as the result of the transaction (e.g. for Buy order - principal + commission + fees) reported in currency of execution.
890MaturityNetMoneyMatNetMny optional SYNOPSIS: Net Money at maturity if Zero Coupon and maturity value is different from par value
119SettlCurrAmtSettlCurrAmt optional SYNOPSIS: Total amount due expressed in settlement currency (includes the effect of the forex transaction)
120SettlCurrencySettlCcy optional SYNOPSIS: Currency code of settlement denomination.
155SettlCurrFxRateSettlCurrFxRt optional SYNOPSIS: Foreign exchange rate used to compute SettlCurrAmt (9) from Currency (5) to SettlCurrency (20)
156SettlCurrFxRateCalcSettlCurrFxRtCalc optional SYNOPSIS: Specifies whether or not SettlCurrFxRate (155) should be multiplied or divided.
63SettlTypeSettlTyp optional SYNOPSIS: Indicates order settlement period. If present, SettlDate (64) overrides this field. If both SettlType (63) and SettDate (64) are omitted, the default for SettlType (63) is 0 (Regular) Regular is defined as the default settlement period for the particular security on the exchange of execution. In Fixed Income the contents of this field may influence the instrument definition if the SecurityID (48) is ambiguous. In the US an active Treasury offering may be re-opened, and for a time one CUSIP will apply to both the current and "when-issued" securities. Supplying a value of "7" clarifies the instrument description; any other value or the absence of this field should cause the respondent to default to the active issue. Additionally the following patterns may be uses as well as enum values Dx = FX tenor expression for "days", e.g. "D5", where "x" is any integer > 0 Mx = FX tenor expression for "months", e.g. "M3", where "x" is any integer > 0 Wx = FX tenor expression for "weeks", e.g. "W13", where "x" is any integer > 0 Yx = FX tenor expression for "years", e.g. "Y1", where "x" is any integer > 0 Noted that for FX the tenors expressed using Dx, Mx, Wx, and Yx values do not denote business days, but calendar days.
64SettlDateSettlDt optional SYNOPSIS: Specific date of trade settlement (SettlementDate) in YYYYMMDD format. If present, this field overrides SettlType (63). This field is required if the value of SettlType (63) is 6 (Future) or 8 (Sellers Option). This field must be omitted if the value of SettlType (63) is 7 (When and If Issued) (expressed in local time at place of settlement)
1016SettlInstructionsDataSetInstroptionalSYNOPSIS: The SettlInstructionsData component block is used to convey key information regarding standing settlement and delivery instructions. It also provides a reference to standing settlement details regarding the source, delivery instructions, and settlement parties
ELABORATION:
1000CommissionDataCommoptionalSYNOPSIS: The CommissionData component block is used to carry commission information such as the type of commission and the rate. Use the CommissionDataGrp component as an alternative if multiple commissions or enhanced attributes are needed.
ELABORATION: This component may be used to provide aggregated commission data of a given CommType(13) where the CommissionDataGrp maybe used to include the detail splits provided the commission is of the same commission basis type. For example, CommissionData may contain CommType(13) of 3 (Absolute) and a Commission(12) value of "15". CommissionDataGrp may be used to show how this Commission(12) value of "15" is split up as long as the CommissionBasis(2642) is also 3 (Absolute) for each of the instances added together. This method of aggregated commission data may also be applied to this component to provide a total when the instances of the detail splits in CommissionDataGrp contain leg level information (indicated by the usage of CommissionLegRefID(2649) in CommissionDataGrp). Note that it is only possible to aggregate values for a single commission basis type.
858SharedCommissionSharedComm optional SYNOPSIS: Commission to be shared with a third party, e.g. as part of a directed brokerage commission sharing arrangement.
1070CommissionDataGrpCommDataoptionalSYNOPSIS: The CommissionDataGrp component block is used to carry commission information such as the type of commission and the rate. It provides an alternative to the CommissionData component if multiple commissions or enhanced attributes are needed.
ELABORATION: The CommissionLegRefID(2649) field is used to reference the LegID(1788) within the InstrumentLeg component, allowing for specifying instrument leg specific commission values when a multilegged security is fully expressed in the same message. This component is not intended for non-leg instances of the CommissionDataGrp component to represent aggregated values of the leg instances within the component when both leg and non-leg instances are included.
1019StipulationsStipoptionalSYNOPSIS: The Stipulations component block is used in Fixed Income to provide additional information on a given security. These additional information are usually not considered static data information.
ELABORATION:
2035MiscFeesGrpMiscFeesoptionalSYNOPSIS: The MiscFeesGrp component is used to provide details of trade and transaction fees other than commissions, e.g. regulatory, exchange, taxes, levies, markup, trade reporting, etc. In the context of ESMA RTS 27 Best Execution Reporting, it may also be used to collect and publish the nature and level of current venue fees, rebates and payouts. Use MiscFeeQualifier(2712) to communicate whether the fee affects trade economics.
ELABORATION: MiscFeesGrp should be used to convey fees related to the transaction (e.g. taxes, transaction based fees, etc.) and should not be used to specify payments based on the price or terms of the contract (e.g. upfront fee, premium amount, security lending fee, contract-based rebates, related fee resets, payment frequency, etc.). For contractual payments use the PaymentGrp component instead.
1076MatchExceptionGrpMtchExcptnoptionalSYNOPSIS: The MatchExceptionGrp component details the matching exceptions and variances identified during the matching process based on the defined matching criteria and tolerances.
ELABORATION:
1077MatchingDataPointGrpMtchDataPntoptionalSYNOPSIS: The MatchingDataPointGrp component details all the trade attributes and tolerances used for trade matching.
ELABORATION:
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: