ClearingBusinessDate (FIX tag 715)

LocalMktDateFIX 4.4FIX 5.0 SP2

ClearingBusinessDate (tag 715) is a LocalMktDate field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 12 message types and is required in 5 of them.

At a glance

Tag: 715
Name: ClearingBusinessDate
Datatype: LocalMktDate (String)
Format: YYYYMMDD
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 12

What the specification says

FIX 4.4

The "Clearing Business Date" referred to by this maintenance request.

FIX 5.0 SP2

The business date for which the trade is expected to be cleared.

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

A real message using tag 715

TradeCaptureReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	178
35	MsgType	AE	Trade Capture Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
571	TradeReportID	EXAMPLE
570	PreviouslyReported	N	not reported to counterparty
32	LastQty	1000000
31	LastPx	1.09210
75	TradeDate	20240101
715	ClearingBusinessDate	20240101
60	TransactTime	20240101-12:00:00.000
552	NoSides1 entry	1	repeating group
54	Side	1	Buy
37	OrderID	ORD-10042
10	CheckSum	024

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 715 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.

Message	MsgType	FIX 4.4	FIX 5.0 SP2	Where in the message
AdjustedPositionReport	BL	—	Required	directly on the message body
AllocationInstruction	J	—	Optional	directly on the message body
AllocationInstructionAlert	BM	—	Optional	directly on the message body
AllocationReport	AS	—	Optional	directly on the message body
AllocationReportAck	AT	—	Optional	directly on the message body
AssignmentReport	AW	Required	Required	directly on the message body
CollateralAssignment	AY	Optional	Optional	directly on the message body
CollateralInquiry	BB	Optional	Optional	directly on the message body
CollateralInquiryAck	BG	Optional	Optional	directly on the message body
CollateralReport	BA	Optional	Optional	directly on the message body
CollateralRequest	AX	Optional	Optional	directly on the message body
CollateralResponse	AZ	—	Optional	directly on the message body
ContraryIntentionReport	BO	—	Required	directly on the message body
DerivativeSecurityList	AA	—	Optional	directly on the message body
MarketDataSnapshotFullRefresh	W	—	Optional	directly on the message body
PositionMaintenanceReport	AM	Required	Required	directly on the message body
PositionMaintenanceRequest	AL	Required	Required	directly on the message body
PositionReport	AP	Required	Required	directly on the message body
RequestForPositions	AN	Required	Required	directly on the message body
RequestForPositionsAck	AO	—	Optional	directly on the message body
SecurityDefinition	d	—	Optional	directly on the message body
SecurityDefinitionUpdateReport	BP	—	Optional	directly on the message body
SecurityList	y	—	Optional	directly on the message body
SecurityListUpdateReport	BK	—	Optional	directly on the message body
SettlementObligationReport	BQ	—	Optional	directly on the message body
TradeCaptureReport	AE	Optional	Optional	directly on the message body
TradeCaptureReportAck	AR	—	Optional	directly on the message body
TradeCaptureReportRequest	AD	Optional	Optional	directly on the message body

Wire format

A calendar date in the market's local timezone, with no time component and no offset. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 715 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[715];field?.name;   // "ClearingBusinessDate"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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

Try the decoder Source on GitHub