JP5466334B1 - Electronic record receivable record request management apparatus and electronic record receivable record request management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic record receivable record request management device that contributes to the realization of a collective settlement service for electronic record receivables, which is easy to use between different parties of a transaction financial institution and considers the burden on the user. I will provide a.
[Solution] In addition to a paying company, a paying company, and a purchasing financial institution, an agent who acts as a proxy for the procedure for requesting records related to electronic record receivables is added to the collective payment service usage contract, and the request for the occurrence record and transfer record is made Assuming the scheme performed by, information related to collective contracts is managed in the contract DB. When payment data is received, the presence or absence of a collective contract is confirmed in the contract DB, and if there is a collective contract, a record of the occurrence of electronically recorded receivables with the paying company as the debtor and the agent as the creditor is requested, If so, request a transfer record that transfers the electronic record receivable from the agent to the purchasing financial institution. If there is no lump sum contract, request a record of occurrence of electronically recorded receivables with the paying company as the debtor and the paying company as the creditor.
[Selection] Figure 6

Description

  The present invention relates to a record request management device for electronic record claims and a record request management method for electronic record claims that contribute to the realization of a collective settlement service for electronic record claims.

  As a new payment method to improve the efficiency of fund procurement by companies, etc., the electronic record credit system was enforced on December 1, 2008. In the electronic record receivables system, monetary receivables such as bills and trade receivables are digitized and managed by an electronic receivables recording institution, and prescribed for third parties who conduct transactions such as purchases of receivables recorded in the electronic receivables recording institution Therefore, it is expected that paper bills will be made paperless by shifting from bills to electronically recorded receivables and that receivables will be mobilized (see 13-16 p. Of Non-Patent Document 1).

  In order to promote the utilization of the electronic record receivables system, “Densai Net” (registered trademark) was established by the Japan Bankers Association in June 2010 as an organization for operating an electronic receivables recording institution that will become a new settlement infrastructure. ) Was established (see Non-Patent Document 2), and registration of electronically recorded receivables by “Densai Net” (registered trademark) began in February 2013.

  Compared to bills, the electronic record receivable system has the advantages of reducing the burden of administrative procedures related to issuance, transportation, management, etc. Since it is possible to transfer receivables with simple procedures, it is also expected that fund procurement by discounting receivables will be promoted, and various methods for smooth transfer of electronically recorded receivables are being studied.

  For example, in order to promptly transfer electronically recorded receivables for fundraising, information regarding the availability of purchase of receivables determined at the time of occurrence and recording of electronically recorded receivables can be used to respond to purchase requests for electronically recorded receivables. Upon receipt of an invention (see Patent Document 1) relating to an electronic record receivable registration device that enables quick judgment (see Patent Document 1) and detailed data of payments subject to a collective settlement service (collective factoring), an occurrence record and transfer record of an electronic record receivable Discloses an invention relating to an electronically recorded bond processing method (see Patent Document 2) that enables generation of necessary data and simultaneous generation and transfer recording.

JP 2009-80728 A JP 2011-175571 A

Financial Services Agency, “Access FSA (Monthly Financial Service Public Relations Magazine) No. 56”, August 1, 2007 [Search August 16, 2013], Internet <URL: http://www.fsa.go.jp /access/19/200707.pdf> Zengin Electronic Receivables Network Co., Ltd., “Densai Net Structure and Practices”, June 2012, [Search August 16, 2013], Internet <URL: http://www.densai.net/pdf/ Pamphlet.pdf>

  The purpose of the present invention is to realize a lump sum settlement service (lump factoring) provided by financial institutions for accounts receivable, targeting electronic record receivables. According to the scheme described below, a supplier who has delivered a product or service (includes not only the goods to be sold but also the service to be delivered) is paid by the supplier for the goods or services from the payer. By transferring receivables to financial institutions without waiting for payment, it is possible to quickly cash them.

  FIG. 1 shows a general scheme of a lump sum settlement service. A lump sum settlement service is used for accounts receivables generated by a delivery company B providing goods and services to a payment company A. This is a contract between the paying company A, the delivering company B, and the purchasing financial institution C that purchases the accounts receivable. Based on this contract, payment company A provides payment data for payments generated by accounts receivable, subject to the lump sum settlement service, to purchase financial institution C, and purchase financial institution C delivers the payment amount based on the payment data. The company B is notified (1). When the supplier B asks the purchasing financial institution C for discounts on the accounts receivable that it wants to cash quickly, the accounts receivable are transferred from the supplier B to the purchasing financial institution C, and the amount of receivable from the purchasing financial institution C The discounted price minus interest is paid to Supplier B (2). If the due date of the accounts receivable comes after that and the payment is made by the paying company A, it is processed as payment to the purchasing financial institution C that newly became the creditor of the accounts receivable (3).

  In this scheme, it is assumed that the purchasing financial institution C makes a credit judgment for the paying company A because the purchasing financial institution C purchases the accounts receivable on the back of credit for the payment ability of the paying company A. It has become.

  Assuming that Denso Net (registered trademark) is used as an electronic bond recording institution when trying to realize such a lump sum settlement service for electronic record claims, as shown in Figure 2 It is possible to become a simple scheme. Requests for the occurrence and transfer of electronically recorded receivables to Densai Net (registered trademark) are made through a contact financial institution (see Non-Patent Document 2 on page 8). Since it can be used as a contact financial institution (see 11p. Of Non-Patent Document 2), the payment company A, the delivery company B, and the purchase financial institution C are their own financial institutions X, X, Z Should be used as a window financial institution (Note that window financial institution Z is usually purchased financial institution C itself or an affiliated company of purchased financial institution C and can be considered substantially the same. is there).

  That is, the payment company A transmits payment data of payments generated by the subject receivables to the counter financial institution X which is its own transaction financial institution, and requests an occurrence record from the electronic receivable recording institution via the counter financial institution X. . When the occurrence record of the electronic record receivable is made, the delivery company B is notified that the occurrence record of the electronic record receivable has been made through the window financial institution Y which is the transaction financial institution of the deliver company B (1). . Supplier B sends a discount request for electronically recorded receivables that it wants to cash immediately to its counterparty financial institution Y, and through the counterfinancial institution Y to the electronic receivables registrar Request a transfer record. When the transfer record of the electronically recorded receivable is performed, the transfer record of the electronically recorded receivable is performed via the contact financial institution Z (which may be the same as the purchased financial institution C), which is the transaction financial institution of the purchased financial institution The purchase financial institution C is notified (2).

  However, it is assumed that the following problems will occur when the collective payment service is provided by the scheme shown in FIG. First, when purchasing electronic record receivables, it is the purchase financial institution C (usually substantive with the contact financial institution Z that provides credit for the payment of the electronic record receivable by the paying company A for certain. However, the credit decision for the paying company A will be examined by the counter financial institution X when starting to use the electronically recorded receivable (see 12p. Of Non-Patent Document 2). There is a problem in that a divergence occurs between the financial institution that performs credit judgment for the company A (window financial institution X) and the financial institution that provides credit (purchasing financial institution C). In order to deal with such problems, the window financial institution X of the paying company A and the window financial institution Z of the purchase financial institution C are required to be the same financial institution.

  Secondly, the delivery company B makes a discount request for electronic record receivables to its counter financial institution Y, which is its transaction financial institution. For example, even if the paying company A and the paying company B agree to use the lump sum settlement service based on the proposal of the purchasing financial institution C, the discount on the electronically recorded receivables can be reduced. This is a problem that the financial institution C may be excluded from this scheme because it is performed by the counter financial institution Y. In order to deal with such a problem, the window financial institution Y of the supplier B and the window financial institution Z of the purchase financial institution C are required to be the same financial institution.

  That is, the payment company A, the delivery company B, and the purchase financial institution C may use the purchase financial institution C or a financial institution related to the purchase financial institution C as a window financial institution to unify the window financial institutions. As required, payment company A, delivery company B, and purchase financial institution C have their own banks, so if such restrictions are used, the companies that can use the lump sum payment service are extremely limited. It becomes a thing.

  In this regard, in the invention described in Patent Document 2, the debtor of the electronic record receivable (corresponding to the paying company A), the creditor of the electronic record receivable (corresponding to the delivery company B), and the SPC (purchasing financial institution) that purchases the electronic record receivable (Corresponding to C) all access the same bank system, that is, it is assumed that the same bank is used as a window financial institution, so that the companies that can use the collective payment service are extremely limited. It is not possible to cope with the problem.

  In addition, in the invention described in Patent Document 2, it is assumed that only detailed data of a loan subject to collective factoring (collective settlement service) is transmitted from the debtor terminal (see paragraph 0025 of Patent Document 2). ) Since the debtor must perform the work of receivables subject to collective factoring (collective settlement service), there may be a problem that the service user is burdened.

  The present invention has been made to address such problems, and is intended for electronically recorded receivables that are easy to use services between different parties of a transaction financial institution and that are designed to reduce the burden on users. It is an object of the present invention to provide an electronic record receivable record request management apparatus and an electronic record receivable record request management method that contribute to the realization of the collective settlement service.

  In response to such a problem of the present invention, the inventor of the present invention, in addition to a payer of a target receivable, a supplier, a purchaser who purchases a receivable, By adding an agent acting on behalf of the request for the occurrence record and transfer record, and requesting the occurrence record and the transfer record by the same entity, the agent, the transaction financial institution of the payer, the supplier, and the purchaser Regardless, we came up with a scheme that enables one-stop transaction financial institutions to realize a collective payment service for electronically recorded receivables. On the premise of this scheme, in the electronic record receivable record request management device according to the present invention, if the information on the use contract of the collective settlement service including the agent is held, the payment data received from the payer can be used. By reducing the burden on the user of the lump sum payment service by determining whether it is eligible for the lump sum payment service based on the presence or absence of the contract, the agent in the use contract is regarded as the creditor of the electronic record receivable By performing the occurrence record, it is possible to realize a collective settlement service without requiring a transfer record from the supplier whose bank is the transaction bank of the supplier.

  That is, the recording request management device for electronically recorded receivables according to the present invention includes a payer who pays for the receivables subject to the electronically recorded receivables, a supplier who has delivered goods or services related to the receivables, and a purchase that purchases the receivables. Information regarding the use contract of the collective settlement service concluded by the agent and the agent acting on behalf of the request for record of occurrence to make the claim as an electronic record claim and the transfer record request for the purchaser to purchase the electronic record claim Storing means for storing, accepting means for accepting payment data of a claim for claiming an occurrence record of an electronically recorded claim, and whether the payment data accepted by the accepting means is based on a claim subject to a collective settlement service, A contract for using the collective payment service by searching the storage means and including a payer and a payer of the payment related to the payment data as contract parties A judgment means for judging from the presence or absence, and for the payment data for which the judgment data is judged not to be based on a claim subject to a collective payment service, based on the payment data, To request the record of occurrence of electronic record receivables to the computer system of the electronic receivables record organization that manages the record ledgers of electronic record receivables, where the payer is the obligor and the payer related to the payment data is the creditor. The first generation means for generating the occurrence record request data and the payment data determined by the determination means that the payment data is based on the receivables subject to the collective settlement service. Based on the above, the payer of the payment related to the payment data is the debtor, and the payer and the payer of the payment related to the payment data are the contracting parties. Incident record request data used to request the occurrence record of electronic record receivables to the computer system of the electronic receivables record organization that manages the record ledgers of electronic record receivables whose creditor is the creditor in the use contract of the collective settlement service including Generating transfer record request data used to request the transfer record of the electronic record receivable from the computer system, wherein the agent is the transferor and the purchaser in the use contract of the lump sum settlement service is the transferee. And a second generation means. A recording claim management apparatus for electronic record claims.

  In the present invention, with respect to payment data based on receivables that are not subject to the lump sum settlement service, it is possible to request an occurrence record of electronically recorded receivables with the payer as the debtor and the supplier as the creditor.

  In the present invention, since the agent and the counter financial institution of the agent are different entities, the generated record request data is transferred to the computer system of the counter financial institution, and the electronic bond record is transmitted via the computer system of the counter financial institution The organization's computer system will be configured to request a record of occurrence, but the agent is an affiliated company of the agent's window financial institution, etc., and the computer system is operated in coordination. May be configured to directly request an occurrence record from the electronic claim receivable record request management apparatus according to the present invention to the computer system of the electronic claim recording organization based on the generated occurrence record request data.

  According to the present invention, in the information relating to the use contract of the collective payment service stored in the storage means, either a periodic discount or a condition corresponding to each time is recorded in each use contract of the collective payment service with respect to the timing of purchasing the receivable. And the determination means, if there is a contract for using the collective payment service that includes the payer and the payer of the payment related to the payment data as contract parties, whether the condition for timing of purchasing the receivable is a periodic discount or a case-by-case And the second generation means determines that the payment data is based on a claim subject to the collective payment service and the condition for timing of buying the claim is a periodic discount. The transfer record request data may be generated together with the generated record request data.

  With this arrangement, if the usage agreement for the lump sum settlement service stipulates that the electronically recorded receivables that have been recorded be purchased immediately, the transfer record of the electronically recorded receivables from the agent to the purchaser is also included. So that funding can be promptly realized by discounting electronic record receivables.

  According to the present invention, in the information relating to the use contract of the collective payment service stored in the storage means, either a periodic discount or a condition corresponding to each time is recorded in each use contract of the collective payment service with respect to the timing of purchasing the receivable. And the determination means, if there is a contract for using the collective payment service that includes the payer and the payer of the payment related to the payment data as contract parties, whether the condition for timing of purchasing the receivable is a periodic discount or a case-by-case And the second generating means determines that the payment data is based on a claim subject to a collective payment service and that the timing condition for purchasing the claim is compatible each time. And generating the transfer record request data after receiving a discount request for the electronic record receivable from the supplier. It can also be. Further, the second generation means, when it is determined by the determination means that the payment data is based on a receivable subject to a collective payment service, and the condition of timing for purchasing the receivable is determined each time, If a request for discount on the electronically recorded receivable from the supplier has not been received before a predetermined time limit based on the payment date in the payment data, the payer and the supplier of the payment related to the payment data are Instead of transfer record request data in which the agent in the collective payment service use contract included in the contract party is the transferor and the purchaser in the collective payment service use contract is the transferee, the transferor is the transferor and the supplier The transfer record request data for requesting the transfer record of the electronic record receivable may be generated.

  If configured in this way, if it is not stipulated in the collective payment service usage contract to immediately purchase electronic record receivables that have been recorded, from the agent to the buyer at the timing desired by the supplier Requesting a record of the transfer of electronic record receivables to realize funding by discounting electronic record receivables, or transfer of electronic record receivables to the supplier if the supplier does not make a discount request until the specified time It is possible to request a record and pay the supplier for the payment received from the payer.

  In the present invention, since the agent and the agent's window financial institution are different entities, the generated transfer record request data is transferred to the computer system of the window financial institution, and the electronic bond record is transmitted via the computer system of the window financial institution. It will be configured to request transfer records from the institution's computer system, but the agent is an affiliated company of the agent's window financial institution, etc., and the computer system is operated in cooperation. May be configured to request transfer records directly from the electronic claim receivable record request management apparatus according to the present invention to the computer system of the electronic claim recording organization based on the generated transfer record request data.

  The present invention can also be specified as a recording claim management method for electronic record claims executed by the record request management apparatus for electronic record claims according to the present invention.

  The recording request management method for electronically recorded receivables according to the present invention includes a payer who pays for the receivables subject to the electronically recorded receivables, a supplier who has delivered goods or services related to the receivables, a purchaser who purchases the receivables, and Stores information related to the use contract of the collective settlement service concluded by the agent acting on behalf of the request for the occurrence record request for making the claim an electronic record claim and the transfer record request for the purchaser to purchase the electronic record claim An electronic recording receivable record request management device provided with a storage means accepts payment data of a claim for claiming an electronic record receivable occurrence record, and the recording request management device accepts the payment data received in the accepting step. Payment related to the payment data by searching the storage means to determine whether the payment is based on a claim subject to a collective payment service A determination step for determining from the presence or absence of a collective payment service usage contract that includes a payer and a delivery party as a contracting party; and the record request management device, wherein the payment data is based on a claim subject to the collective payment service in the determination step. Electronically recorded receivables for payment data determined not to be subject to a payment payer related to the payment data as a debtor and a payer related to the payment data as a creditor based on the payment data A first generation step of generating occurrence record request data for requesting an occurrence record of an electronic record bond to a computer system of an electronic bond record organization that manages a record ledger of the record, and the record request management device in the determination step For the payment data determined to be based on the receivables subject to the collective payment service, the payment data A payment payer related to the payment data is a debtor, and an agent in a collective payment service usage contract including the payment payer and the payer related to the payment data is a creditor. In the record system of the electronic payment receivables that manages the record ledgers of the recorded receivables, the occurrence record request data used for requesting the occurrence records of the electronic record receivables, the transferor as the transferor, and the collective payment service usage contract And a second generation step of generating transfer record request data used to request the transfer record of the electronic record claim from the computer system, wherein the purchaser is the assignee. This is a record request management method.

  The present invention can also be specified as an electronic record claim recording request management method executed by the electronic record claim record request management apparatus according to the present invention corresponding to each configuration described above.

  According to the present invention, it is possible to use a collective settlement service for electronically recorded receivables between different parties of a transaction financial institution without any party starting a transaction with a new financial institution. Also, when users are requested to record the occurrence of electronically recorded receivables, the workload for receiving the receivables subject to the lump sum settlement service is reduced, and a lump sum settlement service for electronic receivables is realized. Can be expected to contribute.

It is a figure which shows the general scheme of a lump sum payment service. It is a figure which shows the scheme assumed when providing a lump sum payment service for electronic record receivables. It is a figure which shows the scheme of the lump sum payment service for the electronic record receivable used as the premise of this invention. It is a figure which shows the outline | summary of embodiment of this invention. It is a block diagram which shows an example of a structure of the recording claim management apparatus of the electronic record receivable concerning this invention. It is a flowchart which shows the processing flow which requests the generation | occurrence | production record of an electronic record loan by the record claim management apparatus of the electronic record bond concerning this invention. It is a figure which shows the data flow at the time of assigning the electronic record receivable with which the generation | occurrence | production record was carried out in the scheme of the collective payment service for the electronic record receivable in this invention. It is a figure which shows the data flow when the electronic record receivable with which the generation | occurrence | production record was carried out is not immediately transferred with the scheme of the lump sum payment service for the electronic record receivable in this invention. It is a figure which shows the data flow at the time of assigning the electronic record receivable with which the occurrence record was recorded based on the discount request from a delivery company by the scheme of the lump sum payment service for the electronic record receivable in this invention. FIG. 4 is a diagram showing a data flow when an electronically recorded receivable that has been recorded is not transferred to a purchasing financial institution even when the due date arrives in the lump sum settlement service scheme for electronic receivables according to the present invention. . It is a figure which shows the data flow in the case of performing generation | occurrence | production recording of the electronic record receivable which is not the object of a lump sum payment service in the scheme of the lump sum payment service for the electronic record receivable in this invention. It is a figure which shows an example of the payment data received in the recording claim management apparatus of the electronic record receivable concerning this invention. It is a figure which shows an example of the contract information storage part of the recording claim management apparatus of the electronic record receivable concerning this invention. It is a figure which shows an example of the bond information storage part of the recording claim management apparatus of the electronic record loan which concerns on this invention.

  Embodiments for carrying out the present invention will be described below in detail with reference to the drawings. In addition, the following description shows an example of embodiment of this invention, Comprising: This invention is not limited to this embodiment.

  First, referring to FIG. 3, a description will be given of a scheme of a collective payment service for an electronically recorded bond that is a premise of the present invention. First, in the problem to be solved by the invention, as described with reference to FIG. 2, when trying to provide a collective settlement service for electronically recorded receivables using “Densai Net” (registered trademark). Payment company A, delivery company B, and purchase financial institution C wish to use their own financial institutions, X, X, and Z, as financial institutions, and each financial institution is different. Become. Therefore, the financial institution that makes a credit decision for the paying company A and the financial institution that provides the credit may differ, and the purchased financial institution C that proposes a collective settlement service may be excluded from this scheme. Is considered to be a problem. In order to deal with these problems, a scheme that can unify the payment financial institution A, the delivery company B, and the purchasing financial institution C is required.

  Therefore, in the present invention, the procedure necessary for the application and the record of occurrence of the electronic record receivable of the paying company A and the procedure necessary for the transfer record of the electronic record receivable when discounting the electronic record receivable based on the request of the delivery company B As shown in FIG. 3, the window financial institution Z of the purchasing financial institution C (usually substantially the same as the purchasing financial institution C) is replaced with the bank financing of the agency D, as shown in FIG. By making it an institution, we have made it possible to create a one-time payment service scheme that unifies counter financial institutions. Since the transaction target of payment company A and delivery company B is agent D instead of window financial institution Z, it is necessary to start a transaction such as opening an account with a new financial institution in order to use the collective payment service. There will be no.

  That is, in the scheme of FIG. 3, when the payment company A transmits payment data of payment generated by the subject receivable to the agent D, the agent D passes through the window financial institution Z, which is its own transaction financial institution, Request an accrual record from an electronic bond recorder. When the occurrence of the electronic record receivable is recorded, the agent D notifies the delivery company B and the paying company A that the occurrence of the electronic record receivable has been recorded via the counter financial institution Z (1). When the supplier B sends a discount request for electronic record receivables that it wants to cash quickly to the agent D, the agent D records the transfer record to the electronic bond record institution through the counter financial institution Z, which is its transaction financial institution. Claim. When the transfer of the electronic record receivable is recorded, the agent D notifies the purchase financial institution C and the delivery company B through the counter financial institution Z that the transfer of the electronic record receivable has been recorded (2). Based on the above flow, the payment company A and the delivery company B can use the collective payment service even if there is no transaction with the window financial institution Z.

  Next, the outline of the embodiment of the present invention will be described with reference to FIG. The agent system shown in FIG. 4 is the procedure necessary for the application and usage record of the electronically recorded receivable of the paying company described above, and the transfer record of the electronically recorded receivable when discounting the electronically recorded receivable based on the request of the delivering company. This is a computer system operated by an agent acting on behalf of necessary procedures, and the financial institution system is a computer system operated by a financial institution of “Densai Net” (registered trademark). Normally, the agent system is configured to correspond to the record request management device for electronic record claims according to the present invention, but the agent is an affiliated company of the agent's window financial institution and operates in conjunction with a computer system. In such a case, the agent system and the financial institution system that are operated as one unit correspond to the record request management apparatus for electronic record receivables according to the present invention.

  As a premise, a payment company that sends payment data from a payment company terminal applies for the use of a service through an agent operating the agent system, reviews the financial institution operating the financial institution system, and concludes a usage agreement, It is necessary for the company to be able to use services related to record receivables. The payment company records payment data in which payment details of payment to be managed as an electronically recorded bond are recorded to the agent system.

  The agent system is provided with a database that stores contract information related to usage contracts for the collective payment service. When payment data is received from a payment company terminal, the database searches the database to identify the debtor identified from the payment data. And the creditor's use of the collective payment service, and if the combination of the debtor and the creditor corresponds to the collective payment service, it is determined that the payment is a target of the collective payment service.

  For payments not covered by the lump sum payment service, as specified from the payment data, the payment company is specified from the payment data, with the paying company as the obligor and the delivery company that delivered the product subject to payment as the creditor. Occurrence record request data for requesting an occurrence record of an electronic record receivable including a claim amount and a due date is generated, and the occurrence record request is made to the electronic claim record institution system via the financial institution system. When the occurrence record of the electronic record receivable is recorded in the record book managed by the electronic receivable recording institution, a notice to that effect is transmitted to the financial institution system, and is notified to the paying company and the delivery company via the agency system.

  For payments subject to the lump sum settlement service, record the occurrence of electronically recorded receivables including the amount of receivable and the due date specified from the payment data, with the paying company specified from the payment data as the debtor and the agent as the creditor. Generation record request data for charging is generated, and the occurrence record is requested to the electronic bond recording institution system via the financial institution system. When the occurrence record of the electronic record receivable is recorded in the record book managed by the electronic receivable recording institution, a notice to that effect is transmitted to the financial institution system, and is notified to the paying company and the delivery company via the agency system.

  Here, if it is stipulated in the contract for the use of the collective payment service that the electronically recorded receivables are immediately discounted (subtracting interest up to the due date to purchase the receivables), the agent is the transferor and the collective payment service is used. Generates transfer record request data for requesting transfer records of electronic record receivables that are subject to occurrence records, with the purchase financial institution specified by the contract as the transferee, and through the financial institution system electronic bond record institution system Request a transfer record. When the transfer record of the electronic record receivable is recorded in the record book managed by the electronic bond recording institution, a notification to that effect is transmitted to the financial institution system and notified to the delivery company and the purchasing financial institution through the agency system. The purchase financial institution that discounts electronically recorded receivables may be the same as the agent operating the agent system or the contact financial institution operating the financial institution system, and notification is not required if it is the same as the agent However, if it is the same as the window financial institution, it is preferable to notify.

  On the other hand, if it is stipulated that discounts on electronically recorded receivables are dealt with each time in the use contract of the lump sum settlement service, the agent will be requested at the timing when a discount request is received from the delivery company after the occurrence is recorded. The transfer record request data is generated to request the transfer record of the electronic record receivable that has been recorded in advance, with the transferor as the transferee and the purchase financial institution identified from the use contract of the lump sum settlement service. Request the transfer record from the electronic bond recording institution system via the institution system. When the transfer record of the electronic record receivable is recorded in the record book managed by the electronic bond recording institution, a notification to that effect is transmitted to the financial institution system and notified to the delivery company and the purchasing financial institution through the agency system. If the purchase financial institution that discounts electronic record receivables is the same as the agent operating the agent system or the contact financial institution operating the financial institution system, notification is not required if it is the same as the agent. However, in the same way as in the previous case, it is preferable to notify if the same as the window financial institution.

  When it is stipulated that discounts for electronically recorded receivables will be dealt with each time in the lump-sum payment service use contract, and there is no discount request from the supplier even if the due date of the electronically recorded receivables that have already been recorded is approaching Is a transfer for requesting transfer records of electronically recorded receivables that have been recorded in advance, with the transferee as the transferee and the transferee specified by the use contract for the collective payment service at the specified timing. Record request data is generated and a transfer record is requested to the electronic bond recording institution system via the financial institution system. When the transfer record of the electronic record receivable is recorded in the record book managed by the electronic bond record organization, a notification to that effect is transmitted to the financial institution system and notified to the delivery company via the agency system.

  FIG. 5 shows an example of the configuration of a record request management apparatus for electronic record claims according to the present invention. The agent system 10 is a computer that includes an auxiliary storage device such as a CPU, main memory, and HDD and is connected to a network such as the Internet. However, the physical configuration of the computer is not particularly limited. Or a part of the functions of one computer, or two or more computers.

  The payment data receiving unit 11, the occurrence record request transmitting unit 14, the discount request receiving unit 15, the transfer record request transmitting unit 16, the notification receiving unit 17, and the notification transmitting unit 18 of the agent system 10 are all functionally specified. The application programs corresponding to these functions are read from the computer HDD or the like to the main memory or the like, and the arithmetic processing is executed by the CPU, thereby realizing each function.

  A storage area of an auxiliary storage device such as a computer HDD is allocated to the contract information storage unit 12 and the bond information storage unit 13, but the physical configuration is not particularly limited, and the payment data receiving unit 11 and the like. An HDD or the like of the same computer as the computer that implements this function may be used, or a database server or the like that is a physically different computer may be used.

  The financial institution system 20 is a computer connected to a network that includes an auxiliary storage device such as a CPU, a main memory, and an HDD, and the physical configuration of the computer is not particularly limited. In the case where the computer system is linked and operated because the agent is an affiliated company of the window financial institution, the financial institution system 20 is configured to be integrated with the agent system 10. .

  The electronic bond recording institution system 30 is a computer that is connected to the financial institution system 20 operated by the counter financial institution through a network and includes an auxiliary storage device such as a CPU, a main memory, and an HDD. It is not particularly limited. The electronic bond recording institution system 30 is provided with a record ledger of electronic record receivables, and when an occurrence record of electronic record receivables or a request for transfer records is received from the financial institution system 20, the occurrence record or transfer record is performed on the record ledgers. Is called.

  The payment company terminal 40, the delivery company terminal 50, and the purchase financial institution terminal 60 are not particularly limited as long as the computer can be connected to a network such as the Internet, and a personal computer or the like equipped with a Web browser is used. It should be used. In the case where the purchase financial institution is an agent, the role of the purchase financial institution terminal 60 is included in the agent system 10 (or the purchase financial institution terminal 60 becomes unnecessary).

  On the premise of the above configuration, processing for requesting the occurrence record and transfer record of the electronic record receivable by the agent system 10 will be described along the process flow of the flowchart of FIG. 6 with reference to FIGS.

  When the payment data recording the payment details of the payment to be managed as the electronic record receivable is transmitted from the payment company terminal 40 of the payment company A to the agent system 10 of the agent D, the agent system 10 receives the payment data receiving unit 11. Is activated to receive payment data (S1). FIG. 12 shows an example of payment data. Each payment data identified by a payment code includes a debtor (payment company) and a creditor (delivery company), a payment amount, a payment date, and the like. Contains information.

  Next, for each received payment data, the contract information storage unit 12 is searched using the debtor (payment company) and creditor (delivery company) as keys (S2). FIG. 13 shows an example of the contract information storage unit 12, but it is a lump sum settlement by four parties (payment company, purchase company, purchase financial institution, and agent). If a service usage contract is signed, a contract code is assigned to each contract, and the settlement is performed in a lump sum including the timing (periodic discount or each time) for purchasing electronic record receivables in response to a discount request from the contracting party and the supplier. Information related to service usage contracts is stored in the contract information storage unit 12.

  For this reason, when the contract information storage unit 12 stores information related to a collective payment service usage contract (collective contract) with the obligor (payment company) and creditor (delivery company) recorded in the payment data as contract parties. Is determined to be a payment subject to the collective payment service, and if it is not stored, it can be determined that the payment is not eligible for the collective payment service (S3). Then, the processing described below is performed.

  Note that the method of searching the contract information storage unit 12 using the above debtor (paying company) and creditor (delivery company) as a key is the method of searching the contract information storage unit 12 and identifying the debtor (payment). 1 shows an example of a method for determining whether or not a collective payment service usage contract including a contractor and a creditor (delivery company) is concluded. In the present invention, whether there is a collective payment service use contract. The method of determining is not limited to this method. For example, by requesting that a contract code for identifying a use contract of the collective payment service be given to the payment data, and searching the contract information storage unit 12 using this contract code as a key, the payment of the payment related to the payment data is also performed. It is possible to determine whether or not there is a contract for use of a collective payment service that includes a contractor and a supplier as contract parties.

  If there is a lump sum contract, that is, it is determined that the payment is subject to the lump sum settlement service, it further relates to a lump sum settlement service usage contract with the obligor (paying company) and creditor (delivery company) as the contracting parties. From the information, the timing of purchasing electronic record receivables from the supplier company is a regular discount (the electronic record receivable is immediately discounted together with the record of occurrence), responds each time (every time there is a discount request from the supplier, the discount of electronic record receivables (S4). It should be noted that the term discounts used here and the corresponding categories only need to indicate their respective meanings, and the terms indicating the contract categories are not limited to these examples.

  FIG. 7 shows the flow of processing in the case where the purchase timing of the electronic record receivable from the supplier company is determined to be a periodic discount. In this case, the payment company A specified from the payment data is the obligor, the agent D specified from the use contract of the lump sum settlement service is the creditor, and the amount and payment date specified from the payment data are included. The generation record request data for requesting the generation record of the electronic record bond is generated (S5).

  Subsequently, the generated record request transmitting unit 14 is activated, and the generated record request data is transmitted to the electronic bond recording institution system 30 via the financial institution system 20 of the counter financial institution Z (necessary for requesting the generation record of the electronic record loan). If such information is included, the format of the generated record request data may be changed in the financial institution system 20), and the generated record is recorded in the record book. When the occurrence record in the record ledger is performed, the notice that the occurrence record is performed by the notification receiving unit 17 of the agency system 10 is received from the electronic bond recording institution system 30 via the financial institution system 20, and the notification transmission unit 18 is sent to the payment company terminal 40 of the payment company A and the delivery company terminal 50 of the delivery company B, and a notification that the occurrence has been recorded is transmitted.

  In this case, the delivery company B has agreed to immediately discount the electronic record receivable in the usage contract, so that the agent D is the transferor and the use of the collective payment service together with the generation of the record request data. Transfer record request data for requesting transfer record of electronic record receivable, specifying target electronic record receivable (electronic record receivable requesting occurrence record) with purchase financial institution C specified from contract as transferee Generate (S6). This step is also executed when the purchasing financial institution becomes the agent, that is, when the purchasing financial institution C and the agent D are the same.

  Subsequently, the transfer record request transmitting unit 16 is activated, and the transfer record request data is transmitted to the electronic bond recording institution system 30 via the financial institution system 20 of the counter financial institution Z (necessary for requesting the transfer record of the electronic record receivable). If such information is included, the transfer record request data may be changed in format or the like in the financial institution system 20), and transfer record to the record book is performed. When the transfer record to the record book is performed, the notice of the transfer record is received by the notification receiving unit 17 of the agent system 10 from the electronic bond recording institution system 30 via the financial institution system 20, and the notification transmitting unit 18 is sent to the delivery company terminal 50 of the delivery company B and the purchase financial institution terminal 60 of the purchase financial institution C to send a notification that the transfer record has been made. At the same time, a funds transfer process is performed for payment of a discount price that accompanies the discount.

  It should be noted that the generation record request and the transfer record request may be made simultaneously, or the transfer record request may be made after receiving the notification of the occurrence record request. In either case, according to this scheme, since the creditor of the electronic record receivable to be transferred is the agent D, the request for the transfer record is not the counter financial institution selected by the delivery company B, but the agent D This can be done through the counter financial institution Z, so that the counter financial institution can be unified.

  Next, FIG. 8 shows the flow of processing in the case where it is determined that the timing of purchasing the electronically recorded receivable from the supplier company corresponds to each time. Even in this case, the payment company A identified from the payment data is the debtor, the agent D identified from the use contract of the collective settlement service is the creditor, and the amount and the due date specified from the payment data are included. The generation record request data for requesting the generation record of the electronic record bond is generated (S7).

  Subsequently, the generated record request transmitting unit 14 is activated, and the generated record request data is transmitted to the electronic bond recording institution system 30 through the financial institution system 20 of the counter financial institution Z, and the occurrence record is recorded in the record book. When the occurrence record is recorded in the record book, the notice that the occurrence record is made by the notice receiving unit 17 of the agency system 10 is received from the electronic bond recording institution system 30 through the financial institution system 20, and further the notification is transmitted. It is the same as the case of the regular discount described above that the section 18 is activated and the notification of the occurrence record is sent to the payment company terminal 40 of the payment company A and the delivery company terminal 50 of the delivery company B. .

  However, in this case, the delivery company B makes a discount request for the electronic record receivable in the usage contract whenever necessary, so no transfer record is requested at this stage. As shown in FIG. 9, the transfer record is requested when the discount request is received from the delivery company B, but the payment due date and the identification code of the purchasing financial institution C regarding the electronically recorded receivable recorded. It is preferable to store the information including etc. in the bond information storage unit 13 as illustrated in FIG.

  As shown in FIG. 9, when a discount request for an electronic record receivable is transmitted from the delivery company terminal 50 of the delivery company B to the agent system 10 of the agent D, the agent system 10 includes a discount request receiving unit 15. Activate and receive discount requests. The transferee D is the transferee, the purchaser financial institution C identified from the information related to the electronic record receivable that is the subject of the discount request by searching the receivable information storage unit 13, and the target electronic record receivable The transfer record request data for requesting the transfer record of the electronic record receivable specifying the recorded electronic record receivable) is generated. This step is also executed when the purchasing financial institution becomes the agent, that is, when the purchasing financial institution C and the agent D are the same.

  Subsequently, the transfer record request transmitting unit 16 is activated, and the transfer record request data is transmitted to the electronic bond recording institution system 30 via the financial institution system 20 of the counter financial institution Z, and the transfer record to the record book is performed. When the transfer record to the record book is performed, the notification of the transfer record is received by the notification receiving unit 17 of the agent system 10 from the electronic bond recording institution system 30 via the financial institution system 20 and further transmitted. Activating the section 18 and sending a notification that the transfer record has been made to the delivery company terminal 50 of the delivery company B and the purchase financial institution terminal 60 of the purchase financial institution C, and in conjunction with this, a discount that accompanies the discount The fund transfer process for payment is performed in the same manner as the case of the regular discount described above.

  On the other hand, when there is no discount request from the delivery company B even when the due date is approaching, specifically, the due date specified in the information on each electronically recorded receivable stored in the receivable information storage unit 13 is used as a reference. If the discount request is not received from the delivery company terminal 50 before the predetermined deadline arrives, it is determined that the delivery company B will carry out the electronic record receivable until the due date, and the delivery company B shown in FIG. Process to become a creditor.

  That is, for the electronically recorded receivable that has reached a predetermined due date based on the due date stored in the receivable information storage unit 13, the information regarding the electronically recorded receivable stored in the receivable information storage unit 13 is the agent D. The transfer record request data for requesting the transfer record of the electronic record receivable is generated with the delivery company B recorded as the creditor in FIG.

  Subsequently, the transfer record request transmitting unit 16 is activated, and the transfer record request data is transmitted to the electronic bond recording institution system 30 via the financial institution system 20 of the counter financial institution Z, and the transfer record to the record book is performed. (However, the transferee is not the purchased financial institution C but the delivery company B), and when the transfer record is made to the record book, the electronic bond recording institution system 30 notifies the agent system 10 through the financial institution system 20. The receiving unit 17 receives the notification that the transfer record has been made, and further activates the notification sending unit 18 to transmit the notification that the transfer record has been made to the delivery company terminal 50 of the delivery company B (however, purchase finance) The notification to the institution C is not performed) is the same as the case of the regular discount described above. When the payment company A receives payment on the due date, the payment is sent to the payment company B which is the creditor.

  FIG. 11 shows the flow of processing when it is determined in S3 that there is no collective contract, that is, it is not a payment subject to the collective settlement service. In this case, the payment company A specified from the payment data is the debtor, the delivery company B is the creditor, and the amount and date of payment specified from the payment data are included, as in the case of the general occurrence record processing. The generation record request data for requesting the generation record of the electronic record bond is generated (S8).

  Subsequently, the generated record request transmitting unit 14 is activated, and the generated record request data is transmitted to the electronic bond recording institution system 30 through the financial institution system 20 of the counter financial institution Z, and the occurrence record is recorded in the record book. (However, the creditor becomes the delivery company B instead of the agent D), and when the occurrence record is recorded in the record book, the notification of the agent system 10 is received from the electronic bond recording institution system 30 through the financial institution system 20. The notification that the occurrence record is performed in the unit 17 is received, and the notification transmission unit 18 is further activated to notify the payment company terminal 40 of the payment company A and the delivery company terminal 50 of the delivery company B that the occurrence record is performed. The transmission is the same as the case of the periodic discount in the batch settlement service described above.

  In the above description, the payment system A, the delivery company B, and the purchase financial institution C in the agency system 10 send and receive payment data, discount requests, and notifications. The payment company terminal 40, the delivery company terminal 50, and the purchase finance. It is assumed that the data is transmitted / received to / from the institution terminal 60 via the network, but the information received by the agent by other means rather than receiving the information directly by data communication with the agent system 10. May be input to the agent system 10 by input from an input terminal by an operator, reading of information by a scanner, or the like, and the input information may be received by the agent system 10.

DESCRIPTION OF SYMBOLS 10 Agent system 11 Payment data reception part 12 Contract information storage part 13 Claim information storage part 14 Occurrence record request transmission part 15 Discount request reception part 16 Assignment record request transmission part 17 Notification reception part 18 Notification transmission part 20 Financial institution system 30 Electronics Debt recording institution system 40 Payment company terminal 50 Delivery company terminal 60 Purchase financial institution terminal

Claims (5)

A payer who pays for a claim subject to an electronically recorded claim, a supplier who has delivered goods or services related to the claim, a purchaser who purchases the claim, and a record request for making the claim as an electronically recorded claim Storage means for storing information on a contract for use of a collective payment service concluded by an agent acting on behalf of a transfer record request for a purchaser to purchase the electronic record receivable;
An accepting means for accepting payment data of a claim for requesting an occurrence record of an electronically recorded claim;
The storage means is searched to determine whether the payment data received by the receiving means is based on a claim subject to a collective payment service, and the payer and the payer related to the payment data are included in the contracting parties. Judgment means to judge from the presence or absence of a collective payment service usage contract,
Based on the payment data, the payer for the payment related to the payment data is determined to be a debtor based on the payment data for which the determination means determines that the payment data is not based on a claim subject to a collective payment service. Generate occurrence record request data for requesting the record of occurrence of electronic record receivables to a computer system of an electronic receivable record organization that manages the record ledgers of electronic record receivables, with the payment supplier relating to the payment data as a creditor First generation means;
A payment payer related to the payment data is determined as a debtor based on the payment data for payment data for which the determination means determines that the payment data is based on a claim subject to a collective payment service. A computer system of an electronic bond recording organization that manages a record ledger of an electronic record receivable that has a creditor as a creditor in a collective payment service use contract that includes a payer and a payer related to the payment data as contract parties. Generation record request data used for requesting the occurrence record of electronic record receivables, and the electronic record receivables in the computer system, wherein the agent is the transferor and the purchaser in the use contract of the collective settlement service is the transferee Second generation means for generating transfer record request data used to request transfer records of
An electronic record receivable record request management apparatus comprising: In the information related to the collective payment service usage contract stored in the storage means, each of the collective payment service usage contracts is recorded with either a periodic discount or a case-by-case condition for timing of purchase of the receivable,
The determination means, if there is a contract for use of a collective payment service including a payer and a payer of the payment relating to the payment data as a contracting party, determines whether a condition for timing of purchasing a bond is a regular discount or corresponding each time;
The second generation unit generates the occurrence when the determination unit determines that the payment data is based on a receivable subject to a lump sum settlement service and a condition for timing of purchasing the receivable is a periodic discount. 2. The record claim management device for electronic record claims according to claim 1, wherein the transfer record claim data is generated together with the record request data. In the information related to the collective payment service usage contract stored in the storage means, each of the collective payment service usage contracts is recorded with either a periodic discount or a case-by-case condition for timing of purchase of the receivable,
The determination means, if there is a contract for use of a collective payment service including a payer and a payer of the payment relating to the payment data as a contracting party, determines whether a condition for timing of purchasing a bond is a regular discount or corresponding each time;
The second generation means, when the determination means determines that the payment data is based on a receivable subject to a collective payment service, and that the condition for timing of purchasing the receivable corresponds to each time, the delivery 3. The record request management apparatus for electronic record claims according to claim 1, wherein the transfer record request data is generated after accepting a discount request for the electronic record claims from a person. The second generation means, when the determination means determines that the payment data is based on a receivable subject to a collective payment service, and the timing condition for purchasing the receivable is determined each time, the payment If a request for discount on the electronic record receivable from the supplier has not been received by the time the payment due date in the data is reached, the payer and the supplier of the payment related to the payment data are Instead of transfer record request data with the transferor as the transferor in the collective payment service usage contract and the purchaser in the collective payment service use contract as the transferee, the transferor and transferee are transferred. 4. The electronic record according to claim 2, wherein transfer record request data for requesting transfer record of the electronic record receivable is generated by a person. Recording billing management apparatus of receivables. A payer who pays for a claim subject to an electronically recorded claim, a supplier who has delivered goods or services related to the claim, a purchaser who purchases the claim, and a record request for making the claim as an electronically recorded claim An electronic record receivable record request management device comprising storage means for storing information relating to a collective payment service use contract concluded by an agent acting on behalf of a transfer record request for a purchaser to purchase the electronic record receivable An accepting step for accepting payment data of a claim for requesting an occurrence record of an electronic record claim,
The record request management device searches the storage means to determine whether the payment data received in the receiving step is based on a receivable subject to a collective payment service, and a payment payer related to the payment data A judgment step for judging from the presence or absence of a contract for use of a collective payment service including a supplier as a contracting party;
Payment for the payment data based on the payment data, for the payment data for which the record request management device has determined that the payment data is not based on a claim subject to a collective payment service in the determination step For requesting the record of occurrence of electronic record receivables to the computer system of the electronic receivables recording organization that manages the record ledgers of electronic record receivables, with the payer as the debtor and the payer of the payment relating to the payment data as the creditor A first generation step of generating occurrence record request data;
The record request management device relates to the payment data based on the payment data for the payment data for which the payment data is determined to be based on a claim subject to a collective payment service in the determination step. An electronic management of a record ledger for electronically recorded receivables, where the payer is the obligor and the agent in the use of the lump sum settlement service that includes the payer and payer of the payment related to the payment data as the contracting party is the creditor. The occurrence record request data used for requesting the occurrence record of the electronic record receivable to the computer system of the receivables record organization, the transferor as the transferor, and the purchaser in the use contract of the collective payment service as the transferee, A second generation process for generating transfer record request data used to request the transfer record of the electronic record receivable from the computer system And-up,
An electronic record receivable recording request management method comprising: