TLMRecsPrem2 4 1 1UserGuide
TLMRecsPrem2 4 1 1UserGuide
TLMRecsPrem2 4 1 1UserGuide
User Guide
DISCLAIMER
SmartStream Technologies makes no representations or warranties regarding the contents of this document. We reserve the right to revise this
document or make changes in the specifications of the product described within it at any time without notice and without obligation to notify any
person of such revision or change.
COPYRIGHT NOTICE
2000 -2013 Copyright of SmartStream Technologies. All rights reserved. No part of this publication may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means - electronic, mechanical, photocopying, recording, or otherwise - without the prior written
permission of SmartStream Technologies Limited.
INTELLECTUAL PROPERTY WARNING
The contents of this document and the software it describes are the intellectual property of SmartStream Technologies Limited. The ideas
contained in this document must not be disclosed to any third party.
TRADEMARK NOTICE
TLM® is a registered trademark of SmartStream Technologies Ltd. All rights reserved.
Other trademarks recognised and property of their respective owner.
DOCUMENT INFORMATION
Edition: 1
November 2013
Contents
Contents
Index ......................................................................................... 1
About this Guide
Introduction
TLM Reconciliations-Premium is the best-of-breed Reconciliations solution for
automation of cash and securities reconciliation. It delivers pre-packaged
processing and user interfaces, and leverages the power of the leading software
on the market, TLM Reconciliations, to maximise match quality, performance,
and user interface experience.
It helps users to discover the root causes of transaction failures, and take
corrective action to reduce costs and improve match rates. Exceptions can be
inspected, investigated, analysed, and resolved using the browser-based
interface.
Related information
The following guides provide additional information:
• SmartStudio User Guide
• Static TLM Administration Guide
• TLM Reconciliations-Premium Administration Guide
• TLM Reconciliations-Premium Data Dictionary
• TLM Reconciliations-Premium Installation Guide (For Oracle and SQL
Server)
• TLM Reconciliations-Premium SYST Table Descriptions
• TLM Reconciliations-Premium User Administration Guide
• WebConnect Installation Guide
About this Guide 3
Logging on
To use the software, you must enter the launch page URL in a browser, such as
Internet Explorer. The Login page will then be displayed and you can enter your
username and password. These are allocated to you by your Administrator.
To log on
1. Enter the launch page URL in a browser.
For example, http://192.168.111.88:7001/WebConnect/login/login.jsp
The Login page is displayed:
This message means that either your user type is not licensed to use the
stated message types, or that the licences for this message type have all been
taken by other users. If you require access to the stated message types, see
your System Administrator.
8 Using the main menu
The special commands that are usually present on the menu are as follows:
• The Options > Change Password option that enables you to change your
password, page 10.
• The Help > Contents option that launches online help, page 11.
• The Help > About option that displays the WebConnect version and build
date.
• The Logout option that enables you to logout, page 12.
Changing password
Provided that your user role gives you access to the Change Password option,
you can change your password at any time without supervisor intervention.
If you attempt to change your password to one that has been used previously, an
error might be displayed that refers you to your system administrator. By default,
the system is configured to prevent you from reusing your last four passwords.
If you search for a file name with an extension, group the entire string in
double quotes ("file name.ext").
• You can use the AND, OR, and NOT operators to refine your search by
creating a relationship between search terms. If you do not specify an
operator, AND is used. For example:
• Specifying "message AND feed" finds topics that contain both
"message" and "feed."
• Specifying "Security OR alias" finds topics that contain either the term
"security" or the term "alias" or both.
• Specifying "balance" NOT "trial" finds topics that contain "balance" but
not "trial."
12 Logging off
Logging off
To log off from TLM Reconciliations-Premium
1. Do one of the following
• Select Menu > Logout option.
Dates
The format in which dates are displayed in WebConnect is dd/MM/yyyy.
If you want to customise the date format you must contact your System
Administrator.
If you want to change the maximum row limit, you will need to contact your
System Administrator.
14 Working with dashboards
Launching a dashboard
In TLM Reconciliations-Premium you might have a cash dashboard, a security
positions dashboard, or an exception dashboard. Each reconciliation service to
which you have subscribed usually will have its own dashboard. Sometimes,
however data for different instrument types, such as cash and securities is
presented in the same common dashboard because the dashboard is the same for
both.
To open a dashboard, you click on or press <Enter> on a dashboard name in the
menu. The first dashboard that you open is displayed in its designed position and
size. When you open a second dashboard, it either opens in an empty a space in
the same window, or as a new tab that overlaps the dashboard that is already
open. If you open a duplicate of an already open dashboard, it is displayed in a
new tab that overlaps the original dashboard. You can optionally open a
dashboard in a new browser window using <Shift + Ctrl>.
To launch a dashboard
1. Select Menu.
A series of menus are displayed.
If the child dashboard is already open and you attempt to launch it again without
pressing the <Shift> key, the dashboard simply refreshes.
Resizing dashboards
Where dashboards are displayed in separate spaces, you can maximise them by
double-clicking on the dashboard tab; double-click again to reset the dashboard
back to its original size and position.
You can also resize the dashboards by dragging the edges. For example, the
image below shows what happens when the right corner of the chart is dragged
towards the right, reducing the size of the tree:
The grey shaded lines show where the dashboards will be resized to when the
mouse button is released.
If you resize or maximise the browser window, the dashboards will
automatically resize to fit in the window.
16 Working with dashboards
Refreshing data
When you make changes on a dashboard, the data in that dashboard might have
to be refreshed before the changes are displayed. You might also need to refresh
the data in other open dashboards to reflect the change.
• Click the refresh icon on the top right of the dashboards title tab.
If there are multiple tabbed dashboards in the space, you can alternatively
right-click and select Refresh All to update the data on each of the tabbed
dashboards.
2. The search prompt is displayed, pre-loaded with the options you selected
initially. Click [Search].
The control's data is refreshed.
If a grid row was previously highlighted, the row is now displayed as the
first row in the grid page. For example, if you had row 9 selected and the
grid displayed rows 1 to 30 on the first page, when you refresh the grid, the
data is refreshed and the grid displays rows 9 to 38, with row 9 highlighted
at the top of the page.
If the row that was highlighted is no longer returned by the search, for
example if some data in that row has been updated and it is now filtered out
by the search, the next row down in the grid is highlighted instead.
Getting started with the software 17
Example:
If any tolerance values have been configured for an input field, they are
displayed when you hover the mouse over the field.
You can use an asterisk (*) as a wildcard in '=' or 'like' searches. You can
also use % as a wildcard in 'like' searches.
Where the search attribute is a datetime attribute, you can enter a time range
as well as a date range.
18 Working with dashboards
2. Click [Search].
The results of your search are displayed.
Default dashboards are displayed with a check mark next to the Set As
Default option.
When you next logon on the same computer, the dashboard is launched
automatically.
Getting started with the software 19
Closing dashboards
Single dashboards are closed in the usual way, by clicking the in the top right
corner of the dashboard’s tab, or by right-clicking on the tab and selecting Close
from the context menu.
You can also close all dashboards in a space, optionally leaving only the
dashboard that is currently in focus open.
If there are more rows returned from the search than will fit in a single
dashboard window, use the scroll bar on the right to scroll down through all the
returned rows.
If grid data is still loading, a blue rotating circle is displayed in the top left of
the grid.
If the grid is in an error state, a red circle with a line through it is displayed in
the top right of the grid, and you cannot perform any actions on the data. You
need to close the grid and reopen it to continue to work with the data.
In situations where there are many tabbed dashboards in a single space, there
might not be enough room to display the upper business logic toolbar, and as
such, it is made available at the top-right of the space via the drop-down menu.
For example:
Getting started with the software 21
You can then use the arrow keys to move the focus up, down or across to the
next adjacent cell.
You can use the <Tab> key to move to focus to the next adjacent cell to the
right, and the <Shift + Tab> keys to move to focus to the next adjacent cell to the
left.
You can also use the <Enter> key to move to focus down to the next cell below,
and the <Shift + Enter> keys to move to focus up to the next cell above.
You can use the <Page Up> and <Page Down> keys to scroll through the grid,
however this does not move the focus.
In some cases, when you give focus to a cell, the heading on that cell’s column
will change. This means that the grid has been configured to use attribute names
such as the column headers, and so the column header will change each time that
you focus on an attribute with a different name to the current column header.
Selecting records
To work with a record that is displayed on a grid, you must first select the
record. You can select individual records, groups of records, a combination of
individual records and groups, or all records in a grid.
When you select one or more groups, the group selector is displayed in orange:
.
When you select individual records, the record selector is displayed in orange
with a blue tick: .
All of the selectors act as toggles, that is, clicking once selects, and clicking
again deselects.
22 Working with grids
To select records
• To select a single record, click , or right-click on the selector and select
Select.
• To select multiple records, click for each record you want to select, or
right-click on each selector and select Select.
• To deselect a single record, click for each record that you want to
deselect, or right-click on each selector and select Deselect.
• To select all the records in the grid, click , or right-click in the selector
pane and select Select All.
• To deselect all the records in the grid, click , or right-click in the selector
pane and select Deselect All.
If any records are already selected, clicking selects all remaining
records. Click again to deselect all.
• To select all groups on the grid, click , or right-click in the selector pane
and select Select All.
There might be two of these buttons in your grid; the one on the left is for
aggregate-on-change groups, and the one on the right is for break-on-change
groups. Clicking on either of these buttons will select or deselect all groups.
• To deselect all the groups in the grid, click , or right-click in the selector
pane and select Deselect All.
If any groups are already selected, clicking selects all remaining groups.
Click again to deselect all.
• To select a group of items, click . Typically, this icon spans more than
one row, for example:
There might be two lots of group selectors on your grid; the one on the left
is for aggregate-on-change groups, and the one on the right is for break-on-
change groups.
• To deselect a group, click for each group that you want to deselect, or
right-click on each group selector and select Deselect.
Getting started with the software 23
The links contained in the context menu depend on the dashboard you are
viewing, however the following options are typically available:
• Change the view - if other views are configured for this grid, page 24.
• Links to launch any child dashboards - for example, the Item Detail
dashboard, page 15.
• Add an attachment – enables you to attach a document to an item, proof, set
or message feed, page 24.
• Edit – puts the grid into edit mode if an edit tool is configured for the grid,
page 90.
• Export the data - to a PDF or Excel document, page 35.
• Select rows and groups, page 21.
• Launch Audit Trail - for the last selected item, page 46.
• Activate business logic tools on the selected items, where available,
page 43.
If more than one item is selected, the same context menu is displayed. The action
that you select is performed on all the selected items, according to the following
rules:
• If you select a number of individual items, the business logic processes them
as one group.
• If you select a number of groups, the business logic still treats them as
separate groups.
• If you select a group and a number of selected items, the business logic
treats the group as a group and all the individual items as another group.
24 Working with grids
Attaching a document
You can use the Add Attachments function to add documents to items, proofs,
sets and message feeds.
You might need to configure your browser’s security settings to enable the
document attach function to work, if your organisation permits you to do so.
To attach a document
1. Right-click on the relevant object in a grid and select Add Attachments.
The Add Attachment window is displayed.
Grid aggregates
Grid views can have 'Aggregate on change' settings applied to one or more of the
displayed columns. These settings group items according to values in the column
you selected and insert a Totals Row. The Totals Row aggregates the numeric
data for the group according to the selected aggregate function.
For example, if the Reconciliation Status column has a sum aggregate on change
set, items with the same Reconciliation Status are displayed together in a group
with a Totals Row at the end of each group showing the sums of the amounts or
quantities that can be summed.
TLM WebConnect represents the aggregate functions with different icons. You
can display the aggregate functions that have been applied to a grid by right-
clicking on a column header and selecting Show Aggregate Criteria. A new row
with a pale blue background is displayed below the column header row, which
contains any aggregates applied to the columns.
For example, in the following dashboard, a count aggregate function has been
applied to Status, a sum aggregate function has been applied to Amount, and a
same aggregate function has been applied to Item Type:
The Aggregate On Change icon is displayed when you hover the mouse over
the column header and indicates that those columns will trigger the display of an
aggregates row whenever the value in that column changes. If required, you can
keep these icons displayed by right-clicking on the column header and selecting
Lock Symbols On.
Getting started with the software 27
Max
Absolute(Max)
Min
Absolute(Min)
Sum
Absolute(Sum)
Net
Absolute(Net)
Same
Average
Weighted Average
Weighted average
The weighted average function uses data from two columns to calculate data,
rather than just one column. The two values that are used for the calculation are
a weighted average and a weighting factor, for example Price and Quantity
respectively. The idea behind the function is to show the overall average Price
paid across the group of items for a single item. The weighted average is
calculated for those two columns as follows:
Imagine a grid that contains the following data:
Trade ID Quantity Price
1 10 10
1 15 10.5
1 20 11
Sorting Data
Each column on the grid displays a drop-down menu from which you can select
sort options for up to 9 columns. A small black arrow in the bottom right corner
of each column header indicates that there is a drop-down menu.
The priority that is set depends on what other sort options have been set for that
view. If this is the only column with sort options, the priority is 1. If there are
already, say, two other columns with sort options, the priority is 3.
Break-on-change or aggregate-on-change options are greyed out in the drop-
down menus, because users cannot specify them in TLM WebConnect.
However, if the View specifies break-on-change or aggregate-on-change options
they are highlighted in the drop-down menu and displayed in the column header
cell. The symbols for these settings are as follows:
Break-on-change
Aggregate-on-change
Note the following:
• If you change any sort options, all on-change settings defined by the view
are removed.
• If you change your view, you will lose your sort and filter settings.
For details on how to change the view, see page 24.
• If you have selected data using groups, you will lose your selection when
you update your sort and filter settings.
• The number of records that a dashboard can display is determined by your
system settings. When your search retrieves more records than the specified
number, the sorting and filtering mechanism cannot retrieve the missing
rows.
To sort data
1. Click on the header of the column you want to sort on to display the sort
menu:
2. To sort the column data in ascending order, select . To sort the data in
descending order, select .
If a column already has sort criteria, set by the user or by the selected View,
the sort is represented by the same symbols in the header cell, for example:
Filtering data
You can dynamically set filtering options for any column on the grid, and for
columns that contain less than 20 distinct values, a drop-down menu is provided
from which you select a value to filter by.
By default the filter works on an exact match basis, so if for example you select
the Set ID column, and enter 123456 in the filter field, the grid displays the
records from the search where the Set ID is equal to 123456. Patterns are case-
sensitive.
The grid data is filtered, and a filter icon is displayed when you hover
the mouse over the column header to show that a filter has been applied to
that column. For example:
A filter icon is also displayed in the status bar when a filter has been
applied to a grid.
3. The grid data is filtered, the image that you have filtered by is displayed in
filter field, and a filter symbol is displayed in the column header to show
that a filter has been applied to that column.
Exporting data
You can export all the data rows in a grid to a spreadsheet or a PDF.
You might have to change your browser’s security settings to enable data to be
exported, if your organisation permits you to do so.
For details on how to configure your internet security, see page 36.
3. If required, you can save the PDF by clicking the Save button on the
toolbar.
36 Working with grids
If the context menu does not contain the Configure option, you cannot change
how the treeview is displayed, other than expanding and collapsing the nodes
using the + and - icons.
The attributes displayed on this screen reflect the group bys configured in
SmartStudio. In this example, the tree has five visible group bys configured
in SmartStudio, with a default level of 3. Visible nodes are indicated by an
eye icon ( ). If you select only invisible nodes (that is, those without the
eye icon) the resulting tree will be blank.
2. To add another group by attribute to the view, select the attribute from the
left-hand list, and click .
38 Working with treeviews
3. To change the order in which the group by attributes are displayed, select an
attribute in the right-hand list and either drag and drop the attribute, or use
the and buttons to move the attribute up or down.
For example, if you configure the tree to display all 5 group bys in the
following order:
4. If you want to revert the tree back to how it was displayed when it was
initially loaded, click [Reset] on the Tree Configuration window.
Getting started with the software 39
If you then select one of the child dashboards, the child is launched as a
drilldown from the currently highlighted treeview node.
If you already have an instance of the child dashboard open and you select the
same dashboard but for a different node, the existing instance of that dashboard
is replaced. If you press <Shift> before selecting the same dashboard, a new
child dashboard is opened.
If the treeview's children are configured in SmartStudio as being in sequence,
you can also use the Next in Sequence and Previous in Sequence options to
cycle through the sequence of available child dashboards. Selecting Next in
Sequence displays the next child dashboard in the sequence. When the last child
dashboard for that node in the tree has been displayed, the first dashboard for the
next node is displayed. Previous in Sequence performs the opposite function,
displaying the previous child dashboard in the sequence, working through
previous nodes in the tree.
If the treeview's children are not configured as being in sequence, selecting Next
in Sequence and Previous in Sequence simply highlights the next or previous
leaf node in the treeview.
If the treeview's children are configured in SmartStudio as being in sequence and
to allow navigation from child, you can also perform this navigation from the
child dashboard itself, using Next in Sequence on Parent and Previous in
Sequence on Parent.
These navigation options can also be performed using keyboard shortcuts,
see below.
40 Working with treeviews
There are a few instances where the behaviour of these keyboard shortcuts
differ:
• If a treeview is launched that has no child treeview controls, keys 1 and 3
navigate its own drilldowns from node to node, in the same way as 4 and 6.
• If a child control launched from a treeview is in focus but is not a tree itself,
keys 4 and 6 navigate the parent tree drilldowns from node to node, in the
same way as 1 and 3.
• If a child control launched from a treeview is in focus, and the focus is on an
editable cell or field, or a record browser, the number pad keys are used for
number input. You must press the <Ctrl> key while using the 1, 3, 4, and 6
keys for keyboard navigation of the parent treeview.
Getting started with the software 41
For datetime attributes, you cannot edit the time element. If the datetime
attribute is configured as editable, only the date element is displayed and can be
edited.
For forms only, tools can also be fired using form buttons.
The availability of the tools depends on the item or exception status. Tools are
greyed out when they are not applicable to the selected items current status.
44 Working with Business Logic tools
Progress Window
Business logic is carried out a group at a time, and progress is displayed on a
Progress window. For example:
The status bar at the top of the window updates the following information during
processing:
The number of operations that have been completed so far.
The lower part of the windows displays any error messages received, up to a
maximum of 10.
When processing has completed, two additional 'Show All' buttons are displayed
to allow you to see more results. For example:
If at any point you want to cancel the business logic processing for the current
group, click [Cancel].
If you activated the business logic on more than one group, the [Cancel Queued]
button is displayed. Click this button if you want to cancel the business logic
processing for groups still waiting to be processed.
Getting started with the software 45
When you click [Cancel] or [Cancel Queued], any groups that have already been
processed are unaffected, i.e. the processing is not rolled back. If you close the
window or the browser while the business logic is still processing items, the
behaviour is the same as if you had clicked [Cancel Queued].
Toolbar icons
The tools allow you to perform the following operations on items:
Button Description
Matches selected items
Cancels a match
Deletes an item
Rejects a match
Deletes a message
Authorises a message
Rejects a message
In the Associated Items grid, you can sort and filter the data in the same way as
for any other grid.
For details on how to sort data, see page 28.
The error numbers start at 1000 when the application server starts and increment
by 1 for every error.
Managing Reconciliations
Reconciliations lifecycle
Each set is processed according to the following reconciliation lifecycle:
Managing Reconciliations 51
You can view and process items at any level in the tree using the full range of
dashboards available to you, by right-clicking the required level and selecting
the dashboard that you want to launch from the context menu. For example, to
view a summary of all Nostro items with the MUMBAI category code and a
lifecycle status of Manual Matching, expand MUMBAI, right-click on Manual
Matching and select Item Status Summary from the context menu. For
example:
2. If required, add to or edit the search criteria to further specify the items that
you want to display on the REC Lifecycles Summary dashboard.
For example, if you only want to view a set’s manual matching items,
ensure that this is the only checkbox selected in the Lifecycle Status area of
the search prompt.
3. Click [Search].
The results returned from your search are displayed in the REC Lifecycles
dashboard.
Managing Reconciliations 55
Summary dashboards
You can drill down to a range of summary dashboards from any level in the REC
Lifecycles Summary dashboard to view a graphical overview of the items at that
level. For details on REX Lifecycles Summary dashboard, see page 52.
For example, to view a summary of the items by status, type and a lifecycle
status of Manual Matching for a specific category, in the REC Lifecycles
Summary dashboard, expand the required category, right-click on the Manual
Matching node, and select Item Status Summary from the context menu.
The Items By Status and Type as well as the Matches by Status dashboards are
launched. For example:
You can view the Items by Type dashboard by selecting that tab. You can also
drill down to the details of the items displayed on the summary dashboards by
right-clicking on a bar or treeview node, and selecting the required dashboard
from the context menu. For example:
The following summary dashboards available, from which you can drill down to
view items in greater detail, as described in the following table:
Summary Displays Drills down to…
Dashboard
Items Status Charts providing an overview of Item by Type, Items by Status, Item
Summary items based on type and status, and Matches
a treeview categorised by match
types.
Items Items based on their age, grouped Items Ageing by Current Priority,
Ageing by priority, days past reference Items Ageing by Days Past
Summary date, and business entity and Reference Date, and Items Ageing
reason/resolution. by Business Entity and Reason
Resolution.
Items A summary of the exceptions raised Items by Exception Status, Item
Exception on items. Exceptions by Priority, Exceptions
Summary by Priority, Exceptions by Inbox,
Item Exceptions by Inbox.
Items Matches that require authorization. Items Requiring Authority and
Authority Matches Requiring Authority.
Summary
56 About the Reconciliations dashboards
Detail dashboards
You can drill down from any level in the REC Lifecycles Summary dashboard
to a range of child dashboards that display a grid containing the items at the
selected level. For example:
Dashboard Displays
Ad-Hoc Displays matches based on the search criteria provided in the
Matches Search Ad-Hoc Matches Search window.
Ad-Hoc Items Displays items based on the search criteria provided in the Ad-
Search Hoc Items Search window.
About Matching
The matching process identifies and groups corresponding transactions between
your general ledger and account servicer statement, to ensure that the
transactions balance and your sets are reconciled.
The following sections describe the different types of matching as well as the
process of set balancing using write-off and net items, and how the opportunity
cost on cash items is calculated.
Types of matching
Matching in TLM Reconciliations-Premium is typically carried out both
automatically and manually. When data is first loaded into the system, perfect
matches are automatically identified and reconciled. The system also produces
suggested matches and progresses them, along with the remaining outstanding
items, to the Manual Matching stage.
Automatic matching
Automatic matching is triggered on completion of a data load, and is performed
by the Matching Service.
The Matching Service processes the items, relationships and exceptions.
Items that are perfect matches, as in the example below, are matched and moved
to history.
Item Type Amount Currency
Our Credit 100 GBP
Their Debit 100 GBP
Amount Difference 0 GBP
Items that are near matches, for example statement and ledger amounts for the
same set but with small differences, are grouped into a suggested match
relationship. For example:
Item Type Amount Currency
Our Credit 100 GBP
Their Debit 110 GBP
Amount Difference 10 GBP
When the auto-matching for a set is complete, the lifecycle status of the set
changes to Progressed and the remaining outstanding items and suggested
matches are displayed on the Reconciliations dashboards.
Manual Matching
After auto-matching is complete, manual matching can be performed on the
outstanding items and suggested matches that remain in the set.
Groups of outstanding items can be formed manually, and are progressed by
either matching or raising exceptions. Throughout this process, set balancing is
achieved through the creation of write-off and net items. For details on Set
balancing, see page 59.
Depending on the quality of the group and the user or account write-off limits,
the match might require authorization by a supervisor.
Managing Reconciliations 59
Set balancing
A set is in balance when all items form a perfect match and there are no missing
balances. However, the information required to form perfect matches might not
be available at the time the user is reconciling the data. As such, and to allow
matching in real-time, write-off items can be created to enable the user to
perform matches, and net items can be created to enable the user to perform
pending matches on unbalanced groups of items.
The ability to create write-offs is constrained by the user and account write-off
limits, as described in Authorising Matching, page 61.
Write-offs
When you match a group of items with an amount difference, a write-off item is
generated that has an amount equal to the amount difference. It is created to
ensure that the set balances, and is always an ‘our side’ ledger value.
For example, the items in the match below will generate an ‘Our Credit’ write-
off item of 10 GBP, enabling the items in the match to be moved to history:
Item Type Amount Currency
Our Credit 110 GBP
Their Debit 100 GBP
Amount Difference 10 GBP
Net Items
Net items are similar to write-offs, in that they are created to facilitate the
matching of items with amount differences, and are always ‘Our Side’ ledger
values. However, net items are only created for pending and pending
authorization matches, and are deleted and replaced by a write-off when the
items in the pending group are matched. If the items in the pending group are
cancelled or deleted, the net item is deleted.
For example, the group of items in the pending match illustrated below will
generate an ‘Our Credit’ net item of 30 GBP:
Item Type Amount Currency
Our Credit 110 GBP
Their Debit 100 GBP
Our Credit 20 GBP
Amount Difference 30 GBP
A net item is automatically adjusted when items are added or removed from a
pending match, so that it always represents the amount difference of the items in
the group. For example, if the 20 GBP ‘Our Credit’ item was removed from the
pending match above, or a Their Credit item of 20 GBP was added to the group,
the value of the net item would change to 10 GBP.
Net items are created with the data values in the match, such as the settlement or
value date and references. Further items forwarded for reconciliation can then be
matched against the net item. This can be used to prevent charges being raised
on a set for outstanding items, when it is known that the items will be received
eventually.
If a match is found against a net item, the item is added to a pending match
group and the normal matching workflow is invoked.
Managing Reconciliations 61
Authorising Matching
During the manual matching process, the user’s ability to create matches is
constrained by the user and account write-off limits, both of which are set by the
Administrator.
If you attempt to perform a match with an amount difference within the user and
set limits, a write-off item is created and the match is sent to History. However,
if the match exceeds these limits, it is rejected. Depending on your configuration,
you might then be prompted to create a pending authorization match, whereby a
net item with the value of the amount difference is created, and the status of the
match changes to pending authorization.
Matches with a status of Pending Authorisation must be approved or rejected by
a second user, as described in Approving Matches. If the match has any
associated net items, the process of authorising the match will delete the net
items and create a write-off item to balance the set. For details on Approving
items and matches, see page 75.
If a match is rejected, the Relationship header and the items are left in an overall
status of Pending and the authorization status of both is changed to
Authorisation Rejected.
For further information about setting account write-off limits, refer to the
Administration Guide. For information about setting user write-off limits, refer
to the User Administration Guide.
Three-way Matching
You can optionally configure sets to be reconciled on a three-way basis. As well
as the usual Ledger and Statement side, and additional Alternate side can be
loaded, and all three sides must be present for that set to be matched. If three-
way matching is enabled on a set, the calculation of Net rules takes into account
all three sides, and calculates the net figure as the largest difference between any
two of the three sides.
For three-way matches, together with the Ledger (L) and Statement (S), the
dashboard also displays the Alternate (S) side. For example:
Managing Reconciliations 63
Managing Items
You can also perform other operations on items, such as splitting items between
suggested matches, marking items as deleted and adding items to exceptions.
64 Performing Manual Matching
Matching Items
You use the Match tool to manually match items. You would typically match
items with a status of Outstanding or Pending. You can however, also match
items with a status of Suggested, Cancelled or Recalled.
Depending on the set and user limits, the match might require authorization
before it is completed. For example, if a match is created with a value difference,
a write-off item is created to balance the set. However, if the amount difference
is too high to be written off by the user, a pending net item is created and the
match status changes to pending authorization.
While sets can be set up to accept multiple currencies, you cannot match
multiple currencies in the same match. If a cross-currency match is attempted a
warning is displayed and the match cannot be completed.
When you manually match an item, the overall status changes to Matched.
To perform a match
1. On a grid dashboard such as Items by Status or Item Matches, select the
items that you want to match.
2. Do one of the following:
• Click the row selector for each item in the match, and then click the
Match button , or right-click and select Match.
• If the grid displays only the items for a single match, you can match all
items. Click the Select All button and then click the Match button
, or right-click and select Match.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The manual match is created for the selected items.
Managing Reconciliations 65
Cancelling a match
You use the Cancel tool to cancel a match. When you cancel a match, the
status changes to cancelled.
When you cancel a pending match, the associated net item’s status changes to
deleted.
To cancel a match
1. Select the match that you want to cancel.
2. Do one of the following:
• To cancel a single match, click the row selector to select the required
item and then click the Cancel button , or right-click and select
Cancel.
• To cancel multiple matches, click the row selector for each item that
you want to cancel and then click the Cancel button , or right-click
and select Cancel.
• To remove all matches displayed on the grid, click the Select All button
and click the Cancel button , or right-click and select Cancel.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected match is cancelled.
Each item can only be part of one pending match at any one time.
66 Performing Manual Matching
When cancelling a pending match, you need only to search for and select one
item from the pending match. By cancelling one item, all the items in the
pending match are cancelled. However, you need to refresh the grid to see the
status change.
Recalling items
You use the Recall tool to recall items in a perfect match from History.
In the case of cash or securities items, this involves reversing the process of
reconciliation and returning groups of items from the status of History to
Outstanding. This might be due to matching the items in error, or because
another item arrived afterwards that needs to be included in the match.
When recalling items, you need only to search for and select one item from a
match. By recalling one item, all items in the match are recalled. However, you
need to refresh the grid to see the status change.
Contra write-offs are generated with a status of Outstanding so that they can be
matched with other items, enabling the set to balance.
You cannot recall an item if:
• Its reconciliation status is Outstanding (and it is not a Netting item).
• Its reconciliation status is Deleted.
• It is part of more than one historic match.
• It is a netting item on an active case.
To recall a match
1. Perform a search that returns the matched items that you want to recall.
2. Select an item in the match group that you want to recall.
3. Do one of the following:
• To recall a single match, click the row selector to select one of the
items in the match and then click the Recall button , or right-click
and select Recall.
• To recall multiple matches, click the row selector for an item from
each match that you want to recall and then click the Recall button ,
or right-click and select Recall.
• If the grid displays only the items for a single match you can recall all
items on the grid. Click the Select All button , and then click the
Recall button , or right-click and select Recall.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
4. Click [OK] to continue.
All items in the group containing the selected item are recalled.
Managing Reconciliations 69
Splitting items
Splitting an item into smaller component items often helps the match rate, as
large value items might not match because of a tolerance limit, whereas lower
value items might fall within those limits.
In order to split an Outstanding item, Advisory items must be manually or
automatically loaded into the system, or you can create advisory items to be used
for split processing using the Item Create Split function.
7. When you have created all of the required Advisory items, and the
difference is 0, click [Save].
The Advisory items are created and are available for split processing.
70 Performing Manual Matching
7. When you have created all of the required Advisory items, and the
difference is 0, click [Save].
The Advisory items are created and are available for split processing.
Managing Reconciliations 71
To split items
1. Perform a search that returns the outstanding and advisory items that you
want to split.
If the items are already displayed but on two different dashboards, you can
use the fast-cut function to put them together on a dashboard. For details on
Putting together items from different dashboards, see page 84.
2. Select the Outstanding item and any number of Advisory items that total the
same amount.
3. Click the Split button or right-click and select Split.
4. Click [OK] to continue.
The original Outstanding item is marked as deleted and the Advisory items
become Outstanding. They are then available for matching.
Deleting an item
You can use the Delete tool to delete an item. This marks the item as deleted,
and is typically during testing of the system. However, this process does not
physically delete the items, so you can restore an item deleted in error, and mark
it as outstanding.
You cannot delete net items, items flagged with a status of history, or items with
outstanding cases.
You can delete items with status not reconciled or pending reconciliation and
match status suggested or recalled.
To delete an item
1. Select the item that you want to delete.
2. Do one of the following:
• To delete a single item, click the row selector to select the required
item and click the Delete button , or right-click and select Delete.
• To delete multiple items, click the row selector to select the required
items and click the Delete button , or right-click and select Delete.
• To delete all items displayed on the grid, click the Select All button
and click the Delete button , or right-click and select Delete.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected items are flagged as Deleted.
72 Performing Manual Matching
Undeleting an item
If you delete an item in error, you can restore it using the Undelete tool.
You can undelete only items that were manually deleted; items that are deleted
as part of the Pending processing cannot be undeleted.
To undelete an item
1. Right-click on a node in the Lifecycles Summary, and select Ad Hoc Items
search.
2. Click the [Clear] button to remove any existing values in the search fields,
and then select Item Status: Deleted.
3. Add any additional search criteria to help you find the item.
4. Click [Search].
A list of the deleted items is displayed.
5. Select the item that you deleted in error.
• Match Details – displays information about the match including the match
type, priority and authorization status.
• Currency Interest Claims – displays the opportunity cost and value date for
cash and currency matches.
• Match Audit – displays all the operations performed on the match, when
they were performed, and the users responsible.
• Item Match Details – displays details of the items in the match.
Match details
This dashboard displays the following match details:
Field Description
Account The identifier to which the item belongs. For example, a
General Ledger account or a Securities Portfolio ID. It is
the local set number recognised by the reconciliations
department.
Category The name of the Relationship Category.
Relationship Type The name for the type of Relationship between the match.
Overall Status The overall status of the match, which can be any of the
following:
• Cancelled - The match has been cancelled.
• Pending - Matching has been initiated but not
complete.
• Suggested - The match has been suggested by the
system.
• Matched - The match is complete.
• Recalled - The match has been recalled.
Creation Type The match creation type.
Authorisation Status Whether the match requires authorization.
Priority The priority of the match, which can be 0, 1 or 2.
The lower the number, the higher is the priority.
Principal Amount The amount of the item.
Principal Date The date on which the entry was made or trade occurred.
Relationship Category The name of the Relationship Category.
Last Action The last action performed on the match.
Last Action Date The date and time when the last action was performed on
the item.
Last Action User The user who performed the last action.
Relationship ID The Relationship ID.
Item Link Count The count of the item link.
Managing Reconciliations 75
5. To authorise a match, select the applicable match items, then right-click and
select Match.
Any pending net items associated with the match are deleted, and, where
required, a write-off item is created to balance the set.
6. To reject a match, select the applicable match items, then right-click and
select Reject.
Managing Reconciliations 77
4. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank, for example, to view
matches with all the lifecycle statuses, do not select any checkbox in the
Lifecycle Status field.
If you want to view all records, do not specify any search parameters.
5. Click [Search].
Searching for all records without specifying any criteria might take a longer
time to return the records, if there are many item rows.
If the search is successful, the resulting matches are displayed in the Ad-Hoc
Matches Search grid.
6. Use the dashboard’s tools to perform the required functions. For details
see page 45.
80 Searching for items and matches
4. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank, for example, to view
items with all the lifecycle statuses, do not select any checkbox in the
Lifecycle Status field.
If you want to view all records, do not specify any search parameters.
5. Click [Search].
Searching for all records without specifying any criteria might take a longer
time to return the records, if there are many item rows.
If the search is successful, the resulting items are displayed in the Ad-Hoc
Items Search grid.
6. Use the dashboard’s tools to perform the required functions. For details
see page 45.
82 Other matching tasks
Viewing Exceptions
You can view the exceptions associated with selected items using the Exceptions
dashboard. The dashboard is available from context menus in various
dashboards, for example, Item Exceptions by Inbox and Items by Status.
See Viewing and editing exception details for information on what actions you
can perform on exceptions, page 130.
Creating exceptions
Exceptions can be raised, for example, if essential information is missing or if a
matched group is outside of the allowed match tolerance, and are usually raised
during manual matching. Exceptions are placed in Inboxes to ensure that the
correct user or team works on them.
Exceptions are created using the Exception Creation dashboard. The dashboard
is available from context menus in various dashboards in TLM Reconciliations-
Premium, for example, Item by Status, Item Matches and Items Ageing by
Current Priority.
To create an exception
1. Select the required item or group of items.
2. Right-click and select Exception Creation.
The Exception Creation dashboard is displayed.
86 Other matching tasks
4. Click [Create].
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
5. Click [OK] to continue.
The exception is created and is ready to be dealt with by an Investigator.
Managing Reconciliations 87
Viewing notes
You can view any existing notes added to an item using the Item Notes
dashboard. The dashboard is available from context menus in various
dashboards, for example, Item by Status and Items Ageing by Current Priority.
Each note that has been added to the item is displayed on a separate page which
you can switch to using the record browser. For example:
Linking items
Linked items are related securities. An asset register has an internal security
identifier for a security known as the internal asset identifier.
Every message has a security identifier attached to it. There are different security
coding conventions such as ISIN, CUSIP, and SEDOL. The security identifiers
are under these coding conventions. Apart from these, there are other codes
named as security aliases, which relate to the same physical security.
A security with one internal asset identifier can have other ISIN, SEDOL,
CUSIP and other identifiers. This list is stored in the asset register.
On receiving a message, GEMS converts the security identifier on the message
to the internal asset identifier using the conversion data in the asset register. This
means that the user sees the same security identifier on all items related to that
security.
A message might be loaded with a security identifier for the same security that is
not included in the asset register. You can add that identifier to the Asset
Register using the Item Link option. This option enables you to bring together
items that have different security identifiers. The unknown security identifier is
added into the asset register against the known security. Then on message input,
this newly identified security identifier is correctly translated by GEMS.
The dashboard is available from context menus in various dashboards, for
example, Item by Status and Items Ageing by Current Priority.
Managing Reconciliations 89
To link an item
1. Select the required item.
2. Right-click and select Item Link.
The Item Link dashboard is displayed.
3. Click the more […] button to select the asset code to which the item is to be
linked.
4. Select the linking scope from the drop-down list.
5. Click [OK].
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
6. Click [OK] to continue.
The selected item is linked.
Unlinking items
Linked items can be unlinked using the Item Unlink function. The dashboard is
available from context menus in various dashboards, for example, Item by Status
and Items Ageing by Current Priority. For details on Linking items, see page 88.
To unlink an item
1. Select the required item.
2. Right-click and select Item Unlink.
The Item Unlink dashboard is displayed.
Editing items
This section deals with:
• Editing rows, see below
• Editing multiple items, page 92
Editing rows
For Sets and Items, you can edit the values in a selected row, or multiple rows on
a grid. While performing in-grid edits, the grid’s tools are not available for use
and are replaced with a Save tool and a Cancel tool. When you have saved (or
cancelled) your changes, the tools are displayed and available for use again.
The data that you can edit is governed by:
• the columns that are displayed in the current view.
• your user Attribute Maintenance settings
• the attributes that are defined as editable for your user role.
If any data has not yet been saved, the row is highlighted with a black line to
denote this. For example:
When a value in a cell is entered or changed, all values within that row are
validated. If any values within the row are of the wrong datatype, or if a
mandatory field is empty, the cell with the error is highlighted with a red
dotted line and the row is highlighted with a red zigzagged line. For
example:
You must correct the data before you can save any of your changes.
4. If required, repeat step 3 for any additional cells and rows that you want to
edit.
5. When you have finished making your changes, select Save from the
grid’s toolbar.
The changes are saved to the database and recorded on the audit trail.
92 Other matching tasks
4. Click [Save].
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
5. Click [OK] to continue.
The changed items are updated with a status of Pending Authorisation, and
must be authorised by a second user.
Managing Reconciliations 93
• To own all of the items displayed in the grid, click and click the
Take Ownership button , or right-click and select Take Ownership.
3. Click [OK] to continue.
The ownership changes to your name.
• To unassign all of the items displayed on a grid, click and click the
Unassign Owner button , or right-click and select Unassign Owner.
3. Click [OK] to continue.
The owner is removed from the item.
94 Working with Proofs
Realtime Proofs
If you request a realtime proof, the system calculates the balances and displays
the ‘live’ details, that is, the situation as of right now. Realtime proofs are not
saved.
Viewing proofs
You can view Realtime and Point in Time proofs on any set.
To view Proofs
1. Do one of the following:
• Launch the REC Lifecycles Summary treeview, right-click a set and
select the proof that you want to view.
• Launch the Set Lifecycles dashboard, right-click a set and select the
proof that you want to view.
A search window is displayed.
2. Enter details in the various fields. If you want to view data for all the
options of a particular field, keep that field blank, for example, to view
records with all the lifecycle statuses, do not select any checkbox in the
Lifecycle Status field.
3. Do one of the following:
• After you have specified the parameters, click [Search].
• If you want to view all the data, then click [Search] without specifying
any search parameters.
Searching for all records without specifying any criteria might take a
longer time to return the records, if there are many sets.
96 Working with Proofs
Securities Proofs:
Column Description
As At The date and time when the balancing was done.
Auth Status Displays whether authorization is required.
Last User The user who last worked on the item.
Last Date The date when the last action was performed.
Last Action The last action performed on the item.
Last Note The last note added on the item.
Proof ID The unique ID generated when the Point In Time
Currency Proof was created.
Field Description
Write Offs - The total amount of credit write-offs. Outstanding credit numbers are
CR displayed in the adjacent field.
Write Offs - The total amount of debit write-offs. Outstanding debit numbers are
DR displayed in the adjacent field.
Net Total The net total of the credit and debit transactions.
Total number of outstanding transactions is displayed in the adjacent
field.
Proof The summary of the set balance.
Missing The difference of balance, between the statement from the closing
Balance balance of the previous day and the opening balance on the next day.
PROOF
Balance Net The sum of the closing statement balance of Ledger and Statement.
Transaction The sum of the loaded securities transactions.
Net
Difference The sum of balance net and transaction net amount.
Missing Bal The sum of the missing balance of Ledger and Statement.
Net
Column Description
Diff to Clos Stmt Absolute difference between Our and Their Latest Closing
Statement Balances.
Diff to Run Tran Absolute difference between Our and Their Latest Running
Transaction Balances.
Diff to Position Absolute difference between Our and Their Latest Positions.
Searching for all records without specifying any criteria might take a
longer time to return the records, if there are many item rows.
If the search is successful, the resulting matches are displayed in the Proof
Items grid. For example:
102 Working with Proofs
2. Select or enter any relevant values to help narrow down the search.
3. Click [Search].
The REC PIT Proof Ad Hoc dashboard is displayed, showing the results of
your search.
Managing Reconciliations 103
To approve a proof
1. Launch one of the Point In Time Proofs dashboards.
2. Select the proofs that you want to approve.
3. Do one of the following:
• To approve a single proof, click to select the required proof and click
the Approve Proof button , or right-click and select Approve Proof.
• To approve multiple proofs, click to select the required proofs and
click the Approve Proof button , or right-click and select Approve
Proof.
• To approve all proofs displayed on the grid, click and click the
Approve Proof button , or right-click and select Approve Proof.
4. Click [OK] to continue.
3. Click [Search].
The REC Lifecycles Summary dashboard is launched, and displays sets for
which authorization has been requested, within an Authorisation
Requested folder.
4. Right-click on the Authorisation Requested folder for the required set, and
select Sets Lifecycles.
The Sets Lifecycles dashboard is launched and displays details of the
reconciliation for which authorization was requested.
5. Select the rejected request that you want to re-submit for authorization, and
click the Reconcile tool on the toolbar, or right-click and select
Reconcile.
6. If prompted to do so, enter a note to explain why you are re-submitting the
request, then click [OK].
The reconciliation request is moved to the Authorisation Requested folder in
the Set Status tree, from which it can be authorised or rejected by an
authorising user. For details on Authorising and Rejecting Reconciliations,
see page 106.
110 Generating Reports
Generating Reports
A number of daily and monthly reports are available to enable you to monitor all
aspects of the system, including the status of matches and exceptions, as well as
daily file processing and billing.
The reports available depend on the role configured for your user, as described
in the following table:
Report Role
Report Role
For further information on the roles referenced in the above table, refer to the
TLM Reconciliations-Premium User Administration Guide.
Reports are generated as PDF files that you can download and save to your
machine. For example:
112 Generating Reports
The reports that you can generate are listed under the Reports heading on the
menu bar. For example:
Managing Reconciliations 113
To generate a report
1. From the main menu, select Reports and then select the name of the report
that you want to generate.
The selected report dashboard is launched.
2. Click the arrow button
If there are any parameters required to generate the report, they are
displayed underneath the report and you must enter them and click the arrow
button to proceed. For example:
When the report has generated, a link is displayed, from which the report
can be downloaded. For example:
Exception lifecycle
Exceptions are raised either automatically as a result of a match process or
manually by a user through the user interface. An exception undergoes the
following state changes:
Exceptions can also be cancelled, if raised in error, and are automatically closed
for certain exception types. For example, Position Break exceptions are
automatically closed when the items are matched and the status is changed to
History.
Managing Exceptions and Alerts 117
When an exception is created, the exception status is set to New. A user picks up
an exception and investigates it. At that time the exception status changes to
Active. After the exception is resolved, the status changes to Resolved. The
system waits for a confirmation for closure. The exception management process
is complete after the confirmation is received. The exception is then closed and
its status changes to Closed. An exception can be reopened after it is closed.
If required, you can generate an alert. This alert can be dismissed.
If the exception was raised in error, you can cancel it. Its status changes from
Active to Cancelled.
Allocation to an Inbox
Inboxes are used to allocate and sub-divide work. At creation time, an exception
is allocated to an Inbox. Inboxes are like workfolders where an exception type is
associated with an Inbox. Users navigate to exceptions through these Inboxes.
Inboxes display the correct set of exceptions assigned to users. This allows a
group to identify who is working on which exception. Users can take ownership
of an exception or they can be assigned to it. The access rights to Inboxes are
determined by the user roles.
Using Inboxes, users can manage exception workloads efficiently and ensure the
correct user or team works on them. An Inbox can contain any number of
exceptions or alerts.
You can move the Inbox contents from one Inbox to another. You can configure
the system to allow users to return exceptions to a default administrator inbox.
To use this function you must create an administrator inbox and specify its name
in the SYST setting ADMIN_INBOX. This displays a button on the Exception
details dashboard, which when clicked returns the exception to the default
administrator’s inbox, from where the Exceptions Administrator can reallocate it
as appropriate. If you want to constrain users to send exceptions only to the
administration inbox, and not to another named inbox, you must remove the
EXR WC Excptn CInbox tool in the REC Exception universe from the user’s
role.
118 Exception Management concepts
Alerts
Alerts are used for notifying users about potential error conditions that have not
yet occurred, but can occur in the future. Alerts are also raised when non-critical
errors occur. Escalations can be raised when required conditions are not met
within the defined time duration, for example, an escalation might be required if
the same exception is raised several times or the time duration for which an
exception has been in a given state.
Alerts are used to notify and escalate exceptions, for example, if an exception is
raised but is not resolved within a preconfigured time, an alert is raised. Each
alert is allocated an alert type and a severity. The severity types are explained
below:
Alert Severity Description
Info Gives a notification.
Regular Indicates that a non-critical error has occurred.
Critical Indicates that potential errors have occurred, which must be
resolved immediately.
Each alert is placed in the relevant inbox, and triggers an e-mail notification to
the user.
Exception types
Exception Type Exception Identification Exception
Resolution
Amount/Quantity This exception should be used to track This exception
Break cash amount or security quantity/value automatically
breaks. They are identified and closes when all
created by auto match rules or by the linked transactions
user. are matched and
status changed to
History.
Amount/Value This exception is created to track The exception is
Date Break potential cash claims or value to be resolved by the
used to track exceptions relating to user, or
value date differences. They are automatically
created automatically when perfectly cancelled if the
matching a group with a value match that created
date/amount discrepancy. The set the exception is
must also have the ‘Auto Value Diff recalled.
Breaks’ parameter enabled
Value Date This exception occurs if there are The exception is
value date differences. resolved by the
user.
Position Exceptions
Overview
TLM Reconciliation Premium now provides the ability to configure multiple
position break exception types.
Prior versions of TLM Reconciliation Premium only catered for a single position
break exception type (‘Position Break’) which clients found too restrictive
because it did not allow any form of break classification.
Functional Overview
The section below provides a brief overview of the new position exception
functionality:
• A new exception category called ‘Position Breaks’ has been introduced.
• All exception types which are defined under the ‘Position Breaks’ category
will fire the same position related logic (exception storming on asset id).
• The standard Reconciliation Premium exception categories are now Cash,
Securities and Position Breaks.
• The default exception type ‘Position Break’ has been moved from the
Securities exception category to the ‘Position Breaks’ category.
• A new relationship category called ‘Position Breaks’ has been introduced.
• Matching Services has been enhanced to generate position breaks when a
perfect match is created against any relationship type under the position
breaks category.
• The position break logic has been modified to automatically create a
position break exception using the same exception type as the relationship
type which is being used to send the position items to history.
By default the relationship type lookup value and the exception type lookup
value must be identical; this is the standard way the system knows which
position break type to create.
• The default relationship type ‘Position Break’ has been moved to the new
‘Position Breaks’ category.
• A new relationship category called ‘Perfect Position’ has been introduced.
• Matching Services has been enhanced to automatically close any open
position exceptions on the same storm key (asset id) when a perfect match is
created against any relationship type under the perfect position category.
• The default relationship type ‘Perfect Position’ has been moved to the new
‘Perfect Position’ category.
• The position processing logic has been enhanced to modify the open
position exception type to reflect the latest classification. For example, if
yesterday a ‘Position Quantity Break’ was opened against the asset but when
todays data is received and processed the matching rules determine that a
Position Market Value break should be created against the asset, the items
will be stormed onto the existing open exception and the exception type will
be changed from ‘Position Quantity Break’ to ‘Position Market Value
Break’ to reflect the latest classification.
• The unknown exception type continues to operate as before.
122 Exception Management concepts
Event List
Create a new event list at the REC Items level.
Workflow Tool
Create a new workflow tool:
Add the event list created above and select Commit Workflow as the next step:
128 Exception Management concepts
Solution Properties
The following solution properties have been added:
Property Name Default Value Note
RECS_POSBREAK_REL_CAT_OPEN 200000001 Relationship category id
which will auto-open
position break exceptions
RECS_POSBREAK_REL_CAT_CLOSE 200000000 Relationship category id
which will auto-close
position break exceptions
RECS_POSBREAK_EXP_CAT_ID 200000001 Exception category id for
position exception types
Managing Exceptions and Alerts 129
These dashboards contain the following controls, from which you can drill down
to view the exception, alert and message details in a grid dashboard:
• Rec Exceptions Inbox Summary – a hierarchical treeview representation of
active exceptions. By default, the treeview is categorised by Inbox,
exception owner, exception status and the total number of exceptions in
each exception type.
• Exceptions by Priority – a bar chart summarising the exceptions in each
exception priority. The number of exceptions is displayed next to the
exception priority name. The exception priorities are Normal, Overdue and
Critical.
• Alerts by Severity - a bar chart that provides a summary of alerts by status.
The number of alerts is displayed next to the alert status name. The alert
statuses are Info, Regular and Critical.
• Alerts by Inbox - a treeview that provides a hierarchical representation of
active alerts. By default, the treeview is categorised by Inbox and Alert
Type.
• Messages by Status – a treeview that provides a hierarchical representation
of the current exception messages in the system. By default, the nodes in the
treeview are categorised by Message Status > Inbox > Owner > Message
Name.
Exception Creation
Exceptions are usually created in the first instance by a reconciler who has
discovered a discrepancy. See Creating Exceptions for details of how this is
done, page 85.
130 Working with Exceptions
Field Description
Next Message The next type of message to be sent for this exception, where
Type applicable.
Next Message The date the next message is to be sent, where applicable.
Date
Next Review The date the next message is to appear in the exception inbox
Date for review, where applicable.
Managing Exceptions and Alerts 133
You can right-click on any message displayed on this dashboard to perform any
of the following options where available on the context menu:
• View the message details, page 135
• View the message audit, page 135
• Attach to Exception, page 143
• View the exception details, page 130
• Detach from Exception, page 139
• Mark as Read
The availability of the buttons depends on the status and type of the message.
For example, the message illustrated above has a status of rejected. As such,
only the [Edit] button is available, so that the message can be changed and
resubmitted by the user.
2. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank. For example, to view
inbound and outbound messages, do not select checkboxes in the Message
Direction field.
If you want to view all records, do not specify any search parameters.
3. Click [Search]
Any messages returned by the search are displayed in the Messages by
Status dashboard.
Managing Exceptions and Alerts 137
For message formats such as emails that are not automatically processed by the
system, you can use the Message Creation dashboard to manually attach the
message to the relevant exception.
3. Enter a subject and their reference for the message, and copy the message
details into the Message field.
4. Click [Attach].
The message is attached to the exception and the appropriate audit trail
entries are created.
138 Working with Exceptions
3. In the Exception ID field, enter the ID of the exception you want to copy the
message to.
4. If you do not want the copied message to be deleted from the current
exception, enter ‘N’ in the Delete from existing exceptions field.
5. Click [OK].
The message is copied to the selected exception.
The system currently supports the creation of MT999 and MT995 outbound
swift messages.
You can select from a variety of outbound message types, including swift and
email, and the message recipient can either be defined automatically from
‘Correspondent’, ‘Inbox’, or ‘Business Entity’, or alternatively sent to a third
party of your choice.
The type of message that you send will determine whether you can edit the
message contents, and also whether the message must be approved by another
user before being sent.
3. Select the type of message you require from the drop-down menu.
The remaining fields are populated with the data dictated by the message
type template, where appropriate.
4. Populate any remaining outbound message fields and where available,
perform any required edits to the prepopulated fields.
5. Click [Send].
If the message type requires authorization, it is displayed in the
Authorisation Requested folder in the Messages by Status tree, and will not
be sent until it has been approved by an authorising user.
Managing Exceptions and Alerts 141
You might need to configure your browser’s security settings to enable the
document attach function to work, if your organisation permits you to do so. For
details see page 24.
• To add all items displayed on the grid, click and click the Add to
Exception button , or right-click and select Add to Exception.
4. Enter the exception ID.
5. Click [OK] to continue.
The selected item is added to the exception.
Managing Exceptions and Alerts 149
Resolving an exception
You use the Resolve tool to resolve an exception. You can resolve exceptions
with New or Active exception status. When you resolve the exception its status
changes to Resolved. After an exception is resolved, the exception is
automatically closed on next data load. After the exception is closed, the status
changes to Closed.
To resolve an exception
1. Select the exception that you want to resolve.
2. Do one of the following:
• To resolve a single exception, click to select the required exception
and click the Resolve button , or right-click and select Resolve.
• To resolve multiple exceptions, click to select the required items and
click the Resolve button , or right-click and select Resolve.
• To resolve all exceptions displayed on the grid, click and click the
Resolve button , or right-click and select Resolve.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected exception is resolved.
Cancelling an exception
The Cancel tool is used to cancel exceptions raised in error. Exceptions with
status as New or Active can be cancelled. When an exception is cancelled, the
exception status changes to Cancelled.
To cancel an exception
1. Select the exception that you want to cancel.
2. Do one of the following:
• To cancel a single exception, click to select the required exception
and click the Cancel button , or right-click and select Cancel.
• To cancel multiple exceptions, click to select the required exceptions
and click the Cancel button , or right-click and select Cancel.
• To cancel all exceptions displayed on the grid, click and click the
Cancel button , or right-click and select Cancel.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected exception is cancelled.
To close an exception
1. Select the exception that you want to close.
2. Do one of the following:
• To close a single exception, click to select the required exception and
click the Close button , or right-click and select Close.
• To close multiple exceptions, click to select the required exceptions
and click the Close button , or right-click and select Close.
• To close all exceptions displayed on the grid, click and click the
Close button , or right-click and select Close.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected exception is closed.
Reopening an exception
The Reopen tool is used to reopen an exception. Only exceptions with an
exception status of Closed can be reopened. When a previously closed exception
is reopened, the exception status is set to New. Cancelled exceptions cannot be
reopened.
To reopen an exception
1. Select the exception that you want to reopen.
2. Do one of the following:
• To reopen a single exception, click to select the required exception
and click the Reopen button , or right-click and select Reopen.
• To reopen multiple exceptions, click to select the required exceptions
and click the Reopen button , or right-click and select Reopen.
• To reopen all exceptions displayed on the grid, click and click the
Reopen button , or right-click and select Reopen.
The Progress window displays the status of the action. For additional
information on the results, click [Show All Results].
3. Click [OK] to continue.
The selected exception is reopened.
• To unassign all of the items displayed on a grid, click and click the
Unassign Owner button , or right-click and select Unassign Owner.
3. Click [OK] to continue.
The owner is removed from the item.
154 Searching for Exceptions and Alerts
4. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank, for example, to view
items with all the lifecycle statuses, do not select any checkbox in the
Lifecycle Status field.
If you want to view all records, do not specify any search parameters.
5. Click [Search].
Searching for all records without specifying any criteria might take a longer
time to return the records, if there are many item rows.
If the search is successful, the resulting items are displayed in the Ad-Hoc
Item Exceptions Search grid. For example:
4. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank, for example, to view
exceptions in any inbox, clear the Inbox field.
If you want to view all records, do not specify any search parameters.
5. Click [Search]:
Searching for all records without specifying any criteria might take a longer
time to return the records, if there are many item rows.
3. Enter the required search parameters. If you want to view data for all the
options of a particular field, keep that field blank. For example, to view
alerts within the whole range of lifecycle statuses, ensure that the
checkboxes in the Lifecycle Status field are not selected.
If you want to view all records, do not specify any search parameters.
4. Click [Search].
Searching for all records without specifying any criteria might take a longer
time to return the records, if there are many item rows.
If the search is successful, the resulting alerts are displayed in the Alert Ad-
Hoc Search dashboard.
5. To view the exception details for an alert from the Alert Ad-Hoc Search
dashboard, select an alert, right-click and select Exception Detail or double-
click an alert.
6. If you want to dismiss an alert, to show that you have acknowledged the
exception, select the alert and do one of the following
• Click the Dismiss button.
• Right-click and select Dismiss.
Working with Exchange Traded
Derivatives
Cash Transactions, Asset Positions and Asset Transactions are all reconciled in
the regular way, that is, internal items are matched against the items from your
clearing institutions. You can view these matches on the standard matching
dashboards. For example:
If you identify any potential issues and breaks, you can use the standard TLM
Reconciliations-Premium dashboards and tools to view, investigate and reconcile
the cash transactions, asset positions and asset transactions associated with
problematic accounts.
Cash Balances are not reconciled. For these items, you can drill down to the
Total Equity proofs dashboards to view a summary of the Total equity value of
each account. This is generated from the cash balances that are loaded into the
system, which are assigned a status of Advisory and used for the purpose of
creating Total Equity proofs.
Working with Exchange Traded Derivatives 163
ETD Proofs
The following sections describe the proofing dashboards that are specific to ETD
balances.
Field Description
Proof Status The account proof status, which can be any of the
following:
- Unbalanced
- Balanced
- Balanced Approved/Unbalanced Approved
Account The Account name
Currency The Account currency, denoted by a three letter code.
Cash Net The net value of cash balances.
Option The net value of the statement and ledger unrealised
Unrealised options.
Net
Futures The net value of the statement and ledger unrealised
Unrealised futures.
Net
Other The net value of any other statement and ledger
Unrealised unrealised instruments excluding futures and options.
Net
Total Equity The net sum of the ledger cash, options unrealised and
Net other unrealised net balances, and that of the statement.
This gives an indication of the value of the account.
Outstanding The value of outstanding cash items.
Cash
Variance The total equity net minus any outstanding cash
balances
As At The date the proof was created
You can view further information on any proof displayed in this dashboard
by right-clicking on the proof and drilling down to the Proof Detail
dashboard. You can also drill down to the Proof Items dashboard to view the
balances captured at the time the proof was taken.
Working with Exchange Traded Derivatives 165
If the Net Asset Value Reconciliations (NAV Recs) module is part of your TLM
Reconciliations-Premium configuration, you will have access to additional
functionality that enables you to reconcile NAV Recs.
The NAV transactions are processed by TLM Reconciliations-Premium in the
same was as standard cash and asset transactions; the main difference is in the
proofing dashboards for NAV balances.
The purpose of the Net Asset Valuation Reconciliation is to validate that the
customer's gross position held with their counterparties accurately reflects the
true gross position held in their books and records.
The following diagram gives a basic overview of the reconciliation process for
NAV Recs:
Internal: External:
High Level Reconciliation
Balance Sheet Trial Balance
Reconciliation Reconciliation
to ensure to ensure
integrity integrity
Detailed Reconciliation
All received Positions, Cash components, and open or unsettled trades are
reconciled to look for discrepancies between them. Any breaks in these elements
are flagged up as exceptions that require some investigation.
The proofs for NAV Recs display a single Proof Status that indicates whether
there is a problem at either the Balance Sheet or Detail level.
You view NAV Rec items on the REC Lifecycles Summary tree. The tree
displays the reconciliation status of NAV items under a ‘NAV’ folder. For
example:
Cash Transactions, Asset Positions and Asset Transactions are all reconciled in
the regular way, that is, internal items are matched against the items from your
clearing institutions. You can view these matches on the standard matching
dashboards. For example:
If you identify any potential issues and breaks, you can use the standard TLM
Reconciliations-Premium dashboards and tools to view, investigate and reconcile
the transactions associated with problematic accounts.
Working with Net Asset Value Reconciliations 169
Field Description
Proof The account proof status, which can be any of the
Status following:
- Unbalanced
- Balanced
- Balanced Approved/Unbalanced Approved
Category The category of the account.
Account The Account name
Currency The Account currency, denoted by a three letter code.
Ledger The Net Asset Value of the internal balance sheet.
NAV
Statement The Net Asset Value of the statements.
NAV
NAV The variance between the Ledger balance and the
Variance Statement balance.
NAV The difference expressed as a percentage of the Net Asset
Basis Value on the Statement side, multiplied by 100. 100 basis
Point points is 1%.
Variance
As At The date the proof was created
You can view further information on any proof displayed in this dashboard
by right-clicking on the proof and drilling down to the Proof Detail
dashboard. You can also drill down to the Proof Items dashboard to view the
balances captured at the time the proof was taken.
Ageing Items
During the load of items relating to the GL reconciliation process, an ageing
lookup is performed against the fiscal calendar to determine to the age date for
an item. This process is performed in addition to the standard ageing that is
already available, and is invoked using the custom POSTLOAD_PROCESS
processing hook during loading.
174 Working with General Ledger proofs
Scorecards
A scorecard is used as a measure of risk against a Proof Header. One scorecard
is created per unique ‘Opportunity’ across Message Feeds belonging to a
particular GL account. They track a number of rated objectives/criteria that are
either met, not met, or have not yet been evaluated. Scorecards are displayed as
part of the proof details, and are often used by approvers when determining
whether the proof is ready to be signed off.
A range of ‘Custom Criteria’ attributes are available for customising the
attributes that should be evaluated and displayed in the Scorecard tab as part of
the GL proof data. These criteria can have automated processes behind them that
test whether a particular test passes, or they can be for manual steps and used as
a checklist item that the user updates to Yes on completion.
When scorecard is first created, all values are initially set to Untested. When a
Refresh is subsequently performed, either manually or as a result of any of the
following operations:
• adding a note to a proof
• adding an attachment to a proof
• inserting a GL item
the criteria with automated processing behind them are tested, and the values are
updated to Yes or No accordingly. Manual criteria are not affected by the refresh,
that is, the status remains as Untested unless manually changed.
When the proof is approved, if all values are Yes or Untested, the status will be
set to Approved - Reconciled. If there are any No values among the criteria, the
status is set to Approved - Unreconciled.
Working with General Ledger (GL) Reconciliations 175
Before the final approval of the scorecard is processed, users should refresh the
scorecard so that the values of any automatic criteria are populated with the
latest values, and the approval status can be accurately determined.
Proof Audit
The following operations that are performed on proofs are audited:
• Balanced Approved
• Unbalanced Approved
• Reset On Loading
• Reset On Auto Assignment
• Reset On Manual Item Insert
• Submitted For Review
• Approved
• Force Approved
• GL Item Inserted
• Inactive
• Rejected
• Cancelled
• Reset On Regrouping
• Unfreezed
• Created
• Scorecard Updated
• Added Note
The audit details are displayed on the Audit dashboard, which is launched when
the Proof Details dashboard is selected.
176 Viewing GL Proofs
Viewing GL Proofs
There will typically be only one active General Ledger proof at any one time,
which is the proof for the fiscal period that is currently being reconciled. You
can also view inactive (old) GL Proofs.
Proofs become Inactive when the Overall Status is Frozen, the Approval Status
is Approved, and the Recs End Date for the Period is today.
To view GL proofs
1. From the Menu, select GL Reconciliations.
A search prompt is displayed.
2. Enter or select any values to help narrow down the search, or leave all the
fields blank to return all proofs, and click [Search].
The REC PIT Proof Summary Tree is displayed. For example:
3. Double-click the set or level in the tree for the proofs that you want to work
with.
A number of chart summaries are displayed. For example:
• If you want to view the Proofs By Status graph, click the Proofs by
Status tab.
• If you want to view the Proofs Balance Summary, click the Proofs
Balance Summary tab.
Working with General Ledger (GL) Reconciliations 177
4. Double-click on the relevant bar in one of the graphs to display the details of
the associated proofs. For example:
Column Description
Category The category to which the proof belongs.
Period The name of the fiscal period for the proof.
Set The set to which the proof belongs.
Doc Displays a paperclip icon if a document is attached to the
item.
Var Displays a green circle if the proof is within the specified
variance; displays a red circle if the variance is greater than
that specified.
Status The status of the proof. Can be one of the following:
• New
• In Progress
• Frozen
• Inactive
Auth The authorization status of the proof.
Reconciler The nominated reconciler for the proof.
st
1 Reviewer The nominated 1st reviewer for the proof.
2nd Reviewer The nominated 2nd reviewer for the proof.
Period Start The start date of the fiscal period.
Period End The end date of the fiscal period.
Proof Start The start date of the proof reconciliation period.
Proof End The end date of the proof reconciliation period.
Last User The user ID of the last user to have acted on the proof.
Last Date The date of the last action on the proof.
Last Action The last action on the proof.
Last Note The last note added to the proof.
Proof ID The unique ID of the proof.
178 Viewing GL Proofs
5. Double-click the row for the proof that you want to view the details for.
The Proof Detail dashboard is displayed. For example:
If there is an item listed that should not be included in the proof calculation, it
can be Cleared. The cleared item then has no effect on the proof calculation.
If an item is cleared by mistake, it can be uncleared.
Viewing Scorecards
One scorecard is created per unique ‘Opportunity’ across Message Feeds
belonging to a particular GL account. They track a number of rated
objectives/criteria that are either met, not met, or have not yet been evaluated.
The status of each of the criteria is displayed on the Scorecard tab. For example:
- criteria failed
- criteria passed
- criteria untested
Some criteria might be for manual tasks, and therefore not updated automatically
by the system. These criteria can be updated manually.
3. Use the dropdown list for the relevant criteria to change the status.
4. Click [OK].
5. The criteria are updated accordingly.
180 Searching for a GL Proof
2. Select the Reconciliation type of GL Recs, and enter any other values to
help narrow down the search.
3. Click [Search].
The REC PIT Proof Ad Hoc dashboard is displayed, showing the results of
your search.
Working with General Ledger (GL) Reconciliations 181
2. Enter the required data in the fields, as described in the following table:
Field Description
Classification Configurable Classification. Can be one of:
• Open
• Recorded
• Unreconciled
Feed ID Select the Message Feed from the list, from where the
Currencies will be taken, if automatic amounts are
selected.
Code The Message Feed short code, automatically
populated when the Feed ID is selected.
182 Manually adding GL items
Field Description
Item Type Type of item. Can be one of:
• GL Credit
• GL Debit
• SL Balance
• SL Credit
• SL Debit
Reason The reason that the manual item is required,
automatically populated when the Reason ID is
selected.
Reason ID Select the reason that the manual item is required.
Transaction Date Select the date of the transaction.
Entered Currency Select the applicable currency from the list.
Entered Amount Enter the relevant amount for the item.
Description Enter a description of the item
Functional Currency Select the applicable function currency from the list.
Note that this currency will be taken from the message
feed for revaluation.
Local Reporting Ccy Select the applicable reporting currency from the list.
Note that this currency will be taken from the message
feed for revaluation.
Automatic Amounts If yes, the currencies will be taken from the message
feeds and the amounts automatically evaluated.
If no, currencies and values must be entered manually.
Functional Amount Functional value. Affected by Automatic Amounts
Local Reporting Local Reporting value. Affected by Automatic
Amount Amounts
Corp Reporting Corporate Value. Affected by Automatic Amounts
Amount
Transaction Reference for the transaction.
Reference
Owner Select the user ID of the owner
Estimated clearing Date for estimated clearing. Will be after the start of
date the reconciliations period.
Item Actual Clearing Date for actual clearing. Will be after the start of the
Date reconciliations period.
PL Impact Profit/Loss Impact
PL Impact Flag Flag Profit/Loss Impact – yes or no.
3. Click [Save]
The item is created on the relevant account.
Working with General Ledger (GL) Reconciliations 183
To attach a document
1. Right-click on the item that you have just created and select Add
Attachments.
The Add Attachment window is displayed. For example:
Editing GL Items
You can edit GL items directly in an item details grid, or you can edit them using
a form. For details see chapter Managing Reconciliations > Other matching
tasks > Editing items > Editing rows.
All of the fields can be edited, except for the following:
• Item Type
• Amount
• Functional and reporting currencies
• Item owner
• Age
• Item resolution
• Audit fields
Using the form you can also add additional data to the item, such as additional
references and clearing dates.
184 Manually adding GL items
Copying items
For statutory reconciliation, it is sometimes useful to manually copy a record
from a non-statutory account to a statutory account and vice-versa where
necessary.
The copy function is only available for sets of reconciliation type General
Ledger. You can only copy items of this reconciliation type to a message feed
belonging to a General Ledger set, provided it is not in an exception.
The copied item is a wholly new version with the same data attributes and has a
link to the original item.
It is possible to specify a target set/message feed for copy at both the set and the
message feed level. Auto Assignment functionality is extended to have the
ability to assign the target set/message feed using custom implementations.
Additionally, the standard administration functions allow you to edit the target
set/message feed. This helps to potentially avoid the need to select a target
set/message feed manually, although it ispossible to override the default values if
necessary.
Furthermore, additional validations are in place if to validate the selection just in
case the overridden selection is invalid for the source set/message feed.
When items are selected for copying and the dashboard is launched for selection
of target set/message feed (see screenshot above), the target set/message feed is
auto populated depending on the selection of the source data, i.e. if the source
set/message feed already has a direct link to the target set/message feed (setup as
part of the AA process), then the target details will be auto populated. If none of
the links are setup, then the approach for selection is to set first followed by
message feed, i.e. user can first select the set using the chooser which displays
all the sets in the system and then select the message feed using the chooser
which displays a list of message feeds that belong to the set selected earlier.
188 Copying items
Item Audit
In the Item Audit window it is indicated that the item has been used for copying
or it is a copy of another item.
Active proofs
The creation of the new item resets any active proof of the target account.
To copy items
1. Select Menu > Ad-Hoc Searches > Items Ad-Hoc.
The Search Prompt - REC Items Ad-Hoc window is displayed.
2. Enter your search criteria and click [Search].
The REC Items Ad-Hoc dashboard is displayed.
3. Select the items you want to copy.
4. Right-click to select Item Bulk Copy.
The Item Bulk Copy window is displayed.
5. Select the Target Set.
6. Select the Target Message Feed.
7. Click [Copy].
Working with General Ledger (GL) Reconciliations 189
Re-measurement Processing
If a set is defined that it requires the re-measurement processing, it derives a rate
that is used on all substantiating items entered for that period or reconciliation
process.
The re-calculation is based on the current General Ledger balance in the original
currency, the current MOR (i.e. the known operating rate) and data from the
previous period (the original and reporting currency balances).
The following diagram illustrates the flow of processing done to calculate the
rate to be used for substantiating items.
Process trigger
When General Ledger balances of the current period are loaded automatically
into the system, the re-measurement process is executed.
A flag at the set level indicates whether it is to be done or not.
Approving a proof
The designated reviewers, at both the first review and final review stage, have
the option to approve the proof.
To approve a proof
1. From the Proofs By Approval dashboard, select the proof that you want to
approve using the selectors.
2. Before the final approval of the scorecard is processed, refresh the scorecard
so that the values of any automatic criteria are populated with the latest
values, and the approval status can be accurately determined. Do one of the
following:
• Click the Refresh Scorecard tool on the toolbar.
• Right-click and select Refresh Scorecard.
3. To approve the proof, do one of the following:
Rejecting a proof
The designated reviewers, at both the first review and final review stage, have
the option to reject the proof.
To approve a proof
1. From the Proofs By Approval dashboard, select the proof that you want to
reject using the selectors.
2. Do one of the following:
Unfreezing a proof
Proofs with an Approval Status of Approved can be ‘unfrozen’ if, for example,
new data has been identified that needs to be added. Proofs can be unfrozen only
up until the Reconciliation End date, as defined by the Fiscal Calendar for the
Header. When unfreezing a proof, all frozen data in ITEM, MESSAGE_FEED
and BANK for that proof will be deleted.
To unfreeze a proof
1. From the Proofs By Approval dashboard, select the proof that you want to
unfreeze using the selectors.
2. Do one of the following:
Revaluation
You would typically revalue items where the applicable currency rates have
changed since the item was loaded.
Revaluating values converts the base item amount (stored in the amount field,
with the corresponding currency in the currency field) to Local Reporting,
Corporate Reporting and Functional equivalents. The actual currencies must be
supplied in a message feed; they cannot be entered manually. If no currency is
present for the Local Reporting, Corporate Reporting or Functional currency,
that field will be empty on revaluation.
The process directly converts the amount for each of the following attributes,
into the corresponding currency:
Amount Amount field Currency field
Functional Amount amount_6 currency_6
Local Reporting amount_3 currency_3
Amount
Corp Reporting amount_2 currency_2
Amount
As part of this processing, the rates between the base currency and the
item.currency_6 for example, are identified using the rate configured in the
Currency Rates Group for the Set. If a Currency Group is not configured for the
Set, a warning is displayed stating that the currency conversion cannot complete.
These other currencies can be reviewed when you are looking for a missing
amount in a different currency to the base currency.
Alerts
Notify users about potential error conditions that have not yet occurred, but can
occur in future.
Audit Trail
A record of all the operations performed on the account.
Cash Balancing
The reconciliation of cash or currency accounts. Cash balances are calculated for
each account currency. Cash account balances are reconciled between your
General ledger balances and those of your account servicer. Moreover balances
are tested to ensure that they flow from closing to opening and then again to
closing balance positions across and within accounting days.
Contact
A user who is going to work on exceptions and reconciliations.
Contact Group
A group of specific type of contacts.
Dashboard
A window that displays a graphical view of the items in the database, in the form
of charts, grids or treeviews.
Dashboard control
The individual element of a dashboard, for example, grid, form or treeview.
Dashboards can contain several controls.
Escalation
An Escalation is raised in the form of an Alert, when the required conditions are
not met in the defined time duration.
Exception
An exception is raised when a match is outside the allowed match tolerance.
2 Glossary of Terms
GEMS server
The GEMS (Generic Messaging System) server loads incoming messages into
the database tables. The contents of these tables are then checked by GEMS to
make sure that the information is as expected and if it is, the data is flagged as
validated and can be processed further within the system.
Inbox
A workfolder used to allocate and sub-divide work.
Item
The cash or security position message once stored in the database is known as an
item.
Knowledge Base
(KB) - Used by GEMS to load files to the database. Defines how incoming data
is to be mapped to the database.
Lead Account
A Lead Account, identified by the Financial Lead Parameter on an Account, has
a configurable Write-off amount. During processing, the lead account for the
account being processed is identified, and the amount is compared to the net
total of the current group.
Lead User
A Lead User has a configurable Write-off amount. During processing, the lead
user for the current user is identified, and the amount is compared to the net total
of the current group.
Lifecycle
The set of pre-determined stages that an Item passes through during its life on
the TLM OnDemand system.
Matches
The reconciliation of items with one or more common data values. A match will
include two or more items, with at least one from your side and one from your
Custodian, counterparty or correspondent bank.
Netting item
New item created to reflect an amount difference in a match. Further items
forwarded for reconciliation can then be matched against the netting item.
Product
Data enrichment feature that allows you to relate a code on an incoming item
with something more meaningful to your organisation such as the method of
financial transaction, for example, shares, bonds or units.
Glossary of Terms 3
Quality Rules
A rule that tests items' attributes to determine how good a match they are
(quality) and therefore which Relationship Type the items are assigned to. These
rules also determine whether the items are to be automatically matched.
Reason Type
Explains the cause of an exception and can be attached to an exception.
Reconciliation
Comparing two sets of data and ensuring that they match.
Relationship Type
Used to define groups of a specific type.
Relationships
Matched items are grouped in a relationship.
Release
The reconciling of items to history. Also referred to as matching.
Resolution Type
Indicates the course of action undertaken to resolve an exception
Securities
The financial products that are traded between institutions in the form of shares,
bonds, warrants and other forms of stock, on behalf of asset managers or global
custodians.
Session
Identifies the commencement of a matching process.
Set type
Type determines whether a set is a Cash or Securities.
4 Glossary of Terms
Trial balance
Provides a '‘snapshot'’ of the balances and volumes of data. This information
should be in balance normally and the screen is generally used to identify any
currencies or assets that are out of balance and that might require corrective
action. The displayed data is for information purposes only and cannot be
amended.
Universe
A collection of attributes that relate to an entity in the TLM OnDemand system.
Examples of universes include Item, Case Summary, Message Header and
Message Type.
A match 65
Exceptions 150
General Ledger Proofs 192
Changing grid view 24
Changing password 10
Index Clearing
General Ledger items 185
Clearing proof items 178
Closing
Resolved exceptions 151
Copying
Exceptions messages 139
Creating
Exceptions messages 137
Creating exceptions 85
A Creating proofs 95
Adding
General Ledger items 181 D
Adding notes to items 87
Ad-Hoc Item Exceptions Search 155 Dashboards
Closing 19
Ad-Hoc Items Search 80 Launching 14
Ad-Hoc Matches Search 78 Overview 13
Aggregates and grids 26 Resizing 15
Alert Ad-Hoc Search 159 Setting as default 18
Alerts 115 Data
Searching for 159 Exporting 35
Approving Filtering 30
Items and matches 75 Refreshing 16
Proofs 103 Deleting
Approving General Ledger Proofs 191, 192 Items 71
Attaching documents 24, 143 Detaching
Audit of GL proofs 175 Exceptions messages 139
Audit proof details 103 Detail dashboards 56
Audit trail Document attach 24, 143
Overview 46 Viewing documents 144
Viewing 46 Downloading documents 144
Viewing items 47
Viewing notes 46
Working with items 47 E
Authorising
Exceptions messages 142 Editing
Items 75 Exception details 130
Items and matches 75 General Ledger items 183
Matches 76 Rows 90
Proofs 103 Editing multiple items 92
Authorising reconciliations 106 Error messages 48
Resubmitting request 108 Exception details 130
Exception management
Alerts 118
B Automatic management 118
Basic concepts 116
Bulk editing Bulk edit fields 147
Exception bulk edit fields 147 Cancelling an exception 150
Items 92 Closing resolved exceptions 151
Multiple exceptions 147 Exception types 119
Business Logic tools 43 Excpetions lifecycle 116
Icons 45 Inboxes 117
Progress window 44 Introduction 115
Reopening exceptions 152
Resolving 149
C Searching for ad-hoc item exceptions 155
Searching for alerts 159
Cancelling Searching for exceptions 157
2 Index
L
G
Lifecycle
General Ledger Reconciliations 50
Proofs 174 Lifecycle authorization 106
General Ledger items Linking items 88
Adding 181 Logging off 12
Clearing 185 Logging on 6
Editing 183
General Ledger Proofs
Approval 191
Approving 192
M
Audit 175 Main menu 8
Cancelling 192 Managing
Items 178 Exceptions messages 133
Rejecting 193 Match
Scorcards 179 Other tasks 82
Searching 180
Match details 74
Submitting 191
Unfreezing 193 Matching
Viewing 176 Adding items to exceptions 148
Authorising and rejecting 76
Getting Started 5
Cancelling a match 65
Graphical decodes 34 Deleting an item 71
Grid aggregate icons 26 Introduction 58
Grids Match details 74
Changing the view 24 Matching items 64
Introduction 20 Opportunity cost 61
Index 3
Pending matches 65
Recalling items 68 R
Removing items from pending matches 67
Realtime proofs
Searching for items and matches 77
Viewing 95
Splitting items 69
Viewing details 98
Undeleting an item 72
Viewing items 101
Viewing details 73
Realtine proofs
Multiple item editing 92
Overview 94
REC Lifecycles dashboards 52
N Recalling items 68
Reconciliations
Navigating the menu 9 Detail dashboards 56
Navigation grids 21 Introduction 49
Notes Main reconciliations dashboards 52
Adding to exceptions 145 Matching 58
Adding to items 87 REC Lifecycles dashboards 52
Creating proof notes 104 Summary dashboards 55
Viewing 88 Reconciliations lifecycle
Viewing audit trail notes 46 Introduction 50
Viewing exception notes 146 Records 21
Viewing proof notes 105 Searching 17
Refreshing data 16
Rejecting
O General Ledger Proofs 193
Items 75
Online Help 11 Matches 76
Opening the menu 9 Rejecting authorisations 106
Opportunity cost 61 Reopening
Other matching tasks 82 Exceptions 152
Ownership Reports
Of exeptions 152 Introduction 110
Of items 93 Resizing dashboards 15
Resolving
Exceptions 149
P Resubmitting rejected reconciliations requests 108
Pending matches 65 Revaluation 194
Point In Time proofs Rows
Editing 90
Approving 103
Audit details 103
Creating 95
Creating Notes 104 S
Overview 94
Scorecards 174, 179
Viewing 95
Viewing details 98 Searching
Viewing items 101 Exceptions messages 136
Viewing notes 105 For alerts 159
For exceptions 157
Progress window 44
For exceptions and alerts 154
Proof For items 80
Audit details 103 For items with exceptions 155
Proof details 98 For matches 78
Proof items 101 General Ledger Proofs 180
Clearing 178 Introduction 77
Proof notes 104, 105 Proofs 102
Proofs Records 17
Approving 103 Second user authorization 106
Creating 95 Selecting records 21
Creating roof notes 104 Sending
General Ledger 174 Exceptions messages 140
Searching 102 Sorting data 28
Viewing 95
Splitting an item 69
Viewing proof notes 105
Submitting General Ledger Proofs 191
Summary dashboards 55
Support 1
4 Index
T
Toolbar icons 45
Tools
Progress window 44
Types of exception 119
U
Unassigning
Owners from exceptions 153
Owners from items 93
Undeleting
Items 72
Unfreezing
General Ledger Proofs 193
Unlinking items 89
V
Viewing
Exception details 130
Exceptions message audit 135
Exceptions message details 135
Exceptions messages 134, 138
General Ledger Proofs 176
Proof items 101
Scorecards 179
Viewing documents 144
Viewing match details 73
Viewing proof details 98
Viewing proofs 95
Views 24
W
Working with Dashboards 13