An example operation may include one or more of monitoring, by a blockchain node, a delivery of a service to a first node from a second node based on a service contract and an order retrieved from a blockchain, determining, by the blockchain node, an incremental charge for a partial delivery of the service based on the monitoring, and executing, by the blockchain node, a smart contract to issue the incremental charge for the partial delivery of the service, and responsive to a resolution of a dispute raised for the incremental charge, add the incremental charge to an incremental invoice.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
2. The system of claim 1, wherein the final invoice includes an incremental invoice that supplements the partial invoice.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. This system is further configured such that the final invoice for the completed service includes an incremental invoice, which supplements a previously issued partial invoice.
3. The system of claim 1, wherein the detected delivery of the first service to the first node from the second node is based on a service contract retrieved from the blockchain ledger.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The monitoring and detection of this service delivery is specifically based on a service contract that has been retrieved from the blockchain ledger.
4. The system of claim 1, wherein the processor is further configured to execute the blockchain smart contract to generate the final invoice in response to a reconciliation of an incremental charge by the first node or by the second node.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The system's processor is further configured to execute a blockchain smart contract to generate the final invoice for the service once an incremental charge has been reconciled (approved or settled) by either the first node (service recipient) or the second node (service provider).
5. The system of claim 1, wherein the processor is configured to commit an intermediate status of the second service delivery to the blockchain ledger.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The system's processor is further configured to commit an intermediate status or progress update of the ongoing service delivery to the blockchain ledger, ensuring its transparency and immutability.
6. The system of claim 5, wherein the intermediate status of the second service del Try is recorded as a blockchain transaction.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. This system is configured to commit an intermediate status of the ongoing service delivery to the blockchain ledger, and this intermediate status is specifically recorded as a verifiable blockchain transaction.
7. The system of claim 1, wherein the processor is further configured to receive consent from the first node and from the second node to commit the partial invoice and the final invoice to the blockchain ledger.
A system for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. Additionally, the system's processor is configured to obtain explicit consent from both the first node (recipient) and the second node (provider) before finalizing and storing both the partial invoice and the final invoice onto the blockchain ledger.
9. The method of claim 8, wherein the final invoice includes an incremental invoice supplementing the partial invoice.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. This method further includes the step where the final invoice for the service delivery is constructed to include an incremental invoice, which serves to supplement or build upon a previously generated partial invoice.
10. The method of claim 8, wherein the detected delivery of the first service to the first node from the second node is based on a service contract retrieved from the blockchain ledger.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. A key aspect of this method is that the detection of the service delivery itself relies on a specific service contract that has been retrieved from the blockchain ledger.
11. The method of claim 8, comprising executing the blockchain smart contract to generate the final invoice in response to a reconciliation of an incremental charge by the first node or by the second node.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The method further comprises executing a blockchain smart contract specifically to generate the final invoice, triggered by the reconciliation (approval or settlement) of an incremental charge by either the first node (recipient) or the second node (provider).
12. The method of claim 8, comprising committing an intermediate status of the second service delivery to the blockehain ledger.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. This method also includes the step of saving an intermediate status or progress update of the ongoing service delivery directly onto the blockchain ledger, ensuring its transparency and immutability.
13. The method of claim 12, wherein the intermediate status of the second service delivery is recorded as a blockchain transaction.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The method includes saving an intermediate status of the ongoing service delivery onto the blockchain ledger, with this intermediate status specifically being recorded as a verifiable blockchain transaction to ensure its integrity.
14. The method of claim 8, comprising receiving consent from the first node and from the second node to commit the partial invoice and the final invoice to the blockchain ledger.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery from a second node to a first node, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. A further step in this method involves receiving explicit consent from both the first node (recipient) and the second node (provider) before proceeding to commit (store) both the partial invoice and the final invoice onto the blockchain ledger.
16. The non-transitory computer readable medium of claim 15, wherein the final invoice includes an incremental invoice supplementing the partial invoice.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The method further involves generating a final invoice that includes an incremental invoice, which supplements a partial invoice previously generated for the service.
17. The non-transitory computer readable medium of claim 15, wherein the detected delivery of the first service to the first node from the second node is based on a service contract retrieved from the blockchain ledger.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. In this method, the detection of the service delivery to the first node from the second node is specifically based on a service contract that has been retrieved from the blockchain ledger.
18. The non-transitory computer readable medium of claim 15, wherein the method further comprises executing the blockchain smart contract to generate the final invoice in response to a reconciliation of an incremental charge by the first node or by the second node.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The stored instructions further cause the processor to execute a blockchain smart contract to generate the final invoice once an incremental charge has been reconciled (approved or settled) by either the first node (recipient) or the second node (provider).
19. The non-transitory computer readable medium of claim 15, wherein the method further comprises committing an intermediate status of the second service delivery to the blockchain ledger.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The stored instructions also cause the processor to save an intermediate status or progress update of the ongoing service delivery directly onto the blockchain ledger, ensuring its transparency and immutability.
20. The non-transitory computer readable medium of claim 19, wherein the e nediate status of the second service delivery is recorded as a blockchain transaction.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The stored instructions further cause the processor to save an intermediate status of the ongoing service delivery onto the blockchain ledger, with this intermediate status specifically being recorded as a verifiable blockchain transaction.
21. The non-transitory computer readable medium of claim 15, wherein the method further comprises receiving consent from the first node and from the second node to commit the partial invoice and the final invoice to the blockchain ledger.
A non-transitory computer readable medium stores instructions that, when executed by a processor, cause it to perform a method of optimizing trusted invoicing. This method involves monitoring service delivery between nodes, determining incremental charges for partial deliveries, executing smart contracts to issue these charges, and adding them to incremental invoices after dispute resolution. The stored instructions also cause the processor to receive explicit consent from both the first node (recipient) and the second node (provider) before committing (storing) both the partial invoice and the final invoice to the blockchain ledger.
23. The system of claim 22, wherein the processor is further configured to execute the blockchain smart contract to generate a final invoice based on the incremental invoice and the second incremental invoice.
A system for optimizing trusted invoicing includes a blockchain node configured to monitor service delivery, determine charges for partial deliveries, and issue multiple incremental invoices. The processor in this system is further configured to execute a blockchain smart contract to generate a comprehensive final invoice, which is based on combining the data from both a first incremental invoice and a second incremental invoice.
25. The method of claim 24, comprising executing the blockchain smart contract to generate a final invoice based on the incremental invoice and the second incremental invoice.
A method for optimizing trusted invoicing involves a blockchain node monitoring service delivery, determining charges for partial deliveries, and issuing multiple incremental invoices. This method specifically comprises executing a blockchain smart contract to generate a comprehensive final invoice, where this final invoice is compiled from the data contained within both a first incremental invoice and a second incremental invoice.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
September 2, 2022
March 26, 2024
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.