JP2017173901A - Electronically recorded monetary claim payment substitution system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To substitute payment of electrically recorded monetary claim.SOLUTION: The electrically recorded monetary claim payment substitution system comprises the steps to: receive telegraph requesting accrual record of an electrically recorded monetary claim; store electrically recorded monetary claim data in a data storage unit on the basis of the telegraph requesting the accrual record; generate an electrically recorded monetary claim accrual record request data file on the basis of the electrically recorded monetary claim data; transmit the electrically recorded monetary claim accrual record request data file to an electrically recorded monetary claim recording institution system; receive inter-account money transfer settlement data file corresponding to the electrically recorded monetary claim accrual record request data file; acquire the electrically recorded monetary claim data corresponding to the inter-account money transfer settlement data file; instruct an account system to handle money transfer on the condition that payer information is set for the electrically recorded monetary claim data; generate an inter-account money transfer settlement report data file on the basis of the inter-account money transfer settlement data file; and transmit the inter-account money transfer settlement report data file to the electrically recorded monetary claim recording institution system.SELECTED DRAWING: Figure 4

Description

  The present invention relates to an electronic recording receivable payment agent system and an electronic recorded receivable payment agent method, and more particularly, to an electronic recorded receivable payment agent system and an electronic recorded receivable payment agent method for performing a payment agent for inter-bank remittance settlement of electronic recorded receivables.

  Electronically recorded receivables can be used in accordance with the Electronically Recorded Receivables Law, which came into effect in December 2008. With respect to receivables arising from business-to-business transactions, their generation, transfer, and payment are electronically simplified. It can be done quickly.

  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 is performed on a system provided by an electronic bond recording institution system (so-called “Densai Net”) through a system provided by a financial institution affiliated with the electronic bond recording institution (hereinafter referred to as “window financial institution”). There is a need to do. Densai Net is provided with a thorough common specification because it is commonly used by financial institutions nationwide. However, when using electronic record receivables, it is required to follow that specification. .

“Densai Net”, [online], the National Bank Association's electronic bond recording agency, the Zengin Electronic Bond Network, [Search Date: February 26, 2016], Internet <URL: https: //www.densai. net / faq

  By the way, an operator having an affiliated company including a subsidiary (for example, a holding company) sometimes pays debts owned by the affiliated company in a lump. As such an example, for example, corporation A having corporation 1, corporation 2 and corporation 3 as affiliates pays the debts of corporation 1, corporation 2 and corporation 3 in a lump sum by the settlement account of corporation A. Can be mentioned. Such a payment scheme is called “payment agency”. For businesses having the above-mentioned affiliated companies, the payment agent may be preferable in order to efficiently manage the balance.

  As described above, when an electronic record receivable is generated, it is necessary to register it in the record book held by the electronic bond recording institution. Need to do. In this occurrence record request, creditor account information, creditor account information that becomes a settlement account of creditor name, debtor name, inter-bank remittance settlement (payment of electronic record receivable is done through inter-bank remittance settlement), and obligor account information Is specified.

  As shown in Non-Patent Document 1, the specification of the electronic bond recording institution system requires that the name of the debtor and the name of the debtor account are the same. In other words, the debtor of the electronically recorded receivable needs to carry out inter-account remittance using the settlement account he has as a debtor settlement account.

  In the payment agency scheme described above, the name of the debtor settlement account is an operator such as the holding company described above, and the name of the debtor is the affiliated company, so the names of the two do not match. In other words, under the specifications required by the electronic bond recording institution system, it is not possible to perform payment for electronic record bonds.

  The present invention has been made in view of such problems, and an object of the present invention is to provide an electronic record receivable payment agent system that makes it possible to perform a payment agent for remittance settlement between accounts of electronic record receivables.

  In order to solve the above problems, an electronic record receivable payment agent system according to the present invention is a method executed by a server computer for performing an electronic record receivable payment agent, wherein the server computer The system is connected to a system, an electronic bond recording institution system, and a client computer, and receives an electronic record receivable occurrence record request message from the client computer, wherein the occurrence record request request message includes obligor information, creditor Including information and payer information, a step of storing electronic record receivable data in a data storage unit based on the received occurrence record request request message, and a step of storing electronic record receivable data based on the stored electronic record receivable data. Generating a record claim occurrence record request data file, the electronic record The right generation record request data file includes the debtor information and the creditor information, the step of transmitting the generated electronic record bond generation record request data file to the electronic bond recording institution system, and the electronic A step of receiving an inter-account remittance settlement data file corresponding to the transmitted electronic record receivable occurrence record request data file from the receivable-recording institution system, and corresponding to the received inter-account remittance settlement data file from the data storage unit Obtaining electronic record receivable data and processing for transferring funds from a payer account to a creditor account for the account system on condition that payer information is set in the obtained electronic record receivable data Between the accounts based on the received inter-account transfer data file Generating a gold settlement report data file, the remittance between the settlement report data file the generated, characterized by comprising a step of transmitting to the Electronic Monetary recording engine system.

  According to the electronic record receivable payment agent system according to the present invention, the electronic record receivable payment agent is performed by paying the debt separately from the debtor settlement account designated in the request for recording the occurrence of the electronic record receivable. Is possible.

It is a figure which shows the example of the whole structure of the electronic record loan payment agency system based on one Embodiment of this invention. It is a figure which shows the example of a structure of the electronic record loan payment agency server based on one Embodiment of this invention. It is a figure which shows the example of the outline | summary of the payment proxy processing of the electronic record receivable which the electronic record receivable payment proxy system which concerns on the 1st Embodiment of this invention performs. It is a flowchart which shows the detailed example of the payment proxy processing of the electronic record loan which the electronic record bond payment proxy system which concerns on the 1st Embodiment of this invention performs. It is a figure which shows the electronic record loan generation | occurrence | production record request request | requirement message input interface which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the user data table which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the electronic record bond data table which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the outline | summary of the payment proxy processing of the electronic record loan which the electronic record loan payment proxy system which concerns on the 2nd Embodiment of this invention performs. It is a flowchart which shows the detailed example of the payment proxy process of an electronic record loan which the electronic record bond payment proxy system which concerns on the 2nd Embodiment of this invention performs.

  Hereinafter, an electronic record receivable payment agent 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 electronically recorded loan payment agency system according to the present invention. In FIG. 1, an electronic record receivable payment agent server 101 is connected to an electronic bond record institution system 103 via a network 102 such as a dedicated line. The electronically recorded loan payment proxy server 101 is connected to a debtor terminal 105 and a creditor terminal 106 via a network 104 such as the Internet.

  The electronic record loan payment agent server 101 is a main computer server that provides a service related to the electronic record loan payment agent system according to the present invention (hereinafter, “electronic record loan payment agent service”). Installed and managed by financial institutions that provide services (hereinafter referred to as “service provider financial institutions”). In response to an electronic record receivable occurrence record request from a user (creditor or debtor), the electronic record receivable payment agent server 101 creates an occurrence record request data file having a common format, and requests the occurrence record request The data file is transmitted to the electronic bond recording institution system 103. It should be noted that the electronic record receivable payment agent server 101 may be implemented alone, or may be implemented by a server computer or host computer of a bank system that provides a bank accounting service that exists in the past. Also, the electronic record bond payment proxy server 101 may be implemented by a single computing device, or may be implemented by being distributed over a plurality of computing devices. In the present embodiment, it is assumed that the electronically recorded bond payment proxy server 101 is mounted alone and connected to a conventional billing system (not shown).

  The electronic bond recording institution system 103 is a system common to all banks (Densai Net) for managing electronic record receivables 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 receiving the generated record request data file from the electronic record receivable payment proxy server 101, the electronic bond record institution system 103 adds the corresponding record original record to the electronic record receivable database. Occur).

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

  The creditor terminal 106 is a client computer terminal possessed by a creditor who uses a service related to the electronic record credit payment agency system of the present invention. The creditor terminal 106 displays an input interface provided by the electronically recorded credit payment agency system. The creditor terminal 106 is used to input information necessary for requesting an occurrence record when an electronically recorded claim is generated by the creditor claim method.

  The input interface may be installed on the debtor terminal 105 and the creditor terminal 106, or may be a WEB screen transmitted from the electronically recorded bond payment proxy server 101.

  The debtor terminal 105 and the creditor terminal 106 described above may be, for example, 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, an example of the configuration of the above-described electronic record receivable payment agent server 101 will be described in detail. The electronically recorded loan payment proxy server 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 bus. 202 is connected.

  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 referred to as a main memory, and stores input data received by the electronically recorded bond payment proxy server 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 debtor terminal 105 and / or the creditor 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.

  In response to receiving the input of settlement account information from the debtor terminal 105 and / or the creditor terminal 106, the output unit 206 transmits the generated record request data file via the network I / F 207.

  The database 208 is implemented by a DBMS (Data Base Management System) and stores a database table such as an electronic record bond data table to be described later.

<First Embodiment>
Next, with reference to FIG. 3, an example of an outline of a payment proxy process for an electronically recorded bond executed by the electronically recorded bond payment proxy system according to the first embodiment of the present invention will be described.

  In the present embodiment, the occurrence record request is made by the debtor claim method, the debtor of the electronically recorded receivable is the corporation a (hereinafter “obligor a”), and the creditor is the corporation b (hereinafter “creditor b”). Suppose that the payer acting on behalf of the debtor a's payment is corporation A (hereinafter “payer A”). Further, it is assumed that the account held by the debtor a is the debtor account α, the account held by the creditor b is the creditor account β, and the account held by the payer A is the payer account γ.

  As described above, in the electronic bond recording institution system 103, the name of the debtor of the electronic record bond and the debtor settlement account need to match. In this embodiment, the debtor is designated as the debtor a, the creditor is designated as the creditor b, the debtor settlement account is designated as the debtor account α, and the creditor settlement account is designated as the creditor account β. Generate record receivables.

  Then, as a settlement for the generated electronically recorded receivable, the amount of funds transferred (transfer) from the payer account γ to the creditor account β is performed with the debtor a as the name of the transfer requester. On the electronic bond recording institution system 103, the debtor settlement account is designated as the debtor account α and the creditor settlement account is designated as the creditor account β. Is done. That is, in the inter-account remittance settlement in which the debtor settlement account is designated as the debtor account α and the creditor settlement account is designated as the creditor account β, funds are transferred from the payer account γ. Instead, actual funds are not transferred between the debtor account α and the creditor account β.

  Next, with reference to FIG. 4, a detailed example of the electronic record receivable payment proxy process executed by the above-described electronic record receivable payment proxy system according to the first embodiment of the present invention will be described.

<Request for occurrence record>
First, the electronic record receivable occurrence record request request message input interface 500 is displayed on the display unit (not shown) of the obligor terminal 105 of the obligor a who becomes the claimant of the occurrence record request. 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. As shown in FIG. 5, the electronic record receivable occurrence record request request message input interface 500 includes a biller user number input field 501, a biller information display field 502, a payer information display field 503, a partner user number input field 504, An opponent information display field 505 and a bond information input field 506 are included.

  The claimant user number input field 501 is a field for inputting the user number of the claimant (debtor). By entering the user number in this field, the biller information display field 502 shows the obligor's user number. Information such as payment account information is displayed. Further, by inputting the user number in this column, information such as the payment account information of the payer who performs the payment agent of the debtor's debt is displayed in the payer information display column 503. The other party user number input field 504 is a field for inputting the user number of the other party (creditor). By entering the user number in this field, the settlement account information of the creditor is displayed in the other party information display field 505. Information such as is displayed. The claim information input field 506 is a field for inputting information such as the amount of claim of the target electronic record claim.

  Here, the user number is a number for identifying each user in the electronic record receivable payment agency system according to the present invention, and may be, for example, a user number assigned by the electronic receivable recording agency system 103. , Not limited to that number. In the present embodiment, it is assumed that the debtor a and the creditor b have registered user numbers in the electronic bond recording institution system 103.

  Returning to the description of FIG. 4, in step S401, the user number of the obligor a is entered in the requester user number input field 501 and counterparty user number input field 504 of the electronic record receivable occurrence record request request message input interface 500, respectively. (In this embodiment, “000000002”) and the other party (creditor b) (in this embodiment, “000000011”) are entered. The entered two user numbers are transmitted from the debtor terminal 105 to the electronically recorded receivable payment agent server 101 (step S401).

  The input unit 205 of the electronically recorded bond payment proxy server 101 receives the two user numbers transmitted in step S401, and the control unit 201 retrieves user data from the user data table 600 based on the user numbers. A record is acquired (step S402). Here, the user data table includes a user data record corresponding to the user number of the debtor a (hereinafter, “user data record a”) and a user data record corresponding to the user number of the creditor b ( Hereinafter, “user data record b”) is acquired.

  FIG. 6 shows an example of the user data table 600. In this embodiment, it is assumed that both creditors and debtors are registered in the user data table 600. No. 2 is a debtor a user data record. Record 3 is a creditor b user data record. The user data table 600 is a database table that stores information about users registered in the electronic record receivable payment agent system according to the present invention, and includes user numbers, user names, and account information (settlement). Account information), and payer user number. The payer user number is the user number of the user who acts as a proxy for the corresponding user (in this embodiment, the payer user number of the debtor a becomes the user number of the payer A. ).

  Next, based on the payer user number included in the user data record a acquired in step S402, the control unit 201 retrieves a user data record (hereinafter referred to as “user data record A”) from the user data table 600. ) Is acquired (step S403). The user data record A has the No. shown in FIG. 1 user data record.

  The user data records a, b, and A acquired in step S402 and step S403 are transmitted to the debtor terminal 105 by the output unit 206 (step S404). When the debtor terminal 105 receives the user data records a, b, and A, as shown in FIG. 5, the biller information display field 502, the payer information display field 503 of the electronic record bond occurrence record request request message input interface 500, as shown in FIG. In the other party information display field 505, information of the obligor a, the creditor b, and the payer A is displayed. In this state, when the debtor a inputs the claim information such as the amount of the claim in the claim information input field 506, an electronically recorded claim occurrence record request message is generated. The generated electronic record receivable occurrence record request request message is transmitted to the electronic record receivable payment proxy server 101 (step S405). The electronic record receivable occurrence record request request message includes at least the biller information displayed in the biller information display field 502 shown in FIG. 5, the payer information displayed in the payer information display field 503, and the counterparty information display field 505. The displayed opponent information and the bond information input in the bond information input field 506 are included.

  Thus, in the user data table 600, the debtor and the payer are registered in association with each other, and the payer information associated with the debtor is only displayed by inputting the debtor's user number. 105 can be displayed. This becomes more efficient, for example, as the debtor's debt is paid more frequently through a payment agent by the payer.

  In the present embodiment, in the user data table 600, the debtor a and the payer A are registered in association with each other, and the payer A is specified by inputting the user number of the debtor a. However, it is not limited to such an example. For example, the payer information may be directly input in the electronic record receivable occurrence record request request message input interface 500. In addition, instead of obtaining information from the user data table 600 based on the user number input in the electronic record receivable occurrence record request request message input interface 500, the debtor and / or creditor information is directly input. Also good.

  Next, when the input unit 205 of the electronic record receivable payment proxy server 101 receives the electronic record receivable occurrence record request request message transmitted in step S405, 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 electronically recorded bond data table 700 (step S406). The electronic record bond data table 700 will be described with reference to FIG.

  The electronic record bond data table 700 is a database table for managing electronic record bonds to be registered in the electronic record bond database of the electronic bond recording institution system 103. As described above, in the electronic bond recording institution system 103, the obligor and the account holder of the settlement account need to match. In the electronic record receivable payment agent system according to the present invention, the electronic record receivable and the payer account are associated with each other and registered in the electronic record receivable data table 700, and the actual inter-account remittance settlement is performed through the payer account.

  As shown in FIG. 7 (a), the electronically recorded bond data table 700 includes a record number, biller information (user number, account information), counterparty information (user number, account information), bond amount, payment. Includes due date, payer information (user number, account information), and payment flag. Information is set in each of these items as shown in Table 1.

  Next, the control unit 201 of the electronic record receivable payment agent server 101 creates an occurrence record request data file based on the record of the electronic record receivable data table 700 inserted in step S406. Then, the output unit 206 transmits the generated occurrence record request data file to the electronic bond recording institution system 103 (step S407). The occurrence record request data file is a data file having a format common to all financial institutions, such as biller information (such as user number and account information of debtor a), counterparty information (user number and account information of creditor b). Etc.), amount of receivable, and due date. Here, the debtor account α of the debtor a who is the claimant is designated in the account information of the claimant designated in the generation record claim data file.

  When the electronic bond recording institution system 103 receives the generated record request data file transmitted in step S407, the electronic record bond is registered in the electronic record bond database and an electronic record bond is generated (step S408). Then, the electronic bond recording institution system 103 creates an occurrence record result data file corresponding to the occurrence record request and transmits it to the electronic record bond payment proxy server 101 (step S409). The occurrence record result data file is a data file for notifying the record result for the occurrence record request, and has a format common to all financial institutions. From this data file, the electronic record loan payment proxy server 101 can know the record number assigned to the electronic record bond.

  When the input unit 205 of the electronically recorded bond payment proxy server 101 receives the generated record result data file transmitted in step S409, the control unit 201 performs electronic recording based on the record number included in the generated record result data file. The bond data table 700 is updated (step S410). As shown in 7 (b) of FIG. 7, the record number assigned to the corresponding electronic record bond is set as the record number.

  Further, in the present embodiment, the electronic record receivable payment agent server 101 inserts a record into the electronic record receivable data table 700 at the stage of receiving the electronic record receivable occurrence record request request message from the debtor, and generates the generated record result data Although the record of the electronically recorded bond data table 700 is updated in response to receiving the file, the present invention is not limited to such a form. For example, the process of step S406 may be omitted, and a record may be newly inserted into the electronic record bond data table 700 including the record number in response to receiving the generated record result data file.

  In the present embodiment, the occurrence record request is made by the obligor claim method, but it is not limited to such a method, and it may be made by the creditor claim method. In this case, the electronically recorded bond occurrence record request message in step S405 of FIG. 4 is generated and transmitted by the creditor terminal 106.

<Bank transfer between accounts>
Next, an example of inter-account remittance settlement processing will be described. The inter-account remittance settlement is a payment method common to all financial institutions, defined by the electronic bond recording institution system 103, for payment of the electronic record receivable.

  When a predetermined number of days before the payment due date of the corresponding electronic record receivable, the electronic receivable recording institution system 103 generates an inter-account remittance settlement data file and transmits it to the electronic record receivable payment proxy server 101 (step S411). The inter-account remittance settlement data file is a data file having a format common to all financial institutions, and includes the record number, debtor information, creditor information, credit amount and the like of the corresponding electronic record loan.

  When the input unit 205 of the electronically recorded bond payment proxy server 101 receives the inter-account remittance settlement data file transmitted in step S411, the control unit 201 reads the corresponding electronic data from the electronically recorded bond data table 700 based on the record number. A recorded bond data record is acquired (step S412). Here, the electronically recorded bond data record described above may be acquired based on debtor information (account information) and creditor information (account information) included in the inter-account remittance settlement data file.

  Next, when the payer information is set in the electronic record receivable data record acquired in step S412, the control unit 201 (if the payer information is set, the payer account γ for the corresponding electronic record receivable is set. ), The transfer requester name is the debtor a, the transfer source account is the payer account γ, and the transfer destination is the creditor account β. To generate transfer data for transferring the credit amount of the corresponding electronic record loan (step S413). Thereafter, based on the generated transfer data, the amount of money transferred from the payer account γ to the creditor account β is transferred. This money transfer process is performed by the output unit 206 transmitting the generated transfer data to the accounting system. Since these processes are conventionally known, the description of the process is omitted in this specification.

  If the payer information is not set in the electronic record receivable data record acquired in step S412 (if the payer information is not set, the obligor account α is changed to the creditor account β for the corresponding electronic record receivable. Step S412 is not executed, and as usual, funds are transferred from the debtor account α to the creditor account β through the inter-account remittance settlement data (the second transfer). The same applies to the embodiment). In addition, whether or not the corresponding electronic record receivable in step S412 uses the payment agent is not limited to determination based on whether or not the payer information is set. For example, in the electronic record receivable data table 700, The item “payment agent flag” may be included, and “1: payment agent” may be set in the item. In this case, the payment agent flag is included in the electronically recorded bond occurrence record request request message transmitted in step S405 (the same applies to the second embodiment).

  When the funds transfer described above is performed, the control unit 201 of the electronically recorded loan payment proxy server 101 creates an inter-account remittance settlement report data file in which the settlement account is designated as the settlement account of the debtor a, and the output unit 206 The inter-account remittance settlement report data file is transmitted to the electronic bond recording institution system 103 (step S414). The inter-account remittance settlement report data file is a data file for performing inter-account remittance settlement reports to the electronic bond recording institution system 103, and has a common format for all banks.

  Here, in the ordinary inter-account remittance settlement, when the inter-account remittance settlement report data file is transmitted to the electronic bond recording institution system 103, payment is made from the obligor settlement account to the creditor settlement account. In the embodiment, since the funds are transferred from the payer account, the actual funds are not transferred from the debtor settlement account to the creditor settlement account.

  Upon receipt of the inter-account remittance settlement report data file, the electronic bond recording institution system 103 updates the corresponding electronic record bond record original record from the electronic record bond database (step S415). In this update process, payment or the like indicating that payment was made in the electronic bond recording institution system 103 is recorded.

  Next, the control unit 201 of the electronic record receivable payment proxy server 101 updates the payment flag of the corresponding record in the electronic record receivable data table 700 to “1: paid” (step S416).

  As mentioned above, the account of the debtor a is designated as the settlement account, the record of the occurrence of the electronically recorded receivable is requested, and the payment of the actual receivable is made by transferring from the account of the payer A to the account of the creditor b By carrying out the above, it is possible to realize a payment agent for electronically recorded receivables.

<Second Embodiment>
Next, with reference to FIG. 8, an example of an outline of a payment proxy process for an electronic record loan executed by the electronic record bond payment proxy system according to the second embodiment of the present invention will be described.

  In the second embodiment, as in the first embodiment, an occurrence record request is made by the debtor claim method. The debtor of the electronically recorded receivable is designated as a corporation a (hereinafter “obligor a”), and the creditor is designated as a corporation. b (hereinafter referred to as “creditor b”), and the payer acting on behalf of the debtor a's payment is referred to as corporation A (hereinafter referred to as “payer A”). Further, it is assumed that the account held by the debtor a is the debtor account α, the account held by the creditor b is the creditor account β, and the account held by the payer A is the payer account γ.

  The request for the record of occurrence of electronic record receivables is the same as in the first embodiment. In the second embodiment, as a settlement for the generated electronically recorded receivable, the receivable amount is transferred from the payer account γ to the service providing financial institution. Then, the same amount of money is transferred from the service providing financial institution to the creditor account β. The funds transfer from the payer account γ to the service providing financial institution is preferably performed before the remittance from the service providing financial institution to the creditor account β.

  Next, with reference to FIG. 9, a detailed example of a payment proxy process for an electronic record receivable executed by the electronic record receivable payment proxy system according to the second embodiment of the present invention described above will be described. The generation record request is the same as the process described with reference to FIG.

  When the payment date of the generated electronic record receivable comes a predetermined number of days ago, the electronic receivable recording institution system 103 generates an inter-account remittance settlement data file and transmits it to the electronic record receivable payment proxy server 101 (step S911).

  When the input unit 205 of the electronically recorded bond payment proxy server 101 receives the inter-account remittance settlement data file transmitted in step S911, the control unit 201 extracts the corresponding electronic data from the electronically recorded bond data table 700 based on the record number. A recorded bond data record is acquired (step S912). Here too, the electronically recorded bond data record may be acquired based on debtor information (account information) and creditor information (account information) included in the inter-account remittance settlement data file.

  Next, when the payer information is set in the electronic record bond data record acquired in step S912, the control unit 201 provides the payer account γ as the debit account and the transfer destination as a service based on the data record. Designate the financial institution and generate fund transfer data for debiting the corresponding electronic record receivable from the payer account γ (step S913). Thereafter, based on the generated fund transfer data, the fund transfer processing of the amount of receivable is performed from the payer account γ to the service providing financial institution. This fund transfer process is performed when the output unit 206 transmits the generated fund transfer data to the accounting system. Since these processes are conventionally known, the description of the process is omitted in this specification. .

  When the above-described funds transfer is performed, the control unit 201 transfers the remittance data from the inter-account remittance settlement data file where the remittance destination is the creditor account β, the remittance source is the debtor account α, and the name of the remittance requester is the debtor a. Is generated (step S914). Thereafter, based on the generated remittance data, the service providing financial institution performs remittance processing to the creditor account β. This remittance process is also performed when the output unit 206 transmits the generated remittance data to the accounting system. Specifically, in this remittance process, the money transferred from the debtor account α of the remittance source designated by the remittance data is not transferred, and the funds transferred by the fund transfer data transmitted to the account system in step S913 are transferred to the remittance destination. Transferred to creditor account β.

  Next, the control unit 201 of the electronically recorded bond payment proxy server 101 creates an inter-account remittance settlement report data file in which the settlement account is designated as the settlement account of the debtor a, and the output unit 206 outputs the inter-account remittance settlement report data. The file is transmitted to the electronic bond recording institution system 103 (step S915). Here, as in the first embodiment, actual funds are not transferred from the debtor account α to the creditor account β.

  When receiving the inter-account remittance settlement report data file, the electronic bond recording institution system 103 updates the corresponding electronic record bond record original record from the electronic record bond database (S916). In this update process, payment or the like indicating that payment was made in the electronic bond recording institution system 103 is recorded.

  Finally, the control unit 201 of the electronic record receivable payment agent server 101 updates the payment flag of the corresponding record in the electronic record receivable data table 700 to “1: paid” (step S917).

  As described above, the description of the electronic record receivable payment agent system according to the present invention has been described in detail, but the specific data structure such as the electronic record receivable data table 700 described in the embodiment is merely an example. Modifications may be made without departing from the matters claimed. Further, the order of the processes shown in the flowcharts of FIGS. 4 and 9 is not necessarily executed in the order shown, and may be changed within the scope of the present invention.

102 Network 104 Network 202 System Bus 500 Electronic Record Claim Generation Record Request Request Message Input Interface 501 Biller User Number Input Field 502 Biller Information Display Field 503 Payer Information Display Field 504 Counter User Number Input Field 505 Counterpart Information Display Field 506 Bond information input field 600 User data table 700 Electronically recorded bond data table

Claims (9)

A method executed by a server computer for performing payment of an electronic record receivable, wherein the server computer is connected to a billing system, an electronic bond recording institution system, and a client computer,
Receiving an occurrence record request request message for an electronic record receivable from the client computer, wherein the occurrence record request request message includes debtor information, creditor information, and payer information;
Based on the received occurrence record request request message, storing electronic record bond data in a data storage unit;
Based on the stored electronic record receivable data, a step of generating an electronic record receivable occurrence record request data file, wherein the electronic record receivable occurrence record request data file includes the debtor information and the creditor information, Steps,
Transmitting the generated electronic record receivable occurrence record request data file to the electronic receivable recording institution system;
Receiving an inter-account remittance settlement data file corresponding to the transmitted electronic record receivable occurrence record request data file from the electronic bond record institution system;
Obtaining the electronically recorded bond data corresponding to the received inter-account remittance settlement data file from the data storage unit;
Instructing the account system to transfer funds from a payer account to a creditor account on the condition that payer information is set in the acquired electronic record bond data;
Generating an inter-account remittance settlement report data file based on the received inter-account remittance settlement data file;
And transmitting the generated inter-account remittance settlement report data file to the electronic bond recording institution system. Instructing the funds transfer process includes:
A step of generating transfer data based on the acquired electronically recorded bond data, wherein the creditor information is specified in a transfer destination account of the transfer data, and the payer information is stored in a transfer source account of the transfer data. The debtor information is specified in the name of the transfer requester of the transfer data, and
The method according to claim 1, further comprising: transmitting the generated transfer data to the billing system. Instructing the funds transfer process includes:
Generating funds transfer data for debiting from a payer account based on the acquired electronic record receivable data;
Transmitting the generated fund transfer data to the billing system;
A step of generating remittance data based on the acquired inter-account remittance settlement data, wherein the creditor information is specified in a remittance destination account of the remittance data, and the debtor information is specified in a remittance source account of the remittance data. And the name of the remittance requester of the remittance data is specified by the debtor information, and
Transmitting the generated remittance data to the accounting system;
The method of claim 1, comprising:   2. The debtor of the inter-cash remittance settlement report data file is designated with the debtor information, and the creditor of the inter-cash remittance settlement report data file is designated with the creditor information. The method as described in any one of thru | or 3. A computer system for performing payment of electronic record receivables, wherein the computer system is connected to a billing system, an electronic bond recording institution system and a client computer,
An input unit configured to receive an electronic record receivable occurrence record request request message from the client computer, wherein the occurrence record request request message includes debtor information, creditor information, and payer information , Input section,
Based on the received occurrence record request request message, the electronic record bond data is stored in the data storage unit,
An electronic record receivable occurrence record request data file is generated based on the stored electronic record receivable data, and the electronic record receivable occurrence record request data file is configured to include the debtor information and the creditor information A control unit;
An output unit configured to transmit the generated electronic record receivable occurrence record request data file to the electronic receivable recording institution system; and
The input unit is further configured to receive an inter-account remittance settlement data file corresponding to the transmitted electronic record receivable occurrence record request data file from the electronic receivable recording institution system,
The controller is
From the data storage unit, obtain electronic record receivable data corresponding to the received inter-account remittance settlement data file,
Instructing the account system to transfer funds from the payer account to the creditor account on the condition that the acquired electronic record credit data payer information is set,
Further configured to generate an inter-account remittance settlement report data file based on the received inter-account remittance settlement data file;
The computer system, wherein the output unit is further configured to transmit the generated inter-account remittance settlement report data file to the electronic bond recording institution system. The controller is
Based on the acquired electronic record receivable data, generate transfer data, the creditor information is specified in the transfer destination account of the transfer data, the payer information is specified in the transfer source account of the transfer data, The debtor information is designated in the name of the transfer requester of the transfer data, and is further configured.
The computer system according to claim 5, wherein the output unit is further configured to transmit the generated transfer data to the billing system. The controller is
Based on the acquired electronic record receivable data, generate funds transfer data for debiting from a payer account,
Based on the acquired inter-account remittance settlement data, remittance data is generated, the creditor information is specified in the remittance destination account of the remittance data, the obligor information is specified in the remittance source account of the remittance data, The remittance requester name of the remittance data is further configured such that the debtor information is designated,
The output unit is
Send the generated funds transfer data to the account system,
Further configured to transmit the generated remittance data to the billing system,
The computer system according to claim 5.   The program for making a computer perform the method as described in any one of Claims 1 thru | or 4.   A computer-readable storage medium storing the program according to claim 8.

Images