FusionBanking TI Upgrade Benefits

Misys FusionBanking Trade Innovation
Upgrade Features & Benefits

Version 1.0
© Misys Limited, or a member of the Misys group of companies, 2014
All Rights Reserved. Confidential - Limited Distribution to Authorised Persons Only, Pursuant to the Terms of the
License Agreement pursuant to which you were granted a licence for this software. This software is protected as an
unpublished work and constitutes a trade secret of Misys Limited, or a member of the Misys group of companies,
Head Office: One Kingdom Street, Paddington, London W2 6BL.
More Information
Need more information? Read more about our products at http://www.misys.com/products.aspx. Or contact your local
Misys office at http://www.misys.com/contact-us.aspx.
Feedback
Do you have comments about our guides and online help? Please address any comments and questions to your local Misys
representative.
Release month and year: November 2014

Contents

Chapter 1 Enhancements at TI Plus Version 1.4 ............................................................................... 7
Overview ................................................................................................................................... 7
The New Architecture ......................................................................................................................... 7
The New User Interface ..................................................................................................................... 8
Amendment Charges .............................................................................................................. 11
Amendment Events ................................................................................................................. 11
Customer Documents ............................................................................................................. 11
Faxes ...................................................................................................................................... 11
On-line Help Text .................................................................................................................... 12
Report Handling ...................................................................................................................... 12
Russian Accounting Requirements ......................................................................................... 12
Service Level Agreements ...................................................................................................... 12
Teams and the Dashboard ............................................................................................................... 13
SWIFT ..................................................................................................................................... 14
SWIFT Message Handling ...................................................................................................... 14
Working Capital Finance ......................................................................................................... 15
Factoring .......................................................................................................................................... 15
Invoice Discounting .......................................................................................................................... 15
Sales Ledger Processing ................................................................................................................. 16
Chapter 2 TI Plus Version 2.2 ........................................................................................................... 17
The Improved Architecture ...................................................................................................... 17
System Management (Global Application) ....................................................................................... 17
Open Source Components ............................................................................................................... 17
Enhancements ........................................................................................................................ 19
Analysis ............................................................................................................................................ 19
Calendars ......................................................................................................................................... 19
Clauses ............................................................................................................................................ 19
Charges ............................................................................................................................................ 19
Currencies ........................................................................................................................................ 21
Customer and Account Retrieval Services ....................................................................................... 21
Customer Details .............................................................................................................................. 21
Customer Documents....................................................................................................................... 22
Customer Gateway........................................................................................................................... 23
Customisation................................................................................................................................... 23
Data Take On ................................................................................................................................... 23
Diary Processing .............................................................................................................................. 23
Export Credit Agency Facilities ........................................................................................................ 24
© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits iii

Financing .......................................................................................................................................... 26
FX Rates .......................................................................................................................................... 26
Imaging............................................................................................................................................. 27
Notes ................................................................................................................................................ 27
Participated Deals ............................................................................................................................ 27
Postings............................................................................................................................................ 27
Remote Printing................................................................................................................................ 28
Reports ............................................................................................................................................. 29
Responses to Enquiries from External Systems .............................................................................. 29
Settlement ........................................................................................................................................ 29
Shipping Guarantees ....................................................................................................................... 29
Silent Confirmation ........................................................................................................................... 30
SLA Processing ................................................................................................................................ 30
Standby Letters of Credit ................................................................................................................. 30
SWIFT .............................................................................................................................................. 30
Transaction Processing .................................................................................................................... 31
Translation Facilities......................................................................................................................... 31
Transfer Letters of Credit ................................................................................................................. 32
Workflow........................................................................................................................................... 32
Link Multiple Shipping Guarantees .................................................................................................. 33
Alternative Formula for Interest Rebate ........................................................................................... 34
Ability to Save a Deal as Template .................................................................................................. 34
Ability to split a commission to more than one party ........................................................................ 34
Auto refresh of Dashboard ............................................................................................................... 35
Enable output of Clearing Service Identifier on MT103 and MT202 ................................................ 35
Murabaha Import Financing ............................................................................................................. 35
Release Password SSO ................................................................................................................... 36
SWIFT Acknowledgement ................................................................................................................ 36
MT292 Creation when cancelling MT202 ......................................................................................... 37
Rate Fixing in Business Hours ......................................................................................................... 37
ECR B 95% Lodgement ................................................................................................................... 38
External DMS Interface .................................................................................................................... 38
Global Processing ............................................................................................................................ 39
Cross Zone Dashboard .................................................................................................................... 40
Workflow Auto-Allocation ................................................................................................................. 40
End of Day Enhancements .............................................................................................................. 41
Framework Deployment Enhancements .......................................................................................... 41
Enhanced Customisation Tool Set ................................................................................................... 41
Departmental Limits ......................................................................................................................... 41
Configuration Management Tool ...................................................................................................... 41
© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits iv

Workflow Orchestration .................................................................................................................... 43
Supply Chain Finance ...................................................................................................................... 43
Software Development Kit ................................................................................................................ 44
Data Extract Configuration Tool ....................................................................................................... 44
Software Development Kit ...................................................................................................... 46
Supply Chain Finance ............................................................................................................. 47
Roadmap Accelerators ........................................................................................................... 47
Sundry Other Features ........................................................................................................... 47
Chapter 6 FusionBanking Trade Innovation Version 2.6 ............................................................... 48
New Screen Look and Feel ....................................................... Error! Bookmark not defined.
Software Development Kit ........................................................ Error! Bookmark not defined.
Financial Supply Chain Management ....................................... Error! Bookmark not defined.
Roadmap Accelerators ............................................................. Error! Bookmark not defined.
Sundry Other Features ............................................................. Error! Bookmark not defined.
© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits v

Chapter 1 Enhancements at TI Plus Version 1.4
Preface
This document provides an overview of the main enhancements made to Misys Trade Innovation and
TI Plus since 4.1.9. Its purpose is to allow banks to determine the business benefits of moving from
their current version of Trade Innovation/TI Plus to the later version FusionBanking Trade Innovation.
It provides a summary of the main enhancements to the product at each release supported for
upgrade by Misys.
This document assumes that readers are familiar with functionality supported by their current release
of Trade Innovation/TI Plus. It has the following chapters:
Chapter 1 Enhancements in TI Plus version 1.4.
Chapter 6 launch of FusionBanking Trade Innovation version 2.6.
© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits vi


This chapter describes the enhancements in TI Plus version 1.4. It covers the new web-based
architecture introduced with this version of the software, and enhancements made to the
software used to handle trade finance.
Overview
TI Plus version 1.4 is the first generally available version of Trade Innovation, in which the
transaction processing modules are provided running on the web, rather than on individual
PCs. All the underlying business logic and functionality of the software remains unchanged,
meaning that the regression testing required to migrate to TI Plus is minimised.
In addition, banks upgrading to TI Plus use their existing Trade Innovation database, meaning
that there is no loss of historical data or of system tailoring parameters.
There are some additional enhancements to the software's functionality, in particular:
• The ability to set up customer service levels and use them to drive workflow (see page 12)
• Support for working capital finance services (see page 15)
The New Architecture

TI Plus version 1.4 uses web technology, removing the need for banks to install software on
individual PCs. This allows banks to install and administer TI Plus for use by multiple regions or
branches in one place, reducing operational costs and implementation effort.
© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 7

TI Plus has been designed to meet the technical infrastructure needs of banks of all sizes, from
the largest to the smallest, whilst allowing a simple upgrade path.
For larger installations, TI Plus web components can be run in a full J2EE environment, with
multiple firewalls separating the web components from the background application and
underlying database servers.
For smaller installations, TI Plus web components can be run on a MS IIS/Tomcat or

Apache/Tomcat platform, possibly on the same physical machine as the application server,
resulting in a small, easy-to-manage server configuration.
The New User Interface

Transaction processing remains based around the Masters window and the Master Summary
window.
The Masters window allows users to browse the database, finding and opening existing
transactions; and to initiate new transactions.
The Master Summary window displays information for an existing transaction and allows users
to continue work on that transaction.

Individual panes can be opened up using the icon. The example below shows the diary area
opened up for viewing.
TI Plus includes a summary of charges and easier access to step history directly from the
Master Summary window.

During transaction processing, all the input fields are now displayed in a single window, as
shown below, instead of in separate windows accessed by tabs.
Information, input fields and buttons are grouped into panes, and each pane has a title. The
and icons open and collapse individual panes.
The fixed area on the left-hand side of the window includes a list of panes in the current
window. Clicking on the title of a pane takes you to that pane, so that you do not have to scroll
down and find it.
This fixed area also has:
• Links that allow the user to navigate the system. These include options that allow you to
close the current window and move back to the previous window, and eventually to log out
of the system
• Links that allow the user to access functionality common to all products, for example for
handling settlement instructions, charges, postings and customer documents; and for
validating and saving input

Amendment Charges
The accuracy of amendment charge calculations has been improved. The effect of double
accounting (which can occur as result of amending the expiry date and its effect on the
amendment charge calculation, due to rounding back to the start of the current period) has
been reduced. The corresponding charge text provides more accurate details of how the
charge is calculated.
Amendment Events
Enhancements have been made to the Adjust, Amend and Beneficiary Response to Amend
events for the following products:
• Standby letters of credit

• Guarantees
• Collection orders
These events now have a Changes button which allows the user to see changes made in that
event. They also now enable more fields than previously for editing.
Previously, parallel Amend events were not allowed for collection orders; if an Amend event
was already in progress for a collection order master, the user was prevented from opening a
second Amend event. The user had to abort or complete the Amend event already under way
before they could start a new one.
The Adjust event remains exclusive.
Customer Documents
Outward documents are now viewed, edited and printed in PDF format using Adobe Reader.
(Microsoft Word is still used to create the document templates.)
Faxes
A new implementation of the fax interface is provided, using a new set of key words within the
document templates and a new set of fax classes on the document server that can be used to
link to the fax system of choice.
Users have the option to keep or strip out the fax routing cover page in a customer document.

On-line Help Text

TI Plus now has contextual on-line help text, which is accessed using the Help link.
Report Handling
A report server has been introduced so that the end user does not have to wait for TI Plus to
create the requested report before continuing with their work. A new Jobs Status Screen allows
users to list all the report jobs submitted and allows view, delete or re-submit them.
Russian Accounting Requirements

A number of enhancements have been made to handle the Russian requirement for cash
method accounting.
Service Level Agreements

TI Plus's new service level agreement (SLA) functionality allows banks to set up SLAs with
customers involving target times for completing time-sensitive events. SLAs provide bank-
defined service levels such as gold, silver or bronze. Overall defaults for different kinds of
activity can be specified with specific agreements for groups of customers or individual
customers.
Target completion times can be specified, either as an absolute time or as a duration. For
example, a gold-level SLA can be set up so that:
• Import letters of credit received before 11:00 am will be processed the same day, but
• Import letters of credit received after 11:00 am by the end of day the following business day

An enhanced TI Plus user interface - the Dashboard - is used during transaction processing to
monitor work in progress and manage workflow so that those target times are met.
The dashboard is an extremely powerful workflow management tool, providing strong

operational control (a requirement of legislation such as Basel II and Sarbanes Oxley). It
identifies performance efficiencies of teams and individuals and enables a high level of overall
visibility for global and regional operating centres.
During transaction processing, events are displayed as having one of three SLA statuses - low,
medium or high, differentiated by colour - depending on how close to their target completion
time they are. The bank defines when an event's status will change to medium and then to
high, relative to its target completion time.
The bank can also provide average processing times for each step in an event. These are used
during transaction processing to calculate and display in graphic formats predictions of the
workloads of different teams and users
Teams and the Dashboard

A hierarchy of teams can be set up to accurately reflect organisational structure. This provides
the scalability to represent just a single branch with teams for different product areas, right up
to a regional or global operation where a regional processing hub or head office wishes to
monitor and report on the activity of a hierarchy of teams across the globe.
The Dashboard shows each team their current workload in graphical format. This enables the
team supervisor to very quickly spot potential problems in complying with the service level
agreements. Work can be reallocated to another team where bottlenecks are identified. A 'what
if' facility enables the supervisor to calculate the work loads based on how many people are
available to work per team.

Profiles defined at team or individual user level define the default views shown on the
Dashboard.
SWIFT
SWIFT MT400 Advice of Payment messages are now supported for both inward and outward
cash letters.
SWIFT Message Handling

A number of operational enhancements have been made to the SWIFT message manager
application.
It now allows incoming messages to be mapped into any event.
It now allows an MT742 Reimburse Claim message to be mapped into the appropriate event for
an import or export letter of credit.
A status of 'Pending' has been introduced. The user can flag a message as pended in order to
be able to ignore it for the present.
For continuation messages (for example MT700 and MT701 Issue of Documentary Credit
messages) merged and completed messages are now shown as a set.
A warning messages is now produced for a second claim against a letter of credit.
The user can now open and review the relevant master record from within the SWIFT message
manager application.

Inward SWIFT messages can now be sorted in the browser according to date and time
received.
Additional capabilities have been introduced to control access to different functional areas of
SWIFT inward message processing
Working Capital Finance

TI Plus now has a new application - the Working Capital Finance application. It uses the
following separate products to handle factoring and discounting:
• Factoring Facility, which allows your bank to set up factoring facilities for individual
customers and to process related drawdowns and charges against a customer's pool of
invoices
• Invoice, which is used to record new invoices against factoring and discounting facilities,
and to amend, discount (and repayment of the individual invoice), cancel and settle
individual invoices
Factoring
The Factoring Facility product allows a bank to establish a factoring facility with the customer,
recording details such as standard settlement instructions for drawdown, frequency of forecast
statements, whether with recourse and the frequency and type of charging.
Once the facility is established the bank can:
• Amend it
• Provide a forecast of amount available for drawdown to the corporate on a regular basis.
• Collect scheduled charges based on statistical amounts (for example, the value of invoices
loaded or paid or overdue) derived from the customer's sales ledger, as well charges that
have arisen on the facility itself since the last charges were collected
• Drawdown against the pool of eligible invoices
Each activity can be handled manually or (with the exception of drawdowns) scheduled to occur
automatically. Forecast and drawdown requests may be triggered by a customer using an
online banking application.
Invoice Discounting
The Invoice Discounting product allows financing against an individual invoice (rather than
against a pool of invoices, as handled by the Factoring Facility product).
The bank purchases the invoice from the seller. There is no obligation by the bank to manage
the seller's receivables as they typically would with a factoring facility, so it is still the seller's
responsibility to chase late payment of invoices, rather than the bank's. The bank can give an
advance (discounted financing) to the customer for a percentage of the invoice value on
request, when the invoice is submitted or at a later date.

Sales Ledger Processing

At corporate customer level, the bank monitors each sales ledger by recording details of
invoices issued. The bank agrees with a corporate customer the percentage advance allowed
for each buyer, and this percentage may vary from buyer to buyer. To be eligible for inclusion in
a drawdown calculation or for discounting, an invoice must meet the certain criteria.
The bank has recorded an invoice it can.
• Amend it
• Cancel it
• Settle it, fully or partially
• Trace for overdue payment
Invoices may also be created, amended or cancelled following a request a customer using an
online banking application.

Chapter 2 TI Plus Version 2.2

This chapter describes the enhancements in TI Plus version 2.2. It covers improvements to the web-
based architecture, and enhancements made to the software used to handle trade finance.
The Improved Architecture

The TI Plus 1.x platform was still tied to the Windows platform at the server side. Banks increasingly
want open platform solutions. TI Plus now meets that requirement using a JEE solution which means
that it is platform independent.
All the pre-existing underlying business logic and functionality of the software remains unchanged. In
addition, banks upgrading to TI Plus use their existing database, meaning that there is no loss of
historical data or of system tailoring parameters.
TI Plus runs in a clustered JEE server (using Spring as a lightweight container). It is envisaged that
large banks and those that require high availability and fault tolerant systems will run appropriately
configured high end JEE application servers.
System Management (Global Application)

The client server control system (CSCS) is replaced by a number of open source and new java
components. The CSCS console becomes a global application console driven by JMX (Java
Management Extensions) to handle logging, diagnostic and management functions. This allows banks
to incorporate TI Plus functions into their own system management consoles such as WebSphere or
Tivoli. This means it becomes a plug and play console.
Changes have been made to support clustering of zone applications, with the aim of increasing
scalability and fault tolerance. Overnight processing for a zone can now be initiated and monitored
from the global application and will be run across the zone cluster.
Changes have been made to allow TI Plus user security processing to integrate with the bank's own,
in particular to allow the bank to monitor users from the global application. TI Plus users can be
automatically created using details from an external authentication system. It is possible to send
notifications to individuals or to all users from the global application, and also forcibly to log them off.
Open Source Components

TI Plus adopts a number of open source components. This means that some of the underlying run
time tools disappear and are replaced. Principally this affects:
• Database access
• Session logging and debugging
• User access
• The Customer Gateway
• SWIFT

• Browser user interface

• File system access
• Unicode
In addition:
• Third party log viewing is handled in whichever way the bank wants
• Batch scheduling calls a Customer Gateway service
• The CVSLOG is replaced by Log4J
Session Logging and Debugging

Session logging and debugging is based on the Apache Commons Logging infrastructure, allowing
integration with compatible logging implementations such as Log4J. If Log4J is used, extra context
information is available, including user, node and zone for each activity. Many third party tools can be
deployed with Log4J, for example to generate email alerts to operations staff if problems are
encountered
User Access
Security in the application servers uses Acegi to provide single sign on capability and
authentication/authorisation checks on all incoming requests. Banks can link into their own security
systems by writing small, Java 'plug in' components in the Acegi framework. The fine-grained security
capabilities of TI Plus are retained.
The Customer Gateway

The Customer Gateway is used far more extensively by TI Plus, for:
• Corporate front end interfacing

• Back office interfacing
• SWIFT messaging
• Data replication
• Batch action processing
• Document handling, including attachments and images
It acts as a stateless service route into TI Plus, thus supporting greater scalability. The messages are
in structured XML format but not initially operating over SOAP. Banks can implement simple java 'plug
in' adaptors to convert TI Plus messages into the required external system message formats and
protocols. A range of standard adaptors will be developed over time to include RMI, EJB, JMS, Misys
Meridian, and Web Services.
Browser User Interface

Data entry via web forms is implemented using industry standard JSF.

File System Access

File system access is handled by a clusterable content management system. This affects standard
reports, configuration import/export, documents and archiving that all refer directly to Windows
folders. If a bank does not already have a preferred content management system, a rudimentary
content management feature is supplied.
Unicode
Unicode is used to give standardised character set encoding and support
Enhancements
The following sections describe the enhancements made in TI Plus version 2.
Analysis
The sundry reference codes provided for your bank to use for analysis purposes now have a new
format, as illustrated below.
Calendars
Your bank can now configure TI Plus so that you can enter unexpected holidays on an ad hoc basis
against local run day calendars. (This is controlled by the system option
CalendarUnexpectedHolidays.)
Clauses
Clause codes are now displayed in the appropriate fields when the user presses the Validate button.
Clauses can now be mapped to the narrative fields of Assignment of Proceeds events.
Charges
TI Plus's charge-handling functionality has been enhanced so that it allows banks to consolidate
charges of the same type for customer correspondence documents (this is controlled by a system
option).

TI Plus now supports:
• Single-cycle charges (see below)

• Multiple charge cycles within a period (see below)
• The aggregation of all charges of the same type when taking charges – for example add up all
SWIFT (or other) charges with one total when taking. On a customer advice the bank will be able
to include total of each correspondence type of charges including a count of related
advices/documents produced since the last advice. Ability to waive one or more of that type
The charge details generated automatically by TI Plus for inclusion on customer documents can now
be amended. Two new fields provide charge text information - one for documents, the other for
SWIFT messages. These fields are used for the bank's own charges and for other banks' charges. A
system option governs whether, by default, they are to be left blank or are to be populated by the
system with charge calculation details. The input clerk can amend their content at run-time.
A new flag is provided to set the default (Take or Defer) for charges at event level.
A new event field - One Or More Charges Modified - has been created to allow your bank to set up a
warning message if a charge schedule is modified during transaction processing.
When a periodic charge is cancelled using a Maintain Charges event, TI Plus now recalculates the
charge up to the processing date in order to determine whether a refund is due or not.
A new event field is now available to facilitate setting up a warning message to be generated
whenever an event involves periodic charges that have been amended in such a way as to result in a
refund to the customer.
Single-cycle Charges
For letters of credit, standby letters of credit, guarantees and participated deals, TI Plus now permits
banks to set up single-cycle charges - charges that are accrued periodically, but taken in arrears
when a payment is made. This caters for transactions involving large amounts and a lengthy life-cycle
where, typically, the period corresponds to the duration of the transaction and the collection of
charges coincides with payment.
Single-cycle charges are calculated from the day the transaction was confirmed (or silently confirmed)
to the date of documents being settled, taking into account any decreases and or increases that took
place during the period. They are designed to cover the duration of the transaction, using a single
period, without predefined repeating charge periods and related regular charge payment events.
Essentially, this provides a more ad-hoc version of the Pay Charges event, but more closely aligned
with payment events.
The charges are accumulated using standard functionality, but with an option to prevent the posting of
accruals.
Single-cycle charges are collected during payment events, at the same time as payment settles. They
stop accruing when the final part-payment settles. They can be cancelled, if required, using a
Maintain Charges event.
Multiple Charges within a Period

An enhancement has been made affecting standard periodic charges that enables banks to collect
multiple charge cycles instead of collecting a small amount of a periodic charge. Also the bank is able
to collect the minimum charge amount at the earliest opportunity possible. When a periodic charge is

started in an event or during its charge pay event, the user is to able specify on the charge schedule a
number of periods (‘Multiple charge by’) required to be calculated instead of the standard one period.
Currencies
The new translation facility supports the display of minor currency unit descriptions in amount fields
and customer documents.
Customer and Account Retrieval Services

TI Plus provides services to allow the bank to browse and retrieve customer and account details from
an external system at run-time, rather than from the TI Plus database. This means that, if the bank
does store customer and account details in an external database, it no longer needs to download
them to the TI Plus database to keep the two databases synchronised. When a customer or account
is retrieved from the external system TI Plus does store a local copy. TI Plus also enables ‘local’
customer details to be entered within TI Plus, that is, details which are not available from an external
customer information file.
Banks can define the content of the customer and account browsers used to suit the information
available at the back office.
TI Plus provides the ability for parties to a transaction to have an account per transaction (like a deal
account), with real-time account opening functionality.
Customer Details
TI Plus holds additional information on customers, including fax and telephone numbers, e-mail
address and department code. These new fields can be used in customer documents. TI Plus also
allows a longer basic number (12 characters), account officer code (10 characters) and account
number (20 characters, consisting of the branch code (4 characters), basic number (12 characters)
and suffix (4 characters)).
Customer special instructions are now structured rather than free format. Special instructions can be
given a relative priority and colour scheme. For example a high priority instruction could be colour
coded red, whilst informational instructions could be blue. Any special instructions held against a party
to a transaction are displayed together with warning and error messages when a transaction is
validated or saved.
TI Plus provides a choice of addresses to use when creating customer correspondence; and allows
the bank to define for each type of document the number of copies, the number of internal copies, and
the number of originals to be produced. This information can be set as a default when the document
type is set up, and amended at runtime.
Pre-allocated Reference Numbers

When pre-allocating blocks of reference numbers to a customer, your bank can now make the
allocation by product/product type combinations, as well as just by product.

Customer Documents
TI Plus uses a new method for producing customer documents in fax, e-mail and mail formats.
Templates for customer documents are first defined as Word .dot templates. They are then converted
into xhtml format, and subsequently loaded into TI Plus, where they are linked to the document types
that will use them. A customer document template utility is provided to handle this process.
During transaction processing, the templates are used to generate customer documents in PDF
format.
Banks can use the customer document template utility to create new templates and amend existing
ones, in conjunction with a document management system.
The customer document template utility also provides facilities to handle any special fonts and graphic
files your bank may use.
All TI Plus document templates are stored in a document management system, (DMS) as opposed to
the database as in previous versions, together with any related attachments and scanned images.
The Word .dot files are also stored in the DMS.
As a one time activity on upgrading to TI Plus, all document templates will need to be converted by
the template utility, prepared for upload, and then imported into TI Plus.
Enhancements have been made to the functionality used to attach documents to a transaction. Users
can now add multiple versions of the same document type to be attached to a transaction, with a
different description for each. A new Replace button is allowed (this is controlled by a system option)
which lets the user replace documents with previous versions being held for information purposes.
This is to cover cases where the initial document is found to include errors or is superseded for other
reasons. It allows you to retain a full history of the documents recorded against the event.
Banks can now configure document types to produce multiple copies of original, internal and copy
versions of customer documents. At runtime the user can use sent documents, incoming and
outgoing SWIFT messages and received documents as attachments to other parties on an ad hoc
basis.
New Event Fields for Customer Documents

New event fields are provided that allow the inclusion of payment total amounts in customer
documents, specifically debit and credit advices. These fields are for use with the following products:
• Import and export guarantees

• Import and export letters of credit
• Import and export standby letters of credit
• Collection orders (all types)
A new event field is provided containing only the tenor text for a draft.
The new fields introduced as a result of enhancements to participation deal processing are available
for inclusion in customer documents.

Customer Gateway
The use of the Customer Gateway has been extended to facilitate communications using messages
in xhtml format. The Gateway is now used to support generic free-format messages, with or without
attachments.
New TI Plus message manager functionality is provided to allow users to create a new master, or a
new event against an existing master, by uploading documents or images into the DMS.
Customisation
TI Plus customisation facilities are now supported in the web-based architecture.
Any existing Visual Basic procedural code written for a customisation project will need to be rewritten
in Java.
Data Take On
TI Plus provides functionality to allow legacy data to be incorporated into TI Plus for the following
products.
• Import and export letters of credit

• Import and export guarantees
This is done using Customer Gateway messages, which then create a data take-on event for each
transaction.
If the bank wishes to incorporate any customer documents or correspondence forming the history of a
transaction, this can be handled as free format correspondence received through the Gateway and
attached to the relevant legacy data master record.
Diary Processing
The Diary Items pane in the Master Summary window has been enhanced, and diary items are now
shown in the SLA Dashboard. There are additional filters, and more information is shown for each
diary item.
Tracer events are now included in the display of diary items, rather than being treated as separate
items.

Diary items are now displayed under the following category headings:
• Manual
• System (Auto)
• System (Manual)
• Tracer
A new Release Items|Diary Items link displays details of the diary actions that will be generated when
the event completes. This allows the supervisor to review the full list.
Certain TI Plus events (for example, Book Off and Expire) involve the creation of a diary action that TI
Plus uses on the appropriate date to create a new event automatically during overnight processing.
Banks can now flag these events so that the diary action is still created, but TI Plus does not generate
the related event automatically; it must be created manually instead.
Authorised users can amend or delete automatically generated diary entries (provided they have the
required security capabilities).
When adding a diary action, or amending an existing one, the user can assign the action to a
particular user or team. The diary item will then appear in the 'to do' list for that user or team in the
SLA Dashboard.
Export Credit Agency Facilities

TI Plus now supports export credit agency facilities, whereby an export credit agency lodges funds
with your bank for the purpose of providing short-term loans to exporters who are customers of your
bank.
Each such lodgement of funds is recorded in TI Plus using a single product - the Export Credit
Agency Facility product. Your bank can distinguish between different types of export credit agency
facilities by setting up product types for that purpose. TI Plus's rules facility can then be used to
govern how a facility should be handled, depending on its product type.
An export credit agency facility is set up for a specific customer following agreement with the export
credit agency.
Loans against an export credit agency facility are handled using financing transactions, which are
linked to the relevant export credit agency facility. The facility can be set up before the financing
transaction, or at the same time.
As a financing transaction is linked to a facility, the amount of the facility is reduced by an equivalent
amount using an automatically generated Drawdown/Revolve Facility event.
The cost-of-funds interest payments due to export credit agencies are set up using interest types, and
the scheduled interest payments are calculated and made to the funding party either automatically
according to the schedule or when a repayment is made against a linked financing transaction (this is
determined by product type settings).
The following financing products can be linked to an export credit agency facility:
• Finance Standalone
• Finance Export LC (for export letters of credit, guarantees and standby letters of credit)
• Finance Outward Collection

Financing and Export Credit Agency Facilities

TI Plus's financing functionality has been enhanced to support export credit agency facilities.

Interest types can now be flagged as one of the following:
Markup Plus Cost of if interest involves a combination of interest for your bank and interest for
Funds internal or external funding.
Markup if interest is for your bank.
Cost of Funds if interest is for internal or external funding.
When defining schedules for interest repayments a new field - the Schedule Tenor field - allows you
to enter the actual number of days for which financing is to be applied, entered as a figure. This
allows separate schedules to be defined for the main term of the deal and for the past due period.
When defining product types for use with financing transactions, you can now flag a product type as
to be used for cost of funds processing. Additional fields are displayed that allow you to enter relevant
details.
On release of the initial event for a financing transaction a drawdown event is automatically generated
against the related export credit agency facility.
Financing
For financing created from letter of credit payment events, TI Plus supports additional fields for
inclusion in documents generated from the main payment event (rather than from the subsidiary
event). In addition, banks can configure TI Plus so that financing interest calculations are made via a
service call to their host system, rather than by TI Plus. This ensures that the amounts recorded are
consistent across databases, and rounding issues are avoided.
A new system option allows the output of financing accruals to the host system interface to be
suppressed.
A new payment action allows the repayment of outstanding post finance against a letter of credit part
payment that had previously paid/settled.
FX Rates
A new interface service is provided to allow banks to request FX exchange rate details and amounts
from an external system when FX deals are being entered in TI Plus. This functionality is activated by
a system option.

Imaging
TI Plus uses a general document management system interface. This allows it to store and retrieve
items such as .pdf documents and electronic images using an external document management
system.
Images are retrieved using their unique URL.
Notes
New functionality is provided to allow the input clerk to view details of the notes entered against a
transaction and to enter new notes with an event still open.
Participated Deals
Banks can now flag each participation deal as requiring manual processing. This means that, instead
of changes to a participated transaction causing changes to the relevant participation deal to be made
automatically, any changes required to the participation deal are made manually instead. This
functionality is implemented using a system option.
For manual participation deals, users can create a Drawdown/Revolve event manually to make any
changes necessary following a change to a participated transaction.
Each participant now has a start date and a release date. These dates define the period for which the
participant will be involved in the deal.
Single-cycle periodic charges now allow charges to be calculated based on the participant's start and
release dates, taking into account any Drawdown or Revolve events that have occurred during the
period. The charge calculation also takes account of the participant's share of the Drawdown/Revolve
Amount.
In order for the syndications department of a bank to be notified automatically about changes made
manually, the bank must define a Customer Gateway message template and include the appropriate
information to be sent when an Amend or Adjust event is created that affects a participated
transaction.
Postings
The way that postings are displayed has been enhanced to improve the readability of information.
Postings are now grouped for display into the following categories:
• Contingent
• Settlement
• Other liability
A new system option allows banks to exclude internal postings from the display.
Another new system option allows banks to define a list of account types that are then used to
determine whether a posting belongs to the 'Other Liability' category.

During transaction processing, as postings are generated, TI Plus compares their posting value date
against the Posting Forward Values Days field to ascertain whether or not they are too far in the
future. A warning message is issued for postings whose posting value date is too far in the future.
Banks can now choose to have this validation carried out for all postings, or to restrict it to postings
that are valid for funds movements. This is controlled by a system option.
The window used to display postings at master level now allows users to order postings by account or
by event.
If ordered by account, TI Plus lists all the accounts that have posting against them for this master, and
the user can select an account and view the netted and un-netted postings for that account.
If ordered by event, postings are listed by category within event.
Remote Printing
TI Plus provides functionality to support remote printing - that is, printing at a location other than the
one where a transaction is being processed. This supports situations where a transaction originates at
a branch and is then processed at a central location, but customer documents need to be printed at
the originating branch for delivery to the customer.
This enhanced functionality is switched on using the RemoteTransactionOrigination system option.
TI Plus handles the production of documents generated during transaction processing using
document printer types, which are used to define a standard set of common print characteristics for
the types of document your bank uses. The document printer types can then be associated with
multiple document templates, allowing you to define common printer attributes (such as colour,
quality, trays and watermarks) that are to be applied for all documents produced using that particular
printer type
When defining the document types used by your system, you can specify one or more a document
printer type for each template. Where more than one document printer type is associated with a
document type, you can flag one of them as the prime document printer type; this is the one that is
used as the default during transaction processing.
The system tailoring functionality called by the Output|Printer Names menu option has been replaced
by new functionality used to set up printer types and then map them to printers and teams.
A team can now be flagged as being a ‘print team’, used solely for remote printing.
During transaction processing, the input clerk enters details of the originating user in the initial event.
These are recorded against the event and on the master record and are used to determine the printer
at which remote printing is to be carried out in the initial event and in subsequent events. When
processing the transaction, TI Plus identifies those document types flagged as available for remote
processing and uses the team to generate the documents, together with a generic front page showing
the originating user's details. The document is then routed for printing using the relevant
team/document printer type/printer mapping.
At the end of the Input step and at the end of the final step in an event's history, TI Plus displays a
window showing the customer documents generated by that event that allows documents to be
printed (excluding items produced automatically during overnight processing).
If your bank has implemented TI Plus's remote printing functionality, an additional pane - the
Originator's Details pane - is present in initial events (that is, events that create a new master record).
It allows you to enter details of the originating user and branch for use when customer documents
need to be printed remotely.

Reports
TI Plus continues to use Crystal Reports as the report writer, but with a new Java-based way of
invoking Crystal Reports at run-time.
TI Plus is delivered with a suite of reports and reporting views. Some reports are now available in PDF
format - see the Release Notes for a list.
The Full Journal Report now shows before and after details for customers.
Responses to Enquiries from External Systems

TI Plus provides services that allow your bank to define responses to enquiries for information from
external systems. Each response consists of a set of data based on TI Plus database fields. This can
be used, for example, to provide an external system with outstanding balance information for one, for
all, or for selected masters that are active within TI Plus.
Three types of enquiry are supported:
• Enquiries on master records for a particular customer

• Detailed enquiries on individual masters and associated payments
• Enquiries on balance information for one or more master records
For responses to enquiries on balance information for one or more master records, a single response
is defined for use with all products. For other enquiries, banks can set up separate responses for use
with a specific product, or product and product type.
When an enquiry message is received, TI Plus creates a response message populated with
information taken from the relevant database fields.
Settlement
TI Plus allows users to change the date of a net payment when reviewing settlements. This allows
separate dates to be entered for the receipt of funds and the payment of funds relating to the same
transaction.
This is useful, for example, where payment is made under an export letter of credit where the date of
the receipt of funds at the nostro is earlier than the credit to the beneficiary's account.
Shipping Guarantees
Shipping guarantees can now use the following SWIFT message types:
MT498 Proprietary Message
MT499 Free format message
MT798 Proprietary Message

MT799 Free format message
TI Plus no longer produces a warning if the principal party in the shipping guarantee does not match
the principal party in the related master record. (Banks can, however, add warnings using standard TI
Plus functionality.)
Silent Confirmation
TI Plus allows banks to silently confirm export letters of credit and export standby letters of credit.
SLA Processing
Banks can now reassign master records from one user to another using TI Plus's configuration
application. This new functionality allows banks to switch all master records from one user to another
(if, for example, an employee leaves the bank) or to reassign master records one by one.
The Work in Progress pane now has filters that allow the user to list work allocated to a particular
master user, master team, event user or event team.
Banks can now define the colours used indicates a transaction's SLA status - high, medium or low.
Users can now open a new transaction from within the Dashboard window - it now contains the same
New Masters pane as the transaction processing application's Masters window.
The Dashboard now lists the user's or team's diary items, showing items that are outstanding and
items that have fallen due today. The user can filter the list by item type, and can also enter a date
range in order to list items that will fall due within the period specified.
Team profiles can now be set up from within the system tailoring application, as well as from within
the Dashboard.
Standby Letters of Credit

Banks can now use the Import Letter of Credit and Export Letter of Credit products to process goods-
related standby letters of credit; and the Import Guarantees and Export Guarantees products to
process standby letters of credit that are not goods-related. This functionality is controlled by a system
option.
SWIFT
TI Plus supports the SWIFT MTx98 Proprietary Message With Other Banks message type.
This is NOT within the context of SCORE to facilitate corporate-to-bank messages.
SWIFT MTn90 Advice of Charges and MTn91 Claim Charges message types can now be sent by any
event (provided that charges are being taken, not claimed, in the event).
The mapping of date information in Tag32A and Tag34A in an incoming MT754 Advice of
Payment/Acceptance/Negotiation message to the relevant fields in the Claim Received or Documents

Present event has been improved, so that it takes account of whether there is information in just one
field or in both.
Transaction Processing
A new event field has been introduced that identifies the staff security band to which a TI Plus user
belongs. (The staff security band is used to restrict the user's access to individual events at the Input,
Review or Authorise step based on the event value.) This new event field can be used in creating
error messages.
Users can now exclude aborted events from the list of events shown in the Event History pane.
Banks can now configure the colours to be used:
• To distinguish between the statuses of transactions in the SLA Dashboard

• To display notes and special instructions
Banks can now configure, at product or product/event level, a header showing contextual processing
information. This is displayed in a pane at the top of the window during transaction processing.
During Outstanding Claim and Outstanding Presentation events the Select button (used to select the
claim to continue, where there is more than one outstanding) is now present during the Log step, as
well as the Input step.
The functionality that permits users to add optional charges and documents to an event has been
enhanced. Now, if the event is, or has, a subsidiary event, the list of optional items includes those
available to both events - the main one and the subsidiary event. A new column - the Originating
Event column - provides the reference of the event for which the item is set up as optional.
Two new event fields are now available to facilitate setting up warning messages to be generated
whenever an event party has too many lines in their address, or too many characters within a line.
Translation Facilities
A new menu option in the static data maintenance application - Country|Static Language Variants -
allows your bank to provide translations of the following static data items:
• Account types
• Account officers
• Base rates
• Charge codes
• Country codes
• Currency major unit names
• Currency minor unit names
• Deal types
• System parameters
• Transaction codes
• Transfer methods

Transfer Letters of Credit

New events are provided for transfer letters of credit to support correspondence and
acknowledgement.
Workflow
TI Plus allows the team ID to be included in a master reference structure.
Incoming SWIFT MT707 Amendment messages can now be automatically routed to the team who
last worked on, or is currently working on, the related transaction.
Incoming SWIFT MT700 messages can be automatically routed to letter of credit, to standby letters of
credit or to guarantees, depending on the information in certain tags.
TI Plus allows banks to identify a responsible user (as opposed to the processing user) for each
master record. This can be used for apportioning revenue.
Your bank can now configure when an approval step will take place. An approval step can now occur
after the Log step, when it is called the Log Approval step; or after the Input step, when it is called the
Approval step. If the system option AlwaysCreateLogApprovalStep is set on then a Log Approval step
is always carried out after the Log step. This is regardless of whether exceptions are discovered. If
the system option AlwaysCreateLogApprovalStep is not set on, then your bank can configure at
individual event level whether an event will have a Log step or not. If an event is configured to have a
Log step with the system option AlwaysCreateLogApprovalStep not set on, then the Log Approval
step appears only if exceptions are discovered.
Provisional events
Your bank can now configure TI Plus so that the event that creates the master record (for example an
import letter of credit Issue event) can be treated as a provisional version of the event. A field within
the Log and Input step for such events allow you to flag the event as provisional, in which case a
subsequent version of the event is needed before the event can be completed. A second field allows
you to indicate whether this subsequent event should be created automatically or not. (Your bank can
set default values for each of these fields for each product.)
This can be used, for example, where bank procedures require a logging and authorisation process at
the branch, with outputs such as handling charges or limits checking, followed by further processing
at a processing centre; or where draft outputs need to be sent to a customer for verification for
completing the issuance.
An event can have any number of subsequent events, each being flagged as provisional until the data
is deemed correct. Each version of the event can have its own defined outputs, with final outputs for
the last version of the event (that is, when the event is no longer provisional).
This functionality is implemented using the system option AllowProvisionalFullDefiningEvent. It can be

used in conjunction with TI Plus functionality that allows your bank to route events to specific users or
teams, depending on which step it is at. It can also be used (in conjunction with TI Plus's rules facility)
to permit draft versions of documents to be produced for provisional events and to control, for
example, the release of tracers, postings and charges.

Link Multiple Shipping Guarantees

Clients require the capability to link multiple Shipping Guarantees to an Inward Documentary
Collection or an Import Letter of Credit transaction. A one to one link will remain between the
Document of Title referenced in the master transaction and the document defined within the Shipping
Guarantee. To achieve multiple linking, multiple Documents of Title are created in the master and a
Shipping Guarantee document can be linked to each. It is not permitted to link the same Shipping
Guarantee document more than once.
Example linking within Inward Documentary Collections
Create an Inward Documentary Collection with two or more Documents of Title:
Two documents with a Shipping Guarantee linked to each

Alternative Formula for Interest Rebate

Where early repayment of interest in part, or in full, is effected under TI Plus 2 Financing transactions,
it may be necessary to return overpaid interest to the customer. Where this situation arises, a rebate
of the overpaid amount is required.
TI Plus 2 uses a ‘Standard’ interest calculation formula which it applies to rebate interest. However,
this enhancement introduces an ‘Alternative’ rebate interest formula, based upon the remaining
number of days to the maturity date of the finance deal.
This is calculated as follows: Maturity value less revised maturity value due to an early principal
payment, calculated using the remaining period/term.
The alternative rebate formula applies to all Financing transactions in TI Plus 2, where interest is
taken in advance.
If separate ‘Cost of funds’ interest applies to a transaction, the alternative rebate formula will apply to
both ‘Customer/Markup’ and ‘Cost of funds interest’ streams.
The formula applies when a part, or the whole, of the outstanding principal amount is repaid early.
Interest rebates are not applicable in Scheduled Pay events:
Early payment is not possible.
Interest, principal amount and value date fields are not editable.
Rebates to the customer are not possible in Amend or Adjust events.
Ability to Save a Deal as Template

For some products TI Plus allows you to create transaction templates to facilitate the creation of new
transactions. Each template contains a basic set of information that is copied into each transaction
created from it. Transaction templates can be:
• Customer-specific, in which case the customer name forms part of the basic data
• Generic, for use with any customer
You can create a new transaction template in one of two ways:
• By basing it on an existing transaction

• By creating a new transaction and then saving it as a template
Ability to split a commission to more than one party

TI Plus allows you to split a charge between the various parties to an event provided that the charge:
• Is not a periodic charge

• Is not a consolidated charge
• Is not a charge that has already been split
• Is a charge for the buyer or the seller - charges for 'Other' parties cannot be split

• Is a charge for your own bank - charges for other banks cannot be split
Auto refresh of Dashboard

TI Plus auto-refreshes the dashboard screen, where a user selects an item from the dashboard,
processes it and then closes the master and goes back to the dashboard.
Enable output of Clearing Service Identifier on MT103 and MT202

There are currently a number of payment clearing systems in use within the European Monetary
Union, such as “Target2” and the “European Bankers Authority”. These clearing systems are
identified in SWIFT MT103 (Credit Transfer) and MT202 (Financial Institution Transfer) messages by
use of three character codes, such as ‘TGT’ or ‘EBA’ which are included in ‘Header Block 3’ of the
outgoing message.
The requirement is to ensure that where users submit messages to a SWIFT - FINCopy service, the
three character alphanumeric code is quoted in Tag 103 (which represents the “Service ID”), of
Header Block 3 in outgoing messages.
This is shown in the following example:
Murabaha Import Financing

‘Murabahah’ is the sale of an asset at cost plus a known markup. A bank purchases a specific item
that the customer requires and then sells the same to the customer at a mutually agreed markup
price, based upon the bank’s cost of financing the purchase. Financing is Shariah compliant and
makes use of TI Islamic functions.

An initial ‘Finance Offer’ is put to the customer, advising such details as the rate to be applied to the
loan. If this offer is accepted, the loan is established. However, the Finance Offer may be rejected by
the customer and a new offer is subsequently created. The introduction of this functionality allows the
creation of the Finance Offer iteratively, until such time as the customer finally accepts or rejects it.
This process makes use of existing, ‘Master full defining event functionality’ whereby several
successive events may be created in a ‘Provisional’ state. This is achieved by use of the ‘Provisional’
flag in the finance create event, which allows the master to be created with a status of, ‘Pre-live’.
When the Finance Offer is eventually accepted by the customer, the ‘Provisional’ flag is not checked
and the create event moves to a ‘Live’ status.
The main feature of the new functionality is the ability to generate a, ‘Finance Offer’ to customers via
the following products, which can be revised on an iterative basis, until its acceptance or rejection:
• Import Letter of Credit (by its subsidiary, Finance Import L/C)
• Inward Collection (by its subsidiary, Finance Inward Collection)
• Standalone Finance
Release Password SSO

The new system option, ‘EnableReleasersPasswordPrompt’, will control password verification at the
event step level. This is triggered when the ‘Confirm’ button is pressed (e.g. Limits Approval, Watch
List Check, Review, Rate Fixing or Authorise).
In general, the password verification behaviour at the event step level will be controlled as per
Windows workstation authentication details (e.g. password criteria, permitted attempts etc.) for login
to TI Plus 2. This means the same authentication credentials are expected to be used by the user to
login to TI Plus 2 and when prompted to authenticate, as the releaser, at the transaction event step
level.
SWIFT Acknowledgement
SWIFT functionality allows for the Sender of a SWIFT message to request an Acknowledgement be
sent for the message. The Acknowledgement message (an F21 message) is generated by the SWIFT
network and either assures that the original message will be delivered to the Recipient (an ACK
message), or that there is a problem with the original message (e.g. a network validated rule is not
satisfied) and it will not be delivered to the Recipient (a NAK message).
Previously, a SWIFT Acknowledgement message could be processed only when the Client used
Merva, but this requirement no longer exists, i.e. processing of SWIFT Acknowledgement messages
is now a general feature in TI Plus.

MT292 Creation when cancelling MT202

Where payments are effected via SWIFT MT103 (Single Customer Credit Transfer), or MT110
(Advice of Cheques) with a covering MT202 (General Financial Institution Transfer) and such
payments subsequently need to be cancelled, MTn92 (Request for Cancellation), or MT111 (Request
for stop Payment of a Cheque) messages are sent by a financial institution, to request a second
financial institution to consider cancellation of the SWIFT message identified in Tag79 in the MTn92.
However, existing TI Plus 2 functionality only permits MT292 messages to be created for the
“Outward Bank Payment” product.
The purpose of this enhancement is to extend current functionality to enable SWIFT “MT292 –
Request for Cancellation” messages to be mapped to the following Clean Payment products:
• Outward Customer Payments

• Outward Cheques
Where cancellation of payments is required, this message will be generated.

Additionally, the MT292 must be transmitted to the financial institution to which the original MT202
was sent (i.e. the party providing cover for the payment), rather than the receiver of the MT103 which
is normal practice. This enhancement is therefore appropriate to transactions where payment is
effected via ‘Beneficiary bank with cover’, or ‘Intermediary with cover’.
It should be noted that this change to functionality is being implemented, even though it
does not adhere to the practice recommended by SWIFT. Sending an MT192 to the
receiver of the MT103 is the recommended and most logical option.
Rate Fixing in Business Hours

The Reconcile Rates function to confirm the spot rates and buy/sell rates is a business hours function.
The FX Rate Fixing function to apply those rates to FX deals may be scheduled to run in business
hours or in EOD. These capabilities are not changed, however the setting of FX deals to rate fixing
today or rate fixing tomorrow can encounter errors if deals are being actioned simultaneously with rate
reconciliation.
A batch function is required to manage logging off daily users prior to running Reconcile Rates. A
Pause and Resume step are provided to allow an authorised user into Reconcile Rates, complete the
process and then resume daily transaction input. The FX Rate Fixing function is available post
reconciliation within the batch function or in the EOD configured by a system option. The following
advantages are provided.
• Reconcile Rates is restricted to Security Officer, Operator or System Administrator users.
• Rate fixing menu items are moved to the Batch application to restrict availability to Batch
Setup users.
Errors encountered under FX rate fixing are presented in short ‘warning’ form in the Batch function
and with full details in the Batch Log.

ECR B 95% Lodgement

The Export Credit Agency Facility product (ECF) is used when an Export Credit Agency lodges funds
with a bank, for the purpose of providing short-term loans to exporters, who may be customers of the
bank.
This enhancement relates to the Export Credit Agency Facility product and provides users with the
ability to do the following:
• Link an underlying instrument, such as an Export Letter of Credit to the ECF, thereby defaulting
the “Available amount” from the underlying instrument to the “Total facility amount” field of the ECF.
• Convert the defaulted amount to another currency.
• Restrict the ECF maximum percentage, defined at Product Type level, which may be drawn
down.
• Round down the Total facility amount to the nearest thousand if required.
External DMS Interface

The bank has a centralised function to process documents received from their customers (or
transaction parties). The bank’s staffs, in this mail room type of function referred to as mail room users
who, pre-process and store incoming documents.
The mail room users may perform tasks such as scan paper documents, save or upload scanned
images and other formats of electronic documents (PDF etc) in the DMS. Also they are expected to
be trained to interpret incoming documents and identify the type of trade transaction (e.g. New LC or
Document Presentation under an existing LC etc.) required in TI, enter basic meta data for each
document when saved or uploaded in DMS, and initiate a new transactions from their DMS into TI
including details of stored documents.
The bank may have procedure to consolidate a set of related documents into a single document or
keep them as individual documents with or without a unique batch identifier. The latter approach
saves TI user input time when processing resulting transaction events in TI.
Interface to an external DMS systems.

Create an appropriate transaction/event based on an incoming request from an external DMS,
including the details of the related documents.
Update details of the transaction and relay specific document metadata to the external DMS.
Search and attach available document attachments from the configured external DMSs via the DMS
Browser to a transaction.
Upload documents held in a file system to the external DMS.
Detach documents from a transaction in TI and notify the external DMS to detach the
documents.
Allow a batch of documents to be processed within a single incoming transaction from an
external DMS

Global Processing
Banks providing trade services are very much focused on how to maintain and grow their trade
service business whilst containing costs, maximising use of their skills, and reacting to changes in the
market in which they operate.
Many banks offering trade services have grown to a size where they have market share and global
reach, and are looking to maximise their assets by adopting a processing model that removes the
constraints otherwise imposed by such factors as:
• The location of their infrastructure
• The location of their staff, and the skills mix at any particular location
• The banking entities they support (banks, brands, subsidiaries etc)
• Multiple time zones
• Multiple base currencies
• Access to operational or management information

Global processing is a way of operating that allows internationally active banks to reduce their
operational cost by automating cross-country operations, transactions and services; and helps them
expand their business across different banking entities, regions and countries, thereby increasing
their revenue and client base. In addition, it allows them to offer as a service the initiation of new
transactions and the progression of existing ones, regardless of where a transaction originated or of
the entities involved.

The TI Plus 2.3 system provides a number of functions to allow a bank to define its global processing
business operation. The purpose of this section is to provide an overview of these features which can
be broadly categorised into the following areas:-
• Static data – details the bank’s zone level and branch level static data
• Banking hierarchy – describes how the bank defines its organisational structure
• Teams/Users/Security – covers how roles are associated with teams and users to determine
the types of transaction a user can enter for their branches
• Multi-bank/branch tailoring – describes the bank’s zone level and branch level tailoring data
together with details covering
o Parameter sets - how processing is determined through different parameter sets
o Product references – describes how product reference and sequence numbers are
defined at main banking entity level
o External systems – how the bank defines external systems and the services they
provide
• Transaction processing, Cross Zone Dashboard and Workflow allocation
• Processing cycle definition and Extended business hours processing
• Reporting
Cross Zone Dashboard

• Charts, WIP and diary items enhanced to show summary of transaction details cross zone
and CZD totals displayed.
• Diary display enhanced to include non-manual transaction types in CZD.
• S.L.A. transaction completion times now displayed in W.I.P., according to user’s time zone
• Ability to filter by transaction on Team & User Totals
• Diary Item Date Range Filtering extended to allow relative date abbreviations for use across
multiple processing cycles
• Ability to reallocate work to user or team from the cross zone dashboard.
• Charts enhanced to show summary of transaction details cross zone CZD totals displayed.
• Introduction of additional Capabilities to Control Access to Dashboard & Master Browser
Workflow Auto-Allocation
• Auto allocation to next step made consistent for SWIFT/Input/Gateway/Batch
• Enhanced work allocation (for next event step) to use: Use event/team map. Capable team
based on branch and role. Use transaction affinity to identify last input team/user
• Provide the ability to allow user to repair SWIFT/Gateway message with no behalf of branch
or assigned team
• improved team/user assignment enquiry details on how auto allocation was determined

End of Day Enhancements

• Ability to map user defined custom control actions to processing cycles
• Ability to map report profiles to processing cycle phases.
• Ability to run EOD Processing cycles concurrently.
• Ability to cancel running EOD step from the Batch job runner.
Framework Deployment Enhancements

• Ability to define tuning parameters to control the resources used by the asynchronous
framework.
• Ability to deploy asynchronous framework as an independent application to reduce impact on
users of the system.
Enhanced Customisation Tool Set

• Customisation Tools have been enhanced to allow alternate customisations for an event to
be overridden at main banking entity level
• The customisation editor and template project have been replaced with an Eclipse project
based implementation
Departmental Limits
The departmental limits application is now available for banks that have a single main banking entity
within a zone.
Where a bank has multiple zones, then the recording of exposures against limits are maintained
completely separately per zone for the single main banking entity within the zone.
Note: Departmental limits cannot be used where a Zone has one than one main banking entity.
Configuration Management Tool

A new tool has been introduced to aid in the deployment of system configuration for sharing of global
baseline set up of parameters in a global processing environment.
The Configuration Management Tool (CMT) provides SQL scripts that enable a user to extract Static
Data and System Tailoring entries from a Zone database. The output from the scripts can then be
used to generate TI Service Request XML messages for import into another zone.
The Main features of the CMT are as follows:

1. Generate TI Service Request XML messages from 25 types Static Data entries.

2. Generate TI Service Request XML messages from 40 System Tailoring entries.

3. The tool can be executed using the command line and Ant scripts.
4. The CMT tool allows the bank to specify an SQL script or a directory of SQL scripts to generate
the XML messages.
5. The bank can optionally specify a directory where the generated XML messages will be created. If
the output directory is not specified, the generated XMLs are created at the same directory as the
input files.
6. The bank can optionally specify that the tool write the XML messages in one line. Otherwise, the
default format is to write the messages in "expanded" form.
7. Extra processing for physically deleted items.

Workflow Orchestration
TI Plus is designed to support the complex workflow requirements of a trade finance bank. In
particular it enables a bank to operate either regionally or globally using a spoke and hub type
workflow set up.
In such a setup bank can offer a local customer facing service in the spoke part of the workflow, for
example receiving and scanning documents received from a customer, negotiating FX contracts and
checking limits and printing out documents for the customer. The hub part of the workflow can provide
a centralised centre of excellence for further data entry and for checking the workability of the
customers’ requests. The hub would typically complete the data entry and any additional checks such
as for watch list compliance. The transaction would then proceed through one or more review steps
before items such as SWIFT messages and accounting entries are released. TI Plus comes with a
delivered set of workflow steps, sequences and conditions that can be configured for each transaction
event according to your bank’s needs. This is known as a workflow orchestration.
Supply Chain Finance

TI Plus Working Capital Finance application has been re-named Supply Chain Finance and has been
significantly extended to support the following:
• Three means of processing finance against eligible invoices:

• The Pool Based Factoring functionality covers drawdowns against a customer’s pool of
invoices. This is the existing factoring functionality
• The Seller Centric functionality covers financing against a customer’s invoices either
individually, or in bulk. Data workflow originates from the seller, who controls the ‘Programme’
and submits requests to buyers. The seller is therefore the ‘Anchor party’
• The Buyer Centric functionality cover financing against a customer’s invoices either
individually, or in bulk. Data workflow originates from the buyer, who controls the ‘Programme’
and offers to its sellers. The buyer is therefore the ‘Anchor party’
• Support for Credit Notes. A credit note can be linked to one or more invoices in order to
adjust the amount available on that invoice

• Changes to the invoice browser to use this as the single point of decision making for
invoice and credit note management and financing
To enable your bank to record, discount or settle invoices received from your customer, it is
necessary to set up a Supply Chain Finance ‘Programme’. A customer may have one or more
programmes, each of which must be allocated its own unique identifier when the terms are agreed
between your bank and your customer.
Software Development Kit

The Software Development Kit augments the flexibility that already exists within TI Plus to tailor the
system to a bank’s needs.
• Ability to create additional workflows for events (workflow orchestrations). This enables you to add in
extra logging, data input, review or post release steps for each event
• Ability to tailor the data that a user sees on each step in order to only show those fields relevant to the
workflow process at that stage. For example to have a basic logging screen and a detailed logging
screen. This can also be used to tailor the visible data on any step in the process
• Ability to notify an external process of an event’s latest status. This enables integration with an external
dashboard
• Ability to open and view a master or event via request from an external dashboard (subject to security)
• Ability to create tables in a customisation project. The tables can be added to events and masters and
the data in the table is accessible for adding to documents
• Ability to add additional applications to the TI Plus applications list
• Ability to create a proxy application for a zone so that transactions within it can be shown like any other
TI Plus event on the dashboard
• Incoming bulk messages can be processed in parallel
• During the configuration of pages using UI control files (formerly known as XML fragments),
the system can now monitor a folder of files rather than a single file
Data Extract Configuration Tool

The data model viewer has been re-developed as an Eclipse plug-in. As part of this, it has been
enhanced to provide a data extract configuration tool.
This supports the ability to extract key tables from TI Plus and transform them into tables within a
staging database (non operational database).

This is designed to enable data from more than one zone to be consolidated into a single database to
enable global MIS reporting. This minimises the workload on the operational databases for reporting.

The Software Development Kit augments the flexibility that already exists within TI Plus to tailor the
system to a bank’s needs.
In 2.5 the key new features introduced include the following:

• Ability to create a workflow that enables non data capture steps in the event processing to
occur in parallel
• New graphical diagram illustrating the created workflow steps and sequence
• Enable event data enrichment from an external source
• Provide a generic verification step type that obtains a customisable, structured response from
an external system
• Ability to hide fields or make them read only according to the event step context in the UI
control file
• Enable a customised field value to be set from an external source
• Enable control of the batch process from an external process/system
Expanded search mechanism in the Data Model Viewer/DECT application
For further details on the more technical features listed above refer to the Technical Release Notes
and the SDK – set of guides.

Supply Chain Finance

• Enable a supply chain related finance to be linked to a Participation Deal
Roadmap Accelerators
A number of features have been introduced through the roadmap accelerator process. This process
enables features required by the customer base to be brought into the TI Plus roadmap.
• New security access rights in the global application
• Workflow for agreement of client wording of Guarantees
• New event fields to indicate if other events are in progress
• Ability to add correspondence event type descriptions for display in dashboard, master
browser and master summary
• Controlling closure of image windows
Sundry Other Features

• New look to login screen
• FX option contract API
• End of day feature to delete old master records in a processing cycle
• Ability to specify the processing order for incoming bulk message items
• Allow new payment and presenter actions in payments dropdown lists

Chapter 6 FusionBanking Trade Innovation Version 2.6
New Screen Look and Feel
Log In
The Log In screen now looks like this:
General Look

Page Footer
The information that was formerly at the top of the page indicating the zone and processing date are
now shown at the foot of the screen.
Entry Fields
The field size for entry fields has been standardised to the width of the column, rather than varying
depending on the length of the data to be entered in the field. From this:
To this:
Browser Icon
The icon used to browse items such as currency lists has changed from this:

To this:
More Details Icon

The icon used to show more details (and other actions) has changed from this:
To this:
Customer More Details

The icon used to show full customer name and address details or full details of a narrative field has
changed from this:
To this:
Expanded Narrative Icon

The icon used to show full details of a narrative field has changed from this:
To this:
Section Collapse/Expand
The collapse icon for a section has changed from this:

To this:
The expand icon for a section has changed from this:
To this:
Main Title Menu Items

The items in the main title (Print, About etc.) have changed from this:
To this:

Secondary Menu Items

The sub-menus such as those for Release Items in an event have changed from this:
To this:
Messages
The Question, Information, Warnings and Errors messages have changed to this style:


Trade Innovation is designed to support the complex workflow requirements of a trade finance bank
enabling a bank to operate either regionally or globally using a spoke and hub type workflow set up
with interaction with other areas of the bank where required. Within this context the following new
features are provided:
• Allow custom fields to appear anywhere on any event section
• Enable tables to be defined for multi value fields
• Enable TI user to access transaction related information held in external systems through
"Portlets"
• Further improvements to the Workflow Orchestration features of SDK
Allow Custom Fields to Appear Anywhere on any Event Section

Previously, all extra data was contained in its own section at the bottom of the page in the associated
function. Now fields can be added to any section on the page. If the section is not shown, an option is
available to show the extra fields as before.
It is also possible to add new sections to the page relative to existing sections.
For example, the following image shows customised fields in the Basic customer details section in
customer maintenance together with two extra sections of Signatures and Licence details.
Enable Tables to be Defined for Multi Value Fields

It is now possible to define the number of items to show in a list box and a maximum number of items
that can be selected at once.

Transaction Input
This feature allows the bank to define a multi-item select input control for use during transaction input.
The values for the list can be a fixed list or derived from a database table.
For example
DHL = DHL
UPS = United Parcel Service
PF = Parcel Force
DS1 = Incoterms not stated on the commercial invoice

DS2 = Description of goods not per Letter of Credit
When the values are displayed the user is able to select one or more items from the list by clicking on
the item and holding down the control key.
Rules and Documents

A new event field type of List is available to allow these values to be used in Rules. This allows:
• Code values to be compared
• Comparison of contains, does not contain, equals, not equals (order of items is not relevant)
• This allows the list field items to be compared against a list or a string
• For a list :
• If FieldX contains 'A'
• If FieldX contains 'A,C' - i.e. if FieldX contains A and C
• If FieldX does not contain 'D'
• If FieldX does not contain 'E,F' i.e. FieldX does not contain E and F
• For a string - the data is simply treated as a 'plain' string for comparison purposes
For example - If CourierList contains UPS – United Parcel Force

The Event fields are also available for selection in Clauses, Gateway documents or Customer
documents.
The part codes are expanded as follows:

• 'Codes' e.g. A,B,C
• 'Descriptions (comma separated)' e.g. Item A, Item B, Item C
• 'Descriptions (new line separated)' e.g. each item separated by a new line :-
Item A
Item B
Item C
The List field can also be used as part of a table event field.
TF dictionary values can also be defined for these items, however, this does require that the field
code plus its value must be a maximum of 5 e.g. cCCC plus single character x list type value - cABCx
for customised field or ABCDx for a non-customised event field.
Gateway Messages
One or more values can also be provided as part of an incoming Gateway message. For example:
<name>ListField</name>
<value>A,B,C,D</value>
Enable TI User to Access Transaction Related Information Held in

External Systems Through "Portlets"
This feature allows data from other systems to be shown in context within Trade Innovation
customised functions in linked or embedded views, which can be thought of as simplified “portlets”.
Linked or embedded views can be defined in the following contexts:
• Static data extension
• Master and Event data extension
Static Data
When augmenting the customer details in the application data extension.
The following items can be extended:
• Customer details

• TI Customer details
An example of usage is to fetch a signature image from an external system and display the signature
within the customer details.
It is possible to pass parameters (as event fields) such as the customer mnemonic to the embedded
view so that it can provide back the correct context data to display.
For example:
Event Data
The following areas can be extended:
• Master (master summary screen)
• Event
• Event Step

Linked vs Embedded Views

Views can be defined in two ways:
• Linked
• Embedded
A linked view is accessible via a menu option added to the list on the left hand side of the page.
Selecting the menu item will show a page dedicated to the content derived behind the view.
For example:
An embedded view is available on the new type of layout defined with an association. A new section
must be added to the layout, and then an embedded view added to the section. No other controls can
be added to the section. The height of the section is declared by a number of rows.
Data returned from external systems is not stored – it is always retrieved at time of viewing.
Workflow Orchestration Improvements
Warnings and Errors in the Data capture and Verification Steps
A number of enhancements have been made to validation processing. In summary :-

• No validation is performed in the log steps
• Standard data validation is performed at the end of input steps

• Watch list check validation is only performed as part of Watch list checking
• Customisation validation can be invoked as part of data capture or verification phase
• User defined errors and warning can now be generated during the verification phase. These
messages can be conditioned on step type or step phase as appropriate
• The ‘Verify batch’ release item processing is now only called immediately prior to release
• Available balance/Balance credit check and FX contract check are now called as part of
validation during data capture and verification (where configured as services)
• Details of any overridden warnings are then recorded against the actual step that generated
them e.g. Input1, Input2, Review1 or Review 2 and so provides a full audit of what overrides
were made in which steps under ‘parallel’ step processing
• Additionally, any API response warning overridden in one review step is recorded separately
to the same warning received again under a separate review step.
The following table outlines the validation processes included in the review and release steps (where
these have been configured) . If ‘Verify batch’ is configured this is only undertaken on release at the
point where the release items are finalised.
Validation type Review steps (final and non final) Release step
Customisation
User-defined error / warning messages
Available Balance
FX Contract Check/Search
Balance Credit Check
Verify Batch

In the rare eventuality that errors or warnings are encountered e.g. a service failure during the release
step itself, an auto-reject mechanism is provided to allow the user to review and resubmit the event
details again for release.
At this point, the error or warning encountered is presented to the user as a warning to review the
problem. After the issue has been addressed the user can retry by overriding the warning and
continuing again to release.
For audit, the errors or warnings encountered at release are also recorded as informational messages
against the ‘release step’ – visible using the show information tick-box. The rejected ‘release step‘ is
also shown in the step history as rejected for audit purposes.
If the release fails during an interactive user session then errors are logged and the user is returned to
their current step.
If the release fails during batch, SWIFT or gateway then the user is returned to the point in the
orchestration defined in the verification step option.
The verification step is defaulted to the latest main-line review type step prior to release. This can be
changed to any data capture or verification step in the orchestration as required.
Action Items – Actionable and View only

Action items support the review of the main event data. Steps which manage external checks do not
allow event action items to be updated - they can be viewed.
Action items are headed ‘Action items requiring review’ where the items can be actioned.
• Within Log, Input and Exchange type steps:

Action items are headed ‘Action items associated with this event’ where action items are display only.
• Within External review, Watch list check and Review type steps:
Enhanced Step History Tree with View Function

The step history is enhanced to allow the user to drill-down individual steps or multiple steps to the
step status transition details using the [+] function:
Details of activity within a step can be viewed. Pressing [-] returns to the step history view.
• The ‘Last action user’ replaced ‘User’ and indicates the last user undertaking the step.
• Step status actions undertaken by the system are flagged as ** System ** under the last
action user.
A View function is provided for all steps types which have an incoming message associated with them
e.g. exchange or external review

• View- Exchange step

• The overridden warnings against this step.
• The response gateway message (if received).
• View – Watch List Check step shows:
• The recorded WLC status details recorded from the response.
• View – External Review step shows:
• The recorded step level customised response details.
• The response memo details entered by the TI user.
The View function replaces the Incoming Messages History Show all function. Within the step history,
details are also available to view where no incoming message has been received.
SWIFT / Gateway Messages Presented within the Event

In the previous release a transaction event would present to view the most recently received
SWIFT/Gateway message for the event within each step. Within steps which receive a gateway
response, this is appropriate only after the response has been received.
In the current release SWIFT/Gateway messages are shown within a transaction event as a list of
messages, with the option to view any one.

Where there is a response message received for the current step, this is pre-selected to view by
default.
Clicking View shows the details.

Master Browser Changes

The filters within the Master Browser are organised into sections providing results for the Master, an
Event or Active steps within an event.
Screen is split into Master, event and step level filters.
Selecting filters from the top section returns Master level details:
Selecting filters within the section highlighted in orange returns Event level details:
New filter of Event status allows events which are ‘In progress’, ‘Completed’ or ‘Aborted’ to be listed.

Selecting filters in the section highlighted in red returns Active step level details:
Getting Started
User Defined Warnings

As the enhancements to validation now allows validation to be invoked in the verification and review
steps it is important to ensure that user defined warnings or customised errors/warnings relating to
data validation are only issued under the appropriate conditions. Specifically, no previously overridden
warnings should be generated at the point the event is released - as any warnings or errors at this
point will cause the release step to be rejected.
Any existing user defined messages and customisation should therefore be reviewed by the bank to
• Ensure that the ‘release step’ itself does not re-generate previously overridden warnings to
ensure that the release step is not erroneously rejected
• Add further tailoring to condition more specifically when messages are to be generated e.g.
this allows the bank to define separate validation messages required in the data capture steps
and verification steps
Conditions in the Release step
User defined messages and customised errors relating to data validation that are applicable to
previous steps should be excluded from being applied in the ‘release step’ itself by adding the
following rule to any User defined message or used to condition processing in the customised project.
• Event release = false – this means that the message is only generated if the event is not in
release or post release
Any other validation such as available balance checking, FX contract checking or bank’s own
checking will however continue to be performed as normal

• REL – Event release – is Y (true) if the last verification step is completed through to
completion of the event .i.e. if step phase of R or P
• RELD – Event released – is Y (true) if the release step itself is completed through to the
completion of the event (this would include print and post release steps)i.e. if step phase is P
• RELG – Event releasing – is Y (true) if the last verification step is completed up to completing
the release step (this includes Rate fixing, Rate fix authorisation, Release pending and
Release steps) i.e. if in the Release step only

Conditioning user defined messages and validation in event steps
Where the bank has configured ‘sequential’ orchestrations and there is therefore only one active step
then event fields such as the following can be used to condition User defined messages and
customisation validation :-
• Current step ID –sequential orchestration
• Current step description - sequential orchestration
• Current step type – sequential orchestration
• Current step type description – sequential orchestration
Where the bank has configured ‘parallel’ step orchestrations then different rules need to be used to
condition messages as no single step identifier is available. The following events fields can be used
to generate messages at different points in the transaction workflow
• Step Phase code – values are
o C – Create
o D – Data capture
o V – Verification
o R - Release
• Step Phase description
However, as discussed above, as these fields do not identify a specific step, it is necessary to include
an additional rule to stop these messages being issued during the ‘release step’ itself as any warnings
or errors at this point will cause the release step to be rejected
Orchestration Verification Step
The newly introduced orchestration verification step is pre-defaulted to the latest review step in the
main-line of the orchestration template. Please change this to another review or input step if required
in the orchestrations.

Open Account/BPO
Overview
The scope of Financial Supply Chain Management in FusionBanking Trade Innovation is expanded to
cover functionalities to support a bank’s Open Account related services from their back office
perspective. The Open Account products are also designed to support the Bank Payment Obligations
(BPO) and financing requirements.
A BPO is an irrevocable undertaking given by a bank to another bank that payment will be made on a
specified date after successful electronic matching of data according to an industry-wide set of rules.
Therefore, a BPO offers:
• An assurance of payment
• Scope for risk mitigation
• Possible use as collateral for finance
An Open Account transaction in FusionBanking Trade Innovation represents the basic details of the
underlying trade transaction plus one or more BPOs if included. The full scope of the Open Account
transaction data is held in FusionBanking Corporate Channels to facilitate customer facing
interactions and necessary communication with an external transaction matching application (TMA).
Therefore, the full Open Account solution has a dependency on FusionBanking Corporate Channels
and TMA. The TMA functionality is delivered by SWIFT Trade Service Utility (TSU).

Open Account products in FusionBanking Trade Innovation are designed to support the bank’s role as
follows:
Trade Customer Bank TMA BPO BPO Obligor
included
Used
Import Buyer Buyer’s bank No Not applicable
Import Buyer Buyer’s bank Yes No
Import Buyer Buyer’s bank Yes Yes Buyer’s bank
Import Buyer Obligor bank Yes Yes Obligor bank

(other than Buyer’s bank) (other than Buyer’s bank)
(not yet supported) (not yet supported)
Export Seller Seller’s bank No Not applicable
Export Seller Seller’s bank Yes No
Export Seller Seller’s bank/ Yes Yes Buyer’s bank

Recipient bank or/and another Obligor
The Open Account products have no dependency on the following SCF concepts:
• Programme
• Programme anchor customer setup as buyer or seller
• Buyer/seller relationship
Transaction Processing
The Open Account workflow complexity ranges from the bank servicing only their customer’s
instructions to being fully engaged with the external TMA involving other bank(s).
When there is dependency on the TMA, the following events can be initiated by the bank’s customer
or TMA:
• Create – undergo one or more multiple provisional events before finalising
• Amend – undergo two or more events before approval or rejection is established
• Cancel – undergo two or more events before approval or rejection is established
• Payment – undergo two or more events before payment is made or rejected
• The payment events support financing capabilities.
• The bank is able participate their BPO risk with other investors.

The events under Import/Export Open Account product are listed in the following illustrations:

Getting Started
This describes the steps you must take to install the Open Account functionality.
Please refer to Database changes for a full list of changes to the database.
Please refer to Schema changes for the full list of changes.
Full details relating to the installation of this release and details on configuring TI Plus are covered in
the accompanying documents:
• Technical Release Notes - FusionBanking Trade Innovation 26
• Technical Release Notes - DB Changes - FusionBanking Trade Innovation 26
Configuration
The following, new .CSV files must be imported via the FusionBanking Trade Innovation Configuration
application in order to create the new products:
• IOA – Import Open Account
• EOA – Export Open Account
• FIO – Finance Import Open Account
• FEO – Finance Export Open Account
Further references
Please refer to the following documents for further information:
• Supply Chain Finance User Guide – FusionBanking Trade Innovation 26
• System Tailoring User Guide - FusionBanking Trade Innovation 26
• Static Data Maintenance User Guide - FusionBanking Trade Innovation 26
• Security User Guide - FusionBanking Trade Innovation 26
• Financing User Guide - FusionBanking Trade Innovation 26
These are not yet updated to include the Open Account details

Host to Host Deal Templates
Overview
‘Deal template’ functionality was originally introduced to enable banks to create ‘Generic’, or
‘Customer specific’ templates from existing transactions, for certain Trade Innovation products (see
below), so that subsequent transactions of a similar type could be created based upon the data saved
in the template. Each deal template, which is based upon an existing ‘Mapped transaction’ and is
created from full defining events (such Issue ILC, Create Collection Order), is assigned a unique
‘Template identifier’.
Trade Innovation ‘Deal template’ functionality was first introduced at Trade Innovation 2.2.7 which
was prior to the implementation of the Trade Innovation ‘Global Processing’ model. Consequently it
was only possible to create a template for a transaction that operated in a single zone. At Trade
Innovation 2.3.0, the new ‘Global processing’ model was introduced and it has therefore become
necessary to enhance Deal template functionality to fit the global model.
As a result, at FusionBanking Trade Innovation 2.6.0, the ability to create templates at Main Banking
Entity (MBE) level has been introduced, thus allowing banks which operate globally to define
templates of the following, distinct types:
Type Purpose
General A generic template available for use by all branches for the MBE associated with
the behalf of branch of the selected transaction
Branch general A generic template available for use in a specific branch for the MBE
Customer specific A customer specific template available for use in any branch for the MBE
Branch customer specific A customer specific template available for use by a single customer for a specific
branch for the MBE
In addition to the Deal template functionality now being enabled at the Global level, Trade Innovation
has been enhanced as follows.
Where a corporate customer submits details of a new transaction to Trade Innovation but wishes to
base this transaction on a previously created transaction, it is now possible for them to be able to
quote the ‘Deal template identifier’ in the incoming gateway message so that Trade Innovation
automatically creates the new transaction, using the template specified.
This functionality allows customers to request a new transaction based upon a specific deal template,
previously created by the bank, where the bank has advised their customer of the deal template
identifier(s) relevant to them.
Getting Started
Security
Whilst all users are able to create a transaction from a template (based upon their permissions) only
those users who are assigned the following capability (Security/Capability map) are authorised to
‘Manage’ (i.e. Add, Update and Delete) deal templates:
• ManageDealTemplates

Products for which Deal Templates may be Created

Templates may be created from full defining events for the following products:
Trade finance products
• Clean Banker’s Acceptance
• Export Credit Agency Facilities
• Import Guarantees
• Import Letters of Credit
• Import Standby Letters of Credit
• Inward Cash Letters
• Inward Clean Collections
• Inward Documentary Collections
• Outward Cash Letters
• Outward Clean Collections
• Outward Documentary Collections
• Participation Deals
• Reimbursements
• Shipping Guarantees
Clean payment products:

• Outward Customer Payments
• Outward Cheques
• Standing Orders

TI - SLA Dashboard and Master Browser Changes

In the Trade Finance Processing and Clean Payments Processing, SLA Dashboard and Master
browser, the ‘New master’ pane is updated as follows:
Depending on a user’s role and event group, the products to which these are linked and the team(s)
and branch(es) in which they’re authorised to work; each user can create a transaction from a deal
template.
This functionality is accessible via the ‘Create from template’ button which is available in the ‘New
master’ pane in both the TI Plus Dashboard and Master Browser. In addition, users may create a deal
from a template from within a transaction (see below).
Where the ‘ManageDealTemplates’ capability is assigned to a user, an additional ‘Manage Deal

Templates’ menu item is made available in the Master browser and also from within a transaction, via
the ‘Other’ menu item:
Master browser

Transaction input – ‘Create from template’ and ‘Other/Manage as template’ options:
Manage Deal Templates – Adding, Updating and Deleting Templates

Users who are authorised to manage deal templates can add, update, or delete a template if required.
It’s also possible to ‘View’ an existing template via the appropriate button:
As previously stated above, templates may be of one of the following types:

• General
• Branch general
• Customer specific
• Branch customer specific
Users may search for existing templates via the filters provided, depending on their team and the
branches that they’re assigned to work in. The ‘Deal templates results’ table lists existing templates,
based upon the search criteria that is set.

Adding a New Template:

Pressing the ‘Add’ button opens the ‘Master browser – Create template from’ screen. This allows the
user to filter for a specific transaction at the event level, upon which to base the template.
Once the transaction is selected and the ‘OK’ button is pressed, the ‘Add deal template’ screen is
initialised:
The user may then add the unique ‘Template ID’ and a description for the template. They may also
determine the type of template that is required (i.e. General/Customer specific etc.) and whether it is
to be used in a specific branch. Pressing ‘OK’ saves the template and it may then subsequently be
used to create further transactions.

FusionBanking TI Upgrade Benefits

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FusionBanking TI Upgrade Benefits

Uploaded by

Copyright:

Available Formats

Misys FusionBanking Trade Innovation

Upgrade Features & Benefits

Release month and year: November 2014

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits iii

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits iv

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits v

Chapter 1 Enhancements in TI Plus version 1.4.

Chapter 2 Enhancements in TI Plus version 2.2.

Chapter 3 Enhancements in TI Plus version 2.3.

Chapter 4 Enhancements in TI Plus version 2.4.

Chapter 5 Enhancements in TI Plus version 2.5.

Chapter 6 launch of FusionBanking Trade Innovation version 2.6.

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits vi

Chapter 1 Enhancements at TI Plus Version 1.4

There are some additional enhancements to the software's functionality, in particular:

The New Architecture

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 7

For smaller installations, TI Plus web components can be run on a MS IIS/Tomcat or

The New User Interface

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 8

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 9

This fixed area also has:

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 10

• Standby letters of credit

The Adjust event remains exclusive.

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 11

On-line Help Text

Russian Accounting Requirements

Service Level Agreements

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 12

The dashboard is an extremely powerful workflow management tool, providing strong

Teams and the Dashboard

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 13

SWIFT Message Handling

It now allows incoming messages to be mapped into any event.

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 14

Working Capital Finance

Once the facility is established the bank can:

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 15

Sales Ledger Processing

The bank has recorded an invoice it can.

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 16

Chapter 2 TI Plus Version 2.2

The Improved Architecture

System Management (Global Application)

Open Source Components

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 17

• Browser user interface

Session Logging and Debugging

The Customer Gateway

• Corporate front end interfacing

Browser User Interface

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 18

File System Access

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 19

TI Plus now supports:

• Single-cycle charges (see below)

Multiple Charges within a Period

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 20

Customer and Account Retrieval Services

Pre-allocated Reference Numbers

© Misys | FusionBanking Trade Innovation – Upgrade Features & Benefits 21

New Event Fields for Customer Documents

• Import and export guarantees