TransBkdTime (FIX tag 483)

UTCTimestampFIX 4.4FIX 5.0 SP2

TransBkdTime (tag 483) is an UTCTimestamp field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag
483
Name
TransBkdTime
Datatype
UTCTimestamp (String)
Format
YYYYMMDD-HH:MM:SS[.sss]
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
2

What the specification says

For CIV A date and time stamp to indicate the time a CIV order was booked by the fund manager.

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

A real message using tag 483

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength159
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
483TransBkdTime20240101-12:00:00.000
10CheckSum010
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 483 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 5.0 SP2Where in the message
CrossOrderCancelReplaceRequesttOptionaldirectly on the message body
ExecutionReport8OptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalinside the MDIncGrp component
NewOrderCrosssOptionaldirectly on the message body
TradeCaptureReportAEOptionalOptionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › TradeReportOrderDetail

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 483 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[483];field?.name;   // "TransBkdTime"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