# Typo?: The 81 value of 452(PartyRole)

**URL:** <https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723>\
**Category:** General Q&A\
**Created:** [August 18, 2022, 2:17pm UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723 "2022-08-18T14:17:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertlau](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@robertlau](https://forum.fixtrading.org/u/robertlau)\
**Post date:** [August 18, 2022, 2:17pm UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/1 "2022-08-18T14:17:16Z")

</div>

The 81 value of 452(PartyRole) in fiximate is as below. Don’t know if the “cient” is a typo?

Broker **cient** ID Added EP68 Updated EP223 [BrokerClearingID]

Also, why “BrokerClearingID” not quite match the “Broker **cient** ID” ?

---

<div class="post-metadata">

**Author:** ![hanno.klein](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/hanno.klein/32/38_2.png) [@hanno.klein](https://forum.fixtrading.org/u/hanno.klein)\
**Post date:** [August 18, 2022, 6:59pm UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/2 "2022-08-18T18:59:38Z")

</div>

This has been fixed in EP271, publication will be early next week. See [here](http://forum.fixtrading.org/t/public-comment-period-fix-protocol-gap-analysis-errors-and-omissions-2021/16386/16) for details.

![image](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/83a145646330264cc41314c9bdd11734275c980f.png)

---

<div class="post-metadata">

**Author:** ![robertlau](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@robertlau](https://forum.fixtrading.org/u/robertlau)\
**Post date:** [August 19, 2022, 2:00am UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/3 "2022-08-19T02:00:54Z")

</div>

@hanno.klein, Just curious - I was thought it is “Broker **Client** ID” as [some sites](https://btobits.com/fixopaedia/fixdic50-sp2-ep/tag_452_PartyRole_.html) states 81=Broker Client ID. Or Broker Clearing ID and “Broker clearing identifier” are the same?

---

<div class="post-metadata">

**Author:** ![hanno.klein](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/hanno.klein/32/38_2.png) [@hanno.klein](https://forum.fixtrading.org/u/hanno.klein)\
**Post date:** [August 19, 2022, 10:34am UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/4 "2022-08-19T10:34:28Z")

</div>

@robertlau, unfortunately this happens when people copy content from the FIX website and make changes without checking with FIX, e.g. through this forum (as you are doing 🙂 ). The website you are referring to has also copied text from the appendix 6-G of the FIX legacy specification and provides a [link](https://btobits.com/fixopaedia/appendices/appendix_6-g.html) to it. If you follow that link you will see:

![image](https://canada1.discourse-cdn.com/flex010/uploads/fixtrading2/original/1X/d3e19bd6c80b06cc082537b5cb3e895837fba331.png)

It is the identifier of the broker used for clearing purposes. It is not the identifier for a client of a broker. The latter is covered by PartyRole(452)=3 (Client ID).

---

<div class="post-metadata">

**Author:** ![ltaikit](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/ltaikit/32/743_2.png) [@ltaikit](https://forum.fixtrading.org/u/ltaikit)\
**Post date:** [August 19, 2022, 5:53pm UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/5 "2022-08-19T17:53:50Z")

</div>

For the record: The original submission for this value to be added states that it is “broker clearing ID” NOT “broker client ID”.

---

<div class="post-metadata">

**Author:** ![robertlau](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@robertlau](https://forum.fixtrading.org/u/robertlau)\
**Post date:** [August 20, 2022, 1:54am UTC](https://forum.fixtrading.org/t/typo-the-81-value-of-452-partyrole/16723/6 "2022-08-20T01:54:04Z")

</div>

Thanks @hanno.klein, @ltaikit. Got it.
