JP6670780B2 - Supplier name confirmation device, supplier name confirmation method and program - Google Patents

Description

  The present invention relates to a supplier name confirmation device, a supplier name confirmation method, and a program for confirming a supplier name in a record request of an electronically recorded credit institution.

  In recent years, in order to avoid risks such as loss and theft, financial institutions have replaced electronic bonds with electronically-recorded receivables that have been approved by the government in place of bonds with the contents of the claims on conventional paper. Used. When electronically recorded receivables are used, the processing of the generation, transfer, and division of the receivables becomes effective when the receivables are electronically recorded (registered) in a record ledger in the computer system of the electronically recorded receivables agency. In this computer system, a record number, a user number, account information, names of creditors and debtors (user names to be described later), payment amounts, payment dates, and the like are managed for electronically recorded receivables. Then, as in the case of the conventional paper bond, the transfer of the bond and the processing of the cash are performed. There are two types of record requests, which are requests to make electronic records in the electronic ledger's record ledger: an occurrence record request, a transfer record request, and a division record request.

  In addition, as electronically recorded receivables institutions, there are two types of institutions that have been independently established and approved by banks, and those that have been established and approved by multiple national banking and banking associations (Densai Net (registered trademark)). There are two types. Inquiries about records to confirm the status of the generation, transfer and division of electronically recorded receivables are available only through the window (terminal) of the financial institution participating in the electronically recorded receivables institution. It has a configuration.

There are two types of recording requests: a creditor's request method, in which the creditor makes a request to record an electronically recorded claim (recording request in which the creditor designates a debtor that is a business partner), and a creditor's request for an electronically recorded claim. There are two types: a debtor claim method for making a record request (record request in which the debtor designates a creditor who is a business partner).
In either of the creditor request method and the debtor request method, the user making the recording request requires an electronically recorded credit institution to determine whether the recording request corresponds to the correct business partner user. When making a record request against the customer, the user name of the user of the customer for whom the record request is made (the name of the debtor in the case of the creditor claim method, It is necessary to confirm the creditor's user name).

  In the case of an electronically recorded receivables agency, user information including the name of the customer (customer name) is queried using the user identification information consisting of either or both of the user number and account information of the user (electronic name). By referring to the electronically recorded receivables user information registered with the recording receivables agency, the supplier name of the user of this supplier can be obtained and the supplier name can be confirmed. However, when requesting the recording of electronically recorded receivables, it is necessary for the user to refer to the supplier name of the user of the supplier in order to confirm the supplier of the electronically recorded receivable making the request. Inquiry of user information and acquisition of supplier name are required, which is a burden on system operation.

  Also, when a user accesses an electronically-recorded credit institution via a financial institution, if the financial institution uses a relay service provider or its own relay device, the relay device makes sure that the business partner in the requested record request is correct. A confirmation screen is displayed on the user's terminal in order to make the user determine whether or not this is the case. Here, in the specifications of the computer system of the electronically recorded receivables institution, since the supplier name of the supplier user is not an item necessary for the recording request, only the user identification information is displayed. For this reason, the user checks whether or not the supplier is the requested supplier using only the user identification information, and does not visually recognize the supplier name on the screen based on the user number and the account information. Must be determined.

  In order to solve the above-mentioned problem, by accessing the system of the electronically recorded receivables agency based on the user information included in the record request supplied by the user and inquiring the user information, Obtain the latest user information from the system, display the user identification information and the supplier name on the display screen for confirmation, and confirm whether or not the user of the partner requesting the record is correct. There is a system that allows the user to confirm (for example, see Patent Document 1).

Japanese Patent No. 5864636

In the above-mentioned Patent Document 1, when a request for recording is made, if the user name of a business partner is changed after confirmation of the user on the requesting side at the time of the above-mentioned recording request, registration of the electronically recorded receivables in the record ledger In the notification of the recording result, the supplier name is different from that at the time of recording request.
For this reason, the user on the billing side returns a recording result notification in which a user name different from the supplier name confirmed when making the recording request is described. For this reason, there is no means for the user to confirm whether he or she has made a mistake in confirming the supplier name or whether there is a problem in the system of the electronically recorded credit institution. For this reason, when the recording result notification is received, it is impossible to grasp the reason why the supplier name in the received recording result notification is different from the supplier name confirmed with itself. In particular, in the case of a batch recording request, the user names of many business partners are confirmed, so if even one of the business partner user names is different, the user will be notified of the recording result of the entire batch recording request. You will have doubts.

  The present invention has been made in view of such circumstances, and even when the supplier name is changed, when the recording result notification returns, the user changes the supplier name. It is an object of the present invention to provide a supplier name confirmation device, a supplier name confirmation method, and a program, which can easily confirm that the customer name has been verified.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. A supplier name confirmation device according to the present invention includes: user identification information for identifying a user; and a user of a business partner corresponding to the user identification information. A storage unit (for example, a business partner name management database in the embodiment) in which a first business partner name, which is the name of the first business partner, is stored, and a request for recording an electronically recorded bond is sent to an electronic bond recording organization. (1) a billing unit (for example, a supplier name confirmation server in the embodiment) performed by a supplier name, and a receiving unit (for example, a recording unit that receives a recording result notification indicating a registration result of an electronically recorded receivable, which is notified by the electronic receivable recording organization) A supplier name confirmation server in the embodiment, and a comparing unit (for example, the supplier in the embodiment) that compares the first supplier name with the second supplier name indicated in the recording result notification. (A name confirmation server), a determining unit (for example, a supplier name confirmation server in the embodiment) for determining whether or not the first supplier name and the second supplier name are mismatched, and a request for recording the electronically recorded receivable. to the user who performed the suppliers name check unit for notifying the result of the determination (e.g., suppliers name verification server in the embodiment) e Bei and the suppliers name confirmation unit is determined to mismatch If the first supplier name exists, not only the user who made the recording request but also the first supplier name that is not matched among the users registered in the storage unit is referred to as the supplier. extracting the user who is from the storage unit, for each of the extracted said user, characterized that you notice the first suppliers name was not matched.

  The supplier name confirmation device according to the present invention, wherein the supplier name confirmation unit corresponds to the user identification information corresponding to the second supplier name indicated in the recording result notification determined to be inconsistent. In addition, the information is written and stored in the storage unit (for example, the supplier name difference database in the embodiment).

  In the supplier name confirmation device of the present invention, the supplier name confirmation unit changes the first supplier name determined to be mismatched in the storage unit to the second supplier name indicated in the recording result notification. The user is made to select whether or not to change, and the first supplier name selected to be changed in the storage unit is changed to the second supplier name.

  In the supplier name confirmation device of the present invention, when the supplier name confirmation unit selects the change of the first supplier name in response to the recording result notification of the batch recording request, it is determined that there is a mismatch in the storage unit. Whether to change the first business partner names individually or collectively change all the mismatched first business partner names is also selected for the user who made the recording request. It is characterized by making it.

  The supplier name confirmation device according to the present invention is arranged such that, when the supplier name confirmation unit receives a request for the history of the first supplier name changed due to mismatch, the latest second supplier name of the record result notification. The first supplier name before the change and the latest second supplier name are displayed on the terminal of the user on the billing side.

In the method for confirming a supplier name according to the present invention, the supplier name confirmation unit includes a user identification information for identifying a user and a first supplier name that is a name of a user of the supplier corresponding to the user identification information. The storage unit, and the receiving unit receives a recording result notification indicating the registration result of the electronically recorded receivable, which is notified by the electronic receivable recording institution, and the comparing unit performs the first transaction. the previous name, the recording result and the process of comparing the second partner names indicated in the notification, determine tough is, the process determines the presence or absence of mismatch between the second partner name and the first partner name And a step in which the supplier name confirmation unit notifies the user who has made the recording request of the electronically recorded claim the result of the determination, and wherein the supplier name confirmation unit determines that there is a mismatch. If the business partner name exists, the use that made the record request Not only among the users registered in the storage unit, among the users registered with the unmatched first supplier name as the business partner, is extracted from the storage unit, and the extracted user Notifying the first supplier name that has become inconsistent with each other .

The program of the present invention associates a computer with user identification information for identifying a user and a first supplier name which is a name of a supplier user corresponding to the user identification information in a storage unit. Means for storing, a means for receiving a recording result notification indicating the registration result of the electronically recorded receivable, which is notified by the electronic receivable recording institution, the first supplier name, and a second supplier name indicated in the recording result notification. Means for determining whether there is a mismatch between the first supplier name and the second supplier name, and notifying a user who has made a request for recording the electronically recorded claim of the result of the determination. In the case where the first supplier name determined to be inconsistent exists, not only the user who made the recording request but also the first registered Trade with 1 supplier name Extracting the user who is from the storage unit, for each of the extracted said user is a program for functioning as a means for notifying the first suppliers name was not matched.

  According to the present invention, since the user name of the user registered in the electronically recorded receivable has been changed, the user name (customer name) of the business partner confirmed when the user made the recording request is changed. Provide a supplier name confirmation device, a supplier name confirmation method and a program that can confirm the change of the supplier user name without confusing the user even when the recording result notification including the different supplier name returns. can do.

It is a figure showing the example of composition of the electronic record receivables system using the supplier name confirmation server by an embodiment of the present invention. FIG. 3 is a diagram showing a configuration example of a user attribute table written and stored in a user management database 13; FIG. 4 is a diagram showing a configuration example of a supplier name management table stored in a supplier name management database 112. It is a sequence diagram which shows the operation example of the electronically recorded claim system at the time of collective recording request of an electronically recorded claim. It is a figure which shows an example of the display screen which the user confirms a business partner in temporary registration and which the business partner name confirmation server 111 generated. FIG. 11 is a diagram showing an example of a display screen generated by the bond management relay server 12 in which a user checks reply information of a batch recording request from the electronically recorded bond institution server 21. It is a figure showing an example of a record result display screen which the supplier name confirmation server 111 generated. It is a figure showing an example of a record result display screen which the supplier name confirmation server 111 generated. FIG. 11 is a diagram showing another configuration example of a supplier name management table stored in a supplier name management database 112. It is a figure showing the example of composition of the electronic record receivables system using the supplier display system by a 2nd embodiment of the present invention. It is a figure showing the example of composition of the supplier name difference table written in supplier name difference database 113. It is a figure showing other examples of composition of a supplier name difference table written into supplier name difference database 113. It is a figure which shows an example of the change difference screen which changes the supplier name of the supplier name management database 112 with respect to the supplier name confirmation server 111. It is a figure showing the example of composition of the electronic record receivables system using the supplier display system by a 3rd embodiment of the present invention.

<First embodiment>
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of an electronically recorded bond system using a supplier name confirmation server (supplier name confirmation device) according to the first embodiment of the present invention. In FIG. 1, an electronically recorded loan system according to the present embodiment includes an electronically recorded bond relay system 1 provided in an electronically recorded loan correspondence service institution A and an electronically recorded bond institution B (for example, Densai Net (registered trademark) or the like). (Electronically Recorded Receivables Institution approved by the country) has an electronically recorded receivables institution system 2 and each of the user terminals 3_1 to 3_m. Hereinafter, the user terminals 3_1 to 3_m may be collectively referred to as the user terminal 3 in some cases.

  The embodiment shown in FIG. 1 shows a form in which a financial institution also has an electronically recorded receivables service institution. Each of the electronically recorded bond relay system 1, the electronically recorded bond institution system 2, and the user terminal 3 is connected by an information communication line 100 including the Internet. Further, in the following description, in the case of the debtor claim method, it is the user who becomes the debtor who executes the record request, and the user who becomes the creditor is the business partner. On the other hand, in the case of the creditor request method, it is the user who becomes the creditor who executes the recording request, and the business partner is the user who becomes the debtor. The user in the present embodiment indicates a company or an individual registered with an electronically recorded credit institution through a financial institution.

The electronically recorded receivables relay system 1 includes a supplier name confirmation system 11, a receivables management relay server 12, a supplier management database 13, and a storage unit 14.
The credit management relay server 12 accesses the electronically-recorded credit institution B of the electronically-recorded credit institution B to make a request for recording in response to a request for a record from a user who makes a request for recording. 2 is answered to the user terminal 3 of the requesting user. In addition, in response to the inquiry of the user information of the supplier name confirmation system 11, the credit management relay server 12 accesses the electronically recorded credit institution system 2 of the electronically recorded credit institution B, and based on the user identification information. Query user information registered in the record ledger.

  Here, the recording request indicates a request for recording of any of the generation, transfer, and division of the electronically recorded claim on the record ledger of the electronically recorded receivables institution B. The user identification information is information for identifying a user, and is information including one or both of a user number and account information. The user has registered the user (account) in the record ledger of the electronically recorded receivables institution B via each financial institution. The user number is a number assigned to each user by the electronically recorded credit institution system 2 of the electronically recorded credit institution B in order to identify a registered user.

  The user information is registration information registered in the electronically recorded credit institution system 2 of the electronically recorded credit institution B, and includes the user number, user name, and account information (bank name, branch name, This is attribute information of the user such as account number and account type. The record number is a number assigned to the electronically recorded receivable registered in the record ledger by the electronically recorded receivables institution system 2 to identify the electronically recorded receivable in accordance with the user information. The registration information is information on each of the electronically recorded receivables, and is information including user information, the amount of the electronically recorded receivables (receivable amount), the due date, the electronically recorded date, and the like, corresponding to the record number.

The user management database 13 stores a user attribute table relating to attribute information of users registered in the electronically recorded receivables-compliant service organization A.
FIG. 2 is a diagram illustrating a configuration example of a user attribute table written and stored in the user management database 13. The user attribute information table includes, for each record corresponding to the user number, the user number, account information including the name of the financial institution, the name of the branch, and the account number, and the name of the user as the attribute information of the user. The user name, the type of business of the user, the due date of the electronically recorded receivable, and the like are stored in association with each other.
Returning to FIG. 1, at the time of provisional registration of the recording request, the request information of the individual recording request or the collective recording request is written and stored in the storage unit 14 by the credit management relay server 12. That is, the storage unit 14 records request information (supplied from the user terminal 3), which is information relating to a recording request for requesting that the record relating to the electronically recorded receivable be recorded in the recording ledger of the electronically recorded receivables institution B. You.

The supplier name confirmation system 11 has a supplier name confirmation server 111 and each of the supplier name management databases 112_1 to 112_n. In the following description, the whole of the supplier name management database 112_1 to the supplier name management database 112_n may be referred to as the supplier name management database 112.
The supplier name confirmation server 111 reads out the supplier name, which is the user name of the supplier, from the supplier name management database 112 based on the user identification information in the charge information of the collective recording request at the time of the collective recording request. Then, a name confirmation display screen in which the supplier name is displayed together with the user identification information is generated. Then, the supplier name confirmation server 111 outputs the generated name confirmation display screen to the user terminal 3.

  In addition, the supplier name confirmation server 111 transmits the supplier name in the supplier name management database 112 at the time of the recording request (hereinafter, sometimes referred to as the supplier name at the time of request) and the recording request from the electronically recorded receivables institution B. A comparison is made with the user name included in the user information indicated in the corresponding recording result notification (hereinafter, sometimes referred to as the latest supplier name). Then, when the record result notification is supplied via the credit management relay server 12, the supplier name confirmation server 111 checks whether the supplier name at the time of billing matches the latest supplier name in the record result notification. It is determined whether or not it is. At this time, the supplier name confirmation server 111 notifies the user terminal 3 that the supplier name at the time of billing and the latest supplier name do not match (that is, do not match).

  Each of the supplier name management databases 112 (from the supplier name management database 112_1 to the supplier name management database 112_n) is provided so as to be associated with each user registered with the electronically recorded receivable correspondence service organization A. In this embodiment, the supplier name management database 112 is created in response to a request of each user registered in the electronically recorded receivables correspondence service organization A before a recording request is made in this embodiment. The creation of the supplier name management database 112 will be described later.

In addition, when the user requests registration of the above-mentioned supplier name management table in advance, the supplier name confirmation server 111 transmits the above-mentioned supplier name management database 112 when the user makes a batch recording request. May be configured to generate a supplier name management table.
Further, the supplier name confirmation server 111 may be configured to generate the supplier name management table in the supplier name management database 112 even if there is no request from the user registered in the electronically recorded receivables-compliant service organization A. good.

FIG. 3 is a diagram illustrating a configuration example of a supplier name management table stored in the supplier name management database 112.
In the supplier name management table, a user number, an account number, a supplier name, and a mismatch flag are written and stored in association with each record corresponding to the user identification information. In this embodiment, both the user information and the account information are used as the user identification information. However, if the information can identify the user, the user ID or the account information is used as the user identification information. Either one may be used. Here, the account information includes a bank name, a branch name, an account number, and the like. The mismatch flag is a flag indicating whether the determination of the supplier name at the time of billing and the latest supplier name in the supplier name confirmation server 111 match or do not match (mismatch). For example, the supplier name confirmation server 111 sets a mismatch flag as “0” when the determination results match, and as “1” when the determination results do not match.

Returning to FIG. 1, the electronically recorded credit institution system 2 of the electronically recorded credit institution B includes an electronically recorded credit institution server 21 and an electronically recorded loan original database 22.
The electronically recorded receivables institution server 21 manages an electronically recorded receivables institution B of the electronically recorded receivables. The electronically recorded receivables institution server 21 performs updating of a record original, notification of a reception result, notification of a record result, and the like in response to a user's request for recording from the user terminal 3. In addition, the electronically recorded receivables institution server 21 extracts and responds to user information in response to a user inquiry from the user terminal 3 for user information.

  The electronically recorded receivables original database 22 stores a recorded original on which each of user information and electronically recorded receivables registration information is recorded. In this record original, the recorded user information is updated in a timely manner in response to a request from a user for change and deletion via a financial institution. For example, if only the user's company name is changed and the user number and account number are not changed, a request to change only the user's company name is accepted and the company name in the user information in the record register is updated. You. Here, the electronically recorded receivables institution server 21 refers to the latest user information (including the user name) registered in the recording ledger and records the information in the output of the recording result notification which is the notification of the response to the recording request. Generate a result notification.

  Each of the user terminals 3_1 to 3_m is a computer or server owned by a company or an individual who is a user. Further, each of the user terminals 3_1 to 3_m includes a display unit 31_1,..., A display unit 31_m as a display device (for example, a liquid crystal display or a touch panel).

Next, creation of a supplier name management table in the supplier name management database 112 will be described. As described above, the supplier name management table is created in response to a registration request from a user.
The user inputs the user number and account information of the customer who wants to be registered in the customer name management table to the display unit 31 of the user terminal 3 for the electronically recorded bond relay system 1 of the electronically recorded credit correspondence service organization A. Input is made to input fields of the displayed registration screen by input means (keyboard, pointing device, touch panel) not shown.
When the request for registering the user name of the supplier to the supplier name management table is supplied from the user terminal 3, the receivable management relay server 12 sends the user name registration processing to the supplier name confirmation server 111. Command.

The supplier name confirmation server 111 refers to the user attribute table in the user management database 13 in the pre-registration of the supplier name, and checks the user number and account information corresponding to the user identification information described in the registration request. If detected, the user name stored corresponding to the user number and the account information is read out as the business partner name.
Then, the supplier name confirmation server 111 writes and stores the read supplier name in the supplier name management table associated with the user who has requested the registration in association with the user number and the account information. .

  On the other hand, the supplier name confirmation server 111 stores the user number and account information corresponding to the user identification information described in the registration request in the user attribute table in the user management database 13 in the pre-registration of the supplier name. If not detected, an inquiry is made to the electronically recorded receivable service organization B for user information using the user identification information. Then, the supplier name confirmation server 111 acquires the user name corresponding to the user identification information as a response to the inquiry from the electronically recorded receivables agency server 21 and sets the user name as the supplier name. Then, the supplier name confirmation server 111 associates the supplier name obtained as a response to the inquiry from the electronically recorded receivables institution server 21 with the user number and account information, and is associated with the user who has requested registration. Write and store in the supplier name management table.

  As described above, in the present embodiment, the supplier name confirmation server 111 of the electronically recorded receivables-compliant service institution A is used when the user registered with the electronically recorded receivables-compliant service institution A requests the registration of the supplier name. For each requesting user, a business partner name management database 112 associated with the user (for example, user number) is created. Then, the supplier name confirmation server 111 compares the supplier name of the user of the supplier requested by the user with respect to the supplier name management table of the supplier name management database 112 associated with the user. It is written and stored in association with the user information corresponding to each supplier name.

  With the above-described configuration, in the present embodiment, before the user makes a batch recording request, the supplier name management database 112 of the electronically recorded receivable corresponding service organization A is created in advance for each use requesting registration. Therefore, when making a batch recording request, the credit management relay server 12 and the electronically recorded credit are used to extract the supplier name indicated by the user identification information from the supplier name management table corresponding to the user identification information. It is easy to make the user confirm in real time without imposing a load by inquiring the institution server 21 for the user information. However, as described above, the recorded original information of the electronically recorded receivable original document database 22 is updated with the recorded user information in response to a request from a user for registration, change, or deletion via a financial institution. . Therefore, the supplier name associated with the user information stored in the supplier name management database 112 and the supplier name associated with the same user number stored in the electronically recorded receivables ledger database 22 are different. Cases occur.

  Next, a description will be given of a process in which the supplier name confirmation server 111 determines whether or not the billing-time supplier name corresponding to the user identification information and the latest transaction name, which are performed for each recording request, match. FIG. 4 is a sequence diagram showing an operation example of the electronically recorded claim system when a request for batch recording of electronically recorded claims is made. As described above, in the present embodiment, the financial institution is configured to include the electronically recorded receivable correspondence service institution A. Hereinafter, the operation of the electronically recorded bond system when the electronically recorded bond is collectively recorded will be described.

Step F1:
Since the user makes a recording request from the home page of the financial institution via the user terminal 3, the financial institution server (not shown) displays a claim on the display unit 31 of the user terminal 3 in the application for requesting recording of the home page of the financial institution. An interface screen for accessing the management relay server 12 is displayed. Then, the user performs a login process using the user ID (identification) and password registered with the financial institution on the interface screen via the user terminal 3. Then, when the login is correctly performed, the credit management relay server 12 displays, on the screen of the display unit 31 via the user terminal 3, a screen display for inputting either the individual record request or the collective record request. indicate. The user selects collective recording request as a recording request on the display unit 31, and stores a plurality of user identification information to be recorded and requested via the user terminal 3 and information of the collective recording request of electronically recorded receivables in, for example, CSV (comma). -separated values) to the electronically recorded receivables-compliant service institution A. Here, in the specifications of the computer system of the electronically recorded receivable correspondence service organization A, the supplier name of the user of the supplier is not an item necessary for the recording request. Only user identification information is included.

The credit management relay server 12 temporarily writes and stores the user identification information and the information of the request for batch recording of the electronically recorded credit in the storage unit 14 as the temporary registration (temporary registration).
Then, the credit management relay server 12 creates a display screen in which the supplier name confirmation server 111 adds the supplier name corresponding to the user identification information in the collective recording request to the input collective recording request information. Ask for.
As a result, the supplier name confirmation server 111 reads out the user identification information and the information of the batch recording request of the electronically recorded receivables from the storage unit 14 via the receivable management relay server 12.

  Then, the supplier name confirmation server 111 selects the supplier name management database 112 corresponding to the identification information of the user who made the batch recording request, and refers to the selected supplier name management database 112. The supplier name confirmation server 111 reads out the supplier name of the supplier for each record request from the supplier name management database 112 based on the user identification information for each record request in the collective record request. The supplier name confirmation server 111 creates a confirmation display screen (temporary registration confirmation screen) to be provided to the user in the temporary registration, and writes and stores the screen in the storage unit 14.

  FIG. 5 is a diagram illustrating an example of the display screen generated by the supplier name confirmation server 111 in which the user confirms the supplier in the temporary registration. In FIG. 5, an area 500 shows user information, a user number, a user name, and account information of a user (a requesting user) who has requested a batch recording request. The area 600 shows the user information of the business partner. As the user information, the user identification information, the supplier name, and the information on the recording request for each recording request are shown in units of record of the serial number. Since this collective recording request is a recording request for the occurrence of an electronically recorded receivable, the amount of the receivable and the due date are indicated as information of the recording request.

The button 701 is provided to execute the collective recording request to the electronic recording credit institution B and execute the request to the credit management relay server 12 when all the suppliers in the collective recording request are correct. A button 702 performs a process of temporarily returning the collective recording request when any of the suppliers in the collective recording request is incorrect, that is, performing a process of temporarily registering the collective recording request again to the credit management relay server 12. Provided for.
In addition, in each case of the recording request of the transfer and the division, the information of the recording request different from FIG. 5 is shown.

  The serial number column indicates the order in which the user identification information is written in the batch recording request file. The column of user number / user name indicates a combination of a user number and a user name (supplier name) corresponding to the user number. The financial institution name / branch name and account number fields contain the name of the financial institution / branch and the account number used by the user who is the business partner of the requesting user. The amount column indicates the amount of the electronically recorded receivable, and the due date column indicates the date of payment for the amount indicated by the electronically recorded receivable.

Step F2:
Next, the supplier name confirmation server 111 outputs the created temporary registration confirmation screen to the user terminal 3 via the credit management relay server 12 as temporary registration confirmation information.
The user terminal 3 displays the temporary registration screen supplied from the supplier name confirmation server 111 on the display unit 31. Then, the user refers to the temporary registration screen displayed on the display screen of the display unit 31 and determines whether or not each supplier of the recording request in the collective recording request is correct according to the user number. This is done by confirming the displayed user name (customer name).

Step F3:
The user, in the result of the determination as to whether or not each supplier of the recording request on the temporary registration screen is correct, if all the suppliers of the recording request in the collective recording request are correct, the Click the approval button. On the other hand, the user clicks the return button on the temporary registration screen of the display unit 31 when the supplier of any of the recording requests in the batch recording request is incorrect.
Here, when the approval button 701 is selected on the display screen of the display unit 31, the user terminal 3 outputs approval information indicating that the user has approved to the electronically recorded receivable service institution A. I do. On the other hand, when the return button 702 is selected on the display screen of the display unit 31, the user terminal 3 outputs return information indicating that the user has issued a return to the electronically recorded receivable service organization A. I do.

Step F4:
When the approval information is supplied from the user terminal 3, the bond management relay server 12 converts the collective recording request information stored in the storage unit 14 to the electronically recorded credit institution server 21 of the electronically recorded credit institution B. To the format to be used. Then, the bond management relay server 12 transmits the format-converted collective recording request information to the electronic recording credit institution server 21 of the electronic recording credit institution B (a request for collective recording request).
On the other hand, when the return information is supplied from the user terminal 3, the charge information of the collective recording request stored in the storage unit 14 is read, and the charge information of the collective recording request stored in the storage unit 14 is deleted.

Step F5:
When the approval information is supplied from the user terminal 3 and the collective recording request is made to the electronically recorded receivables institution server 21 of the electronically recorded receivables institution B, the receivable management relay server 12 collectively transmits the receivables to the user terminal 3. Notifies that the recording request processing has been completed.
On the other hand, when the return information is supplied from the user terminal 3 and the collective recording request information is deleted in the storage unit 14, the collective recording request information read before the deletion is transmitted to the user terminal 3. (Return).

Step F6:
The electronically recorded receivables agency server 21 receives the information on the collective recording request, and assigns a record number as an electronically recorded claim for each recording request in the collective recording request. At this point, the electronically recorded receivables institution server 21 searches the recording ledger of the electronically recorded receivables original ledger database 22 for user information corresponding to the user identification information for each recording request in the collective recording request, and It does not read the user name (customer name).
Then, the electronically recorded receivables institution server 21 notifies the receivable management relay server 12 as a notification indicating that the collective recording request has been received, including the extracted supplier name and the assigned record number, together with the information on the collective recording request. Then, a notification of the reception result of the batch recording request is transmitted (reception response).

Step F7:
The credit management relay server 12 converts the response information of the collective recording request supplied from the electronically recorded credit institution server 21 from a format corresponding to the electronically recorded credit institution server 21 to a format used by the user terminal 3. That is, the credit management relay server 12 generates an answer confirmation screen similar to the temporary registration confirmation screen shown in FIG. 5 from the answer information of the collective recording request.
Then, the credit management relay server 12 writes and stores the generated response confirmation screen in the storage unit 14, and outputs the response confirmation screen to the user terminal 3 (reception response).

  FIG. 6 is a diagram showing an example of a display screen generated by the bond management relay server 12 in which the user checks the response information of the batch recording request from the electronically recorded bond institution server 21. In FIG. 6, an area 550 shows user information, a user number, a user name, and account information of a user (a requesting user) who has requested a batch recording request, similarly to the area 500 of FIG. I have. The area 650 shows the user information of the business partner. As the user information, the user identification information, the supplier name, and the electronically recorded receivable information for each record request are shown in units of record of serial numbers.

  Here, the supplier name described in the column of user number / user name is the supplier name in the supplier name management database 112 by the supplier name confirmation server 111. As the electronically recorded receivable information, each record number and the registration status are shown together with the amount and the due date of the electronically recorded receivable for each recording request in the collective recording request. The record number is a number in the record ledger of the electronically recorded receivable assigned by the electronically recorded receivables agency server 21 for each recording request. The registration status has not been confirmed at the time of this response. Since this batch recording request is a recording request for the occurrence of an electronically recorded receivable, the amount, the due date and the registration status of the receivable are indicated in the electronically recorded receivable information.

Step F8:
The electronically recorded receivables institution server 21 transmits a response (recording result notification) regarding the establishment and failure of the registration for the collective recording request to the receivables management relay server 12. That is, the electronically recorded receivables agency server 21 adds a transaction result item in place of the registration status item in the electronically recorded receivable information of FIG. The information of the collective recording request response indicating whether the result has been established or the record has not been established is transmitted to the credit management relay server 12. At this time, the electronically recorded receivables institution server 21 searches the record ledger of the electronically recorded receivables ledger database 22 for user information corresponding to the user identification information for each record request in the collective record request, and Read the name (customer name). For this reason, the user name included in the user information included in the record result notification is not the supplier name extracted from the supplier name management database 112 by the supplier name confirmation server 111, but is electronically recorded by the electronically recorded credit institution server 21. This is the latest user name (latest business partner name) in the user information extracted from the bond original document database 22 based on the user identification information of the business partner.

Step F9:
When the supplier name confirmation server 111 is supplied with the information of the collective recording request response (recording result notification) from the electronically recorded receivables institution server 21 via the receivable management relay server 12, based on this information, the recording result is obtained. It is determined whether or not the latest supplier name in the notification matches the billing supplier name in the supplier name management table of the supplier name management database 112. At this time, the supplier name confirmation server 111 displays the comparison result between the latest supplier name and the billing supplier name in the field of the mismatch flag in the supplier name management table shown in FIG. 3 for each user identification information. Set a flag.
Then, the supplier name confirmation server 111 refers to the supplier name management table and generates a recording result display screen indicating the result of the recording result notification. The receivable management relay server 12 transmits the recording result display screen generated by the supplier name confirmation server 111 to the user terminal 3 (batch recording response).
In addition, the user terminal 3 displays the recording result display screen supplied from the supplier name confirmation server 111 on the display unit 31.

  FIG. 7 is a diagram illustrating an example of a recording result display screen generated by the supplier name confirmation server 111. In the area 800, when the supplier name at the time of billing and the latest supplier name do not match, as shown in the figure, "The user name of the supplier has been changed from the content at the time of billing. Please press the button and check the details. "Is displayed. An area 801 shows the results regarding the establishment and non-establishment of registration for a batch recording request. In this area 801, the character “OK” is displayed when all the recording requests in the collective recording request are satisfied without any problem. On the other hand, when any recording request in the collective recording request is not satisfied, Is displayed as "NG". An area 802 shows user information, a user number, a user name, and account information of a user (a requesting user) who has requested a batch recording request. The button 803 indicates “detailed billing details” and is a button for requesting billing details. When the user clicks this button, the user terminal 3 requests the supplier name confirmation server 111 for a display screen showing billing details.

Step F10:
When the user clicks a button 803 for requesting billing details shown in FIG. 7 on the recording result display screen of the display unit 31, the user terminal 3 sends the billing details to the electronically recorded receivable service institution A. Request.
The supplier name confirmation server 111 generates a claim detail display screen based on the notification of the record result and the supplier name management table in response to the request for bill detail.

  FIG. 8 is a diagram illustrating an example of a recording result display screen generated by the supplier name confirmation server 111. As in FIG. 6, an area 550 shows user information, a user number, a user name, and account information of a user (a requesting user) who has requested a batch recording request. An area 660 shows the user information of the business partner. As the user information, user identification information, supplier name, electronically recorded receivable information, and presence / absence of mismatch are shown for each record request in serial record units. Here, the supplier name described in the column of user number / user name is not the supplier name extracted from the supplier name management database 112 by the supplier name confirmation server 111, but the electronically recorded credit institution server 21. Is the latest user name (latest business partner name) in the user information extracted from the electronically recorded receivable original database 22 based on the user identification information of the business partner. The presence / absence of mismatch indicates whether the supplier name at the time of billing matches the latest supplier name. For example, if they match, nothing is described (the flag is not set), and In the case of, an asterisk is described (a flag is set).

  In addition, in the column of electronically recorded receivables information, along with the amount, payment date and record number of the electronically recorded receivable, the record of the electronically recorded receivable that made a record request as a transaction result is recorded in the transaction result item instead of the registration status item Indicates whether the record was established (registered) or the record was not established (not registered). The button 680 indicates “detailed billing details”, and is a button for requesting a difference in mismatch between the supplier name at the time of billing and the latest supplier name. When the user clicks this button 680, the user terminal 3 requests the supplier name confirmation server 111 for a display screen showing the difference between the mismatch between the billing supplier name and the latest supplier name. .

Step F11:
The supplier name confirmation server 111 outputs to the user terminal 3 a billing detail screen that is a display screen of the created billing detail.
As a result, the user terminal 3 displays the detailed billing screen supplied from the supplier name confirmation server 111 on the display unit 31.
The user refers to the detailed billing detail screen displayed on the display unit 31 of the user terminal 3 and supplied from the receivable management relay server 12, and refers to each record request in the batch recording request for the record ledger of the electronically recorded receivables institution B. Confirmation of the establishment and non-establishment of the registration. Further, the user confirms which of the business partners does not match and the business name at the time of billing has been changed to the latest business name.

  Next, when the user clicks the button 680, the user terminal 3 causes the supplier name confirmation server 111 to display a confirmation display screen indicating the difference between the mismatch between the billing supplier name and the latest supplier name. Request. In response to this, the supplier name confirmation server 111 generates a confirmation display screen in which each of the billing supplier name determined to be inconsistent and the latest supplier name are arranged, and displays the generated confirmation display screen on the user terminal. Send to 3. The user terminal 3 displays on the display unit 31 a confirmation display screen in which the supplier name at the time of billing supplied from the supplier name confirmation server 111 and the latest supplier name are arranged.

As described above, in this embodiment, the supplier changed the supplier name from the billing supplier name to the latest supplier name due to the mismatch between the supplier name at the time of billing and the supplier name in the recording result notification. FIG. 8 shows whether the supplier name at the time of all storage requests in the collective recording request matches or does not match the latest supplier name in the recording result notification at the time of the collective recording request. The billing details screen shown can be easily checked all at once. Thus, the user can be prompted to change the supplier name to the latest supplier name in the supplier name management table of the supplier name management database 112. The supplier name confirmation server 111 changes the billing-time supplier name in the supplier name management table of the supplier name management database 112 to the latest supplier name in response to a request from the user to change the supplier name. It is good also as composition.
In addition, when there is a supplier name determined to be inconsistent, not only the user who made the recording request but also the registered customer who is registered with the electronically recorded receivables-compliant service organization A, A user whose name is a business partner is extracted from the user management database 13, and the business partner name confirmation server 111 is notified so that all extracted users are notified of the business partner name that has become inconsistent. May be configured.
For this reason, according to the present embodiment, the use of a user other than the user who made the recording request is notified by notifying the user of the mismatched business partner name to all the users who have made this user a business partner. The user can confirm the user of the business partner whose business partner name has been changed at an early stage before requesting the batch recording.

  Further, in the present embodiment, when the user performs the temporary registration of the collective recording request with respect to the electronically recorded receivable correspondence service organization A, not only the user identification information but also the user identification information for each recording request in the temporarily registered collective recording request Since the supplier name corresponding to the user identification information can be read in advance from the supplier name management table in the supplier name management database 112, and the supplier name read together with the user identification information can be indicated to the user. Thus, the user can easily confirm in real time without imposing a load on each of the credit management relay server 12 and the electronically recorded credit agency server 21.

  Further, in the present embodiment, in the electronically recorded receivables-compliant service institution A, the supplier name management database 112 is provided in association with each user, so that access from other users can be prevented. Leakage of information such as business partners can be prevented, and security of user confidentiality can be improved.

  Further, the supplier name management table of the supplier name management database 112 shown in FIG. 3 in the above-described embodiment may be replaced with the configuration shown in FIG. FIG. 9 is a diagram showing another configuration example of the supplier name management table stored in the supplier name management database 112. In FIG. 9, a registered name is added in addition to the user number, account information, supplier name, and mismatch flag in the supplier name management table in FIG. The registered name is a name different from the supplier name, which is given to the user of the supplier by the user who requests the registration of the supplier name management table, and in which the supplier can be identified more clearly.

For example, if the user is a company, the user name is the company name of this company. For this reason, the business partners may be different departments in the same company. In this case, only the business partner name can be used to determine only the company, and it is difficult to determine whether the business partner in the recording request is correct.
However, as shown in FIG. 7, by registering each department of the company as a registered name, for example, the sales department, Inc., as the registered name, it is possible to correspond to the user identification information when confirming the temporary registration. By displaying the supplier name and the registered name, the supplier can be determined in detail.
In the case of this configuration, the column of the user number / user name in the area 600 in FIG. 5 becomes the column of the user number / user name / registered name.

  The supplier name confirmation server 111 responds to the request for creating a confirmation display screen (temporary registration confirmation screen) to be provided to the user in the provisional registration from the receivable management relay server 12 and responds to each recording request in the collective recording request. Based on the user identification information, each of the supplier name and registered name of the supplier for each record request is read from the supplier name management table of the supplier name management database 112. Then, the supplier name confirmation server 111 provides the user in the temporary registration by replacing the user number / user name field in the area 600 of FIG. 5 with a user number / user name / registered name field. A temporary registration confirmation screen is created and written and stored in the storage unit 14.

By using the configuration of the supplier name management table in the supplier name management database 112 shown in FIG. 7, when the user confirms the temporary registration of the batch recording request, the user identification is displayed on the temporary registration confirmation screen. Since the supplier name and the registered name are displayed according to the information, the supplier can be determined in more detail.
Further, in the supplier name management table having another configuration, the registered name is registered as the name of the product to be handled, not the name of the correct department, so that the user can intuitively determine the registered name. This makes the discrimination easier.
At this time, the user inputs the user number, account information, and registered name of the customer to be registered in the supplier name management table to the electronically recorded loan relay system 1 of the electronically recorded credit correspondence service organization A. In the input field of the registration screen displayed on the display unit 31 of FIG. 3, input is made by input means (keyboard, pointing device, touch panel) (not shown) to register in the supplier name management table.

<Second embodiment>
Hereinafter, a second embodiment of the present invention will be described with reference to the drawings. FIG. 10 is a diagram showing a configuration example of an electronically recorded bond system using a supplier display system according to the second embodiment of the present invention. 10, the same components as those in the first embodiment in FIG. 1 are given the same names. The second embodiment is different from the first embodiment in FIG. 1 in that the supplier name confirmation system 11 ′ uses the supplier name confirmation server 111 and each of the supplier name management database 112 _ 1 to the supplier name management database 112 _n. And a supplier name difference database 113. Hereinafter, differences between the second embodiment and the first embodiment will be described. In this supplier name difference database 113, a supplier name difference table of the combination of the supplier name at the time of billing and the latest supplier name, which has already been described above, is written and stored.

FIG. 11 is a diagram illustrating a configuration example of the supplier name difference table written in the supplier name difference database 113. This supplier name difference table is provided in association with each user registered in the user management database 13 of the electronically recorded receivables-compliant service organization A.
The supplier name difference table shown in FIG. 11 includes, for each table of users whose billing-time supplier name and the latest supplier name are determined to be inconsistent, the user number and account information of the user of the supplier, The supplier name at the time of billing and the latest supplier name are shown.
The supplier name confirmation server 111 compares the supplier name at the time of billing with the latest supplier name indicated in the recording result notification from the electronically recorded receivables institution B, and the supplier name at the time of billing and the latest supplier name. If they do not match, as shown in FIG. 11, they are written and stored in the supplier name difference table of the user who made the recording request in the supplier name difference database 113, as shown in FIG.

  When the user requests the difference of the supplier name (the supplier name determined to be mismatched) from the user terminal 3 to the electronically recorded receivables relay system 1 ′ of the electronically recorded receivable correspondence service organization A, the supplier The name confirmation server 111 refers to the supplier name difference database 113, reads out each of the billing-time supplier name and the latest supplier name for each user identification information from the supplier name difference table corresponding to the user, A confirmation display screen for confirming the difference, which is a display screen having the configuration shown in FIG. 11, is generated and output to the user terminal 3. Then, the user terminal 3 displays the confirmation display screen supplied from the electronically recorded bond relay system 1 'on the display unit 31.

Further, the date and time information changed to the latest transaction name may be described corresponding to each latest transaction name.
Also, if the user name has been changed many times, from the first billing supplier name to the latest supplier name, it will be arranged in chronological order in the above record, and the changed date information will be added to each record It is good also as a structure which performs.

  With the above-described configuration, according to the present embodiment, when the user requests the history of the supplier name from the user terminal 3, the supplier name confirmation server 111 transmits the supplier name at the time of billing and the latest supplier name. By referring to the supplier name difference table indicated correspondingly, the history of the change of the supplier name can be easily provided to the user, and the previous name of the current supplier name (latest transaction name) can be provided. A confirmation display screen showing the name of the customer can be easily provided to the user.

  FIG. 12 is a diagram showing another configuration example of the supplier name difference table written in the supplier name difference database 113. The supplier name difference table of the supplier name management database 112 shown in FIG. 12 includes, for each table of users whose billing-time supplier name and the latest supplier name are determined to be inconsistent, use of the supplier user. The information includes the customer number and account information, the supplier name at the time of billing, the registered name at the time of billing, the latest supplier name, and the latest registered name. Here, the registration name at the time of billing is a registration name given by the user in correspondence with the supplier name at the time of billing. The latest registered name is a registered name assigned by the user in correspondence with the latest supplier name. When the user requests the registration of the registration name from the user terminal 3 to the electronic record receivables relay system 1 'of the electronic record receivable service organization A, the registered name of the supplier name management database 112 is changed. I do.

At this time, the supplier name confirmation server 111 reflects the changed registered name in the supplier name difference database 113.
That is, when the supplier name in the supplier name management database 112 is changed to the latest transaction name, the supplier name confirmation server 111 also changes the registered name to the latest registered name in accordance with the latest supplier name. Then, in the supplier name difference database 113, the supplier name confirmation server 111 arranges the above-mentioned records in chronological order from the first supplier name at the time of billing and the registered name at the time of billing to the latest supplier name and the latest registered name, It is good also as a structure which adds the information of the changed date to each.

  With the above-described configuration, according to the present embodiment, when the user requests the history of the supplier name from the user terminal 3, the supplier name confirmation server 111 transmits the supplier name and the registered name at the time of billing. By referring to the supplier name difference table in which the latest supplier name and the latest registered name are shown correspondingly, it is possible to easily provide the user with a history of changes in the supplier name and the registered name, and It is possible to easily provide a supplier name and a registered name before the current supplier name (latest transaction name) and registered name (latest registered name).

Further, when a button 680 (a button for requesting a change difference confirmation) on the recording result display screen of FIG. 8 is clicked, a change difference screen for performing a process of changing the supplier name from the supplier name at the time of billing to the latest supplier name is displayed. May be displayed.
FIG. 13 is a diagram showing an example of a change difference screen for changing the supplier name in the supplier name management database 112 to the supplier name confirmation server 111. The supplier name confirmation server 111 generates a change difference screen with reference to the supplier name difference table of the supplier name difference database 113 shown in FIG. 11, and outputs the generated change difference screen to the user terminal 3. Then, the user terminal 3 displays the change difference screen supplied from the electronically recorded receivables relay system 1 'on the display unit 31.

  In the change difference screen of FIG. 13, in the area 900, the user number, account information, billing supplier name, latest Columns for a supplier name and a selection flag are provided. In the selection flag column, the user writes a flag on the display screen of the display unit 31 of the user terminal 3. In the present embodiment, for example, it is assumed that the flag is set when “1” is written in the selection flag column, and that the flag is not set when “0” is written.

  The button 910 indicates “batch change”, and the supplier name corresponding to the record of all users whose in-call supplier name and the latest supplier name do not match is displayed in the supplier name management. A button for requesting a process for changing to the latest supplier name in the database 112. When the user clicks on this button 910, the user terminal 3 sends a request to the supplier name confirmation server 111 in the supplier name management table of the supplier name management database 112 and the supplier name at the time of billing and the latest transaction. A request is made to collectively change all supplier names that do not agree with the supplier name to the latest supplier name. As a result, the supplier name confirmation server 111 refers to the supplier name difference table of the supplier name difference database 113, and in the supplier name management table of the supplier name management database 112, All business partner names that do not match with the business partner name are collectively changed to the latest business partner name.

  The button 920 indicates “selection change”, and in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match, the supplier name selected by the selection flag in the area 900 is displayed. Is a button for requesting a process to change only the latest supplier name in the supplier name management table of the supplier name management database 112. When the user clicks this button 920, the user terminal 3 sends a message to the supplier name confirmation server 111 in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match. A request is made to change only the supplier name selected by the selection flag in the area 900 to the latest supplier name in the supplier name management table of the supplier name management database 112. Thereby, the supplier name confirmation server 111 refers to the supplier name difference table of the supplier name difference database 113, and in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match, Only the supplier name selected by the selection flag in the area 900 is changed to the latest supplier name in the supplier name management table of the supplier name management database 112.

  Further, in the area 930, characters “individual change button” are shown. In the lower part of this area 930, each of the buttons 940 arranged at the position corresponding to the row of the record for each user is displayed in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match. This button is used to request processing for changing only the supplier name in the row corresponding to this button 940 to the latest supplier name in the supplier name management table of the supplier name management database 112. When the user clicks this button 920, the user terminal 3 sends a message to the supplier name confirmation server 111 in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match. A request is made to change only the supplier name in the row corresponding to this button 940 to the latest supplier name in the supplier name management database 112. Thereby, the supplier name confirmation server 111 replaces only the supplier name in the row corresponding to this button 940 with the supplier name in the record of the user in which the supplier name at the time of billing and the latest supplier name do not match. The name is changed to the latest supplier name in the management database 112.

  With this configuration, according to the present embodiment, due to the need to change the user's business partner name, the business partner name of the user whose billing business partner name does not match the latest business partner name is changed collectively. In addition, it is possible to provide a method of changing selection, individual change, and to improve the convenience of managing the supplier name in the supplier name management table of the supplier name management database 112 of the user.

<Third embodiment>
Next, FIG. 14 is a diagram showing a configuration example of an electronically recorded bond system using a supplier display system according to the third embodiment of the present invention.
Further, in FIG. 14, in addition to the configuration in FIG. 1, financial institutions C_1 to C_p are provided. In the following description, the entirety of the financial institution C_1 to the financial institution C_p may be referred to as the financial institution C. The other configuration in FIG. 14 is different from the configuration in FIG. 10 in the second embodiment in which the electronically recorded receivables service institution A is provided in the financial institution. It is provided as an independent institution, and serves as a relay center for transmitting and receiving data such as a recording request and a response to the recording request between the financial institution C and the electronically recorded credit institution B.

For this reason, the user accesses the financial institution server 4 of the financial institution C registered with the user from the user terminal 3 and performs a log-in process to the financial institution C of the financial institution C. Then, after successfully logging in to the financial institution server 4 of the financial institution C, the user terminal 3 sends the electronically recorded receivables service institution A of the electronically recorded receivables service institution A via the link on the financial institution C homepage. A, and is connected to the electronically-recorded bond relay system 1 ′ of A, and in the first and second embodiments, the electronically-recorded bond institution B requests the electronically-recorded bond institution system 2 to record electronically-recorded bonds (individually-recorded request, Batch recording request).
As described above, the electronically recorded receivables relay system 1 ′ of the electronically recorded receivables service institution A is configured such that each of the financial institution C_1 through the financial institution servers 4_1,... It is connected to the user terminal 3 of a user who is a customer of the institution C.

The user management database 13 may be divided into a plurality of divided databases, that is, a user management divided database. In this case, each of the user management division databases is assigned (associated) for each financial institution C. Each of the user management division databases stores a user attribute table indicating an attribute of a customer (user) of the assigned financial institution C.
In the storage unit 14, similarly to the user management database 13, the storage area is divided into a plurality of divided storage areas, and each divided storage area is assigned to each financial institution C. Then, in each of the divided storage areas, information of a collective recording request of a customer of each financial institution C is stored.

  Each of the supplier name management databases 112 is assigned to each financial institution C. For example, the supplier name management database 112_1 is assigned to the financial institution C_1, and the supplier name management database 112_n is assigned to the financial institution C_p. Each of the supplier name management databases 112 is divided into a plurality of divided databases, that is, a supplier name divided database. Each of the supplier name division databases stores a supplier name management table for each customer of the financial institution C associated with each other.

  According to the above-described configuration, the user management database 13, the storage unit 14, and the supplier name management database 112 in the electronically recorded receivables relay system 1 'in the electronically recorded receivables service institution B are associated with each financial institution C. Therefore, the security of data management of each financial institution can be ensured. Further, in the supplier name management database 112, a supplier name management table for each customer is stored in each of the supplier name division databases, so that security for each customer of the financial institution C can be maintained.

  Also, a program for realizing each function of the supplier name confirmation system 11 in the electronically recorded receivable system in FIGS. 1, 10 and 14 is recorded on a computer-readable recording medium and recorded on this recording medium. By reading the program into a computer system and executing the program, the supplier name in the supplier name management database 112 at the time of the billing request for the supplier name matches the latest supplier name in the information of the record result notification. It may be determined whether or not the process has been performed, and the determination result may be notified to the user terminal, and a process for prompting a change in the supplier name may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices.

The “computer system” also includes a homepage providing environment (or a display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" refers to a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short time. In this case, it is also assumed that a program that holds a program for a certain period of time, such as a volatile memory in a computer system serving as a server or a client in that case, is included. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system.

  The embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiments, and includes a design and the like within a range not departing from the gist of the present invention.

1, 1 '... Electronically recorded bond relay system 2: Electronically recorded bond institution system 3_1, 3_m: User terminal 4_1, 4_p: Financial institution server 11, 11': Customer confirmation system 12: Bond management relay server 13: User Management database 14 ... Storage unit 21 ... Electronically recorded receivables agency server 22 ... Electronic receivables ledger database 31_1, 31_m ... Display unit 111 ... Supplier name confirmation server 112_1, 112_n ... Supplier name management database 113 ... Supplier name difference database A ... Electronically Recorded Receivables Service Institution B: Electronically Recorded Receivables Institution C_1, C_p: Financial Institutions

Claims (7)

A storage unit in which user identification information for identifying a user and a first business partner name that is a name of a business partner user corresponding to the user identification information are stored in association with each other;
A receiving unit that receives a recording result notification indicating a registration result of the electronically recorded receivable, which is notified by the electronic receivables recording organization,
A comparing unit that compares the first supplier name with a second supplier name indicated in the recording result notification;
A determining unit that determines whether there is a mismatch between the first supplier name and the second supplier name,
The relative user who recorded claims were performed of electronic records receivables, Bei example and suppliers name check unit for notifying the result of the determination,
If the first supplier name determined to be mismatched exists by the supplier name confirmation unit, not only the user who made the recording request, but also the users registered in the storage unit, The user having the mismatched first supplier name as a business partner is extracted from the storage unit, and each of the extracted users is notified of the mismatched first business partner name.
Customer name verification device, wherein a call. The supplier name confirmation unit,
The second supplier name indicated in the recording result notification, which is determined to be inconsistent, is written and stored in the storage unit in association with the corresponding user identification information. Supplier name confirmation device described in. The supplier name confirmation unit,
The user is allowed to select whether to change the first supplier name determined to be inconsistent in the storage unit to the second supplier name indicated in the recording result notification, and change the name in the storage unit. 3. The supplier name confirmation device according to claim 1, wherein the first supplier name selected is changed to the second supplier name. 4. The supplier name confirmation unit,
When the change of the first supplier name is selected in response to the recording result notification of the collective recording request, the first supplier name determined to be inconsistent in the storage unit is individually changed or determined to be inconsistent. 4. The supplier name confirmation device according to claim 3, wherein the user who has made the recording request is also made to select whether or not to change all the first supplier names collectively. The supplier name confirmation unit,
When a request for the history of the first business partner name changed due to the mismatch is input,
The first supplier name before being changed to the latest second supplier name in the record result notification and the latest second supplier name are displayed on the terminal of the user on the billing side. The supplier name confirmation device according to any one of claims 1 to 4, wherein The supplier name confirmation unit associates the user identification information for identifying the user with the first supplier name, which is the name of the user of the supplier corresponding to the user identification information, and stores them in the storage unit. Process
The receiving unit, notified by the electronic credit recording organization, a process of receiving a recording result notification indicating the registration result of the electronically recorded loan,
A comparing unit that compares the first supplier name with a second supplier name indicated in the recording result notification;
Determine tough is a process determines the presence or absence of mismatch between the first partner name and the second partner name,
A step in which the supplier name confirmation unit notifies the user who has made the recording request of the electronically recorded claim the result of the determination ,
If the first supplier name determined to be mismatched exists by the supplier name confirmation unit, not only the user who made the recording request, but also the users registered in the storage unit, The user having the mismatched first supplier name as a business partner is extracted from the storage unit, and each of the extracted users is notified of the mismatched first business partner name. customer name confirmation method, characterized in that it comprises a process. Computer
Means for storing the user identification information for identifying the user in the storage unit in association with the first supplier name which is the name of the user of the supplier corresponding to the user identification information;
A means for receiving a recording result notification indicating the registration result of the electronically recorded receivable, which is notified by the electronic receivable recording institution;
Means for comparing the first supplier name with the second supplier name indicated in the recording result notification;
Means for determining whether there is a mismatch between the first supplier name and the second supplier name,
When notifying the user who has requested the recording of the electronically recorded claim, the first supplier name determined to be inconsistent exists when notifying the result of the determination, if only the user who has requested the recording is required. Among the users registered in the storage unit, the users who have the mismatched first supplier name as the business partner are extracted from the storage unit, and each of the extracted users is A program for functioning as a means for notifying the first supplier name that has become inconsistent .

Images