ExecRestatementReason (FIX tag 378)

intFIX 4.4FIX 4.2

ExecRestatementReason (tag 378) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types, always optionally. It is an enumerated field with 12 defined values.

At a glance

Tag: 378
Name: ExecRestatementReason
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 2
Valid values: 12

What the specification says

Code to identify reason for an ExecutionRpt message sent with ExecType=Restated or used when communicating an unsolicited cancel.

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

A real message using tag 378

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	139
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
378	ExecRestatementReason	0	GT Corporate action
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	047

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name	Dialects
0	GT Corporate action	GT_CORPORATE_ACTION / GTCorporateAction	FIX 4.4, FIX 4.2
1	GT renewal / restatement (no corporate action)	GT_RENEWAL / GTRenewal	FIX 4.4, FIX 4.2
2	Verbal change	VERBAL_CHANGE / VerbalChange	FIX 4.4, FIX 4.2
3	Repricing of order	REPRICING_OF_ORDER / RepricingOfOrder	FIX 4.4, FIX 4.2
4	Broker option	BROKER_OPTION / BrokerOption	FIX 4.4, FIX 4.2
5	Partial decline of OrderQty (e.g. exchange-initiated partial cancel)	PARTIAL_DECLINE_OF_ORDERQTY / PartialDeclineOfOrderQty	FIX 4.4, FIX 4.2
6	Cancel on Trading Halt	CANCEL_ON_TRADING_HALT	FIX 4.4
7	Cancel on System Failure	CANCEL_ON_SYSTEM_FAILURE	FIX 4.4
8	Market (Exchange) Option	MARKET	FIX 4.4
9	Canceled, Not Best	CANCELED_NOT_BEST	FIX 4.4
10	Warehouse recap	WAREHOUSE_RECAP	FIX 4.4
99	Other	OTHER	FIX 4.4

Where tag 378 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 4.2	Where in the message
ExecutionReport	8	Conditional	Optional	directly on the message body
TradeCaptureReport	AE	Optional	—	directly on the message body

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 378 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 execRestatementReason = message.fields[378]?.raw;// e.g. "0" — GT Corporate action// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(378)  ?.enumValues?.find((e) => e.value === execRestatementReason)  ?.description;

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