FIX Protocol Tag 60: TransactTime

Practical notes on TransactTime

TransactTime is the UTC time the business event happened: when the client created the request, or when the sell side executed or changed the order.

• It is required on New Order Single, Order Cancel Request and Order Cancel/Replace Request from FIX 4.2.
• On Execution Reports it is the sell side's time of the event, which is the time to use for trade records.
• It differs from SendingTime (52), which is when the message went on the wire.

Common mistakes

• Leaving it off order messages: the most frequent cause of a Required tag missing reject.
• Writing it in ISO 8601 format: 373=6 Incorrect data format.

See also:Required tag missing (373=1)Incorrect data format (373=6)

Tag 60 in each FIX version

Values and message usage as defined in a specific version.

• FIX 4.0
• FIX 4.1
• FIX 4.2
• FIX 4.3
• FIX 4.4
• FIX 5.0
• FIX 5.0 SP1
• FIX 5.0 SP2

Data type

UTCTIMESTAMP: Date and time in UTC as YYYYMMDD-HH:MM:SS, optionally followed by fractions of a second (.sss).

Example

60=20261020-14:30:05.120

Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.

Message types that use tag 60

• IOI 35=6
• Advertisement 35=7
• Execution Report 35=8
• Order Cancel Reject 35=9
• New Order Single 35=D
• New Order List 35=E
• Order Cancel Request 35=F
• Order Cancel/Replace Request 35=G
• Allocation Instruction 35=J
• List Cancel Request 35=K
• List Execute 35=L
• List Status 35=N
• Allocation Ack 35=P
• Quote Request 35=R
• Quote 35=S
• Settlement Instructions 35=T
• Market Data Incremental Refresh 35=X
• Derivative Security List 35=AA
• New Order Multileg 35=AB
• Multileg Order Cancel/Replace 35=AC
• Trade Capture Report Request 35=AD
• Trade Capture Report 35=AE
• Quote Request Reject 35=AG
• Quote Status Report 35=AI
• Quote Response 35=AJ
• Confirmation 35=AK
• Position Maintenance Request 35=AL
• Position Maintenance Report 35=AM
• Request For Positions 35=AN
• Position Report 35=AP
• Trade Capture Report Ack 35=AR
• Allocation Report 35=AS
• Allocation Report Ack 35=AT
• Confirmation Ack 35=AU
• Settlement Instruction Request 35=AV
• Collateral Request 35=AX
• Collateral Assignment 35=AY
• Collateral Response 35=AZ
• Collateral Report 35=BA
• Confirmation Request 35=BH
• Trading Session List 35=BJ
• Security List Update Report 35=BK
• Allocation Instruction Alert 35=BM
• Contrary Intention Report 35=BO
• Security Definition Update Report 35=BP
• Settlement Obligation Report 35=BQ
• Derivative Security List Update Report 35=BR
• Trading Session List Update Report 35=BS
• Market Definition 35=BU
• Market Definition Update Report 35=BV
• Order Mass Action Report 35=BZ
• Order Mass Action Request 35=CA
• Party Details List Report 35=CG
• Margin Requirement Inquiry 35=CH
• Margin Requirement Inquiry Ack 35=CI
• Margin Requirement Report 35=CJ
• Party Details List Update Report 35=CK
• Party Risk Limits Report 35=CM
• Security Mass Status 35=CO
• Account Summary Report 35=CQ
• Party Risk Limits Update Report 35=CR
• Party Entitlements Report 35=CV
• Party Entitlements Update Report 35=CZ
• Trade Match Report 35=DC
• Party Risk Limits Report Ack 35=DE
• Party Risk Limit Check Request 35=DF
• Party Risk Limit Check Request Ack 35=DG
• Party Action Request 35=DH
• Party Action Report 35=DI
• Mass Order 35=DJ
• Mass Order Ack 35=DK
• Position Transfer Instruction 35=DL
• Position Transfer Instruction Ack 35=DM
• Position Transfer Report 35=DN
• Market Data Statistics Request 35=DO
• Market Data Statistics Report 35=DP
• Collateral Report Ack 35=DQ
• Market Data Report 35=DR
• Pay Management Request 35=DY
• Pay Management Report 35=EA
• Mass Quote Ack 35=b
• Security Definition 35=d
• Security Status 35=f
• Trading Session Status 35=h
• Mass Quote 35=i
• Order Mass Cancel Request 35=q
• Order Mass Cancel Report 35=r
• New Order Cross 35=s
• Cross Order Cancel Replace Request 35=t
• Cross Order Cancel Request 35=u
• Security Types 35=w
• Security List 35=y

Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.