JP2003036357A - Intermediating method and device for electronic settlement - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent management of settlements of transaction between corporations by electronic draft from becoming complicated due to a draft of the same drawer and payee being issued for each contract. SOLUTION: An electronic draft center server 301 of an electronic draft center 101 extracts information of a transaction of which buyer and seller coincide from the information of transaction received from a marketplace 102 and presents the extracted information of transaction to a terminal 401 in a corporation on a selling side and, for information of a plurality of transactions selected by the selling side, creates one piece of information of an electronic draft in a new sum of settlement totaling each amount of settlement. The server 301 further performs processing of draft drawing, processing of transfer and processing of repayment according to the information of an electronic draft.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for settlement of funds in transactions between companies, and more particularly to a method and apparatus for electronically performing bill settlement.

[0002]

2. Description of the Related Art At present, bills are frequently used as a means of settlement in transactions between companies. By using bills, the buyer of a transaction (the bill maker) can delay the date when the funds must be prepared. The seller of the transaction (biller of the bill) can also discount the bill to obtain funds, or use the bill directly as a means of payment in another transaction.

[0003] Conventionally, as a method of electronically handling a bond or debt that is generated as an alternative means of such transfer to a cash or deposit account, an electronic bill to digitize a bill or a check,
A technique called electronic check is known (for example, Japanese Patent Laid-Open Nos. 2000-113089 and 2000-1).
13075, JP-A-9-218905, etc.). In these technologies, electronic data indicating that there is an intention to pay the future price is registered from the system of the payer to the system of the payee, and the funds are settled according to the contents of the registration data. Also, in these technologies, it is necessary to prevent duplicates of electronic bills and electronic checks from being duplicated and transferred, so that electronic bills and electronic checks are not stored in the recipient's system, but publicly stored. There is also known a mechanism in which a typical registration agency is prepared and electronic bills and electronic checks are stored in the registration agency (for example, Japanese Patent Laid-Open No. 11-296603).

[0004]

At present, as an electronic commerce site, an intermediary agency for establishing a sales contract on a network called a marketplace is being prepared. In the marketplace, both sellers and buyers can enter into contracts electronically by using the network. If the buyer pays funds to the seller's bank account for settlement of the contract concluded in this marketplace, the transaction party will notify the bank holding the account of the portion related to the funds settlement in the transaction contract data. do it. However, if you try to use a bill when you settle a contract signed in the marketplace,
Since the bill requires a paper face, it cannot be electronically processed on the network. Therefore, an electronic bill is required so that the transaction contract can be settled in the marketplace.

The use of the conventionally known electronic bill and check system for settlement of transactions in this market place has the following problems. In other words, because there is no function to organize correspondence between contracts and electronic bills in the marketplace, one electronic bill will be issued for each contract in one marketplace, and the same issuer or payee Many bills are generated, and the bills cannot be divided when transferred, etc.,
It is difficult to manage.

Therefore, according to the present invention, the settlement of transaction contracts in a plurality of marketplaces by using electronic bills does not need to be divided into electronic bills for each marketplace or each transaction contract in the marketplaces. The purpose is to integrate information.

Another object of the present invention is to manage electronic bills so that the number of bills drawn from the settlement information of the integrated transaction contract does not become too large and partial transfer can be performed.

As described above, according to the present invention, a method of collecting payment information of a plurality of transaction contracts in a plurality of marketplaces into payment information that allows electronic bills to be collectively sent out,
A method for managing bills that can be electronically drafted for the convenience of the bill recipient from the collected payment information is shown.

[0009]

SUMMARY OF THE INVENTION According to the present invention, a plurality of pieces of transaction information involving settlement of funds between a buyer and a seller are received and stored in a storage means. An electronic payment intermediation method for extracting transaction information that matches with each other, and creating one transaction information in which the total settlement amount of each of the plurality of transaction information selected from the extracted transaction information is the new settlement amount. Characterized by the device.

The present invention also provides a transfer processing method for an electronic bill based on the electronic bill information stored in the storage means and including the sender's identifier, the payee's identifier, the first settlement amount, and the settlement date. The electronic bill information to the recipient's computing environment, and in accordance with the instructions from the computing environment, the sender's identifier, the designated new recipient's identifier, and the designated second
A new electronic bill including the settlement amount and settlement date of the electronic bill is stored in the storage means, and the first settlement amount is updated by the amount obtained by subtracting the second settlement amount from the first settlement amount. A method and apparatus are featured.

[0011]

BEST MODE FOR CARRYING OUT THE INVENTION A first embodiment of a process of collecting a plurality of contracts in a plurality of marketplaces will be described in detail. In this embodiment, an electronic bill center 101 that manages electronic bills is provided. As shown in FIG. 1, the electronic bill center 101 is connected with a company A 104, a company B 105, a company C 106, a marketplace 102, and a bank 107, which are companies that issue and receive bills, through a network 108 to process transactions. I do.
The flow of processing of this embodiment is shown in FIG. FIG. 2 illustrates the relationship between the marketplace process 201, the electronic bill center process and the data 202 to be processed, and the seller company and the buyer company process 203 in this embodiment. The arrows in the figure represent the movement of data.

FIG. 3 shows the configuration of the electronic bill center server 301 which processes transactions in the electronic bill center 101. The electronic bill center server 301 includes a communication device 303,
A processor 304 and a storage device 305 are connected by a bus 302 and are configured. Here, the communication device 303 is the network 1
A mechanism for connecting the electronic bill center server 301 to the in-company terminal 401, marketplace 102 and bank 107 of each participating company via 08. Processor 30
4 is a microprocessor, for example, and is a storage device 30.
5 is a device that executes the processing program stored in the storage device 5.
The storage device 305 is, for example, a memory or a fixed disk, and stores a processing program and information related to electronic bill transactions. Specifically, the storage device 305 stores each program of the center contract integration process 307, the automatic contract integration process 308, the center bill transfer process 309, the center bill transfer process 310, the contract information DB (database) 701, and the transfer preparation D.
Each data of B1101, bill DB1801, participant DB901, code conversion table 601, and contract integration candidate table 1001 is stored.

FIG. 4 shows the configuration of the in-company terminal 401 installed by a company that conducts bill transactions (a company that issues bills and a company that receives bills) to process transactions. The corporate terminal 401 includes a communication device 403, a processing device 404, a display device 405, an input device 406, a storage device 410, and a bus 402.
Connect and configure with. Here, the communication device 403 is a mechanism for connecting the corporate terminal 401 to the electronic bill center server 301 via the network 108. The processing device 404 is, for example, a microprocessor, and is a device that executes the process stored in the storage device 410. The storage device 410 is, for example, a memory or a fixed disk, and stores a processing program. The display device 405 is, for example, a display, and outputs information to a person who processes transactions. The input device 406 is, for example, a keyboard, and receives input of information from a person who processes transactions.

In the first embodiment, an electronic bill center 101 that manages electronic bills receives transaction contract information from the marketplace, sends this information to a company that receives the electronic bills, and makes an agreement to collectively perform settlement. It is a method of integration. Below, Company A104 (Company name is “Iroha Co., Ltd.”)
And company B105 (company name "Nihohe Co., Ltd.")
In the marketplace, company A104
Explains the flow of processing when the transaction contract is concluded as the buyer and the company B105 as the seller. Even in the case of other transactions,
The seller of the transaction, the buyer of the transaction, and the market place perform the same processing as the company A 104, the company B 105, and the market place 102, respectively.

When the company A, which is a buyer, and the company B, which is a seller, conclude a transaction contract in the marketplace, the marketplace transmits the marketplace contract information 501 shown in FIG. 5 to the electronic bill center 101. The marketplace contract information 501 is transmitted to the electronic bill center 101 for each transaction contract in the marketplace. The marketplace contract information 501 includes marketplace ID 502, contract date 503, seller company name 504, seller company ID 505, buyer company name 506, buyer company ID 507, product name 508, product details 509,
It consists of a payment amount 510, a payment date 511, a bill issuing date 512, and a marketplace contract number 513.

The marketplace ID 502 is a number for the electronic bill center 101 to uniquely identify the marketplace 102 connected to the electronic bill center 101, and is a number unique to the marketplace with which the transaction contract is made. Contract date 503 indicates the date when the contract was signed at the marketplace. The seller company name 504 is
It is the seller of the transaction and the name of the seller company that provides the goods or services. The seller company ID 505 is a number used by the marketplace to identify the seller company. The buyer company name 506 is the name of the buyer company who is the buyer of the transaction and receives the product or service. The buyer company ID 507 is a number used by the marketplace to identify the buyer company. The product name 508 is the name of the product or service of the transaction. Product details 509
Is the details of the contents of the product or service of the transaction. The payment amount 510 is an amount paid as consideration for a product or service. The settlement date 511 is a date to settle the funds as consideration for the goods and services, and is a redemption date of the electronic bill to be given for the transaction. Bill Drawer (Buyer Company)
Is the payment date 511.
Pay the bill holder by. The bill issuing date 512 is the date when the buyer of the transaction issues the electronic bill of the transaction. The marketplace contract number 513 is a number for uniquely identifying the transaction contract in the marketplace.

When the electronic bill center 101 receives the marketplace contract information 501, the electronic bill center 101 performs an electronic bill drawing process, which will be described later, based on the received marketplace contract information 501. Buyer company ID here
507 and seller company ID 505 are for identifying the company, but different marketplaces 102 because they are uniquely determined by the marketplace 102.
Then, the contents may not be compatible. Therefore, the electronic bill center 101 converts the items of information received from the marketplace 102 into a format that can be handled uniformly within the electronic bill center 101. The code conversion table 601 shown in FIG. 6 is used to perform this conversion. The code conversion table 601 is a table showing how each code manager 602 holds various codes. The code manager 602 indicates an organization that manages codes, and is a character string indicating the electronic bill center 101 or a marketplace ID. The code type 603 is the type of code to be converted, and here, the company ID can be converted. The code data 604 records the code of the code type 603 managed by each code manager 602.

According to the code conversion table 601, the electronic bill center 101 and the electronic bill center 10 which are code managers.
It is possible to know how each marketplace participating in 1 allocates a company ID to a company that conducts transactions, and it is possible to perform mutual conversion of the company ID. Specifically, the marketplace ID of the marketplace contract information 501 is "MPID01" and the seller company ID is "ARM401". Therefore, from the code conversion table 601, the electronic bill center 101 of the seller company of this transaction contract is displayed. It is converted to "0002" as the company ID to be managed. Similarly, for the buyer company, marketplace contract information 50
The marketer ID is “MP
Since the market place of ID01 is managed as "HIS148", it can be converted to "0001" as the company ID managed by the electronic bill center 101.

The electronic bill center 101 receives the marketplace contract information 501 from the marketplace 102, creates new contract information 703 in the contract information DB 701 shown in FIG. 7, and stores it in the item of the same name. Specifically, the marketplace ID 70 of the contract information 703
5, contract date 706, seller company name 707, buyer company name 70
9, product name 711, product details 712, payment amount 71
3, settlement date 714, bill issuance date 715, and marketplace contract number 716 for marketplace ID 50 of marketplace contract information 501, respectively.
2, contract date 503, seller company name 504, buyer company name 50
6, product name 508, product details 509, payment amount 51
0, settlement date 511, bill issuing date 512, and marketplace contract number 513 are set. Also, the seller company ID
708 and a buyer company ID 710 are a company I managed by the electronic note center 101 for the seller company ID 505 and the buyer company ID 507 of the marketplace contract information 501, respectively.
Set the value converted to D. The contract number 704 is unique in all contract information 703, and the contract information 703 is unique.
Is set for each contract information 703, for example, as a natural number.
The state 717 represents the processing state of the contract of the contract information 703, and “not yet paid” is set as the initial state.
When the integration process ends, the status 717 is changed to “integrated”.

The contract information DB 701 stores all marketplace contract information 501 received in the past from all marketplaces. This contract information DB701
This makes it possible to handle transaction contracts in multiple marketplaces collectively. In FIG. 7, the information of the marketplace contract information 501 received last is recorded in the column of the contract number of the contract information 703 of “65”.

Information is recorded in the contract information DB 701 for each transaction contract in the marketplace. The transaction contract in this marketplace depends on the type of marketplace, but many transaction contracts occur even for the same seller and buyer for each type of product or each transaction input.
Therefore, when the bills are drawn out in units of the contract information 701, the recipient may be inconvenient because the number of similar bills becomes too large. So this contract information DB70
The information in item 1 is referred to by the seller company of the transaction (the company that receives the bill) to determine how to consolidate the contracts and issue the electronic bill. When there is a request from a company to integrate contracts, the electronic bill center 101 receives the contract information DB 701.
The contract information in which the company is a seller company is searched, and all the contract information 703 selected as a result is transmitted. The company that receives this classifies the contracts according to the contracts that are collectively issued. The center contract integration process 307 and the seller contract integration process 407 that are processes for doing this will be described with reference to FIG. As an example, a case where the company B105 requests contract integration is taken as an example.

In the company B, which is a seller company, when the seller contract integration process 407 is started by the company terminal 401 (step 851), the company terminal 401 displays the display device 405.
A company ID and password input screen is displayed on the screen, and the company person in charge of the company receives the company ID and password (step 852). Here, the company ID and password input screen is a screen that prompts the user to enter the company ID and password.
The company ID is a code managed by the electronic bill center 101 and assigned so as to be unique to each company. The password is a code for each company to connect to the electronic bill center 101, and is registered in the electronic bill center 101 by each company.

Upon receiving the input of the company ID and the password, the in-company terminal 401 transmits this to the electronic bill center 101 (step 853). Electronic bill center server 30
In step 1, when the center contract integration process 307 is activated (step 801), the electronic bill center server 301
Waiting for the connection from the company, when the company ID and password are sent from the company, they are received (step 802) and the participant DB shown in FIG. 9 shows that the company ID and password are correct.
Verification is performed according to 901.

The participant DB 901 is a DB for recording participant information 907 which is a set of a company ID 902, a password 903, a company name 904, a settlement bank name 905 and an account number 906. ID9
02 to password 903 of the company, company name 904,
The settlement bank name 905 and the account number 906 can be checked. Here, the settlement bank name 905 is the bank name for which the company performs the electronic bill fund settlement process, and the account number 906 is the account number of the bank specified by the settlement bank name 905.

The center contract integration processing 307 searches the participant DB 901 by the received company ID and checks whether the retrieved password 903 is the same as the received password. If they are the same, the company ID and password are not verified. If it is successful, if not the same, the verification is unsuccessful and the process ends (step 803). After that, if the verification of the company ID and password is mentioned, the participant DB 9
It is assumed that the confirmation processing of the correspondence between the company ID and the password by 01 is performed.

When the verification of the company ID and the password is successful, the center contract integration process 307 next searches the contract information DB 701 by the company ID received from the seller company. This search is performed by the seller company ID 7 in the contract information DB 701.
08 is the received company ID and the contract information DB 70
The contract information 703 of which the status 717 of 1 is “unassigned” is searched (step 804). Next, the results selected by the search are classified according to the company ID of the buyer, and different integration candidate numbers 1003 are assigned to the respective classifications to obtain the contract integration candidate table 1001 in FIG. 10 (step 805).

Contract information 10 in the contract integration candidate table 1001
02 items (contract number 1004, marketplace ID 1005, contract date 1006, seller company name 1007,
Seller company ID 1008, Buyer company name 1009, Buyer company ID 1010, Product name 1011, Product details 1012,
Settlement amount 1013, settlement date 1014, bill issuing date 101
5. In the marketplace contract number 1016), the value of the corresponding item of the same name in the contract information 703 of the contract information DB 701 is copied and recorded. However, integration candidate number 100
No. 3 assigns the same number to contracts classified into the same category, and gives different numbers to contracts classified into different classes. The center contract integration process 307 transmits the created contract integration candidate table 1001 to the seller company (step 806).

When the seller contract integration process 407 of the seller company receives the contract integration candidate table 1001 (step 854),
All the information of the contract integration candidate table 1001 is displayed on the display device 405 for each integration candidate number, and the input of the contract to be combined is received from the input device 406 (step 855). This input is performed by the person in charge of the seller company inputting all the "contract number" of the contract to be combined. The seller contract integration processing 407 of the seller company transmits all the inputted contract numbers to the electronic bill center 101 (step 856).

Upon receipt of the contract number to be integrated from the in-company terminal 401 of the seller company (step 807), the center contract integration processing 307 confirms whether the received contract number has the same integration candidate number 1003 in the contract integration candidate table 1001. If they are not the same, the process ends (step 808). The status 717 of the contract information 703 of the contract information DB 701 corresponding to the received contract number is changed to “integrated” and registered in the drawing preparation DB 1101 shown in FIG. 11 (step 80).
9).

The contract integration information 1103 recorded in the drawing preparation DB 1101 is the contract information 7 of the received contract number.
03 information, the following processing is performed. Drawing preparation DB
The contract number 1104 of 1101 records all the received contract numbers. Seller company ID 1 in the drawing preparation DB 1101
106, seller company name 1105, buyer company ID 1108,
The buyer company name 1107 records the information of the item of the same name in the contract information 703 corresponding to the received contract number. The payment amount 1109 of the payment preparation DB 1101 records the total of each payment amount 713 of the contract information 703 corresponding to the received contract number. Settlement date 1110 of the drawing preparation DB 1101
Records the latest settlement date 714 among the settlement dates 714 of the contract information 703 corresponding to the received contract number. The bill issuance date 1111 of the draft preparation DB 1101 is the bill issuance date 71 of the contract information 703 corresponding to the received contract number.
Record the latest draft date 715 of the five. Here, the settlement date included in the contract corresponding to the settlement date and the bill issuance date,
If it is earlier than the bill issuance date, the buyer of the transaction will have to prepare funds or issue bills before the settlement date and the bill issuance date of the first contract. Therefore, in the present embodiment, the act of concluding a contract is performed at the request of the seller of the transaction. Therefore, the settlement date and the bill issuance date are set to be the latest days so that the buyer of the transaction is not disadvantaged. The state 1112 records “integrated” for the contract integration information 1103 that has been contract integrated.

The distribution preparation DB 1101 shown in FIG. 11 stores the contract number “20, 32, 35” and “50” as the contract number to be integrated by the company B in the state where the integrated information of the contract is present.
A diagram showing a state in which only "61" is specified, and then the center contract integration process and the seller contract integration process are activated again and two contracts of "62, 65" are specified and the information is additionally recorded. Is. As a result, the contract with the contract number "61" has already been integrated with other contracts without drawing out the bills at the same time, and the contract numbers "62" and "65" have to be settled by the bills of the two contracts. Becomes In the above, the process of combining a plurality of contracts in a plurality of marketplaces as a unit of a bill that can be drawn out at the same time has been shown.

Next, a second embodiment of the processing for collecting a plurality of contracts in a plurality of marketplaces will be described. The processing flow of the second embodiment is shown in FIG. Figure 1
2 is a marketplace process 120 according to the present embodiment.
1. Processing of electronic bill center and data 12 of the processing target
02, the processing 1203 of the seller company and the buyer company is illustrated. The arrows in the figure represent the movement of data. In the second embodiment, the electronic bill center 1 has a rule that a company that is a bill receiver in advance arranges a contract.
This is a method of registering 01. Hereinafter, a rule that the company B registers in the storage device 305 in advance (contract integration rule 1301) and a flow of processing when the company A enters into a transaction contract as a buyer and the company B as a seller will be described.

The company B, which is a seller of a transaction for making a settlement using the electronic bill center 101, registers in advance a rule on a method of concluding a contract in the electronic bill center 101. This rule evaluates the transaction contract information sequentially sent from the marketplace and integrates the transaction contract with the previous transaction contract between Company A and Company B, or creates a new contract integration unit. It is for deciding what to do.

In order to integrate transaction contracts using this rule, the electronic bill center 101 has a contract integration rule DB 1301 shown in FIG.
Holds 03. The contract integration rule DB 1301 includes, as items, a rule number 1304, a seller company ID 1305, a settlement amount upper limit 1306, an application start transfer date 1307, an application end transfer date 1308, an application start transfer date 1309, an application end transfer date 1310, and an integrated end amount 1311, A company having a rule application end date 1312 holds a contract integration rule 1303 for collecting a plurality of contracts.

Here, the rule number 1304 is a number for uniquely identifying the rule contract integration rule 1303 in the contract integration rule DB 1301. Seller company ID 130
Reference numeral 5 is a company ID of the seller company of the transaction to which the rule is applied, which is a company ID 902 managed by the participant DB 901. The payment amount upper limit 1306 is the upper limit of the payment amount of the contract to be summarized based on this contract integration rule,
For transactions with a payment amount exceeding this payment amount upper limit,
Not subject to contract integration. The application start transfer date 1307 and the application end transfer date 1308 are the contract integration rule 1303.
Determine the range of draft dates for contracts to be summarized based on
The application start settlement date 1309 and the application end settlement date 1310 are
Based on the contract integration rule 1303, the settlement date range of the contracts to be put together is determined. The integration end amount 1311 is an amount for ending the contract integration. Rule application end date 131
2 is the last day to apply the contract integration rule 1303.

In this contract integration rule 1303, between the contract integration rules 1303 having the same seller company ID 1305, the period from the application start distribution date 1307 to the application end distribution date 1308 and the application start settlement date 1309 to the application end settlement date 13
Make sure there is no overlap in both 10 periods. That is, when a bill issuing date and a settlement date are specified for a certain seller company ID, the application start issuing date 1307 to the application end issuing date 1
There are not a plurality of contract integration rules 1303 in which the period 308 includes the designated bill issuing date and the period from the application start settlement date 1309 to the application end settlement date 1310 includes the designated settlement date.

The process of collecting contracts using this rule is the automatic contract integration process 308. The processing of this automatic contract integration processing 308 is shown in FIG. As in the first embodiment, when the electronic bill center 101 receives the marketplace contract information 501 from the marketplace, converts the code, and additionally records the contract information in the contract information DB 701, the automatic contract integration processing 308 is activated. (Step 1401).

The automatic contract integration processing 308 is a contract information DB.
The contract information 703 whose status 717 added from 701 is “unassigned” is taken out, and the contract integration rule 1303 matching the contract information 703 is retrieved from the contract integration rule DB 1301 and taken out (step 1402). This search is to retrieve the contract integration rule 1303 that satisfies the following five points. First, the contract company information 703 and the contract integration rule 1303 match the seller company ID. Further, the settlement amount of the contract information 703 is less than or equal to the settlement amount upper limit of the contract integration rule 1303. Further, the bill issuance date of the contract information 703 is after the application start issuance date and the application end issuance date of the contract integration rule 1303. Further, the settlement date of the contract information 703 is after the application start settlement date of the contract integration rule 1303 and before the application end settlement date. Further, the processing date of this processing is before the rule application end date of the contract integration rule 1303.

If there is no contract integration rule 1303 that matches the contract information 703 (No at step 1403), the transaction contract of this contract information 703 is not combined with other transaction contracts. That is, new contract integration information 1103 is created and added to the drawing preparation DB 1101 independently from this contract information 703 (step 1408). This is done by creating new contract integration information 1103 in the distribution preparation DB 1101 and copying the information of the contract information 703 to the corresponding item of the contract integration information 1103. In this copy,
The contract number 704 of the contract information 703 is set to the contract integrated information 110.
3 contract number 1104. Similarly contract information 7
The seller company name 707 of 03 to the seller company name 1105 of the contract integration information 1103, and the seller company ID 70 of the contract information 703
8 to the seller company ID 1106 of the contract integration information 1103,
Buyer company name 709 of the contract information 703 is the contract integrated information 11
The buyer company name 1107 of 03, the buyer company ID 710 of the contract information 703, and the buyer company ID 1 of the contract integration information 1103
108, the settlement amount 713 of the contract information 703 to the settlement amount 1109 of the contract integration information 1103, the settlement date 714 of the contract information 703 to the settlement date 1110 of the contract integration information 1103.
Also, the bill-drawing date 715 of the contract information 703 is copied to the bill-drawing date 1111 of the integrated contract information 1103. The state 717 of the contract information 703 added at this time is “integrated”, and the state 1112 of the contract integrated information 1103 is “unassigned (integrated)”. Here, “integration end” means the contract integration information 1103 in which another contract cannot be additionally integrated.

If there is a contract integration rule 1303 that matches the contract information 703 (Yes in step 1403),
The server of the electronic bill center 101 is a drawing preparation DB 1101.
Then, it is searched whether or not the contract integration information 1103 that is the target of the integration of the contract information 703 already exists (step 1404). This is to search the contract integration information 1103 created by the contract integration rule extracted in step 1402, and is performed under the following conditions. First contract information 703
And the contract integration information 1103, the seller company ID, the buyer company I
D must match. The contract integration information 1103
Of the bill issuance date 1111 is after the application start issuance date 1307 and before the application end issuance date 1308 of the contract integration rule acquired in step 1402. Further, the settlement date 1110 of the contract integration information 1103 is the application start settlement date 1309 of the contract integration rule 1303 extracted in step 1402.
After that and before the application end settlement date 1310. Further, the state 1112 of the contract integration information 1103 is “not yet issued”. If there is no contract integration information 1103 that meets these conditions (No in step 1405), the transaction contract of this contract information 703 will not be further integrated with the contract integration information already registered in the drawing preparation DB 1101. In this case, an item of new contract integration information is added to the contract information 703 (step 1409). This is the same as the above-mentioned step 1408, but the state 1112 of the contract integration information 1103 is set to “unassigned”.

When the contract integration information 1103 to be integrated is found from the drawing preparation DB 1101, it is confirmed whether or not the settlement amount 1109 is equal to or more than the integration end amount 1311 of the contract integration rule 1303 as a result of the search in step 1402 ( Step 1406). When the settlement amount 1109 of the existing contract integration information 1103 is equal to or more than the integration end amount 1311, the state 111 of the contract integration information 1103.
2 is updated to “not yet issued (completion of integration)” (step 141
0), the new contract integrated information 1103 item for the new contract information 703 is added to the drawing preparation DB 1101. This is the same processing as step 1409 described above. The settlement amount 110 of the existing contract integration information 1103
It is possible to manage so that the sum of 9 and the settlement amount 1109 of the new contract integration information 1103 does not exceed the integration end amount 1311.

When the settlement amount 1109 of the contract integration information 1103 found in step 1404 is less than the integration end amount 1311, the automatic contract integration processing 308 synthesizes the new contract information 703 with the found contract integration information 1103. (Step 1407). This synthesis is performed by contract information 703 for the settlement amount 1109 of the contract integration information 1103.
Payment amount 713 is added, and the bill issuance date 1111 of the contract integration information 1103 and the bill issuance date 715 of the contract information 703 are added.
Billing date for new contract integration information 1103
111 is the settlement date 1110 of the contract integration information 1103 and the settlement date 714 of the contract information 703, whichever is later, is set as the settlement date 1110 of the new contract integration information 1103.

After completing the contract integration process according to the rules of the day, the electronic bill center 101 searches the contract integration rule DB 1301 for a new contract integration rule 1303 after the rule application end date. If there are one or more search results, the integration of contracts integrated by these rules is terminated. Specifically, the following processing is performed. The status 1112 of the item 1102 of the drawing preparation DB 1101 is “not yet drawn” or “not yet drawn (integrated)”, so that the seller company ID 1106, the buyer company ID 1108, the bill drawing date 1111 and the settlement date 1110 are newly applied to the rule. The contract integration information 1103 that matches the contract integration rule 1303 that has passed the date 1312 is searched. This search is to retrieve contract integration information 1103 that satisfies the following four points. First, the seller company ID 1106 of the contract integration information 1103
And the seller company ID 1305 of the contract integration rule 1303 match. Further, the bill issuance date of the contract integration information 1103 is after the application start issuance date 1307 of the contract integration rule 1303 and before the application end issuance date 1308. Further, the settlement date of the contract integration information 1103 is the application start settlement date 1309 or later of the contract integration rule 1303 and the application end settlement date 131.
Before 0. Contract integration information 110 that meets this condition
If 3 is found, the state 1112 of the contract integration information 1103 is set to “integrated”.

The above-mentioned automatic contract integration processing is performed on the contract information shown in FIG. 7 as follows. First, as the contract information of the contract number “61” in the contract information DB 701, the contract integration rule 1303 of the rule number “1” is used from the seller company ID, the bill issuance date, and the settlement date. As a result, the contract integration information 1103 indicates that the contract number is “61” and the seller company I
D is "0002", buyer company ID is "0001", settlement date is "2001/6/28", and bill issuance date is "2001".
/ 3/15 ", and the contract integration information 1103 with the settlement amount of" 3,000,000 "is created.
If the contract integration rule similarly applied is applied to the contract information 703 of “2”, the contract integration rule of rule number “2” is used, and the seller company ID is “0002”, the buyer company ID is “0001”, and the settlement is performed. The day is "2001/6/2"
Contract integration information 1103 in which the bill issuance date is "2001/3/20" and the settlement amount is "2,500,000"
Is made. Similarly, the contract information 703 of the contract numbers “63” and “64” in the contract information DB 701 is also processed, and the contract integrated information 1103 is created from each. Next, in the processing of the contract information 703 with the contract number “65”, the contract integration rule 1303 conforming to the contract information 703 is the rule with the rule number “2”, and the contract number “62”.
The contract information 703, the seller company ID, and the buyer company ID are the same. Therefore, the contract information 703 whose contract number is "62"
Contract number is “65” in the contract integration information 1103 created in
The contract information 703 of is integrated. Although the company ID does not change due to composition, the payment amount, the bill issuance date, and the payment date are changed as shown in the automatic contract integration process. That is, the settlement amount of the contract integration information 1103 becomes “3,500,000” by adding the settlement amount of the new contract, and the bill issuance date is the bill issuance date “2001/3/20” of the contract integration information 1103 and the contract information 703. Billing date of contract number "65" of "20"
Take the later date of 01/3/23 ”to“ 2001/3 ”
/ 23 ”, and the settlement date is also the later date,“ 2001/6/27 ”. Further, the contract integration information 11
"65" is added to the contract number of 03 to make "62,65".

After that, when the contract integration processing by the rule in the electronic bill center 101 on March 15, 2001 is finished, the rule number "1" is past the rule application end date of the contract integration rule 1303, so this rule State 111 of the contract integration information 1103 whose contract number is “61” in the drawing preparation DB 1101 in order to end the contract integration by
Change 2 to "Integrated". Similarly, March 25, 2001
When the day processing is finished, it is the rule application end date of the contract integration rule 1303 of the rule number “2”, so the state of the contract integration information 1103 in which the contract number integrated based on this rule is “62,65” Change 1112 to "Integrated".

Next, an electronic bill is drawn out from the contracts made by the first and second embodiments, which is a process of putting together a plurality of contracts in a plurality of marketplaces, and the electronic bills are transferred. An embodiment of a management method such as reimbursement and redemption will be described. FIG. 1 shows the flow of processing of this embodiment.
5 shows. FIG. 15 shows 1551 at the time of transfer and 155 at the time of transfer.
2. Processing 1501 of marketplace, processing 1501 of electronic bill center and processing target data 1502, processing 15 of seller company and buyer company in the present embodiment of redemption 1553
The relationship of No. 03 is illustrated. The arrows in the figure represent the movement of data. The drawing of this electronic bill is based on the drawing preparation DB 1101 created in the first and second embodiments.
This is done based on the data of the contract integration information 1103.

Drawing out electronic bills from the summarized contract,
An embodiment for managing will be described. First, based on the contract information collected in the contract integration information DB 1101, the center bill drawing process 309 in the bill center and the bill paying process 408 in the buyer company for the buyer company to draw out the electronic bill will be described with reference to FIG.

In the company A, which is the buyer of transactions in the marketplace, when the bill of purchase billing processing 408 is started to draw out the electronic bill (step 1651).
The in-company terminal 401 of the buyer company is displayed on the display device 405 as company I.
The screen for entering D and the password is displayed, and the input of the company ID and the password is received from the input device 406 (step 1).
652). Here, the screen for entering the company ID and password is a screen for prompting the user to enter the company ID and password. Company A
Upon receiving the input of the company ID and the password, the in-company terminal 401 transmits the same to the electronic bill center (step 1653). When the center bill issuing process 309 of the electronic bill center 101 for issuing a bill by the buyer company is activated (step 1601), the company ID and password are received from the buyer company (step 1602), and the company ID and password are verified. (Step 1603) If the verification fails, the process ends.

The center bill drawing process 309 searches the drawing preparation DB 1101 by the received company ID, and transmits the information of candidates that can be drawn as an electronic bill to the company A (step 1604). Specifically, the drawing preparation DB
In 1101, the buyer company ID 1108 is the I of the company connected to the electronic bill center in the center bill drawing process.
All the contract integrated information 1103 that is D and the status 1112 is “integrated” are searched, and the matched contract integrated information 11 is searched.
03 to contract number 1104, seller company name 1105, seller company ID 1106, buyer company name 1107, buyer company ID
A set of information 1108, settlement amount 1109, settlement date 1110, and bill issuing date 1111 is transmitted to the company A who is the buyer.

When the bill-of-bills billing process 408 of the company A receives the information of the candidates that can be billed as a bill from the server of the electronic bill center (step 1654), the company A is billed.
The person in charge of the selection selects a candidate to be actually drawn out as an electronic bill from the candidates, and transmits the result of the selection to the electronic bill center 101 as a bill drawing registration (step 165).
5).

Here, the distribution candidate displayed on the display device 405 of the company terminal 401 when the company terminal 401 of the company A displays the information received from the server of the electronic bill center and selects a candidate to be drawn as an electronic bill. The list screen 1701 is shown in FIG. The draft candidate list screen 1701 displays information 1704 of electronic bill candidates received from the electronic bill center for all the candidates 1703 for each item 1702, and also inputs a selection of the draft of the candidate in a draft selection field 1705.
Selection box 1706. Shake button 170
It is assumed that when 7 is pressed, the candidate 1703 corresponding to the selection box 1706 checked at that time is instructed to be drawn as an electronic bill. In-company terminal 4 of company A
01 sends the contract number of the candidate 1703 whose selection box 1706 has been checked to the electronic bill center as the bill drawing registration. In the example of FIG. 17, the contract number is “62,6
Since the candidate "5" is selected, the in-company terminal of the company A transmits the contract number "62,65" to the electronic bill center as center distribution registration.

When the electronic bill center receives the contract number which is the bill drawing registration (step 1606), the electronic bill center executes the process of issuing the contract integrated information 1103 in the drawing preparation DB 1101 corresponding to the received contract number as an electronic bill. Drawing out an electronic bill is to record the information of the drawn bill in a bill DB 1801 managed by the electronic bill center shown in FIG.

The bill DB 1801 manages, as bill information 1802, all the electronic bills that have been sent out at that time. The bill information 1802 is the bill number 1804,
Recipient company name 1805, Recipient company ID 1806, Drawer company name 1807, Drawer company ID 1808, Settlement amount 180
9 has items of a settlement date 1810 and a bill issuing date 1811.

The registration of the electronic bill is first executed in the bill DB1.
The seller company ID 1106 of the integrated contract information 1103 that is about to be sent out as an electronic bill matches the recipient company ID 1806 of the bill information 1802, and similarly, the buyer company ID 1108 of the integrated contract information 1103 is the issuing company of the bill information 1802. The bill information 1802 that matches the ID 1808 and the settlement date 1110 of the contract integration information 1103 and the settlement date 1810 of the bill information 1802 are searched for (step 1607). If there is bill information 1802 that matches the above three items, the settlement amount 1809 of the bill information 1802 is set to the settlement amount 1 of the contract integration information 1103.
109 is added, and the state 1112 of the contract integration information 1103 is added.
Is set to “sent” (step 1609).

As a result, the same issuing company ID and receiving company I
D, it is assumed that a new bill is drawn without generating a plurality of bill information 1802 on the settlement date. Bill DB 1801
When the corresponding bill information D402 cannot be found by the search of, the bill information 180 is newly added to the bill DB 1801.
802 is added, and other note information 1 is added to the note number 1804.
Number that can be uniquely identified from the bill number of 802, Receiving company I
D1806 is the seller company ID 1 of the contract integration information 1103.
106 and the recipient company name 1805 include contract integration information 1103.
The seller company name 1105, the issuing company ID 1808 is the buyer company ID 1108 of the contract integration information 1103, and the issuing company name 1807 is the buyer company name 110 of the contract integration information 1103.
7, settlement amount 1809, settlement date 1810, bill issuing date 1
The payment amount 1 of the contract integration information 1103 is shown in 811.
The values of the items 109, settlement date 310, and bill issuing date 1111 are copied, and the state 1112 of the contract integration information 1103 is set to "issued" (step 1610). As a result, it is assumed that the bills classified into the new issuing company ID 1808, the receiving company ID 1806, and the settlement date 1810 are newly issued.

Next, the transfer of the electronic bill will be described. In the transfer of the electronic bill, the settlement amount of the bill information 1804 is added / subtracted so that the bill information 1804 of the same payee / drawer does not occur in the bill DB 1801.

The details of the transfer process will be described with reference to the flowchart of FIG. 19 by taking the process of transferring the electronic bill from the company B (Nihohe Co., Ltd.) to the company C (Tochiri Co., Ltd.) as an example. When the transfer source processing 409 is started by the transfer source company to transfer the bill (step 195).
1) The in-company terminal 401 of the transfer source company is the display device 40.
A screen for inputting the company ID and password is displayed on 5, and the input of the company ID and password is received from the input device 406 (step 1952). Here, the screen for entering the company ID and password is a screen for prompting the user to enter the company ID and password. When the transfer source process 409 of the transfer source company B receives the company ID and password, it transmits them to the electronic bill center (step 1953).

The server 301 of the electronic bill center transfers the bill of the center 310 to the bill to be transferred by the transfer source company.
Is activated (step 1901), the company ID and password are received from the transfer source company (step 190).
2) The company ID and password are verified, and if the verification fails, the process ends (step 1903). In the center bill transfer process 310, the received company ID is the bill DB1.
Bill information 180 equal to the recipient company ID 1805 of 801
2 is searched from the bill DB 1801. The bill information 1802 obtained as a result of the search is the information of the electronic bill owned by the transfer source company and is transferable. The center bill transfer process 310 collects all the bill information 1802 of the electronic bills that can be transferred and is obtained as a result of the search, and as a list of transferable bills 2001 shown in FIG. Send to former company (Step 19)
04).

This transferable bill list 2001 is a bill D.
Transferable bill information 2002 is created from each bill information 1802 obtained by the search from B1801. A bill number 2003, a recipient company name 2004, a recipient company ID 2005, a issuing company name 2006, a issuing company ID 2008, a settlement amount 2009 of a list of transferable bills 2001,
The settlement date 2010 and the bill issuing date 2011 are the bill DB 18
01 bill number 1804, recipient company name 1805, recipient company ID 1806, issuing company name 1807, issuing company ID 1
The values of 808, settlement amount 1809, settlement date 1810, and bill issuing date 1811 are copied.

The in-company terminal 401 of the transfer source company receives the list of transferable bills 2001 (step 195).
4) The transfer bill selection screen is displayed on the display device 405.
Here, the transfer bill selection screen is a list of transferable bills 200
1 is a screen that displays all of the transferable note information 2002 included in 1 and prompts the user to input a note number to be transferred in the transferable note information 2002. The in-company terminal 401 of the transfer source company receives the input of the bill number of the bill to be transferred from the input device 406 (step 1955). Next, the in-company terminal 401 of the transfer source company displays an input screen of the transfer destination company on the display device 405 and receives the input of the company ID of the transfer destination company (step 1956). The transfer destination input screen is a screen that prompts the user to input information that specifies the company to which the bill is transferred, and here, as the information that specifies the company, the company ID managed by the electronic bill center is used. Next, the in-company terminal 401 of the transfer source company displays the input screen for the payment amount of the bills to be transferred, and receives the input amount of the bills to be transferred (step 1957). The input screen of the transfer bill amount is a screen for prompting the user to input how much of the transfer amount of the electronic bill to be transferred. As described above, the in-company terminal 401 of the transfer source company has the bill number of the bill to be transferred and the transfer destination company I.
D, when the settlement amount of the bill to be transferred is received, these are transmitted to the server of the electronic bill center (step 195).
8).

When the server of the electronic bill center receives the bill number of the bill to be transferred, the company ID of the bill to be transferred, and the payment amount of the bill to be transferred from the in-company terminal 401 of the transfer source company (step 1905), the information is entered. Bill DB1 based on
A bill transfer process is performed for 801 (step 19).
06). The following processing is performed as the processing for transferring this bill. First, the bill information 1802 designated by the bill number of the bill to be transferred, the issuing company ID 1808, and the issuing company name 180
7. Payment date 1810 is the same, recipient company ID 180
Bill information 6 where 6 is the same as the transferee company ID
Search for 02. When the bill information 1802 is found as a result of the search, the settlement amount 1 of the bill information 1802
In 809, the settlement amount of the bill to be transferred received from the transfer source company is added.

If the bill information 1802 is not found as a result of the search, new bill information 1802 is created.
At this time, the recipient company ID 1806 is set to the company ID designated as the transfer destination, and the recipient company name 1805 is set by searching the participant DB 901 for the company name corresponding to the set company ID. To search the participant DB 901 and set the recipient company name, the participant DB 901 searches the participant information 907 for which the company ID 902 is the company ID designated as the transfer destination, and the company name 904 of the participant information 907 is searched. This is done by copying it to the recipient company name. Bill information 18
A settlement amount 1809 of 02 sets the settlement amount of the bill to be transferred received from the transfer source company. The bill number 1804 of the bill information 1802 sets a number different from any bill number 1804 of the other bill information 1802. Drawer name 1
The values of the corresponding items from the bill information 1802 designated by the bill number of the bill to be transferred are copied to 807, the issuing company ID 1808, the settlement date 1810, and the bill issuing date 1811. By these processes, the right of the electronic bill for the transfer to the transferee company is generated.

Next, the center bill transfer process 310 deletes the right of the electronic bill transferred from the transfer source (step 1907). This is the bill number 180 of the bill to be transferred first.
The amount designated as the settlement amount of the bill to be transferred is subtracted from the settlement amount 1809 of the bill information 1802 designated in 4. If the result of subtracting the payment amount is 0,
The bill information 1802 is deleted from the bill DB 1801. As a result, the transferor loses the right to the electronic bill by the specified amount. If the result is negative when the payment amount is subtracted, the transfer of the bill is invalidated, the transfer amount 1809 of the transfer source is returned to the original value, and the addition of the transfer amount of the transfer destination or creation of the bill information 1802 is canceled.

Electronic bills registered in the bill DB 1801 are automatically redeemed. The processing contents of the redemption processing 311 in the server 301 of this electronic bill center will be described below. The server 301 of the electronic bill center uses the bill DB1 every day.
801 is searched for the bill information 1802 whose settlement date 1810 is the current day. Bill information 180 found
The following processing is performed for each of the two. First, the participant DB 9 based on the recipient company ID 1806 of the bill information 1802.
01 is retrieved to acquire the settlement bank name 905 and account number 906 of the company designated as the receiving company. Next, the participant DB 901 is searched by the issuing company ID 1808 of the bill information 1802, and the settlement bank name 905 and the account number 906 of the company designated as the issuing company are acquired.
The redemption of the electronic bill is performed by transferring the funds from the account specified by the account number of the settlement bank of the issuing company retrieved above to the account specified by the account number of the settlement bank of the recipient company. The electronic bill center server 301 sends to the bank 107 designated as the settlement bank of the issuing company,
Both the account numbers in the participant DB and the settlement amount information in the bill information 1802 are notified, and the transfer of funds between both accounts is requested. The electronic bill center server 301 may notify the settlement bank of the recipient company of the account number of the recipient company and the settlement amount information of the bill information 1802. The bank 107 designated as both settlement banks deposits and withdraws money from the designated accounts to complete the settlement of funds. The electronic bill center sends a bill settlement request to the bank, and then the bill DB 18
The bill information 1802 is deleted from 01.

[0065]

As described above, according to the present invention, the settlement information of a plurality of transaction contracts in a plurality of marketplaces is collected in accordance with a direct instruction of a seller of a transaction (a bill maker) or an instruction by a rule. You can Therefore, management does not occur because many similar electronic bills do not occur.
The bills can be divided and transferred.

[Brief description of drawings]

FIG. 1 is an overall view of a system according to an embodiment of the present invention.

FIG. 2 is a diagram showing an outline of transaction contract integration processing performed according to an instruction from a seller company according to the first embodiment.

FIG. 3 is a configuration diagram of an electronic bill center server 301 of the embodiment.

FIG. 4 is a configuration diagram of a company terminal 401 according to the embodiment.

FIG. 5 is a diagram showing an example of marketplace contract information sent to an electronic bill center as information on a contract for a transaction.

FIG. 6 is a diagram showing an example of a table for converting each code system in the electronic bill center.

FIG. 7 is a diagram showing a data configuration of a contract information DB 701 according to the embodiment.

FIG. 8 is a flowchart illustrating a procedure of contract integration processing according to the first embodiment.

FIG. 9 is a diagram showing a data configuration of a participant DB 901 of the embodiment.

FIG. 10 is a diagram showing a data configuration of a contract integration candidate table 1001 according to the first embodiment.

FIG. 11 is a diagram showing a data structure of a drawing preparation DB 1101 according to the embodiment.

FIG. 12 is a diagram showing an outline of processing for integrating transaction contracts based on the rules of the second embodiment.

FIG. 13 is a diagram showing a data configuration of a contract integration rule 1303 according to the second embodiment.

FIG. 14 is a flowchart showing a processing flow of automatic contract integration processing 308 of the second embodiment.

FIG. 15 is a diagram showing an outline of processing of performing transfer and redemption according to the embodiment.

FIG. 16 is a flowchart illustrating a flow of a bill drawing process according to the embodiment.

FIG. 17 is a diagram showing an example of a distribution candidate list screen 1701.

FIG. 18 is a diagram showing a data configuration of a bill DB 1801 of the embodiment.

FIG. 19 is a flowchart showing a flow of processing when a bill is transferred according to the embodiment.

FIG. 20 is a diagram showing a data configuration of a transferable bills list 2001 of the embodiment.

[Explanation of symbols]

Reference numeral 101: electronic bill center, 301: electronic bill center server, 307: center contract integration process, 308: automatic contract integration process, 309: center bill distribution process, 310: center bill transfer process, 701: contract information DB, 1101: distribution Preparation DB, 1303: Contract integration rule, 1801: Bill DB

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Haruka Someya             1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture             Ceremony company Hitachi Systems Development Laboratory (72) Inventor Takeuchi ▲ Country ▼ people             890 Kashimada, Sachi-ku, Kawasaki City, Kanagawa Stock             Hitachi, Ltd. Financial Systems Division

Claims (15)

[Claims] 1. A plurality of pieces of transaction information accompanied by settlement of funds between a buyer and a seller are received and stored in a storage means, and transaction information in which the buyer is the same and the seller is the same is extracted from the transaction information. An electronic payment intermediary method is characterized in that one transaction information is created in which a new payment amount is a sum of respective payment amounts for a plurality of transaction information selected from the extracted transaction information. 2. The electronic device according to claim 1, wherein the extracted transaction information is presented to a seller side, and one transaction information is created from a plurality of the transaction information selected by the seller side. Payment intermediary method. 3. The electronic settlement intermediary method according to claim 1, wherein a rule stored in a storage means is applied to the extracted transaction information to select the plurality of transaction information. 4. The settlement date of the one transaction information to be created is the latest settlement date of the settlement dates of the respective fund settlements for the plurality of selected transaction information. Electronic payment mediation method described. 5. An electronic bill having the payer of the buyer, the payee of the seller, and a bill settlement date as a bill settlement date for the one created transaction information is stored in a storage means. The electronic payment intermediary method according to claim 1, characterized in that 6. A transfer processing method for an electronic bill based on electronic bill information, which is stored in a storage means and includes a sender's identifier, a payee's identifier, a first settlement amount, and a settlement date. New electronic note information transmitted to the payee's computing environment and including the sender's identifier, the designated new payee's identifier, the designated second settlement amount, and the settlement date according to instructions from the computing environment. Is generated and stored in a storage unit, and the first settlement amount is updated by an amount obtained by subtracting the second settlement amount from the first settlement amount. 7. Depending on the calculation environment of the fund settlement intermediary, a plurality of transaction information items involving the settlement of funds between the buyer and the seller are received and stored in the storage means, and the buyers match in the transaction information. The transaction information matching the seller is extracted, and one transaction information is created in which the total settlement amount of each of the plurality of transaction information selected from the extracted transaction information is a new settlement amount. Notifying the computing environment of the first financial institution with which the seller trades the first account number of the buyer, the second account number of the second financial institution with which the seller trades, and the settlement amount of the one transaction information. The transfer of funds is requested, and the transaction information is settled from the account of the first account number to the account of the second account number of the second financial institution according to the calculation environment of the first financial institution. Electricity characterized by moving money Settlement mediation method. 8. An electronic bill having the payer of the buyer, the payee of the seller, and a bill settlement date as a bill settlement date for the created transaction information, and stores the bill in a storage means. 8. The electronic settlement intermediary method according to claim 7, wherein the settlement amount of the one transaction information is moved on a bill settlement date. 9. A means for receiving a plurality of pieces of transaction information involving fund settlement between a buyer and a seller and holding the transaction information in a storage means, and transaction information in which the buyer and the seller are the same among the transaction information. A plurality of transaction information selected from the extracted transaction information, and a unit for creating one transaction information having a new settlement amount as a sum of settlement amounts of the plurality of transaction information selected from the extracted transaction information. Electronic payment intermediary device. 10. A means for presenting the extracted transaction information to a seller side, wherein the means for producing creates one transaction information from a plurality of the transaction information selected by the seller side. The electronic payment intermediary device according to claim 9. 11. The electronic settlement intermediary apparatus according to claim 9, further comprising means for applying a rule stored in a storage means to the extracted transaction information to select the plurality of transaction information. 12. A means for creating an electronic bill having the payer of the buyer, the payee of the seller, and a bill settlement date as a bill settlement date for the created transaction information and storing the bill in a storage unit. The electronic payment intermediary device according to claim 9, further comprising: 13. A sender's identifier, a recipient's identifier, a first
Storage means for storing electronic bill information including the settlement amount and settlement date, means for transmitting the electronic bill information to the recipient's computing environment, and the identifier of the sender, designated according to instructions from the computing environment. Means for creating and storing in the storage means a new electronic bill including the new payee identifier, the designated second settlement amount and the settlement date; and the second settlement based on the first settlement amount. An electronic settlement intermediary device, characterized in that the first settlement amount is updated by an amount obtained by subtracting the amount. 14. A means provided in a calculation environment of a fund settlement intermediary institution, for receiving a plurality of pieces of transaction information involving a settlement of funds between a buyer and a seller and storing the transaction information in a storage means, and a buyer among the transaction information. Means for extracting transaction information in which the same and sellers match, and one transaction information in which the sum of the respective settlement amounts of the plurality of transaction information selected from the extracted transaction information is a new settlement amount. And a first account number of the buyer, a second account number of a second financial institution with which the seller transacts, and the one transaction with the computing environment of the first financial institution with which the buyer transacts. A means for notifying the settlement amount of information and requesting the transfer of funds, and a means provided in the computing environment of the first financial institution, and from the account of the first account number to the second of the second financial institution. To the account of the account number of the one transaction information Electronic settlement intermediation apparatus characterized by a means for moving the already amount. 15. A means for creating an electronic bill with the payer of the buyer, the payee of the seller, and a bill settlement date as a bill settlement date for the created transaction information and storing the bill in a storage unit. 15. The electronic payment intermediary device according to claim 14, wherein the means for performing the transfer moves the payment amount of the one transaction information on the bill payment date.