Example Use-Case
We now consider an example use case of a procurement process, with the potential to exit into a tokenized invoice.
In the initialization phase, participants of the business process set up organization registries, workgroup shields and workflow verifiers, according to the Baseline Protocol.
In the phase of (repeated) worksteps, the participants baseline their business process. The document flow starts with purchase orders, and continues with order confirmations, shipping notifications, goods receipts and subsequently invoices.
These documents, coming from one participant’s System of Record (SoR, for example an SAP ERP) are transformed into a common domain model that all participants are able to read and write to, and then sent to suppliers over secure channels, according to the patterns of the Baseline Protocol.
Changes to the purchase order, e.g., due to quantity adjustments or material substitutes, are exchanged between the buyer and supplier to keep their respective systems of record in sync.
Proofs of state synchronization are notarized on Baseledger, the Mainnet, without revealing the sensitive content of the business data to third parties. In reference implementations, this happens automatically between different Provide and Unibright Baseline-as-a-Service stacks, a Protocol Pair Tuple and Baseledger itself.
In the exit phase, proof of the final state is notarized, for example into Ethereum, and can be used as a trigger for tokenization to enable automated payment or Enterprise DeFi (“Decentralized Finance”) applications.
Last modified 3mo ago
Copy link