Post:marker

Post:marker is Tullett Prebon’s straight-through processing service for post-trade notifications. Created in response to client demand, it reinforces Tullett Prebon’s commitment to hybrid broking, offering traders the efficiency of automated trade confirmation combined with the understanding and insight that only voice broking can provide.

Post:marker facilitates straight-through processing and enhances operational efficiency;

As soon as trade execution has taken place, traders receive electronic notifications to their desktop;

They can accept or reject notifications with a single click, so that errors in trades can be detected and corrected more quickly;

Following affirmation, trade details are transmitted automatically into counterparties’ middle and back office systems, so that positions are updated immediately.

The Technology

Post:marker is hosted on a secure IIS web server. All connections are via https protocol (hypertext transfer protocol secure) using strong encryption;

Users are authenticated to the Post:marker system via a combination of username/password and digital certificate (1024 bit);

All transactions are represented in XML (extensible markup language) documents, which are governed by a Document Type Definition (DTD).

Legal status of approved transaction

This is not affected by the Post:marker service. The legal record of the contract remains the voice tape or the transaction log of the trading platform.

 Post:marker DTDs

• Documents to View or Download
  (Acrobat PDF)

---

 Post:marker Schemas

• Weekly Roll Convention Scheme
  (Acrobat PDF)

---

 Post:marker Documentation

Tullett Prebon have found that the documentation of the BrokerML standard has a mixed audience with both business and technical customers.

Our objective is to make the acquisition and navigation of the appropriate BrokerML specifications, with regard to any given product, as painless as possible. The documentation has been divided into what is hopefully a logical set, from which the relevant data can be obtained.

The documentation has been divided in two main categories:

1. Generic aspects of BrokerML:
Introducing the concepts and components that are present in all BrokerML XML documents.

2. Product Specific Properties:
Defining the components of BrokerML that are specific to a given product or trading strategy.

For a given product the reader should read all of the generic documents combined with the specific documentation addressing the relevant product.

For example a reader responsible for Term Deposits should obtain the following documents.

---

 Generic Documents

• BrokerML - Overview v2.3
  High level overview and introduction to the BrokerML standards. (Acrobat PDF)
• BrokerML - Business Component Framework v2.3
  The business components of BrokerML, high level.(Acrobat PDF)
• BrokerML - Business Component Framework Technical Definitions v2.3
  The business components of BrokerML at a more technical level. (Acrobat PDF)
• BrokerML - Coding Schemes v2.3
  Explains the approach to static data. (Acrobat PDF)
• BrokerML - Design Guidelines v2.4
  BrokerML Design Guidelines document that may be of interest to technicians in this area. (Acrobat PDF)

---

 Product Specific Documents

• BrokerML - Term Deposit Definition v2.4
  Specific components for term deposit deals.
  (Acrobat PDF)