US20220292467A1 - Trade settlement system, trade settlement method, and trade settlement program - Google Patents

Trade settlement system, trade settlement method, and trade settlement program Download PDF

Info

Publication number
US20220292467A1
US20220292467A1 US17/635,199 US201917635199A US2022292467A1 US 20220292467 A1 US20220292467 A1 US 20220292467A1 US 201917635199 A US201917635199 A US 201917635199A US 2022292467 A1 US2022292467 A1 US 2022292467A1
Authority
US
United States
Prior art keywords
node
settlement
trade
shipper
processing unit
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
US17/635,199
Other languages
English (en)
Inventor
Tetsunosuke SHINYA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tokio Marine and Nichido Fire Insurance Co Ltd
Original Assignee
Tokio Marine and Nichido Fire Insurance 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 Tokio Marine and Nichido Fire Insurance Co Ltd filed Critical Tokio Marine and Nichido Fire Insurance Co Ltd
Assigned to TOKIO MARINE & NICHIDO FIRE INSURANCE CO., LTD. reassignment TOKIO MARINE & NICHIDO FIRE INSURANCE CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SHINYA, Tetsunosuke
Publication of US20220292467A1 publication Critical patent/US20220292467A1/en
Pending legal-status Critical Current

Links

Images

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083—Shipping
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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
    • G06Q2220/00—Business processing using cryptography

Definitions

  • the present invention relates to a trade settlement system, a trade settlement method, and a trade settlement program.
  • Patent Literature 1 describes a technology in which “Upon receipt of a letter-of-credit issuance instruction, a transaction code is set, a record is stored in a trade transaction DB, and a letter-of-credit issuance request including the transaction code is transmitted. Upon receipt of this request, a trade transaction server sets a bank management code, and transmits a letter-of-credit issuance report including the bank management code together with the transaction code included in the request. Upon receipt of the letter-of-credit issuance report, the bank management code included in the report is stored in a record of the trade transaction DB that includes the transaction code included in the report.
  • the trade transaction server When bill-of-lading data has been generated, the trade transaction server adds the bank management code to the bill-of-lading data, and transmits the bill-of-lading data. Upon receipt of the bill-of-lading data, a record is stored in the bill-of-lading DB in association with a record of the trade transaction DB that includes the bank management code included in the bill-of-lading data.”
  • a trade settlement system in one aspect of the present invention is a trade settlement system that uses one or more computers, in which each of the one or more computers includes, for a bilateral contract including both obligations of a change of name from one party to another party of contract parties, the change of name accompanying a transfer of ownership of an article to be sold or purchased in a trade, and settlement using predetermined electronic money for a consideration relating to the sale and purchase: a settlement processing unit that performs the settlement by using a smart contract on a blockchain; and a processing unit that processes the change of name by using the smart contract on the blockchain, in a case where the settlement has been successful.
  • processing of the change of name may include processing for changing a name of an owner of a predetermined shipping document including at least a bill of lading relating to the article.
  • the predetermined shipping document may be configured as blockchain data.
  • the settlement may include settlement that includes payment using electronic currency between a plurality of parties concerned according to trade terms.
  • the settlement may include settlement that includes processing for paying freight of the trade to a carrier according to the trade terms by using the electronic currency.
  • the settlement may include settlement that includes processing for paying a cargo marine premium relating to the trade to an insurer according to the trade terms by using the electronic currency.
  • the settlement may include settlement that includes payment using virtual currency.
  • each of a shipper node, a consignee node, and a carrier node may be configured by the one or more computers, the shipper node serving as a node of a shipper of the trade, the consignee node serving as a node of a consignee of the trade, the carrier node serving as a node of a carrier of the trade.
  • the settlement processing unit of the consignee node may perform the settlement by remitting the consideration relating to the sale and purchase of the article to the settlement processing unit of the shipper node.
  • the processing unit of the carrier node may process the change of name by changing a name of a predetermined shipping document from the shipper to the consignee, the predetermined shipping document including a bill of lading relating to the article to be sold or purchased in the trade.
  • each of a shipper node, a consignee node, and a carrier node may be configured by the one or more computers, the shipper node serving as a node of a shipper of the trade, the consignee node serving as a node of a consignee of the trade, the carrier node serving as a node of a carrier of the trade.
  • the settlement processing unit of the consignee node may perform the settlement by remitting the consideration relating to the sale and purchase of the article to the settlement processing unit of the shipper node.
  • the settlement processing unit of the shipper node may perform the settlement by remitting freight of the trade to the settlement processing unit of the carrier node.
  • the processing unit of the carrier node may process the change of name by changing a name of a predetermined shipping document from the shipper to the consignee, the predetermined shipping document including a bill of lading of the article to be sold or purchased in the trade.
  • each of a shipper node, a consignee node, and a carrier node may be configured by the one or more computers, the shipper node serving as a node of a shipper of the trade, the consignee node serving as a node of a consignee of the trade, the carrier node serving as a node of a carrier of the trade.
  • the settlement processing unit of the consignee node may perform the settlement by remitting the consideration relating to the sale and purchase of the article to the settlement processing unit of the shipper node, and may perform the settlement by remitting freight of the trade to the settlement processing unit of the carrier node.
  • the processing unit of the carrier node may process the change of name by changing a name of a predetermined shipping document from the shipper to the consignee, the predetermined shipping document including a bill of lading of the article to be sold or purchased in the trade.
  • an insurer node may be configured by the one or more computers, the insurer node serving as a node of an insurer of the trade.
  • the settlement processing unit of the shipper node may perform the settlement by remitting the freight of the trade to the settlement processing unit of the carrier node, and remitting a cargo marine premium of the trade to the settlement processing unit of the insurer node.
  • an insurer node may be configured by the one or more computers, the insurer node serving as a node of an insurer of the trade.
  • the settlement processing unit of the consignee node may perform the settlement by remitting the consideration relating to the sale and purchase of the article to the settlement processing unit of the shipper node, and remitting a cargo marine premium of the trade to the settlement processing unit of the insurer node.
  • an insurer node may be configured by the one or more computers, the insurer node serving as a node of an insurer of the trade.
  • the settlement processing unit of the consignee node may perform the settlement by remitting the consideration relating to the sale and purchase of the article to the settlement processing unit of the shipper node, may perform the settlement by remitting the freight of the trade to the settlement processing unit of the carrier node, and may perform the settlement by remitting a cargo marine premium of the trade to the settlement processing unit of the insurer node.
  • a trade settlement method in another aspect of the present invention is a trade settlement method that uses one or more computers.
  • Each of the one or more computers performs, for a bilateral contract including both obligations of a change of name from one party to another party of contract parties, the change of name accompanying a transfer of ownership of an article to be sold or purchased in a trade, and settlement using predetermined electronic money for a consideration relating to the sale and purchase: a settlement processing step of performing the settlement by using a smart contract on a blockchain; and a processing step of processing the change of name by using the smart contract on the blockchain, in a case where the settlement has been successful.
  • a trade settlement program in another aspect of the present invention is a trade settlement program that uses one or more computers.
  • the trade settlement program causes each of the one or more computers to perform, for a bilateral contract including both obligations of a change of name from one party to another party of contract parties, the change of name accompanying a transfer of ownership of an article to be sold or purchased in a trade, and settlement using predetermined electronic money for a consideration relating to the sale and purchase: a settlement processing step of performing the settlement by using a smart contract on a blockchain; and a processing step of processing the change of name by using the smart contract on the blockchain, in a case where the settlement has been successful.
  • FIG. 1 is a configuration diagram illustrating an example of a mechanism of trade settlement according to an embodiment.
  • FIG. 2 is a configuration diagram illustrating an example of a trade settlement system according to the embodiment.
  • FIG. 3 is a diagram illustrating an example of a configuration of a distributed ledger node.
  • FIG. 4 is a diagram illustrating an example of a data structure of an invoice.
  • FIG. 5 is a diagram illustrating an example of a data structure of a bill of lading.
  • FIG. 6 is a diagram illustrating an example of a data structure of an insurance policy request.
  • FIG. 7 is a diagram illustrating an example of a data structure of an insurance policy.
  • FIG. 8 is a diagram illustrating an example of a hardware configuration of a distributed ledger node.
  • FIG. 9 is a diagram illustrating an example of a detailed configuration of the trade settlement system.
  • FIG. 10 is a diagram illustrating an example of a flow of invoice preparation approval processing.
  • FIG. 11 is a diagram illustrating an example of a flow of bill-of-lading preparation approval processing.
  • FIG. 12 is a diagram illustrating an example of a flow of insurance policy preparation approval processing.
  • FIG. 13 is a diagram illustrating an example of a flow of settlement processing in the case of CIF.
  • FIG. 14 is a diagram illustrating an example of a flow of settlement processing in the case of CFR.
  • FIG. 15 is a diagram illustrating an example of a flow of settlement processing in the case of FOB.
  • FIG. 16 is a diagram illustrating an example of a flow of change-of-name processing.
  • FIG. 17 is a diagram illustrating an example of a consignee screen.
  • FIG. 18 is a diagram illustrating an example of a shipper screen.
  • a trade settlement system 1 to which an embodiment in one aspect of the present invention has been applied is described below with reference to the drawings.
  • the embodiment described below is divided into a plurality of sections or embodiments, as needed for convenience, and description is provided. However, unless otherwise specified, the plurality of sections or embodiments has a relationship with each other, and one section or embodiment has a relationship of a variation, details, an additional description, or the like of part or the entirety of another section or embodiment.
  • the number or the like (including the number of pieces, a numerical number, an amount, a range, and the like) of elements is referred to, the number or the like of elements is not limited to a specified number, and may be greater than or equal to the specified number or may be less than or equal to the specified number, unless otherwise specified and excluding a case where the number or the like of elements is obviously limited to the specified number in principle, and other cases.
  • components (including element steps or the like) of the embodiment are not necessarily essential, unless otherwise specified and excluding a case where it can be considered that the components are obviously essential in principle, and other cases.
  • the shape or the like of the component or the like includes, for example, a shape or the like that is substantially approximated or similar to the shape or the like of the component or the like, unless otherwise specified and excluding a case where it can be obviously considered that this is not the case in principle, and other cases.
  • the similar is applied to the numerical number and the range that have been described above.
  • a consignee 3 serving as an importer executes a sale and purchase contract with a shipper 2 serving as an exporter, and the consignee 3 causes a bank to prepare a letter of credit, and delivers the letter of credit to the shipper 2 .
  • the shipper 2 ships products serving as articles in accordance with the terms of the contract.
  • a carrier 5 serving as a shipping company issues a bill of lading (B/L) to the shipper 2 in exchange for cargo.
  • the shipper 2 attaches the letter of credit and shipping documents (the bill of lading, an invoice, a certificate of cargo marine insurance, or the like), and requests that a bank buy a documentary bill of exchange (a self-order bill of exchange).
  • the shipper 2 collects a cost of the products.
  • the bank that has complied with a request to buy the documentary bill of exchange sends the documentary bill of exchange and the shipping documents to a bank of the consignee that has issued the letter of credit.
  • the bank of the consignee 3 receives the documentary bill of exchange, the shipping document, or the like, and pays the cost to the bank of the shipper 2 .
  • the bank of the consignee 3 requests that the consignee 3 accept the documentary bill of exchange.
  • the consignee 3 accepts the documentary bill of exchange, and also receives the bill of lading.
  • the consignee 3 receives the products from the carrier 5 in exchange for the bill of lading.
  • FIG. 1 is a configuration diagram illustrating an example of a mechanism of trade settlement according to the embodiment.
  • This is a mechanism of using the trade settlement system 1 according to the present embodiment to guarantee the simultaneous fulfillment of obligations of a bilateral contract among a shipper 2 , a consignee 3 , a carrier 5 , and an insurer 6 by using a trade settlement platform 4 .
  • the name of an owner indicating a vesting destination of ownership on shipping document data is changed from the shipper 2 to the consignee 3 from among contracting parties, and a cost of products moves between accounts from the consignee 3 to the shipper 2 .
  • a procedure of paying freight to be paid to the carrier 5 and a cargo marine premium to be paid to the insurer 6 is performed similarly by using the trade settlement platform 4 .
  • FIG. 2 is a configuration diagram illustrating an example of a trade settlement system according to the embodiment.
  • the trade settlement platform 4 is implemented by a distributed ledger network (what is called a blockchain). Therefore, the trade settlement platform 4 is a distributed processing environment obtained by combining one or more computers called distributed ledger nodes 100 .
  • the trade settlement platform 4 is communicably connected to an operation terminal 200 via a network 50 such as a local area network (LAN), a wide area network (WAN), the Internet, a portable telephone network, or a composite communication network of the LAN, the WAN, the Internet, the portable telephone network, and the like.
  • LAN local area network
  • WAN wide area network
  • the Internet a portable telephone network
  • a composite communication network of the LAN, the WAN, the Internet, the portable telephone network, and the like such as a local area network (LAN), a wide area network (WAN), the Internet, a portable telephone network, or a composite communication network of the LAN, the WAN, the Internet, the portable telephone network, and
  • the network 50 may be a virtual private network (VPN) or the like on a wireless communication network such as a portable telephone communication network.
  • VPN virtual private network
  • the operation terminal 200 is a terminal to be used by each user of the shipper 2 , the consignee 3 , the carrier 5 , and the insurer 6 .
  • the operation terminal 200 may be any device that can be connected to the trade settlement platform 4 via browser software or application software, such as a smartphone, a personal computer, or a tablet device of each of the users.
  • the distributed ledger node 100 may be any device that can configure the trade settlement platform 4 via browser software or application software, such as a smartphone, a personal computer or a tablet device.
  • the blockchain is a technology for storing data in a distributed environment by handling a set of pieces of management data, such as transaction data, as data called a “block”, and connecting a block to previous data, like a chain (by adding a hash value or the like for referring to a block, and associating blocks with each other in such a way that preceding or subsequent blocks can be traced).
  • a set of pieces of management data such as transaction data, as data called a “block”
  • connecting a block to previous data like a chain (by adding a hash value or the like for referring to a block, and associating blocks with each other in such a way that preceding or subsequent blocks can be traced).
  • processing of settlement or a change of name is implemented by a smart contract on the basis of the blockchain.
  • the smart contract has been executed as a program on the blockchain, non-falsification can be guaranteed, and processing can be performed speedily and reliably.
  • each user of the shipper 2 , the consignee 3 , the carrier 5 , and the insurer 6 performs a procedure of preparation of shipping documents, a change of name (a change in a vesting destination that accompanies the transfer of ownership), or a movement of a fund on the trade settlement platform 4 , by using an operation terminal 200 of each of the users.
  • This enables the simultaneous fulfillment of obligations relating to a bilateral contract in a trade transaction.
  • the trade settlement platform 4 cooperates with a currency settlement platform 450 .
  • the currency settlement platform 450 may process settlement in electronic money (electronized money having an exchange value that is roughly similar to an exchange value of money) in addition to virtual currency.
  • Examples of electronic money include electronic currency obtained by electronizing real physical currency for which credit is guaranteed by each government, such as dollars or euros, electronic money or the like that is provided by a private enterprise or the like, electronized securities, real property, or the like, and others having a monetary exchange value that is similar to a monetary exchange value of the above.
  • virtual currency is electronic money.
  • virtual currency is considered to be part of electronic money in consideration with characteristics of virtual currency.
  • virtual currency is not limited to this, and it can be said that virtual currency can be electronically handled, and has a monetary exchange value.
  • Virtual currency has similarity to electronized securities, real property, or the like in consideration with a speculative aspect, and it can be considered that virtual currency is similar to electronic money in the point of convenience of settlement.
  • the currency settlement platform 450 is implemented, for example, by a distributed ledger network (what is called a blockchain). Therefore, the currency settlement platform 450 is a distributed processing environment obtained by combining one or more computers called electronic wallet nodes 400 .
  • the currency settlement platform 450 is communicably connected to the trade settlement platform 4 via the network 50 .
  • FIG. 3 is a diagram illustrating an example of a configuration of a distributed ledger node.
  • a distributed ledger node 100 includes a storage unit 110 , a control unit 130 , and a communication unit 160 .
  • the storage unit 110 includes a smart contract storage unit 111 and a node role information storage unit 116 .
  • the smart contract storage unit 111 includes, as blockchain data, an invoice 112 , a bill of lading 113 , an insurance policy request 114 , and an insurance policy 115 .
  • FIG. 4 is a diagram illustrating an example of a data structure of an invoice.
  • the invoice 112 includes an invoice code 112 A, an invoice status 112 B, owner name 112 C, shipper name 112 D, consignee name 112 E, an export port 112 F, an import port 112 G, Incoterms 112 H, payment currency name 112 J, platform currency name 112 K, product name 112 L, product class 112 M, product unit price 112 N, the number of products 112 P, invoice preparation date and time 112 Q, an electronic signature of an invoice preparer 112 R, invoice update date and time 112 S, and an electronic signature of an invoice updating person 112 T.
  • the invoice status 112 B is a hashed character string that means “approved”, “not-yet-approved”, or the like, and is control information for avoiding a double transaction by rewriting a character string into another character string every time a change is made to data of the invoice to avoid updating from a state indicated by a previous status.
  • the owner name 112 C is information that specifies the name of an owner of the invoice, and is an item that will be rewritten from the shipper 2 to the consignee 3 at the time of simultaneous fulfillment of obligations.
  • the Incoterms 112 H is information that specifies trade terms. The other items are data items that generally configure the invoice.
  • FIG. 5 is a diagram illustrating an example of a data structure of a bill of lading.
  • the bill of lading 113 includes a bill-of-lading code 113 A, a bill-of-lading status 113 B, owner name 113 C, a target invoice code 113 D, shipper name 113 E, consignee name 113 F, carrier name 113 G, an export source 113 H, an export destination 113 J, payment currency name 113 K, product name 113 L, freight price 113 M, bill-of-lading preparation date and time 113 N, an electronic signature of a bill-of-lading preparer 113 P, bill-of-lading update date and time 113 Q, and an electronic signature of a bill-of-lading updating person 113 R.
  • the bill-of-lading status 113 B is a hashed character string that means “approved”, “not-yet-approved”, or the like, and is control information for avoiding a double transaction by rewriting a character string into another character string every time a change is made to data of the bill of lading to avoid updating from a state indicated by a previous status.
  • the owner name 113 C is information that specifies the name of an owner of the bill of lading, and is an item that will be rewritten from the shipper 2 to the consignee 3 at the time of simultaneous fulfillment of obligations.
  • the bill of lading (B/L) has a real right effect in a trade transaction, and it can be said that an owner described in the owner name 113 C is an owner of cargo.
  • the carrier name 113 G is information that specifies the carrier 5 .
  • the freight price 113 M is freight serving as a consideration paid to the carrier 5 for carrying cargo.
  • the other items are data items that generally configure the bill of lading.
  • FIG. 6 is a diagram illustrating an example of a data structure of an insurance policy request.
  • the insurance policy request is data to be used to apply for insurance.
  • the insurance policy request 114 includes an insurance policy request code 114 A, an insurance policy request status 114 B, insurance policy request person name 114 C, insured person name 114 D, insurer name 114 E, adviser name 114 F, a target invoice code 114 G, a target bill-of-lading code 114 H, insurance policy request preparation date and time 114 J, an electronic signature of an insurance policy request preparer 114 K, insurance policy request update date and time 114 L, and an electronic signature of an insurance policy request updating person 114 M.
  • the insurance policy request status 114 B is a hashed character string, and is control information for avoiding a double transaction by rewriting a character string into another character string every time a change is made to data of the insurance policy request to avoid updating from a state indicated by a previous status.
  • the insurance policy request person name 114 C is information that specifies the name of an applicant on an insurance policy.
  • the insured person name 114 D is generally information that specifies a beneficiary of insurance money.
  • FIG. 7 is a diagram illustrating an example of a data structure of an insurance policy.
  • the insurance policy is a certificate that is issued when applied insurance has been accepted, and has been established.
  • the insurance policy 115 includes an insurance policy code 115 A, an insurance policy status 115 B, an owner name 115 C, a target insurance policy request code 115 D, an amount of compensation 115 E, a premium 115 F, insurance policy preparation date and time 115 G, an electronic signature of an insurance policy preparer 115 H, insurance policy update date and time 115 J, and an electronic signature of an insurance policy updating person 115 K.
  • the insurance policy status 115 B is a hashed character string that means “approved”, “not-yet-approved”, or the like, and is control information for avoiding a double transaction by rewriting a character string into another character string every time a change is made to data of the insurance policy to avoid updating from a state indicated by a previous status.
  • the owner name 115 C is information that specifies the beneficiary of insurance money, and is an item that will be rewritten from the shipper 2 to the consignee 3 at the time of simultaneous fulfillment of obligations.
  • the node role information storage unit 116 stores information that distinguishes a role that is played by the distributed ledger node 100 .
  • the distributed ledger node 100 plays a role of part of the trade settlement platform 4 in a fluid or fixed manner. Therefore, there is a possibility that the distributed ledger node 100 will temporarily serve as any of a node of the shipper 2 , a node of the consignee 3 , a node of the carrier 5 , and a node of the insurer 6 .
  • the control unit 130 includes an invoice processing unit 131 , a bill-of-lading processing unit 132 , an insurance policy processing unit 133 , a settlement processing unit 134 , and an output information generation unit 135 .
  • the invoice processing unit 131 , the bill-of-lading processing unit 132 , and the insurance policy processing unit 133 are implemented by a processor loading smart contract codes provided on respective blockchains of an invoice, a bill of lading, and an insurance policy.
  • the invoice processing unit 131 is a smart contract relating to a blockchain of an invoice. Specifically, the invoice processing unit 131 prepares an invoice, approves the invoice, makes a change such as a change of name, or deletes the invoice.
  • the bill-of-lading processing unit 132 is a smart contract relating to a blockchain of a bill of lading. Specifically, the bill-of-lading processing unit 132 prepares a bill of lading, approves the bill of lading, makes a change such as a change of name, or deletes the bill of lading.
  • the insurance policy processing unit 133 is a smart contract relating to a blockchain of an insurance policy. Specifically, the insurance policy processing unit 133 prepares an insurance policy, approves the insurance policy, makes a change such as a change of name, or deletes the insurance policy.
  • the settlement processing unit 134 provides an application programming interface (API) for performing settlement processing, in response to the smart contract code.
  • API application programming interface
  • the settlement processing unit 134 transfers processing that corresponds to called settlement processing to the currency settlement platform 450 .
  • the settlement processing unit 134 issues, to the currency settlement platform 450 , an instruction to move a fund of a specified amount between specified electronic wallet nodes.
  • This fund may be in currency that the currency settlement platform 450 can handle, and may be, for example, in any of virtual currencies or in a real currency.
  • the output information generation unit 135 generates information to be displayed on a screen for an instruction and a result of processing performed by each of the invoice processing unit 131 , the bill-of-lading processing unit 132 , and the insurance policy processing unit 133 . Specifically, the output information generation unit 135 generates displayed information that indicates a button instructing that an invoice be generated, a region that receives an input of a data item of the invoice, or a region that displays the generated invoice. The output information generation unit 135 generates information to be displayed on a screen for each of a bill of lading and an insurance policy, similarly to the invoice.
  • the communication unit 160 performs communication with another device via the network 50 .
  • packet communication according to the TCP/IP protocol is employed, but the communication is not limited to this.
  • FIG. 8 is a diagram illustrating an example of a hardware configuration of a distributed ledger node.
  • the distributed ledger node 100 has a hardware configuration implemented by a housing of what is called a server device, a work station, a personal computer, a smartphone, or a tablet terminal.
  • the distributed ledger node 100 includes an processor 101 , a memory 102 , a storage 103 , an input device 104 , a display device 105 , a communication device 106 , and a bus 107 that connects respective devices.
  • the processor 101 is an arithmetic device such as a central processing unit (CPU).
  • CPU central processing unit
  • the memory 102 is a memory device such as a random access memory (RAM).
  • RAM random access memory
  • the storage 103 is a non-volatile storage device that can store digital information, such as what is called a hard disk drive, a solid state drive (SSD), or a flash memory.
  • a hard disk drive such as what is called a hard disk drive, a solid state drive (SSD), or a flash memory.
  • SSD solid state drive
  • the input device 104 is a device that receives an input of any or some of a keyboard, a mouse, a touch panel, and a microphone.
  • the display device 105 is a device that conducts a display on any or some of various output devices such as an organic electro-luminescence (EL) display.
  • EL organic electro-luminescence
  • the communication device 106 is a network interface card (NIC) that performs communication with another device via a network, a board or the like that performs communication with another device via an HDMI cable, an antenna device that performs wireless communication with another device via a wireless network, or a communication module or the like that performs communication with another device in one-to-one wireless communication.
  • NIC network interface card
  • the invoice processing unit 131 , the bill-of-lading processing unit 132 , the insurance policy processing unit 133 , the settlement processing unit 134 , and the output information generation unit 135 of the distributed ledger node 100 described above are implemented by a program (a smart contract) that causes the processor 101 to perform processing.
  • This program is distributed from another device via a network according to a mechanism of a blockchain, is stored in the memory 102 or the storage 103 , is loaded into the memory 102 for execution, and is executed by the processor 101 .
  • the storage unit 110 of the distributed ledger node 100 is implemented by the memory 102 and the storage 103 .
  • the communication unit 160 is implemented by the communication device 106 .
  • An example of a hardware configuration of the distributed ledger node 100 has been described above.
  • a configuration of the distributed ledger node 100 can be classified into a larger number of components according to the content of processing.
  • one component can be classified in such a way that a larger number of pieces of processing are performed.
  • each control unit (the invoice processing unit 131 , the bill-of-lading processing unit 132 , the insurance policy processing unit 133 , the settlement processing unit 134 , or the output information generation unit 135 ) may be constructed by dedicated hardware (ASIC, GPU, or the like) that achieves each function. Furthermore, processing of each of the control units may be performed by one piece of hardware, or may be performed by plural pieces of hardware. Moreover, the distributed ledger node 100 does not need to constantly include all of the respective units, and may temporarily include all of the control units or only some of the control units. It is sufficient if the distributed ledger node 100 configures part of a blockchain and a smart contract.
  • operation terminal 200 and the electronic wallet node 400 basically have a hardware configuration that is similar to a hardware configuration of the distributed ledger node.
  • FIG. 9 is a diagram illustrating an example of a detailed configuration of a trade settlement system.
  • the trade settlement platform 4 and the currency settlement platform 450 are communicably connected by using a network and an API server as an interface. Stated another way, the trade settlement platform 4 is connected to the currency settlement platform 450 , by using a call of the API.
  • the API server provides an API, and controls a required movement of a fund between electronic wallet nodes 400 according to a type and a parameter of a called interface.
  • the electronic wallet node 400 includes a shipper node 400 B that performs processing on an electronic wallet of a shipper, a consignee node 400 A that performs processing on an electronic wallet of a consignee, a carrier node 400 C that performs processing on an electronic wallet of a carrier, an insurer node 400 E that performs processing on an electronic wallet of an insurer, and a network operator node 400 D that performs processing on an electronic wallet of a network operator.
  • each electronic wallet node is configured by one or more computers, and the allocation of a wallet to a computer that configures each of the electronic wallet nodes may be dynamically changed.
  • the distributed ledger node 100 includes a shipper node 100 B that performs processing on a blockchain and a smart contract of a shipper, a consignee node 100 A that performs processing on a blockchain and a smart contract of a consignee, a carrier node 100 C that performs processing on a blockchain and a smart contract of a carrier, an insurer node 100 E that performs processing on a blockchain and a smart contract of an insurer, and an adviser node 100 D that performs processing on a blockchain and a smart contract of an adviser.
  • each distributed ledger node is configured by one or more computers, and the role of a computer that configures each of the distributed ledger nodes may be dynamically changed. Every time, an assigned role is written to the node role information storage unit 116 of the distributed ledger node 100 , and the distributed ledger node acts as a node having the role.
  • the operation terminal 200 includes a shipper operation terminal 200 B that performs processing on an input/output of a shipper, a consignee operation terminal 200 A that performs processing on an input/output of a consignee, a carrier operation terminal 200 C that performs processing on an input/output of a carrier, an insurer operation terminal 200 E that performs processing on an input/output of an insurer, and an adviser operation terminal 200 D that performs processing on an input/output of an adviser.
  • a shipper operation terminal 200 B that performs processing on an input/output of a shipper
  • a consignee operation terminal 200 A that performs processing on an input/output of a consignee
  • a carrier operation terminal 200 C that performs processing on an input/output of a carrier
  • an insurer operation terminal 200 E that performs processing on an input/output of an insurer
  • an adviser operation terminal 200 D that performs processing on an input/output of an adviser.
  • FIG. 10 is a diagram illustrating an example of a flow of invoice preparation approval processing.
  • a shipper starts invoice preparation approval processing.
  • an invoice preparation request and item data of an invoice are transmitted from the shipper operation terminal 200 B to the shipper node 100 B (step S 001 ).
  • the shipper operation terminal 200 B receives an input of data of each item of an invoice from the shipper 2 , and transmits the data to the shipper node 100 B.
  • the shipper node 100 B prepares an invoice smart contract (step S 002 ). Specifically, in the shipper node 100 B, the invoice processing unit 131 generates a blockchain of the invoice.
  • the invoice processing unit 131 of the shipper node 100 B reports an invoice status to the consignee node 100 A in such a way that the invoice smart contract can be shared (step S 003 ).
  • the shipper node 100 B reports, to the shipper operation terminal 200 B, a result of preparing the invoice smart contract together with invoice data (step S 004 ).
  • the consignee node 100 A reports to the consignee operation terminal 200 A that the invoice smart contract is shared, together with the invoice data (step S 005 ).
  • a phase of preparation of an invoice has been described above.
  • a blockchain that is, a smart contract, of the invoice is generated, and the shipper operation terminal 200 B and the consignee operation terminal 200 A obtain invoice data.
  • the consignee operates the consignee operation terminal 200 A, and transmits, to the consignee node 100 A, a request to approve the invoice together with an invoice code and an invoice status (step S 006 ).
  • the invoice processing unit 131 of the consignee node 100 A approves the invoice smart contract (step S 007 ). This approval processing is performed according to a general blockchain consensus algorithm.
  • the consignee node 100 A transmits the invoice data to the shipper operation terminal 200 B and the consignee operation terminal 200 A, and reports a result of approving the invoice smart contract (step S 008 ).
  • a phase of approval of an invoice has been described above.
  • a blockchain that is, a smart contract, of the invoice is approved, and approved invoice data is transmitted to the shipper operation terminal 200 B and the consignee operation terminal 200 A.
  • FIG. 11 is a diagram illustrating an example of a flow of bill-of-lading preparation approval processing.
  • the bill-of-lading preparation approval processing of FIG. 11 indicates a case where Incoterms indicating transaction terms of trade is cost, insurance, and freight (CIF) or cost and freight (CFR), and a shipper that has received approval of an invoice starts the bill-of-lading preparation approval processing.
  • CIF cost, insurance, and freight
  • CFR cost and freight
  • an invoice code and a carrier code are transmitted from the shipper operation terminal 200 B to the shipper node 100 B (step S 101 ).
  • the shipper operation terminal 200 B receives an input of an invoice code and a carrier code of a selected carrier from the shipper 2 , and transmits the invoice code and the carrier code to the shipper node 100 B.
  • the shipper node 100 B shares an invoice smart contract with the carrier (step S 102 ). Specifically, in the shipper node 100 B, the invoice processing unit 131 transmits the invoice code to the carrier node 100 C.
  • the carrier node 100 C transmits invoice data to the carrier operation terminal 200 C to report that the invoice smart contract is shared (step S 103 ).
  • the carrier operation terminal 200 C can obtain the invoice data.
  • the carrier 5 transmits a request to prepare a bill of lading and item data of the bill of lading from the carrier operation terminal 200 C to the carrier node 100 C (step S 104 ).
  • the carrier operation terminal 200 C receives an input of data of each item of the bill of lading from the carrier 5 , and transmits the data to the carrier node 100 C.
  • the carrier node 100 C prepares a bill-of-lading smart contract (step S 105 ). Specifically, in the carrier node 100 C, the bill-of-lading processing unit 132 generates a blockchain of the bill of lading.
  • the bill-of-lading processing unit 132 of the carrier node 100 C reports a bill-of-lading status to the shipper node 100 B in such a way that the bill-of-lading smart contract can be shared (step S 106 ).
  • the carrier node 100 C reports, to the carrier operation terminal 200 C, a result of preparing the bill-of-lading smart contract together with bill-of-lading data (step S 107 ).
  • the shipper node 100 B reports to the shipper operation terminal 200 B that the bill-of-lading smart contract is shared, together with the bill-of-lading data (step S 108 ).
  • a phase of preparation of a bill of lading has been described above.
  • a blockchain that is, a smart contract, of the bill of lading is generated, and the shipper operation terminal 200 B and the carrier operation terminal 200 C obtain bill-of-lading data.
  • the carrier 5 operates the carrier operation terminal 200 C, and transmits, to the carrier node 100 C, a request to approve the bill of lading together with a bill-of-lading code and a bill-of-lading status (step S 109 ).
  • the bill-of-lading processing unit 132 of the carrier node 100 C approves the bill-of-lading smart contract (step S 110 ). This approval processing is performed according to a general blockchain consensus algorithm.
  • the bill-of-lading processing unit 132 of the carrier node 100 C reports a bill-of-lading status to the consignee node 100 A in such a way that the bill-of-lading smart contract can be shared (step S 111 ).
  • the bill-of-lading processing unit 132 of the carrier node 100 C transmits the bill-of-lading data to the shipper operation terminal 200 B and the carrier operation terminal 200 C, and reports a result of approving the bill-of-lading smart contract (step S 112 ).
  • a phase of approval of a bill of lading has been described above.
  • a blockchain that is, a smart contract, of the bill of lading is approved, and approved bill-of-lading data is transmitted to the shipper operation terminal 200 B and the carrier operation terminal 200 C.
  • FIG. 12 is a diagram illustrating an example of a flow of insurance policy preparation approval processing.
  • the insurance policy preparation approval processing of FIG. 12 indicates a case where Incoterms indicating transaction terms of trade is CIF, and the insurance policy preparation approval processing is started by a shipper that has received approval of an invoice and approval of a bill of lading.
  • Incoterms is CFR or FOB
  • an invoice code, a bill-of-lading code, an adviser code, and an insurer code are transmitted from the shipper operation terminal 200 B to the shipper node 100 B (step S 201 ).
  • the shipper operation terminal 200 B receives, from the shipper 2 , an input of an invoice code, a bill-of-lading code, an adviser code of a selected adviser, and an insurer code of a selected insurer, and transmits, to the shipper node 100 B, the invoice code, the bill-of-lading code, the adviser code, and the insurer code.
  • an adviser plays a role of mediating an application for insurance.
  • the shipper node 100 B prepares an insurance policy preparation request smart contract (step S 202 ). Specifically, in the shipper node 100 B, the insurance policy processing unit 133 generates a blockchain of a request to prepare an insurance policy.
  • the insurance policy processing unit 133 of the shipper node 100 B reports an insurance policy request status to an adviser node 100 D that has been specified by the adviser code in such a way that the insurance policy request smart contract can be shared (step S 203 ).
  • the insurance policy processing unit 133 of the adviser node 100 D reports an insurance policy request status to an insurer node 100 E of an insurer 6 that has been specified by the insurer code in such a way that the insurance policy request smart contract can be shared (step S 204 ).
  • the insurance policy processing unit 133 of the insurer node 100 E prepares an insurance policy smart contract (step S 205 ). Specifically, in the insurer node 100 E, the insurance policy processing unit 133 generates a blockchain of an insurance policy.
  • the insurance policy processing unit 133 of the insurer node 100 E reports an insurance policy status to the adviser node 100 D in such a way that the insurance policy smart contract can be shared (step S 206 ).
  • the insurance policy processing unit 133 of the adviser node 100 D reports an insurance policy status to the shipper node 100 B in such a way that the insurance policy smart contract can be shared (step S 207 ).
  • a phase of preparation of an insurance policy has been described above.
  • a blockchain that is, a smart contract, of the insurance policy is generated, and the shipper node 100 B and the adviser node 100 D can obtain insurance policy data.
  • the insurer 6 operates the insurer operation terminal 200 E, and transmits, to the insurer node 100 E, a request to approve an insurance policy together with the insurance policy code and an insurance policy status (step S 208 ).
  • the insurance policy processing unit 133 of the insurer node 100 E reports an insurance policy status to an adviser node 100 D that has been specified by the adviser code in such a way that the request to approve the insurance policy can be shared (step S 209 ).
  • the insurance policy processing unit 133 of the adviser node 100 D approves the insurance policy smart contract (step S 210 ). This approval processing is performed according to a general blockchain consensus algorithm.
  • the insurance policy processing unit 133 of the adviser node 100 D transmits insurance policy data to the shipper node 100 B and the insurer node 100 E, and reports a result of approving the insurance policy smart contract (step S 211 ).
  • the insurance policy processing unit 133 of the shipper node 100 B transmits the insurance policy data to the shipper operation terminal 200 B, and reports a result of approving the insurance policy smart contract (step S 212 ).
  • a phase of approval of an insurance policy has been described above.
  • a blockchain that is, a smart contract, of the insurance policy is approved, and approved insurance policy data is transmitted to the shipper operation terminal 200 B, the adviser node 100 D, and the insurer node 100 E.
  • FIG. 13 is a diagram illustrating an example of a flow of settlement processing in the case of CIF.
  • Settlement processing is started in a state where at least an invoice and a bill of lading have been prepared and approved.
  • the necessity of preparation and approval of an insurance policy depends on a transaction, and therefore the preparation and approval of the insurance policy is not essential.
  • the present flow example indicates an example of a transaction in which an insurance contract is made.
  • a consignee pays the sum of a cost of products, freight, and a premium to a shipper, and the shipper respectively pays the freight and a cargo marine premium to the carrier 5 and the insurer 6 .
  • the shipper node 100 B requests that the consignee node 100 A start payment processing (step S 301 ). Specifically, the settlement processing unit 134 of the shipper node 100 B transmits, to the consignee node 100 A, remittance information including at least a remittance source address (information specifying a wallet), a remittance destination address, the purpose of remittance, and a remittance amount. It is assumed that the settlement processing unit 134 refers to a shipper, a consignee, product name, product unit price, and the number of products on an invoice, freight price on a bill of lading, and a premium on an insurance policy, and specifies the remittance information. However, this is not restrictive. Information that the shipper 2 has input in the shipper operation terminal 200 B may be used, or registered information on a system for predetermined transactions or on a system for virtual currency transactions may be referred to.
  • the settlement processing unit 134 of the consignee node 100 A transmits the remittance information to an electronic wallet of the consignee node 400 A, and transmits a request to pay a cost (step S 302 ).
  • the consignee node 400 A remits an amount specified by the remittance amount from an electronic wallet of a consignee specified by the remittance source address to an electronic wallet of a shipper specified by the remittance destination address, and updates a cost payment settlement balance (step S 303 ).
  • the consignee node 400 A reports a result of paying the cost to the consignee node 100 A (step S 304 ).
  • the consignee node 400 A transmits, to the consignee node 100 A, a result of remittance including a remittance status code and a transaction code.
  • the settlement processing unit 134 of the consignee node 100 A transmits a cost payment status to the shipper node 100 B, and shares the cost payment status (step S 305 ).
  • the shipper node 100 B requests that the shipper node 400 B pay freight (step S 306 ).
  • the settlement processing unit 134 of the shipper node 100 B transmits, to the shipper node 400 B, remittance information including at least a remittance source address, a remittance destination address, the purpose of remittance, and a remittance amount. It is assumed that the settlement processing unit 134 refers to a shipper, a consignee, and freight price on a bill of lading, and specifies the remittance information. However, this is not restrictive. Information that the shipper 2 has input in the shipper operation terminal 200 B may be used, or registered information on a system for predetermined transactions or on a system for virtual currency transactions may be referred to.
  • the shipper node 400 B remits an amount specified by the remittance amount from an electronic wallet of a shipper specified by the remittance source address to an electronic wallet of a carrier specified by the remittance destination address, and updates a freight payment settlement balance (step S 307 ). Then, the shipper node 400 B reports a result of paying freight to the shipper node 100 B (step S 308 ). Specifically, the shipper node 400 B transmits, to the shipper node 100 B, a result of remittance including a remittance status code and a transaction code.
  • the shipper node 100 B requests that the shipper node 400 B pay a premium (step S 309 ).
  • the settlement processing unit 134 of the shipper node 100 B transmits, to the shipper node 400 B, remittance information including at least a remittance source address, a remittance destination address, the purpose of remittance, and a remittance amount. It is assumed that the settlement processing unit 134 refers to a shipper and consignee on an invoice, and a premium on an insurance policy, and specifies the remittance information. However, this is not restrictive. Information that the shipper 2 has input in the shipper operation terminal 200 B may be used, or registered information on a system for predetermined transactions or on a system for virtual currency transactions may be referred to.
  • the shipper node 400 B remits an amount specified by the remittance amount from an electronic wallet of a shipper specified by the remittance source address to an electronic wallet of an insurer specified by the remittance destination address, and updates a premium payment settlement balance (step S 310 ). Then, the shipper node 400 B reports a result of paying a premium to the shipper node 100 B (step S 311 ). Specifically, the shipper node 400 B transmits, to the shipper node 100 B, a result of remittance including a remittance status code and a transaction code.
  • FIG. 14 is a diagram illustrating an example of a flow of settlement processing in the case of CFR.
  • Settlement processing is started in a state where at least an invoice and a bill of lading have been prepared and approved.
  • the necessity of preparation and approval of an insurance policy depends on a transaction, and therefore the preparation and approval of the insurance policy is not essential.
  • the present flow example indicates an example of a transaction in which an insurance contract is made.
  • CFR Incoterms
  • the flow is basically similar to a flow of settlement processing in the case of CIF, but there is a difference in a flow of payment of a premium. Therefore, a section of processing for paying a premium (the processes of steps S 309 to S 311 in FIG. 13 ) in the case of CFR is described below.
  • the consignee node 100 A requests that the consignee node 400 A pay a premium (step S 309 ′).
  • the settlement processing unit 134 of the consignee node 100 A transmits, to the consignee node 400 A, remittance information including at least a remittance source address, a remittance destination address, the purpose of remittance, and a remittance amount. It is assumed that the settlement processing unit 134 refers to a shipper and consignee on an invoice, and a premium on an insurance policy, and specifies the remittance information. However, this is not restrictive. Information that the consignee 3 has input in the consignee operation terminal 200 A may be used, or registered information on a system for predetermined transactions or on a system for virtual currency transactions may be referred to.
  • the consignee node 400 A remits an amount specified by the remittance amount from an electronic wallet of a consignee specified by the remittance source address to an electronic wallet of an insurer specified by the remittance destination address, and updates a premium payment settlement balance (step S 310 ′).
  • the consignee node 400 A reports a result of paying a premium to the consignee node 100 A (step S 311 ′). Specifically, the consignee node 400 A transmits, to the consignee node 100 A, a result of remittance including a remittance status code and a transaction code.
  • FIG. 15 is a diagram illustrating an example of a flow of settlement processing in the case of FOB.
  • Settlement processing is started in a state where at least an invoice and a bill of lading have been prepared and approved.
  • the necessity of preparation and approval of an insurance policy depends on a transaction, and therefore the preparation and approval of the insurance policy is not essential.
  • the present flow example indicates an example of a transaction in which an insurance contract is made. Under terms indicated by the Incoterms “FOB” of trade terms, a consignee pays a cost of products to a shipper, and the consignee pays freight and a cargo marine premium to the carrier 5 and the insurer 6 , respectively.
  • FOB Incoterms
  • the flow is basically similar to a flow of settlement processing in the case of CFR, but there is a difference in a flow of payment of freight. Therefore, a section of processing for paying freight (the processes of steps S 306 to S 308 in FIG. 14 ) in the case of FOB is described below.
  • the consignee node 100 A requests that the consignee node 400 A pay freight (step S 306 ′).
  • the settlement processing unit 134 of the consignee node 100 A transmits, to the consignee node 400 A, remittance information including at least a remittance source address, a remittance destination address, the purpose of remittance, and a remittance amount. It is assumed that the settlement processing unit 134 refers to a shipper, a consignee, and freight price on a bill of lading, and specifies the remittance information. However, this is not restrictive. Information that the consignee 3 has input in the consignee operation terminal 200 A may be used, or registered information on a system for predetermined transactions or on a system for virtual currency transactions may be referred to.
  • the consignee node 400 A remits an amount specified by the remittance amount from an electronic wallet of a consignee specified by the remittance source address to an electronic wallet of a carrier specified by the remittance destination address, and updates a freight payment settlement balance (step S 307 ′).
  • the consignee node 400 A reports a result of paying freight to the consignee node 100 A (step S 308 ′). Specifically, the consignee node 400 A transmits, to the consignee node 100 A, a result of remittance including a remittance status code and a transaction code.
  • FIG. 16 is a diagram illustrating an example of a flow of change-of-name processing. Change-of-name processing is started in a case where settlement processing in the case of trade terms illustrated in any of FIGS. 13 to 15 has been successful (completed).
  • the invoice processing unit 131 of the shipper node 100 B updates ownership of an invoice smart contract to the consignee 3 (step S 312 ). Specifically, the invoice processing unit 131 performs processing for rewriting the owner name 112 C of an invoice from the shipper 2 to the consignee 3 .
  • the invoice processing unit 131 of the shipper node 100 B shares a result of updating ownership with the consignee node 100 A, the carrier node 100 C, and the insurer node 100 E (step S 313 ). Specifically, the invoice processing unit 131 of the shipper node 100 B transmits an invoice code and an invoice status to each of the consignee node 100 A, the carrier node 100 C, and the insurer node 100 E in such a way that a result of updating is shared.
  • a change of name of an invoice in change-of-name processing has been described above. By performing this processing, an obligation of a change of name on a shipping document (an invoice) from the shipper 2 to the consignee 3 is fulfilled.
  • the bill-of-lading processing unit 132 of the carrier node 100 C updates the ownership of a bill-of-lading smart contract to the consignee 3 (step S 314 ). Specifically, the bill-of-lading processing unit 132 performs processing for rewriting the owner name 113 C of a bill of lading from the shipper 2 to the consignee 3 .
  • the bill-of-lading processing unit 132 of the carrier node 100 C shares a result of updating ownership with the shipper node 100 B, the consignee node 100 A, and the insurer node 100 E (step S 315 ). Specifically, the bill-of-lading processing unit 132 of the carrier node 100 C transmits a bill-of-lading code and a bill-of-lading status to each of the shipper node 100 B, the consignee node 100 A, and the insurer node 100 E in such a way that a result of updating is shared.
  • a change of name of a bill of lading in change-of-name processing has been described above. By performing this processing, an obligation of a change of name on a shipping document (a bill of lading) from the shipper 2 to the consignee 3 is fulfilled.
  • the insurance policy processing unit 133 of the insurer node 100 E updates the ownership of an insurance policy smart contract to the consignee 3 (step S 316 ). Specifically, the insurance policy processing unit 133 performs processing for rewriting the owner name 115 C of an insurance policy from the shipper 2 to the consignee 3 .
  • the insurance policy processing unit 133 of the insurer node 100 E shares a result of updating ownership with the shipper node 100 B, the consignee node 100 A, and the carrier node 100 C (step S 317 ). Specifically, the insurance policy processing unit 133 of the insurer node 100 E transmits an insurance policy code and an insurance policy status to each of the shipper node 100 B, the consignee node 100 A, and the carrier node 100 C in such a way that a result of updating is shared.
  • a change of name of an insurance policy in change-of-name processing has been described above. By performing this processing, an obligation of a change of name on a shipping document (an insurance policy) from the shipper 2 to the consignee 3 is fulfilled.
  • FIGS. 13 to 15 and the change-of-name processing illustrated in FIG. 16 are indivisible processing, and when the entirety of the settlement processing and the change-of-name processing that have been described above has been successful (completed) normally, effects are exhibited. In a case where part of the processing fails to be completed, the entirety of the settlement processing and the change-of-name processing is discarded. Stated another way, the processing returns to a state before the start of the settlement processing and the change-of-name processing.
  • FIG. 17 is a diagram illustrating an example of a consignee screen.
  • a consignee screen 600 indicates an example of a status display screen that is displayed in a state where the consignee 3 has logged in to the consignee node 100 A.
  • a contract list 601 is displayed in a list form, and in each contract of the list, “type of contract” 602 , “contract reference” 603 , “contract status” 604 , and “document owner” 605 are displayed.
  • FIG. 18 is a diagram illustrating an example of a shipper screen.
  • a shipper screen 700 indicates an example of a status display screen that is displayed in a state where the shipper 2 has logged in to the shipper node 100 B.
  • the shipper screen 700 includes a policy summary field 701 and an electronic wallet field 730 of a shipper.
  • items of a policy and values of the items, a premium payment status 702 , and an insurance owner 703 are displayed.
  • the electronic wallet field 730 a wallet balance 731 , a billed amount of payment 732 , and a balance after payment 733 are displayed.
  • the insurer 6 can also view a similar screen.
  • invoice preparation approval processing bill-of-lading preparation approval processing
  • insurance policy preparation approval processing settlement processing
  • change-of-name processing is not restrictive.
  • EXW free carrier
  • FCA free alongside ship
  • CPT carriage paid to
  • CIP carriage and insurance paid to
  • DAF delivered at frontier
  • DES delivered ex ship
  • DEQ delivered duty unpaid
  • DDU delivered duty paid
  • DDP delivered duty paid
  • the present invention is not limited to the embodiment described above Various modifications can be made to the embodiment described above without departing from technical ideas of the present invention.
  • the distributed ledger node 100 and the electronic wallet node 400 are configured by computers different from each other, but this is not restrictive.
  • the distributed ledger node 100 and the electronic wallet node 400 may be configured by the same computer. In such a case, efficiency of arithmetic processing can be improved. Therefore, even in a large-scale platform, the flexible utilization of hardware resources can be easily achieved.
  • technical elements of the embodiment described above may be independently applied, or the technical elements may be divided into a plurality of portions such as program parts and hardware parts, and may be applied.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Technology Law (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
US17/635,199 2019-08-14 2019-08-14 Trade settlement system, trade settlement method, and trade settlement program Pending US20220292467A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2019/031925 WO2021029029A1 (ja) 2019-08-14 2019-08-14 貿易決済システム、貿易決済方法および貿易決済プログラム

Publications (1)

Publication Number Publication Date
US20220292467A1 true US20220292467A1 (en) 2022-09-15

Family

ID=74570957

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/635,199 Pending US20220292467A1 (en) 2019-08-14 2019-08-14 Trade settlement system, trade settlement method, and trade settlement program

Country Status (5)

Country Link
US (1) US20220292467A1 (ja)
EP (1) EP4016425A4 (ja)
JP (1) JP7083031B2 (ja)
CN (1) CN114207644A (ja)
WO (1) WO2021029029A1 (ja)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220335494A1 (en) * 2020-10-09 2022-10-20 Alipay (Hangzhou) Information Technology Co., Ltd. Managing blockchain-based trustable transaction services
US11935048B2 (en) 2020-10-09 2024-03-19 Alipay (Hangzhou) Information Technology Co., Ltd. Managing blockchain-based trustable transaction services

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210150597A1 (en) * 2019-11-20 2021-05-20 International Business Machines Corporation Automated invoicing
CN113095747B (zh) * 2021-03-04 2022-05-17 支付宝(杭州)信息技术有限公司 基于区块链技术的电子提单流转方法及装置
WO2022190181A1 (ja) * 2021-03-08 2022-09-15 株式会社日立物流 物流荷物所在共有システム、物流荷物所在共有方法及びそのプログラム

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4927150B2 (ja) 2009-10-30 2012-05-09 株式会社日本総合研究所 貿易決済関連データ管理システムおよびその方法
WO2017098519A1 (en) * 2015-12-08 2017-06-15 Tallysticks Limited A system and method for automated financial transaction validation, processing and settlement using blockchain smart contracts
CA3027630A1 (en) * 2016-07-01 2018-01-04 Wells Fargo Bank, N.A. International trade finance blockchain system
JP6718980B2 (ja) * 2017-06-30 2020-07-08 株式会社三井住友銀行 貿易取引のためのシステム、方法、およびプログラム

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220335494A1 (en) * 2020-10-09 2022-10-20 Alipay (Hangzhou) Information Technology Co., Ltd. Managing blockchain-based trustable transaction services
US11798050B2 (en) * 2020-10-09 2023-10-24 Alipay (Hangzhou) Information Technology Co., Ltd. Managing blockchain-based trustable transaction services
US11935048B2 (en) 2020-10-09 2024-03-19 Alipay (Hangzhou) Information Technology Co., Ltd. Managing blockchain-based trustable transaction services

Also Published As

Publication number Publication date
EP4016425A4 (en) 2023-04-12
EP4016425A1 (en) 2022-06-22
CN114207644A (zh) 2022-03-18
JP7083031B2 (ja) 2022-06-09
JPWO2021029029A1 (ja) 2021-09-13
WO2021029029A1 (ja) 2021-02-18

Similar Documents

Publication Publication Date Title
US20220292467A1 (en) Trade settlement system, trade settlement method, and trade settlement program
WO2017098519A1 (en) A system and method for automated financial transaction validation, processing and settlement using blockchain smart contracts
US20190139136A1 (en) Systems and methods for trading, clearing and settling securities transactions using blockchain technology
JP4677188B2 (ja) 統合サプライチェーンシステム中の管理、資金供給および供給方法と装置
US20200380505A1 (en) Auto-pilot transactions using smart contracts
US20190295046A1 (en) Settlement facilitation hub
US20190340697A1 (en) Method and system for administering life insurance products through classifying insured lives to allocate costs
WO2022046123A1 (en) User-controlled currency conversion system and method
JP2018055235A (ja) 債券取引決済管理システムおよび債券取引決済管理方法
US20140244342A1 (en) Accounting for contract formation and fulfillment activities
JP2018124640A (ja) 貿易支援方法、仮想通貨管理方法、貿易支援システム、仮想通貨管理システム、貿易支援プログラム、および仮想通貨管理プログラム
WO2019162915A1 (en) System for managing an order between a client and a supplier
US20240020769A1 (en) Processing data for administering stable value products with pooling and capping of risk features utilizing computer-implemented methods and computer systems
US11170441B2 (en) System and method for enhanced electronic networked settlement processor
US11023972B2 (en) Financial transaction management system and financial transaction management method
EP4239556A1 (en) Method and apparatus for providing recommendations based on return data
US20240112276A1 (en) Microservice-based platform for management of insurance policies
WO2024124298A1 (en) Methods and systems for minting a stablecoin
United States. International Trade Administration Trade Finance Guide: A Quick Reference for US Exporters
JP2022191027A (ja) 情報処理方法、情報処理装置及びプログラム
JP2022070335A (ja) プログラム、情報処理方法、及び情報処理装置
IES86476B2 (en) Cloud chain sourcing and trade management orchestration platform
IES86476Y1 (en) Cloud chain sourcing and trade management orchestration platform

Legal Events

Date Code Title Description
AS Assignment

Owner name: TOKIO MARINE & NICHIDO FIRE INSURANCE CO., LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SHINYA, TETSUNOSUKE;REEL/FRAME:059014/0483

Effective date: 20220124

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED