SecurityIDSource

, ,
1

Imported from previous forum

2

Do we not need a SecurityIDSource value to represent the sender ? i.e. if I maintain a unqiue instrument ID which I want to set in SecurityID what would I set SecurityIDSource to ?

Regards, Azam.

3

[ original email was from Jim Northey - jnorthey@jandj.com ]
SecurityIDSource is optional by agreement with counterparty.

For a unique identifier that does not comply with any of the standards listed you can agree to use a value in the one hundreds that is mutually agreed upon with your counterparty or just omit the SecurityIDSource attribute (field).

> Do we not need a SecurityIDSource value to represent the sender ? i.e. if I maintain a unqiue instrument ID which I want to set in SecurityID what would I set SecurityIDSource to ?
>
> Regards, Azam.
>

4

Thanks for that. However most organisations have ‘quality’ internal namespaces and as such I would suggest a common value for this to represent the sender. This is useful for automatic namespace matching.

Regards, Azam.
> SecurityIDSource is optional by agreement with counterparty.
>
> For a unique identifier that does not comply with any of the standards listed you can agree to use a value in the one hundreds that is mutually agreed upon with your counterparty or just omit the SecurityIDSource attribute (field).
>
>
> > Do we not need a SecurityIDSource value to represent the sender ? i.e. if I maintain a unqiue instrument ID which I want to set in SecurityID what would I set SecurityIDSource to ?
> >
> > Regards, Azam.
> >
>