JP6018690B1 - Installment payment electronic record receivable management system - Google Patents

Abstract

Electronic record receivables by installment payment are managed. A step of receiving an electronic record receivable request message, generating a plurality of electronic record receivable data based on the generated record request request message, and corresponding to each of the plurality of electronic record receivable data A plurality of electronic record receivable occurrence record request data files; a plurality of electronic record receivable occurrence record request data files; a plurality of electronic record receivable occurrence record request data files; Receiving the electronic record loan occurrence record result data file and assigning a record number to each of the plurality of electronic record bond data. [Selection] Figure 3

Description

  The present invention relates to an installment payment electronic record receivable management system and an installment payment electronic record receivable management method, and more particularly to an installment payment electronic record receivable management system and an installment for managing a plurality of electronic record receivables as a set of installment electronic record receivables. The present invention relates to a method for managing electronic payment receivables.

  In December 2008, the Electronic Record Claims Law was enacted, and new monetary claims (electronic record claims) different from existing nominated claims and bills claims can be used. With this electronically recorded receivable, businesses can safely and easily and quickly generate and transfer such receivables by making electronic records on the Internet (PC) or FAX for payment of receivables arising from inter-company transactions. Can be done.

  In order to generate electronic record receivables, it is necessary to register them in a record ledger held by an electronic receivable recording institution established by the National Bank Association. This registration must be done through a system provided by the Zengin Electronic Bond Network (so-called “Densai Net”). Densai Net has a thorough common specification because it is commonly used by financial institutions nationwide. However, when using electronically recorded receivables, it is necessary to follow that specification.

  For the above-mentioned electronic record receivables, the maximum period (payment site) from the date of occurrence recorded in the occurrence record (electronic record date of occurrence record, that is, the date on which the electronic record receivable takes effect) to the due date ) Will be extended from “1 year” to “10 years”. This makes it possible to make payments using electronically recorded receivables even when the payment site conducts a long-term transaction due to capital investment or the like.

“Mechanism and Practice of Electronic Credit Recorder System”, [online], Zengin Electronic Credit Network, June 13, 2013, [Search Date: October 22, 2015], Internet <URL: http: //web.archive.org/web/20130619221522/http://www.densai.net/pdf/Pamphlet.pdf>

  By the way, when a business operator makes capital investment, the leasing company purchases equipment on behalf of the business operator, and the business operator repays the equipment purchase cost by installment payment such as monthly installment to the leasing company. Yes. As described above, when the payment site for electronic record receivables is extended to 10 years, it is expected that electronic record receivables will be used for payment of equipment purchase costs between businesses and leasing companies.

  Electronically recorded receivables do not have the concept of “installment payments” and can only generate a single electronically recorded receivable and change its due date. In other words, multiple payments cannot be made with electronically recorded receivables. When an electronic record receivable is issued, a request is made through a system provided by a financial institution that has partnered with the electronic receivables recording organization (hereinafter referred to as “the contact financial institution”), but it is ultimately generated against Densai Net The recording request data file is transmitted, and Densai Net creates an occurrence recording result data file. For this reason, the mechanism for requesting occurrence is dependent on the specifications of Densai Net. For this reason, as long as electronically recorded receivables do not have the concept of “installment payments”, the present system cannot manage installment payments for electronically recorded receivables.

  The present invention has been made in view of such a problem, and an object thereof is to provide an installment payment electronic record receivable management system that makes it possible to generate an electronic record receivable by installment payment.

  In order to solve the above problems, an installment payment electronic record receivable management system according to the present invention is a method executed by a server computer for managing electronic record receivables by installment payment, the server computer comprising: Connected to an electronic bond recording institution system and a client computer, and receiving from the client computer an electronic record receivable generation record request request message, wherein the generated record request request message is a claim amount of the electronic record receivable, A step including the number of payments, a payment period, and / or an installment payment amount, and a step of generating a plurality of electronic record bond data based on the received occurrence record request request message, the plurality of generated electronic The recorded bond data has a common identification number and the plurality of generated electronic record bond data. Each having a due date assigned a different date within the payment period, and a plurality of electronic record receivable occurrence record request data files respectively corresponding to the generated plurality of electronic record receivable data A step of creating, a step of transmitting the created plurality of electronic record bond occurrence record request data files to the electronic bond record agency system, and a plurality of electronic record bond occurrence records transmitted from the electronic bond record agency system Receiving a plurality of electronic record receivable occurrence record result data files corresponding to each of the billing data files, and generating the record numbers assigned to each of the received plurality of electronic record receivable occurrence record result data files Assigning to each of the plurality of electronically recorded bond data It is characterized in.

  According to the installment payment electronic record receivable management system according to the present invention, by handling a plurality of electronic record receivables as a set of electronic record receivables, it is possible to generate, change and manage electronic record receivables by installment payment.

It is a figure which shows the example of the whole structure of the installment payment electronic recording receivable management system based on one Embodiment of this invention. It is a figure which shows the example of a structure of the installment payment electronic recording receivable management apparatus based on one Embodiment of this invention. It is a flowchart which shows the process of generation | occurrence | production record request of an installment payment electronic record receivable which the installment payment electronic record receivable management system which concerns on one Embodiment of this invention performs. It is a figure which shows the example of a user data table based on one Embodiment of this invention. It is a figure which shows the example of the electronic record bond generation | occurrence | production record request request | requirement message input interface based on one Embodiment of this invention. It is a figure which shows the example of the installment payment electronic recording bond data table based on one Embodiment of this invention. It is a figure which shows the example of the electronic record bond generation | occurrence | production record request acceptance message input interface based on one Embodiment of this invention. It is a flowchart which shows the process of the change record request of an installment payment electronic record receivable which the installment payment electronic record receivable management system which concerns on one Embodiment of this invention performs. It is a figure which shows the example of the electronic record bond change recording request message | telegram input interface data input interface based on one Embodiment of this invention. It is a figure which shows the example which updates the installment payment electronic recording bond data table shown in FIG.

  Hereinafter, an installment payment electronic record receivable 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 the configuration of the entire installment payment electronic record receivable management system according to the present invention. In FIG. 1, an installment payment electronic record receivable management apparatus 101 is connected to an electronic receivable recording institution system 103 via a network 102 such as a dedicated line. The installment payment electronic record receivable management apparatus 101 is connected to a creditor terminal 105 and a debtor terminal 106 via a network 104 such as the Internet.

  The installment payment electronic record receivable management apparatus 101 is a main apparatus that provides a service related to the installment payment electronic record receivable management system according to the present invention (hereinafter, “installment payment electronic record receivable management service”). Established and managed at financial institutions that provide debt management services (hereinafter referred to as “service-providing financial institutions”). Installment payment electronic record receivable management apparatus 101, when there is an occurrence record request for electronic record receivable (hereinafter referred to as "installment payment electronic record receivable") by installment payment from a user, a plurality of occurrence record request data files having a common format And the occurrence record request data file is transmitted to the electronic bond recording institution system 103. Further, the installment payment electronic record receivable management apparatus 101 receives a plurality of generated record result data files corresponding to the transmitted generated record request data files from the electronic bond recording institution system 103. Note that the installment payment electronic record receivable management apparatus 101 may be implemented alone or may be implemented by a server or host of a bank system that provides a bank accounting service that exists in the past. Further, the installment payment electronic record receivable management apparatus 101 may be implemented by a single computing device, or may be implemented by being distributed over a plurality of computing devices.

  The electronic bond recording institution system 103 is a densai net provided by an electronic bond recording institution established by the National Bank Association. The electronic bond recording institution system 103 is a system that records generation, transfer, etc. of an electronic record bond, and includes an electronic record bond database that stores a record book for each electronic record bond. Upon receipt of the generated record request data file from the installment payment electronic record receivable management apparatus 101, the electronic bond record institution system 103 adds the corresponding record book record to the electronic record claim database (by adding to this record book, the electronic record claim database is added). The occurrence record result data file relating to the occurrence record is created and transmitted to the installment payment electronic record receivable management apparatus 101.

  The creditor terminal 105 is a client computer terminal possessed by a creditor who uses a service related to the installment payment electronic recording claim management system according to the present invention. The creditor terminal 105 displays an input interface provided by the installment payment electronic record bond management system. On the input interface, for example, when an electronically recorded bond is generated by a request from a creditor (creditor billing method), the creditor inputs information necessary for making a request for record of occurrence.

  The debtor terminal 106 is a client computer terminal possessed by a debtor who uses a service related to the installment payment electronic record receivable management system according to the present invention. The debtor terminal 106 displays an input interface provided by the installment payment electronic record receivable management system. On the input interface, for example, in the case of a creditor billing method, information necessary for giving consent to a record request by a creditor is input.

  The input interface may be installed on the creditor terminal 105 and the debtor terminal 106, or may be a WEB screen transmitted from the installment payment electronic recording bond management apparatus 101. In addition, the occurrence record request may be a debtor request method in which an electronic record receivable is generated by a request from the debtor.

  The creditor terminal 105 and the debtor terminal 106 described above may be information communication terminal devices such as a personal computer, a workstation, and a PDA having a communication function. A computing device and an information communication terminal device are a computing device including a central processing unit (CPU), a memory, a storage device, and the like, and are integrated by a CPU processing a computer program stored in the memory or the storage device. The functions according to the present invention can be executed and the functions can be realized. Note that the above-described system configuration is for illustration, and does not limit the system configuration capable of executing the present invention.

  Next, with reference to the block diagram of FIG. 2, the configuration of the above-described installment payment electronic record receivable management apparatus 101 will be described in detail. The installment payment electronic record receivable management apparatus 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 network I / F 207, and a database 208, each of which is a system. They are connected via a bus 202.

  The control unit 201 is also called a central processing unit (CPU), and controls each of the above components and calculates data. Further, the control unit 201 reads out various programs stored in the auxiliary storage unit 204 for executing various processes according to the present embodiment to the main storage unit 203 and executes them. The main storage unit 203 is also called a main memory, and stores input data received by the installment payment electronic record receivable management apparatus 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 input unit 205 receives input information from the creditor terminal 105 and the debtor terminal 106 via the network I / F 207. Also, the generated record result data file transmitted from the electronic bond recording institution system 103 is received via the network I / F 207.

  The output unit 206 outputs an occurrence record request data file in response to receiving input of settlement account information from the creditor terminal 105.

  The database 208 includes a database table such as an installment payment electronic recording bond data table to be described later.

  Next, with reference to FIG. 3, a description will be given of the process of requesting a record of occurrence payment electronic record receivable executed by the installment payment electronic record receivable management system according to the present invention. In the present embodiment, it is assumed that when a business operator makes a capital investment, the equipment is purchased through a leasing company. Installment payment electronic record receivable shall be generated by creditor claim method with lender as creditor and business as debtor. In addition, both creditors and debtors will use electronically-recorded receivables with the service providing financial institution as a window.

  The creditor who becomes the requester of the occurrence record inputs the user number of the creditor and the user number of the other party (debtor) from an input interface (not shown) displayed on the display unit of the creditor terminal 105. Here, the user number is a number for identifying each user in the installment payment electronic record receivable management system according to the present invention. For example, the user number may be given by the electronic receivable recording institution system 103. However, it is not limited to that number. In this embodiment, it is assumed that the creditor and the debtor have their user numbers registered in the electronic bond recording institution system 103. The entered user number is transmitted from the creditor terminal 105 to the installment payment electronic record credit management device 101 (step S301).

  The input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the user number transmitted in step S301, and the control unit 201 reads the user data record from the user data table 400 based on the user number. Is acquired (step S302).

  FIG. 4 shows an example of the user data table 400. In the present embodiment, it is assumed that both creditors and debtors are registered in the user data table 400. No. 1 record is a creditor user data record, No. Record 2 is a debtor user data record. The user data table 400 is a database table that stores information about users registered in the installment payment electronic record receivable management system according to the present invention, and includes user numbers, user names, and account information used for settlement ( Payment account information), and terminal address. The terminal address is the IP address of the computer terminal possessed by the user. 1, the address of the debtor terminal 106 is No. 1. 2 records are set respectively.

  Next, the output unit 206 of the installment payment electronic record receivable management apparatus 101 transmits the user data record (user data records of both the creditor and the debtor) acquired in Step S302 to the creditor terminal 105 (Step S302). S303). When the creditor terminal 105 receives the user data record, the creditor terminal 105 displays the user data in the biller information display column and the counterparty information display column of the electronic record bond occurrence record request request message input interface 500, respectively. The electronic record receivable occurrence record request request message input interface 500 will be described with reference to FIG.

  The electronic record receivable occurrence record request request message input interface 500 is an input interface for generating an information message for generating an electronic record receivable managed as an installment payment. As shown in FIG. 5, the electronic record bond occurrence record request request message input interface 500 includes a biller information display field 501, a counterparty information display field 502, and a bond information input field 503.

  The receivable information input field 503 is a field for inputting information on electronically recorded receivables by installment payment. The amount of receivable, monthly payment amount (if installment payment is monthly payment), number of installment payments, monthly payment date, electronic recording year Information such as the date of the month (which is the recording date of the occurrence of electronically recorded receivables) and the final payment date is entered. It is not necessary to input all the input items in the above-described bond information input field 503. For example, automatic calculation items may be calculated by inputting the input items shown in Table 1 below. The payment period means a period from the electronic recording date to the final payment date.

  When the creditor inputs information on the electronic record receivable occurrence record request request message input interface 500, the creditor terminal 105 transmits the information as an electronic record receivable record request request message to the installment payment electronic record receivable management device 101 (step S304). . The electronically recorded receivable occurrence record request request message includes at least the creditor information displayed in the claimant information display field 501 shown in FIG. 5, the debtor information displayed in the counterparty information display field 502, and the credit information input field 503. The entered bond information (including automatically calculated items if they are automatically calculated) is included.

  Next, when the input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the electronic record receivable occurrence record request request message transmitted in step S304, the control unit 201 performs the operation based on the electronic record receivable occurrence record request request message. Then, a record is inserted into the installment payment electronic record bond data table 600 (step S305). The installment payment electronic record bond data table 600 will be described with reference to FIG.

  The installment payment electronic record receivable data table 600 is a database table for managing electronic record receivables to be registered in the electronic record receivable database of the electronic receivable recording institution system 103. As described above, the electronic bond recording institution system 103 does not have the concept of managing electronic record bonds by installment payment, but only manages a single electronic record bond. In the installment payment electronic record receivable management system according to the present invention, a plurality of electronic record receivables are grouped and managed as one electronic record receivable group, thereby realizing an electronic record receivable by installment payment.

  As shown in FIG. 6, the installment payment electronic record receivable data table 600 includes installment payment electronic record receivable number, record number, creditor user number, debtor user number, claim amount, payment date, settlement account information, and Includes payment flag. In the present embodiment, since the number of payments is designated as “60” in the electronic record receivable occurrence record request request message input interface 500 shown in FIG. 5, 60 electronic record receivables are generated. The installment payment electronic record receivable number is assigned one identification number for grouping each of the 60 electronic record receivables. In the present embodiment, the same installment payment electronic record receivable number is assigned to all 60 electronic record receivables. For example, the same number is assigned to only N digits, and the remaining digits are serial numbers. An installment payment electronic record receivable number may be assigned.

  As the record number, the record number assigned by the electronic bond recording institution system 103 is set by requesting the occurrence of the record to the electronic bond recording institution system 103. In this embodiment, since the monthly payment amount is designated as “10,000” yen, the amount of the bond is set. In this embodiment, the payment due date is designated as the 25th day of each month, so the 25th day of each month from the designated electronic record date (occurrence record date) to the final due date is set. .

  Next, the control unit 201 of the installment payment electronic record receivable management apparatus 101 creates an occurrence record request data file based on each record of the installment payment electronic record receivable data table 600 inserted in step S305. Then, the output unit 206 transmits the generated record request data file to the electronic bond recording institution system 103 (step S306). The occurrence record request data file is a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103, and is counterparty information (in this embodiment, since it is a creditor claim method, debtor information), It has information such as the amount of receivable and due date. As described above, in this embodiment, since 60 electronic record claims are generated, 60 occurrence record request data files are created and transmitted to the electronic bond recording organization system 103 60 times. Become.

  When the electronic bond recording institution system 103 receives the generated record request data file transmitted in step S306, it generates an generated record request notification data file and transmits it to the installment payment electronic record bond management apparatus 101 (step S307). The occurrence record request notification data file is a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103, and is a file for notifying the other party that an occurrence record request has been made. In this embodiment, since both the creditor and the debtor use the service providing financial institution as a window, the raw record request notification data file is transmitted to the installment payment electronic record claim management apparatus 101. This occurrence record request notification data file is also transmitted 60 times.

  Next, when the input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the generated record request notification data file transmitted in step 307, the control unit 201 performs the operation based on the received generated record request notification data file ( The request request message is generated by aggregating the 60 occurrence record request notification data files) and transmitted to the debtor terminal 106 indicated by the terminal address of the user data record acquired in step S302 (step S308). Since it is essential to obtain the consent of the obligor, who is the counterpart, when generating the electronically recorded receivable, the consent of the other party is obtained by transmitting the consent request message in this way.

  When the debtor terminal 106 receives the approval request message transmitted in step S308, the approval request message is displayed on the electronic record bond occurrence record request approval message input interface 700. The electronic record bond occurrence record request acceptance message input interface 700 will be described with reference to FIG.

  The electronic record receivable record request acceptance message input interface 700 is an input interface for generating an approval message indicating that the creditor has approved the record of occurrence of the electronic record receivable, and the obligor information (the obligor information) input by the creditor. Display field 701), creditor information (creditor information display field 702), and creditor information (bond information display field 703) are displayed.

  In this state, when the debtor executes the consent (for example, by pressing a “confirm” button displayed on the electronic record receivable occurrence record request acceptance message input interface 700), it indicates that the debtor has accepted. The approval message is transmitted to the installment payment electronic record receivable management apparatus 101 (step S309).

  When the input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the acceptance message transmitted in step S309, the control unit 201 corresponds to each of the generated record request data file (60) created in step S306. , Create an occurrence record request acceptance data file. Then, the output unit 206 transmits the generated record request data file to the electronic bond recording institution system 103 (step S310). The generated record request acceptance data file is a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103, and counterparty information (in this embodiment, since it is a creditor claim method, obligor information) , Information on the amount of receivables and the due date. As described above, in this embodiment, since 60 electronic record claims are generated, 60 occurrence record request data files are created and transmitted to the electronic bond recording organization system 103 60 times. Become.

  Originally, when an electronic record receivable occurrence record request is made, one approval is obtained for one occurrence record request, but in this embodiment, 60 electronic record receivable occurrence record requests are obtained. It is established by obtaining one-time consent from the other party. In other words, the installment payment electronic record receivable management apparatus 101 receives one acceptance message from the other party and creates 60 occurrence record request acceptance data files from the acceptance message, so the other party needs to make 60 authorizations. There is no. In this way, by grouping together the 60 electronic record claims occurrence record requests, the approval is only required once, and the burden on the other party's approval can be reduced.

  When the electronic bond recording institution system 103 receives the generated record request acceptance data file transmitted in step S310, it registers the electronic record bond in the electronic record bond database and generates 60 electronic record bonds (step S311). Then, the electronic bond recording institution system 103 creates an occurrence record result data file corresponding to 60 occurrence record requests and transmits it to the installment payment electronic record bond management apparatus 101 (step S312). The generated record result data file is a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103, and is used for notifying a record result for the generated record request. With this data file, the installment payment electronic record receivable management apparatus 101 can know the record numbers assigned to each of the 60 electronic record receivables.

  When the input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the generated record result data file transmitted in step S312, the control unit 201 installs the installment payment based on the record number included in the generated record result data file. The payment electronic record receivable data table 600 is updated (step S313). As shown in FIG. 6B, the record number is set to a record number uniquely assigned to each of the 60 electronic record bonds.

  In this way, a plurality of electronic record receivables are grouped and managed as one electronic record receivable group, thereby making it possible to manage electronic record receivables by installment payment. The installment payment electronic record receivable management apparatus 101 generates a plurality of electronic record receivables from the information such as the monthly payment amount, the monthly payment date, and the payment period input by the creditor (occurrence record requester). Since the record request is made, the burden on the creditor is reduced.

  In the present embodiment, the installment payment electronic record receivable management device 101 inserts a record into the installment payment electronic record receivable data table 600 when receiving the electronic record receivable occurrence record request request message from the creditor, Although the record of the installment payment electronic recording bond data table 600 is updated in response to receiving the recording result data file, the present invention is not limited to such a form. For example, the process of step S305 may be omitted, and a record may be newly inserted into the installment payment electronic record bond data table 600 including the record number in response to receiving the occurrence record result data file.

<Request change record>
Next, with reference to FIG. 8, a description will be given of a process for changing the claim information of the installment payment electronic record claim generated and recorded by the explanation of FIG. For example, in the state where there are electronic payment receivables with monthly payments of 10,000 yen for a payment period of 5 years, the creditor changed the monthly payments to 6,000 yen only for the remaining 2 years (Request for change record).

  The creditor who becomes the requester of the change record inputs the installment payment electronically recorded receivable number from an input interface (not shown) displayed on the display unit of the creditor terminal 105. The input installment payment electronic record receivable number is transmitted from the creditor terminal 105 to the installment payment electronic record receivable management apparatus 101 (step S801).

  The input unit 205 of the installment payment electronic record receivable management apparatus 101 receives the installment payment electronic record receivable number transmitted in step S801, and the control unit 201 performs installment payment electronic record based on the installment payment electronic record receivable number. All installment payment electronic record bond data records are acquired from the bond data table 600 (step S802).

  Next, the output unit 206 of the installment payment electronic record receivable management apparatus 101 transmits the installment payment electronic record receivable data record acquired in step S802 to the creditor terminal 105 (step S803). When the creditor terminal 105 receives the installment payment electronic record receivable data record, based on the installment payment electronic record receivable data record, the creditor terminal 105 sends the electronic record receivable change record request request message input interface 900 to the current payment count, payment period, etc. (By editing the received installment payment electronic record receivable data record). The electronic record bond change record request request message input interface 900 will be described with reference to FIG.

  The electronic record receivable change record request request message input interface 900 is an input interface for generating an information message for making a change record request for an existing installment payment electronic record receivable. As shown in FIG. 9, the electronic record receivable change record request request message input interface 900 includes a biller information display field 901, a counterparty information display field 902, and a receivable change information input field 903.

  The receivable change information input field 903 is a field for inputting change information related to electronically recorded receivables by installment payment. The amount of receivables, monthly payment amount (if installment payment is monthly payment), the number of installment payments, the monthly payment date, electronic Information such as the recording date, final payment date, change start period, and change end period is input.

  In the present embodiment, the monthly payment amount is changed to 6,000 yen only for the remaining two years of the five-year payment period (that is, from April 15, 2019 to March 31, 2020). In the bond information input field 803, 6,000 yen is input as the monthly payment amount, and the above-described period is input as the change start period and the change end period.

  When the creditor inputs information in the electronic record receivable change record request request message input interface 900, it is transmitted from the creditor terminal 105 to the installment payment electronic record receivable management device 101 as an electronic record receivable change record request request message (step S804). . The electronically recorded receivable change record request request message includes at least creditor information displayed in the claimant information display field 901 shown in FIG. 9, obligor information displayed in the counterparty information display field 902, and a receivable change information input field 903. Includes receivable change information entered in.

  Next, when the input unit 205 of the installment payment electronic record receivable management device 101 receives the electronic record receivable change record request request message transmitted in step S804, the control unit 201 determines that the electronic record receivable change record request request message has been received. Then, the corresponding record in the installment payment electronic record bond data table 600 is updated (step S805). In the present embodiment, the corresponding record in the installment payment electronic record bond data table 600 is updated so as to be updated from 10 (a) to 10 (b) in FIG. In this example, since the record of the payment period for two years is changed, 24 installment payment electronic record receivable data records are to be updated.

  Next, the control unit 201 creates a change record request data file based on each record of the installment payment electronic record receivable data table 600 updated in step S805 (step S806). The change record request data file is also a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103, similar to the occurrence record request data file, and this data file is transmitted to the electronic bond recording institution system 103. By doing so, it is possible to request change recording of the corresponding electronic record receivable.

  Next, a change record request notification data file is created by the electronic bond recording institution system 103 (step 807), and the obligor accepts the change record request by the creditor. Steps S807 to S809 of these processes are as follows. Since this is the same as S307 to S309 described in FIG.

  After step S810, the output unit 206 of the installment payment electronic record receivable management apparatus 101 transmits the created change record request acceptance data file to the electronic bond record institution system 103 (step S810). The recorded bond database is registered (step S811), and the change record result data file is transmitted to the installment payment electronic record bond management apparatus 101 (step S812). In the present embodiment, 24 electronic record receivables are to be changed. Therefore, 24 change record request data files are transmitted to the electronic bond recording institution system 103, and 24 change record result data file electronic receivables are received. Reception from the recording institution system 103 is performed.

  Also in the present embodiment, since the change record request is accepted by the obligor's one-time approval in response to the change record request from the creditor, the burden on the debtor is reduced.

  When the payment period is shortened or the number of payments is reduced in the electronic record receivable change record request request message input interface 900 shown in FIG. 9, unnecessary electronic record receivables remain. For example, when the number of payments is reduced from 60 to 48 (for example, when the number of payments is reduced by increasing the monthly payment amount, or when the amount of receivables itself is reduced), an electronic record for December counted from the final payment date The debt becomes unnecessary. In this case, an inter-account remittance settlement report data file may be created for an unnecessary electronic record receivable for December and transmitted to the electronic bond recording institution system 103. The inter-account remittance settlement report data file is a data file having a format common to all financial institutions defined by the electronic bond recording institution system 103. By transmitting this data file to the electronic bond recording institution system 103, the corresponding The electronic record receivable is paid, and the electronic record receivable disappears on the record ledger.

  In addition, as another method for shortening the payment period or reducing the number of payments, an unnecessary electronic record receivable may be deleted by making a change record request to the electronic bond recording institution system 103. . In this method, the change record request data file indicating that the electronic record receivable to be deleted is to be deleted is transmitted to the electronic bond recording institution system 103 and the consent of the other party is obtained. To do.

  In addition, in the electronic record receivable change record request request message input interface 900 shown in FIG. 9, when extending the payment period or increasing the number of payments, an additional electronic record receivable is required. In this case, the same installment payment electronic record receivable number as the existing installment payment electronic record receivable is assigned, and an additional installment payment electronic record receivable data record is added to the installment payment electronic record receivable data table 600. Further, by transmitting the additional electronic record receivable occurrence record request data file to the electronic receivable recording institution system 103, the electronic record receivable corresponding to the increased number of payments is generated.

  Also in the installment payment electronic record receivable management apparatus 101, the payment flag of the corresponding record in the installment payment electronic record receivable data table 600 is updated to “1: paid”.

  In the present embodiment, the claim contents of the installment payment electronic record receivable are changed by requesting the change record of the electronic record receivable, but the present invention is not limited to such a form. For example, for all electronic record receivables subject to change, the inter-account remittance settlement report data file is sent to the electronic receivables recording institution system 103 (that is, all electronic record receivables subject to change have been paid) An electronically recorded bond whose contents have been changed may be generated. The method for generating an electronically recorded bond is the same as that described with reference to FIG.

  As described above, the description of the installment electronic record receivable management system according to the present invention has been described in detail, but the specific data structure such as the installment payment electronic record receivable data table 600 described in the embodiment is illustrative. However, changes may be made without departing from the claimed subject matter.

102 Network 104 Network 202 System Bus 400 User Data Table 500 Electronic Record Claim Generation Record Request Request Message Input Interface 501 Requester Information Display Field 502 Counterparty Information Display Field 503 Claim Information Input Field 600 Installment Payment Electronic Record Claim Data Table 700 Electronic Record Acceptance record request acceptance message input interface 701 Obligor information display field 702 Creditor information display field 703 Claim information display field 900 Electronic record receivable change record request request message input interface 901 Claimer information display field 902 Counter party information display field 903 Receivable change Information input field

Claims (8)

A method executed by a server computer for managing electronic record receivables by installment payment, wherein the server computer is connected to an electronic bond recording institution system and a client computer,
A step of receiving an electronic record receivable occurrence record request request message from the client computer, wherein the occurrence record request request message is a receivable amount, payment count, payment period, and / or installment payment amount of the electronic record receivable Including steps, and
A step of generating a plurality of electronic recording bond data based on the received occurrence record request request message, wherein the generated plurality of electronic recording bond data has a common identification number, and Each of the electronically recorded bond data has a due date assigned a different date within the payment period; and
Creating a plurality of electronic record receivable occurrence record request data files corresponding to each of the generated plurality of electronic record receivable data;
Transmitting the created electronic record receivable occurrence record request data file to the electronic receivables record institution system;
Receiving a plurality of electronic record receivable occurrence record data files corresponding to each of the plurality of electronic record receivable occurrence record request data files transmitted from the electronic receivable recording institution system;
Assigning a record number assigned to each of the plurality of received electronic record bond occurrence record result data files to each of the plurality of generated electronic record bond data. The server computer is connected to a second client computer;
Receiving a plurality of electronic record bond occurrence record notification data files corresponding to each of the plurality of electronic record bond occurrence record request data files transmitted from the electronic bond record institution system;
Aggregating the received plurality of electronic record bond occurrence record notification data files to generate an occurrence record request acceptance request message; and
Receiving an occurrence record request acceptance message from the client computer;
Creating a plurality of electronic record receivable occurrence record request acceptance data files corresponding to each of the received plurality of electronic record receivable occurrence record notification data files;
2. The method according to claim 1, further comprising the step of: transmitting the created plurality of electronic record receivable occurrence record request acceptance data files to the electronic receivable record institution system. Receiving a change record request request message corresponding to a part or all of the generated plurality of electronic record bond data from the client computer, wherein the change record request request message includes a changed claim amount, a changed claim amount, A step including the number of payments, the modified payment period, and / or the modified installment payment amount;
Updating the generated plurality of electronic record bond data based on the received change record request request message;
Creating a plurality of electronic record receivable change record request data files corresponding to each of the updated plurality of electronic record receivable data;
Transmitting the created plurality of electronic record receivable change record request data files to the electronic receivable recording institution system;
Receiving a plurality of electronic record bond change record result data files corresponding to each of the plurality of electronic record bond change record request data files transmitted from the electronic bond record institution system;
The method according to claim 1, further comprising: When the change record request request message includes the number of payments after change or the payment period after change,
If the number of payments after the change is less than the number of payments before the change, or the payment period after the change is shorter than the number of payments before the change,
Creating a remittance settlement report data file between accounts based on the post-change payment count or the post-change payment period;
The method according to claim 3, further comprising: transmitting the created inter-account remittance settlement report data file to the electronic bond recording institution system. When the change record request request message includes the number of payments after change or the payment period after change,
If the number of payments after the change is greater than the number of payments before the change, or the payment period after the change is longer than the number of payments before the change,
Based on the change record request request message, creating an electronic record receivable occurrence record request data file;
4. The method according to claim 3, further comprising the step of transmitting the created electronic record bond occurrence record request data file to the electronic bond record institution system. A computer system for managing electronic record receivables by installment payment, the computer system being connected to an electronic bond recording institution system and a client computer,
An occurrence record request request message receiving unit that receives an occurrence record request request message of an electronic record receivable from the client computer, wherein the occurrence record request request message includes a claim amount of the electronic record receivable, the number of payments, a payment period, And / or an accrual payment request message receiving unit including an installment payment amount;
On the basis of the received occurrence record request request message, an electronic record receivable data generating unit that generates a plurality of electronic record receivable data, wherein the plurality of generated electronic record receivable data has a common identification number, Each of the generated plurality of electronically recorded bond data includes an electronically recorded bond data generation unit having a payment date assigned a different date within the payment period;
An electronic record receivable occurrence record request data file creation unit that creates a plurality of electronic record receivable occurrence record request data files corresponding to each of the generated plurality of electronic record receivable data;
A plurality of electronic record receivable occurrence record request data files created as described above, and an electronic record receivable occurrence record request data file transmission unit for transmitting to the electronic receivable record institution system;
Electronic record bond occurrence record result data file receiving unit for receiving a plurality of electronic record bond occurrence record result data files corresponding to each of the transmitted plurality of electronic record bond occurrence record request data files from the electronic bond record organization system When,
A computer comprising: a recording number assigning unit that assigns a recording number assigned to each of the plurality of received electronic record bond occurrence record result data files to each of the generated plurality of electronic record bond data system.   The program for making a computer perform the method as described in any one of Claims 1 thru | or 5.   A computer-readable storage medium storing the program according to claim 7.