JP2014211711A - Electronic recording credit inter-account remittance settlement management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system and method of specifying electronic recording credit in which inter-account remittance settlement is carried out prior to payment date of credit, and electronic recording credit in which inter-account remittance settlement is determined not to be carried out.SOLUTION: An electronic credit record organization system includes: disclosure data request means to claim disclosure data; reception means to receive the disclosure data from the electronic credit record organization system corresponding to the claim; and disclosure data classification means to classify data on electronic recording credit in which inter-account remittance settlement is scheduled to be carried out from the disclosure data as settlement schedule data, and to classify data on electronic recording credit in which inter-account remittance settlement is determined not to be carried out as not-settlement schedule data.

Description

  The present invention relates to an electronically recorded receivable-account remittance settlement management system and an electronically recorded receivable account remittance settlement management method, and more particularly to an inter-account remittance settlement object prior to the due date of inter-account remittance settlement of an electronically recorded receivable account. Electronically recorded receivables (planned settlement) and electronically recorded receivables (non-settled) that are not subject to inter-account remittance settlement About.

  In June 2007, the Electronic Record Loan Act was enacted and promulgated, and was enforced in December 2008. Electronically recorded receivables are regarded as a requirement for the generation and transfer of receivables by electronically recording them in a record book of an electronic receivables recording organization (hereinafter referred to as a recording organization). Electronic record receivables, instead of conventional paper bills, are managed by a computer-certified electronic receivables record organization that manages the names of creditors and debtors, payment amounts, and due dates on a computer. It can be transferred and cashed. This not only promotes transaction security and liquidity of receivables, but also simplifies management operations through paperless bills.

  Electronically recorded receivables manage information on a computer, compared to conventional paper bills, avoiding the risk of loss or theft associated with paper bills, and cashing receivables before the settlement deadline Therefore, the effect of smoothing the funding of companies is also expected. Moreover, since electronically recorded receivables can be divided and transferred in addition to transactions at the face value, it is possible to respond flexibly, for example, by dividing only the necessary amount and cashing early (for example, , See Patent Document 1).

  The Electronic Record Claims Act presupposes that multiple recording institutions will be established from the viewpoint of ensuring user convenience. There are two main types of recording institutions: a recording agency established by a so-called mega bank and a recording agency established by the National Banking Association. The latter provides all bank participation services (hereinafter referred to as “Densai Net” (registered trademark)), and is only available through the contact of each financial institution.

  Payment of electronic record receivables using Densai Net is in principle made by payment between accounts. This settlement is automatically transferred from the debtor account to the creditor account when the payment date of the bond is reached.

  Specifically, Densai Net will provide settlement data (creditor's account information, payment amount, etc.) to the debtor's window financial institution, and the debtor's window will be paid when it becomes two bank business days before the due date. The institution starts preparation for inter-account remittance by the bank system provided by the financial institution.

  When the payment date is reached, the obligor's window financial institution remits the amount of the receivable payment to the creditor's window financial institution (in the banking system provided by the financial institution, the amount of payment from the obligor's account is The debited data that has been debited is generated, and the payment data is generated in which the payment amount of the receivable is credited to the creditor's account).

  Densai Net, which has received inter-account remittance settlement notices, records payments etc. after three bank business days of the due date, and extinguishes the electronically recorded receivables (in case of inability to pay)

  By the way, as a creditor, there is a need to know in advance the receivables to be settled. Also, from the standpoint of the debtor, for example, when the cause creditor whose debtor is the paying company owned by the creditor is forcibly executed, the debtor can confirm the fact that the debtor cannot perform remittance between accounts due to the creditor's circumstances. It is not always possible to grasp this, and it would be desirable to know at an early stage that it will become impossible to pay.

Japanese Patent No. 4201824 JP 2009-110125 A

  In the conventional inter-account remittance settlement for electronically recorded receivables, there was no sufficient means for creditors to grasp in advance the receivables to be settled. In addition, the debtor has sufficient means to grasp the fact before the inter-account remittance settlement, even though it has been determined in advance that the creditor will not be eligible for inter-account remittance settlement. Did not exist.

  According to Patent Document 2, when settlement of accounts receivable is made between accounts, it is possible to promptly deposit creditors into a deposit account by using settlement data relating to electronically recorded claims. If the creditor's causal claim is forcibly executed before the settlement data is created by Densai Net, the settlement data for the claim is not created. However, if the creditor's causal claim is forcibly executed after the settlement data is created, the existing banking system does not have information on the claim in advance even if it is determined that payment will not be possible before settlement. Therefore, it cannot be grasped.

  The present invention has been made in view of such a problem, and in an existing banking system, a recording institution is requested for disclosure data of information on a creditor or an obligor's electronic recording receivable, and based on the disclosed data A system that can identify electronically recorded receivables (scheduled for non-settlement) for which remittance between accounts has been completed before the due date of the receivable or that remittance between accounts is determined to be impossible It aims to provide a method. Regarding the debtor's electronically recorded receivable, the accuracy of specifying the electronically recorded receivable scheduled to be non-settled can be increased by further matching the disclosed data with the above-mentioned settlement data.

  In order to solve the above-mentioned problems, an electronically recorded receivable inter-account remittance settlement management system according to the present invention is connected to an electronic receivable recording institution system that manages a record book of electronic recorded receivables via a network, A computer system for managing inter-account remittance settlement, wherein the electronic receivables recording institution system requests disclosure data in the record base of electronic receivables whose specific date is the inter-account remittance settlement date. The disclosure data has information that can be determined that at least the inter-account remittance settlement of the electronically recorded receivable is not confirmed before the inter-account remittance settlement date. And a first receiving means for receiving the disclosed data from the electronic bond recording institution system and the inter-account remittance settlement in response to the request. Based on the information that can be determined that there is no confirmation before the inter-account remittance settlement date, from the disclosed data, the electronically recorded receivable that the inter-account remittance settlement is scheduled to be performed Characterized in that the data is classified as settlement schedule data, and disclosed data classification means for classifying data on electronically recorded receivables that are determined not to be repatriated between accounts as non-settlement schedule data. To do.

  According to the electronically recorded receivable-account remittance settlement management system according to the present invention, the electronically recorded receivable (disclosed due on the due date of the receivable) for the disclosure data acquired from the recording institution has been deleted and compulsory execution recorded. ) Is classified as non-settlement scheduled data, and the electronically recorded receivables subject to settlement are classified as settlement scheduled data on the due date of other receivables, without waiting for the due date Can be identified. In addition, for the debtor side, by matching the above disclosed data with the settlement data transmitted from the recording organization, the electronically recorded receivables that are determined to be non-settlement in advance will be issued before the due date. It is possible to identify the cause of the non-settlement schedule.

It is a figure which shows the example of the network structure of the remittance settlement management system between electronic record receivable accounts based on one Embodiment of this invention. It is a figure which shows the example of a structure of the remittance settlement management system between electronic recording receivable accounts based on one Embodiment of this invention. It is a figure which shows the example of the disclosure data which can be acquired from a recording organization by making a disclosure request to a recording organization based on one Embodiment of this invention. It is a figure which shows the example of the payment data transmitted from the recording organization based on one Embodiment of this invention. It is a figure which shows the example of the payment completed data transmitted from the bank system based on one Embodiment of this invention. It is a figure which shows the example of the withdrawal data transmitted from the bank system based on one Embodiment of this invention. The example of the user data storage part 700 of the remittance settlement management system 101 between electronic record receivable accounts based on one Embodiment of this invention is shown. The example of the payment result data memory | storage part 800 of the electronically recorded receivables account remittance payment management system 101 based on one Embodiment of this invention is shown. It is a flowchart which shows the example of a series of processes which the electronic payment receivable account remittance settlement management system based on one Embodiment of this invention performs. It is a flowchart which shows the example of a series of processes which the electronically recorded receivable account remittance settlement management system based on another embodiment of this invention performs. The example of the disclosure claim data which the electronic payment receivable account remittance settlement management system based on one Embodiment of this invention produces | generates is shown. It is a figure which shows the example of the payment failure notification data transmitted from the recording organization based on one Embodiment of this invention.

  Hereinafter, an electronically recorded receivable account remittance settlement management system according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram showing an example of a network configuration of an electronically recorded receivable-account remittance settlement management system 101 according to the present invention. In FIG. 1, an electronically recorded receivable-account remittance settlement management system 101 communicates via a network 102 with a “Densai Net” 103 provided by a recording organization that participates in all banks. Further, it communicates with a “bank system” 104 which is a conventional bank billing system via the network 105. Furthermore, it communicates with the client computer 106 which the user of the electronically recorded receivable account remittance settlement management system 101 uses via the network 107. Note that the bank providing the bank system 104 is a bank that handles accounts for performing inter-account remittance settlement of electronically recorded receivables recorded in the record book of the Densai Net 103.

  The Densai Net 103 is a system that records the generation and transfer of electronic record receivables, and includes an electronic record receivable DB that stores a record book for each electronic record receivable. Densai Net 103 extracts a claim record (managing an account designated by the creditor and / or debtor of the electronic record claim) from the electronic record claim DB two bank business days before the due date of the claim. , Generate payment data from the extracted records. The generated settlement data is transmitted to the electronically recorded receivable account remittance settlement management system 101 via the network 102. In addition, payment notification data is generated for electronically recorded receivables (unsettled electronically recorded receivables) for which remittance between accounts was not performed on the due date of receivables (for example, insufficient balance), and electronically recorded via network 102 This is sent to the inter-debt remittance settlement management system 101.

  The electronically recorded receivable inter-account remittance settlement management system 101 makes a disclosure request for making a request for disclosure of electronic receivables on the due date of payment to Densai Net 103 two bank business days before the due date of the receivables. Data is generated and the disclosure request data is transmitted to the Densai net 103 via the network 102. In response to receiving the disclosure request data, Densai Net 103 extracts from the electronic record receivable DB a receivable record with the account handled by the bank providing the bank system 104 as a settlement account, and the disclosed data is extracted from the extracted receivable record. Generate. The generated disclosure data is transmitted to the electronically recorded receivable account remittance settlement management system 101 via the network 102. Here, the disclosure data is information on the record book of receivables and payables handled by Densai Net 103, and each financial institution makes a disclosure request only for receivables and payables that have their bank account as a settlement account. Is allowed. In this embodiment, an example in which the recording institution is the Densai Net is shown, but the recording institution is not limited to the Densai Net, and may be a recording institution system provided by Megabank, for example.

  The bank system 104 is a system that provides bank accounting services that exist in the past. When the due date of the receivable is reached, the amount of the debt is deducted from the bank account of the debtor, and withdrawn data relating to the withdrawal is generated. Also, the credit amount is deposited in the creditor's account, and deposited data relating to the deposit is generated. Both the withdrawn data and the deposited data are transmitted to the electronically recorded receivable account remittance settlement management system 101 via the network 105. In the present embodiment, the bank system 104 is configured as a separate system from the electronically recorded receivable-account remittance settlement management system 101, but both may be configured as a single system.

  The client computer 106 is a terminal for inquiring the result of the electronic record receivable and / or the debt payment including the electronic record receivable to be non-settled, which is provided by the electronic record receivable inter-account remittance settlement management system 101. is there. In this embodiment, the client computer 106 for inquiring the execution result of the electronically recorded receivable-account remittance settlement management system 101 is taken as an example. However, the client computer 106 is not limited to the client computer, and for example, a mobile connected via a wireless network A computer device having a communication function such as a computer or a mobile phone may be used.

  Next, with reference to the block diagram of FIG. 2, the configuration of the above-described electronic record receivable account remittance settlement management system 101 will be described in detail. The electronically recorded receivable-account remittance settlement management system 101 includes a control unit 201, a main storage unit 203, an auxiliary storage unit 204, an input unit 205, an output unit 206, a database 207, and a network I / F 208. Connection is made via the bus 202.

  The control unit 201 is also called a central processing unit (CPU), performs control of each of the above-described constituent elements and data calculation, and reads various programs stored in the auxiliary storage unit 204 to the main storage unit 203 and executes them. To do. The main storage unit 203 is also called a main memory, and stores input data received by the electronically recorded receivable-account remittance settlement management system 101, computer-executable instructions, data after arithmetic processing by the instructions, and the like.

  The auxiliary storage unit 204 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. Since the main storage unit 203 has a relatively smaller storage capacity than the auxiliary storage unit 204, it is used for temporary data storage, arithmetic processing, and the like, whereas the auxiliary storage unit 204 stores necessary data and information. Used for long-term storage and preservation. That is, when the control unit 201 executes a program to perform data calculation, the necessary data or program is read from the auxiliary storage unit 204 to the main storage unit 203, and the calculation result data is stored and stored for a long time. To do so, the control unit 201 writes the calculation result data in the auxiliary storage unit 204. The database 207 includes database tables of a user data storage unit 700 and a settlement result data storage unit 800 described later.

  The network I / F 208 is an interface for communicating with the Densai net 103, the bank system 104, and the client computer 106, and communicates via each of the network I / Fs 211, 221 and 231.

  The Densai Net 103, the bank system 104, and the client computer 106 are ordinary computers having a processor, a memory, and the like. In addition to the function for connecting to the network, a storage device, an LCD, etc. However, the present invention is not limited to this, and various hardware known in this technical field can be built in or connected to the display device. In addition, an OS and various drivers or applications are installed in the computer, and various processes described later in the present embodiment are executed as a whole.

  Next, with reference to FIG. 3, an example of disclosed data provided by the recording organization is shown. As described above, the disclosure data is data for disclosing information about the record book recorded in the recording organization in response to a disclosure request from the bank. Since each bank is allowed to request disclosure of electronically recorded receivables with its bank account as the settlement account, electronic records are recorded every day from the two business days before the due date of the receivable until the due date. Request for disclosure is made from the receivable transfer management system 101 between receivable accounts to the recording institution (in this embodiment, Densai Net 103) (Disclosure request data is transmitted to Densai Net 103). Disclosure data is provided from Densai Net 103.

  Disclosure data includes “record number” for identifying electronic record receivables, “date of occurrence” for electronic record receivables, “date of payment” for electronic record receivables, “amount of receivables”, “unsettled amount” for electronic record receivables, electronic records “Number of transfers” that indicates the number of times the receivable has been transferred, “Number of times of division” that indicates the number of times that the electronically recorded receivable has been divided, “Presence of forced execution etc.” that indicates whether the electronically recorded receivable has been compulsorily executed, etc. “Restriction of transfer” indicating whether or not the receivable is restricted, “Receivable status classification” indicating the status of the electronically recorded receivable, “Unpaid reason” indicating whether or not the electronically receivable is insolvent, and Consists of “Possibility of opposition” indicating whether or not an opposition has been filed against electronically recorded receivables. For example, if an electronic record receivable is compulsorily executed, “1: Yes” is set in “Recorded compulsory execution”, and the electronic receivable Is not eligible for inter-account remittance. In addition, if settlement is completed before the inter-account remittance settlement, the “Receivable status classification” is set to “2: Disappeared”, and the electronically recorded receivable is also subject to inter-account remittance settlement even if the receivable due date is reached. It will not be. In this way, it is possible to determine that the electronically recorded receivables will not be repatriated between accounts on the due date by referring to the values of “Recorded compulsory execution” and “Debt status classification” in the disclosure data. In addition, the information is not limited to whether or not the forced execution is recorded or the credit status classification, and may include other information that can determine that the inter-account remittance settlement of the electronically recorded credit is not performed.

  Next, referring to FIG. 4, an example of settlement data provided from a recording institution is shown. The settlement data is information relating to the electronically recorded receivable that is provided by the recording institution and is subject to inter-account remittance settlement on the due date. When the payment date of the receivable is two bank business days before, the data of the electronically recorded receivable to be settled is provided from the recording institution to the bank that handles the debtor's account that is the subject of the inter-account remittance settlement.

  In the present embodiment, the Densai Net 103 extracts the electronic record receivable in which the bank account that provides the bank system 104 is designated as the debtor account from the electronic record receivable DB, and generates settlement data. The generated settlement data is transmitted to the electronically recorded receivable account remittance settlement management system 101 via the network 102. Settlement data includes “record number” for identifying electronically recorded receivables, “amount of receivables”, “payment date” for electronically receivables, “creditor code” for identifying creditors, and “financial institutions” which are creditor account information. Code ”,“ Branch Code ”,“ Account Type ”,“ Account Number ”,“ Account Holder ”,“ Debtor Code ”that identifies the debtor,“ Financial Institution Code ”that is the debtor's account information,“ Branch It consists of “code”, “account type”, “account number”, and “account holder”.

  Next, referring to FIG. 5, an example of deposited data transmitted from the bank system 104 to the electronically recorded receivable account remittance settlement management system 101 via the network 105 is shown. Deposited data is data relating to the deposit generated by the bank system 104 when the payment amount from the debtor is actually deposited into the creditor's account. The received data includes “EDI number (record number)”, “financial institution code”, “branch code”, “account type”, “account number”, “account name” that identifies the creditor and the target electronic record receivable. It consists of “person” and “payment amount”.

  Next, with reference to FIG. 6, an example of withdrawn data transmitted from the bank system 104 to the electronically recorded receivable account remittance settlement management system 101 via the network 105 is shown. The debited data is data relating to deduction generated by the bank system 104 when the payment amount is actually deducted from the debtor's account. The deducted data is “EDI number (record number)”, “financial institution code”, “branch code”, “account type”, “account number”, “account name” that identifies the debtor and the subject electronic record receivable. It consists of “person” and “deduction amount”.

  Next, an example of the user data storage unit 700 of the electronically recorded receivable-account remittance settlement management system 101 according to an embodiment of the present invention will be described with reference to FIG. In the present invention, for electronically recorded receivables that are subject to inter-account remittance settlement, data that the receivables have been extinguished before the due date (electronically recorded receivables that have been settled), or non-settlement schedules. The user data storage unit 700 is a database table used for specifying a creditor or a debtor of an electronic record loan to be extracted. That is, the electronic record receivable in which the user registered in the user data storage unit 700 is a creditor or a debtor is a target of processing executed by the electronic record receivable inter-account remittance settlement system 101 according to the present invention. The user data storage unit 700 may register all users who use a bank account providing the electronically recorded receivable account transfer and settlement system 101 as a creditor account or a debtor account. Only users who wish to receive services executed by the remittance settlement management system 101 may be registered.

  The user data storage unit 700 includes a “user code” for identifying a user, “financial institution code”, “branch code”, “account type,“ account number ”, and“ account holder ”for user account information. Is comprised.

  In this way, since the user to be processed by the electronically recorded receivable-account remittance settlement management system 101 according to the present invention is specified based on the record registered in the user data storage unit 700, For example, when there is a request to limit the service provided by the electronically recorded receivable-account remittance settlement management system 101 to some users, only some of those users are registered in the user data storage unit 700. Can be realized.

  Next, with reference to FIG. 8, an example of the settlement result data storage unit 800 of the electronically recorded receivable-account remittance settlement management system 101 according to an embodiment of the present invention is shown. The settlement result data storage unit is a database table that stores information relating to whether or not it is a target for inter-account remittance settlement, which will be described later, and whether or not inter-account remittance settlement has been performed on the due date of the receivable. Settlement result data storage unit is “Record number” for identifying electronic record receivables, “Receivable amount” for electronic record receivables, “Payment due date” for electronic record receivables, and whether electronic record receivables are subject to settlement on the due date "Settlement schedule" indicating that the electronic record receivable has been settled on the due date, or if the electronic record receivable is scheduled to be non-settled (not subject to settlement) on the due date It consists of “non-settlement reason” and “non-settlement reason” when electronic record receivables are not paid on the due date (unsettled receivables).

  Next, a series of processing executed by the electronically recorded receivable-account remittance settlement management system 101 according to an embodiment of the present invention will be described using the flowchart of FIG. This embodiment assumes batch processing, but is not limited to batch processing, and can be implemented by online processing or a combination of batch processing and online processing.

  As shown in FIG. 3, processing is executed on October 29, 2013, which is an electronically recorded receivable whose payment date is specified as October 31, 2013, two business days before the payment date. Shall.

  Since it is after two bank business days of the payment date of the receivable and before the date of the payment of the receivable (S901), the control unit 201 of the electronically recorded receivable account remittance settlement management system 101 stores the user data. A record is read from the part 700 (S902). The read user data is stored in the main storage unit 203. As described above, the user data storage unit 700 stores information related to a user (creditor) to be processed by the electronically recorded receivable-account remittance settlement management system 101 according to the present invention. A request for disclosure is made for all electronically recorded receivables whose creditor account is the user's account registered in the storage unit.

  Next, the control unit 201 generates disclosure request data based on the user data stored in the main storage unit 203 (S903). As shown in FIG. 11, the disclosure request data includes a “request number” for identifying a disclosure request, a “financial institution code”, a “branch code”, an “account type code”, “ "Account number", "Disclosure classification code" indicating the disclosure category, "Disclosure search method code" indicating the disclosure search method, "Position code" indicating whether the disclosure is related to the creditor or debtor, "Payment date (from)" ”,“ Payment date (to) ”and“ processing classification code ”indicating whether the processing is synchronous processing or asynchronous processing.

  In the item “request number”, an arbitrary value assigned by the electronically recorded receivable-account remittance settlement management system 101 is set. In the items “financial institution code”, “branch code”, “account type code”, and “account number” , The financial institution code, branch code, account type, account number, and account holder value of each record of the user data read in S902 are set. The item “Disclosure Classification Code” is “1: Disclosure of Recorded Items (User)”, “Disclosure Search Method Code” is “2: Position”, “Position Code” is “01: Creditor”, “Payment Date” “From” and “Payment due date (to)” are set to October 31, 2013, which is the payment due date, and “2: Asynchronous processing” is set to “Processing classification code”.

  Next, the control unit 201 transmits the disclosure request data generated in S903 to the Densai net 103 via the network I / F 208 (S904). When the Densai Net 103 receives the disclosure request data via the network I / F 211 (S905), it reads the disclosure request data one by one and sets the account included in each record of the disclosure request data as a creditor account. The electronic record receivable data to be extracted is extracted from the electronic record receivable DB, and the disclosed data as shown in FIG. 3 is generated (S906). Disclosure data is generated for each creditor account. For example, referring to FIG. 7, the financial institution code, branch code, account type, account number, and account holder included in the record stored in the user data storage unit 700 are “0009”, “261”, “1”, respectively. ”,“ 1234567 ”, and“ Yamada Taro ”, the electronic record receivable records in which the above-described values are set in the items of the account information in the electronic record receivable DB are extracted, and the payment date is October 31, 2013. The day is set.

  The densai net 103 transmits all of the disclosed data generated in S906 to the electronically recorded receivable-account remittance settlement management system 101 via the network I / F 211 (S907).

  The electronically recorded receivable-account remittance settlement management system 101 receives the disclosed data via the network I / F 208 (S908). The received disclosure data is stored in the main storage unit 203.

  Next, the control unit 201 reads the disclosed data stored in the main storage unit 203 and extracts valid data (S909). Disclosure data is data that has already been repatriated between accounts in the past (electronically recorded receivables with the same creditor number that have been repatriated between accounts in the past. ”) And data that has not yet been settled, for example, as shown in FIG. 3, data with a bond status classification of“ 1: existence ”is extracted as valid data. The valid data extracted in this way becomes data relating to the electronically recorded receivables scheduled to be settled on the due date of the receivables and the electronically recorded receivables scheduled to be non-settled. The extracted valid data is stored in the main storage unit 203. In this embodiment, as a method for extracting valid data, a record in which “1: existence” is set in the credit status category is extracted, but a corresponding date is set as the payment date of the credit. Nevertheless, in this embodiment (October 31, 2013), an electronically recorded receivable (with a receivable status classification of “2”) that is scheduled to be unsettled on the due date of the receivable has already been completed. : “Disappearance” data) is also extracted and managed, the data for the item “payment due date” of October 31, 2013 may be extracted from the disclosed data.

  Next, the control unit 201 inserts valid data stored in the main storage unit 203 into the settlement result data storage unit 800 (S910). In the items “record number”, “payment due date”, and “credit amount” of the settlement result data storage unit 800, values of the same items of valid data are set. In the item “settlement schedule”, “1: settlement schedule” indicating that the inter-account remittance settlement is scheduled to be performed on the due date is set. As the value of the item “settlement schedule”, “1” may be set in this step, or a value of “1” may be set as an initial value.

  Next, the control unit 201 reads valid data stored in the main storage unit 203 and extracts non-settlement scheduled data (S911). Here, the extraction of non-settlement schedule data is, for example, when the electronic record receivable is compulsorily executed, and the corresponding electronic record receivable is not subject to inter-account remittance settlement, as shown in FIG. Since a value such as “1: Yes” is set in “Presence / No Record of Forced Execution etc.” in the disclosed data, such data, that is, data relating to electronically recorded receivables that are not subject to settlement on the due date of the receivable is extracted (described above) As described above, data with the item “bond status classification” value of “2: disappearance” may be extracted from the valid data as non-settlement scheduled data). The data extracted in this manner can be classified as non-settlement schedule data, and the remaining valid data can be classified as settlement schedule data to be subject to inter-account remittance settlement on the due date. Settlement schedule data and non-settlement schedule data are stored in the main storage unit 203.

  In this way, according to the electronically recorded receivable-account remittance settlement management system 101 according to the present invention, by using the disclosed data, the non-settlement scheduled data and the settlement scheduled data are classified before the payment due date. Therefore, it is confirmed that the creditor who is the user of the electronically recorded receivable inter-account remittance settlement management system 101 is not subject to non-settlement in advance and the electronic receivable that is subject to inter-account remittance settlement on the due date. The electronic receivables that are available can be ascertained in advance.

  Next, the control unit 201 updates the record in the settlement result data storage unit 800 inserted in S910 corresponding to the non-settlement scheduled data stored in the main storage unit 203 (S912). For the electronically recorded receivable corresponding to the non-settlement scheduled data extracted in S911, since it has been determined in advance that inter-account remittance settlement will not be performed on the due date, the settlement result data storage unit 800 corresponding to the electronically recorded receivable The record is updated. Specifically, the non-settlement schedule data stored in the main storage unit 203 is read. A record in the settlement result data storage unit 800 is selected using a recording number included in the read non-settlement schedule data as a key. For the record in the selected settlement result data storage unit 800, “2” indicating that inter-account remittance settlement is not performed is set in the item “settlement schedule”. The item “non-settlement reason” has a value for identifying the cause of non-settlement schedule (in this embodiment, the cause loan is forcibly executed, in this case “1: forced execution”) Is set. After setting the above value, the settlement result data storage unit 800 is updated.

  In this way, before the due date of receivables, check whether the corresponding electronically recorded receivables are eligible for settlement, and register the planned payment status in the database, thereby transferring money between electronically recorded receivable accounts. A creditor who is a user of the payment management system 101 can check an electronically recorded credit that is scheduled to be settled on the due date (non-settlement scheduled) by referring to the record in the settlement result data storage unit 800 at any time. it can. For example, by inputting a user number from the client computer 106 connected to the remittance settlement management system 101 between electronic record receivable accounts, a record is extracted from the settlement result data storage unit 800 for the electronic record receivable of the user, and the network By transmitting the record to the client computer 106 via the I / F 208 and displaying it on the display unit (not shown) of the client computer 106, the user confirms the settlement schedule state of the corresponding electronic record receivable. can do.

  Next, the process returns to S901, and it is determined whether it is after the two bank business days of the payment due date and before the payment due date of the receivable (S901). It is determined that the date is later than the current date of the payment due date, and if it is not the current date of the payment due date, the processing of S902 to S912 described above is repeated. This means that the above process is repeated after two bank business days before the due date and before the due date. By repeating the process in this way, for example, even if it is an electronically recorded receivable that is scheduled to be settled two bank business days before the due date, it will be forcibly executed etc. on the day before the due date and become non-settled. It is possible to extract the electronically recorded receivables for which is confirmed as non-settlement scheduled data.

  When the payment date of the bond is reached (S913), the banked system 104 generates the deposited data (S914), and the deposited data is transferred via the network I / F 221 to the electronically recorded receivable account remittance settlement management system. 101. The deposited data is stored in the main storage unit 203.

  Next, the control unit 201 matches the settlement schedule data extracted in S911 with the deposited data, and confirms whether or not the account has actually been deposited for the settlement schedule data (S915). If the record number and EDI number (record number) match, and the amount of receivable matches the amount of money received by comparing the scheduled settlement data with the received data, the remittance settlement between accounts of the corresponding electronic record receivable Has been done. As shown in FIG. 5, the item “EDI number” of the received data corresponds to the first nine digits of the item “record number” of the disclosed data, and both are obtained by comparing the EDI number and the record number. Can be matched.

  Next, the control unit 201 extracts, as unsettled data, an electronically recorded receivable for which inter-account remittance settlement has not been performed as a result of matching in S915, and sets an electronically recorded receivable for which inter-account remittance settlement has been performed as settled data. Extract. The extracted settled data and unsettled data are stored in the main storage unit 203.

  The control unit 201 updates the record of the settlement result data storage unit 800 inserted in S910 corresponding to the settled data and unsettled data stored in the main storage unit 203 (S916). Based on the matching result in S915, it is determined whether or not the inter-account remittance settlement is actually performed for the corresponding electronic record receivable, and the settlement result is reflected in the settlement result data storage unit 800. Specifically, settled data and unsettled data stored in the main storage unit 203 are read. A record in the settlement result data storage unit 800 is selected using the record number included in the settled data and unsettled data read as a key. Of the records in the selected settlement result data storage unit 800, for the record extracted based on the record number of settled data, “1” indicating that the inter-account remittance settlement has been performed is displayed in the item “settlement result”. For the record set and extracted based on the record number of unsettled data, “2” indicating that inter-account remittance settlement has not been performed is set in the item “settlement result”. After setting the above value, the settlement result data storage unit 800 is updated.

  Next, the process returns to S901, where it is determined whether or not it is after two bank business days of the payment date and before the payment date of the receivable (S901), and the determination is “No”. And the process moves to S913, where it is determined whether or not it is the due date of the receivable, and if the determination is “No”, whether or not it is after 3 bank business days of the receivable due date. Is determined (S917). If it is determined in the above determination that the payment date is after 3 bank business days, Densai Net 103 generates non-payment notification data as shown in FIG. 12 (S918).

  The non-payable notification data is data relating to the electronically recorded receivable for which the receivable has not been paid, which is generated by the Densai Net 103 after the due date of the electronic receivable. Non-payment notice data includes “record number” for identifying electronically recorded receivables, “debt amount”, “payment due date” for the relevant receivable, “non-payment notice acceptance date” for accepting non-payment notice, and non-payment notice It is composed of “non-payment notice confirmation date”, “non-payment reason code” indicating the reason for non-payment, and “non-payment reason detail code” indicating the details of the reason.

  The Densai Net transmits the payment failure notification data generated in S918 to the electronically recorded receivable-account remittance settlement management system 101 via the network I / F 211 (S919). The electronically recorded receivable-account remittance settlement management system 101 receives the payment failure notification data via the network I / F 208 (S920). The received non-payment notification data is stored in the main storage unit 203.

  Next, the control unit 201 matches the payment failure notification data stored in the main storage unit 203 with the settled data and the unsettled data extracted in S915 and stored in the main storage unit 203 (S921). The matched payment failure notification data is stored in the main storage unit 203.

  The control unit 201 updates the record in the settlement result data storage unit 800 that matches in S921 and corresponds to the electronically recorded receivable of the insolvency notification data stored in the main storage unit 203 (S922). The settled data and unsettled data that match the insolvency notification data in S921 are data in which the corresponding electronic record receivable has not been paid on the due date of the receivable, and the item “non-payment reason code” of the insolvency notification data Since the reason for the unsettled payment can be specified by the value of, the reason for the insolvency is reflected in the record of the settlement result data storage unit 800 corresponding to the corresponding electronic record receivable. Specifically, the payment failure notification data stored in the main storage unit 203 is read. A record in the settlement result data storage unit 800 is selected by using the record number included in the read non-payment notification data as a key. In the selected record of the settlement result data storage unit 800, the item “non-payable reason code” in the non-payable notification data is set in the item “non-payable reason” of the corresponding electronic record receivable. After setting the above value, the settlement result data storage unit 800 is updated (S922).

  In this way, based on the value set in the insolvency notification data transmitted from the Densai Net 103, the settlement result data storage unit 800 corresponding to the electronic record receivable that has not been settled on the due date of the receivable is stored. Since the record non-payable reason code is updated, the reason why the electronic record receivable account remittance settlement management system 101 is unsettled on the due date can be managed.

  As described above, it is checked whether or not the corresponding electronic record receivable is actually settled on the due date of the receivable, and the state of the payment result and the insolvency notification data transmitted from the Densai Net 103 are stored in the database. The creditor who is a user of the electronically recorded receivable account remittance settlement management system 101 can always refer to the record in the settlement result data storage unit and confirm the settlement result of the corresponding electronically recorded receivable. Can do.

  Next, a series of processing executed by the electronically recorded receivable-account remittance settlement management system according to another embodiment of the present invention will be described using the flowchart of FIG.

  As shown in FIG. 3, processing is executed on October 29, 2013, for electronically recorded receivables with a due date of October 31, 2013, which is two bank business days before those due dates. And

  Since it is after the two bank business days of the due date of the receivable and before the due date of the receivable (S1001), Densai Net 103 has a due date of October 31, 2013, Settlement data is generated for electronically recorded receivables whose account is handled by a bank providing the recorded receivable account remittance settlement management system 101 (S1002). Assuming that the bank code of the bank that provides the electronically recorded receivable account remittance settlement management system 101 is “0009”, the financial institution code of the debtor information is “0009” from the electronically recorded receivable DB, and the payment date is 2013. Settlement data is generated by extracting the data on October 31.

  Next, the Densai net 103 transmits the settlement data generated in S1002 to the electronically recorded receivable-account remittance settlement management system 101 via the network I / F 211 (S1003). The electronically recorded receivable-account remittance settlement management system 101 receives settlement data via the network I / F 208 (S1004). The received payment data is stored in the main storage unit 203.

  Next, the control unit 201 of the electronically recorded receivable-account remittance settlement management system 101 merges the settlement data stored in the main storage unit 203 for each account information of the debtor. Then, the control unit 201 generates disclosure request data based on the merged payment data (S1005). As described above, the disclosure request data is configured in the format shown in FIG. 11, but the items “payment due date (from)” and “payment due date (to)” are set with the payment due date to be processed. , Items “financial institution code”, “branch code”, “account type”, “account number” and “account holder” are the financial institution code of the obligor information of the settlement data stored in the main storage unit 203, the branch The code, account type, account number, and account holder value are set, and the item “position code” is set to “02: debtor”. Since the setting values of the other items are the same as those described in S903, description thereof is omitted here.

  Next, the control unit 201 transmits the disclosure request data generated in S1005 to the Densai net 103 via the network I / F 208 (S1006). Upon receiving the disclosure request data via the network I / F 211 (S1007), the Densai Net 103 reads the disclosure request data one by one and corresponds to the account information included in the data record of the disclosure request data. 3 is extracted from the electronic record receivable DB, and the disclosed data as shown in FIG. 3 is generated (S1008). Disclosure data is generated for each debtor account. For example, referring to FIG. 4, the financial institution code, branch code, account type, account number, and account holder of the debtor account information of the settlement data are “0009”, “143”, “1”, “9999999999”, respectively. Since it is “Suzuki Jiro”, an electronic record receivable record in which the above-described value is set in each item of the account information in the electronic record receivable DB is extracted, and the date of October 31, 2013 is set as the payment date.

  The densai net 103 transmits all of the generated disclosure data to the electronically recorded receivable account remittance settlement management system 101 via the network I / F 211 (S1009).

  The electronically recorded receivable-account remittance settlement management system 101 receives the disclosed data via the network I / F 208 (S1010). The received disclosure data is stored in the main storage unit 203.

  Next, the control unit 201 reads the settlement data and the disclosure data stored in the main storage unit 203, and matches both records (S1011). Since the settlement data is merged for each debtor's account and the disclosure data is the data for each debtor's account, matching the two results in disclosure information about the electronically recorded receivables subject to inter-account remittance settlement. Can be tied.

  Next, the control unit 201 extracts settlement schedule data from the result of matching in S1011 (S1012). Here, since the settlement data is data on the electronically recorded receivable that is generated by Densai Net 103 and is scheduled to be settled on the due date of the receivable, the electronically recorded receivable of the settlement data that matches the disclosed data is The electronically recorded receivables scheduled to be settled on the due date, and the settlement data is extracted as the settlement scheduled data. The extracted payment schedule data is stored in the main storage unit 203.

  Next, the control unit 201 inserts the settlement schedule data stored in the main storage unit 203 into the settlement result data storage unit 800 (S1013). In the items “record number”, “payment date”, and “credit amount” of the settlement result data storage unit 800, values of the same items of the settlement scheduled data are set. In the item “settlement schedule”, “1” indicating that inter-account remittance settlement is scheduled to be performed on the due date is set.

  Next, the control unit 201 extracts non-settlement schedule data (S1014). Here, the non-settlement scheduled data is data in which it is determined that the electronically recorded receivable is not settled without waiting for the due date of the receivable, and disclosed data that does not match the settlement data as a result of matching in S1011 , And the payment data, but the disclosure data item “Forcible Execution Execution Recorded” is set to a value such as “1: Yes” (electronically recorded receivables that have been forcibly executed) Extract as data. The extracted non-settlement schedule data is stored in the main storage unit 203.

  In this way, according to the electronically recorded receivable-account remittance settlement management system 101 according to the present invention, using the disclosed data and the settlement data, the electronically-recorded receivable subject to inter-account remittance settlement before the due date. , And the electronically recorded receivables that are determined not to be subject to inter-account remittance settlement in advance can be identified, so that the debtor who is the user of the electronic receivable inter-account remittance settlement management system 101 It is possible to ascertain electronic record receivables that are subject to inter-account remittance and electronic record receivables that are not eligible.

  Next, the control unit 201 updates the record of the settlement result data storage unit 800 inserted in S1013 corresponding to the non-settlement schedule data stored in the main storage unit 203 or stores the non-settlement schedule data in the settlement result data storage. It is inserted into the part 800 (S1015). For the electronically recorded receivable corresponding to the non-settlement scheduled data extracted in S1014, it has been determined in advance that the inter-account remittance settlement will not be performed on the due date, so that the settlement result data storage unit 800 corresponding to the electronically recorded receivable The record is updated. Specifically, the non-settlement schedule data stored in the main storage unit 203 is read. A record in the settlement result data storage unit 800 is selected using a recording number included in the read non-settlement schedule data as a key. For the record in the selected settlement result data storage unit 800, “2” indicating that inter-account remittance settlement is not performed is set in the item “settlement schedule”. The item “reason for non-settlement” is set with a value indicating the cause of non-settlement (in this embodiment, the cause loan is forcibly executed, in this case “1”). In addition, as a result of selecting a record in the settlement result data storage unit 800 using the record number described above as a key, if there is no corresponding record (a record in which the disclosed data and the settlement data are not matched in S1011), a record of non-settlement scheduled data A record is inserted into the settlement result data storage unit 800 based on the value of. Since the setting values of each item of the record to be inserted are as described above, the description is omitted. After setting the above value, the settlement result data storage unit 800 is updated.

  In this way, before the due date of receivables, it is checked whether the electronically recorded receivables are scheduled to be settled, and the settlement schedule status is registered in the database, thereby managing remittance settlement between electronically recorded receivable accounts. A debtor who is a user of the system 101 can check an electronically recorded bond that is scheduled to be settled on the due date (non-settled) by referring to the record in the settlement result data storage unit 800 at any time. For example, by inputting the debtor's user number from the client computer 106 connected to the electronically recorded receivable-account remittance settlement management system 101, a record is extracted from the settlement result data storage unit 800 for the electronic recorded receivable of the user. Then, the user transmits the record to the client computer 106 via the network I / F 208 and displays the record on the display unit (not shown) of the client computer 106. The state of can be confirmed.

  Next, it is determined whether or not it is the current date of payment (S1016), and if it is not the current date of payment, the process returns to S1005. That is, it is determined that it is after the two bank business days of the due date and not the due date, and if it is not the due date, the above-described processing of S1005 to S1015 is repeated until the day before the due date. By repeating the process in this way, for example, even if a settlement is scheduled two business days before the due date, an electronic record has been confirmed that forced execution etc. has been recorded the day before the due date and that it is scheduled to be non-settled It is possible to grasp that the receivables are also scheduled for non-settlement in advance.

  Next, when the due date of the receivable is reached (S1016), the bank system 104 generates debited data (S1017), and the debited data is transferred to the electronically recorded receivable account via the network I / F 221. It is transmitted to the management system 101. The withdrawn data is stored in the main storage unit 203.

  Next, the control unit 201 performs matching between the settlement schedule data extracted in S1012 and stored in the main storage unit 203 with the withdrawn data, and whether or not an account has actually been deducted for the settlement schedule data. Confirmation is performed (S1018). If the record number and EDI number match when the scheduled payment data and the debited data match, and the amount of the receivable matches the amount of the debit, the remittance settlement between the accounts of the corresponding electronically recorded receivable was performed. It will be. As shown in FIG. 4 and FIG. 6, the bank code, branch code, account type, account number, and account holder of the debited data are the bank code, branch code, and account type, which are debtor account information of the settlement scheduled data. It corresponds to the account number and account holder, and matching of both data becomes possible by comparing those items.

  Next, the control unit 201 extracts, as unsettled data, an electronically recorded receivable for which inter-account remittance settlement has not been performed as a result of the matching in S1018, and sets an electronically recorded receivable for which inter-account remittance settlement has been performed as settled data. Extract. The extracted settled data and unsettled data are stored in the main storage unit 203.

  Next, the control unit 201 updates the record of the settlement result data storage unit 800 inserted in S1013 corresponding to the settled data and unsettled data stored in the main storage unit 203 (S1019). This is because the result of matching in S1018 determines whether or not the inter-account remittance settlement has actually been performed for the corresponding electronic record receivable, so that the settlement result is reflected in the settlement result data. Specifically, settled data and unsettled data stored in the main storage unit 203 are read. A record in the settlement result data storage unit 800 is selected using the record number included in the settled data and unsettled data read as a key. Of the records in the selected settlement result data storage unit 800, for the record extracted based on the record number of settled data, “1” indicating that the inter-account remittance settlement has been performed is displayed in the item “settlement result”. For the record set and extracted based on the record number of unsettled data, “2” indicating that inter-account remittance settlement has not been performed is set in the item “settlement result”. After setting the above value, the settlement result data storage unit 800 is updated.

  Next, the process returns to S1001, and it is determined whether it is after the two bank business days of the payment due date and before the payment due date of the receivable (S1001). When the determination is made, the process proceeds to S1020, and it is determined whether or not it is after 3 bank business days of the payment date of the receivable (S1021). If it is determined in the above determination that the payment date is after three bank business days, Densai Net generates non-payment notification data as shown in FIG. 12 (S1022).

  Densai Net transmits the payment failure notification data generated in S1022 to the electronically recorded receivable-account remittance settlement management system 101 via the network I / F 211 (S1023). The electronically recorded receivable-account remittance settlement management system 101 receives non-payment notification data via the network I / F 208 (S1024). The received non-payment notification data is stored in the main storage unit 203.

  Next, the control unit 201 matches the payment failure notification data stored in the main storage unit 203 with the settled data and unsettled data extracted in S1018 and stored in the main storage unit 203 (S1025). The matched non-payment notification data is stored in the main storage unit 203.

  The control unit 201 updates the record in the settlement result data storage unit 800 that matches in S1025 and corresponds to the electronically recorded receivable of the insolvency notification data stored in the main storage unit 203 (S1026). Specifically, the payment failure notification data stored in the main storage unit 203 is read. A record in the settlement result data storage unit 800 is selected by using the record number included in the read non-payment notification data as a key. In the selected record of the settlement result data storage unit 800, the item “non-payable reason code” in the non-payable notification data is set in the item “non-payable reason” of the corresponding electronic record receivable. After setting the above value, the settlement result data storage unit 800 is updated.

  In this way, by checking whether or not the corresponding electronic record receivable has actually been settled on the due date of the receivable, and registering the state of the payment result in the database, the remittance settlement management system 101 between electronic record receivable accounts. The obligor who is the user can always confirm the settlement result of the corresponding electronic record receivable by referring to the record in the settlement result data storage unit.

  As described above, the description of the electronically recorded receivable-account remittance settlement management system according to the present invention has been described in detail. Specific data structures such as disclosed data and the user data storage unit 700 described in the embodiment are illustrative. However, the present invention may be modified without departing from the scope of claims.

102 Network 105 Network 107 Network 202 System Bus

In order to solve the above-mentioned problems, an electronically recorded receivable inter-account remittance settlement management system according to the present invention is connected to an electronic receivable recording institution system that manages a record book of electronic recorded receivables via a network, A computer system for managing inter-account remittance settlement, wherein the electronic receivables recording institution system requests disclosure data in the record base of electronic receivables whose specific date is the inter-account remittance settlement date. The disclosure data includes disclosure data requesting means having information indicating presence / absence of the electronic record receivable or information indicating presence / absence of compulsory execution of the electronic record receivable; first receiving means for receiving the disclosure data from creditor recording engine system, wherein the information indicating the presence or absence of electronic records receivable, or the electronic SL Based on the information indicating the enforcement presence receivables, from the disclosure data, classifies the data for the electronic recording receivables is scheduled to the remittance between settlement occurs as payment schedule data, the remittance between settlement is performed Disclosed data classification means for classifying data on electronic record receivables that have not been determined as non-settlement scheduled data.

Claims (12)

A computer system connected to an electronic bond recording institution system for managing a record ledger of electronic record receivables and a remittance settlement between accounts of electronic record receivables via a network,
Disclosure data requesting means for requesting disclosure data of a record base of an electronic record receivable having a specific date as an inter-account remittance settlement date to the electronic receivable recording institution system, wherein the disclosed data includes at least the electronic record receivable Having the information that can be determined that the inter-account remittance settlement is not performed before the inter-account remittance settlement date,
In response to the claim, a first receiving means for receiving the disclosed data from the electronic bond recording agency system;
Based on the information that can be determined that the inter-account remittance settlement is not performed before the inter-account remittance settlement date, the inter-account remittance settlement is performed from the disclosed data. Disclosure data classification that classifies data on electronically recorded receivables that are scheduled to be settled as scheduled payment data, and classifies data on electronically recorded receivables that are determined not to be repaid between accounts as non-settled scheduled data And a computer system. A first database storing information relating to the creditor account and / or the debtor account of the electronically recorded receivable;
The computer system according to claim 1, wherein the disclosure data requesting unit requests the disclosure data for each creditor's account or debtor's account based on the first database. A second database storing information relating to the inter-account remittance settlement;
A first data storage means for storing the settlement schedule data and the non-settlement schedule data in the second database, the settlement schedule data and the non-settlement schedule data stored in the second database. Identifies that the inter-account remittance settlement is scheduled to be performed on the inter-account remittance settlement date and that the inter-account remittance settlement is not performed on the inter-account remittance settlement date. The computer system according to any one of claims 1 and 2, further comprising: The computer system is connected to a billing system via a network,
A second receiving means for receiving, from the account system, received data indicating that the amount of the electronically recorded receivable has been deposited on the creditor account on the inter-account remittance settlement date;
Data comparison means for comparing the deposited data and the settlement schedule data;
Based on the comparison between the deposited data and the settlement schedule data, the data regarding the electronically recorded receivables for which the inter-bank remittance settlement was performed on the inter-account remittance settlement date is classified as settled data from the settlement schedule data. And a settlement schedule data classification means for classifying data on electronically recorded receivables for which the inter-account remittance settlement has not been performed on the inter-account remittance settlement date as unsettled data. 4. The computer system according to any one of 3. A second data storage means for storing the settled data and the unsettled data in the second database, wherein the settled data and the unsettled data stored in the second database are respectively It is further possible to identify that the inter-account remittance settlement was performed on the inter-account remittance settlement date and that the inter-account remittance settlement was not performed on the inter-account remittance settlement date. The computer system according to claim 4. Second receiving means for receiving payment data having information related to inter-account remittance payment from the electronic bond recording institution system;
A first data comparison means for comparing the disclosed data with the payment data;
The disclosed data classifying means is further configured to perform electronic receivables for which inter-account remittance settlement is scheduled to be performed from the disclosed data based on the comparison between the disclosed data and the settlement data by the first data comparing means. The data on the electronically recorded receivables for which it is determined that the inter-account remittance settlement is not performed is classified as non-settlement scheduled data. Computer system. A database that stores information about payments between accounts,
1st data storage means for storing the settlement schedule data and the non-settlement schedule data in the database, wherein the settlement schedule data and the non-settlement schedule data stored in the database are respectively remittance between accounts. It is possible to identify that the inter-account remittance settlement is scheduled to be performed on the settlement date and that it is confirmed that the inter-account remittance settlement is not performed on the inter-account remittance settlement date. The computer system according to claim 6, further comprising: The computer system is connected to a billing system via a network,
A third receiving means for receiving, from the account system, debited data indicating that the electronically recorded receivable amount has been deducted from the debtor account on the inter-account remittance settlement date;
A second data comparing means for comparing the withdrawn data and the settlement schedule data;
Based on the comparison between the withdrawn data and the settlement schedule data, the data regarding the electronically recorded receivables for which the inter-bank remittance settlement was performed on the inter-account remittance settlement date is classified as settled data from the settlement schedule data And a settlement schedule data classification means for classifying data on electronically recorded receivables for which the inter-account remittance settlement has not been performed on the inter-account remittance settlement date as unsettled data. 8. The computer system according to any one of 7. A second data storage means for storing the settled data and the unsettled data in the database, wherein the settled data and the unsettled data stored in the database are each the inter-account remittance settlement date; 9. The method of claim 8, further comprising: identifying that the inter-account remittance settlement has been performed and that the inter-account remittance settlement has not been performed on the inter-account remittance settlement date. The computer system described. A method for managing remittance settlement between accounts of electronic record receivables, which is executed by a computer connected via a network and an electronic receivables record institution system for managing a record ledger of electronic record receivables,
Requesting the electronic receivables recording institution system for disclosure data of the record base of electronic receivables with a specific date as the date of transfer between accounts, wherein the disclosed data is at least between the accounts of the electronic receivables Having information capable of determining that remittance settlement is not confirmed before the inter-account remittance settlement date;
Receiving the disclosure data from the electronic bond recorder system in response to the claim;
Based on the information that can be determined that the inter-account remittance settlement is not performed before the inter-account remittance settlement date, from the disclosed data,
Classifying data about electronically recorded receivables for which inter-account remittance settlement is to be performed as settlement scheduled data;
Classifying data on electronically recorded receivables for which it is determined that inter-account remittance is not performed as non-settlement scheduled data. Receiving settlement data having information related to the inter-account remittance settlement from the electronic bond recording institution system;
Comparing the disclosed data with the payment data,
The method according to claim 10, wherein the step of classifying as the settlement schedule data and the step of classifying as the non-settlement schedule data are further performed based on a comparison between the disclosure data and the settlement data.   The program for making a computer perform the method as described in any one of Claim 10 or 11.

Images