You are on page 1of 4

Introduction to the Accord GUI

In order to access the Accord service, you logon to SWIFTAlliance WebStation with your personal
username and password. Your username is linked to your PKI certificate which uniquely identifies
you on Accord.
Once you are logged in, the Accord interface loads. The interface consists of 5 modules;
these can be found in the selector bar on the left side of the screen. The Accord modules are:
Settings, Easy Search, Tasks, Monitor and Dashboard. You use the Settings module to customise your
Accord environment. We will see this at a later stage.
The About tab shows you the version of the Accord GUI, your certificate name and your
roles: these are the permissions that have been assigned to you.
Use the Easy Search module to quickly run a simple search without the need to predefine a
task. Fill in one or more of the fields and press the Search button.
The Tasks module is used to manage tasks: you can run pre-defined tasks or create your
own. Tasks are searches in the Accord database. They can be used to look for confirmations that
match the search criteria that you specify.
The Monitor module is where operators spend most of their time. It shows an overview of
your active tasks and the confirmations that each task has found. Here you manage your
confirmations and do exception handling.
The last module, Dashboard, provides a dashboard for supervisors with statistical
information such as matching rates and operator activity.
To view matching rates, select this option from the drop-down list and choose the period
you want to cover, from 1 to 24 hours. Then click the submit button.
For each Deal Status, the dashboard shows the number of confirmations that were
processed over the period you selected. Each line represents a different instrument. If needed, you
can toggle between absolute values and matching rates in percentages.


Forcing Match

An Accord, a trade is mismatched when the most important fields are identical but when there are
differences between other fields, typically containing the settlement details.

1) When you open the trade details you will notice a red traffic light next to each mis-matched
field.

2) In this particular case, the difference is cosmetic and you conclude that these confirmations
should actually match. You use the Accept As Match action to instruct Accord to update the
deal status from Mismatched to Matched.


3) When you double-click the task to refresh the task output, the confirmation no longer
appears in the task output for mis-matched confirmations. Instead it appears in the output
of the task for matched confirmations.

4) Double-click the confirmation to view its details. The deal status is indeed matched.


5) The History tab shows you the actions taken on this confirmation. It tells you that this trade
was manually matched as a result of an operator intervention.







Sending a Chaser

An unmatched trade, is a trade for which we have not yet received our counterpartys confirmation.
You can send a chaser to remind your counterparty that they still need to confirm this trade. Select
Create Chaser from the context-sensitive menu.

1) You are now looking at the Chaser Composition window. The message for your counterparty
can be typed in the right half of the window but this is time-consuming and not very
efficient.

2) It is better to select a chaser template, this is a pre-defined message that contains a
combination of free text and fields from the confirmation for which you are creating the
chaser. The NoConfRcvd template asks your counterparty to confirm this trade.

3) When you press Send Chaser, Accord sends the message you have composed. If your
counterparty is also using Accord for this transaction, they will receive the chaser in their
Accord interface. Otherwise, Accord will send them an MT 399 message in your name.

4) You want to keep track of the confirmations for which you have sent Chasers. You can easily
do this by assigning a User Status to this trade. In this case we assign the status ChaserSent.
You can search for confirmations based on their User Status.

5) When you go to the History tab, you can see that a chaser was sent, at which time and by
whom.





Viewing Paring Confirmations

This is a very powerful feature of Accord that is called Pairing. A trade is unmatched when Accord
cannot find a confirmation that contains the same trade details. The pairing process constantly looks
for duos of confirmations that might be related to the same trade as they contain the same values in
all but one or two of the crucial fields defining the transaction. In practice, it means that the pairing
process finds discrepancies due to human mistakes or misunderstandings.

1) This active task looks for unmatched deposit confirmations.

2) When you open the trade details, you see that Accord has not found a matching
counterparty confirmation.


3) Notice the presence of the Pairing tab. Accord has found 1 message that pairs with your
confirmation.

4) When you click on the Related Item button, you see the details of the paired confirmation.
You notice that there is a difference in the Value Date.


5) You conclude that this confirmation is indeed related to the same trade and you verify the
correctness of your own confirmation. You find that your counterparty has made an error so
you decide to send a chaser asking to amend the trade details. Use the pre-defined chaser
template Amend Value Date.

6) You assign the User Status Chaser Sent to keep track of the actions that you have taken.