JP2007140890A - Account management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an account management method capable of money transfer management in the account more easily with respect to a technology for controlling and managing remittances of public utilities charges and deduction by using a computer in the account of a financial institution. <P>SOLUTION: Balance in the account is managed by dividing it into disposable balance and balance for other transfer. In doing this division, in response to designation by a user or the like, transferred party information for specifying a transferred party and an amount of transferred money are stored in association with each other every transferred party (a claimant). When a transfer request is received, the transferred party information included in the transfer request is compared with the transfer information stored in advance, and the validity of the request is determined on the basis of the comparison result. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a technique for controlling and managing a transfer or withdrawal of a utility bill using a computer in an account of a financial institution.

  Conventionally, public charges, credit card payments, and other personal reserves have been transferred and debited (hereinafter referred to as transfers) from bank accounts. For this transfer, it was necessary to keep the account balance larger than the transfer amount. As a conventional technique for controlling (managing) an account in this way, there is Patent Document 1. In patent document 1, it aims at preventing the balance shortage, without providing another account. In order to achieve this purpose, in Patent Document 1, when the invoice comes, the debit amount is transferred to a cell divided within one account, such as an electricity bill, from which the user can withdraw. It is to be controlled so that there is no.

JP 2003-168010 A

  However, in Patent Document 1, the billing amount is transmitted from the billing party (electric power company or the like) to the home, and the banking system is accessed from the home regarding the information, and the billing amount is moved to the cell corresponding to the billing by this access. In other words, it is necessary to check the billing amount at home and access the bank system. For this reason, it has the subject that a user is loaded.

  However, if the user simply does not access the bank system, there is a problem that the validity of the billing amount cannot be confirmed.

  Therefore, in the present invention, the balance in the account is managed by dividing it into a disposable balance and other transfer balance. At this time, according to the designation of the user, etc., for each transfer destination (biller), the transfer destination information for specifying the transfer destination and the transfer amount are stored in association with each other. The transfer destination information included in the transfer request is compared with the transfer information stored in advance, and the validity of the request is determined according to the comparison result.

The present invention also includes the following aspects.
(1) The amount stored in advance and the amount included in the transfer request are further compared, and if the difference is within a predetermined range as a result of the comparison, it is determined as a valid transfer request.
(2) In this case, the determination criterion may be changed for each transfer destination. That is, the predetermined range may be varied depending on the transfer destination. In addition, it may be considered that it is divided into one that is variable each month such as an electricity bill and one that is a fixed amount such as rent. This predetermined range includes zero (that is, coincidence).
(3) The transfer amount stored in advance may be calculated based on the past transfer amount of the transfer destination. For example, an average value for the past year is included. This amount may be the amount specified by the user.
(4) Moreover, you may manage for every transfer instead of performing for every transfer destination.
(5) Further, in the present invention, the amount included in the transfer request determined to be legitimate may be locked or notified to the user. As the lock of the amount, the transfer amount may be moved to a specific cell as in Patent Document 1.

  According to the present invention, transfer management in an account can be executed more easily.

  Embodiments of the present invention will be described with reference to the drawings.

  First, FIG. 1 shows a system configuration diagram in the present embodiment. Each computer is connected to each other via a network. Each computer has a processing device such as a memory, a storage device including a hard disk, and a CPU, and the processing device executes information processing according to a program stored in the storage device.

Hereinafter, the processing content of this Embodiment is demonstrated.
(Disposable balance method registration)
In step 201, the billing system 104 is notified of the use of the disposable balance method from the general-purpose terminal 101 used by the customer, the ATM 102, and the BTS 103 used by the financial institution staff based on the request from the customer. Based on this notification, the account system 104 registers a value indicating a disposable balance in the balance display classification of the ledger DB 203. For example, the character string “disposable balance” is registered.

Premise information used when using the disposable balance method from the general-purpose terminal 101 used by the customer, the ATM 102, and the BTS 103 used by the financial institution staff based on the bill from the customer to the billing system 104 in step 204 To be notified. Based on this notification, the accounting system 104 registers the input information in the deposit / withdrawal contract information DB 206 using the deposit / withdrawal registration information update function 205. As an example, account number “0123456”, scheduled deposit / withdrawal amount “8,400”, scheduled processing date “8 days”, variation category “variable amount”, client code “5678901234”, contractor number “09012345678”, holiday treatment “post-business” Register "day".
(Create deposit / withdrawal schedule details)
Create a deposit / withdrawal schedule for the current month. In step 301, the billing system 104 acquires a balance display category from the ledger DB 203. As an example, if the account number is “0123456”, the balance display classification is “disposable balance”.

  In step 302, the accounting system 104 determines that the balance display category is “true” when the balance display category is “disposable balance”, and false when the balance is real. If true, the process proceeds to step 303, and if false, the process is terminated. For example, if the account number is “0123456”, the balance display classification is “disposable balance”, so the determination is true, and the process proceeds to step 303.

  In step 303, the billing system 104 acquires data in the deposit / withdrawal contract information DB 206. In the case of account number “0123456” as an example, the amount of deposits and withdrawals.

  In step 304, the billing system 104 determines that the holiday handling acquired from the deposit / withdrawal contract information DB 206 is true for the next business day and false for the previous business day. If true, go to step 306; if false, go to 305. For example, if the account number is “0123456” and a holiday is handled as “next business day”, the result becomes true and the process proceeds to 306. Although there are a plurality of records in the account number “0123456”, it is assumed that all records are processed in the same way.

  In step 305, the accounting system 104 calculates the previous business day of the current month from the scheduled processing date acquired from the deposit / withdrawal contract information DB 206 and sets it as the scheduled processing date.

  In step 306, the accounting system 104 calculates the next business day of the current month from the scheduled processing date acquired from the deposit / withdrawal contract information DB 206 and sets it as the scheduled processing date. As an example, when calculating the scheduled processing date for August 2004, assuming that the account number is “0123456”, the scheduled processing date is “8th”, and the holiday is treated as “next business day”, the scheduled processing date is “2004”. August 9th.

In step 307, the scheduled processing date calculated in step 305 or 306 is registered in the current deposit / withdrawal statement DB 308. Also, the deposit / withdrawal scheduled amount, the client code, and the contractor number acquired from the deposit / withdrawal contract information DB 206 are registered. In addition, an unprocessed value is registered in the processing status of the current deposit / withdrawal detail DB 308. As an example, an account number “0123456”, a scheduled processing date “August 9, 2004”, a client code “5678901234”, a contractor number “09012345678”, and a processing status “processing not yet completed” are registered.
(Consistency check)
Accepts deposit / withdrawal request data and executes consistency check when performing account transfer processing.

  In step 401, the billing system 104 acquires a balance display category from the ledger DB 203.

  In step 402, the accounting system 104 determines that the balance display category is true when the balance is a disposable balance, and false when the balance is a real balance. For example, in the case of the account number “0123456”, the balance display classification is “disposable balance”, and the process proceeds to step 403.

  In step 403, the billing system 104 acquires data in the current month deposit / withdrawal detail DB 308.

  In step 404, it is determined whether the client code in the deposit / withdrawal request data 400 matches the client code in the current month deposit / withdrawal details DB 308. If they match, it is determined to be true, and if they are not constant, it is determined to be false. For example, if the client code “5678901234” in the deposit / withdrawal request data 400 and the client code “5678901234” in the current deposit / withdrawal details DB 308 are true, the processing proceeds to step 405.

  In step 405, it is determined whether or not the contractor number in the deposit / withdrawal request data 400 matches the contract number in the current month deposit / withdrawal details DB 308. If they match, it is determined to be true, and if they do not match, it is determined to be false. For example, if the contractor number “09012345678” in the deposit / withdrawal request data 400 and the contractor number “09012345678” in the current month deposit details DB 308 are true, the processing proceeds to step 408.

  In step 406, a value meaning processed is registered in the processing status of the current deposit / withdrawal statement 308. As an example, “processed” is registered in the processing status of the record of the account number “0123456”, the client code “5678901234”, and the contractor number “09012345678”.

  In step 407, data is acquired from the deposit / withdrawal contract information DB 206.

  In step 408, the number of transactions in the deposit / withdrawal contract information DB 206 is incremented. As an example, in the case where the account number “0123456”, the client code “5678901234”, and the contract number “09012345678” in the deposit / withdrawal contract information DB 206 are “0”, the incremented transaction number is “1”.

  In step 409, data is acquired from the deposit / withdrawal result DB 410.

  In step 411, the total amount of transfer amount in the deposit / withdrawal result DB 410 is calculated, and the average amount of deposit / withdrawal is calculated by dividing the total amount of transfer amount by the value divided by the number of transactions calculated in step 408. As an example, if the account number “0123456”, the client code “5678901234”, the contractor number “09012345678”, the transfer amount “8,400”, and the number of transactions incremented in step 408 are “1” in the deposit / withdrawal record DB 410 The total amount is “8,400”, and the average deposit / withdrawal amount is “8,400”.

  In step 412, the number of transactions calculated in step 408 is registered in the deposit / withdrawal contract information DB 206. As an example, the transaction count “1” calculated in step 408 is registered.

  In step 413, the transfer amount of the deposit / withdrawal request data 400 is registered in the deposit / withdrawal result DB 410. For example, in the case of the client code “5678901234”, the account number “0123456”, the contractor number “09012345678”, and the transfer amount “8,400” of the deposit / withdrawal request data 400, the account number “0123456” “8,400”, client code “5678901234”, and contractor number “09012345678” are registered.

In step 414, the oscillating process is executed.
(Disposable balance calculation)
In step 501, the accounting system 104 acquires the account balance and balance display classification from the ledger DB 203.

  In step 502, the accounting system 104 determines that the balance display category is true when the balance is a disposable balance, and false when the balance is an actual balance. For example, in the case of the account number “0123456”, the balance display classification is “disposable balance”, and the process proceeds to step 503.

  In step 503, data in the current deposit / withdrawal detail DB 308 is acquired.

  In step 504, the total value of the planned deposit / withdrawal amounts of the records whose processing status in the current deposit / withdrawal detail DB 308 is “unprocessed” is calculated. As an example, in the case of the data of FIG. 9, the total value is “315,800”.

  In step 505, the disposable balance is calculated by adding the total deposit / withdrawal amount to the account balance. As an example, when the account number “0123456” in the ledger DB 203, the account balance “1,560,000”, and the total deposit / withdrawal amount calculated in Step 504 is “315,800”, the disposable balance is “1,875,800”.

  In step 506, the disposable balance is displayed on the general-purpose terminal 101, ATM 102, BTS 103, and the like.

  The present invention can be improved by using a balance inquiry function of a financial institution and a computer.

System Configuration. Disposable balance method registration flow. Deposit / withdrawal schedule creation flow. Consistency check. Disposable balance calculation. Ledger DB. Deposit / withdrawal contract information DB. Monthly deposit / withdrawal details DB. Deposit / withdrawal request data. Withdrawal results DB.

Explanation of symbols

101 ... General-purpose terminal, 102 ... ATM, 103 ... BTS, 104 ... Accounting system.

Claims (5)

In an account management method for performing a transfer process in response to a transfer request from a transfer destination using a computer,
For each account managed by the computer, for each transfer destination, transfer destination information for specifying the transfer destination and the transfer amount are stored in association with each other,
Receiving a transfer request including transfer destination information for identifying the transfer destination from the transfer destination;
Compare the received transfer destination information with the transfer information stored in advance,
An account management method characterized in that the validity of a claim is determined according to the comparison result, and the processing corresponding to the transfer request is executed according to the determination result. The account management method according to claim 1,
The transfer request includes the amount to be transferred,
Compare the stored transfer amount with the amount included in the transfer request,
In the account management method, the determination of the validity is further determined as a valid request when the comparison result of the amount satisfies a predetermined relationship. In the account management method according to claim 2,
In the account management method, the comparison of the amounts is determined as a valid transfer request when the difference is within a predetermined range as a result of the comparison as the predetermined relationship. In the account management method in any one of Claim 3 thru | or 4,
Account management characterized in that, as a process in response to the transfer request, when the determination result is determined to be valid, an amount corresponding to the amount to be transferred out of the balance of the account is locked. Method. In the account management method in any one of Claims 1 thru | or 4,
An account management method characterized in that the transfer amount stored in advance is calculated based on a history of a corresponding transfer destination.

Images