Claims:CLAIMS
What is claimed is:
1. A method comprising:
executing, through at least one server, a computing platform engine; and
executing, through a data processing device communicatively coupled to the at least one server through a computer network, a component of the computing platform engine, characterized in that:
the component of the computing platform engine automatically inherits a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween, the transactional environment relevant to at least one account with an entity represented through the at least one server, and the at least one account representing a customer of the entity associated with the data processing device,
the computing platform engine determines a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and
the computing platform engine modifies the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the at least one account are segregated at will.
2. The method of claim 1, comprising the data processing device being one of: at least one other server and at least one client device.
3. The method of claim 1, wherein the computing platform engine modifies the domain logic one of: at the at least one server and at the data processing device by way of the computing platform engine component.
4. The method of claim 1, further comprising extracting, through the computing platform engine, another set of criteria from another domain logic of another data processing device communicatively coupled to the at least one server through the computer network to arrive at the set of criteria.
5. The method of claim 1, wherein the set of criteria comprises at least one of: a geographical qualifier, a segment related qualifier, a local regulatory qualifier, and a qualifying account definition that captures at least one of: at least one transactional parameter, account balance related behavior, a length of relationship between the customer and the entity, and a product of the entity consumed.
6. The method of claim 5, comprising the at least one transactional parameter pertaining to at least one of: a credit transaction, a debit transaction, an underlying product of the entity, a processing channel and a transactional scheme.
7. The method of claim 1, comprising distributedly executing the computing platform engine across a plurality of servers as the at least one server.
8. A server comprising:
a memory; and
a processor communicatively coupled to the memory, characterized in that the processor executes instructions associated with a computing platform engine to:
control execution of a component of the computing platform engine through a data processing device communicatively coupled to the server through a computer network,
enable the component of the computing platform engine to automatically inherit a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween, the transactional environment relevant to at least one account with an entity represented through the server, and the at least one account representing a customer of the entity associated with the data processing device,
determine a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and
modify the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the at least one account are segregated at will.
9. A system comprising:
at least one server executing a computing platform engine; and
a data processing device communicatively coupled to the server through a computer network, the data processing device executing a component of the computing platform engine, characterized in that:
the component of the computing platform engine automatically inherits a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween, the transactional environment relevant to at least one account with an entity represented through the at least one server, and the at least one account representing a customer of the entity associated with the data processing device,
the computing platform engine determines a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and
the computing platform engine modifies the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the at least one account are segregated at will.
10. The system of claim 9, wherein the computing platform engine extracts another set of criteria from another domain logic of another data processing device communicatively coupled to the at least one server through the computer network to arrive at the set of criteria.
, Description:
OPTIMIZED SEGREGATION OF AN OPERATIONAL AND A NON-OPERATIONAL BALANCE OF AN ACCOUNT WITH AN ENTITY

FIELD OF TECHNOLOGY
[0001] This disclosure relates generally to transactional computing systems and, more particularly, to optimized segregation of an operational and a non-operational balance of an account with an entity.

BACKGROUND
[0002] A customer of a banking institution may have one or more account(s) with the banking institution. Post the BASEL III accord, it may be important to identify the balance makeup of an account of the customer to determine whether the account includes an operational balance or not. The operational balance may be a monetary amount held at the banking institution by the customer. The monetary amount may be earmarked for operational purposes by the customer based on internal/external rules or a combination thereof. Failure to segregate the operational and the non-operational balance of the account may lead to qualifying the whole account balance as 100% constituting an outflow during calculation of a Liquidity Coverage Ratio (LCR).

SUMMARY
[0003] Disclosed are a method, a server and/or a system of optimized segregation of an operational and a non-operational balance of an account with an entity.
[0004] In one aspect, a method includes executing, through one or more server(s), a computing platform engine, and executing, through a data processing device communicatively coupled to the one or more server(s) through a computer network, a component of the computing platform engine. The component of the computing platform engine automatically inherits a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween. The transactional environment is relevant to one or more account(s) with an entity represented through the one or more server(s), and the one or more account(s) represents a customer of the entity associated with the data processing device.
[0005] The computing platform engine determines a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and modifies the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the one or more account(s) are segregated at will.
[0006] In another aspect, a server includes a memory and a processor communicatively coupled to the memory. The processor executes instructions associated with a computing platform engine to control execution of a component of the computing platform engine through a data processing device communicatively coupled to the server through a computer network, and to enable the component of the computing platform engine to automatically inherit a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween. The transactional environment is relevant to one or more account(s) with an entity represented through the server, and the one or more account(s) represents a customer of the entity associated with the data processing device.
[0007] The processor also executes instructions associated with the computing platform engine to determine a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and to modify the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the one or more account(s) are segregated at will.
[0008] In yet another aspect, a system includes one or more server(s) executing a computing platform engine, and a data processing device communicatively coupled to the server through a computer network. The data processing device executes a component of the computing platform engine. The component of the computing platform engine automatically inherits a domain logic of the data processing device pertaining to a transactional environment of the data processing device based on communication therebetween. The transactional environment is relevant to one or more account(s) with an entity represented through the one or more server(s), and the one or more account(s) represents a customer of the entity associated with the data processing device.
[0009] The computing platform engine determines a set of criteria following the automatic inheritance of the domain logic based on analysis thereof, and modifies the domain logic as applied to transactional information associated with the customer of the entity based on applying the set of criteria thereto such that an operational balance of the customer and a non-operational balance of the customer both represented through the one or more account(s) are segregated at will.
[0010] Other features will be apparent from the accompanying drawings and from the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The embodiments of this invention are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
[0012] Figure 1 is a schematic view of a computing system, according to one or more embodiments.
[0013] Figure 2 is a schematic view of a computing platform engine executing on a server of the computing system of Figure 1, according to one or more embodiments.
[0014] Figure 3 is a schematic view of an optimization engine of the computing platform engine of Figure 2, according to one or more embodiments.
[0015] Figure 4 is a process flow diagram detailing the operations involved in optimized segregation of an operational and a non-operational balance of an account with an entity, according to one or more embodiments.
[0016] Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION
[0017] Example embodiments, as described below, may be used to provide a method, a server and/or a system of optimized segregation of an operational and a non-operational balance of an account with an entity. Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments.
[0018] Figure 1 shows a computing system 100 (e.g., a distributed computing system), according to one or more embodiments. In one or more embodiments, computing system 100 may include a number of servers 1021-N communicatively coupled to one another through a computer network 104 (e.g., a Wide Area Network (WAN), a Local Area Network (LAN) and/or a short range network (e.g., WiFi®, Bluetooth®)). Other forms of computer network 104 are within the scope of the exemplary embodiments discussed herein. In one or more embodiments, computing system 100 may also include a number of client devices 1061-M communicatively coupled to the number of servers 1021-N through computer network 104. As implied above, computer network 104 may, in some embodiments, encompass a wide variety of computer networks.
[0019] In one or more embodiments, computing system 100 may be a traditional computing system with data centers, a cloud based computing system or a hybrid computing system. In one or more embodiments, computing system 100 may provide one or more computing environment(s) through a computing platform 150 thereof. Computing platform 150, as discussed herein, may encompass hardware, software, operating systems, applications including browsers and/or virtualized environments (e.g., virtual machines representing operating systems, virtual storage). Figure 1 shows a computing platform engine 170 (e.g., a comprehensive engine enabling capabilities and functionalities provided through computing platform 150) executing on a server 1021 and components (e.g., computing platform engine components 1702-N; computing platform engine components 1761-M) executing on other servers 1022-N and client devices 1061-M. Examples of client devices 1061-M may include but are not limited to desktop computers, laptops, notebooks, smart devices and mobile phones. Other client devices 1061-M including thin clients are within the scope of the exemplary embodiments discussed herein. Each client device 1061-M may represent a type of a channel for accessing capabilities provided through computing platform engine 170.
[0020] Each server 1021-N discussed above may be a standalone server or a network of servers configured to operate in conjunction with one another and capable of handling large sets of data. “Processor,” as used herein, may also refer to a number of processors configured to operate in conjunction with one another. In one or more embodiments, each server 1021-N may include a processor 1721-N communicatively coupled to a memory 1741-N. Figure 1 shows computing platform engine 170 stored in memory 1741; computing platform engine 170 may be executable through processor 1721. Similarly, computing platform engine components 1702-N and computing platform engine components 1762-M may be stored in corresponding memories to be executed on processors associated therewith.
[0021] Figure 1 also shows data sources 1901-R within computing system 100. In one or more embodiments, data sources 1901-R may include but are not limited to mainframes, Relative Database Management Systems (RDBMS), NoSQL databases, feeds, files, legacy systems, Software-as-a-Service (SaaS), a Management Information System (MIS) and an entitlement data server. In one or more embodiments, data sources 1901-R may be local to one or more servers 1021-N, local to one or more client devices 1061-M and/or external to both the one or more servers 1021-N and the one or more client devices 1061-M. An example data source 1901-R may include account information of authorised users 1921-M; each authorised user 1921-M may be at a client device 1061-M of computing system 100. It should be noted that client device 1061-M (e.g., a common computing resource) may be shared by multiple users and that one authorised user 1921-M per client device 1061-M discussed above is merely for illustrative purposes.
[0022] Other forms of information within data sources 1901-R are within the scope of the exemplary embodiments discussed herein. In one or more embodiments, one authorised user 1921-M may differ from another authorised user 1921-M in terms of roles within an entity or outside thereof. For example, one or more servers 1021-N may be associated with an example entity of a banking institution, and one or more client devices 1061-M may be associated with one or more authorised users 1921-M (e.g., customers of the banking institution, banking personnel). One or more other servers 1021-N may be associated with another example entity of a software service provider associated with computing platform engine 170. One or more other client devices 1061-M may also be associated with one or more other authorised users 1921-M (e.g., sales, pre-sales, testing and/or development team personnel associated with the another example entity of the software service provider).
[0023] Figure 2 shows computing platform engine 170 executing on server 1021, according to one or more embodiments. It should be noted that computing platform engine 170 may interact with computing platform engine components 1702-N executing on one or more other server(s) 1022-N and/or computing platform engine components 1761-M executing on one or more client devices 1061-M, as discussed above with respect to Figure 2..
[0024] Post the BASEL III accord, it may be important to identify the balance makeup of an account of a customer entity (or, customer; e.g., a business entity, a banking institution, a company) to determine whether the account includes an operational balance or not. The operational balance may be a monetary amount held at another banking institution by the customer thereof. The monetary amount may be earmarked for operational purposes by the customer based on internal/external rules or a combination thereof. Thus, server 1021 executing computing platform engine 170 may be associated with a software service provider providing optimized solutions discussed herein. Alternatively, server 1021 executing computing platform engine 170 may be associated with the another banking institution at which the monetary amount is held by the customer. In some cases, the another banking institution may even overlap with the customer.
[0025] In some cases, the account balance makeup may indicate full, partial or non-operational balance. Based on the criteria stipulated by applicable regulatory jurisdictions, different rules may apply to determine a percentage of the operational balance vs. the non-operational balance. This nature of the account balance makeup may enable arrival at an outflow percentage that is one of the elements to determine a Liquidity Coverage Ratio (LCR). The LCR may be obtained by dividing a value (amount) of liquid assets of the customer by a total net cash flow. In some calculations, only highly liquid assets may be considered. As per Basel III requirements, the customer may be required to hold (e.g., at the another banking institution) liquid assets sufficient to fund outflows for 30 days.
[0026] Failure to segregate the operational and non-operational balances may lead to qualification of a whole account balance of the customer as 100% outflow in the calculation of LCR, which may lead to a competitive disadvantage in offerings thereof and/or inefficient handling of liability position by the treasury of the another banking institution thereof. A capability to qualify the account balance makeup of the liability position at will may enable the another banking institution/software service provider to identify behavioral aspect(s) across geographies, segments and/or sectors, base the aforementioned identification on customer insights, craft product solutions therefor and/or optimize usage of balance sheet capital.
[0027] A vast majority of the banking/financial institutions (e.g., including the another banking institution) may create a mechanism to periodically extract transactions of the customer that lead to specific liability positions (e.g., overnight) to apply business intelligence tools (e.g., including spreadsheet analyses) thereto to create requisite data representations (e.g., data cubes). For example, the periodic extraction may be manual and may occur only on a monthly or quarterly basis, thereby causing lost opportunities with respect to the account balance of the customer, mismanagement with respect to the customer and unoptimized product solution(s).
[0028] In one or more embodiments, computing platform engine 170 executing on server 1021 (or, distributedly on one or more servers 1021-N and/or one or more client devices 1061-M) may solve the abovementioned problems through automatically inheriting the transactional environment of a customer 250 (e.g., the customer discussed above) of an entity 220 (e.g., the another banking institution, the software service provider discussed above) and optimizing the process of segregating operational and non-operational balances of the customer account held thereat. Figure 2 shows a customer transactional environment 202 as including another server 1022 communicatively coupled to server 1021, according to one or more embodiments. In one or more other embodiments, the aforementioned customer transactional environment 202 may subsume (or, include) one or more other servers 1022-N and/or one or more client devices 1061-M. Figure 2 shows another server 1022 as part of customer transactional environment 202 solely for purposes of illustration; here, another server 1022 may be associated with customer 250 of entity 220.
[0029] Figure 2 shows computing platform engine 170 as including optimization engine 210 to perform the optimization discussed herein, according to one or more embodiments. As seen in Figure 1, server 1022 that is part of customer transactional environment 202 may execute computing platform engine component 1702 thereon that may interact with a domain logic 262 implemented in server 1022 (or, client device(s) 1061-M as discussed above). In one or more embodiments, domain logic 262 may represent customer transactional environment 202 and may constitute one or more sets of instructions that encodes rules pertaining to creation, modification and storage of data and other criteria and/or data workflows. In one or more embodiments, optimization engine 210 may automatically inherit domain logic 262 of server 1022 by way of computing platform engine component 1702 based on communication therewith.
[0030] In one or more embodiments, optimization engine 210 may update/modify (e.g., at server 1021, at server 1022, depending on the implementation) domain logic 262 to take into consideration geographical/segment related qualifiers that capture rules as per segments and/or local regulatory qualifiers and/or qualifying account definitions that capture criteria such as transactional parameters (e.g., transactional values, transactional volumes, transactional types), account balance related behavior (e.g., periodic (e.g., daily) changes, minimum, maximum, average balance over a timeframe), length of relationship between customer 250 and entity 220, products of entity 220 consumed and availability and usage pattern of facilities (e.g., provided through entity 220). Other criteria are within the scope of the exemplary embodiments discussed herein.
[0031] In one or more embodiments, the transactional parameters discussed above may pertain to credit/debit transactions, underlining products (e.g., of entity 220 used by customer 250; examples of products may include but are not limited to trade, deposits, investments, cash management), processing channels (e.g., manual, host-to-host (H2H), standing instructions) and schemes of transactions (e.g., BACS, CHAPs, wire transfers, SWIFT®, cheque, cash). In one or more embodiments, domain logic 262 may then be programmed/updated/modified by optimization engine 210 by way of computing platform engine component 1702 to assess transactional volumes on a periodic (e.g., daily: minimum/maximum/average values discussed above) basis. In one or more embodiments, the criteria to assess transactional volumes may represent tiered interest rates, banded interest rates or a combination thereof.
[0032] In one or more embodiments, the transactional values discussed above may also be assessed periodically (e.g., daily) on minimum/maximum/average bases and/or based on criteria pertaining to tiered interest rates, banded interest rates or a combination thereof. Additionally, in one or more embodiments, domain logic 282 (and, thereby, the criteria thereof) pertaining to a transactional environment (e.g., a customer transactional environment 204) of another customer (e.g., customer 290) of entity 220 may be automatically inherited by optimization engine 210. Figure 2 shows server 1023 as being associated with customer transactional environment 204 of customer 290. Figure 2 shows banking information 252 as including accounts 2841-P of customer 250 and accounts 2861-Q of customer 290 stored in memory 1741 of server 1021. In one or more embodiments, optimization engine 210 of computing platform engine 170 may perform the optimization processes and modifications discussed herein on banking information 252 specific to customer 250.
[0033] In one or more embodiments, the automatic inheritance of domain logic 282 may enable extraction of criteria associated therewith. In one or more embodiments, if the aforementioned extracted criteria may be optimal or useful with respect to modifying domain logic 262, optimization engine 210 may aggregate the criteria/rules from domain logic 282 and/or other external domain logic(s) (pertaining to customer(s)/non-customer(s) of entity 220), analyze the aforementioned aggregated criteria/rules to arrive at the criteria (refer to Figure 3) with which to program/modify domain logic 262. In one or more embodiments, the criteria (e.g., criteria 304) arrived at may once again pertain to the criteria discussed above with regard to domain logic 262.
[0034] In one or more embodiments, other modules with which to program domain logic 262 via optimization engine 210 may include a decision module (decision module 310; refer to Figure 3) that defines the rules/criteria to qualify the balance makeup of one or more account(s) 2841-P to identify a possible excess amount earmarked as operational balance or an amount that falls below a threshold. In one or more embodiments, these amounts may be based on outflow based criteria (e.g., 25%, 40%, 100%). In one or more embodiments, these other modules may further include an identification module (identification module 302; refer to Figure 3) to identify qualifying customers (e.g., customer 250, customer 290) and accounts (e.g., accounts 2841-P, accounts 2861-Q) thereof. In one or more embodiments, the identification module may apply criteria based on country, segment, sector of operation of the customer and concomitant rules on account balances and transactions. Figure 2 also shows transactions 288 associated with customer 250 and transactions 294 associated with customer 290 stored as part of banking information 252.
[0035] Figure 3 shows optimization engine 210 including modules with which domain logic 262 may be programmed, according to one or more embodiments. Alternately, in one or more embodiments, optimization engine 210 may automatically inherit domain logic 262 and perform modification thereof at server 1021. In one or more embodiments, banking information 252 (daily balance, customer information) may be analyzed by way of identification module 302 of optimization engine 210 to calculate inflow/outflow percentages. In one or more embodiments, criteria 304 discussed above such as segment/geography based qualifiers 304 and account definitions 306 may be applied onto domain logic 262 to reassess banking information 252 based on modifying domain logic 262 (or, performance assessment of banking information 252 at server 1021). Other criteria 304 may include operational balance criteria 308, as shown in Figure 3. In one or more embodiments, criteria 304 may be applied based on analyzing domain logic 262 following inheritance thereof. First, in one or more embodiments, criteria 304 may be determined based on the analysis of domain logic 262 following the automatic inheritance thereof.
[0036] In one or more embodiments, analyses of banking information 252 through identification module 302 and criteria 304 may be filtered through a decision module 310 that applies the aforementioned criteria 304 on the analyzed data. In one or more embodiments, optimization engine 210 may further include an analytics module 312 to provide point-in-time, periodic (e.g., daily) patterns of the account balance makeup (e.g., of accounts 2841-P of customer 250) that are bank based, branch/country based and/or business/customer segment based. For the aforementioned purpose, in one or more embodiments, transactions 288 of customer 250 may be captured and analyzed through one or more modules of optimization engine 210 including analytics module 312.
[0037] In one or more embodiments, analytics module 312 may find further use in pricing, regulatory pricing, stress testing with respect to the operational account balances, trend/behavioral analyses with respect to customer 250 etc. In one or more embodiments, thus, optimization engine 210 may enable segregation of operational and non-operational account balances (e.g., segregated operational balance 392, segregated non-operational balance 394) at will, thereby leading to optimal use of balance sheet capital of customer 250 and enabling entity 220 to craft optimized product solutions to customer 250. Figure 3 also shows interaction of optimization engine 210 with server 1023 to extract criteria 352 pertaining to domain logic 282, according to one or more embodiments. As discussed above, the aforementioned extraction of criteria 352 may enable arrival at criteria 304, according to one or more embodiments.
[0038] Figure 4 shows a process flow diagram detailing the operations involved in optimized segregation of an operational and a non-operational balance of an account (e.g., account(s) 2841-P) with an entity (e.g., entity 220), according to one or more embodiments. In one or more embodiments, operation 402 may involve executing, through one or more server(s) (e.g., server 1021), a computing platform engine (e.g., computing platform engine 170). In one or more embodiments, operation 404 may involve executing, through a data processing device (e.g., server 1022) communicatively coupled to the one or more server(s) through a computer network (e.g., computer network 104), a component (e.g., computing platform engine component 1702) of the computing platform engine.
[0039] In one or more embodiments, the component of the computing platform engine may automatically inherit a domain logic (e.g., domain logic 262) of the data processing device pertaining to a transactional environment (e.g., customer transactional environment 202) of the data processing device based on communication therebetween. In one or more embodiments, the transactional environment may be relevant to one or more account(s) (e.g., account(s) 2841-P) with the entity represented through the one or more server(s), and the one or more account(s) may represent a customer (e.g., customer 250) of the entity associated with the data processing device.
[0040] In one or more embodiments, the computing platform engine may determine a set of criteria (e.g., criteria 304) following the automatic inheritance of the domain logic based on analysis thereof. In one or more embodiments, the computing platform engine may then modify the domain logic as applied to transactional information (e.g., transactions 288) associated with the customer of the entity based on applying the set of criteria such that an operational balance of the customer and a non-operational balance of the customer both represented through the one or more account(s) are segregated (e.g., segregated operational balance 392, segregated non-operational balance 394) at will.
[0041] It may be appreciated that the various systems, methods, and apparatus disclosed herein may be embodied in a non-transitory machine-readable medium (e.g., a hard disk, a Compact Disc (CD), a Digital Video Disc (DVD), a Blu-ray disc®) and/or a machine-accessible medium compatible with a data processing system (e.g., computing system 100, servers 1021-N), and/or may be performed in any order.
[0042] The structures and modules in the figures may be shown as distinct and communicating with only a few specific structures and not others. The structures may be merged with each other, may perform overlapping functions, and may communicate with other structures not shown to be connected in the figures.
[0043] Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.