TransactTime (FIX tag 60)

UTCTimestampFIX 4.4FIX 4.2FIX 5.0 SP2

TransactTime (tag 60) is an UTCTimestamp field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 44 message types and is required in 25 of them.

At a glance

Tag
60
Name
TransactTime
Datatype
UTCTimestamp (String)
Format
YYYYMMDD-HH:MM:SS[.sss]
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
44

What the specification says

FIX 4.4

Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")

FIX 4.2

Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")

FIX 5.0 SP2

Timestamp when the business transaction represented by the message occurred.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 60

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength158
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
60TransactTime20240101-12:00:00.000
10CheckSum208
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 60 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeFIX 4.4FIX 4.2FIX 5.0 SP2Where in the message
Advertisement7OptionalOptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionalOptionaldirectly on the message body
AllocationInstructionAckPRequiredOptionalOptionaldirectly on the message body
AllocationInstructionAlertBM——Optionaldirectly on the message body
AllocationReportASOptional—Optionaldirectly on the message body
AllocationReportAckATRequired—Optionaldirectly on the message body
CollateralAssignmentAYRequired—Requireddirectly on the message body
CollateralReportBA——Optionaldirectly on the message body
CollateralRequestAXRequired—Requireddirectly on the message body
CollateralResponseAZRequired—Requireddirectly on the message body
ConfirmationAKRequired—Requireddirectly on the message body
ConfirmationAckAURequired—Requireddirectly on the message body
ConfirmationRequestBHRequired—Requireddirectly on the message body
ContraryIntentionReportBO——Optionaldirectly on the message body
CrossOrderCancelReplaceRequesttRequired—Requireddirectly on the message body
CrossOrderCancelRequestuRequired—Requireddirectly on the message body
DerivativeSecurityListAA——Optionaldirectly on the message body
DerivativeSecurityListUpdateReportBR——Optionaldirectly on the message body
ExecutionReport8OptionalOptionalOptionaldirectly on the message body
IOI6OptionalOptionalOptionaldirectly on the message body
ListCancelRequestKRequiredRequiredRequireddirectly on the message body
ListExecuteLRequiredRequiredRequireddirectly on the message body
ListStatusNOptionalOptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshX——Optionalinside the MDIncGrp component
MarketDefinitionBU——Optionaldirectly on the message body
MarketDefinitionUpdateReportBV——Optionaldirectly on the message body
MassQuoteiOptionalOptionalOptionalinside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgementbOptional—Optionalinside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplaceACRequired—Requireddirectly on the message body
NewOrderCrosssRequired—Requireddirectly on the message body
NewOrderListEOptionalOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABRequired—Requireddirectly on the message body
NewOrderSingleDRequiredRequiredRequireddirectly on the message body
OrderCancelReject9OptionalOptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGRequiredRequiredRequireddirectly on the message body
OrderCancelRequestFRequiredRequiredRequireddirectly on the message body
OrderMassActionReportBZ——Optionaldirectly on the message body
OrderMassActionRequestCA——Requireddirectly on the message body
OrderMassCancelReportrOptional—Optionaldirectly on the message body
OrderMassCancelRequestqRequired—Requireddirectly on the message body
PositionMaintenanceReportAMRequired—Optionaldirectly on the message body
PositionMaintenanceRequestALRequired—Optionaldirectly on the message body
QuoteSOptionalOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptional—Optionalinside the QuotReqRjctGrp component
QuoteResponseAJOptional—Optionaldirectly on the message body
QuoteStatusReportAIOptional—Optionaldirectly on the message body
RequestForPositionsANRequired—Requireddirectly on the message body
SecurityDefinitiond——Optionaldirectly on the message body
SecurityDefinitionUpdateReportBP——Optionaldirectly on the message body
SecurityListy——Optionaldirectly on the message body
SecurityListUpdateReportBK——Optionaldirectly on the message body
SecurityStatusfOptionalOptionalOptionaldirectly on the message body
SecurityTypesw——Optionalinside the SecTypesGrp component
SettlementInstructionRequestAVRequired—Requireddirectly on the message body
SettlementInstructionsTRequiredRequiredRequireddirectly on the message body
SettlementObligationReportBQ——Optionaldirectly on the message body
TradeCaptureReportAERequired—Optionaldirectly on the message body
TradeCaptureReportAckAROptional—Optionaldirectly on the message body
TradeCaptureReportRequestADOptional—Optionalinside the TrdCapDtGrp component
TradingSessionListBJ——Optionalinside the TrdSessLstGrp component
TradingSessionListUpdateReportBS——Optionalinside the TrdSessLstGrp component

Wire format

A UTC date and time. The fractional-seconds part is optional, so two timestamps can be equal but not byte-identical. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 60 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";​const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);​const field = message.fields[60];field?.name;   // "TransactTime"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other UTCTimestamp fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44