The data matching engine of the TR world

• Collect it• Cleanse it

• Match it

Why do you need TRAMS?

6 Trade repositories

100s of FCMs

1000s of clients

1,000,000s of lines of data

What could possibly

go wrong?

TR output file

DelegatedTR output

file

Delegated TR output

file

Firm books and

records

TRAMS

Client TR

Clg Broker 1 TR

Clg Broker 2 TR

TRAMS Example:

Back office system

Clearing Broker 1

Clearing Broker 2

Multiple file outputs, multiple repositories,

no certainty of consistent

or correct records

UTI management such as enrichment or

reconciliation between different data sources

360 degree vision of your data

Account segregation

Daily Summary of Exceptions

14/04/2023 6

Daily view of exceptions

Set up rules which determine how your data is matched and reported

on

Compare all your data with your clients or the Trade

Repository

Data is mapped to the Golden Source of data Audit adjustments

being made

Flexible reporting – you decide how to break your data up

Daily Summary of Exceptions - Detail

Reporting now

Trades & positions in multiple systems

Bilateral OTC & Exchange-Traded reports follow different paths

Manual feeds to books & records No guarantee of the accuracy

of your trade reports Yet to achieve full reconciliation

of your books & records against TR

Reporting using TRAMS

Collects, identifies anomalies & normalises the data

Matches TR outputs to your books & records

Rules based reconciliations Automated interfaces (adaptors) UTI reconciliation across multiple

sources Data accuracy along the audit trail

Risk of future fines and loss of professional reputation

Automation of manual processing eliminates exposure

What difference does TRAMS make?

What does this mean to you?

Client retention

Generate more business

No worries about future fines

Reduce risk

A decent night’s sleep…

Stay out of jail !

9