ExecAckStatus (FIX tag 1036)

charFIX 5.0 SP2

ExecAckStatus (tag 1036) is a char field defined in FIX 5.0 SP2. It appears in 1 message type and is required in 1 of them. It is an enumerated field with 3 defined values.

At a glance

Tag: 1036
Name: ExecAckStatus
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 1
Valid values: 3

What the specification says

The status of this execution acknowledgement message.

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

A real message using tag 1036

ExecutionAcknowledgement · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	103
35	MsgType	BN	ExecutionAck
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
1036	ExecAckStatus	0	Received, not yet processed
17	ExecID	EXEC-88117
54	Side	1	Buy
10	CheckSum	073

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 5.0 SP2 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
0	Received, not yet processed	RECEIVED_NOT_YET_PROCESSED
1	Accepted	ACCEPTED
2	Don't know / Rejected	DONT_KNOW_REJECTED

Where tag 1036 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	Requiredness	Where in the message
ExecutionAcknowledgement	BN	Required	directly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 1036 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const execAckStatus = message.fields[1036]?.raw;// e.g. "0" — Received, not yet processed// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1036)  ?.enumValues?.find((e) => e.value === execAckStatus)  ?.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-fix50sp2

Try the decoder Source on GitHub