RegistStatus (FIX tag 506)

charFIX 4.4FIX 5.0 SP2

RegistStatus (tag 506) is a char field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types and is required in 1 of them. It is an enumerated field with 4 defined values.

At a glance

Tag: 506
Name: RegistStatus
Datatype: char
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2
Valid values: 4

What the specification says

FIX 4.4

Registration status as returned by the broker or (for CIV) the fund manager

FIX 5.0 SP2

Registration status as returned by the broker or (for CIV) the fund manager:

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

A real message using tag 506

RegistrationInstructionsResponse · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	99
35	MsgType	p	Registration Instructions Response
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
513	RegistID	EXAMPLE
514	RegistTransType	0	New
508	RegistRefID	EXAMPLE
506	RegistStatus	A	Accepted
10	CheckSum	227

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
A	Accepted	ACCEPTED
R	Rejected	REJECTED
H	Held	HELD
N	Reminder – i.e. Registration Instructions are still outstanding	REMINDER_IE_REGISTRATION_INSTRUCTIONS_ARE_STILL_OUTSTANDING / REMINDER_I_E_REGISTRATION_INSTRUCTIONS_ARE_STILL_OUTSTANDING

Where tag 506 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
PositionReport	AP	Optional	Optional	directly on the message body
RegistrationInstructionsResponse	p	Required	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 506 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 registStatus = message.fields[506]?.raw;// e.g. "A" — Accepted// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(506)  ?.enumValues?.find((e) => e.value === registStatus)  ?.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