Sign In to Follow Application
View All Documents & Correspondence

Account Management System

Abstract: Systems and methods for managing a bank account are described herein. The method includes receiving a request for associating a secondary balance to the bank account through an electronic interface (110), wherein a value of the secondary balance is greater than a value of a primary balance associated with the bank account. The method further includes computing a time bound amount based at least on the secondary balance and the primary balance and providing a secondary rate of interest on the time bound amount for a user defined period, wherein the secondary rate of interest is higher than a primary rate of interest levied on the primary balance.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
02 February 2011
Publication Number
32/2012
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application

Applicants

TATA CONSULTANCY SERVICES LIMITED
NIRMAL BUILDING, 9TH FLOOR, NARIMAN POINT, MUMBAI-400021, MAHARASHTRA, INDIA

Inventors

1. SHAHU VARUN
TATA CONSULTANCY SERVICES LTD., SYNERGY PARK SEZ UNIT 26, GACHIBOWLI, HYDERABAD 500 019, ANDRA PRADESH, INDIA

Specification

FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention'.
ACCOUNT MANAGEMENT SYSTEM
2. Applicant(s)
NAME NATIONALITY ADDRESS
TATA CONSULTANCY Nirmal Building, 9th Floor, Nariman Point,
Indian
SERVICES LIMITED Mumbai-400021, Maharashtra, India
3. Preamble to the description
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.

ACCOUNT MANAGEMENT SYSTEM
TECHNICAL FIELD
The present subject matter relates, in general, to banking and, in particular, to
systems and methods for management of a bank account within a banking environment.
BACKGROUND
Financial institutions, retail banks in particular, allow customers or account
holders to store their funds in bank accounts, such as savings accounts. Such accounts generally require the account holder to maintain a certain monthly or quarterly minimum balance of funds. The minimum balance is assumed by the retail banks as a secured amount and available for various purposes, e.g., revolving liquidity, using as float funds, extending as loans and advances to retail and wholesale account holders, and investing in government, mutual and insurance bonds. In lieu of the secured amount, the banks offer returns to the account holder at a specific rate of interest. Further, an account holder may qualify for various services based on the maintenance of the minimum balance, for example, loans, credit cards, etc. Accounts that fail to meet the minimum balance requirement are generally subjected to maintenance charges.
SUMMARY
This summary is provided to introduce concepts related to management of a
bank account, which is further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.

In one implementation, the method includes receiving a request for associating a
value of a secondary balance to the bank account through an electronic interface, wherein the value of the secondary balance is greater than a value of a primary balance associated with the bank account. The method further includes computing a time bound amount based at least on the secondary balance and the primary balance and providing a secondary rate of interest on the time bound amount for a user defined period, wherein the secondary rate of interest is higher than a primary rate of interest levied on the primary balance.
BRIEF DESCRIPTION OF THE DRAWINGS
The detailed description is described with reference to the accompanying figures.
In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and components.
Fig. 1 illustrates an exemplary account management system to manage a bank
account, in accordance with an embodiment of the present subject matter.
Fig. 2 depicts an exemplary method to manage in a bank account, in accordance
with an implementation of the present subject matter.
Fig. 3 depicts an exemplary method to determine whether a transaction is
allowed, in accordance with an implementation of the present subject matter.
DETAILED DESCRIPTION
Typically, customers of a financial institution, such as a retail bank, store their
funds in low interest accounts, for example checking account or savings account, and invest their funds in high interest accounts, such as fixed deposit accounts. The low interest

accounts, such as savings accounts, allow a customer or an account holder to avail a low rate of interest, say 3%, on their funds as long as he/she maintains a minimum balance of funds stipulated by the bank. Accounts that fall below the bank-stipulated balance can be levied with penalties. Thus, many account holders or account holders tend to maintain more funds in the low-interest accounts than is needed. As a result, the account holder fails to make income out of the extra funds that can be transferred instead to high interest accounts, such as fixed deposit accounts.
The transfer of such funds to other higher interest accounts generally requires
the account holder to periodically monitor the low interest account and actively participate in the transfer transaction. This level of attention is often burdensome on the account holder and results in sub-optimal allocation of monetary assets. Further, should the account holder accidentally transfer a lot of funds to the higher interest account or experience an unexpected withdrawal of the funds from the low-interest account, re-transferring funds from the high interest account to the low interest account involves payment of fee and unnecessary paperwork. Additionally, the high interest accounts, such as fixed deposits, etc., generally suit either medium or long term investments and may not be a good option for account holders who like to have liquid assets at their disposal. While there are a number of short term credit sources available for such account holders, there exist no short term investment options suited to all kinds of account holders.
From the perspective of banks, many account holders have funds far exceeding
the bank-stipulated minimum balance. However, since the account holders have not committed the excess of funds to the bank, the banks may not be in a position to invest such funds elsewhere.

The embodiments described herein provide for systems and methods to
efficiently manage a bank account and use the existing financial resources, such as funds, to the advantage of both the account holder and the financial institutions. In one implementation, an account management system logically divides the total funds in a single account, such as a savings account, into a time bound amount and an on-demand amount. Each of the two amounts is associated with a different rate of interest. As will be appreciated by a person skilled in the art, the incremental amount, also referred to as the interest earned, will be based on the rate of interest and the time period for which a given predefined amount remained deposited in the account.
In one implementation, the time bound amount may be associated with a high
interest rate comparable to the interest rate disbursed on fixed deposit accounts, say 8%, while the on-demand amount earns a low interest rate say about 3%. The time bound amount can be the difference between a bank-stipulated primary balance and a secondary balance. The secondary balance may either be defined by an account holder or may be associated to an account based on a trend noticed over a period of time, indicating that an account holder tends to keep funds over and above the primary balance. On the other hand, the on-demand amount is the difference between the total funds in the account and the time bound amount. For example, in an account having total funds of INR 50,000, a secondary balance of INR 25,000, and primary balance of INR 5000, the time bound amount is INR 20,000 and the on-demand amount is INR 30,000.
With such a logical segregation of accounts, the account holder gets the
advantage of being able to make short term or long term investments without having to create

separate accounts. Thus, such an account management system provides the account holder
properties of both a high interest account and low interest account, but on a single account.
Additionally, since this service may be automatically renewed, the account
holder does not need to make a conscious effort to track his/her funds and channel the extra funds towards investments. Also, unlike fixed deposit accounts, the account management system does not associate a stringent lock-in or maturity period with the time bound amount and allows for emergency withdrawals with minimal risk. Further, greater flexibility is offered to the account holders as the secondary balance may be defined by the account holder. Additionally, the account management system allows the financial institutions to invest the time bound amount, which was not committed earlier by the account holder, and to generate more revenues through loans and advances.
Further, in one implementation, the exemplary system may also associate a
transaction count with the account to keep track of the number of times an account holder extracts money from the time bound amount via a withdrawal transaction. If the transaction count exceeds a predetermined number of counts, say 3, the system may either reject a transaction or allow the transaction by levying a maintenance fee. Alternatively, the system may also provide a buffer time period for the account holder to replenish the account within the buffer time period and avoid such penalties and to continue to receive higher rate of interest on the time bound amount. However, if the account holder fails to replenish the account during the buffer time period, additional penalty may be imposed.
While aspects of described systems and methods for the account management
system can be implemented in any number of different computing systems, environments,

and/or configurations, the embodiments are described in the context of the following exemplary system(s).
Fig. 1 illustrates an exemplary network environment 100 implementing an
account management system 102, according to an embodiment of the present subject matter. In said embodiment, the network environment 100 includes the account management system 102 configured to manage one or more accounts of an individual within a financial institution, for example a retail bank. In one implementation, the account management system 102 may be included within an existing banking system. Further, the account management system 102 may include mainframes, personal computers, laptops, personal digital assistants (PDAs), etc. It will be understood that the account management system 102 may be accessed by account holders through computing devices or applications residing on computing devices, such as online banking applications, automatic teller machines (ATMs), mobile banking applications, interactive voice response machines, etc. In the illustration, the account management system 102 is coupled to a portable computer 104-1, an ATM 104-2, and a handheld device 104-3 (collectively referred to as computing devices 104) through the network 106 for allowing account holders to access their accounts.
The network 106 may be a wireless network, wired network or a combination
thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and such. The network 106 may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example,

Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol
(TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other.
In one implementation, the account management system 102 includes a
processor(s) 108, input-output (I/O) interface(s) 110, and a memory 112. The processor(s) 108 are coupled to the memory 112. The processor(s) 108 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor(s) 108 are configured to fetch and execute computer-readable instructions stored in the memory 112.
The I/O interface(s) 110 may include a variety of software and hardware
interfaces, for example, a web interface allowing the account management system 102 to interact with the computing devices 104. Further, the I/O interface(s) 110 may enable the account management system 102 to communicate with other computing devices, such as web servers and external repositories. The I/O interface(s) 110 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and wireless networks such as WLAN, cellular, or satellite. The I/O interface(s) 110 may include one or more ports for connecting a number of devices to each other or to another server.
The memory 112 can include any computer-readable medium known in the art
including, for example, volatile memory (e.g., RAM), and/or non-volatile memory (e.g., EPROM, flash memory, etc.). In one embodiment, the memory 112 includes program module(s) 114 and program data 116. The program module(s) 114 further include an association module 118, a determination module 120, an analysis module 122, and other

module(s) 124. It will be appreciated that such modules may be represented as a single
module or a combination of different modules. Additionally, the memory 112 further includes
program data 116 that serves, amongst other things, as a repository for storing data fetched
processed, received and generated by one or more of the program module(s) 114. The
program data 116 includes, for example, association data 126, determination data 128,
analysis data 130, and other data 132. In one embodiment, the association data 126, the
determination data 128, the analysis data 130, and the other data 132, may be stored in the
memory 112 in the form of data structures. Additionally, the aforementioned data can be
organized using data models, such as relational or hierarchical data model.
In one implementation, the account management system 102 maintains the
information pertaining to one or more accounts, such as savings accounts. The accounts within a financial institution, such as a retail bank, global and local banks, community banks, etc., are owned by an account holder. The information may be stored in the other data 132 or in an external repository associated with the account management system 102. Such bank accounts, interchangeably referred to as accounts hereinafter, are characterized by a primary balance. The primary balance may be an annual, quarterly or daily minimum balance of funds that an account holder is expected to maintain. However, as will be appreciated, in certain cases, the total funds in the account of one or more account holders are typically greater than the primary balance.
In one implementation, the analysis module 122 monitors the account for a
pre-determined time duration, for example, six months to determine whether the total funds in the account are over and above the primary balance. If the total funds exceed the primary balance at a lapse of the pre-determined time period, the analysis module 122 generates an

indication for the account holder based on which the account holder may provide a value of a secondary balance. In said implementation, the association module 118 associates the secondary balance with the account. Alternatively, the association module 118 may, after generation of the indication, automatically select the value of secondary balance from a predefined list of values of the secondary balance, and subsequently associate the secondary balance with the account. It should be noted that the secondary balance is over and above the primary balance stipulated by the financial institution. Further, the maximum value of the secondary balance may be restricted to a pre-defined amount.
Once the secondary balance is associated with the account under consideration,
the association module 118 may also assign a secondary time period, which is characterized by a start date and an expiry date. The secondary time period may be defined by the account holder or the financial institution or both.
Based on the secondary balance, the determination module 120 computes a
time bound amount and an on-demand amount. In one implementation, the determination module 120 computes the time bound amount by evaluating the difference between the secondary balance and the primary balance. In a similar manner, the determination module 120 may also compute the on-demand amount by calculating the difference between the value of total funds in the account and the time bound amount. Further, once the time bound amount and the on-demand amount are obtained; the determination module 120 subjects a secondary rate of interest on the time bound amount and a primary rate of interest on the on-demand amount. It will be understood that the primary rate of interest is the rate of interest earned on low interest accounts, say 3%, while the secondary rate of interest, in one implementation, is comparable to the rate of interest offered on typical high interest accounts, for example, fixed

deposit accounts and time deposit accounts. In an example, the secondary rate of interest may be 8%.
Furthermore, the determination module 120 also disburses an incremental
amount based on the aforementioned rate of interest. It will be appreciated that the incremental amount, also referred to as the interest earned, will be based on the rate of interest and the time period for which a given predefined amount remained deposited in the account.
After the expiry date of the secondary time period, the time bound amount
earns the primary rate of interest similar to the rate of interest earned on the on-demand amount.
In another implementation, the determination module 120 may automatically
update the secondary time period after the expiry date so that the account holder continues to receive the secondary rate of interest on the time bound amount. Such an automatic updation may be stopped by the account holder if he so desires.
Further, once the total funds are segregated into the time bound amount and the
on-demand amount, the analysis module 122, in one implementation, analyzes whether or not the account holder can perform a transaction based on an availability of funds in the account. For example, consider the case that the account holder wishes to perform a transaction, say withdraw an amount. Such a request for withdrawal transaction may be received from the account holder through the computing devices 104. In this case, if the withdrawal amount is greater than the total funds that are available in the account, the transaction is rejected. On the other hand, if the withdrawal amount is equal to the total funds, the transaction is allowed and a maintenance fee can be levied.

In another case, if the withdrawal amount if less than the total funds, the
analysis module 122 further compares the withdrawal amount and the available amount, where available amount is the difference between the on-demand amount and the primary balance. If the withdrawal amount is less than or equal to the available amount, the analysis module 122 allows the account holder to perform the transaction. However, if the withdrawal amount is greater than the available amount, the analysis module 122 ascertains whether one or more previous transactions (i.e., transactions prior to the newly requested withdrawal transaction) have been made based on the transaction count. In one implementation, each of such withdrawals and related previous transactions may be monitored. The analysis module 122 can monitor and count the number of such transactions. The transaction count gets incremented every time the account holder performs a transaction, for example withdraws an amount below the secondary balance.
In one case, if the withdrawal count is less than or equal to the pre-determined
transaction counts, say 3, the analysis module 122 allows the transaction and increments the transaction count. Additionally, in said implementation, after each transaction count, the analysis module 122 may also initialize a buffer time period to allow the account holder to replenish his account up to the secondary balance within the buffer time period. The analysis module 122 is also configured to generate reminders, which indicate the transaction count and the buffer time period, for the account holders. Such reminders may be generated within a grace period that starts after the buffer time period. Furthermore, the analysis module 122 can levy penalties in case the account holder fails to replenish his account during the buffer time period.

In another case, if the withdrawal count has exceeded the predetermined
transaction count, the analysis module 122 allows the transaction but charges a maintenance fee to the account holder's account, thus indicating that the account holder has failed to maintain the time bound amount within the secondary time period and has also exceeded the number of times emergency withdrawals can be made.
This can be further explained with reference to an example. The example, in no
way, should be considered to be limiting. In an example, consider an account holder's saving account having total funds of INR 50,000, secondary balance of INR 25,000, secondary time period of 1 year, and primary balance of INR 5,000. The determination module 120 provides a higher rate of interest on the time bound amount, i.e., INR 20,000. The time bound amount, as specified earlier, is the difference between the secondary balance and the primary balance. Similarly, the determination module 120 provides a primary rate of interest on the on-demand amount, which is the difference between the total funds and the time bound amount, INR 30,000 in this case. Consider a scenario in which the account holder wishes to make a withdrawal. In such a scenario, the determination module 120 determines the available amount, which is computed to be INR 25,000 in this case. If the withdrawal amount is up to INR 25,000, the account management system 102 allows the transaction.
If the withdrawal is between INR 25,000 and INR 45,000, the transaction
count is checked. If the transaction count is less than or equal to the predetermined value of transaction counts, the transaction is cleared without any maintenance fee. However, if the transaction count is greater than the predetermined value of transaction counts, the transaction is cleared but a maintenance fee is levied since the account holder has failed to maintain the

time bound amount within the secondary time period and has also exceeded the number of times the emergency withdrawals can be made.
If the withdrawal amount is above INR 45,000 and below INR 50,000, the
transaction is cleared by charging an additional service fee since the account holder has failed to maintain the primary balance requirement as well. If the withdrawal amount is greater than the total fund, i.e., INR 50,000, the transaction is rejected.
In one implementation, the analysis module 122 can generate visual charts, to
visually represent data related to the account. The data may include the details of the account holder, the total funds in the account, the secondary time period and its expiry and start date; the time bound amount, the on-demand amount, the withdrawal counts, incremental amount, and the buffer period, etc. Such a visual chart also depicts various transactions, such as withdrawals, and the fees levied, in case the secondary balance falls below the committed value. Additionally, the secondary rate of interest earned on the secondary balance may also be depicted on the visual chart. The visual charts are presented to the account holder through the computing devices 104.
Thus, the account management system 102 logically divides the total fund
within a single account, such as a savings account, into time bound amount and the on-demand amount, both of which receive different rates of interest. Such an account provides the account holder advantages of both a high interest account and low interest account without having to create two or more separate accounts, thereby reducing paperwork and allowing the account holder to better operate and manage the accounts. Additionally, since this service may be automatically renewed, the account holder does not need to make a conscious effort to track his/her funds and make appropriate investments.

Also, unlike, fixed deposit accounts, the account management system does not
associate a stringent lock in or maturity period with the time bound amount and allows for emergency withdrawals with minimal risk. Further, greater flexibility is offered to the account holders as the secondary balance may be defined by the account holder. Additionally, the account management system 102 allows the financial institutions to invest the time bound amount, which was not committed earlier by the account holder, and generate more revenues through loans and advances.
Fig. 2 illustrates a method 200 for managing an account, according to an
embodiment of the present subject matter. The exemplary method may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, and the like that perform particular functions or implement particular abstract data types. The method may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
The order in which the method is described is not intended to be construed as a
limitation, and any number of the described method blocks can be combined in any order to implement the method, or alternate methods. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. The method described herein is with reference to account

management system 102; however, the method can be implemented in other similar systems
albeit with a few variations as will be understood by a person skilled in the art.
At block 202, an account associated with a primary balance is monitored for a
pre-determined time duration. In one implementation, the analysis module 122 monitors the account for the pre-determined time duration, for example, six months. The account is associated with a primary balance, which may be a quarterly or annual balance that an account holder is expected to maintain. If after the lapse of the predetermined time duration, it is determined that the total funds are over and above the primary balance, an indication may be generated for the account holder.
At block 204, a value of secondary balance is obtained. In one implementation,
the account holder may provide a value of secondary balance on receiving the indication. In another implementation, an association module 118 may select from a pre-defined list of values of secondary balance and associate the secondary balance with the account.
At block 206, a time bound amount and an on-demand amount are determined
based on the primary balance and the secondary balance. In an implementation, the determination module 120 computes the time bound amount based on the difference between the secondary balance and the primary balance, and the on-demand amount based on the difference between the total funds and the total time bound amount.
In one implementation the analysis module 122 may also associate a
transaction count with the account such that the transaction count is incremented every time a transaction occurs. Additionally, a buffer time period may also be initialized for the account holder to replenish his account should the transaction count get incremented.

At block 208, a secondary rate of interest is provided on the time bound
amount. For example, the determination module 120 provides a secondary rate of interest on the time bound amount and a primary rate of interest on the on-demand amount. The time period for which the time bound amount receives the secondary rate of interest may be configured by the account holder or the financial institution or both.
Fig. 3 illustrates an exemplary method 300 for determining whether an account
holder can initiate a transaction, as per one embodiment of the present subject matter. The exemplary method may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, and the like that perform particular functions or implement particular abstract data types. The method may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
The order in which the method is described is not intended to be construed as a
limitation, and any number of the described method blocks can be combined in any order to implement the method, or alternate methods. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. The method described herein is with reference to account management system 102; however, the method can be implemented in other similar systems albeit with a few variations as will be understood by a person skilled in the art.

At block 302, receiving a request for a transaction. For example, a request for
transaction, such as a withdrawal transaction, is received. Based on the availability of funds in the account, the account management system 102 allows or rejects a transaction, as described in the following paragraphs.
At block 304, it is determined that the withdrawal amount is less than the total
funds in an account. For example, the analysis module 122 compares the withdrawal amount with the total funds in the account. If, on comparison, the withdrawal amount is greater than the total funds, the transaction is rejected (not shown). On the other hand, if the withdrawal amount is equal to the total funds, the transaction is allowed and a service fee is levied (not shown).
However, if the withdrawal amount if less than the total funds, a further
comparison is made between the withdrawal amount and an available amount at block 306.
The available amount may be computed as the difference between the on-demand amount and
the primary balance. If the withdrawal amount is less than or equal to the available amount
("Yes" Branch of block 306), the analysis module 122 allows the account holder to perform
the transaction at block 308. However, if the withdrawal amount is greater than the available
amount ("No" Branch of block 306), a further determination is made at block 310.
At block 310, it is ascertained whether a previous transaction has been made.
For example, the transaction count is checked since a part of the withdrawal amount will have to be extracted from the time bound amount. If the withdrawal count is less than or equal to the pre-determined number of transaction counts, say 3 ("Yes" Branch of block 310), the analysis module 122 allows the transaction and increments the withdrawal counter at block 312. Additionally, in said implementation, after each transaction count, the analysis module

122 may also initialize a buffer time period to allow the account holder to replenish his account up to the secondary balance within the buffer time period. Furthermore, the determination module 120 can levy penalties in case the account holder fails to replenish his account during the buffer time period.
However, if the withdrawal count has exceeded the predetermined number of
counts ("No" Branch of block 310), the analysis module 122 allows the transaction but assigns a maintenance fee to the account holder's account.
Although embodiments for an account management system have been
described in language specific to structural features and/or methods, it is to be understood that the invention is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary embodiments for the account management system.

I/We Claim:
I. An account management system (102) comprising: a processor (108);
a memory (112) coupled to the processor (108), wherein the memory (112) comprises,
an association module (118) configured to associate a secondary balance to a bank account, wherein a value of the secondary balance is greater than a value of a primary balance associated with the bank account; and a determination module (120) configured to,
compute a time bound amount based in part on the secondary balance and the primary balance; and
subject a secondary rate of interest on the time bound amount for a time period defined by an account holder, wherein the secondary rate of interest is higher than a primary rate of interest accrued on the primary balance.
2. The system (102) as claimed in claim 1 further comprises an analysis module (122)
configured to:
determine a number of previous transactions based on a transaction count; process a transaction if the transaction count is within a predetermined transaction count; and
increment the transaction count based on the processing.
3. The system (102) as claimed in claim 2, wherein the analysis module (122) is further
configured to initialize a buffer time period after the increment of the transaction
count.

4. The system (102) as claimed in claim 2, wherein the analysis module (122) is further
configured to:
determine whether a withdrawal amount is less than total funds in the account and the withdrawal amount is greater than an available amount; and
in response to the withdrawal amount being greater than the available amount, identify whether a previous transaction has occurred based on the transaction count.
5. The system (102) as claimed in claim 2, wherein the analysis module (122) is further
configured to:
monitor the bank account for a pre-determined time duration to determine whether total funds exceed the primary balance at a lapse of the pre-determined time period; and
generate an indication based on the monitoring.
6. The system (102) as claimed in claim 1, wherein the secondary balance is provided by the account holder.
7. A computer implementable method comprising:
receiving a request for associating a secondary balance to a bank account through an electronic interface (110), wherein a value of the secondary balance is greater than a value of a primary balance;
computing a time bound amount based at least on the secondary balance and the primary balance; and
providing a secondary rate of interest on the time bound amount for a user defined period, wherein the secondary rate of interest is higher than a primary rate of interest levied on the primary balance.

8. The method as claimed in claim 7, wherein the providing comprises disbursing an on-demand amount at the primary rate of interest, wherein the on-demand amount and the time bound amount are within the bank account.
9. The method as claimed in claim 7 further comprises:
receiving a request for a transaction;
determining a number of previous transactions based on a transaction count; processing the transaction if the transaction count is within a predetermined transaction count; and
incrementing the transaction count based on the processing.
10. The method as claimed in claim 9, wherein the method comprises:
determining whether a withdrawal amount is less than total funds in the account;
if the withdrawal amount is less than the total funds in the account, further determining whether the withdrawal amount is greater than an available amount; and
in response to the withdrawal amount being greater than the available amount, further identifying whether a previous transaction has been made based on the transaction count.
11. A computer-readable medium having embodied thereon a computer program for
executing a method comprising:
receiving a request for associating a secondary balance to a bank account through an electronic interface (110), wherein a value of the secondary balance is greater than a value of a primary balance associated with the bank account;
computing a time bound amount based in part on the secondary balance and the primary balance; and

providing a secondary rate of interest on the time bound amount for a user defined period, wherein the secondary rate of interest is higher than a primary rate of interest associated with the primary balance.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 298-MUM-2011-US(14)-HearingNotice-(HearingDate-16-04-2021).pdf 2021-10-03
1 abstract1.jpg 2018-08-10
2 298-mum-2011-form 5.pdf 2018-08-10
2 298-MUM-2011-Correspondence to notify the Controller [09-04-2021(online)].pdf 2021-04-09
3 298-mum-2011-form 3.pdf 2018-08-10
3 298-MUM-2011-CLAIMS [20-09-2018(online)].pdf 2018-09-20
4 298-MUM-2011-FORM 26(23-9-2011).pdf 2018-08-10
4 298-MUM-2011-COMPLETE SPECIFICATION [20-09-2018(online)].pdf 2018-09-20
5 298-mum-2011-form 2.pdf 2018-08-10
5 298-MUM-2011-FER_SER_REPLY [20-09-2018(online)].pdf 2018-09-20
6 298-MUM-2011-OTHERS [20-09-2018(online)].pdf 2018-09-20
6 298-mum-2011-form 2(title page).pdf 2018-08-10
7 298-MUM-2011-FORM 18(6-1-2012).pdf 2018-08-10
7 298-mum-2011-abstract.pdf 2018-08-10
8 298-mum-2011-form 1.pdf 2018-08-10
8 298-mum-2011-claims.pdf 2018-08-10
9 298-MUM-2011-FER.pdf 2018-08-10
9 298-MUM-2011-CORRESPONDENCE(23-9-2011).pdf 2018-08-10
10 298-MUM-2011-CORRESPONDENCE(6-1-2012).pdf 2018-08-10
10 298-mum-2011-drawing.pdf 2018-08-10
11 298-mum-2011-correspondence.pdf 2018-08-10
11 298-mum-2011-description(complete).pdf 2018-08-10
12 298-mum-2011-correspondence.pdf 2018-08-10
12 298-mum-2011-description(complete).pdf 2018-08-10
13 298-MUM-2011-CORRESPONDENCE(6-1-2012).pdf 2018-08-10
13 298-mum-2011-drawing.pdf 2018-08-10
14 298-MUM-2011-CORRESPONDENCE(23-9-2011).pdf 2018-08-10
14 298-MUM-2011-FER.pdf 2018-08-10
15 298-mum-2011-claims.pdf 2018-08-10
15 298-mum-2011-form 1.pdf 2018-08-10
16 298-mum-2011-abstract.pdf 2018-08-10
16 298-MUM-2011-FORM 18(6-1-2012).pdf 2018-08-10
17 298-mum-2011-form 2(title page).pdf 2018-08-10
17 298-MUM-2011-OTHERS [20-09-2018(online)].pdf 2018-09-20
18 298-MUM-2011-FER_SER_REPLY [20-09-2018(online)].pdf 2018-09-20
18 298-mum-2011-form 2.pdf 2018-08-10
19 298-MUM-2011-FORM 26(23-9-2011).pdf 2018-08-10
19 298-MUM-2011-COMPLETE SPECIFICATION [20-09-2018(online)].pdf 2018-09-20
20 298-mum-2011-form 3.pdf 2018-08-10
20 298-MUM-2011-CLAIMS [20-09-2018(online)].pdf 2018-09-20
21 298-mum-2011-form 5.pdf 2018-08-10
21 298-MUM-2011-Correspondence to notify the Controller [09-04-2021(online)].pdf 2021-04-09
22 abstract1.jpg 2018-08-10
22 298-MUM-2011-US(14)-HearingNotice-(HearingDate-16-04-2021).pdf 2021-10-03

Search Strategy

1 298_MUM_2011_07-02-2018.pdf