JP2015228120A - Electronic recording credit occurrence management system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and a method for controlling the occurrence of an electronic recording credit.SOLUTION: An electronic recording credit occurrence management system identifies the maximum amount of an electronic recording credit on the basis of obligator information contained in a received occurrence recording request, specifies the credit amount of the obligator by identifying the electronic recording credit, which has already occurred, of the obligator, and determines whether or not the electronic recording credit amount of the obligator exceeds the maximum amount when the occurrence recording request is transmitted to an electronic credit recording institution system. In response to the determination that the electronic recording credit amount exceeds the maximum amount, the electronic recording credit occurrence management system determines whether or not the credit amount of the electronic recording credit of the obligator falls within the range of the maximum amount when the occurrence recording of the electronic recording credit is recorded on the day when the occurrence recording request is received. When the electronic recording credit amount is determined to exceed the maximum amount, and the credit amount of the electronic recording credit of the obligator is determined not to fall within the range, the electronic recording credit occurrence management system determines, on the basis of the data of results of a received request for decision, any one of not accepting the occurrence recording request, accepting the request by temporarily increasing the maximum amount, and accepting the request by constantly increasing the maximum amount.

Description

  The present invention relates to an electronic record receivable generation management system and method. More specifically, the present invention relates to a system for a financial institution to supervise a debtor's electronic record receivable, and to control the amount of occurrence or the number of records recorded for the occurrence of an electronic record receivable over a certain period, and Regarding the method.

  Conventionally, bills are mainly used as a settlement method as a method of deferred payment based on inter-company credit. In other words, a company that intends to use a bill receives a bill of paper after entering into a current account transaction contract with a bank, and draws a bill instead of cash based on an agreement with the other party during a commercial transaction. It was devoted to payment. When the due date of the bill (for example, 2 to 3 months after the bill is issued), the amount indicated on the bill is exchanged with the bill through the financial institution by presenting the bill at that time. Will be paid to the holder from.

  In addition, when the performance of a company that is a bill maker deteriorates and it becomes impossible to settle the bill on the due date, it is said that the bank of the company does not pass the bill. By detecting signs and restricting the delivery of bill paper itself in stages or based on a prescribed screening, it is possible to prevent the occurrence of a “bill of bills” that could lead to corporate bankruptcy. There was also a case.

  On the other hand, in recent years, electronically recorded receivables (also called “Densai (registered trademark)”) have come to be widely used as a new settlement method. As described in Non-Patent Document 1, electronic record receivables are sent to electronic receivable recording institutions (also referred to as “Densai Net (registered trademark)”) established by the National Bank Association. It is generated by requesting a record of occurrence of an electronic record receivable based on a request from a customer. The generated electronic receivables will be automatically repaid from the debtor account to the creditor account when the prescribed payment date shown in the electronic record receivable arrives. Records such as payments to the ledger are also made automatically. More specifically, when the payment due date approaches (for example, two bank business days before the payment due date), the electronic bond recording institution provides information for performing inter-account remittance settlement with a financial institution having a debtor account (debt). Creditor account, creditor account, due date, amount of receivable, record number of electronically recorded receivable, etc.) A financial institution having a debtor account performs inter-account remittance settlement based on the received information when the due date arrives.

  In this way, electronically recorded receivables function as a settlement means that supports intercompany credit as with conventional bills, but also have a system similar to bankruptcy in bills. That is, as described in Non-Patent Document 2, for debtors that could not be settled on the due date due to lack of funds, etc., the insolvency registration was made at the electronic bond recording institution, and the data on inability to be paid are all participating financial institutions. Will be notified. When data regarding inability to pay is notified twice in a predetermined period, a certain penalty such as a transaction restriction is imposed on the obligor in the same way as when a bill failure occurs.

“Preparation Office for Electronic Receivables Record Organizations”, “National Bank Association Electronic Receivables Record Practice Q & A-Illustrated by Zenginkyo Electronic Receivables Recorder“ Densai Net ””, Bank Training Company, March 2010 Yoshiko Ogi, “Densai Practical Q & A”, General Association of Financial and Financial Situation, July 2013

  As mentioned above, both bills and electronically-recorded receivables function as a means of settlement based on intercompany credit, but there are significant differences in terms of issuance restrictions in response to a decline in sales and business performance. With regard to bills, it is possible to control bills by increasing or decreasing the issuance of bill paper itself, since the transaction financial institution knows the actual state of the company.

  However, electronically recorded receivables do not have paper like bills, and are all managed with electronically recorded data, so they cannot be managed in the same way as bills. If the use is permitted, there is a problem that an electronic record receivable can be generated without an upper limit.

  The present invention has been made in view of such a problem, and an object of the present invention is to provide a system and method capable of controlling the generation of electronic record bonds in accordance with the actual situation of a company. More specifically, in the present invention, when a company intends to generate electronic record receivables, the transaction financial institution can make an extreme setting to increase or decrease the generated amount or control the number of recorded records. It is an object of the present invention to provide a system and method involved in the generation of electronic record receivables.

  In order to solve the above problems, a method executed by a computer for controlling the amount of occurrence of an electronic record receivable for each obligor, which is an aspect of the present invention, is included in the received occurrence record request. Identifying an extreme amount of electronically recorded receivables that can be generated for the debtor based on the information; identifying a debtor amount of the obligor by identifying an already recorded electronically recorded claim of the debtor; Determining whether the debt amount of the debtor's electronic record receivable exceeds the identified extreme amount when the received occurrence record request is transmitted to the electronic receivables record institution system; and In response to the determination that the amount exceeds the maximum amount, if the occurrence record of the electronic record receivable is recorded on the date indicated by the received occurrence record request, Determining whether or not the amount of the electronically recorded receivable falls within the range of the identified extreme amount, and is determined to exceed the identified extreme amount and does not fall within the range of the identified extreme amount If it is determined, based on the data of the received deliberation result, the received request for occurrence record is not accepted, the extreme amount is temporarily accepted, and the extreme amount is constantly increased. And receiving a step of determining one of them.

  According to the present invention, there is an effect that it is possible to control the generation of electronic record receivables according to the actual state of a company. In addition, according to the present invention, it is possible to accept the occurrence of an electronic record receivable for a business performance deterioration destination by not accepting it, or accepting it by a temporary measure, and determining that the business performance deterioration does not have an effect for the time being and can accept it permanently.

A detailed understanding of the embodiments disclosed herein can be obtained from the following description, illustrated with reference to the accompanying drawings.
It is a figure which shows the outline | summary of the whole system containing the management server which concerns on this invention. It is a figure explaining the system configuration | structure of the management server which concerns on this invention. It is a figure which shows the processing flow regarding extreme amount control performed by the management server which concerns on this invention. It is a figure which shows an example of the reservation request data of an occurrence record. It is a figure which shows the processing flow regarding the upper limit generation | occurrence | production number control of an electronic record receivable performed by the management server which concerns on this invention. It is a functional block diagram of the management server which concerns on this invention.

  Hereinafter, embodiments of the present invention will be described in detail. FIG. 1 is a diagram showing an overview of the entire system including the management server 120 according to the present invention. As shown in FIG. 1, the bank system 100 is connected to the debtor terminal 130 and the electronic bond recording institution system 140 so that they can communicate via a network. The communication among the bank system 100, the debtor terminal 130, and the electronic bond recording institution system 140 only needs to be able to execute mutual communication with a certain level of security. It is done by using. Moreover, the bank system 100 has an approval server 110 and a management server 120 that can communicate with each other. Hereinafter, each component will be described.

  The bank system 100 is a system used in a financial institution, and includes a billing system, an information system, and the like. In the present specification, for the sake of convenience of explanation, only the approval server 110 and the management server 120 are shown as components related to the present invention. However, it is understood that the bank system 100 includes an accounting system and an information system. I want to be. On the other hand, as another embodiment, the bank system 100 links the debtor terminal 130, the electronic bond recording institution system 140, and the bank account system and information system separately from the bank account system and information system. The relay system may be a system outside the bank.

  The approval server 110 provides a function for approving various cases raised by the person in charge. In particular, in the present specification, a permanent or temporary increase of the debtor's extreme amount, Provides a function to approve whether or not to allow the generation of electronically recorded bonds. When the management server 120 determines that a predetermined condition for the occurrence of the electronic record receivable is met, the approval server 110 receives the approval data from the management server 120 and sends the approval result for the approval to the management server. 120 is notified.

  Since the management server 120 is located between the debtor terminal 130 and the electronic bond recording institution system 140, it is a server called a relay server or a linkage server. In response to receiving the request for the record of occurrence of the electronic record receivable requested from the debtor terminal 130, the management server 120 performs processing as will be described later to control the amount of occurrence of the electronic record receivable You can make settings and control the number of occurrences.

  The debtor terminal 130 is a terminal used by a debtor who makes a request for record of occurrence of an electronically recorded claim, and communicates with the bank system 100 and the management server 120. The debtor is a customer who has applied for a Densai Net usage contract and is permitted to use it as a debtor and is assigned a user number from the Densai Net. One user number is assigned to one user.

  The electronic bond recording institution system 140 is a system that communicates with participating financial institutions participating in the Densai Net and records generation records, transfer records, payments, etc. of electronic record bonds in a record book.

  FIG. 2 is a diagram illustrating the system configuration of the management server 120 according to the present invention. The management server 120 includes a control unit 201, a main storage unit 202, an auxiliary storage unit 203, an interface (I / F) unit 204, an output unit 205, a hold DB 206, and a condition DB 207 that are connected to each other via a transmission path such as the bus 210. I have. In FIG. 2, only one control unit 201, main storage unit 202, and auxiliary storage unit 203 are shown. However, it is also possible to implement parallel and distributed processing by using a plurality of them. It is.

  The control unit 201 is also called a central processing unit (CPU), performs control of each component in the management server 120 and data calculation, and stores various programs stored in the auxiliary storage unit 203 into the main storage unit 202. To read and execute. The main storage unit 202 is also called a main memory, and stores various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit 203 is a storage device typified by a hard disk (HDD) and is used when data and programs are stored for a long period of time.

  The interface (I / F) unit 204 serves as an interface for transmitting and receiving data to and from other systems and devices, and accepts various commands and input data (such as various masters and tables) from the system operator. Provide an interface. The output unit 205 provides a display screen that displays the processed data.

  The hold DB 206 is a database that stores the occurrence record request received from the debtor terminal 130. As will be described later, when the management server 120 transmits the occurrence record request to the electronic bond recording institution system 140, or the management server 120 does not transmit the occurrence record request to the electronic bond recording institution system 140 (that is, the electronic record If it is determined that the claim occurrence record request is not accepted), the occurrence record request data is deleted from the hold DB 206.

  The condition DB 207 is a database that stores extreme amount information for each obligor, that is, information on an upper limit that can generate an electronically recorded receivable for each obligor. In one embodiment of the present invention, the condition DB 207 stores extreme amount information for each obligor and for each creditor so that the obligor can set an extreme amount according to a business relationship with a specific creditor. It may be configured as follows. In addition, the condition DB 207 is a database that stores information on the upper limit value of the number of records of electronic record receivables for each debtor. In one embodiment of the present invention, as in the case of the extreme amount described above, the debtor can set an upper limit value of the number of occurrences of electronic record receivables according to the business relationship with a specific creditor. The DB 207 may be configured to store information on the upper limit value of the number of records of electronic record receivables for each obligor and for each creditor. Each data stored in the condition DB 207 is given a user number indicating an individual debtor.

  Hereinafter, a method of controlling the generation of electronic record bonds will be described, but there are roughly two types of control methods. One is a method of controlling the balance of electronically recorded receivables for each debtor with an extreme amount, and the other is a method for controlling the number or amount of electronically recorded receivables recorded within a certain period for each obligor. It is. First, referring to FIG. 3, a method for controlling the balance of electronic record receivables for each debtor in an extreme amount will be described. Next, referring to FIG. Explain how to control the number of occurrences or amounts of claims.

  FIG. 3 shows a processing flow related to extreme amount control executed by the management server 120 according to the present invention.

  In S <b> 301, management server 120 receives an occurrence record request from debtor terminal 130 and stores it in hold DB 206. As another embodiment, the management server 120 may receive an occurrence record request from the debtor terminal 130 and process it in-memory without storing it in the hold DB 206. The generation record request may be a generation record reservation request as shown in FIG. 4 as an example. As shown in FIG. 4, the reservation request data 400 for occurrence records includes information such as debtor information, creditor information, amount of claims, designation date of occurrence, due date, payment method, and the like.

  In S302, management server 120 reads the debtor information included in the received occurrence record request, refers to condition DB 207 based on the read debtor information, and records the electronic record claims that can be generated for the debtor. Identify the extreme amount. The extreme amount can be arbitrarily determined by the financial institution for each obligor, but in the description of this embodiment, for the sake of convenience, the explanation will be made assuming that the obligor's extreme amount is 500,000 yen.

  In S303, management server 120 identifies the debtor's credit amount by identifying the debtor's existing electronically recorded credit. Identification of an existing electronic record receivable can be performed by the management server 120 accessing the electronic receivable recording institution system 140 using the debtor's user number as a key. Alternatively, as another embodiment, the management server 120 downloads the data of the debtor's electronic record receivable from the electronic receivable recording institution system 140 in advance at a predetermined timing and stores the data in the management server 120. May be performed by accessing the data of the debtor's electronically recorded receivable in which is stored. In other words, any method may be used as long as the identification is performed based on the data of the debtor's electronic record receivable at a predetermined time. Furthermore, the identification of existing electronic record receivables may be not only the debtor's user number but also the debtor's user number and the branch and account units of the transaction financial institution. When using electronically recorded receivables with multiple accounts, the transaction financial institution should specify the amount of the obligor's receivable within the appropriate range from the whole to individual accounts for the same obligor. In addition, the identification of the existing electronic record receivable is to identify the electronic record receivable that has not been repatriated between accounts at a certain identification time.

  In addition, when the reservation request data 400 of the debtor's occurrence record is stored in the hold DB 206, the management server 120 also refers to the reservation request data 400 stored in the hold DB 206 to identify a specific identification. The amount of the electronically recorded receivable of the debtor whose occurrence record date is specified before that point is specified.

An example of an existing electronic record receivable of the identified debtor is shown below. In this example, the reservation request data 400 (occurrence designation date: 4/20) stored in the hold DB 206 does not exist. The record number is a number for identifying each electronic record receivable, and is originally represented by 20-digit alphanumeric characters. However, for convenience of explanation in this specification, as shown below, 4-digit alphanumeric characters are used. It will be expressed as
(Record number) (Payment date) (Receivable amount)
M000 4/15 \ 50,000
M001 4/25 \ 150,000
M002 5/23 \ 200,000
M003 6/25 \ 100,000

  In S304, the management server 120, if the occurrence record request received in S301 is transmitted as it is to the electronic bond recording institution system 140 and is recorded as an occurrence record in the record book on 4/20, which is the designated occurrence date. In addition, it is determined at the time of identification when the request for occurrence record is received whether or not the credit amount of the debtor's electronic record receivable exceeds the extreme amount identified in S302 on 4/20.

  In the example of Fig. 4, the amount of electronically recorded receivables is ¥ 100,000. Therefore, if the requested record of electronically recorded receivables is recorded in the record book as it is on 4/20, the amount of receivables of electronically recorded receivables It will be judged that the total amount will be 600,000 yen, which will exceed the extreme amount of 500,000 yen of the debtor concerned.

  As a result of the determination by the management server 120 as described above, if the maximum amount is exceeded, the process proceeds to S306. On the other hand, if the maximum amount is not exceeded, the process proceeds to S305.

  In S 305, the management server 120 reads the reservation request data 400 from the hold DB 206 and transmits it to the electronic bond recording institution system 140 when 4/20, which is the specified occurrence date, arrives. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. Alternatively, if the occurrence record request received in S301 is not a reservation request data 400 but a request to generate an occurrence record on the reception day, the management server 120 promptly requests the occurrence record request after the processing in S304. It transmits to the electronic bond recording institution system 140. In addition, when the amount is not excessively exceeded on 4/20, which is the designated occurrence date, the management server 120 receives the occurrence record request from the hold DB 206 even when 4/20, which is the designated occurrence date, does not arrive. The reservation request data 400 may be read and transmitted to the electronic bond recording institution system 140.

  In S306, in the case where the amount is excessively exceeded on 4/20, which is the specified occurrence date, the management server 120 returns the electronic record receivable based on the reservation request data 400 on the specified occurrence date included in the received occurrence record request. Electronic record receivables that are due for payment until 4/20, which is the specified date of occurrence included in the received request for occurrence records, from the existing electronic record receivables when the occurrence record is recorded It is determined whether it falls within the extreme amount of the debtor after deducting.

  More specifically, the management server 120 identifies the debtor's electronically recorded receivable that is due for payment prior to the specified date of occurrence. In the above example, the management server 120 identifies the electronically recorded receivable (payment date: 4/15, receivable amount: \ 50,000) with the record number M000. However, in this example, the total amount of receivables for the electronically recorded receivables with record numbers M001, M002, and M003 is 550,000 yen, so adding the electronically recorded receivable (100,000 yen) based on the reservation request data 400 will still It will exceed the extreme amount of the debtor. Therefore, in this example, the management server 120 determines that it does not fall within the extreme by the occurrence specified date. In this case, the process proceeds to S310.

  In another embodiment of the present invention, when an electronically recorded receivable whose due date arrives before the specified date of occurrence is settled without delay, the occurrence of an electronically recorded receivable based on the reservation request data 400 on the specified date of occurrence In some cases, even if a record is recorded, it falls within the extreme amount of the obligor. In such a case, the process proceeds to S307.

  In S307, the management server 120 sends an alert indicating that “the current amount exceeds the maximum amount but falls within the maximum on the specified date of occurrence” to the output unit 205 (for example, an administrator connected to the management server 120) Display via a display device such as a display of a mobile terminal. The management server 120 can also send such an alert to the debtor terminal 130 via the network in order to indicate it to the debtor.

  In S308, the management server 120 identifies that the other electronic record receivable has come within the maximum amount by detecting that another electronically recorded receivable has been settled by inter-account remittance on the payment date. As described above, when the payment due date approaches, the electronic receivables recording institution provides information for performing inter-account remittance settlement to a financial institution having a debtor account (debtor account, creditor account, due date, amount of receivable) , Electronic record receivable record number, etc.). The banking system 100 of a financial institution having a debtor account performs inter-account remittance based on the received information when the due date arrives. However, the record number of the electronically recorded receivable to be settled and the debtor are specified. The bank system 100 can notify the management server 120 of the record number of the electronic record receivable and the debtor information.

  Since the management server 120 can detect that another electronic record receivable has been settled based on the notified record number and debtor information, the management server 120 stores the data of the remaining electronic record receivable of the specified debtor and the hold DB 406. It can be identified from the stored reservation request data 400 that it is within the extreme amount of the obligor.

  The banking system 100 of the financial institution having the debtor account receives the balance information of the debtor's settlement account (only the balance at that time) when receiving the information for performing the inter-account remittance settlement from the electronic bond recording organization. If necessary, it is determined whether or not the amount of the receivable can be settled on the designated date of occurrence by checking the transfer reservation / transfer reservation information. If it is determined by this determination processing that inter-account remittance settlement cannot be performed on the specified occurrence date, the bank system 100 can perform error processing and notify the operator in charge of the financial institution of a warning. If other electronically recorded receivables are not settled due to a shortage of the debtor's settlement account on the due date, the process does not proceed to S309, and the occurrence record is not made, and is connected to the management server 120. An error message to that effect is displayed on the manager terminal and the customer terminal 130.

  In S309, the management server 120 reads the reservation request data 400 from the hold DB 206 and transmits it to the electronic bond recording institution system 140 when the specified occurrence date arrives. As a result, the electronic bond recording institution system 140 records the occurrence record in the record book based on the reservation request data 400 on 4/20, which is the occurrence designation date. In addition, among the existing electronic record receivables, if the amount of receivables of the electronic record receivables that are due before the specified date of occurrence included in the received request for occurrence records is deducted, If the transaction financial institution determines that the remittance between accounts of the obligor is surely performed on the due date, the management server 120 generates the occurrence even if the specified date of occurrence does not arrive. When the request for recording is received, the reservation request data 400 may be read from the holding DB 206 and transmitted to the electronic bond recording institution system 140. In that case, it is the same as the case where the maximum amount is not exceeded in S304, and is handled in the same manner as in S305.

  Next, the processing after S310, which is executed when it is determined in S306 that it does not fall within the limit by the occurrence designation date, will be described.

  In S310, the management server 120 notifies the output unit 205 (for example, the management server 120 that an amount exceeding the maximum amount at the present time and does not fall within the limit until the specified occurrence date arrives). Display via a display device such as a display of the manager terminal. In response to the notification of such an alert, the person in charge of the transaction financial institution “increases the maximum amount only for the current time” and “increases the maximum amount per se” for the reservation request data 400. The request data is generated and transmitted to the request server 110. At this time, the created approval data can be based on the result of discussion between the person in charge of the transaction financial institution in contact with the debtor.

  In S <b> 311, the management server 120 receives the approval result data from the approval server 110.

  In S312, the management server 120 determines whether the data of the deliberation result indicates approval or disapproval. In the case of approval, the process proceeds to S314, and in the case of denial, the process proceeds to S313.

  In S313, the management server 120 transmits to the debtor terminal 130 that it cannot accept the occurrence record request received from the debtor terminal 130 in S301. In addition, when the occurrence record request is stored in the hold DB 206, the management server 120 deletes the data from the hold DB 206.

  In S314, management server 120 determines whether the data of the deliberation result indicates that an increase is allowed only this time, or indicates that a permanent increase of the extreme amount itself is allowed. If an increase is permitted for the current time only, the process proceeds to S315. On the other hand, if an increase in the extreme amount itself is permitted, the process proceeds to S316.

  In S <b> 315, the management server 120 reads the reservation request data 400 from the holding DB 206 when the occurrence designation date arrives, and transmits it to the electronic bond recording institution system 140. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. In another embodiment, the management server 120 reads the reservation request data 400 from the hold DB 206 and transmits it to the electronic bond recording institution system 140 at the time when the increase of the current time is recognized even if the occurrence specified date has not arrived. It can also be configured.

  In S316, management server 120 updates the amount information of the extreme amount of the debtor stored in condition DB 207 based on the data of the result of the request. Thereby, the obligor can generate an electronically recorded bond based on the updated extreme amount information.

  In S317, management server 120 reads reservation request data 400 from hold DB 206 when the occurrence designation date arrives, and transmits it to electronic bond recording institution system 140. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. In another embodiment, the management server 120 reads the reservation request data 400 from the hold DB 206 and transmits it to the electronic bond recording institution system 140 at the time when the extreme amount is updated even if the specified occurrence date has not arrived. You can also

  As described above, the method of controlling the extreme amount for each obligor has been described with reference to FIG. 3, but other embodiments can be adopted. For example, if a debtor generates an electronic record receivable for a specific counterparty every month, that is, if a debt is generated for a specific counterparty every month, that specific counterparty (creditor) It is also possible to set a monthly maximum amount every time. In such a case, identification of the extreme amount of the debtor in S302 and identification of the existing bond in S303 are performed for each creditor (creditor unit).

  In another embodiment, the number of occurrences of electronically recorded receivables that can be generated within a certain period (for example, a period that can be arbitrarily set by a transaction financial institution such as six months) is set for each debtor. Alternatively, it is possible to set the total amount of occurrence of electronic record receivables that can be generated within a certain period for each debtor.

  Next, with reference to FIG. 5, a processing flow related to a method for controlling the number or amount of electronically recorded claims generated within a certain period for each debtor executed by the management server 120 according to the present invention will be described. .

  In S <b> 501, the management server 120 receives an occurrence record request from the debtor terminal 130 and stores it in the hold DB 206. As another embodiment, the management server 120 may receive an occurrence record request from the debtor terminal 130 and process it in-memory without storing it in the hold DB 206. The generation record request may be a generation record reservation request as shown in FIG. 4 as an example. As shown in FIG. 4, the reservation request data 400 for occurrence records includes information such as debtor information, creditor information, amount of claims, designation date of occurrence, due date, payment method, and the like.

  In S502, the management server 120 reads the debtor information included in the received occurrence record request, and refers to the condition DB 207 based on the read debtor information for the debtor within a certain period (for example, monthly). Identify the maximum number or maximum amount of electronic record receivables that can occur within one month from the beginning of the month to the end of the month. The maximum number or amount of electronic record receivables that can be generated can be arbitrarily determined by the financial institution for each obligor, but in the explanation of this embodiment, it is assumed that only the maximum number is set for convenience. The explanation will be made assuming that the maximum number of debtors is four times a month (in April).

  In S503, the management server 120 identifies the existing electronic record receivable of the obligor, and the electronic record that has already been generated with the period designated as the occurrence designated date from the first day within the fixed period to the identification time. Identify the number of claims. Identification of an existing electronic record receivable can be performed by the management server 120 accessing the electronic receivable recording institution system 140 using the debtor's user number as a key. Alternatively, as another embodiment, the management server 120 downloads the data of the debtor's electronic record receivable from the electronic receivable recording institution system 140 in advance at a predetermined timing and stores the data in the management server 120. May be performed by accessing the data of the debtor's electronically recorded receivable in which is stored. In other words, any method may be used as long as the identification is performed based on the data of the debtor's electronic record receivable at a predetermined time. Furthermore, the identification of existing electronic record receivables may be not only the debtor's user number but also the debtor's user number and the branch and account units of the transaction financial institution. When using electronically recorded receivables with multiple accounts, the transaction financial institution should specify the amount of the obligor's receivable within the appropriate range from the whole to individual accounts for the same obligor. In addition, the identification of the existing electronic record receivable is to specify the electronic record receivable including the specified date of occurrence within a certain period.

  In addition, when the reservation request data 400 of the record of occurrence of the debtor is stored in the hold DB 206, the management server 120 also refers to the reservation request data 400 stored in the hold DB 206, and the debtor has already been generated. Identify the number of electronically recorded claims.

An example of an existing electronic record receivable of the identified debtor is shown below. In this example, the reservation request data 400 (occurrence designation date: 4/20) stored in the hold DB 206 does not exist.
(Record number) (Date specified) (Loan amount)
M000 4/1 \ 50,000
M001 4/5 \ 150,000
M002 4/10 \ 200,000
M003 4/15 \ 100,000

  In S504, the management server 120, if the generated record request received in S501 is transmitted to the electronic bond recording institution system 140 as it is and recorded as an generated record in the record book, the electronic record loan of the obligor is recorded. It is determined whether or not the number of cases exceeds the upper limit number of possible electronic record receivables identified in S502.

  In the example of FIG. 4, since the number of already generated electronic record receivables is four, if the occurrence record of the requested electronic record receivable is recorded in the record book as it is, the number of occurrences of the electronic record receivable is 5 Therefore, it is determined that the maximum number of electronic record receivables that can be generated by the debtor will be exceeded.

  As a result of the determination by the management server 120 as described above, if the upper limit number is exceeded, the process proceeds to S506. On the other hand, if the upper limit number is not exceeded, the process proceeds to S505.

  In S <b> 505, the management server 120 reads the reservation request data 400 from the hold DB 206 when the occurrence designation date arrives, and transmits it to the electronic bond recording institution system 140. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. Alternatively, if the occurrence record request received in S501 is not a request for reservation data 400 but a request to generate an occurrence record on the reception day, the management server 120 requests the occurrence record request immediately after the processing in S504. It transmits to the electronic bond recording institution system 140. When the upper limit number is not exceeded, the management server 120 reads the reservation request data 400 from the hold DB 206 and receives it in the electronic bond recording institution system 140 at the time when the generation record request is received even if the specified occurrence date has not arrived. It can also be set as the structure which transmits.

  Next, the processing after S506 executed when it is determined in S504 that the upper limit number is exceeded will be described.

  In S 506, the management server 120 sends an alert indicating that “the number of electronic record receivables that can be generated by the debtor exceeds the upper limit” to the output unit 205 (for example, for the administrator connected to the management server 120. Display via a display device such as a terminal display). When such an alert is displayed, the person in charge of the transaction financial institution creates approval data for the reservation request data 400 for “increase the upper limit number only for this time” and “increase the upper limit number per se”. To the approval server 110. At this time, the created approval data can be based on the result of discussion between the person in charge of the transaction financial institution in contact with the debtor.

  In S507, management server 120 receives the approval result data from approval server 110.

  In S508, the management server 120 determines whether the data of the deliberation result indicates approval or disapproval. In the case of approval, the process proceeds to S510, and in the case of denial, the process proceeds to S509.

  In S509, the management server 120 transmits to the debtor terminal 130 that it cannot accept the occurrence record request received from the debtor terminal 130 in S501. In addition, when the occurrence record request is stored in the hold DB 206, the management server 120 deletes the data from the hold DB 206.

  In S510, the management server 120 determines whether the data of the deliberation result indicates that an increase in the upper limit number is permitted only this time, or indicates that a permanent increase in the upper limit number itself is permitted. To do. If an increase in the upper limit number is recognized only in this time, the process proceeds to S511. On the other hand, if a permanent increase in the upper limit number itself is recognized, the process proceeds to S512.

  In S <b> 511, the management server 120 reads the reservation request data 400 from the hold DB 206 and transmits it to the electronic bond recording institution system 140 when the occurrence designation date arrives. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. The management server 120 is configured to read the reservation request data 400 from the hold DB 206 and transmit it to the electronic bond recording institution system 140 at the point in time when an increase frame for this time is permitted even if the occurrence specified date has not arrived. You can also

  In S512, management server 120 updates the upper limit number of electronic record receivables that can be generated by the obligor, which is stored in condition DB 207, based on the data of the deliberation result. Thereby, the obligor can generate an electronically recorded receivable based on the updated information on the maximum number of cases.

  In S513, the management server 120 reads the reservation request data 400 from the holding DB 206 when the occurrence designation date arrives, and transmits it to the electronic bond recording institution system 140. As a result, the electronic bond recording institution system 140 records the generated record in the record master book based on the reservation request data 400. The management server 120 can also be configured to read the reservation request data 400 from the hold DB 206 and transmit it to the electronic bond recording institution system 140 when the upper limit number is updated without the specified occurrence date. .

  As described above, the method of controlling the number of occurrences of electronic record receivables within a certain period for each obligor has been described, but other embodiments can be adopted. For example, once a record of occurrence of a debtor is recorded in a record book with a third party as a creditor, an electronically recorded credit may turn around and the debtor itself becomes a creditor. At that time, if the specified date of split transfer of electronically recorded receivables, in which the split transfer record is recorded with the obligor itself as the creditor (transferr), is included within a certain period subject to the determination of the occurrence record, It is also possible to identify an electronic record receivable by adding it to the number of existing electronic record receivables, assuming that an occurrence record request has been sent for electronic record receivables (so-called child receivables) generated by the split. This will count not only the parent receivable but also the child receivables of the electronically recorded receivables related to the split transfer with the debtor itself as the creditor. Even if it occurs, it is possible to control by the upper limit number set for each obligor in consideration of the child receivables.

  In the above description, the method for controlling the number of records of electronic record receivables within a certain period of time for the debtor has been described, but the method for controlling the amount of money generated is also the same. In S502, the management server 120 reads the debtor information included in the received occurrence record request, refers to the condition DB 207 based on the read debtor information, and can generate the debtor within a certain period of time. Identify the maximum amount of electronic record receivables. Although the transaction financial institution can arbitrarily determine the upper limit for each obligor, in the explanation of this embodiment, for convenience, when the upper limit of the obligor is 500,000 yen, in the example of FIG. Since the amount of receivables is ¥ 100,000, if the requested record of electronic record receivables is recorded in the record book as it is on 4/20, the total amount of receivables of electronic record receivables will be 600,000 yen, It is determined that the upper limit amount of 500,000 yen within a certain period of the debtor will be exceeded. The subsequent processing is the same as in the case of the number of cases. On the other hand, if the upper limit is not exceeded, the process proceeds to S505, and if the upper limit is exceeded, the process proceeds to S506. When the upper limit is exceeded, in S508, the management server 120 determines whether the approval result data indicates approval or not, and in the case of approval, the process proceeds to S510. As long as the upper limit is increased "," the upper limit itself is constantly increased "is taken.

  FIG. 6 is a functional block diagram of the management server 120 according to the present invention.

  The management server 120 includes a transmission / reception unit 601, a condition collation unit 602, an alert generation unit 603, a control unit 201, a hold DB 206, and a condition DB 207. The hold DB 206 and the condition DB 207 have the same functions as the hold DB 206 and the condition DB 207 described above with reference to FIG.

  The transmission / reception unit 601 transmits / receives data to / from other systems in the bank system 100 (for example, the approval system 110, the accounting system, the information system, etc.), the debtor terminal 130, and the electronic bond recording institution system 140.

  The condition matching unit 602 includes information on the maximum amount for each obligor acquired from the condition DB 207, information on the upper limit of the number of occurrences of electronic record receivables or the upper limit of the amount of occurrence for each obligor, and electronic receivables. Total amount of the debtor's outstanding electronic record receivables acquired from the recording organization system 140 (in real-time or pre-downloaded) and the total number of the debtor's already recorded electronic record receivables Are respectively compared, and it is determined whether or not the extreme amount or the upper limit value or the upper limit amount is exceeded. If necessary, the condition matching unit 602 can also use the reservation request data 400 of the electronically recorded bond read from the holding DB 206 for the comparison.

  The alert generation unit 603 described in S307 is an alert indicating that “currently exceeds the maximum amount but falls within the maximum on the specified date of occurrence”, and in S310, “exceeds the maximum amount at the present time and is generated. An alert indicating that it will not fall within the limit until the designated date arrives, and “the upper limit of the number of occurrences of electronic record receivables that can be generated by the debtor or the upper limit of the amount to be generated” described in S506 An alert indicating “over” is displayed via the output unit 205 (for example, a display device such as a display of a manager terminal connected to the management server 120). Moreover, the alert production | generation part 603 can also transmit these alerts to another system or apparatus (for example, debtor terminal 130).

  The control unit 201 acquires, from the condition DB 207, extreme amount information for each obligor or information on the upper limit value of the number of occurrences of electronically recorded receivables or the upper limit amount of the generated amount for each obligor. In addition, the control unit 201 accesses the electronic bond recording institution system 140 to identify the balance of the debt amount of the debtor's already recorded electronic record claims, or the number of the debtor's already recorded electronic record claims or the total amount of the generated amounts. To do. Further, the control unit 201 can access the electronic bond recording institution system 140 in advance at a predetermined timing, download the data of the debtor's electronic record bond, and store it in the management server 120.

  Furthermore, the control unit 201 stores the generated record request received from the debtor terminal 130 in the hold DB 206 or deletes the generated record request determined not to be transmitted to the electronic bond recording institution system 140 from the hold DB 206.

<Summary>
Although the principle of the present invention has been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the spirit of the present invention. Will understand. That is, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium.

100 Bank System 110 Approval Server 120 Management Server (Relay Server, Cooperation Server)
DESCRIPTION OF SYMBOLS 130 Debtor terminal 140 Electronic bond recording organization system 201 Control part 202 Main memory part 203 Auxiliary memory part 204 Interface (I / F) part 205 Output part 206 Reservation DB
207 Condition DB
210 Bus 601 Transmission / reception unit 602 Condition verification unit 603 Alert generation unit

Claims (11)

A method executed by a computer for controlling an amount of electronic record receivables for each debtor, the method comprising:
Identifying the maximum amount of electronically recorded receivables that can be generated for the debtor based on the debtor information included in the received accrual record request;
Identifying the debtor's claim amount by identifying the debtor's existing electronic record claim; and
Determining whether the debt amount of the debtor's electronic record receivable exceeds the identified extreme amount when the received occurrence record request is transmitted to an electronic receivables record institution system;
In response to the determination that the identified maximum amount has been exceeded, if an occurrence record of an electronic record claim is recorded on the date indicated by the received occurrence record request, the debtor's electronic record claim Determining whether or not the amount of receivables is within the identified extreme amount range;
When it is determined that the identified extreme amount is exceeded and it is determined that it does not fall within the range of the identified extreme amount, the received request for occurrence record is not accepted based on the received data of the deliberation result. Determining one of the following: temporarily increasing and receiving the extreme amount, and constantly increasing and receiving the extreme amount.   Identifying the maximum amount of electronically recorded receivables that may be incurred for the obligor, and identifying the obligor's receivable amount by identifying the obligor's existing electronically recorded receivables The method of claim 1, wherein the method is performed every time. The received occurrence record request is an occurrence record reservation request;
3. The method according to claim 2, wherein the reservation request for the occurrence record includes debtor information, creditor information, amount of claim, occurrence designation date, payment date, and settlement method information.   In the case where there is a reservation request for the occurrence record of the debtor that has already occurred, the method further comprises the step of adding the amount of credit indicated by the reservation request that has already occurred to the credit amount of the debtor specified. The method according to claim 3.   By identifying the debtor's electronic record receivable that is due prior to the specified date of occurrence indicated by the reservation request for the generated record, it falls within the identified maximum amount on the specified date of occurrence. 4. The method of claim 3, further comprising the step of determining whether or not.   Regarding the reservation request for the occurrence record, if it is determined that the identified extreme amount is exceeded and it is determined that it falls within the range of the identified extreme amount on the occurrence designated date, In response to the fact that the electronic record receivable is settled within the maximum amount due to the settlement on the due date, the method further comprises the step of transmitting the received request for occurrence record to the electronic receivable recording institution system. 4. A method according to claim 3, characterized in that   The method according to claim 1, wherein the identified extreme amount is set with respect to a cumulative amount of electronically recorded receivables generated during a certain period determined by the debtor's transaction financial institution.   When it is determined not to accept the received occurrence record request based on the received request result data, a message indicating that the received occurrence record request is not accepted is transmitted, and the received occurrence record request is The method of claim 2, further comprising the step of deleting.   The method further comprises the step of transmitting the received request for occurrence record to the electronic bond recording institution system when it is determined to temporarily increase and accept the extreme amount based on the received approval result data. The method according to claim 2. Based on the received approval result data, when it is determined to accept the increased amount,
Updating the amount information of the debtor's extreme amount;
3. The method of claim 2, further comprising the step of transmitting the received occurrence record request to an electronic bond recording agency system. A system that controls the amount of electronic record receivables generated by each debtor,
Means for identifying, based on debtor information included in the received accrual record request, an extreme amount of electronic record receivables that can be generated for the debtor;
Means for identifying the debtor's credit amount by identifying the debtor's existing electronic record claims;
Means for determining whether or not a debt amount of the debtor's electronic record receivable exceeds the identified extreme amount when the received occurrence record request is transmitted to an electronic receivable recording institution system;
In response to the determination that the identified maximum amount has been exceeded, if an occurrence record of an electronic record claim is recorded on the date indicated by the received occurrence record request, the debtor's electronic record claim Means for determining whether or not the amount of receivable is within the identified extreme amount range;
When it is determined that the identified extreme amount is exceeded and it is determined that it does not fall within the range of the identified extreme amount, the received request for occurrence record is not accepted based on the received data of the deliberation result. And means for determining one of temporarily increasing and receiving the extreme amount and constantly increasing and receiving the extreme amount.

Images