Indexes

Message Layouts
Session
PreTrade
Trade
PostTrade
Infrastructure

Message

Confirmation (AK)

ID70
PedigreeAdded FIX.4.4
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.
Field
Name
Type
Req'd
Comments
Pedigree
Y
MsgType = AK
Added FIX.4.4
664
Y
Unique ID for this message
Added FIX.4.4
772
Mandatory if ConfirmTransType is Replace or Cancel
Added FIX.4.4
859
Only used when this message is used to respond to a confirmation request (to which this ID refers)
Added FIX.4.4
666
Y
New, Cancel or Replace
Added FIX.4.4
773
Y
Denotes whether this message represents a confirmation or a trade status message
Added FIX.4.4
797
Denotes whether or not this message represents copy confirmation (or status message)
Absence of this field indicates message is not a drop copy.
Added FIX.4.4
650
Denotes whether this message represents the legally binding confirmation
Absence of this field indicates message is not a legal confirm.
Added FIX.4.4
665
Y
Added FIX.4.4
573
Added EP246
940
Used to communicate an "affirmed" Confirmation(35=AK) status message (i.e. when ConfirmType(773) = 1 (Status)) to interested parties that need to or should receive such confirmation status message.
This field must not be used when sending a Confirmation(35=AK) message that needs to be affirmed.
Added EP215
Added EP275
2390
Added EP215
1832
Used to communicate the status of the central clearing workflow.
Added EP196
Updated EP215
Insert here the set of "Parties" (firm identification) fields defined in "Common Components of Application Messages"
Required for fixed income
Also to be used in associated with ProcessCode for broker of credit (e.g. for directed brokerage trades)
Also to be used to specify party-specific regulatory details (e.g. full legal name of contracting legal entity, registered address, regulatory status, any registration details)
Added FIX.4.4
Indicates number of orders to be combined for allocation. If order(s) were manually delivered set to 1 (one).Required when AllocNoOrdersType = 1
Added FIX.4.4
Added EP237
70
Used to refer to an earlier Allocation Instruction.
Added FIX.4.4
793
Used to refer to an earlier Allocation Instruction via its secondary identifier
Added FIX.4.4
467
Used to refer to an allocation account within an earlier Allocation Instruction.
Added FIX.4.4
828
Added EP237
829
Added EP237
855
Added EP237
1937
Added EP237
2374
Added EP258
2372
Must be set if EncodedTradeContinuationText(2371) field is specified and must immediately precede it.
Added EP258
2371
Encoded (non-ASCII characters) representation of the TradeContinuationText(2374) field in the encoded format specified via the MessageEncoding(347) field.
Added EP258
574
Added EP237
60
Y
Represents the time this message was generated
Added FIX.4.4
75
Y
Added FIX.4.4
Time of last execution being confirmed by this message. Use ExecutionTimestamp(2749) in ExecAllocGrp component when there are multiple trades.
Added FIX.4.4
Updated EP237
Y
Insert here the set of "Instrument" (symbology) fields defined in "Common Components of Application Messages"
Added FIX.4.4
Insert here the set of "InstrumentExtension" fields defined in "Common Components of Application Messages"
Added FIX.4.4
Insert here the set of "FinancingDetails" fields defined in "Common Components of Application Messages"
Added FIX.4.4
Added FIX.4.4
Updated EP95
Added FIX.4.4
Updated EP95
If traded on Yield, price must be calculated "to worst" and the <Yield> component block must specify how calculated, redemption date and price (if not par). If traded on Price, the <Yield> component block must specify how calculated - "Worst", and include redemptiondate and price (if not par).
Added FIX.4.4
80
Y
The quantity being confirmed by this message (this is at a trade level, not block or order level)
Added FIX.4.4
854
Added FIX.4.4
54
Y
Added FIX.4.4
15
Added FIX.4.4
2897
Added EP273
30
Added FIX.4.4
Y
Added FIX.4.4
Updated EP95
79
Y
Account number for the trade being confirmed by this message
Added FIX.4.4
661
Added FIX.4.4
798
Added FIX.4.4
6
Y
Gross price for the trade being confirmed
Always expressed in percent-of-par for Fixed Income
Added FIX.4.4
74
Absence of this field indicates that default precision arranged by the broker/institution is to be used
Added FIX.4.4
423
Price type for the AvgPx field
Added FIX.4.4
Added EP230
860
Added FIX.4.4
Insert here the set of "SpreadOrBenchmarkCurveData" fields defined in "Common Components of Application Messages"
Added FIX.4.4
861
Reported price (may be different to AvgPx in the event of a marked-up or marked-down principal trade)
Added FIX.4.4
58
Added FIX.4.4
354
Added FIX.4.4
355
Added FIX.4.4
81
Used to identify whether the trade was a soft dollar trade, step in/out etc. Broker of credit, where relevant, can be specified using the Parties nested block above.
Added FIX.4.4
381
Y
Gross trade amount for the allocated account being confirmed.
Added FIX.4.4
Updated EP258
157
Added FIX.4.4
230
Optional "next coupon date" for Fixed Income
Added FIX.4.4
158
Added FIX.4.4
159
Required for Fixed Income products that trade with accrued interest
Added FIX.4.4
738
Required for Fixed Income products that pay lump sum interest at maturity
Added FIX.4.4
920
For repurchase agreements the accrued interest on termination.
Added FIX.4.4
921
For repurchase agreements the start (dirty) cash consideration
Added FIX.4.4
922
For repurchase agreements the end (dirty) cash consideration
Added FIX.4.4
238
Added FIX.4.4
237
Added FIX.4.4
118
Y
Added FIX.4.4
890
Net Money at maturity if Zero Coupon and maturity value is different from par value
Added FIX.4.4
119
Added FIX.4.4
120
Added FIX.4.4
2899
Added EP273
155
Added FIX.4.4
156
Added FIX.4.4
63
Added FIX.4.4
64
Added FIX.4.4
Insert here the set of "SettlInstructionsData" fields defined in "Common Components of Application Messages"
Used to communicate settlement instructions for this Confirmation.
Added FIX.4.4
Added FIX.4.4
858
Used to identify any commission shared with a third party (e.g. directed brokerage)
Added FIX.4.4
Use as an alternative to CommissionData if multiple commissions or enhanced attributes are needed.
Added EP204
Added FIX.4.4
Required if any miscellaneous fees are reported.
Added FIX.4.4
Updated EP95
Added EP246
Added EP246
Y
Added FIX.4.4

Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy