JP5864636B2 - Electronic record receivable counterparty name display system - Google Patents

Description

  The present invention relates to an electronic record receivable counterparty user name display system and an electronic record receivable counterparty user name display method, and in particular, when making an electronic record receivable record request, displays the name of the counterpart user, The present invention relates to a system for displaying a name of a counterparty user of an electronic record receivable and a method of displaying a name of a counterparty of an electronic record receivable.

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

  Electronically recorded receivables manage information on a computer compared to conventional paper bills, so you can avoid risks such as loss or theft associated with paper bills and convert the receivables before the settlement deadline. Therefore, the effect of smoothing the cash flow of companies is also expected. In addition, since the electronically recorded receivable can be divided and transferred in addition to the transaction at the face value, it is possible to flexibly deal with such as dividing only the necessary amount and cashing it at an early stage.

  The Electronic Record Claims Act presupposes that multiple electronic bond recording institutions will be established from the viewpoint of ensuring user convenience. There are two main types of electronic bond recording institutions: electronic bond recording institutions established by so-called megabanks and electronic bond recording institutions established by national bank associations. The latter provides all bank participation services (hereinafter “Densai Net” (registered trademark)) and can only be used through the contact of each financial institution (hereinafter “participating financial institutions”). .

  Users who wish to use electronically recorded receivables need to register their accounts through a system provided by participating financial institutions (hereinafter “banking system”). When an account is registered, a user number for identifying a user is allocated in the electronic bond recording institution, and user information including a user name is recorded in the record book of the electronic bond recording institution.

  When the account is registered, the user can make a request for recording of the occurrence of electronic record receivables. When an accrual record request is made, the banking system creates an accrual record request data file having a format common to all financial institutions and sends it to a system provided by the electronic bond recording institution (hereinafter referred to as “electronic bond recording institution system”). To do. In response to the receipt of the request data file, the electronic bond recording institution system adds the corresponding record ledger record to the electronic record receivable database of the electronic bond recording institution system, thereby generating the electronic record receivable become.

  Many participating financial institutions provide an input interface for the user in their banking system, and the user can make the above-described generation record request by using the input interface. Specifically, by inputting information such as creditor and debtor user numbers and settlement account information from the input interface, the above-described occurrence record request data file is created based on the information. .

JP 2011-039799 A

  By the way, when executing the record request for the occurrence of electronically recorded receivables, the creditor request method (in which the creditor designates the obligor (the other party user)) to generate the electronically recorded receivable from the creditor side, and from the debtor side There is a debtor billing system that generates electronically recorded receivables (the debtor designates the creditor (the other party's user)). Regardless of the generation method, from the standpoint of requesting occurrence records, the name of the other party's user (name of debtor in the case of creditor claim method, creditor in the case of debtor claim method) Name) is required.

  According to the specifications of the current electronic bond recording institution system, when registering an account (user), the user name is also recorded in the record book. Under these circumstances, in order to confirm the name of the other party's user when executing the claim for occurrence record in the situation where the electronic record receivable has not yet occurred, the user information inquiry function provided by the electronic receivables recording institution system It is necessary to use. In the user information inquiry function, the bank system creates a user information inquiry request data file including the user number and / or settlement account information of the user to be inquired, and electronically stores the user information inquiry request data file. When the data is transmitted to the bond recording institution system, the electronic bond recording institution system creates a user information inquiry result data file including user information to be inquired from the record original book and transmits it to the bank system.

  Although an occurrence record request for an electronic record receivable is made through the banking system, the occurrence record request data file is finally transmitted to the electronic claim record institution system, and the electronic claim record institution data system includes the occurrence record request data file. Since the generation record result data file is created based on this, the generation record request mechanism depends on the specifications of the electronic bond recording institution system.

  As described above, it is possible to confirm the name of the other party's user by using the user information inquiry function when executing the occurrence record request. However, when executing the occurrence record request, the user is requested in advance. Executing the information inquiry function is a huge burden on the user. In addition, when the user information inquiry function is executed, a user information inquiry request data file is created and transmitted, and a user information inquiry result data file is created and transmitted accordingly. Frequent execution of such processing during daytime hours when the system is executed can have a significant impact on the banking system, the electronic bond recording institution system, and the traffic between the two systems.

  In order to solve the above-described problem, there is a method of holding user information including the user name in the bank system at the time when an occurrence record request for an electronic record bond is executed. This method will be described with reference to FIG. In the example of FIG. 1, 1) User B requests account registration of User B through financial institution B. 2) When the request is made, user B's account registration (user registration) is made in the record book on the electronic bond recording institution, and 3) in the user database B of the bank system B provided by the financial institution B. User information including the user name of user B is registered. 4) In the above-described situation, the user A, through the financial institution A, uses the user A as the debtor and the user B (the account held by the financial institution B is designated as the creditor settlement account of the user B). Request the record of occurrence of electronically recorded receivables designated as creditors (other users) (obligor claim method). In this state, user A requests that the occurrence record request be made after confirming the name of user B who is the creditor (the other party's user) when executing the occurrence record request for the electronic record receivable. However, 5) Even when the user B's inquiry is made to the user database A of the bank system A provided by the financial institution A when the occurrence record request is executed, the user information of the user B is still present. It is not registered and cannot be confirmed as described above. This means that only the user number of the other party's user is specified in the data record request data file that is exchanged with the electronic bond record organization when the record request for electronic record claims is executed. This is because the specification does not specify the name of the other party's user. That is, since user B has registered his / her account through financial institution B, financial institution A cannot use the user information of user B, and when user A requests an occurrence record. Therefore, the name of the user B (other user) cannot be confirmed.

  In Patent Document 1, based on the distribution information and commercial flow information held by a company, which is the basis for the generation of accounts receivables, an application for electronic records of generated accounts receivables to an electronic claims recording institution, An electronic record receivable application system is disclosed that performs management associated with distribution information and commercial flow information on electronically recorded electronic receivables. However, in the invention described in Patent Document 1, the name of the other party user cannot be confirmed in advance when the occurrence record request is executed.

  The present invention has been made in view of such a problem, and it is possible to confirm the name of a counterpart user when executing an occurrence record request based on the specifications of the system of an existing electronic bond recording organization. It is an object of the present invention to provide an electronic record creditor counterparty user name display system and an electronic record creditor counterparty user name display method.

  In order to solve the above-mentioned problem, the electronic record receivable counterparty user name display system according to the present invention is an electronic receivable recording organization for displaying the name of the counterpart user when executing a request for record of occurrence of an electronic record receivable. A computer system connected to the system and a client computer, a user data storage unit storing user data about the other user of the electronic record receivable, and an occurrence record request or transfer from the client computer to the electronic record receivable A request receiving unit that receives a request for recording request, and a user information inquiry request data creating unit that creates user information inquiry request data based on the received request when a predetermined time has elapsed; User information for transmitting the created user information inquiry request data to the electronic bond recording institution system. An inquiry request data transmitting unit, a user information inquiry result data receiving unit for receiving user information inquiry result data from the electronic bond recording institution system, and the user data based on the received user information inquiry data A user data record is added to the storage unit, or a user data management unit that updates the user data record of the user data storage unit, and the user data storage unit uses the received request based on the received request A user data acquisition unit for acquiring a user data record; and a user data transmission unit for transmitting the acquired user data record to the client computer.

  According to the electronic record receivable counterparty user name display system according to the present invention, it is possible to confirm the name of the counterpart user when executing the request for recording the occurrence of the electronic record receivable. In addition, the latest partner user name can be confirmed without affecting the banking system, the electronic bond recording institution system in the daytime, and the traffic between the two systems.

It is a figure which shows the outline | summary of the process which a bank system and an electronic bond recording organization perform at the time of performing the present generation | occurrence | production record request. It is a figure which shows the outline | summary of the process which the electronic record loan other party user name display system which concerns on one Embodiment of this invention performs. It is a block diagram which shows the example of a structure of the whole electronic recording loan other party user name display system which concerns on one Embodiment of this invention. It is a flowchart which shows the process which the electronic recording credit other party user name display system which concerns on one Embodiment of this invention performs. It is a figure which shows the example of the screen of the input interface screen 500 which concerns on one Embodiment of this invention. It is a figure which shows the example of the user data storage part 141 which concerns on one Embodiment of this invention. It is a figure which shows another example of the user data storage part 141 which concerns on one Embodiment of this invention. It is a figure which shows the example of the input interface screen 800 changed from the input interface screen 500 shown in FIG. It is a figure which shows the outline | summary of the process which the electronic record loan other party user name display system which concerns on another embodiment of this invention performs. It is a flowchart which shows the process which the electronic recording credit other party user name display system which concerns on another embodiment of this invention performs.

  Hereinafter, with reference to the accompanying drawings, a detailed description will be given of a name display system for the other party of electronic record credit according to an embodiment of the present invention. FIG. 2 is a diagram showing an outline of processing executed by the electronically recorded loan partner user name display system according to the present invention.

  In the example of FIG. 2, 1) User B requests account registration for User B through financial institution B. 2) When the request is made, user B's account registration (user registration) is made in the record book on the electronic bond recording institution, and 3) in the user database B of the bank system B provided by the financial institution B. User information including the user name of user B is registered. 4) In the above-described situation, the user A, through the financial institution A, uses the user A as the debtor and the user B (the account held by the financial institution B is designated as the creditor settlement account of the user B). Request the record of occurrence of electronically recorded receivables designated as creditors (other users) (obligor claim method). 5) When the request is made, the banking system A provided by the financial institution A sends the user number and / or the other party user (user B) designated in the request for the record of occurrence to the electronic bond recording institution. A user information inquiry request is made based on the settlement account information. 6) When the user information inquiry request is made, a user information inquiry result data file is transmitted from the electronic bond recording institution to the bank system A. Therefore, the bank system A sends the database A to the database A based on the data file. User information of user B is registered. 7) In such a situation, the bank system A refers to the user database A and obtains the user information for the user B when making the above-described request for recording the occurrence of the electronic record receivable. The name of the person B (the other party user) can be confirmed. The processes 5) and 6) are performed in a predetermined time zone (for example, at night) after the end of the service time zone (hereinafter referred to as “service time zone”). .

  Next, with reference to FIG. 3, an example of the configuration of the entire electronic record receivable party user name display system according to the present invention will be described. In FIG. 3, the electronic record receivable counterparty user name display device 101 is connected to the electronic receivable recording organization system 103 via a network 102 such as a dedicated line. Further, the electronic record creditor counterparty user name display device 101 is connected to a client computer 105 via a network 104 such as the Internet.

  The electronic record receivable party user name display device 101 is a main computing device that provides a service of the electronic record receivable party user name display system according to the present invention. When the electronic record receivable counterparty user name display apparatus 101 requests the occurrence record request of the electronic record receivable from the user, it creates an occurrence record request data file having a format common to all financial institutions, and the occurrence record request Processing such as transmitting the data file to the electronic bond recording institution system 103 is performed. It should be noted that the electronic record receivable counterparty user name display device 101 may be implemented alone, or may be implemented by a bank system server or host that provides bank accounting services that exist in the past.

  The electronic record creditor counterparty user name display device 101 includes a network I / F 110, a control unit 120, a main storage unit 130, and an auxiliary storage unit 140, and these elements are connected via a system bus.

  The network I / F 110 transmits and receives data to and from the electronic bond recording institution system 103 and the client computer 105 connected via the networks 102 and 104, respectively.

  The control unit 120, also called a central processing unit (CPU), controls the above-described components and performs data calculations, and reads various programs stored in the auxiliary storage unit 140 to the main storage unit 130 and executes them. To do. The main storage unit 130 is also referred to as a main memory, and stores input data received by the electronic record creditor counterparty user name display device 101, computer-executable instructions, data after arithmetic processing by the instructions, and the like.

  The auxiliary storage unit 140 is a storage device represented by a hard disk (HDD) and stores a database table such as a user data storage unit 141. The auxiliary storage unit 140 also stores a program (not shown) for causing the control unit 120 to execute various processes according to the present invention.

  The electronic bond recording institution system 103 is a system for recording generation, transfer, etc. of electronic record receivables provided by an electronic receivable recording institution established by the National Bank Association, and stores a record book for each electronic record receivable An electronic record bond database 150 is provided. When the electronic bond receivable organization system 103 receives the generated record request data file from the electronic record receivable counterparty user name display device 101, the electronic receivable record institution system 103 executes processing such as adding a corresponding record master record to the electronic record receivable database 150.

  The client computer 105 is a computer terminal for inputting a request for a service provided by the electronic record credit partner user name display system according to the present invention. The user inputs information necessary for making an electronic record receivable occurrence record request from the input interface displayed on the client computer 105. The input information is transmitted to the electronic record credit partner user name display device 101, and processing such as occurrence recording is performed.

  The above-mentioned electronic record creditor counterparty user name display device 101 may be configured by one or a plurality of computing devices. The client computer 105 described above may be an information terminal device such as a personal computer, a workstation, or a PDA having a communication function. A computing device and an information terminal device are computing devices including a central processing unit (CPU), a memory, a storage device, and the like, and are centralized by a CPU processing a computer program stored in the memory or the storage device. It is controlled, and the processing according to the present invention can be executed and its function can be realized. Note that the above-described system configuration is for illustration, and does not limit the system configuration capable of executing the present invention.

  Next, with reference to FIG. 4, processing executed by the electronic record creditor user name display system according to the present invention will be described. In the present embodiment, the following matters are assumed. 1) It is assumed that a request for a record of occurrence of an electronic record receivable in which user 1 is designated as a debtor and user 2 is designated as a creditor is received from user 1 through a service providing financial institution (obligor claim method) ). 2) User 1 has already registered an account (user) in the electronic bond recording institution system 103 through the service providing financial institution. 3) User 2 has already registered an account (user) in the electronic bond recording institution system 103 through a financial institution other than the service providing financial institution. 4) User 2 shall have no record of using electronically recorded receivables by either creditors or debtors through service-providing financial institutions.

<Request reception>
The user 1 inputs the user number of the user 1 from the input interface displayed on the client computer 105. The entered user number is transmitted from the client computer 105 to the electronically recorded credit partner user name display device 101 (S401).

  The network I / F 110 of the electronic record receivable counterparty user name display device 101 receives the user number transmitted in S401, and the control unit 120 uses it from the user data storage unit 141 based on the user number. A person data record is acquired (S402).

  Next, the network I / F 110 of the electronic record receivable counterparty user name display device 101 transmits the user data acquired in S402 to the client computer 105 (S403). When the client computer 105 receives the user data, the client computer 105 displays the user data in the biller information display box 501 of the input interface screen 500. The input interface screen 500 will be described with reference to FIG.

  The input interface screen 500 is an interface screen for inputting information necessary for executing the occurrence record request. In order to execute an accrual record request, biller information (including debtor information in case of debtor billing method, user number and settlement account information), counterparty user information (creditor information in case of debtor billing method) , Including user number and settlement account information), and receivable information (including the amount of receivables, payment date, electronic record date, and whether there are restrictions on transfer). Information is entered.

  When the user 1 inputs the information shown in FIG. 5 from the input interface screen 500 and presses the confirmation button 502, the generated record request data including the input information is transmitted to the electronic record credit partner user name display device 101. (S404).

  When the network I / F 110 of the electronic record receivable counterparty user name display device 101 receives the generated record request data transmitted in S404, the control unit 120 causes the counterpart user number and / or included in the generated record request data to be received. The other party user settlement account information and data including the time stamp are added to the temporary storage data storage unit 142 (not shown) (S405). The temporary storage data storage unit 142 is a database table that stores a user number necessary for executing a user information inquiry to the electronic bond recording institution system 103, which will be described later. In the present embodiment, the temporary storage data storage unit 142 is implemented in the form of a database table, but is not limited to such a format, and a queue is implemented in the main storage unit 130 or the auxiliary storage unit 140, It may be implemented in a form that is added to the queue.

  The processes of S401 to S405 described above are executed in the service time zone. It is assumed that the processing of S406 to S410 described below is executed in a predetermined time zone (for example, night time zone) after the service time zone has elapsed. Accordingly, in S404, since the user 1 can refer to the confirmation result after the next day, an indication to that effect may be displayed on the input interface screen 500.

<Addition / update of user data storage unit>
The process from S406 is started when a predetermined time comes after the service time period ends, for example, when a batch file is activated by time activation. The control unit 120 of the electronically recorded bond other party user name display device 101 acquires all records from the temporarily stored data storage unit 142 in the order of time stamps (S406). The temporary storage data storage unit 142 stores the counterpart user number and time stamp as described above, and executes the following processing based on all the acquired records.

  Next, the control unit 120 reads the acquired records (hereinafter referred to as temporary storage records) one by one, and based on the other party user number and / or the other party user settlement account information included in the temporary storage record. An information inquiry request data file is created, and the user information inquiry request data file is transmitted to the electronic bond recording institution system 103 (S407). The user information inquiry request data file is a data file for inquiring user information to the electronic bond recording institution system 103 as described above, and has a format common to all financial institutions. The electronic bond recording institution system 103 acquires the corresponding user data from the electronic record bond database 150 based on the received user information inquiry request data file, creates a user information inquiry result data file, It transmits to the recorded credit other party user name display device 101 (S408). In this way, it is possible to acquire the name of the other party user who is the latest when the user information inquiry is performed. Note that the user information inquiry process executed in S407 and S408 is the same as the current process, and thus detailed description thereof will be omitted.

  Next, the network I / F 110 of the electronic record receivable counterparty user name display device 101 receives the user information inquiry result data file transmitted in S408, and the control unit 120 stores the user information inquiry result data file in the user information inquiry result data file. A user data record is added to the user data storage unit 141 on the basis of the included user information (if a user data record having the same user number already exists, the user data record is updated. (S409). Here, the user data storage unit 141 will be described with reference to FIG.

  The user data storage unit 141 is a database table that stores information about users registered in the electronic bond recording organization. The user data storage unit 141 includes items “user number”, “user name”, and “user name (kana)”. No. of FIG. 1 record corresponds to the user data record of user 1, 2 corresponds to the user data record of user 2, and in S409, No. 2 record is obtained. 2 records are added (updated).

  Further, as shown in FIG. 7, the user data storage unit 141 may store information by associating the user 1 with the user 2 who is the counterpart user. In this case, in the acquisition of the user data record from the user data storage unit 141 in S411 described later, the record is acquired based on the user number (creditor user number) included in the generated record request data. .

  The processes of S407 to S409 are executed one by one for all the temporarily saved data records acquired in S406, and when the process for the last record is completed, all the records in the temporarily saved data storage unit 142 are deleted (S410). In this way, the user number and / or the settlement account information (temporary storage data record) designated as the other party user is stored in the temporary storage data storage unit 142 in the processing such as the occurrence record request processed in the service time zone. Then, the user information inquiry is executed based on the stored temporary storage data record, and the record in the user data storage unit 141 is added / updated. Each time it is executed, the record in the user data storage unit 141 can be updated to the latest. In the present embodiment, the configuration is such that all the records are acquired from the temporarily stored data storage unit 142 at the same time. However, the present invention is not limited to such a format, and the temporarily stored data records are stored one by one from the temporarily stored data storage unit 142. S911 to S914 may be repeated until acquisition and processing for all records are completed. Further, the temporary storage data record in the temporary storage data storage unit 142 may be deleted one by one.

  As described above, when an occurrence record request is made by a user, a user information inquiry request is made after the service time period ends based on the request, and the user data is obtained based on the user information inquiry result data. Since the storage unit 141 is updated, it is possible to confirm the latest name of the other-party user when requesting the occurrence record of the electronic record receivable described later.

<Execution request for electronic record receivables>
Next, the process of S410 is performed, and it becomes the service time zone of the next day, and the subsequent process is started when the user 1 logs in again to the input interface screen 500 described above. The network I / F 110 of the electronic record receivable counterparty user name display device 101 receives the generated record request data transmitted in S404, and the control unit 120 is based on the other party user number included in the generated record request data. The user data record is acquired from the user data storage unit 141 (S411).

  Next, the control unit 120 supplements the generated record request data transmitted in S404 with the name of the counterpart user included in the user data record acquired in S411, and transmits the generated record request data to the client computer 105. (S412).

  Upon receiving the generated record request data, the client computer 105 displays the generated record request data on the input interface screen 800 transitioned from the input interface screen 500 (see FIG. 8). As described above, since the user data of the user 2 is held in the user data storage unit 141, the user name of the user 2 is displayed in the partner information display box 801 of the input interface screen 800, and is generated. When executing the recording request, it becomes possible to confirm the name of the other party user.

  In such a state, when the user 1 presses the execute button 802, an occurrence record request execution indication is transmitted from the client computer 105 to the electronic record creditor counterparty user name display device 101 (S413). The network I / F 110 of the electronic record receivable party user name display device 101 receives the generated record request execution indication transmitted in S413, and the control unit 120 generates based on the generated record request data transmitted in S404. A record request data file is created, and the generated record request data file is transmitted to the electronic bond recording institution system 103 (S414). In response to this, the electronic bond recording institution system 103 executes occurrence recording (S415). The generation record request data file has a format defined common to all financial institutions, and the generation record request to the electronic bond recording institution system 103 is the same process as that for executing the current generation record request. Therefore, detailed description in this specification is omitted.

  As described above, when a request for an occurrence record request from a user is received, the request is saved, and the user data storage unit 141 is updated by executing a user information inquiry in a time zone such as nighttime. Therefore, even if the other party user (user 2 in this embodiment) has never used the electronic record receivable through the service providing financial institution, the user 1 uses The person's name can be confirmed. In the present embodiment, an example of executing an electronic record receivable record request (obligor claim method) in which the user 1 is designated as a debtor and the user 2 is designated as a creditor has been described. It is not limited to the example. Request for record of occurrence of electronically recorded receivables specified by user 1 as creditor and user 2 as debtor (creditor claim method), or user 1 as debtor and use Any record request for the electronic record receivable designated by the user 2 as the other user of the user 1, such as a transfer record request for the electronic record receivable 1 with the creditor 2 as the creditor, may be used.

  Next, with reference to FIG. 9, an outline of processing executed by the electronic record receivable party user name display system according to another embodiment of the present invention will be described.

  In the example of FIG. 9, 1) User B designates user B as a debtor and user A (account held by financial institution A as the creditor settlement account of user A) through financial institution B. ) Is designated as a creditor (the other party's user) and an occurrence record request is made for the electronically recorded receivable 1. 2) When the request is made, the electronic record receivable 1 is recorded in the record book on the electronic receivable recording institution, and 3) the user B is also used in the user database B of the bank system B provided by the financial institution B. The person's name is registered. 4) When the occurrence record is executed at the electronic bond recording institution, the occurrence record result data file of the electronic record bond 1 is transmitted to the bank system A provided by the financial institution A. Occurrence record result data file is a data file that contains records recorded in the record book and is recorded at the electronic bond recording institution, and is a bank of a financial institution having a settlement account designated by the creditor and debtor (In this embodiment, the creditor of the electronically recorded receivable 1 is the user A, and the account held by the financial institution A is designated as the user A's settlement account. The data file is sent to bank system A). 5) The bank system A stores a user data record for the user B in the user database A of the bank system A based on the debtor information (user B information) included in the received occurrence record result data file. to add. 6) After the above occurrence record request, User A is designated through Financial Institution A as User A as Debtor and User B (User B's creditor settlement account is the account held by Financial Institution B) Request the occurrence record of the electronically recorded receivable 2 designated as creditor (the other party user). 7) When the request is made, the bank system A refers to the user database A and acquires user information for the user B. In this way, when the occurrence record request is executed through the bank system B, the bank system A uses the occurrence record result data file transmitted from the electronic bond recording institution to the user database A for use by the user B. Since the creditor information is registered, when executing the request for recording the occurrence of the electronically recorded receivable 2, the creditor (the other party) User's name can be confirmed.

  Next, processing executed by the electronic record creditor counterparty user name display system according to another embodiment of the present invention will be described with reference to FIG. In the present embodiment, the following matters are assumed. 1) It is assumed that a request for an occurrence record request of electronic record receivable 1 in which user 2 is designated as a debtor and user 1 is designated as a creditor is received from user 2 through a financial institution other than the service providing financial institution. (Debtor request method). 2) After the occurrence record of the electronic record receivable 1 is recorded, the request for the record of occurrence of the electronic record receivable 2 that designates the user 1 as the debtor and the user 2 as the creditor is made through the service providing financial institution. Suppose that it was from user 1 (obligor claim method). 3) User 1 has already registered an account (user) in the electronic bond recording institution system 103 through the service providing financial institution. 4) The user 2 has already registered an account (user) in the electronic bond recording institution system 103 through a financial institution other than the service providing financial institution. 5) User 2 shall have no record of using electronically recorded receivables in either creditors or debtors through service-providing financial institutions.

<Addition / update of user data storage unit>
When the occurrence record for the electronic record receivable 1 is recorded, the electronic receivable record institution system 103 is a participating financial institution that manages the debtor settlement account of the electronic record receivable 1, that is, the electronic record receivable counterparty user possessed by the service providing financial institution The generated record result data file is transmitted to the name display device 101 (S1001). The occurrence record result data file includes at least creditor information (user information including the user number and name of the user 2) of the electronic record loan 1. The generation record result data file has a format common to all financial institutions and is already known, and therefore detailed description thereof will be omitted. It is also known that when the occurrence record is executed in the electronic bond recording institution system 103, the occurrence record result data file is transmitted to the bank system of the financial institution having the settlement account designated by the counterparty user. Description is omitted.

  Next, the network I / F 110 of the electronic record receivable counterparty user name display device 101 receives the generated record result data file transmitted in S1001, and the control unit 120 displays the creditor included in the generated record result data file. Based on the information (user information of user 2), a user data record is added to the user data storage unit 141 (if a user data record having the same user number already exists, the user data record is used) The user data record is updated) (S1002).

  The above-described update / addition processing of the user data storage unit 141 in S1001 and S1002 may be executed in a predetermined time zone (for example, nighttime zone) after the service time zone ends or is used. It may be executed in a time zone for processing a request from a person. In this way, when processing such as an occurrence record request is executed through a financial institution other than the service providing financial institution, the result data file of the record request is received from the electronic bond recording institution system 103, and the user data storage unit Since the record addition / update 141 is executed, the user data storage unit 141 can be updated in response to the request for recording.

<Execution request for electronic record receivables>
In such a situation, the user 1 makes an occurrence record request using the input interface displayed on the client computer 105 (S1003 to S1011) (S1003 to S1006 are the same as S401 to S404 in the example of FIG. 4). Correspondingly, S1007 to S1011 correspond to S411 to S415 in the example of FIG. In the generation record request, since the user data storage unit 141 holds the latest user information, the user information of the user 2 can be acquired in S1007, and the user 1 requests the generation record. At this time, the name of the other party user can be confirmed.

As described above, when the user 2 requests the occurrence record request through the financial institution other than the service providing financial institution, the occurrence record result data file transmitted from the electronic bond recording institution system 103 in response to the request is stored in the occurrence record result data file. Based on the above, a user data record is added to the user data storage unit 141. Therefore, an occurrence record request for an electronic record receivable in which the user 1 is designated as a debtor and the user 2 is designated as a creditor (counter user) is requested. When doing so, the name of the other user can be confirmed. In the present embodiment, an example of executing an electronic record receivable record request (obligor claim method) in which the user 1 is designated as a debtor and the user 2 is designated as a creditor has been described. It is not limited to the example. Request for record of occurrence of electronically recorded receivables specified by user 1 as creditor and user 2 as debtor (creditor claim method), or user 1 as debtor and use Any record request for the electronic record receivable designated by the user 2 as the other user of the user 1, such as a transfer record request for the electronic record receivable 1 with the creditor 2 as the creditor, may be used.

  As described above, the description of the electronic record receivable party user name display system according to the present invention has been described in detail, but specific examples such as the user data storage unit 141 and the temporary storage data storage unit 142 described in the embodiment are described. The data structure is merely exemplary and changes may be made without departing from the claimed subject matter.

102 network 104 network 501 claimant information display box 502 confirmation button 801 partner information display box 802 execute button

Claims (8)

A method executed by a computer connected to an electronic bond recording institution system and a client computer for displaying the name of a counterparty user when executing an electronic record bond occurrence record request, wherein the computer is a user A data storage unit,
The method
Receiving a request for an occurrence record request or a transfer record request for an electronic record claim from the client computer , wherein the request includes a counterpart user identification number of the electronic record claim ;
Creating user information inquiry request data based on the counterpart user identification number ;
Transmitting the created user information inquiry request data to the electronic bond recording institution system;
Receiving user information inquiry result data from the electronic bond recording institution system;
Based on the received user information inquiry data, a step of adding a user data record to the user data storage unit or updating a user data record of the user data storage unit , the usage The other party user data corresponding to the person information inquiry result data is not stored in the user data storage unit or is different from the user data record stored in the user data storage unit ,
In response to the received request,
Obtaining a user data record from the user data storage unit based on the counterparty user identification number;
Transmitting the acquired user data record to the client computer;
Creating an occurrence record request data file or a transfer record request data file and sending it to the electronic bond recording agency system . Depending on when a given time has passed,
Creating the user information inquiry request data;
Transmitting the created user information inquiry request data;
Receiving the user information query result data;
The method according to claim 1, further comprising: adding a user data record to the user data storage unit or updating the user data record of the user data storage unit. A method executed by a computer connected to an electronic bond recording institution system and a client computer for displaying the name of a counterparty user when executing an electronic record bond occurrence record request, wherein the computer is a user A data storage unit,
The method
In response to the request for occurrence record or transfer record request for the first electronic record claim, the occurrence record result data or transfer record result data for the first electronic record claim is received from the electronic claim record institution system. The generation record result data and the transfer record result data include counterpart user data of the first electronic record bond ,
Based on the received generation record result data or the received transfer record result data, a user data record is added to the user data storage unit, or a user data record in the user data storage unit is updated. a step, the counterpart user data is different from the user data has not been stored in the storage unit, or the stored user data storage section the user data records, the steps,
Receiving a request for occurrence record request data or transfer record request data for a second electronic record claim from the client computer, wherein the request includes a counterpart user identification number of the electronic record claim; and ,
In response to the received request,
Obtaining a user data record from the user data storage unit based on the counterparty user identification number;
Transmitting the acquired user data record to the client computer;
Creating an occurrence record request data file or a transfer record request data file for the second electronic record claim and sending the file to the electronic claim record organization system . A computer system connected to an electronic bond recording institution system and a client computer for displaying the name of a counterparty user when executing an occurrence record request for an electronic record bond,
A user data storage unit;
A request receiving unit that receives a request for an occurrence record request or a transfer record request for an electronic record claim from the client computer , wherein the request includes a counterpart user identification number of the electronic record claim ,
Depending on when a given time has passed,
Based on the counterparty user identification number , a user information inquiry request data creating unit for creating user information inquiry request data;
The user information inquiry request data transmission unit that transmits the created user information inquiry request data to the electronic bond recording institution system;
A user information inquiry result data receiving unit for receiving user information inquiry result data from the electronic bond recording institution system;
Based on the user information query the received data, add the user data record to the user data storage unit, or, met the user data management section updates the user data records of the user data storage unit The other party user data corresponding to the user information inquiry result data is not stored in the user data storage unit or is different from the user data record stored in the user data storage unit. Person data management department ,
In response to the received request,
A user data acquisition unit that acquires a user data record from the user data storage unit based on the counterpart user identification number ;
A user data transmission unit for transmitting the acquired user data record to the client computer;
A computer system comprising: an occurrence record request data file or an assignment record request data file, and an occurrence record / assignment record request processing unit that transmits the file to the electronic bond recording institution system. A computer system connected to an electronic bond recording institution system and a client computer for displaying the name of a counterparty user when executing an occurrence record request for an electronic record bond,
A user data storage unit;
In response to the request for occurrence record or transfer record request for the first electronic record claim, the occurrence record result data or transfer record result data for the first electronic record claim is received from the electronic claim record institution system. A first receiving unit , wherein the generation record result data and the transfer record result data include counterpart user data of the first electronic record bond ,
Based on the received generation record result data or the received transfer record result data, a user data record is added to the user data storage unit, or a user data record in the user data storage unit is updated. User data management unit , wherein the other party user data is not stored in the user data storage unit or is different from the user data record stored in the user data storage unit The management department ,
A second receiving unit for receiving a request for occurrence record request data or transfer record request data for a second electronic record claim from the client computer , wherein the request includes a counterpart user identification number of the electronic record claim; A second receiver including :
In response to the received request,
A user data acquisition unit that acquires a user data record from the user data storage unit based on the counterpart user identification number ;
A transmission unit for transmitting the acquired user data record to the client computer;
A computer comprising: a generation record / transfer record request processing unit that creates an occurrence record request data file or transfer record request data file for the second electronic record bond and transmits the file to the electronic bond recording institution system system. The program for making a computer perform the method as described in any one of Claims 1 thru | or 3 . A computer-readable storage medium storing the program according to claim 6 . A computer comprising a processor and a memory, wherein the memory stores a program for causing the processor to execute the method according to any one of claims 1 to 3 .

Images