TransactTime (FIX tag 60)

UTCTimestampFIX 4.4FIX 4.2

TransactTime (tag 60) is an UTCTimestamp field defined in FIX 4.4 and FIX 4.2. 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 and FIX 4.2
Messages
44

What the specification says

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

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.2Where in the message
Advertisement7OptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionaldirectly on the message body
AllocationInstructionAckPRequiredOptionaldirectly on the message body
AllocationReportASOptionaldirectly on the message body
AllocationReportAckATRequireddirectly on the message body
CollateralAssignmentAYRequireddirectly on the message body
CollateralRequestAXRequireddirectly on the message body
CollateralResponseAZRequireddirectly on the message body
ConfirmationAKRequireddirectly on the message body
ConfirmationAckAURequireddirectly on the message body
ConfirmationRequestBHRequireddirectly on the message body
CrossOrderCancelReplaceRequesttRequireddirectly on the message body
CrossOrderCancelRequestuRequireddirectly on the message body
ExecutionReport8OptionalOptionaldirectly on the message body
IOI6OptionalOptionaldirectly on the message body
ListCancelRequestKRequiredRequireddirectly on the message body
ListExecuteLRequiredRequireddirectly on the message body
ListStatusNOptionalOptionaldirectly on the message body
MassQuoteiOptionalOptionalinside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgementbOptionalinside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplaceACRequireddirectly on the message body
NewOrderCrosssRequireddirectly on the message body
NewOrderListEOptionalOptionalinside the ListOrdGrp component
NewOrderMultilegABRequireddirectly on the message body
NewOrderSingleDRequiredRequireddirectly on the message body
OrderCancelReject9OptionalOptionaldirectly on the message body
OrderCancelReplaceRequestGRequiredRequireddirectly on the message body
OrderCancelRequestFRequiredRequireddirectly on the message body
OrderMassCancelReportrOptionaldirectly on the message body
OrderMassCancelRequestqRequireddirectly on the message body
PositionMaintenanceReportAMRequireddirectly on the message body
PositionMaintenanceRequestALRequireddirectly on the message body
QuoteSOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptionalinside the QuotReqRjctGrp component
QuoteResponseAJOptionaldirectly on the message body
QuoteStatusReportAIOptionaldirectly on the message body
RequestForPositionsANRequireddirectly on the message body
SecurityStatusfOptionalOptionaldirectly on the message body
SettlementInstructionRequestAVRequireddirectly on the message body
SettlementInstructionsTRequiredRequireddirectly on the message body
TradeCaptureReportAERequireddirectly on the message body
TradeCaptureReportAckAROptionaldirectly on the message body
TradeCaptureReportRequestADOptionalinside the TrdCapDtGrp 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