Tag commonly used to pass foreign investor ID

, ,
1

Imported from previous forum

2

Hi All,

May I know which FIX tag commonly used in the market to communicate investor ID such as

  • Foreign Investor ID / IRC No. (Korea Market)
  • CDS No. (Malaysia Market)
  • FINI ID (Taiwan)

Is it tag1 or tag109?

Thanks,

Mike

3

[ original email was from John Greenan - john.greenan@alignment-systems.com ]
In FIX 4.2 it’s tag 1. I’ve implemented tag 1 for Taiwan, Korea, Shanghai and Shenzhen.

Hi All,

May I know which FIX tag commonly used in the market to communicate
investor ID such as

  • Foreign Investor ID / IRC No. (Korea Market)
  • CDS No. (Malaysia Market)
  • FINI ID (Taiwan)

Is it tag1 or tag109?

Thanks,

Mike

4

I’ve used it in 4.2 for Warsaw and Moscow(MICEX).

In FIX 4.2 it’s tag 1. I’ve implemented tag 1 for Taiwan, Korea, Shanghai and Shenzhen.

Hi All,

May I know which FIX tag commonly used in the market to communicate
investor ID such as

  • Foreign Investor ID / IRC No. (Korea Market)
  • CDS No. (Malaysia Market)
  • FINI ID (Taiwan)

Is it tag1 or tag109?

Thanks,

Mike

5

In FIX 4.3 and above it is the Parties block as follows:

448 PartyID
447 PartyIDSource with the values
1 = Korean Investor ID or
4 = Malaysian Central Depository Number or
3 = Taiwanese Trading Acct
452 PartyRole 5 = Investor ID

Regards,
Hanno.

Hi All,

May I know which FIX tag commonly used in the market to communicate
investor ID such as

  • Foreign Investor ID / IRC No. (Korea Market)
  • CDS No. (Malaysia Market)
  • FINI ID (Taiwan)

Is it tag1 or tag109?

Thanks,

Mike

6

How are firms handing countries that are not accounted for in Tag 447, such as India or Brazil?

Thanks,
Monica Vega Amor/ Linedata

Hi All,

May I know which FIX tag commonly used in the market to communicate investor ID such as

  • Foreign Investor ID / IRC No. (Korea Market)
  • CDS No. (Malaysia Market)
  • FINI ID (Taiwan)

Is it tag1 or tag109?

Thanks,

Mike

7

[ original email was from Andrei Goldchleger - agoldchleger@bvmf.com.br ]
There are at least two options:

  1. Use PartyIDSource = ‘D’ (Proprietary/Custom Code)

  2. Define a custom domain.

8

Thanks, will look into both options.

There are at least two options:

  1. Use PartyIDSource = ‘D’ (Proprietary/Custom Code)

  2. Define a custom domain.

9

[ original email was from John Greenan - john.greenan@alignment-systems.com ]
Thread resurrection!

What version of FIX are you using and for which asset class? New order single or new order list? Direct connection or via hub?

For 4.2 and equities any broker I’ve ever set this up with has used tag 1, that about 30 brokers to trade Shanghai/Shenzhen/Taiwan/Korea.

I would always advise NOT to create custom interpretations of existing tags and/or custom values for existing tags. That can cause havoc if you are using a non-direct connection to a broker - if there’s a hub inbetween the buy-side and sell-side.

Thanks, will look into both options.

There are at least two options:

  1. Use PartyIDSource = ‘D’ (Proprietary/Custom Code)

  2. Define a custom domain.