Systems and methods for global transfers

SYSTEMS AND METHODS FOR GLOBAL TRANSFERS

RELATED APPLICATIONS

This application claims the benefit of, and priority to, U.S. Provisional Application No. 61/513,171, filed July 29,2011.

BACKGROUND

Existing systems and methods for international transfer of funds lack consistency and cannot offer the best rates. For example, there are various channels (internet, call center, branch, etc.) and entities that customers can utilize for international transfers. However, there is typically a lack of ownership and global strategy regarding foreign exchange pricing, resulting in each channel and/or entity essentially managing their own foreign exchange market (FX).

In addition, most international transfer systems only provide real time rates for currencies that are considered supported by a certain treasury. Rates used for unsupported currencies are sheet rates, not live rates, which vary by entity and are not competitive. For transfers involving unsupported currencies, customers are often shown an indicative or sheet rate in a review page; only after the transfer has been executed are the customers shown the final, actual rate. We have determined that this discrepancy between the rates can be considerable, especially for large amounts.

Existing international transfer systems also lack the ability to deal efficiently with outages, during which live or real time rates are temporarily unavailable.

We have developed systems and methods for global transfers that minimize or eliminate such problems, allowing such systems and methods to advantageously provide, for example,

CA 2843397 2019-11-22

WO 2013/019709 ca 02843397 2014-01-27 PCT/US2012/048804 consistent, competitive pricing and/or level of service for transfers involving supported and/or unsupported currencies, at any time and/or any location.

SUMMARY

A global transfers computer system comprises a customer database storing customer information for customers having a plurality of accounts with different entities in different countries; a global customer data computer application electronically receiving the customer information, and storing the customer information in said customer database; a user interface receiving electronic global transfer instructions from the customer; a global transfers computer application, implemented by at least one computer, effecting a global transfer from a first account with a first entity in a first country to a second account with a second entity in a second country responsive to the global transfer instructions, wherein the first and second accounts are linked, and wherein the global transfer is a foreign exchange (FX) transfer or a non-FX transfer; and a foreign exchange computer application, implemented by the at least one computer, obtaining real time rates for FX transfers by connecting to a treasury via a treasury application programming interface, wherein the foreign exchange application interfaces in real-time with a global treasury computer system to obtain FX rates for currencies supported by a global treasury, and wherein the foreign exchange computer application interfaces with a local treasury computer system to obtain FX rates for currencies unsupported by the global treasury.

In some embodiments, the foreign exchange application is configured to generate an electronic request for quote (RFQ) to obtain the FX rates, enabling a single deal per transaction.

In some embodiments, the foreign exchange application is configured to cache the real time rates at a predetermined time and to use the cached rates for weekend transfers.

In some embodiments, the user interface is configured so that the FX rate electronically displayed on a review page is the same a$ the FX rate electronically displayed on a confirmation page, and comprises a final rate.

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

In some embodiments, the user interface is configured so that the FX rate electronically displayed on a review page comprises an indicative rate responsive to a centralized multi base currency configuration, and the FX rate electronically displayed on a confirmation page comprises a final rate.

In some embodiments, the global transfers application i$ configured to electronically provide different rates to different customers based on predetermined criteria. In some embodiments, the predetermined criteria comprise at least one of proposition, global proposition, tier, transfer amount, and transaction volume. In some embodiments, the global transfers application is configured to provide different rates to different customers based on global proposition. In some embodiments, the global transfers application is configured to apply a globally consistent default spread for each proposition.

In some embodiments, the global customer data application is configured to perform a linking validation, confirming that the first and second accounts are associated with the same person, and that the first and second accounts are electronically linked.

In some embodiments, the global transfers application is configured to electronically connect with the global customer data application for a transfer authorization electronically retrieving the linking validation result, and electronically retrieving global compliance screening information for the customer from the central customer database.

In some embodiments, when at least one of the first and second accounts has one or more joint parties for whom there is no global compliance screening information in the central customer database, the global transfers application is configured to electronically connect with a third party system for real time global compliance screening for the joint parties.

In some embodiments, the global transfer instructions comprise electronic instructions to perform at least one of an immediate transfer, a future transfer, a recurring transfer, and a transfer history search.

WO 2013/019709

CA 02843397 2014-01-27

PCT/VS2012/048804

In some embodiments, the global transfers application includes at least one of a computerized customer service representative component and a computerized reconciliation component providing administrative functionality for staff users.

In some embodiments, the global transfers application is configured to perform automated distribution of FX income to the different entities.

In some embodiments, the global transfers application is configured to electronically receive transaction summaries from a plurality of operational and settlement accounts.

In some embodiments, the global transfers application is configured to generate one or more FX income reports reporting FX income by proposition.

In some embodiments, the foreign exchange application is configured to use an electronic request for quote (RFQ) to obtain the FX rates for unsupported currencies using a Foreign Exchange Manager (FXM) computer application, and to use accumulation to apply streamed FX rates for supported currencies using a Foreign Exchange Accumulator (FXA) computer application.

In some embodiments, a computer implemented method for performing global transfers includes electronically receiving customer information, by at least one computer implementing a global customer data computer application: storing the customer information, by the at least one computer implementing the global customer data computer application, in a customer database for customers having a plurality of accounts with different entities in different countries;

receiving, by a user interface, electronic global transfer instructions from the customer; effecting a global transfer from a first account with a first entity in a fust country to a second account with a second entity in a second country responsive to the global transfer instructions, by at least one computer implementing a global transfers computer application, wherein the first and second accounts are linked, and wherein the global transfer is a foreign exchange (FX) transfer or a non-

FX transfer; and obtaining real time rates for FX transfers, by at least one computer implementing a foreign exchange computer application, by connecting to a treasury via a treasury application

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 programming interface, wherein the foreign exchange application interfaces in real-time with a global treasury computer system to obtain FX rates for currencies supported by a global treasury, and wherein the foreign exchange computer application interfaces with a local treasury computer system to obtain FX rates for currencies unsupported by the global treasury.

In some embodiments, the method includes generating, by the at least one computer implementing the foreign exchange computer application, an electronic request for quote (RFQ) to obtain the FX rates, enabling a single deal per transaction.

In some embodiments, the method includes caching the real time rates, by the at least one computer implementing the foreign exchange computer application, at a predetermined time, and using the cached rates for weekend transfers.

In some embodiments, the method includes electronically displaying on a review page, by the user interface, the same FX rate as is electronically displayed on a confirmation page, wherein the FX rate displayed on the review page is a final rate.

In some embodiments, the method includes electronically displaying on a review page, by the user interface, an indicative rate responsive to a centralized multi base currency configuration, and electronically displaying on a confirmation page, by the user interface, a final rate.

In some embodiments, the method includes electronically providing different rates to different customers, by the at feast one computer implementing the global transfers computer application, based on predetermined criteria. In some embodiments, the predetermined criteria comprise at least one of proposition, global proposition, tier, transfer amount, and transaction volume. In some embodiments, the method includes electronically providing different rates to different customers, by the at least one computer implementing the global transfers computer application, based on global proposition. In some embodiments, the method includes applying, by the at least one computer implementing the global transfers computer application, a globally consistent default spread for each proposition.

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2O12/048804

In some embodiments, the method includes performing a linking validation, by the at least one computer implementing the global customer data computer application, confirming that the first and second accounts are associated with the same person, and that the first and second accounts are electronically linked.

In some embodiments, the method includes electronically connecting, by the at least one computer implementing the global transfers computer application, to the at least one computer implementing the global customer data computer application, for a transfer authorization electronically retrieving the linking validation result, and electronically retrieving global compliance screening information for the customer from the central customer database.

In some embodiments, the method includes, when at least one of the first and second accounts has one or more joint parties for whom there is no global compliance screening information in the central customer database, electronically connecting, by the at least one computer implementing the global transfers computer application, with a third party system for real time global compliance screening for the joint parties.

In some embodiments, the method includes receiving, by the user interface, electronic global transfer instructions from the customer, wherein the global transfer instructions comprise electronic instructions to perform at least one of an immediate transfer, a future transfer, a recurring transfer, and a transfer history search.

In some embodiments, the method includes providing administrative functionality for staff users, by the at least one computer implementing the global transfers computer application, via at least one of a computerized customer service representative component and a computerized reconciliation component.

In some embodiments, the method includes perforating, by the at least one computer implementing the global transfers computer application, automated distribution of FX income to the different entities.

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

In some embodiments, the method includes electronically receiving, by the at least one computer implementing the global transfers computer application, transaction summaries from a plurality of operational and settlement accounts.

In some embodiments, the method includes generating, by the at least one computer implementing the global transfers computer application, one or more FX income reports reporting FX income by proposition.

In some embodiments, the method includes using an electronic request for quote (RFQ) to obtain the FX rates for unsupported currencies, by at least one computer implementing a Foreign Exchange Manager (FXM) computer application, and using accumulation to apply streamed FX rates for supported currencies, by at least one computer implementing a Foreign Exchange Accumulator (FXA) computer application.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a diagram of an exemplary architecture for a Global Transfers computer system according to some embodiments of the invention.

Figure 2 shows an exemplary Global View page, according to some embodiments.

Figure 3 shows an exemplary Country Selection screen, according to some embodiments.

Figure 4 shows an exemplary- Transfer Details screen, according to some embodiments.

Figure 5 shows an exemplary Review Details screen, according to some embodiments.

Figure 6 shows an exemplary Confirmation page, according to some embodiments.

Figure 7 shows an exemplary Global Transfers History page, according to some embodiments.

Figure 8 shows an exemplary Global Transfers History page with a list of transfers that meet selected criteria.

Figure 9 shows an exemplary Global Transfers History page with details of a selected transfer. Figure 10 shows an exemplary View Future Transfers page, according to some embodiments.

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

Figure 11 shows an exemplary Accounting Business Flow for supported currencies (local currency to local currency).

Figure 12 shows an exemplary Accounting Business Flow for supported currencies (local currency to foreign currency).

Figure 13 shows an exemplary Accounting Business Flow for supported currencies (foreign currency to foreign currency).

Figure 14 shows an exemplary Accounting Business Flow for supported currencies (local currency to foreign currency, no foreign exchange required).

Figure 15 shows an exemplary Accounting Business Flow for supported currencies (foreign currency to foreign currency, no foreign exchange required).

Figure 16 shows an exemplary Accounting Business Flow for supported currency to unsupported Currency, according to some embodiments.

Figure 17 shows an exemplary Accounting Business Flow for unsupported currency to supported currency, according to some embodiments.

Figure 18 shows an exemplary Accounting Business Flow for unsupported currency to unsupported currency, according to some embodiments.

Figure 19 shows an alternative exemplary Accounting Business Flow for unsupported currency to unsupported currency, according to some embodiments.

DETAILED DESCRIPTION

The present invention relates to improved systems and methods for transfers and/or currency exchanges. In some embodiments, the invention allows customers who have relationships with more than one entity of a bank around the world (e.g., are registered internet banking users having accounts with the Bank in more than one countiy) to advantageously link their personal internet banking system (PIB) profiles from the various entities together. Customers can thereby authenticate to one PIB and then perform single sign on (SSO) to other

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 linked profiles from other entities, for example, for customer accounts in different countries. In what is referred to herein as “Global View” (GV), customers optionally have an aggregated view of all their accounts from all linked PIBs in each PIB, and the view is consistent in each. The PIB profiles are preferably stored in a central reference data store maintaining customer specific information, such as a Global Customer Data Utility (GCDU) as described herein. GCDU receives data feed from entities and stores the data centrally for retrieval. In some embodiments, customer data are stored in a distributed manner.

In some embodiments, the invention provides customers with “Global Transfer” (GT) capabilities, enabling customers to transfer funds between their accounts internationally. Such Global Transfers are also referred to herein as “Me2Me” (M2M) transfers, as they are transfers between accounts held by the same person and optionally associated with PIB profiles that have been linked using Global View. Global Transfers include, for example, FX transactions, which involve foreign exchange (e.g., debit GBP and credit USD), and/or non-FX transactions, which do not involve foreign exchange (e.g., debit GBP and credit GBP). Real time, preferential FX rates are preferably applied to all FX transactions, for supported and/or unsupported currencies.

In some embodiments, a currency is considered supported if a Global Treasury (e.g., Hong Kong) can provide a guaranteed FX rate and the banking system connected to the Global Treasury has accounts established to make and receive payments in that currency. In various embodiments, supported currencies may include, but arc not limited to, one or more of the following standard currencies: AED, AUD, BHD, CAD, CHF, CZK. DKK, EUR, GBP, HKD, JPY, KWD, KYD, MXN, NOK, NZD, PLN, SAR, SEK, SGD, USD, ZAR. In some embodiments, real time rates for supported currencies provided by the present invention are more efficient and/or cost effective than those previously available, because a request for quote model is optionally used, making a single deal per transaction possible.

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

A currency may be considered unsupported for various reasons, such as no liquidity i insufficient demand for trading, local regulation I currency control, etc. In various embodiments, unsupported currencies may include, but are not limited to, one or more of foe following: ( 1 ) currencies that the Global Treasury has no liquidity for (e.g,, BMD, BND, EGP, JOD, LBP, LKR, OMR, PKR, PYG, QAR); (2) currencies tradable only onshore in that country (e.g., IDR, INR, MYR, PHP, VND); (3) currencies unsupported due to local regulation (e.g,, THB); and/or (4) currencies for which the government provides the final rate (e.g., BRL). In some embodiments, real time rates for unsupported currencies were not previously available, and the present invention enables them to be provided.

Supported and unsupported currencies are not limited to the above-described characteristics. In alternative embodiments, other criteria may be used in addition to or instead of those described above for determining whether a currency is considered supported or unsupported by a certain treasury. In addition, the criteria may change over time. In alternative embodiments, supported currencies are currencies managed and/or converted by a global treasury or other treasury that allows such currency to be considered supported, whereas unsupported currencies are dealt directly, managed and/or converted by a local treasury.

Figure 1 is a diagram of an exemplary architecture for a Global Transfers computer system according to some embodiments of the invention.

From a Global Transfers front end, customers can, for example, log in to an entity PIB system and create, change, and/or delete instructions to transfer fonds between accounts held in different entities by the same customer, and/or request a history of transfer transactions. As described in further detail below in connection with the screenshots, in some embodiments, this

WO 2013/819709

CA 02843397 2014-01-27

PCT/US2012/048804 functionality involves sending messages through an Enterprise Application Interface (EAI) to a Global Transfers application, for example using Enterprise Messaging.

In some embodiments, the invention utilizes a Global Transfers application such as the standard Global Direct (GDi). GDi is a commercially available payment warehouse that can connect to a primary Global Treasury (e.g., Hong Kong) and/or a Local Treasury as needed via a Treasury Application Programming Interface (TAPI). In various embodiments, GDi provides one or more of the following fonctions: accept payment instructions from different channels (customer facing and staff facing); quety, book, and finalize discount foreign exchange deals with the Global Treasury; initiate payment instructions to source and destination entities to support cross-border transfers; maintain the history of cross-border transfers; provide email notification to customers on scheduled transfer failures; and/or communicate with GCDU to retrieve Linking Validation (LV) status and Security Compliance Data Matching (SCDM) scanning status of a customer.

In some embodiments, GCDU may perform an automated Linking Validation (also referred to as Same Person Validation), to verify that the PIB profiles of the accounts that the customer is transferring between belong to the same person. The Linking Validation may analyze, for example: Front End (FE) and Customer Service Representative (CSR) updates to SSO, SSO linking notification to GCDU, GCDU customer information retrieval from entity banking system, and/or same person validation using Global Name Recognition (GNR).

In some embodiments, GDi may call GCDU to perform a Transfer Authorization (TA), retrieving the same person Linking Validation result as well as any SCDM scanning results stored in the GCDU database for the customer. SCDM provides a real time watchlist scanning capability to GDi, to perform a global compliance check on the customer using one or more resources such

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 as the U.S. Office of Foreign Assets Control (OFAC) watch list. For joint accounts in which information for one or more of the account holders is not present in GCDU for an authorization check, GDi may interface with SCDM to perform a real time check for those joint parties. GCDU and SCDM are accessible to the Front End and GDi, for example, using Enterprise Messaging via an EA1, or network of EAIs.

In some embodiments, the invention utilizes a group standard application such as Foreign Exchange Manager (FXM) to get rates for FX transactions. In some embodiments, FXM optionally leverages a Request for Quote (RFQ) model, in which all transactions are RFQ based. Each transaction has a single deal, which is direct between the pair of currencies (no double deal, e.g., using an intermediary currency such as USD), Responsive to the FXM RFQ, the TAPI gets risk margins, market rates, rate margins, netting, and/or income management information from the Treasury (e.g., generated by a liquidity engine). Supported currencies are dealt with a Global Treasury (e.g., Hong Kong). Unsupported currencies are dealt directly with a Local Treasury. Sales margin may be determined, for example, either by the Treasury, or in FXM, or in GDi. In some embodiments, different sales margins may be set, for example, by country and/or currency pair, and/or other predetermined criteria. Sales margin/spread can be applied manually through designated personnel, automatically through a software application, or semi-automatically through a computer and/or human intervention.

In some embodiments, FXM is configured with a contingency mechanism to deal with outages (e.g., a Treasury/TAPl may be turned off, a specific currency pair may be disabled due to market volatility or the need to manually update rates, etc.). As rates are being requested, the system periodically caches the rates for all the currency pairs and stores them in FXM. If an Outage occurs, transfers during the outage may be made using the FX rates stored in FXM, not

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 live Treasury rates. In some embodiments, cached rates may be used on weekends as well, optionally adjusted responsive to automated and/or manual analysis of rate trends to assess risk.

In some embodiments, using the RFQ model via FXM provides better, more efficient, more cost effective and/or more accurate rates as compared to what was previously available. For example, when using an application such as Foreign Exchange Accumulator (FXA) to get FX rates, an individual trade is not made for each transaction; rather, the system aggregates customer currency transfers and books deals with the Global Treasury when a predetermined number of transactions have been processed (e.g., about every 15 minutes), using streamed rates that the Global Treasury pushes to the system. In contrast, no accumulation is necessary using the FXM RFQ model according to some embodiments of the invention; the system makes a separate rate request for each transaction, and can create and/or establish a single deal per transaction. Unlike FXA, which streams rates that are typically refreshed about every five minutes, wait times for deals can be significantly shorter using the FXM RFQ model. In addition, unlike FXA, which can only connect to the Global Treasury (and, thus, can only get live rates for currencies supported by the Global Treasury), FXM can connect to Local Treasuries to get real time FX rates for currencies that are not supported by the Global Treasury.

In various alternative embodiments, the FXM RFQ model is used as described above for unsupported currencies, but different options may be used for supported currencies. For example, in one alternative option for supported currencies, the bucket and accumulation features of FXA are moved to FXM and streaming of rates occurs for each currency pair bucket. The transactions accumulated have a single deal per bucket (though the deal ID mapping is individual per transaction). In another alternative option for supported currencies, FXA (implementing bucket and accumulation features) is used for supported currencies, while the FXM RFQ model is used for unsupported currencies, with no changes to FXA or FXM. Sales margin is applied in FXA for

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 supported currencies, and in Treasury for unsupported currencies. Other approaches for obtaining rates for supported and/or unsupported currencies, using FXM, FXA, and/or other applications/methods, may be used.

In some embodiments, FXA is not used for Global Transfers, but provides other capabilities to GDi. For example, in some embodiments, FXA is used for FX order watches. Customers can set up a standing instruction to watch one or more currency pairs and make a deal when a certain threshold is reached. For example, if the USD against GBP rises to a predetermined number or falls to a predetermined number, then buy/sell the currency per the instruction.

In some embodiments, real time rates are available 24 hours a day 5.5 days a week via Global FX Routing. For example, in some embodiments, Hong Kong is used as the Global Treasury. When the market in Hong Kong is not open, another designated treasury may serve as 15 the Global Treasury. For example, before Hong Kong opens, Australia/New Zealand may be used, and after Hong Kong closes, UK may be used, then US, then Australia/New Zealand again. Thus, for example, a deal may be booked in Hong Kong, but have an FX rate from the US Treasury guaranteed by a New York entity. In some embodiments, FXM may store FX rates for use within a predetermined period of time. For example, a customer initiates a transfer at 5 pm

EST, at which time FX rates are requested and stored in FXM. If the customer returns at 7 pm, in some embodiments, the FX rates used will be those stored in FXM, not from the Treasury.

In some embodiments, the customer experience for unsupported currencies is closely aligned to the supported currency experience. For example, even where regulations require 25 countries to use the Local Treasury for FX transfers, the FX rate displayed to the customer on the review and confirm pages should be consistent. The rate displayed is the actual FX rate applied to

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 the transaction if the customer chooses to continue, not an indicative rate. The rate applied is preferably retrieved automatically from the Treasury via the TAPI, with no manual intervention needed to update the rates.

In alternative embodiments, indicative rates (which may have wider spreads than real time rates) may still be used (e.g., where markets are closed and no alternative is available), but may be more efficient, more cost effective, and/or more consistent with final rates, as compared to what was previously available. In some embodiments, instead of each entity setting their own indicative rates, a multi base currency mechanism is used as follows. Each entity configures and maintains indicative FX rates for all the base currencies that they support, for example, in a centralized GDi table. These indicative FX rates are shown on the review page. The system will get the specified indicative pair if the supported currency in the pair is part of the multi base currency configuration. Where a pair is unsupported to unsupported, a default base currency will be applied (e.g., USD).

For example: a transfer between INR and GBP, where the entity has USD, CAD, and GBP as base currencies. If the entity has USD, CAD, and GBP as base currencies, and the unsupported currency is INR, the following pairs should be entered in the multi base currency configuration (e.g., using a GDi CSR Tool): USD-INR, INR-USD, CAD-INR, INR-CAD, GBP-INR, INR-GBP. As the credit currency is GBP, which is in the multi base currency configuration, GDi gets the indicative rate pair INR-GBP from the table. If there is no corresponding pair in the table (e.g., pair is missing), GDi will use USD as the default base currency.

In some embodiments, when markets are closed or an entity bank is not available, that entity cannot be used in the transfer. The customer may be advised, for example, that the transfer

WO 2013/019709

CA 02843397 2014-01-27

PCT/VS2012/048804 will be made at a later time (e.g., next day trade). In some embodiments, weekend transfers are stored in FXM, and cleared when the first market opens.

In some embodiments, the invention provides the ability to use different FX rates and/or fees for different customers (segmented pricing), on an ongoing basis or for a limited period. Customers and/or transactions may be differentiated, for example, based on the customer proposition (group with specified benefits/privileges, e.g., standard Premier, Advance or Retail as offered commercially by HSBC and/or other criteria that may optionally be used), the customer’s tier (e.g., free for high value customers, a fee for lower value customers), the transfer amount (e.g., under/over USS50K), the volume of use (e.g., greater/less than 10 transactions per month), and/or other predetermined criteria. In some embodiments, the rates/spreads to be applied and the parameters for driving the rates (value, volume, etc.) arc globally consistent. In some embodiments, segmented pricing may be used during the week, and a single sales margin (which does not vary by customer/transaction characteristic(s), but in some embodiments may vary by country) will be used during the weekend.

In some embodiments, segmented pricing is utilized by changing the spread depending on the customer proposition. For example, Premier customers may be provided with a better exchange rate (smaller spread) as compared to Advance customers (larger spread). In some embodiments, the spread to apply may be based on the customer’s Global Proposition (e.g., if the customer’s Global Proposition is Premier, even if they are making a transfer between Advance/Retail accounts, the Premier spread will apply). Preferably, there is a globally consistent spread for each proposition across entities. To support this feature, a global default spread for each proposition may be established for all entities, which is managed centrally (cither manually or through an algorithm) to ensure consistency. However, there is flexibility in the system to enable spreads to be defined by country if desired. The spread is preferably common across all

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 currencies supported by that entity. Two propositions (Premier and Advance) are described in this example; however, any number of other propositions may be supported.

Various methods of determining and/or offering FX rates differentiated by proposition may be used. One exemplary process to offer FX rates differentiated by proposition is as follows. GDi maps entity and proposition to a Tier ID. Tier ID is used to access the spreads (e.g., in FXA). An additional message may be used to retrieve Global Proposition from GCDU. When GDi receives the ProvidcTransferlnstruction, it will send a new message to GCDU (Transfer Authorization 3) receiving the Same Person Validation status, and the Global Proposition. If the Same Person Validation status is false (the relationship is unknown), GDi returns the error back to the front end. If the Same Person Validation status is true, GDi will compute the Tier ID based on the debit entity and Global Proposition.

For example:

Debit Entity; Canada

Canada Premier tier ID: 1

Canada Advance tier ID: 2

Customer A Global Proposition: Premier

Customer B Global Proposition: Advance

For Customer A, GDi will send the tier ID = 1 to FXA. FXA returns the rate applying the Canada Premier spread. For Customer B, GDi will send the tier ID = 2 to FXA. FXA returns the rate applying the Canada Advance spread. In some embodiments, for cases where a Global Proposition cannot be identified, the Premier tier is used. On the due date for future-dated or recurring transfers, the same logic is applied (get the Same Person Validation status, and Global Proposition; check the Same Person Validation status; compute the Tier ID; get the rate from FXA), If the Validate messages (debit and credit) return any associated customer, the TA message will be sent to GCDU again for the joint parties.

WO 2013/019709

CA 02843397 2014-01-27

PCT7US2012/048804

In some embodiments, FX income for transfers using supporting currencies is calculated and/or reported by remitting entity, as the FX income belongs to the debit account holding entity. Preferably, FX income distribution (e.g., monthly payments to entities) is automated (e.g., through GDi), and the system is configured to store and maintain payment details (accounts, credit cunency, specific payment details, etc.). In some embodiments, automated email notices of FX income payments are sent (e.g., monthly), and the system is configured to store and maintain contact details.

In some embodiments, the invention provides the ability to create or modify a report of income that can be attributed to foreign exchange transactions, by proposition and/or subsegment. For example, the report can provide information on the foreign exchange income that can be attributed to Premier, Advance, and sub-segment as a result of Global Transfers at the country, region, and global level. A transaction table stores each completed transaction, and has the Global Proposition as one of the fields. A batch to create the reports can separate the transactions based on proposition. In some embodiments, the GDi CSR provides two reports regarding FX income for Global Transfer transactions, with report fields as summarized in Tables I and 2 below.

Table 1. Report Fields - FX Profit Analysis Summary Report

<td> Field Name</td><td> Description</td>

<td> Sending Entity</td><td> Debit entity (3 char country code)</td>

<td> Premier USD FX Markup</td><td> Total of Premier FX Income made. Amount in USD.</td>

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

<td> Advance USD FX Markup</td><td> Total of Advance FX Income made. Amount in USD.</td>

<td> Total USD FX Markup</td><td> Sum of Premier USD FX Markup and Advance USD FX Markup</td>

<td> Number of Premier Transactions</td><td> Premier transactions</td>

<td> Number of Advance Transactions</td><td> Advance transactions</td>

<td> Total Number of transactions</td><td> Sum of Number of Premier Transactions and Number of Advance Transactions</td>

Table 2. Report Fields - FX Profit Analysis Detail Report

<td> Field Name</td><td> Description</td>

<td> Sending Entity</td><td> Debit entity (3 char country code)</td>

<td> Receiving Entity</td><td> Credit entity (3 char country code)</td>

<td> Premier USD FX Markup</td><td> Total of Premier FX Income made. Amount in USD.</td>

<td> Advance USD FX Markup</td><td> Total of Advance FX Income made. Amount in</td>

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

<td></td><td> USD.</td>

<td> Total USD FX Markup</td><td> Sum of Premier USD FX Markup and Advance USD FX Markup</td>

<td> Number of Premier Transactions</td><td> Premier transactions</td>

<td> Number of Advance Transactions</td><td> Advance transactions</td>

<td> Total Number of transactions</td><td> Sum of Number of Premier Transactions and Number of Advance Transactions</td>

Figures 2-10 show exemplary customer facing screen shots for Global Transfers, according to some embodiments of the invention. Front End (F/E or FE) application portlets are provided to entities for integration into their local PIB to provide a global consistent look and feel. Externalized content and configuration on the FE can provide for any local variations (e.g., language translations).

Figure 2 shows an exemplary Global View landing page. In addition to being able to create/change/delete instructions to transfer funds between their accounts held in different 10 entities, customers can, for example, schedule future dated and recurring transfers, and request a history of transfer transactions.

Figure 3 shows an exemplary Country Selection screen. When the customer selects the Global Transfers option on the Global View page, a Country Selection screen is presented. The

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 country selection portlet retrieves a list of customer-linked profiles from a regional SSO server, and then displays the countries that the customer has linked and are available for global transfers (e.g., in a dropdown menu). The customer selects the country they want to transfer money From and To from the dropdowns. The country selection portlet will then send a message to GDi via

EAI to ensure that the two countries are transactable, and receive a result as to whether the customer can proceed with the transfer. Clicking “Next Step” will direct the customer to a Transfer Details screen. Preferably, the transfer is made from the debiting entity, so if this is not the PIB that the customer is logged on to, clicking “Next Step” may redirect them to the PIB they are transferring from. This may be done using SSO, so there is no need for the country to re- authenticate.

Figure 4 shows an exemplary Transfer Details screen. Messages are sent from the front end to the Debiting (Dr) Entity Banking System / Back Office System (BOS) and Crediting (Cr) Entity BOS before displaying the Transfer Details screen to retrieve a list of accounts that the customer can select for the Global Transfer. The transfer portlet will populate the account lists. The front end then sends a message to GDi for fields that can be pre-populated into the Transfer Details page. These fields may include, for example, email address, email contact preference, and/or any entity-specific fields (e.g., reason for transfer) submitted by the customer in previous transactions. After collecting the information, the transfer portlet will present the Transfer Details page to the customer for transfer details entry. The customer selects the accounts they want to transfer From and To, the Currency, Amount, and whether they want to do an immediate or future-dated transfer. Some countries may also require a Reason for Transfer; if so, a dropdown box with the appropriate data may be provided.

Figure 5 shows an exemplary Review Details screen. Once the customer has entered and submitted the transfer details, the transfer portlet will send a message containing the transfer

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 instruction to GDi. On receipt of the transfer request, GDi will send messages to the Debiting Entity BOS and Crediting Entity BOS to perform transfer pre-transaction validation. The message may be sent as a bundled message from GDi to EA1. GDi will send a Transfer Authorization message to GCDU to retrieve the transfer validation status of the transacting customer and associated parties to the account. When GCDU does not contain the transfer validation status of the requested parties, GDi will send a message to SCDM to perform real time scanning against these profiles. Based on the returned SCDM result, GDi will determine whether the transaction should proceed. If so, the customer is directed to the Review Details page to review the transfer details before confirming. An exchange rate (for FX transfers) and any error messages are included on the Review Details page.

Figure 6 shows an exemplary Confirmation page. Once the customer confirms the details of the transfer, the transfer portlet will send a message to GDi via EAI to complete the transfer. For immediate transfers, GDi will execute the transfer, and the customer is presented with the Confirmation page. For future-dated or recurring transfers, GDi will capture the instruction and present acknowledgement details. For transfer processing, GDi will send a message to the Debiting Entity BOS to execute a transaction that debits the Customer Account and credits the entity’s Operational Account. On successful debit, GDi will send a second message to the Crediting Entity BOS to execute a transaction that debits the entity’s Operational Account and credits the Customer Account.

Figure 7 shows an exemplary Global Transfers History page. When the customer selects this option from the Global View page, the front end sends a request to regional SSO to get linked identities, and then displays the countries that the customer has linked and are available for global transfers (e.g., in a dropdown menu). It also sends a message to each of the BOS to get a list of accounts to display in the dropdown. The customer chooses the transfers he/shc wants to search

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 for, for example by specifying the From Country/Territory, From Account, and Date Range. When the customer selects “Search Transfers History” a message is sent to GDi to retrieve the transfer list and the customer is presented with a list of transfers that meet the criteria selected, as shown, for example, in Figure 8. The customer can click on each of these transfers to obtain more details of the transfer. If the customer clicks on one of the transfers on the list a message is sent to GDi to retrieve more details about the transfer, and the details are presented to the customer, as shown, for example, in Figure 9.

Figure 10 shows an exemplary View Future Transfers page. When the customer selects this option from the Global View page, similar to Transfer History, the front end sends a request to regional SSO to get linked identities, and then displays the countries that the customer has linked and are available for global transfers (e.g., in a dropdown menu). It also sends a message to each of the BOS to get a list of accounts to display in the dropdown. The customer chooses the transfers he/she wants to search for, for example by specifying the From Country/Territory, From Account, and Date Range. When the customer selects “Search Future Transfers” a message is sent to GDi to retrieve the transfer list and the customer is presented with a list of transfers that meet the criteria selected. The customer can click on each of these transfers to obtain more details of the transfer.

Future dated or recurring transfer instructions can also be updated. The front end portlet will send a message to GDi, which will capture the amended instruction, validate the details, and return the details to the portlet for the customer to review. When the customer confirms the changes, the front end portlet will send a message to GDi to proceed with the changes, and an acknowledgement will be returned the customer that GDi has applied the changes. For cancellations, the customer selects a future dated or recurring transfer and submits. The front end portlet will send a message to GDi, which will remove the selected future transfer instruction

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 from its scheduler. Results of the cancel operation will be returned to the portlet for acknowledgement to the customer.

In some embodiments, an FX calculator page may be provided. The front end portlet will send a message to GDi to request a list of currencies that the customer can select for foreign exchange rate calculation, and the retrieved currency list will be populated into From and To currency lists accordingly. One the customer has selected the currencies and the amount to be converted, the portlet will send a message to GDi to calculate a conversion amount. The result will be returned the portlet and displayed to the customer.

GDi may also provide a variety of staff facing functions. For example, in some embodiments, GDi has a CSR Tool that provides customer service representatives or other designated personnel the functionality to view, amend, and/or delete a customer transfer in the GDi system. The CSR Tool may also allow staff to specify currency cut-off periods, holidays, and/or maintenance periods for their respective entities, during which GDi may not enact transfers. The CSR Tool may also allow staff to maintain business rules, for example: a global daily limit rule (setting a predetermined transfer limit value per customer per day), a per customer limit rule (less than or equal to the global daily limit), entity level limit rules (setting a predetermined limit on volume and/or amount of transfers per a predetermined time period), a per transaction limit rule (set at the entity level; any single transfer from that entity cannot exceed this limit), a duplicate check rule (performing a check for duplicate transfer instructions within a predetermined time frame, e.g., 24 hours, 3 minutes, etc.), a maximum payment account limit role, a number of senders per account limit rule, etc. Due to local government regulations in different entities, other local limits may be applicable (e.g., total inbound transactional limit of USD9000 per month in Brazil).

WO 2013/019709 CA 02843397 2014-01-27 PCT/US2012/048804

In some embodiments, another staff facing application (e.g., eCare) provides customer service representatives or other personnel the functionality to administer customer profiles and perform profile linking and/or de-linking for a customer. Outstanding scheduled transfers may be displayed during the profile de-linking process.

From the customer perspective, Global Transfers are real time, or near real time, as the accounts are debited and credited immediately, similar to domestic PIB transfers. In some embodiments, for real time debiting and crediting of customer accounts for Global Transfers, operational accounts (suspense accounts) are established in each entity for each currency that the entity offers the real time debiting and crediting service. These accounts are labeled in Figure 1 as “GT Operational Accounts” of the Debiting (Dr) Entity and Crediting (Cr) Entity. The operational accounts accept real time debit and credit postings where the contra posting is to a customer account. For example, when a customer confirms a transaction, there is a real time debit from the customer’s account with the Dr Entity to a Dr Entity Operational Account, and a corresponding real time credit to the customer’s account with the Cr Entity from a Cr Entity Operational Account (these steps are labeled 1 and 2 in Figures 11-19, discussed further below). In some embodiments, the credit portion will not be initiated until confirmation has been received from the sending entity that the customer’s account has been debited. Preferably, there is no limit on the value, volume, or frequency of the real time or online postings. The operational accounts may have an intra-day debit balance without any manual intervention to approve postings.

In addition, debit and credit currency accounts (settlement accounts) are established (one per currency) in the Global Treasury country' (e.g., Hong Kong). These accounts are labeled in Figure 1 as “Dr CCY Accounts” and “Cr CCY Accounts,” and are not entity specific. In some embodiments, for Treasury Settlement, the debit and credit currency accounts are debited and

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 credited by the Global Treasury on a deal level. In some embodiments, the Treasury Settlement may be a batch settlement containing all the transactions since the previous settlement.

The debit and credit currency accounts may also be used to makc/receive payments to/from the entity operational accounts for settlement. In some embodiments, transferred funds do not move internationally during the transfer itself; settlement of the debit and credit entity operational accounts is initiated by GDi at a predetermined later time (e.g., at the end of the entity’s day). Settlement is preferably per currency, per entity, and is a batch settlement containing all the transactions since the previous settlement. Settlement may be via inbound or outbound bulk or batch wire payment (e.g., MT103 or MT103+, which are standard message types established by the Society for Worldwide Interbank Financial Telecommunication (SWIFT) to make payments to a bank/entity in another country). In some embodiments, payments are supported by straight-through processing (STP). Payments are preferably made on the same business day as the real time postings; however, as wire rooms typically close before the end of the entity’s business day, there may be an overnight balance. In some cases, due to time differences, inbound payments to clear a debit balance on an operational account may not be received until the next business day.

Figures 11-19 show exemplary Accounting Business Flows for different types of Globa) Transfers. Cross-border transfers can be made from to/from a local or a foreign currency. As used herein, local currency (LCY) means that the currency of the account is the legal tender of the country in which it is domiciled (e.g., a CAD account with a Canadian entity). Foreign currency (FCY) means that the currency of the account is not the same as the country in which it is domiciled (e.g., a GBP account with an Australian entity). Cross-border transfer types may include, for example:

LCY to LCY (e.g., CAD account in Canada to a GBP account in UK);

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804

LCY to FCY (e.g., CAD account in Canada to a GBP account in Australia); and FCY to FCY (e.g., CAD account in France to a GBP account in Australia).

In some cases, cross-border transfers may have No FX Required (e.g., CAD account in Canada to a CAD account in Hong Kong, or USD account in Canada to a USD account in Hong Kong).

Referring to Figure 11, an excmplaty Accounting Business Flow is shown for a transfer from local currency to local currency, in which a foreign exchange was made. (Here, both currencies are supported, and the FX deal may have been made, for example, as described above, using real time rates from the Hong Kong Treasury, optionally obtained by FXM RFQ. If one or both of the currencies in the pair was unsupported, the FX deal may have been made using real time rates from one or more Local Treasuries, obtained by FXM RFQ.) In Figure 11, the entity GT Operational Accounts in Figure 1 are labeled as GP (Global Premier) Transfer Suspense Accounts, and the Dr/Cr CCY Accounts are labeled as Settlement Accounts. As described above, steps 1 and 2 (labeled “Real time Fund Movement” in Figure 1) are preferably performed in real time, or near real time (in the same unit of work, in system terms). These are the Online Enact steps that begin the transaction. Steps 3a and 3b (Debit Settlement and Credit Settlement, respectively; each labeled “Batch Settlement” in Figure 1) may be performed at a predetermined later time (e.g., at the end of the day). For Treasury Settlement, the Debit and Credit Settlement Accounts may be debited and credited by the Treasury on a deal level.

In some embodiments, if the transfer involves an unsupported currency that can only be traded onshore in that country, steps 1 and/or 2 will include a local FX from the unsupported currency to a base currency that is supported. Figures 16-17 show exemplary Accounting Business Flows for supported currency to unsupported currency, and unsupported currency to supported currency, respectively, under this scenario. In Figures 16-17, both currencies are local

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 currencies (GBP in UK and MYR in Malaysia). MYR can only be bought onshore. Local FX to supported currency uses USD as the base currency. In alternative embodiments, the base currency may be GBP instead of USD, in which case no FX would be required in Hong Kong. Figures 1819 show two alternative exemplary Accounting Business Flows for unsupported currency to unsupported currency under this scenario, the first using the same base currency, and the second using different base currencies. Other accounting methods may be used.

In some embodiments, as part of the reconciliation process, each operational account and settlement account may generate a message (e.g., MT940, established by SWIFT for the paperless transmission of account information) at the end of the day to report its transaction activities and/or balance information. In some embodiments, an electronic account statement is received by a GDi Reconciliation Tool from each banking system for each of its accounts (see “TXN Summary” in Figure 1). For example, at the end of the day, each entity generates an outward MT940 to GDi to report the transaction activities of each of its operational accounts. At the end of the day in Hong Kong, Hong Kong generates an outward MT940 to GDi to report the transaction activities of each of its settlement accounts. Bulk or batch posting items (e.g., net payments to/from the entity operational accounts) can be effectively replaced with the underlying customer transfers using identification and matching based, for example, on reference number and amount. Staff can use the GDi Reconciliation Tool to view and track any outstanding transactions that have not yet been reconciled. In various embodiments, the reconciliation tool may feature one or more of the following: ageing analysis, manual matching, partial matching, audit trails, input reports, and/or dual control.

It is to be understood that the invention is not limited in its application to the details of construction and to the arrangements of the components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced

WO 2013/019709

CA 02843397 2014-01-27

PCT/US2012/048804 and carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein are for the purpose of description and should not be regarded as limiting.

As such, those skilled in the art will appreciate that the conception, upon which this disclosure is based, may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out the several purposes of the present invention. It is important, therefore, that the invention be regarded as including equivalent constructions to those described herein insofar as they do not depart from the spirit and scope of the present invention.

For example, the specific sequence of the described process may be altered so that certain processes are conducted in parallel or independent, with other processes, to the extent that the processes are not dependent upon each other. Thus, the specific order of steps described herein is not to be considered implying a specific sequence of steps to perform the process. In alternative embodiments, one or more process steps may be implemented by a user assisted process and/or manually. Other alterations or modifications of the above processes are also contemplated. For example, further insubstantial approximations of the process and/or algorithms are also considered within the scope of the processes described herein.

In addition, features illustrated or described as part of one embodiment can be used on other embodiments to yield a still farther embodiment. Additionally, certain features may be interchanged with similar devices or features not mentioned yet which perform the same or similar functions. It is therefore intended that such modifications and variations are included within the totality of the present invention.