In our current project (FIX 5.0 sp2), we introduced the Symbol tag in the NewOrderMultileg <AB> message. This raised the question of whether the NoLegs group (tag 555) with a value of 0 must always be included in the message when no legs are present.

Context:
• According to the FIX specification, the NoLegs tag is used to indicate the number of legs in a multileg order. A value of 0 means there are no legs.
• The FIX protocol enforces strict message structure compliance to ensure compatibility between systems and market participants.

Questions:
1. Is it strictly required by the FIX specification to include the NoLegs group with a value of 0 when no legs are present in a multileg order?
2. What are the potential consequences (e.g., message rejection) of omitting this tag when there are no legs?
3. Are there any best practices or recommendations regarding this? For example, would it be better to make this tag conditionally required?

We want to strike a balance between adhering to the FIX specification and optimizing message size and structure. Any advice or practical examples would be greatly appreciated!

In our current project (FIX 5.0 sp2), we introduced the Symbol tag in the NewOrderMultileg <AB> message. This raised the question of whether the NoLegs group (tag 555) with a value of 0 must always be included in the message when no legs are present.

Context:
• According to the FIX specification, the NoLegs tag is used to indicate the number of legs in a multileg order. A value of 0 means there are no legs.
• The FIX protocol enforces strict message structure compliance to ensure compatibility between systems and market participants.

Questions:
1. Is it strictly required by the FIX specification to include the NoLegs group with a value of 0 when no legs are present in a multileg order?
2. What are the potential consequences (e.g., message rejection) of omitting this tag when there are no legs?
3. Are there any best practices or recommendations regarding this? For example, would it be better to make this tag conditionally required?

We want to strike a balance between adhering to the FIX specification and optimizing message size and structure. Any advice or practical examples would be greatly appreciated!

• fix-protocol

Share Improve this question Follow edited Mar 27 at 10:18 Christoph John 3,35822 gold badges1515 silver badges2525 bronze badges asked Mar 26 at 23:28 Alex LyovochkinAlex Lyovochkin 3333 bronze badges 2

• 1 Wait a minute, a multi leg order without legs? – Christoph John Commented Mar 27 at 4:52
• For e.g., we have an existent spread instrument with the symbol "A-B", with Leg1= [LegSymbol=A, ratio 1, side Buy]; and Leg2=[LegSymbol=B, ratio 1, side Sell] is it enough to define Symbol=A-B only, or do we need to put NoLegs=0, or having NoLegs with full matching spreads definition is mandatory – Alex Lyovochkin Commented Mar 27 at 10:13

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 4

I learned that it seems to be OK to have a multi leg order without legs. In fact, this was changed in EP131: https://www.fixtrading./packages/ep131/

You must not send NoLegs=0 since the NumInGroup fields must bear a positive number: https://www.fixtrading./standards/tagvalue-online/#lexical-encoding-for-fix-datatypes (look for NumInGroup)

Sequence of character digits without commas or decimals. Value must be positive.

But if you want to use FIX5.0 SP2 (without any of the EPs or FIXLatest) then you probably need to change your data dictionary and let your counterparties know that you do not send NoLegs group when no legs are present. Otherwise you will end up with rejected messages.

It is common practice to use features/fields from newer FIX versions, so it should normally pose no problem to leave out the NoLegs group as long as your counterparties are aware of it.