JP5875654B1 - Payment data processing system, method and program thereof - Google Patents

Abstract

Provided is a payment data processing system that collectively receives bill issue request data and electronic record receivable occurrence record request data and promotes the transition from a bill of exchange to an electronic record receivable. SOLUTION: Payment data receiving means 409 for extracting bill issue request data from payment data, and sending a user information inquiry request to the electronic bond recording institution system for a payment destination included in the extracted bill issue request data. Based on the result data, the user number corresponding to the payee is specified, and the transfer candidate data is deleted from the transfer candidate data creation means 410 for registering the transfer candidate data in the transfer candidate data storage unit and the bill issue data. A transfer candidate that creates payment data in the standard format of the electronic bond recording organization based on the bill issue request data processing means 412 that converts the data into a data format that can be accepted by the bill issue system and the transfer candidate data storage unit 408 And data processing means 413. [Selection] Figure 4

Description

  The present invention relates to a payment data processing system, method and program therefor, and more specifically, payment data for receiving and processing data for requesting the issuance of bills of payment and data for requesting the occurrence record of electronically recorded bonds. Processing system, its method and program, which extracts billing request data for companies that have obtained user numbers at electronic bond recording institutions and promotes the transition from bills of payment to electronic records The present invention relates to a payment data processing system, a method thereof and a program which can be performed.

  Densai (registered trademark), which started in 2013 as a new monetary claim that overcomes the problems of bills / designated claims (trade receivables, etc.), is attracting attention as a new payment method to replace bills. For paying companies, the issuance of bills is cumbersome and the burden of mailing bills and stamp taxes on bills is large. On the other hand, densai is easily generated by transmission / reception of electronic data, etc., and costs associated with the generation can be reduced.

  In addition to the above, Densai has many advantages such as the possibility of split transfer, but for various reasons, there are not a few paying companies that use both bills of payment and Densai as a settlement method.

  First of all, in order to shift from bills to densai, not only paying companies but also payee companies need a contract for using an electronic bond recording organization. Furthermore, when transferring Densai, the transferee company also needs a contract for use with an electronic bond recording organization, so the intention of the company that can be the transferee must also be considered. Therefore, even if the paying company has already adopted Densai as a means of payment with some paying companies, the bills are used together due to the circumstances of other paying companies or transferee companies. There is.

  By the way, conventionally, a financial institution provides a payment bill issuing agency service in which a bill of payment is created as a proxy and mailed to a payee company (for example, see Non-Patent Document 1). By using such a bill issuing agency service, the customer can reduce complicated procedures for issuing bills.

Sumitomo Mitsui Banking Corporation, “Billing Billing Service“ Notes Clear ”Service Overview”, [online], [searched on September 29, 2014], Internet <URL: http://www.smbc.co.jp/hojin / denshisaiken / sonota / notesclear />

  A bill issuing system of a financial institution that provides a payment bill issuing agency service and an electronic bond recording institution linkage system of a financial institution that provides an electronic bond recording agency service are designed independently. Therefore, for example, a paying company that uses both bills of payment and densai creates separate bill issuance request data for the bill issuance system and densai occurrence record request data for the electronic bond recording organization linkage system. Needed to be sent to the system.

  In addition, even if the payee company that currently uses the bill of payment as a means of payment is potentially allowing the shift to Densai, the payer company has few opportunities to know its intentions, I missed many opportunities.

  The present invention has been made in view of the above-described problems, and is a payment data processing system, method and program for receiving and processing bill issue request data and electronic record bond occurrence record request data collectively, A payment data processing system that can facilitate the transition from bills of payment to electronically recorded receivables by extracting billing issuance request data for companies that have acquired user numbers at bond receivables An object is to provide a method and a program.

  In order to solve the above problems, a payment data processing system according to the present invention is a payment data processing system connected to a bill issuing system, an electronic bond recording institution cooperation system, and an electronic bond recording institution system via a network. The transfer candidate data storage unit that stores the user number, payee company code, payee company name, record request date, and claim amount, and the payment data created in the standard format of the electronic bond record organization from the client computer. Then, from the received payment data, the bill issuance request data for the bill issuance system including the bill system identifier is extracted, and the remaining electronic record receivable occurrence record request data for the electronic receivables recording institution linkage system is extracted. Payment data receiving means for transmitting payment data to the electronic bond recording organization cooperation system; About the payee company code included in the bill issuance request data extracted by the payment data receiving means, the bill issuer system is inquired of the payee company name, and based on the acquired payee company name with respect to the electronic bond recording institution system When a user information inquiry request is transmitted and user information exists in the inquiry result data received from the electronic bond recording institution system, a user number corresponding to the payee company code is determined based on the inquiry result data. Transfer candidate data for registering transfer candidate data in the transfer candidate data storage unit based on bill issuing data including the payee company code specified by the user number and the acquired payee company name specified From the bill issuing data extracted by the creating means and the payment data receiving means, stored in the migration candidate data storage unit A bill issuance request data processing means for deleting a record including a payee company code, converting the data into a data format acceptable by the bill issuing system, and transmitting the converted data to the bill issuing system; And transfer candidate data processing means for creating payment data in an electronic bond recording organization standard format based on the department.

It is a figure which shows the whole network structure which concerns on one Embodiment of this invention. It is a figure which shows an example of the information stored in the payee master memory | storage part which concerns on one Embodiment of this invention. It is a figure which shows an example of the information stored in the user master memory | storage part which concerns on one Embodiment of this invention. It is a block diagram which shows the structure of the payment data processing system which concerns on one Embodiment of this invention. It is a figure which shows an example of the information stored in the transfer candidate data storage part which concerns on one Embodiment of this invention. It is a figure which shows the electronic bond recording organization standard format of generation | occurrence | production record request data. It is a figure which shows an example of the payment data which concern on one Embodiment of this invention. It is a figure which shows an example of the payment data after processing the payment data of FIG. 7 which concerns on one Embodiment of this invention. It is a figure which shows another example of the payment data which concern on one Embodiment of this invention. It is a figure which shows another example of the payment data which concern on one Embodiment of this invention. It is a figure which shows an example of the payment data after processing the payment data of FIG. 10 which concerns on one Embodiment of this invention. It is a flowchart which shows the payment data processing process which concerns on one Embodiment of this invention. It is a message sequence diagram which shows the payment data processing process which concerns on one Embodiment of this invention. It is a figure which illustrates the migration proposal screen which concerns on one Embodiment of this invention.

  Hereinafter, a payment data processing system and a payment data processing method according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

(System configuration)
FIG. 1 is a diagram showing an overall network configuration according to an embodiment of the present invention. In FIG. 1, a payment data processing system 101 installed in a bank 1 is installed in a client computer 102 installed in a payment company 2 that is a customer of the bank 1, a bill issuing system 103 installed in the bank 1, and a bank 1. The electronic bond recording institution cooperation system 104 is configured to communicate with a network 105 such as the Internet. The payment data processing system 101 and the electronic bond recording institution linkage system 104 are configured to communicate with an electronic bond recording institution system 106 installed in the electronic bond recording institution 3 via a network 107 such as a dedicated line. Yes.

  The payment data processing system 101 receives payment data including bill issue request data for the bill issue system 103 and electronic record bond occurrence record request data for the electronic bond recording institution cooperation system 104 from the client computer 102. The payment data processing system 101 can sort the received payment data into bill issue request data and electronic record receivable occurrence record request data, appropriately convert the data into a data format acceptable to each system, and transmit the data.

  In addition, the payment data processing system 101 makes a user information inquiry to the electronic bond recording institution system 106 based on the name of the payment destination in the bill issue request data, and as a result of the user information inquiry, the user corresponding to the payment destination. When the number is specified, it can be presented to the client computer 102 as a payment destination that can be transferred to the electronic record receivable.

  The bill issuance system 103 prints a bill of payment in a predetermined format based on the received bill issuance request data and the imprint data obtained and managed in advance from the payment company 2 and mails it to the payee company. . The bill issuing system 103 has a payee master storage unit for storing information on payees for each paying company, including a paying company code, a payee company code, a payee company name, and an address, as shown in FIG. Prepare.

  The electronic bond recording institution linkage system 104 makes it possible to use the service provided by the electronic bond recording institution system 106. In this embodiment, the electronic bond recording institution linkage system 104 receives the electronic record bond occurrence record request data from the payment data processing system 101. By transmitting to the electronic bond recording institution system 106, the electronic record receivable can be recorded in the record book of the electronic bond recording institution. As shown in FIG. 3, the electronic bond recording institution linkage system 104 uses a user number, user name, and settlement account information (branch number, deposit type (“1” for ordinary deposit, “1” for current deposit, “ 2 ”) and an account number), a user master storage unit for storing information on users registered with the electronic bond recording organization.

  Next, the configuration of the payment data processing system 101 will be described in detail with reference to the block diagram of FIG. In FIG. 4, only a necessary functional configuration is shown assuming a single computer system, but the payment data processing system 101 is configured as a part of a multi-functional distributed system by a plurality of computer systems. You can also.

  In the payment data processing system 101, a RAM 403, an input device 404, an output device 405, a communication control device 406, and a storage device 407 including a nonvolatile storage medium (ROM, HDD, etc.) are connected to the CPU 401 via the system bus 402. It has the structure made. The storage device 407 includes a program storage area for storing a software program for performing the above-described functions, and a data storage area for storing data acquired at any time, data as a processing result, and the like. Each means of the program storage area described below is actually an independent software program, its routines, components, and the like, which are called from the storage device 407 by the CPU 401 and expanded in the work area of the RAM 403 while appropriately referring to the database and the like. Each function is performed by being executed sequentially.

  The data storage area includes a migration candidate data storage unit 408.

  The transfer candidate data storage unit 408 stores payment data that can be transferred from a bill to an electronically recorded bond. In one embodiment, as shown in FIG. 5, the migration candidate data storage unit 408 includes a biller_user number, a payment company code, a biller_biller name, a trading partner_user number, and a payee company code. Stores the payee company name, the bank contract flag, the record request date, and the amount of receivables.

  The bank contract flag indicates whether or not the payee company has a use contract of the electronic bond recording organization 3 with the bank 1 managing the payment data processing system 101 (“0” when there is no use contract). If there is a usage contract, “1”).

  In this embodiment, the payment data processing system 101 receives the payment data created in the electronic bond recording organization standard format shown in FIG. 6 from the client computer 102, and includes a header record of payment data including a transferable data record. The biller_user number of the transfer candidate data storage unit 408, the payment company code included in the dummy item of the header record in the payment company code of the transfer candidate data storage unit 408, and the header record Claimer_Biller_name is the claimant_Biller_name in the transfer candidate data storage unit 408, Payee company code included in the dummy item of the data record is the payee company code in the transfer candidate data storage unit 408, and header record The recording request date included in the transfer candidate data storage unit 408 and the data recording date The credit amount of the code is stored in the credit amount of the migration candidate data storage unit 408, respectively.

  Further, the payment data processing system 101 stores the payee company name acquired from the bill issuing system 103 in the payee company name of the migration candidate data storage unit 408 based on the payee company code.

  Furthermore, the payment data processing system 101 stores the user number acquired from the electronic bond recording institution system 106 in the transaction partner_user number of the migration candidate data storage unit 408 based on the payee company name.

  If only software programs stored in the program storage area are listed, the payment data receiving means 409, the transfer candidate data creating means 410, the transfer proposal presenting means 411, the bill issue request data processing means 412, And migration candidate data processing means 413.

  When the payment data reception means 409 receives the payment data created in the electronic bond recording organization standard format from the client computer 102, the payment data reception means 409 uses the received payment data as the bill issue request data for the bill issue system 103 and the electronic bond recording organization linkage. The electronic record receivable occurrence record request data is distributed to the electronic record receivable occurrence record request data for the system 104, and the electronic record receivable occurrence record request data is transmitted to the electronic receivable record institution cooperation system 104. In the present embodiment, the payment data receiving means 409 extracts a data record including the bill system identifier in the transaction partner_user number, and transmits the remaining payment data to the electronic bond recording institution cooperation system 104.

  The migration candidate data creation means 410 inquires the bill issuing system 103 about the payee company name and address for the payee company code included in the dummy item of the data record of the payment data extracted by the payment data receiving means 409. Next, the migration candidate data creation means 410 transmits a user information inquiry request based on the acquired payee company name to the electronic bond recording institution system 106. When receiving the user information inquiry request, the electronic bond recording institution system 106 acquires user information including the payee company name to be inquired from the record original book, and returns inquiry result data.

  When the user information exists in the inquiry result data, the migration candidate data creation unit 410 specifies the user number corresponding to the payee based on the inquiry result data and the address acquired from the bill issuing system 103. In one embodiment, the migration candidate data creation unit 410 compares the address included in the inquiry result data with the address acquired from the bill issuing system 103, and identifies the user number of the matching user information.

  Subsequently, the migration candidate data creation unit 410 registers the migration candidate data in the migration candidate data storage unit 408 based on the payment data for the payee whose user number is specified. When registering the transfer candidate data, the transfer candidate data creating means 410 sets “1” to the bank contract flag of the corresponding transfer candidate data for the payment data to the payee whose bank account is included in the settlement account information of the inquiry result data. set.

  Based on the transfer candidate data storage unit 408, the transfer proposal presenting unit 411 can present a payment destination that can be transferred to the electronic record bond to the client computer 102. In one embodiment, the transfer proposal presenting means 411 may display a transfer proposal screen including a transferable payee company code, a payee company name, and a transfer flag on the client computer 102 as shown in FIG. it can. The migration flag of this embodiment is an input item that allows selection of either “do not consider migration” or “consider migration”, and can be set for each payable customer.

  When the OK button is pressed on the migration proposal screen, the migration proposal presentation unit 411 acquires information set on the migration proposal screen from the client computer 102. In one embodiment, based on the acquired information, the record including the payee company code for which the “do not consider migration” instruction is set is deleted from the migration candidate data storage unit 408.

  The bill issuance request data processing means 412 deletes the record including the payee company code stored in the migration candidate data storage unit 408 from the payment data distributed as the bill issuance request data for the bill issuance system 103, and issuance of the bill The system 103 converts the data into an acceptable data format, and transmits the converted data to the bill issuing system 103.

  The migration candidate data processing unit 413 determines whether there is migration candidate data with a bank contract. In the present embodiment, it is determined whether or not the record “bank contract flag: 1” exists in the migration candidate data storage unit 408. If there is transfer candidate data with a bank contract, the transfer candidate data processing means 413 makes an inquiry to the electronic bond recording organization cooperation system 104 for the transaction partner_user number in the transfer candidate data storage unit 408 with the bank contract. Get payment account information.

  Finally, the transfer candidate data processing unit 413 creates payment data in an electronic bond recording institution standard format based on the transfer candidate data storage unit 408 (and the acquired settlement account information), and transmits the payment data to the client computer 102.

  In the present embodiment, the transfer candidate data processing means 413 acquires the settlement account information from the user master storage unit of the electronic bond recording institution linkage system 104, but in another embodiment, the electronic bond recording institution system 106 You can also use the provided user information inquiry service.

  In this embodiment, the migration candidate data processing unit 413 transmits the payment data created in the electronic bond recording institution standard format to the client computer 102, but in another embodiment, the created payment data is sent to the electronic bond. It can also be transmitted to the recording institution cooperation system 104.

(Embodiment)
Next, payment data processing steps according to the first to fourth embodiments will be described with reference to the flowchart of FIG. 12 and the message sequence diagram of FIG. It is assumed that the paying company A makes a use contract of the electronic bond recording organization 3 with the bank 1 in advance and is given a user number (000000001) from the electronic bond recording organization 3. The bank 1 registers the user who has signed a usage contract for the electronic bond recording institution 3 with the bank 1 in the user master storage unit of the electronic bond recording institution linkage system 104, as shown in FIG. It is assumed that a record to be stored is stored. In addition, the payment company A makes a contract for using the bill issuing agency service provided by the bank 1 in advance, and the company shown in FIG. 2 issues the bill as the payment destination of the payment company A (payment company code: 1111). Assume that it is stored in the payee master storage unit of the system 103.

(First embodiment)
The person in charge X of the payment company A creates payment data in the electronic bond recording organization standard format via the client computer 102 and transmits it to the payment data processing system 101 (S1201). In this embodiment, it is assumed that the payment data shown in FIG. 7 is created. The header record includes biller information (user identification number: 000000001, biller name: payment company A), biller settlement account information (bank number: 0009, branch number: 200, deposit type: 2, account number) : 1111111, etc.), in addition to the record request date (2014/9/30), which is the date of occurrence of receivables (electronically recorded receivables and bills payable), the paying company code for uniquely identifying the paying company in the bill issuing system 103 (1111) is stored in the dummy item.

  Data record 1 is electronic record receivable occurrence record request data for the electronic receivables record institution cooperation system 104, and information on the counterparty (user identification number: 111111111) and settlement account information of the counterparty (bank number: 0009, branch) Number: 200, Deposit type: 2, Account number: 4234567, etc.), and the amount of receivable (3,000,000 yen) are stored.

  The data record 2 is bill issuance request data for the bill issuance system 103, and the transaction partner_user number is an identifier for bill system (indicating that the data is bill issuance request data for the bill issuance system 103). tegata) is stored. In addition to the amount of receivable (1,000,000 yen), the data record 2 stores a payee company code (5555) for uniquely identifying the payee company in the bill issuing system 103 in a dummy item.

  The data record 3 is also bill issue request data for the bill issue system 103, and a bill system identifier (tegata) is stored in the trading partner_user number. Further, in data record 3, in addition to the amount of receivable (5,000,000 yen), the payee company code (6666) is stored in the dummy item.

  The payment data created by the user X includes other additional data records, trailer records, and end records, but will not be described in detail.

  When the payment data receiving means 409 of the payment data processing system 101 receives the payment data created in the electronic bond recording organization standard format from the client computer 102, the received payment data is converted into the bill issuing request data for the bill issuing system 103. Then, the electronic record receivable occurrence record request data is distributed to the electronic record receivable occurrence record request data for the electronic bond record institution cooperation system 104 (S1202), and the electronic record receivable occurrence record request data is transmitted to the electronic receivable record institution cooperation system 104 (S1203).

  In the present embodiment, the payment data receiving means 409 extracts the data record 2 and the data record 3 including the bill system identifier (tegata) in the transaction partner_user number, and the remaining payment data including the data record 1 is extracted. It is assumed that it has been transmitted to the electronic bond recording organization cooperation system 104.

  In S1204, the migration candidate data creation means 410 of the payment data processing system 101 sends the payee company code to the bill issuing system 103 for the payee company code included in the dummy item of the data record of the payment data extracted by the payment data reception means 409. Query name and address. When the bill issuing system 103 retrieves and transmits the payee company name and address from the payee master storage unit (S1205), the transfer candidate data creation means 410 sends the acquired payee company to the electronic bond recording institution system 106. A user information inquiry request based on the name is transmitted (S1206).

  In this embodiment, the migration candidate data creation means 410 inquires about the payee company code (5555, 6666), and from the bill issuing system 103, the payee company name (Kanto store) for the payee company code (5555) and It is assumed that an address (Minato-ku, Tokyo ...), a payee company name (Japanese store) and an address (Chuo-ku, Tokyo ...) for the payee company code (6666) are acquired.

  Upon receiving the user information inquiry request, the electronic bond recording institution system 106 acquires user information including the payee company name to be inquired from the record original book, and returns inquiry result data (S1207). In one embodiment, in response to a user information inquiry request using a company name as a key, the electronic bond recording institution system 106 includes 1 in addition to the user number and address, when user information including the target company name exists. Alternatively, query result data including a plurality of settlement account information (only bank number and branch number) is returned.

  In the present embodiment, the electronic bond recording institution system 106 responds to a user information inquiry request with the company name (Kanto store) as a key, and a user number (000000100), an address (Minato-ku, Tokyo ...), and Returns the inquiry result data including the settlement account information (bank number: 0009, branch number: 200), and in response to a user information inquiry request with the company name (Japanese store) as the key, the user number (000000101) and address (Tokyo) Chuo-ku, Tokyo), and the return of inquiry result data including settlement account information 1 (bank number: 0009, branch number: 200) and settlement account information 2 (bank number: 0009, branch number: 300) To do.

  If the user information exists in the branch of S1208, the migration candidate data creation unit 410 specifies the user number corresponding to the payee based on the inquiry result data and the address acquired from the bill issuing system 103 (S1209). ). In one embodiment, the migration candidate data creation unit 410 compares the address included in the inquiry result data with the address acquired from the bill issuing system 103, and identifies the user number of the matching user information.

  In the present embodiment, it is assumed that the user numbers are specified for both the payee 1 (payee company name: Kanto store) and the payee 2 (payee company name: Japanese store).

  In S1210, the migration candidate data creation unit 410 registers the migration candidate data in the migration candidate data storage unit 408 based on the payment data for the payee whose user number is specified. When registering the transfer candidate data, the transfer candidate data creating means 410 sets “1” to the bank contract flag of the corresponding transfer candidate data for the payment data to the payee whose bank account is included in the settlement account information of the inquiry result data. set.

  In this embodiment, since any payee has the bank account (bank number: 0009) in the settlement account information, registration of migration candidate data in the migration candidate data storage unit 408 as shown in FIG. Is assumed to have been performed.

  Subsequently, the migration proposal presenting means 411 of the payment data processing system 101 presents the payment destination that can be migrated to the electronic record bond to the client computer 102 based on the migration candidate data storage unit 408 (S1211).

  In this embodiment, the migration proposal presenting means 411 displays a migration proposal screen including a payment destination 1 (Kanto store) and a payment destination 2 (Japanese store) as transferable payment destinations as shown in FIG. It shall be displayed in

  When the user X inputs an intention to move on the migration proposal screen on the client computer 102 and presses the OK button (S1212), the migration proposal presenting means 411 receives the migration intention set on the migration proposal screen from the client computer 102. The information is acquired, and the record including the payee company code for which the instruction “do not consider transfer” is set is deleted from the transfer candidate data storage unit 408 (S1213).

  In the present embodiment, it is assumed that an instruction to “consider migration” is set for the payee 1 and the payee 2, and the transfer candidate data storage unit 408 still has a record.

  In S1214, the bill issue request data processing means 412 of the payment data processing system 101 receives the payee stored in the migration candidate data storage unit 408 from the payment data distributed as the bill issue request data for the bill issue system 103 in S1202. Delete records that contain company codes. In the present embodiment, the data record 2 including the payee company code (5555, 6666) stored in the migration candidate data storage unit 408 and the data record 3 are deleted.

  Thereafter, the bill issuance request data processing means 412 converts the bill issuance request data into a data format acceptable by the bill issuance system 103, and transmits the converted data to the bill issuance system 103 (S1215).

  In S1216, the migration candidate data processing unit 413 of the payment data processing system 101 determines whether there is migration candidate data with a bank contract. In the present embodiment, since the record “bank contract flag: 1” exists in the migration candidate data storage unit 408, the process proceeds to S1217, and the migration candidate data processing unit 413 uses the transaction partner_use of the migration candidate data with the bank contract. For the person number, the electronic bond recording institution cooperation system 104 is inquired for settlement account information (S1217). When the electronic bond recording institution linkage system 104 retrieves and transmits settlement account information from the user master storage unit (S1218), the transfer candidate data processing unit 413, based on the transfer candidate data storage unit 408 and the acquired payment account information. Then, payment data is created in the electronic bond recording institution standard format and transmitted to the client computer 102 (S1219).

  In this embodiment, the transfer candidate data processing unit 413 makes an inquiry to the electronic bond recording institution cooperation system 104 for the transaction partner_user number (000000100, 000000101) of the transfer candidate data storage unit 408, and the transaction partner_user. Settlement account information (branch number: 200, deposit type: 2, account number: 1234567) and settlement account information 1 (branch number: 200, deposit type: 2, (Account number: 2234567) and settlement account information 2 (branch number: 300, deposit type: 2, account number: 3234567) are acquired, and payment data as shown in FIG. it can.

  When a plurality of settlement account information is acquired for the trading partner_user number, the transfer candidate data processing unit 413, for example, “deposit type is 2: giving priority to current account”, “branch number” It is possible to select one settlement account information using an arbitrary method such as “prioritize a small account” and use it to create payment data.

(Second Embodiment)
In the second embodiment, a case will be described in which the person in charge X of the payment company A who has created the same payment data (FIG. 7) as in the first embodiment does not consider the transition from a bill to an electronically recorded bond. The same processing as that of the first embodiment is performed from S1201 to S1210. In S1211, the migration proposal presenting unit 411, as shown in FIG. It is assumed that the migration proposal screen including the destination 2 (Japanese store) is displayed on the client computer 102.

  When the user X inputs an intention to move on the migration proposal screen on the client computer 102 and presses the OK button (S1212), the migration proposal presenting means 411 receives the migration intention set on the migration proposal screen from the client computer 102. The information is acquired, and the record including the payee company code for which the instruction “do not consider transfer” is set is deleted from the transfer candidate data storage unit 408 (S1213).

  In this embodiment, it is assumed that an instruction “do not consider migration” is set for the payee 1 and the payee 2, and the record including the payee company code (5555, 6666) is deleted from the transfer candidate data storage unit 408. .

  In S1214, the bill issue request data processing means 412 obtains a record including the payee company code stored in the migration candidate data storage unit 408 from the payment data distributed as the bill issue request data for the bill issue system 103 in S1202. delete. In this embodiment, since there is no record in the migration candidate data storage unit 408, the process proceeds to S1215, and the bill issue request data processing unit 412 converts the bill issue request data into a data format that can be accepted by the bill issue system 103. The converted data is transmitted to the bill issuing system 103 (S1215).

  In this embodiment, in S1202, the payment data including the data record 2 and the data record 3 distributed as bill issue request data is converted into a data format acceptable by the bill issue system 103, and the converted data is converted into a bill issue system. It is assumed that the message is transmitted to 103.

  In S1216, the migration candidate data processing unit 413 determines whether or not there is migration candidate data with a bank contract. In this embodiment, since there is no record in the migration candidate data storage unit 408, the process proceeds to S1219. However, since there is no record in the migration candidate data storage unit 408, the process ends.

(Third embodiment)
In the third embodiment, it is assumed that the person in charge X of the payment company A created payment data (FIG. 9) different from the first embodiment and the second embodiment, and considers the transition from bills to electronic record receivables. A case where there is no payee to be described will be described.

  The person in charge X of the payment company A creates payment data in the electronic bond recording organization standard format via the client computer 102 and transmits it to the payment data processing system 101 (S1201). As shown in FIG. 9, the header record includes biller information (user identification number: 000000001, biller name: paying company A), biller settlement account information (bank number: 0009, branch number: 200). , Deposit type: 2, account number: 1111111, etc.), in addition to the record request date (October 31, 2014) that is the date of occurrence of receivables (electronically recorded receivables and bills of payment), the bill issuing system 103 uniquely identifies the paying company The payment company code (1111) for identification is stored in the dummy item.

  Data record 1 is electronic record receivable occurrence record request data for the electronic receivables record institution cooperation system 104, and information on the counterparty (user identification number: 111111111) and settlement account information of the counterparty (bank number: 0009, branch) Number: 200, Deposit type: 2, Account number: 4234567, etc.), and the amount of receivable (3,000,000 yen) are stored.

  The data record 2 is bill issuance request data for the bill issuance system 103, and the transaction partner_user number is an identifier for bill system (indicating that the data is bill issuance request data for the bill issuance system 103). tegata) is stored. In addition to the amount of receivable (1,000,000 yen), the data record 2 stores a payee company code (3333) for uniquely identifying the payee company in the bill issuing system 103 in a dummy item.

  The data record 3 is also bill issue request data for the bill issue system 103, and a bill system identifier (tegata) is stored in the trading partner_user number. Further, in data record 3, in addition to the amount of receivable (1,000,000 yen), the payee company code (4444) is stored in the dummy item.

  The payment data created by the user X includes other additional data records, trailer records, and end records, but will not be described in detail.

  When the payment data reception means 409 receives the payment data created in the electronic bond recording organization standard format from the client computer 102, the payment data reception means 409 uses the received payment data as the bill issue request data for the bill issue system 103 and the electronic bond recording organization linkage. The data is distributed to the electronic record receivable occurrence record request data for the system 104 (S1202), and the electronic record receivable occurrence record request data is transmitted to the electronic receivable record organization cooperation system 104 (S1203).

  In the present embodiment, the payment data receiving means 409 extracts the data record 2 and the data record 3 including the bill system identifier (tegata) in the transaction partner_user number, and the remaining payment data including the data record 1 is extracted. It is assumed that it has been transmitted to the electronic bond recording organization cooperation system 104.

  In S1204, the migration candidate data creation means 410 of the payment data processing system 101 sends the payee company code to the bill issuing system 103 for the payee company code included in the dummy item of the data record of the payment data extracted by the payment data reception means 409. Query name and address. When the bill issuing system 103 retrieves and transmits the payee company name and address from the payee master storage unit (S1205), the transfer candidate data creation means 410 sends the acquired payee company to the electronic bond recording institution system 106. A user information inquiry request based on the name is transmitted (S1206).

  In this embodiment, the migration candidate data creation means 410 inquires about the payee company code (3333, 4444), and from the bill issuing system 103, the payee company name (Saitama store) and the payee company code (3333) and It is assumed that the address (Saitama Prefecture ...), the payee company name (Yokohama store) and the address (Kanagawa Prefecture ...) for the payee company code (4444) are acquired.

  Upon receiving the user information inquiry request, the electronic bond recording institution system 106 acquires user information including the payee company name to be inquired from the record original book, and returns inquiry result data (S1207).

  In the present embodiment, the electronic bond recording institution system 106 responds to both a user information inquiry request using the company name (Saitama store) as a key and a user information inquiry request using the company name (Yokohama store) as a key. It is assumed that the inquiry result data with no corresponding user information is returned.

  If the user information does not exist in the branch of S1208, the process proceeds to S1215, and the bill issue request data processing unit 412 converts the bill issue request data into a data format that can be accepted by the bill issue system 103, and the converted data is converted into a bill. It is transmitted to the issuing system 103.

  In this embodiment, in S1202, the payment data including the data record 2 and the data record 3 distributed as bill issue request data is converted into a data format acceptable by the bill issue system 103, and the converted data is converted into a bill issue system. It is assumed that the message is transmitted to 103.

  In S1216, the migration candidate data processing unit 413 determines whether or not there is migration candidate data with a bank contract. In this embodiment, since there is no record in the migration candidate data storage unit 408, the process proceeds to S1219. However, since there is no record in the migration candidate data storage unit 408, the process ends.

(Fourth embodiment)
In the fourth embodiment, payment data (FIG. 10) different from those in the first to third embodiments is created by the person in charge X of the payment company A, and a part of studying the transition from bills to electronic record receivables The case where the payee has not signed a usage contract for the electronic bond recording organization 3 with the Bank will be described.

  The person in charge X of the payment company A creates payment data in the electronic bond recording organization standard format via the client computer 102 and transmits it to the payment data processing system 101 (S1201). As shown in FIG. 10, the header record includes biller information (user identification number: 000000001, biller name: paying company A), biller settlement account information (bank number: 0009, branch number: 200). , Deposit type: 2, account number: 1111111, etc.), in addition to the record request date (2014/11/30) that is the date of occurrence of receivables (electronically recorded receivables and bills payable), the bill issuing system 103 uniquely identifies the paying company The payment company code (1111) for identification is stored in the dummy item.

  Data record 1 is electronic record receivable occurrence record request data for the electronic receivables record institution cooperation system 104, and information on the counterparty (user identification number: 111111111) and settlement account information of the counterparty (bank number: 0009, branch) Number: 200, Deposit type: 2, Account number: 4234567, etc.), and the amount of receivable (3,000,000 yen) are stored.

  The data record 2 is bill issuance request data for the bill issuance system 103, and the transaction partner_user number is an identifier for bill system (indicating that the data is bill issuance request data for the bill issuance system 103). tegata) is stored. In addition to the amount of receivable (1,000,000 yen), the data record 2 stores a payee company code (5555) for uniquely identifying the payee company in the bill issuing system 103 in a dummy item.

  The data record 3 is also bill issue request data for the bill issue system 103, and a bill system identifier (tegata) is stored in the trading partner_user number. Further, in data record 3, in addition to the amount of receivable (2,000,000 yen), the payee company code (7777) is stored in the dummy item.

  The payment data created by the user X includes other additional data records, trailer records, and end records, but will not be described in detail.

  When the payment data receiving means 409 of the payment data processing system 101 receives the payment data created in the electronic bond recording organization standard format from the client computer 102, the received payment data is converted into the bill issuing request data for the bill issuing system 103. Then, the electronic record receivable occurrence record request data is distributed to the electronic record receivable occurrence record request data for the electronic bond record institution cooperation system 104 (S1202), and the electronic record receivable occurrence record request data is transmitted to the electronic receivable record institution cooperation system 104 (S1203).

  In the present embodiment, the payment data receiving means 409 extracts the data record 2 and the data record 3 including the bill system identifier (tegata) in the transaction partner_user number, and the remaining payment data including the data record 1 is extracted. It is assumed that it has been transmitted to the electronic bond recording organization cooperation system 104.

  In S1204, the migration candidate data creation means 410 of the payment data processing system 101 sends the payee company code to the bill issuing system 103 for the payee company code included in the dummy item of the data record of the payment data extracted by the payment data reception means 409. Query name and address. When the bill issuing system 103 retrieves and transmits the payee company name and address from the payee master storage unit (S1205), the transfer candidate data creation means 410 sends the acquired payee company to the electronic bond recording institution system 106. A user information inquiry request based on the name is transmitted (S1206).

  In this embodiment, the migration candidate data creation means 410 inquires about the payee company code (5555, 7777), and from the bill issuing system 103, the payee company name (Kanto store) for the payee company code (5555) and It is assumed that the address (Minato-ku, Tokyo ...), the payee company code (7777), the payee company name (Osaka store) and the address (Osaka prefecture ...) are acquired.

  Upon receiving the user information inquiry request, the electronic bond recording institution system 106 acquires user information including the payee company name to be inquired from the record original book, and returns inquiry result data (S1207).

  In the present embodiment, the electronic bond recording institution system 106 responds to a user information inquiry request with the company name (Kanto store) as a key, and a user number (000000100), an address (Minato-ku, Tokyo ...), and Returns inquiry result data including settlement account information (bank number: 0009, branch number: 200), and in response to a user information inquiry request with company name (Osaka store) as the key, user number (777777777), address (Osaka) )) And settlement account information (bank number: 7777, branch number: 777) is returned.

  If the user information exists in the branch of S1208, the migration candidate data creation unit 410 specifies the user number corresponding to the payee based on the inquiry result data and the address acquired from the bill issuing system 103 (S1209). ).

  In the present embodiment, it is assumed that user numbers are specified for both payee 1 (payee company name: Kanto store) and payee 2 (payee company name: Osaka store).

  In S1210, the migration candidate data creation unit 410 registers the migration candidate data in the migration candidate data storage unit 408 based on the payment data for the payee whose user number is specified. When registering the transfer candidate data, the transfer candidate data creating means 410 sets “1” to the bank contract flag of the corresponding transfer candidate data for the payment data to the payee whose bank account is included in the settlement account information of the inquiry result data. set.

  In this embodiment, for payment data for a payee 1 (payee company name: Kanto store) having the bank account (bank number: 0009) in the settlement account information, the bank contract flag of the corresponding migration candidate data is “1”. It is assumed that migration candidate data is registered in the migration candidate data storage unit 408 as shown in FIG.

  Subsequently, the migration proposal presenting means 411 of the payment data processing system 101 presents the payment destination that can be migrated to the electronic record bond to the client computer 102 based on the migration candidate data storage unit 408 (S1211).

  In the present embodiment, it is assumed that the migration proposal presenting means 411 displays a migration proposal screen including a payment destination 1 (Kanto store) and a payment destination 2 (Osaka store) as transferable payment destinations on the client computer 102.

  When the user X inputs an intention to move on the migration proposal screen on the client computer 102 and presses the OK button (S1212), the migration proposal presenting means 411 receives the migration intention set on the migration proposal screen from the client computer 102. The information is acquired, and the record including the payee company code for which the instruction “do not consider transfer” is set is deleted from the transfer candidate data storage unit 408 (S1213).

  In the present embodiment, it is assumed that an instruction to “consider migration” is set for the payee 1 and the payee 2, and the transfer candidate data storage unit 408 still has a record.

  In S1214, the bill issue request data processing means 412 of the payment data processing system 101 receives the payee stored in the migration candidate data storage unit 408 from the payment data distributed as the bill issue request data for the bill issue system 103 in S1202. Delete records that contain company codes. In this embodiment, the data record 2 including the payee company code (5555, 7777) stored in the migration candidate data storage unit 408 and the data record 3 are deleted.

  Thereafter, the bill issuance request data processing means 412 converts the bill issuance request data into a data format acceptable by the bill issuance system 103, and transmits the converted data to the bill issuance system 103 (S1215).

  In S1216, the migration candidate data processing unit 413 of the payment data processing system 101 determines whether there is migration candidate data with a bank contract. In the present embodiment, since the record “bank contract flag: 1” exists in the migration candidate data storage unit 408, the process proceeds to S1217, and the migration candidate data processing unit 413 uses the transaction partner_use of the migration candidate data with the bank contract. For the person number, the electronic bond recording institution cooperation system 104 is inquired for settlement account information (S1217). When the electronic bond recording institution linkage system 104 retrieves and transmits settlement account information from the user master storage unit (S1218), the transfer candidate data processing unit 413, based on the transfer candidate data storage unit 408 and the acquired payment account information. Then, payment data is created in the electronic bond recording institution standard format and transmitted to the client computer 102 (S1219).

  In this embodiment, the transfer candidate data processing unit 413 makes an inquiry to the electronic bond recording institution linkage system 104 for the transaction partner_user number (000000100) of the transfer candidate data storage unit 408, and the transaction partner_user number ( 11 (000000100) can be acquired (branch number: 200, deposit type: 2, account number: 1234567) and payment data as shown in FIG.

  As shown in FIG. 11, for the payee (Osaka store) who has not signed a usage contract for the electronic bond recording organization 3 with the Bank, the transaction partner_user number (777777777) remains set. Accordingly, the person in charge X who has received the payment data confirms the settlement account information with the payee (Osaka store) and sets the settlement account information of the payment data, whereby the electronic record receivable for the electronic bond recording institution linkage system 104 is set. It can be used as generation record request data.

  In addition, the user information inquiry service provided by Densai Net (registered trademark) system, one of the electronic receivables recording institutions, is with the financial institution that performs user information inquiry as of the filing date. For users who do not have a Densai Net usage contract, detailed settlement account information including the account number cannot be obtained. In the future, due to a change in the service contents of the electronic bond recording institution system 106, a process for acquiring detailed settlement account information will be established even for users who have a contract with the electronic bond recording institution 3 only with other banks. The payment data in which the settlement account information is set can be transmitted to the client computer 102 even for a user who does not have a usage contract for the electronic bond recording organization 3 with the Bank.

  As described above, according to the present invention, a payment company that uses both a bill of payment and an electronically recorded receivable as a settlement means creates payment data including bill issuing data and electronically recorded receivable occurrence claim data in a lump. Processing can be outsourced to an institution.

  In addition, the payment data processing system of the present invention extracts payment data for bill issuance with a company whose user number has been acquired at an electronic bond recording institution as a payee, and payment that can be transferred from the bill of payment to an electronic record bond. With this configuration, the paying company can recognize a payee that is potentially allowed to shift to an electronically-recorded bond, and promote the shift from a bill of exchange to an electronically-recorded bond.

Claims (7)

A payment data processing system connected via a network to a bill issuing system, an electronic bond recording institution cooperation system, and an electronic bond recording institution system,
A migration candidate data storage unit for storing a user number, a payee company code, a payee company name, a record request date, and a claim amount;
Receiving payment data created in a standard format of electronic bond recording organization from a client computer, and extracting the bill issuing request data for the bill issuing system including the bill system identifier from the received payment data, and Payment data receiving means for transmitting the remaining payment data, which is electronic record receivable occurrence record request data for a recording institution cooperation system, to the electronic receivable recording institution cooperation system;
About the payee company code included in the bill issuance request data extracted by the payment data receiving means, the payee company name is inquired to the bill issuing system, and the acquired payee company name is sent to the electronic bond recording institution system. Based user information inquiry request,
If there is user information in the inquiry result data received from the electronic bond recording institution system, based on the inquiry result data, specify the user number corresponding to the payee company code,
Transfer candidate data creation means for registering transfer candidate data in the transfer candidate data storage unit based on bill issuing data including the payee company code in which the user number is specified and the acquired payee company name; ,
From the bill issue request data extracted by the payment data receiving means, delete the record including the payee company code stored in the migration candidate data storage unit, and convert it into a data format acceptable by the bill issue system, Bill issue request data processing means for transmitting the converted data to the bill issuing system;
A migration candidate data processing means for creating payment data in an electronic bond recording institution standard format based on the migration candidate data storage unit. Based on the migration candidate data storage unit, the client computer is provided with a migration proposal screen that presents a payment destination that can be transferred to the electronic record receivable, and the payment destination for which an instruction not to consider the migration is set on the migration proposal screen The system according to claim 1, further comprising a migration proposal presenting unit that deletes a record including a company code from the migration candidate data storage unit. The migration candidate data storage unit is configured to determine whether the payee company has a use contract for an electronic bond recording institution managing the electronic bond recording institution system with a financial institution managing the payment data processing system. Further store the Bank contract flag indicating
The migration candidate data creation means sets a bank contract flag of the corresponding migration candidate data for a payment destination whose bank account is included in the settlement account information of the inquiry result data,
The transfer candidate data processing means inquires about the user number of the transfer candidate data for which the bank contract flag is set, obtains settlement account information by inquiring to the electronic bond recording organization cooperation system, and acquires the acquired settlement account information. The system according to claim 1, wherein the payment data is used to create the payment data. Connected to the bill issuing system, electronic bond recording institution linkage system, and electronic bond recording institution system via the network, and stores the user number, payee company code, payee company name, record request date, and claim amount In a payment data processing system having a candidate data storage unit,
The payment data receiving means of the payment data processing system receiving payment data created in a standard format of an electronic bond recording organization from a client computer;
The payment data receiving means, from the received payment data, extracting bill billing request data for the bill issuing system including a bill system identifier;
The payment data receiving means transmitting the remaining payment data, which is electronic record receivable occurrence record request data for the electronic bond recording institution cooperation system, to the electronic bond recording institution cooperation system;
The payment candidate data creation means of the payment data processing system inquires the bill issuing system for the name of the payee company for the payee company code included in the bill issuance request data extracted by the payment data reception means;
The transition candidate data creation means transmits a user information inquiry request based on the acquired payee company name to the electronic bond recording institution system;
When the user information exists in the inquiry result data received from the electronic bond recording institution system, the migration candidate data creation means specifies the user number corresponding to the payee company code based on the inquiry result data. And steps to
The migration candidate data creation means registers the migration candidate data in the migration candidate data storage unit based on the bill issuance billing data including the payee company code in which the user number is specified and the acquired payee company name. The steps of
The bill issuance request data processing means of the payment data processing system deletes the record including the payee company code stored in the migration candidate data storage unit from the bill issuance claim data extracted by the payment data receiving means, Converting to a data format acceptable to the bill issuing system;
The bill issuing request data processing means transmits the converted data to the bill issuing system;
The transfer candidate data processing means of the payment data processing system performs the step of creating payment data in an electronic bond recording organization standard format based on the transfer candidate data storage unit. After the step where the migration candidate data creating means registers migration candidate data,
A step of providing a migration proposal screen for presenting a payment destination that can be transferred to an electronically recorded bond to the client computer, based on the migration candidate data storage unit, the migration proposal presenting means of the payment data processing system;
The migration proposal presenting means further executes a step of deleting from the migration candidate data storage unit a record including a payee company code in which an instruction not to consider migration is set on the migration proposal screen. The method of claim 4. The migration candidate data storage unit is configured to determine whether the payee company has a use contract for an electronic bond recording institution managing the electronic bond recording institution system with a financial institution managing the payment data processing system. Further store the Bank contract flag indicating
The transfer candidate data creation means sets the bank contract flag of the corresponding transfer candidate data for a payment destination whose bank account is included in the settlement account information of the inquiry result data when registering the transfer candidate data,
Before the migration candidate data processing means creates payment data,
The transfer candidate data processing means further executes a step of obtaining the settlement account information by inquiring of the electronic bond recording organization cooperation system for the user number of the transfer candidate data in which the bank contract flag is set,
5. The method according to claim 4, wherein the migration candidate data processing means creates payment data using the acquired settlement account information.   A program for causing a computer to execute the method according to claim 4.

Images