NetGrossInd (FIX tag 430)

intFIX 4.4FIX 4.2

NetGrossInd (tag 430) 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 2 defined values.

At a glance

Tag
430
Name
NetGrossInd
Datatype
int
Dialects
FIX 4.4 and FIX 4.2
Messages
2
Valid values
2

What the specification says

FIX 4.4

Code to represent whether value is net (inclusive of tax) or gross

FIX 4.2

Code to represent whether value is net (inclusive of tax) or gross.

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

A real message using tag 430

BidResponse · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength107
35MsgTypelBid Response (lowercase L)
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
420NoBidComponents2 entries2repeating group
12Commission125000.00
430NetGrossInd1Net
12Commission125000.00
430NetGrossInd1Net
10CheckSum217
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.

ValueMeaningSymbolic name
1NetNET / Net
2GrossGROSS / Gross

Where tag 430 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 4.2Where in the message
BidRequestkOptionalOptionalinside the BidCompReqGrp component
BidResponselOptionalOptionalinside the BidCompRspGrp component

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 430 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 netGrossInd = message.fields[430]?.raw;// e.g. "1" — Net// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(430)  ?.enumValues?.find((e) => e.value === netGrossInd)  ?.description;

Other int 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