+

WO2003067489A1 - Systeme de support d'echanges commerciaux - Google Patents

Systeme de support d'echanges commerciaux Download PDF

Info

Publication number
WO2003067489A1
WO2003067489A1 PCT/JP2003/001313 JP0301313W WO03067489A1 WO 2003067489 A1 WO2003067489 A1 WO 2003067489A1 JP 0301313 W JP0301313 W JP 0301313W WO 03067489 A1 WO03067489 A1 WO 03067489A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
buyer
seller
unit
delivery data
Prior art date
Application number
PCT/JP2003/001313
Other languages
English (en)
Japanese (ja)
Inventor
Kazuo Masuda
Masafumi Manno
Masayo Saegusa
Original Assignee
The Financialeyes Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by The Financialeyes Co., Ltd. filed Critical The Financialeyes Co., Ltd.
Priority to AU2003244359A priority Critical patent/AU2003244359A1/en
Publication of WO2003067489A1 publication Critical patent/WO2003067489A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/08—Auctions

Definitions

  • This effort relates to a transaction support server, a transaction support system, a transaction support method, and a program.
  • the present invention relates to a transaction support server, a transaction support system, a transaction support method, and a program for associating seller delivery data with buyer delivery data.
  • Japanese Patent Application Laid-Open No. 2000-91213 discloses a method of performing an erasing process by carrying around the erasing key information generated at the time of issuing the invoice data.
  • a transaction support server for supporting a transaction between a seller and a buyer is provided in a representation format in which the seller processes.
  • Seller's delivery data including product identification information, product quantity, and product unit price
  • buyer's delivery including product identification information, product quantity, and product price expressed in a format used by the buyer for processing
  • a transaction data storage unit that stores information for associating data
  • a seller data reception unit that receives seller delivery data generated by the transaction from the seller terminal, and a buyer that generates the transaction
  • the transaction data storage unit uses the transaction data storage unit, the seller data received by the seller data receiver, and the buyer data received by the buyer data receiver using the transaction data storage unit.
  • the matching unit that associates the data with the data and at least one of the seller's delivery data and the buyer's delivery data
  • an output unit which outputs one of the terminal buyer least.
  • the transaction data storage unit has a conversion table for converting between the seller's expression format and the buyer's expression format, and the matching unit uses the conversion table to convert the delivery data to obtain the seller's data.
  • the delivery data may be associated with the buyer's delivery data.
  • the conversion table describes the product identification information, product quantity, amount, and supplier identification information included in the seller's delivery data, and the product identification information, product quantity, amount, and business partner included in the buyer's delivery data.
  • the identification information is stored in association with the expression form of the identification information, and the matching unit stores the delivery data of the seller whose supplier identification information indicates the buyer and the buyer who determines that the supplier identification information indicates the seller.
  • the conversion table may be used to associate the buyer's delivery data and the seller's delivery data determined to correspond to at least a part of the product identification information, the product quantity, and the price with each other.
  • the transaction data storage unit has a conversion table that stores the product identification information included in the seller's delivery data and the product identification information included in the buyer's delivery data in association with each other.
  • the seller data is received using the conversion table.
  • the unit further includes a detail matching unit for associating the product identification information included in the delivery data received with the product identification information included in the buyer delivery data, and the output unit includes one of the buyer delivery data and the seller delivery data. May be output together with the information indicating that the detailed matching section is associated with the product identification information included in the other.
  • the output unit may transmit the delivery data associated with the matching unit to the buyer in the form of a purchase or hand expression.
  • a mismatch notification unit that notifies at least one of the seller and the buyer of the incompatibility may be further provided.
  • the mismatch notification unit associates the buyer's transaction amount, product identification information, product quantity, delivery date, and product unit price with the seller's transaction amount, product identification information, product quantity, delivery date, and product unit price.
  • the change information receiving section that receives the changed information, and the changed information is transmitted to the buyer and the seller. It may further include a statement conversion unit that converts the seller into the other delivery data, and a change information transmission unit that transmits the changed information converted by the statement conversion unit to the other as update data of the delivery data. If the matching unit cannot find the buyer's delivery data corresponding to the seller's delivery data received by the seller data receiving unit within a preset period, the purchase data and hand delivery data corresponding to the seller's delivery data are A mismatch notification unit may be further provided to notify the seller of the absence.
  • a data format storage unit that stores information on the data format when the seller performs the reconciliation process and information on the data format when the buyer performs the reconciliation process; and Based on the seller's delivery data, using the data format storage unit, clearing data for clearing accounts payable corresponding to buyer's delivery data or receivables corresponding to seller's delivery data is settled. It may further include a clearing data generation unit that generates data in each of the seller, purchase, and hand data formats.
  • a payment information receiving unit that receives notification that the buyer has completed payment for the transaction, and the buyer and seller send the reconciliation data generated by the reconciliation data generation unit on condition that the payment information receiving unit receives notification that the payment has been completed.
  • a reconciliation data transmitting unit for transmitting to the user.
  • a small amount of seller delivery data purchase Using at least one of the above, the payment data generation unit that generates the private / private data corresponding to the delivery data, and the payment data generated by the payment data generation unit together with the payment identification information that specifies the payment and the buyer or buyer A payment data transmission unit for transmitting to the house bank, wherein the transaction data storage unit stores information specifying the delivery data corresponding to the payment data and the payment identification information transmitted by the payment data transmission unit in association with each other.
  • the application data generation unit uses the delivery data corresponding to the payment identification information in the transaction data storage unit.
  • the reconciliation data may be generated.
  • a netting unit that generates netting data that uses at least one of the seller's delivery data and the buyer's delivery data to offset the receivables or payables corresponding to the delivery data between the seller and the buyer, and the netting unit generates the netting data Generate reconciliation data to settle accounts payable corresponding to buyer's delivery data or receivables corresponding to seller's delivery data based on seller's or buyer's delivery data used in the transaction. And an embedded data generation unit.
  • a transaction support system including a seller's business support terminal, a buyer's business support terminal, and a transaction support server that supports transactions between the seller and the buyer
  • the business support terminal has a shipping information storage unit that stores information on shipping of goods as seller delivery data, and a seller transmitting unit that transmits the delivery data stored by the shipping information storage unit to the transaction support server.
  • the business support terminal has an acceptance information storage unit that stores information related to product acceptance as buyer delivery data, and a purchase and hand transmission unit that sends the delivery data stored in the acceptance information storage unit to the transaction support server.
  • the transaction support server provides the seller's delivery including the product identification information, product quantity, and product unit price expressed in a format used by the business support terminal of the seller for processing.
  • Transaction data storage unit that stores information for associating data with buyer delivery data including product identification information, product quantity, and product unit price expressed in a format used by the business support terminal of the buyer for processing.
  • a seller data receiving unit that receives the seller's delivery data generated by the transaction from the seller's business support terminal, and receives the buyer's delivery data generated by the transaction from the buyer's business support terminal Using the buyer data reception unit and the transaction data storage unit, the seller data reception unit receives the seller delivery data and the buyer data A matching unit that associates the buyer's delivery data received by the receiving unit, and at least one of the seller's delivery data and the buyer's delivery data associated with the matching unit with the business support terminal of at least one of the seller and the buyer.
  • a transaction support method in which a computer supports a transaction between a seller and a buyer.
  • Managing a transaction data store that stores information; and Receiving the delivery data from the seller's terminal, receiving the buyer's delivery data generated due to the computer power transaction from the buyer's terminal, and receiving the delivery data from the buyer's terminal using the transaction data storage unit.
  • Associating the seller's delivery data with the buyer's received delivery data; and the computer converts at least one of the associated seller's delivery data and buyer's delivery data into at least one terminal of the seller and the buyer. And outputting to the
  • a computer program for supporting a transaction between a seller and a buyer includes a seller's information including a product identification information, a product quantity, and a product unit price expressed in a format used by the seller for processing.
  • a transaction data storage module for storing information for associating the delivery data with the buyer's delivery data including the product identification information, the product quantity, and the product unit price expressed in a format used by the buyer for processing;
  • Data receiving module that receives from the seller terminal the delivery data of the seller caused by the transaction, and the purchase that receives the delivery data of the buyer that is caused by the transaction from the terminal of the buyer!
  • the seller data receiving module receives the seller delivery data and the buyer data receiving module receives the buyer delivery data. It has a matching module to be associated with, and an output module that outputs at least one of the seller's delivery data and the buyer's delivery data associated with the matching module to at least one terminal of the seller and the buyer.
  • Figure 1 is a schematic diagram of the entire transaction support system.
  • FIG. 2 is a functional block diagram of the transaction support server 10.
  • FIG. 3 is a diagram showing an example of the bill data received by the seller data receiving unit 104.
  • FIG. 4 is a diagram showing an example of the payment schedule data received by the buyer data receiving unit 108.
  • FIG. 5 is a diagram showing an example of a table stored in the transaction data storage unit 110.
  • FIG. 6 is a diagram showing an example of a table stored in the conversion table 112.
  • FIG. 7 is a diagram showing another example of the table stored in the conversion table 112.
  • FIG. 8 is a diagram showing an example of delivery data transmitted from the output unit 134 to the business support terminal 50 of the buyer as a part of the bill data.
  • FIG. 9 is a diagram illustrating an example of information notified by the mismatch notification unit 1338 to the buyer.
  • FIG. 10 is a diagram illustrating an example of the change information transmitted by the change information transmitting unit 144.
  • FIG. 11 is a diagram illustrating an example of payment data transmitted by the payment data transmitting unit 148.
  • FIG. 12 is a diagram showing an example of netting data generated by the netting unit 150. As shown in FIG.
  • FIG. 13 is a diagram illustrating an example of a table stored in the data format storage unit 156.
  • FIG. 14 is a flowchart in which the transaction support server 10 outputs delivery data in association with each other.
  • FIG. 15 is a flowchart in which the transaction support server 10 performs a netting process and a clearing process.
  • FIG. 16 is a block diagram showing a hardware configuration of the transaction support server 10.
  • BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.
  • Figure 1 shows the outline of the whole transaction support system.
  • the transaction support system includes a transaction support server 10, a business support terminal 30 for sellers, and a business support terminal 50 for buyers.
  • the transaction support server 10 connects, for example, the seller's business support terminal 30 and the buyer's business support terminal 50 via a network.
  • the transaction support system is composed of, for example, a network system using WWW technology.
  • the transaction support system is an example of the transaction support system according to the present invention.
  • the transaction support server 10 supports transactions between sellers and buyers. That is, the transaction support server 10 obtains the delivery data from the business support terminal 30 of the seller and the business support terminal 50 of the buyer, and transfers the delivery data held by the seller and the delivery data held by the buyer. Correspond.
  • the delivery data in this case is various information related to the transaction, including, for example, shipping data created by the seller or accounting data based on the shipping data, or acceptance data created by the buyer or accounting data based on the acceptance data. .
  • the transaction support server 10 associates the delivery data obtained from the business support terminal 30 of the seller with the delivery data obtained from the business support terminal 50 of the buyer, and sends the data to each business support terminal. In other words, it facilitates billing, reconciliation, reconciliation, and negotiations in the event of data mismatch between sellers and buyers.
  • the transaction support server 10 is an example of the transaction support server according to the present invention.
  • the seller's business support terminal 30 supports the seller's business. That is, the seller's business support terminal 30 receives order data, checks inventory, creates shipping data, and creates accounting data such as accounts receivable.
  • the seller's business support terminal 30 is a shipping information storage unit that stores information on the shipment of goods as seller's delivery data, and a seller transmission that sends the delivery data stored in the shipping information storage unit to the transaction support server 10. Unit.
  • the seller's business support terminal 30 also has a receivables management unit that manages receivables and receivables data generated by the shipment of goods, and creates and issues invoice data and processes related to payment for the invoice data. And a requesting unit.
  • the receivables management unit and the billing unit may be physically different systems.
  • the buyer's business support terminal 50 supports the buyer's business. That is, the business support terminal 50 of the buyer performs transmission of order data, creation of acceptance data, creation of accounting data such as accounts payable, and the like.
  • the buyer's business support terminal 50 buys information on product acceptance. It includes an acceptance information storage unit that stores the delivery data as a handover data, and a buyer transmission unit that sends the delivery data stored in the acceptance information storage unit to the transaction support server 10.
  • the buyer's business support terminal 50 further includes an accounts payable management unit that manages accounts payable that arises from the acceptance of goods and a payment unit that pays the goods to the seller.
  • FIG. 2 shows functional blocks of the transaction support server 10.
  • the transaction support server 10 includes a seller data reception unit 104, a buyer data reception unit 108, and a transaction data storage unit 11
  • matching section 120 statement confirmation section 130, output section 134, mismatch notification section 138, change information receiving section 142, change information transmitting section 144, and payment approval section 14.
  • the seller data receiving unit 104 receives the seller's delivery data generated due to the transaction from the seller's business support terminal 30 together with the invoice data for the transaction, and outputs the data to the matching unit 120. That is, the seller data receiving unit 104 receives the seller's delivery data including a plurality of data items generated due to the transaction from the seller's business support terminal 30, and outputs the data to the matching unit 120.
  • the seller data receiving unit 104 receives, for example, bill data corresponding to a plurality of delivery data created by the business support terminal 30 of the seller, together with the delivery data.
  • the delivery data received by the seller data receiving unit 104 includes the product identification information, the product quantity, the delivery date, and the product unit price.
  • the invoice data is data for requesting the buyer to pay for the price corresponding to the delivery data, and includes, for example, a billing amount, a payment date, and the like.
  • FIG. 3 shows an example of bill data received by the seller data receiving unit 104.
  • the seller data receiving unit 104 receives, as bill data, bill specification information (hereinafter, bill data ID), bill amount, and a plurality of delivery data.
  • the seller data receiving unit 104 includes, as delivery data, a plurality of data item names (transaction ID, shipping ID, shipping date, business partner, product ID, quantity, unit price, amount, shipping destination) and these data items.
  • Receive shipment data including data corresponding to (AB 000135, 01NOV0031, 2001/1 January 01, Company B, SO 005, 12 dozen, 60,000 yen, 720,000 yen, Company B X factory) .
  • the data is expressed in an expression format when the seller's business support terminal 30 processes the data.
  • the expression format is a data format that enables a business support terminal or a human to recognize a predetermined meaning (such as product identification information and a product quantity).
  • a predetermined meaning such as product identification information and a product quantity.
  • an object having a predetermined meaning is defined in advance. This is a format for displaying characters, numbers, and the like in an order and combination.
  • the buyer data receiving unit 108 receives the buyer's delivery data generated due to the transaction from the business support terminal 50 of the buyer together with the scheduled payment data corresponding to the delivery data, and outputs the data to the matching unit 120. That is, the buyer data receiving unit 104 receives, from the business support terminal 50 of the buyer, buyer delivery data including a plurality of data items generated due to the transaction, and outputs the data to the matching unit 120.
  • the buyer data receiving unit 108 receives, for example, payment schedule data created by the buyer's business support terminal 30 and corresponding to a plurality of delivery data.
  • the delivery data received by the buyer data receiving unit 108 includes product identification information, product quantity, and product unit price.
  • FIG. 4 shows an example of the payment schedule data received by the buyer data receiving unit 108.
  • the buyer data receiving unit 108 receives scheduled payment data identification information (hereinafter, scheduled payment data ID), scheduled payment amount, and a plurality of delivery data as scheduled payment data.
  • the buyer data receiving unit 108 sends a plurality of data item names (transaction number, acceptance ID, acceptance date, shipping source, product ID, quantity, unit price, total price, and a person in charge of acceptance) as delivery data.
  • Inspection data including the data corresponding to the data items (AB 000135, HI 3—0013725, 05 NOVO 1, Company A, abc—115, 144, 5,000 yen, 720,000 yen, ⁇ ) Receive.
  • the data items and data in this case are expressed in an expression format when the business operation terminal 50 of the buyer processes the data. That is, at least a part of the delivery data received by the buyer data receiving unit 108 may have a different expression form from the delivery data received by the seller data receiving unit 104.
  • the transaction data storage unit 110 stores the seller's delivery data expressed in the expression format used by the seller for processing and buying! In addition, information for associating the purchase data expressed in the expression format when the hand is processed with the hand delivery data is stored. That is, the transaction data storage unit 110 stores the merchandise identification information expressed in the seller's expression format, the seller's delivery data including the item quantity and the unit price, the merchandise identification information expressed in the buyer's expression format, Stores information for associating product quantity and buyer delivery data including product unit price. In the present embodiment, the transaction data storage unit 110 stores, as the information for association, transaction identification information that allows both the seller and the buyer to uniquely identify the transaction (for example,
  • the transaction identification information is “AB 0 0 1 3 5” corresponding to the “transaction ID” item received by the seller data receiving unit 104 in FIG. 3, and the buyer data receiving unit 1 108 in FIG. Is "AB 0 0 0 1 3 5" corresponding to the "transaction number” item received.
  • FIG. 5 shows an example of a table stored in the transaction data storage unit 110.
  • the transaction data storage unit 110 stores information for extracting the transaction identification information in association with the seller / buyer. That is, the transaction data storage unit 110 stores the item names of the transaction identification information in association with the expression form of the seller and the buyer. For example, the transaction data storage unit 110 stores “transaction ID” in association with the seller “company A”. In this case, the transaction identification information can be extracted by reading the data of item name “Transaction ID” from the delivery data received from “Company”.
  • the transaction data storage unit 110 has a conversion table 112.
  • the conversion table 1 1 2 stores information for converting between the seller's expression form and the buyer's expression form.
  • the conversion table 1 1 2 contains the product identification information, the product quantity, the amount, the delivery date, the delivery date, and the customer identification information included in the seller's delivery data, the product identification information included in the buyer's delivery data, Store the quantity of goods, amount of money, delivery date, and representation format of tori I destination identification information in association with each other.
  • the conversion table 1 1 2 contains the merchandise identification information, merchandise quantity, price, delivery date, and supplier identification information included in the seller's delivery data, and the merchandise identification information, merchandise quantity, and amount included in the buyer's delivery data.
  • the delivery date, and the supplier identification information itself may be stored in association with each other.
  • FIG. 6 shows an example of a table stored in the conversion table 112.
  • the conversion table 1 1 2 contains the data item names (shipping ID, shipping date, supplier, merchandise ID, quantity, unit price, amount, shipping destination) of “company” as a seller and “ The data item names of “Company B” (inspection ID, acceptance date, shipping source, product ID, quantity, unit price, total amount, and the person in charge of acceptance) are stored in association with each other.
  • the conversion table 1 1 2 Using the data item names, the product identification information, product quantity, delivery date (shipment date and acceptance date), amount, and the like included in the delivery data of the seller and buyer are associated with each other.
  • FIG. 7 shows another example of the table stored in the conversion table 112.
  • FIG. 7A shows an example of a table in which the conversion table 112 stores the date expression format.
  • the conversion table 111 stores the date expression format in association with the seller or the buyer. In this case, even if the method of displaying the date differs between the seller and the buyer, they can be mutually converted by using the conversion table 112.
  • FIG. 7 (B) shows an example of a table in which the conversion table 112 stores product identification information.
  • the conversion table 112 stores the merchandise identification information (ie, merchandise ID) expressed in the seller's expression format and the merchandise identification information expressed in the buyer's expression format in association with each other.
  • the conversion table 112 further stores the transaction unit of the product in association with the seller or the buyer. In this case, even if the transaction unit of the goods differs between the seller and the buyer, displaying the transaction unit of both the seller and the buyer will not make the seller or the buyer misunderstand. It is also possible to convert product quantities to each other.
  • FIG. 7 (C) shows an example of a table in which the conversion table 112 stores the expression format of the product unit price or the price.
  • the conversion table 1 1 2 stores the currency unit when expressing the unit price or the amount of money in association with the seller or the buyer.
  • the statement matching unit 122 may obtain the exchange rate of the specified currency unit using the conversion table 112, and may convert the exchange rate to a preset currency unit.
  • the matching section 120 receives the seller's billing data from the seller data receiving section 104, and receives the buyer's delivery data from the buyer data receiving section 108. Then, the delivery data of the seller and the delivery data of the buyer are associated with each other and output to the statement confirmation unit 130. That is, the matching unit 120 uses the transaction data storage unit 110 to store the sales data received by the seller data receiving unit 104. The hand delivery data is associated with the buyer delivery data received by the buyer data receiving unit 108. At that time, the matching unit 120 stores the delivery data of the seller and the delivery data of the buyer in association with each other.
  • the matching unit 120 stores the delivery data of the seller and the delivery data of the buyer in association with the bill data identification information (hereinafter, bill data ID). Further, matching section 120 associates the delivery data of the seller with the delivery data of the buyer using the transaction identification information. If it is not possible to match the seller's delivery data with the buyer's delivery data within a preset period, the matching unit 120 informs the non-coincidence notification unit 1 via the statement confirmation unit 130 that the association cannot be made. 3 Output to 8.
  • bill data ID bill data identification information
  • the matching section 120 has a statement matching section 122, a statement conversion section 124, and a payment data generation section 126.
  • the detail matching unit 122 associates a plurality of data items included in the delivery data. That is, the detail matching unit 122 associates a plurality of data items (that is, detail items) included in the corresponding seller's delivery data and buyer's delivery data.
  • the detail matching unit 1 2 2 uses the conversion table 1 1 2 to associate the product identification information included in the seller's delivery data with the product identification information included in the buyer's delivery data, and confirm the statement. Output to section 130.
  • the item matching unit 1 2 2 can also calculate the “shipping ID” and “acceptance ID”, “shipping date” and “acceptance date”, “customer” and “shipping source”, and the product quantity in the seller's expression format. And the total price may be associated with the product quantity and total price in the buyer's expression format, respectively.
  • the detail conversion unit 124 uses the conversion table 112 to convert the information included in the delivery data of one of the sellers and buyers into the other representation format. For example, when the seller corrects the amount of the delivery data or the like, the detail conversion unit 124 converts the changed information into seller delivery data and outputs the changed information to the change information transmission unit 144.
  • the payment data generation unit 126 receives the scheduled data ID (or invoice data ID, shipping ID, acceptance ID) from the payment approval unit 144, and the seller or the buyer corresponding to the scheduled data ID. Using the delivery data, payment data corresponding to the delivery data is generated and output to the payment data transmitting unit 148. At that time, the payment data generating unit 126 issues payment identification information for specifying payment by the payment data, and Output to the payment data transmitting section 148 together with the data. That is, the payment data generation unit 126 uses at least one of the seller's delivery data and the buyer's delivery data associated with the matching unit 120 to generate payment data corresponding to the delivery data.
  • the payment data is data for performing payment processing of the price corresponding to the delivery data.
  • the payment data of the product corresponding to the acceptance data is transmitted to the business support terminal 5 of the buyer. 0 or data for the buyer's bank system to process payment.
  • payment data may include payee identification information identifying the payee (eg, the seller's account number), payer identification information identifying the payer (eg, the buyer's account number), payment amount, and identifying the payment.
  • Payment identification information (hereinafter referred to as payment ID).
  • the payment data generation unit 126 further outputs the payment ID to the transaction data storage unit 110. In this case, when receiving the payment ID from the payment data generation unit 126, the transaction data storage unit 110 stores the delivery data corresponding to the payment ID in association with the payment ID.
  • the transaction data storage unit 110 stores the information for specifying the delivery data corresponding to the payment data and the payment ID transmitted by the payment data transmission unit 148 in association with each other. Further, upon receiving the netting ID from the payment approval unit 146, the payment data generation unit 126 outputs the netting data corresponding to the netting ID to the payment data transmission unit 148 as payment data.
  • the payment ID at that time is, for example, a netting ID. That is, the transaction data storage unit 110 stores the netting ID and information specifying the delivery data corresponding to the netting ID in association with each other.
  • the detail confirmation section 130 is composed of the price, product identification information, product quantity, delivery date, and product price included in the delivery data of the seller associated with the matching section 120, and the price included in the delivery data of the buyer. It is determined whether or not the contents correspond to the product identification information, the product quantity, the delivery date, and the product unit price. That is, upon receiving the seller's delivery data and the buyer's delivery data associated with each other from the matching unit 120, the statement confirmation unit 130 receives the amount of money, product identification information, product quantity, delivery date, Then, it is determined whether or not the unit prices correspond to each other, and if it is determined that they correspond, the corresponding delivery data of the seller and delivery data of the buyer are output to the output unit 134.
  • the detailed confirmation unit 130 outputs the associated delivery data of the seller and delivery data of the buyer to the mismatch notification unit 1380.
  • the amount is the place It is the total amount in a fixed transaction.
  • the delivery date is the date on which the product was delivered, for example, the date of shipment divided by the date of acceptance.
  • the statement confirmation unit 130 may determine whether the other data items match. That is, the statement confirmation unit 130 determines whether the data items specified in advance match each other. Further, with respect to the bow I destination identification information, the statement confirmation unit 130 determines whether or not the vendor identification information included in the seller's delivery data indicates the buyer who transmitted the corresponding delivery data.
  • the statement confirmation unit 130 determines whether or not the supplier identification information included in the buyer's delivery data indicates the seller who transmitted the corresponding delivery data.
  • the output unit 134 receives the seller's business support terminal 30 and the buyer's business support terminal 50 at least one of them. Send. That is, the output unit 134 outputs at least one of the seller's delivery data and the buyer's delivery data associated with the matching unit 120 to at least one terminal of the seller and the buyer.
  • the output unit 13 4 indicates that the item matching information included in one of the buyer's delivery data and the seller's delivery data is associated with the product identification information included in the other. Output with information.
  • Output unit 134 Outputs the delivery data together with the information indicating the correspondence, so that the seller or the buyer can perform the matching process using the corresponding delivery data between the seller and the buyer.
  • the output unit 134 outputs, together with the bill data, the delivery data of a plurality of sellers corresponding to the bill data and the buyer's delivery data corresponding to the seller's delivery data.
  • the delivery data of the seller can be used as detailed data relating to the invoice data.
  • the output unit 134 transmits the delivery data associated with the matching unit 122 to the buyer in a buyer's expression format. That is, the output unit 134 converts the delivery data of the seller associated with the matching unit 122 into an expression format of the buyer, and transmits the converted data to the business support terminal 50 of the buyer in association with the delivery data of the buyer. .
  • the buyer's business support terminal 50 displays the corresponding seller's delivery data and the buyer's delivery data in the representation format of the business support terminal.
  • the output unit 1 3 4 sends the delivery data associated with the matching unit 1 2 2 to the seller in the seller's expression format.
  • the output unit 134 associates the seller's delivery data with the buyer's delivery data, and further converts the data item name into a buyer's expression format and sends it. That is, the output unit 134 transmits the seller's delivery data and the buyer's delivery data in association with the buyer's data item name.
  • the output ⁇ [34] may transmit the bill data and the delivery data corresponding to the bill data at different timings. For example, the output unit 134 first transmits the bill data to the business support terminal 50 of the buyer. Thereafter, when the buyer requests the detailed data of the bill data, the output unit 134 transmits the delivery data corresponding to the bill data as clear data.
  • the discrepancy notification unit 1338 Upon receiving the delivery data from the statement confirmation unit 130, the discrepancy notification unit 1338 informs the seller's business support terminal 30 and the buyer's business support terminal that the seller's delivery data does not correspond to the buyer's delivery data. Send to at least one of 50. In other words, the discrepancy notification unit 1338 indicates that if the statement confirmation unit 130 does not correspond to at least one of the transaction amount, product identification information, product quantity, delivery date, and product unit price, the seller will not respond. And notify at least one of the buyers.
  • the mismatch notification unit 1 3 8 associates the buyer's transaction amount, product identification information, product quantity, delivery date, and product unit price with the seller's transaction amount, product identification information, product quantity, delivery date, and product unit price.
  • the inconsistency notification unit 1 3 8 includes the buyer's transaction amount, product identification information, item quantity, delivery date, and unit price, and the corresponding seller's transaction amount, item identification information, item quantity, delivery date, At least one of the business support terminal 30 of the seller and the business support terminal 50 of the buyer is transmitted to one side so as to display the and the product unit price side by side.
  • FIG. 9 shows an example of information notified to the buyer by the mismatch notification unit 1388.
  • the inconsistency notifying section 1338 associates the delivery data of the seller with the plurality of data items included in the delivery data of the buyer and transmits the data items to the business support terminal 50 of the buyer.
  • the mismatch notification section 1 3 8 highlights the data items that do not match (in this example, “total amount”). It is desirable to transmit data to be displayed on the business support terminal 50 of the buyer as described above.
  • the inconsistency notifying unit 1338 be converted so that it can be displayed in the expression format of the hand and the hand, and then transmitted.
  • the change information receiving unit 142 receives the change information of the delivery data from the business support terminal 30 of the seller or the business support terminal 50 of the buyer, and outputs it to the detail conversion unit 124. That is, when one of the buyer and the seller has changed the information included in the delivery data in response to the notification of the mismatch notification unit 138, the change information receiving unit 144 receives the changed information. .
  • the detail conversion unit 124 converts the change information into the other delivery data of the seller and the buyer, and changes the change information. Output to transmitters 1 4 4.
  • the change information transmitting unit 144 Upon receiving the change information from the detail conversion unit 124, the change information transmitting unit 144 receives the received change information as update data of the delivery data, and transmits the change information to the business support terminal 30 of the seller and the business support terminal 50 of the buyer. Send to at least one. For example, when one of the seller and the buyer changes the delivery data, the change information transmitting unit 144 transmits the change information generated by the change to the other of the seller and the buyer as update data.
  • FIG. 10 shows an example of the change information transmitted by the change information transmitting section 144.
  • the change information transmitting section 144 converts the delivery data changed by the seller into the buyer's expression format and transmits the converted data to the business support terminal 50 of the buyer as update data.
  • the business support terminal 50 of the buyer can read the received update data and update the delivery data.
  • the payment approval unit 146 receives from the business support terminal 50 of the buyer that the payment for the invoice data is approved, and outputs it to the payment data generation unit 126.
  • the payment approval unit 144 may receive the bill data ID as information indicating that the payment corresponding to the bill data is approved.
  • the payment approver unit 146 sends the information (acceptance ID, etc.) identifying the delivery data to approve the payment to the effect that the payment is approved. May be received.
  • the payment approval unit 144 receives the payment data ID of the payment data corresponding to the invoice data as information indicating that the payment is approved.
  • the payment approval section 1 4 6 Receiving the approval of the payment, and outputs it to the payment data generation unit 126.
  • the payment data transmitting unit 148 Upon receiving the payment data from the payment data generating unit 126, the payment data transmitting unit 148 transmits the payment data and the payment ID to the business support terminal 50 of the buyer or the banking system of the buyer. That is, the payment data transmitting unit 148 transmits the payment data generated by the payment data generating unit 126 together with the payment ID specifying the payment to the buyer or the bank of the buyer.
  • the payment ID in this case may be the same as the expected payment data ID.
  • FIG. 11 shows an example of payment data transmitted by the payment data transmitting unit 148.
  • FIG. 11A shows an example of the payment data transmitted by the payment data transmitting section 148 to the buyer.
  • the payment data transmitting unit 148 uses the “transfer person”, “transfer destination”, “payment ID”, “amount”, and ⁇ ⁇ “date” as payment data as the buyer's business support terminal 50 Send to
  • the payment data transmitting unit 148 transmits payment data that summarizes obligations corresponding to a plurality of delivery data.
  • FIG. 11 (B) shows an example of the payment data transmitted by the payment data transmitting section 148 to the bank system.
  • the payment data transmitting unit 148 transmits “account name”, “transferor”, “netting IDJ”, “amount”, and “date” as payment data to the bank system.
  • the payment data is data for instructing payment for the remaining debt amount when the receivables and debts between the seller and the buyer are offset.
  • the netting unit 150 refers to the delivery data stored in the matching unit 120, generates netting data for offsetting the receivable or debt corresponding to the delivery data between the seller and the buyer, and specifies the netting data.
  • the information is output to the seller's business support terminal 30, the buyer's business support terminal 50, and the payment data generation unit 126 together with the netting ID to be set. That is, the netting unit 150 uses at least one of the seller's delivery data and the buyer's delivery data to generate netting data that offsets the receivable or debt corresponding to the seller's and buyer's delivery data. For example, the netting unit 150 generates netting data using delivery data corresponding to the receivables and payables having the same settlement date.
  • the netting unit 150 may use the delivery data corresponding to the receivables and payables with different settlement dates to generate netting data including interest generated due to the difference in settlement dates. It is desirable that the netting section 150 generates netting data in the expression format of the destination. In this case, the seller or buyer's business support terminal that has received the netting data displays the netting data together with the delivery data, and determines whether or not to permit the netting. When permitting the netting, the business support terminal of the seller or the buyer transmits to the payment approval unit 146 the approval of the settlement using the netting data together with the netting ID.
  • FIG. 12 shows an example of netting data generated by the netting unit 150.
  • the netting unit 150 creates a list in which the receivables and the payables are associated with each other for the unsettled transaction identification information (that is, the transaction ID) of the two parties having a business relationship. Then, netting data for performing the offsetting processing by combining the plurality of receivables and payables is generated. The netting unit 150 transmits the remaining amount of the credit and the amount of the debt after the offset processing to the two parties in association with the netting ID specifying the netting processing.
  • the deposit information receiving unit 154 receives the information that the buyer has completed the payment for the transaction (ie, the deposit information) and outputs it to the application data generating unit 158.
  • the deposit information receiving unit 154 may receive the deposit information from the financial institution, the business support terminal 30 of the seller, or the business support terminal 50 of the buyer.
  • the payment information receiving unit 154 receives a notification that the buyer has paid using the payment data, together with the corresponding payment ID.
  • the deposit information receiving unit 154 receives the deposit information for the service after the offset of the receivables and debts by the netting unit 150 together with the netting ID corresponding to the netting, and the application data generating unit 158 Output to
  • the data format storage unit 156 stores information on the data format when the seller's business support terminal 30 performs the reconciliation process after payment and the data when the buyer's business support terminal 50 performs the reconciliation process after payment. Stores information about the format. For example, when the seller's business support terminal 30 uses data created in XML for the receivable clearing process, the data format storage unit 156 relates to the XML tag as information on the data format. Stores information.
  • FIG. 13 shows an example of a table stored in the data format storage section 156.
  • the data format storage unit 156 stores the data format in association with each company.
  • the data format storage unit 156 corresponds to the company “Company A” "X system format", which is the data format when the business support terminal performs accounting processing.
  • the application data generation unit 158 Upon receiving the payment ID from the payment information receiving unit 154, the application data generation unit 158 converts the application data in the data format of the corresponding output destination based on the delivery data corresponding to the payment ID. Generate it and output it to the clearing data transmitter 16. That is, the reconciliation data generation unit 158 uses the reconciliation data in the data format storage unit 156 based on the delivery data in the matching unit 120 corresponding to the payment information. Generate data. For example, the clearing data generation unit 158 specifies the delivery data corresponding to the received payment ID using the transaction data storage unit 110, and generates clearing data using the specified delivery data.
  • the reconciliation data generation unit 158 generates, as reconciliation data, data for clearing the seller's receivables and the buyer's accounts receivable corresponding to the delivery data associated with the matching unit 120. .
  • the clearing data generator 158 When receiving the payment ID (netting ID in this example) corresponding to the netting data, the clearing data generator 158 generates clearing data for the receivables and payables corresponding to the netting ID. Output to the clearing data transmission section 16 2.
  • the clearing data generation unit 158 extracts the transaction ID corresponding to the received netting ID from the matching unit 120, and generates clearing data using the delivery data corresponding to the extracted transaction ID. .
  • the application data transmitting unit 162 Upon receiving the application data from the application data generation unit 158, the application data transmitting unit 162 transmits the application data to the business support terminal 30 of the seller and the business support terminal 50 of the buyer.
  • the clearing data transmitting unit 162 uses the clearing data generated by the clearing data generating unit 158 on the condition that the payment information receiving unit 154 has received the payment completion for the transaction.
  • the reconciliation data is in a data format corresponding to each of the business support terminals, so that the business support terminal receiving the reconciliation data can easily perform the reconciliation processing.
  • FIG. 14 shows a flow in which the transaction support server 10 outputs delivery data in association with each other.
  • the buyer's business support terminal 50 sends the order data to the seller's business support terminal 30
  • the seller's business support terminal 30 creates shipping data (ie, seller's delivery data) corresponding to the order data. And ship the ordered products.
  • Business support end of buyer End 50 upon receiving the goods, creates acceptance data for the goods received (ie, buyer delivery data).
  • the seller data receiving unit 104 of the transaction support server 10 receives the invoice data including a plurality of shipping data from the seller transmitting unit provided in the seller's business support terminal 30, and the buyer data receiving unit 108 provides the buyer's business support.
  • the payment schedule data including the plurality of acceptance data is received from the buyer transmission unit provided in the terminal 50, and each is output to the matching unit 120 (S100).
  • the matching unit 120 refers to the transaction data storage unit 110 and associates the seller's shipping data with the buyer's acceptance data using the transaction identification information (S104).
  • the statement matching unit 122 associates the plurality of data items included in the shipping data and the acceptance data with each other, and sends the data to the statement confirmation unit 130.
  • Output (S 1 1 2).
  • the statement confirmation unit 130 confirms whether or not the data items specified in advance are identical from the plurality of data items included in the shipping data and the acceptance data (S114).
  • the statement confirmation unit 130 When it is determined that the specified data items are all the same (S118: Yes), the statement confirmation unit 130 outputs the associated shipping data and acceptance data to the output unit 134. I do.
  • the output unit 134 transmits the associated shipping data and acceptance data together with the bill data to the business support terminal 50 of the buyer, and requests confirmation of the contents (S122).
  • the payables management unit provided in the business support terminal 50 of the buyer displays the corresponding items of the received shipment data and acceptance data side by side, and when the buyer inputs the approval of payment, the transaction support server 10 confirms that the payment is approved.
  • the received inspection data and the shipment data corresponding to the inspection data are transmitted in association with each other, and the shipment data and the inspection data are stored as payment approved data (S130).
  • the matching unit 120 determines whether or not a predetermined time has elapsed, and when the predetermined time has elapsed. (S134: Yes), the process proceeds to the mismatch notification process of S138.
  • the predetermined time has not elapsed (S134: No)
  • the processing of S104 and S108 is repeated.
  • the statement confirmation unit 130 determines that there is a mismatch in the specified data items (S118: No)
  • the associated shipping data and the received The data is output to the mismatch notification section 1338.
  • the inconsistency notifying section 1338 transmits the corresponding shipping data and acceptance data to the seller's business support terminal 30 and the buyer's business support terminal 50 together with information indicating that the contents do not match (S1). 3 8).
  • the seller and buyer check the received shipping data and acceptance data.For example, if the buyer finds an error, the Accounts Payable Dept. provided in the business support terminal 50 of the buyer creates change data. And sends it to the transaction support server 10.
  • the change information receiving unit 144 of the transaction support server 10 Upon receiving the change data from the business support terminal 50, the change information receiving unit 144 of the transaction support server 10 outputs the change data to the account conversion unit 124 (S144).
  • the detail conversion unit 124 converts the received change data into the seller's expression format, and outputs the converted data to the change information transmission unit 144 (S146).
  • the change information transmission unit 144 transmits the change data converted into the seller's expression format to the seller's business support terminal 30 and the buyer's business support terminal 50 (S150).
  • the payment approval unit 1 46 approves payment of the corresponding shipping data and acceptance data. Is stored as processed data (S130).
  • FIG. 15 shows a flow in which the transaction support server 10 performs a netting process and a clearing process.
  • the netting section 150 extracts payment approved data from the shipping data and acceptance data (that is, delivery data) stored in the matching section 120 at a predetermined timing, and associates the extracted data with the seller and the buyer (S2). 0 0).
  • the netting unit 150 sorts the receivables and payables corresponding to the extracted delivery data by associating them with creditors and debtors, and pays off the receivables and payables after the offset processing.
  • the amount and the amount of debt are calculated, and the calculated amount of debt, the amount of receivables, and the netting ID are transmitted as netting data to the creditor or the debtor or the seller or buyer (S210).
  • the creditor and the debtor who have received the netting data transmit the netting ID to the transaction support server 10 as information indicating that the settlement using the netting data is approved
  • the transaction support server 10 approves the payment.
  • the unit 146 receives the netting ID, and outputs it to the payment data generation unit 126 (S215).
  • the payment data generator 1 2 6 uses the remaining receivables and payables after the offset processing corresponding to the netting ID.
  • the payment data including the payment ID (netting ID in this example) is generated and output to the payment data transmitting unit 148 (S220).
  • the payment data transmitting unit 148 transmits the payment data to the debtor's bank system (S225).
  • the debtor's house bank system that has received the payment data pays the debt amount after the offset to the creditor's house bank system, and outputs to the transaction support server 10 that the payment has been completed, together with the payment ID.
  • Receipt information receiving unit 154 receives from the debtor's bank system the payment information indicating that the debt amount after the offset has been remitted along with the payment ID, and outputs it to application data generation unit 158 (S230). ).
  • the clearing data generation unit 158 specifies the delivery data corresponding to the payment ID using the transaction data storage unit 110 (S240).
  • the clearing data generation unit 158 further generates clearing data for clearing the specified delivery data in the data format in the data format storage unit 156 and outputs the clearing data to the clearing data transmitting unit 162 (S 250).
  • the application data transmitting unit 162 transmits the application data to the business support terminal 30 of the seller and the business support terminal 50 of the buyer corresponding to the delivery data (S260).
  • the receivables management unit and the billing unit of the business support terminal 30 of the seller who has received the reconciliation data use the reconciliation data thus received and receivable (receivable data) and receivables corresponding to the shipping data.
  • the accounting data corresponding to the bill is applied.
  • the payables management unit of the business support terminal 50 of the buyer who has received the reconciliation data uses the received reconciliation data to execute the reconciliation process for the receivables (payables data) corresponding to the acceptance data. Do.
  • FIG. 16 is a block diagram showing a hardware configuration of the transaction support server 10.
  • the transaction support server 10 includes a CPU 700, a ROM 702, a RAM 704, and a communication interface 706.
  • the CPU 700 operates based on the programs stored in the ROM 702 and the RAM 704.
  • the communication interface 706 communicates with the outside via a communication network.
  • a hard disk drive 710 as an example of a storage device stores setting information and a program for operating the CPU 700. Or read the program and provide it to CPU 700.
  • the CD-ROM drive 716 reads data or programs from the CD-ROM 718 and provides it to the CPU 700.
  • Communication interface 706 connects to the Internet to send and receive data I believe.
  • the software executed by the CPU 700 is stored in a recording medium such as the flexible disk 714 or the CD-ROM 718 and provided to the user.
  • the software stored on the recording medium may be compressed or uncompressed.
  • the software is installed in the hard disk drive 710 from the recording medium, read out to the RAM 704, and executed by the CPU 704.
  • the software stored and provided on the recording medium has a functional configuration of a seller data receiving module, a buyer data receiving module, a transaction data storage module, and a matching module.
  • the transaction data storage module has a conversion table.
  • the matching module has, as sub-modules, a statement matching module, a statement conversion module, and a payment data generation module. The processing performed by these modules on the computer and performed by the CPU 700 is the same as the function and operation of the corresponding components in the transaction support server 10 according to the present embodiment, and a description thereof will be omitted. .
  • the flexible disk 7 18 or the CD-ROM 7 18 as an example of the recording medium shown in FIG. 16 includes the transaction support server 10 in all the embodiments described in the present application. Some or all functions of the operation can be stored.
  • These programs may be read directly from the recording medium to the RAM and executed, or may be read and executed by the RAM after being installed in the hard disk drive.
  • the program may be stored on a single recording medium or on a plurality of recording media.
  • the modules stored in the recording medium may provide their respective functions in cooperation with the operating system. For example, the function may be requested to the operating system to perform part or all of the function, and the function may be provided based on a response from the operating system.
  • Recording media include flexible disks, CD-ROMs, optical recording media such as DVDs, magnetic recording media such as MDs, magneto-optical recording media such as PDs, tape media, magnetic recording media, and IC cards.
  • a semiconductor memory such as a miniature force can be used.
  • a storage device such as a hard disk or a RAM provided in a server system connected to a dedicated communication network or the Internet may be used as a recording medium, and the program may be provided to the transaction support server 10 via the communication network.
  • the transaction support system of the present embodiment it is possible to easily perform the seller's delivery data, the purchase transaction, and the hand delivery data matching process.
  • the processing of clearing the accounts receivable and payable can be facilitated. For example, even if the buyer pays a part of the invoice issued by the seller, the seller identifies the delivery data corresponding to the payment using the transaction support server 10 and sets the sales The receivables can be cleared.
  • not only can sellers clear accounts receivable but buyers can easily clear accounts payable.
  • by performing the netting process in the trading system it becomes easy to clear a plurality of receivables and payables corresponding to the netting.
  • the delivery data of the seller and the delivery data of the buyer may be associated using other items of the transaction identification information. That is, the matching unit 120 converts a part of a plurality of data items included in the seller's delivery data or the buyer's delivery data by using the conversion table 112 to thereby obtain the seller's delivery data.
  • the delivery data of the buyer may be associated with.
  • the matching unit 120 converts the conversion table 1 between the delivery data of the seller whose supplier identification information indicates the buyer and the delivery data of the buyer who has determined that the supplier identification information indicates the seller. Using 1 and 2, the delivery data of the seller, which is determined to correspond to at least a part of the product identification information, the product quantity, and the transaction amount, and the delivery data of the buyer, are associated with each other.
  • the supplier identification information is This is information that specifies the seller or buyer that is the destination, for example, information that specifies the shipping destination or shipping source, and a business partner code.
  • the seller's delivery data can be obtained without negotiating the transaction identification information between the seller and the buyer in advance. Can be associated with the buyer's delivery data.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système de support d'échanges commerciaux offrant un procédé permettant le règlement flexible des demandes/livraisons en fonction des données commerciales reçues dans des formats de données respectifs de la part de la société propre et d'un partenaire commercial. Les unités (104, 108) de réception de données acquièrent simultanément ou séparément des données de plan de paiement, et une pluralité de données d'expédition/inspection connexes, envoyées respectivement par le vendeur et l'acheteur, et transfèrent ces données à une unité (120) d'appariement. L'unité d'appariement effectue une corrélation entre les éléments conformément à l'information concernant le format des données de chaque partie concernée, qui est stockée dans l'unité (110) de stockage de données commerciales, et les transfère à une unité (130) de vérification de compte, puis transmet les données de paiement converties à l'acheteur ou à une banque de l'acheteur. Le paiement est normalement effectué sous forme d'un règlement net défini en fonction des comptes débiteurs/créditeurs sur lesquels une contrepartie a été versée en avance.
PCT/JP2003/001313 2002-02-07 2003-02-07 Systeme de support d'echanges commerciaux WO2003067489A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003244359A AU2003244359A1 (en) 2002-02-07 2003-02-07 Trading support system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2002031577A JP2003233765A (ja) 2002-02-07 2002-02-07 取引支援サーバ、取引支援システム、取引支援方法、およびプログラム
JP2002-31577 2002-02-07

Publications (1)

Publication Number Publication Date
WO2003067489A1 true WO2003067489A1 (fr) 2003-08-14

Family

ID=27677937

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2003/001313 WO2003067489A1 (fr) 2002-02-07 2003-02-07 Systeme de support d'echanges commerciaux

Country Status (3)

Country Link
JP (1) JP2003233765A (fr)
AU (1) AU2003244359A1 (fr)
WO (1) WO2003067489A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018190168A (ja) * 2017-05-02 2018-11-29 株式会社アール・アンド・エー・シー 照合プログラムおよびデータ照合方法

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006072403A (ja) * 2004-08-31 2006-03-16 Dainippon Printing Co Ltd 金券の請求データ生成システム
JP2006331254A (ja) * 2005-05-30 2006-12-07 Chuo Joho System:Kk 企業間商取引の決済システム
JP4204056B2 (ja) * 2005-07-13 2009-01-07 イーサポートリンク株式会社 連続ファクタリングシステム
JP4305926B2 (ja) * 2005-07-13 2009-07-29 イーサポートリンク株式会社 生鮮ファクタリングシステム
JP2007102457A (ja) * 2005-10-04 2007-04-19 Hitachi Ltd 売掛債権消込管理システム、売掛債権消込管理方法、売掛債権消込管理プログラム
JP4478092B2 (ja) * 2005-10-14 2010-06-09 株式会社日立製作所 ネッティング処理装置、ネッティング処理方法およびネッティング処理プログラム
CN1811814A (zh) * 2006-03-01 2006-08-02 阿里巴巴公司 一种账户充值的方法和系统
JP2008250440A (ja) * 2007-03-29 2008-10-16 Mitsubishi Electric Information Systems Corp ネッティングシステム
JP5089495B2 (ja) * 2008-06-04 2012-12-05 三菱電機株式会社 拠点生産情報連携システム
JP2011018301A (ja) * 2009-07-10 2011-01-27 Hidekatsu Ukuta 銀行口座統合管理システム
KR100960285B1 (ko) * 2009-12-24 2010-06-07 김영기 신용카드 시스템을 응용한 바이어 뱅크 중심의 국제 무역 결제 시스템 및 방법
JP6803741B2 (ja) * 2016-12-16 2020-12-23 株式会社オービック 商品管理単位変換装置、商品管理単位変換方法および商品管理単位変換プログラム
EP3651087A1 (fr) * 2018-11-09 2020-05-13 Phoenix Contact GmbH & Co. KG Dispositif et procédé de conversion des données à partir d'une interface client numérique d'un système réseau informatique
JP7240140B2 (ja) * 2018-11-12 2023-03-15 株式会社オービック 取引データ照合装置、取引データ照合方法および取引データ照合プログラム
JP7075081B2 (ja) * 2018-12-26 2022-05-25 株式会社スマイルワークス 情報処理装置、情報処理方法及びプログラム
JP2021117620A (ja) * 2020-01-23 2021-08-10 株式会社マネーフォワード 情報処理装置、情報処理方法及びプログラム
JP7409984B2 (ja) * 2020-07-17 2024-01-09 株式会社オービック 業務支援装置、業務支援方法、及び業務支援プログラム
JP7556722B2 (ja) 2020-09-18 2024-09-26 株式会社東計電算 取引明細照合システム及び取引明細照合方法
WO2023127116A1 (fr) * 2021-12-28 2023-07-06 ファーストアカウンティング株式会社 Dispositif de traitement de données, procédé de traitement de données et programme

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996012242A1 (fr) * 1994-10-13 1996-04-25 World Trade Centers Association, Inc. Systeme de transactions complet
WO2000048053A2 (fr) * 1999-02-12 2000-08-17 Etime Capital, Inc. Systeme et procede de gestion de transactions commerciales
JP2001028026A (ja) * 1998-07-03 2001-01-30 Bank Of Tokyo-Mitsubishi Ltd 取引支援システム
WO2001041020A1 (fr) * 1999-12-03 2001-06-07 Bottomline Technologies, Inc. Systeme de facturation et de paiement base serveur
WO2001098957A2 (fr) * 2000-06-21 2001-12-27 Tapx Limited Procede et systeme de traitement de transaction financiere

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1996012242A1 (fr) * 1994-10-13 1996-04-25 World Trade Centers Association, Inc. Systeme de transactions complet
JP2001028026A (ja) * 1998-07-03 2001-01-30 Bank Of Tokyo-Mitsubishi Ltd 取引支援システム
WO2000048053A2 (fr) * 1999-02-12 2000-08-17 Etime Capital, Inc. Systeme et procede de gestion de transactions commerciales
WO2001041020A1 (fr) * 1999-12-03 2001-06-07 Bottomline Technologies, Inc. Systeme de facturation et de paiement base serveur
WO2001098957A2 (fr) * 2000-06-21 2001-12-27 Tapx Limited Procede et systeme de traitement de transaction financiere

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Object Management Group", 4 May 2001, DRAFT RFP, VER.1.1, OMG DOCUMENT NO. FINANCE, article "Account receivable account payable-AR/AP facility", pages: 1 - 37, XP002968854 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018190168A (ja) * 2017-05-02 2018-11-29 株式会社アール・アンド・エー・シー 照合プログラムおよびデータ照合方法

Also Published As

Publication number Publication date
AU2003244359A1 (en) 2003-09-02
JP2003233765A (ja) 2003-08-22

Similar Documents

Publication Publication Date Title
WO2003067489A1 (fr) Systeme de support d'echanges commerciaux
JP4677188B2 (ja) 統合サプライチェーンシステム中の管理、資金供給および供給方法と装置
US8290865B2 (en) Push payment system and method including billing file exchange
AU2007319459B2 (en) Payment processing system debt conversion notification
CA2835516C (fr) Systeme de point de vente utilisant un reseau de cartes prepayees/de cartes cadeaux
US20040049459A1 (en) System and method for integrated electronic invoice presentment and payment
US20080208723A1 (en) System and method for settling trades in a digital merchant exchange
JP2007507799A (ja) 自動支払と自動調整のためのシステムおよび方法
JP2005501326A (ja) 国際代金引換配送システム及び方法
CN111161045A (zh) 基于区块链进行出口卖方信贷的方法、存储介质
KR100407397B1 (ko) 무역서식 전자문서 및 전자문서교환방식에 의한무역자동화시스템
WO2023163833A1 (fr) Système et procédé d'intérêt de produit pouvant être suivi
JP2001266031A (ja) 商品取引信用補完システム
JP3273966B2 (ja) Ｐｏｓ端末及びホストコンピュータ
AU2024200088A1 (en) Point-of-sale system using prepaid/gift card network
AU2002365544B2 (en) Method and apparatus for management, financing and supply in an integrated supply chain system
JP2004145894A (ja) 債権決済システム
JP2001101308A (ja) 電子商取引システム
AU2004229081A1 (en) Settlement of Transactions

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载