Abstract: Embodiments are described for a digital currency hub (DCH) comprising a memory and a processor. The processor is configured to receive a confirmation of a transaction. The confirmation indicates a first amount in a first cryptocurrency (the “transaction amount”) and a second amount in a second cryptocurrency (the “network fee”). The processor is further configured to adjust a first position corresponding to the first cryptocurrency based on the first amount and adjust a second position corresponding to the second cryptocurrency based on the second amount. The adjustments can be pro-rata. The processor is further configured to calculate gains or losses based on the adjustments of the positions. In some embodiments, the DCH enables the ERP system to handle cryptocurrencies according to the rules of various accounting principles in parallel, because the ERP system is not compatible or capable of handling digital transactions with respect to accounting regulations directly.

Abstract: Embodiments are described for a digital currency hub (DCH) comprising a memory and a processor. The processor is configured to receive a payment request from an enterprise resource planning (ERP) system and determine a first cryptocurrency, a cryptocurrency network, and a wallet address. The payment request indicates a first amount in a fiat currency. The processor is further configured to determine a first amount and transmit a payment command to the cryptocurrency network indicating the first cryptocurrency, the first amount, and the wallet address. The processor is further configured to receive a payment confirmation and generate a first account statement indicating the first amount and a business partner. The ERP system uses entities and processes, such as a fiat currency, accounts, business partners, and account statements, to communicate with the DCH. The DCH takes care to translate the entities and processes so that payments can be executed via crypto networks.

Abstract: A procedure and address data store contains electronic records, and each master data record contains a pre-shared master address for a procedure originator. A procedure responder verifies a pre-shared master address associated with an originator. The master address is the root node of the destination addresses in a hierarchical tree of destination addresses. Each child address is derived from a parent address using a record identifier (e.g., an invoice or payment reference) and a cryptographic key derivation algorithm. The responder receives, from the originator, a procedure record including a record identifier associated with a procedure. The responder then predicts the destination address based on the pre-shared master address associated with the originator, the record identifier, and the algorithm. It is then arranged for the responder to complete the procedure with the originator via the predicted destination address, and information about the completed procedure is stored in a distributed ledger.

Abstract: This disclosure describes systems, software, and computer implemented methods including receiving a request from a second entity to transfer a digital asset to a first entity. Receiving a request for an address and public key is sent to an asset custody application executing on a device that is managed by the first entity. Receiving, a public key and a wallet address and sends the wallet address to the second entity. Further this disclosure describes receiving a request to transfer a digital asset from a first entity to a second entity. Generating a transaction package pursuant to the one or more parameters, the transaction package including a transaction and a public key of a digital wallet associated with the first entity. Executing the transaction and sending the signed transaction package to a distributed ledger.

Abstract: This disclosure describes systems, software, and computer implemented methods including receiving a request from a second entity to transfer a digital asset to a first entity. Receiving a request for an address and public key is sent to an asset custody application executing on a device that is managed by the first entity. Receiving, a public key and a wallet address and sends the wallet address to the second entity. Further this disclosure describes receiving a request to transfer a digital asset from a first entity to a second entity. Generating a transaction package pursuant to the one or more parameters, the transaction package including a transaction and a public key of a digital wallet associated with the first entity. Executing the transaction and sending the signed transaction package to a distributed ledger.

Abstract: Systems, methods, and computer media for implementing a process map navigation tool are provided herein. A process map provides a graphical user interface that represents a process. Icons represent process components or steps and are related using flow connectors to indicate an ordered relationship between the process components. Users can click on an icon and either initiate the corresponding process component or launch a menu of tasks relevant to the step. The icons can also include indicators to provide workflow information.

Abstract: Systems, methods, and computer media for implementing a process map navigation tool are provided herein. A process map provides a graphical user interface that represents a process. Icons represent process components or steps and are related using flow connectors to indicate an ordered relationship between the process components. Users can click on an icon and either initiate the corresponding process component or launch a menu of tasks relevant to the step. The icons can also include indicators to provide workflow information.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a request for information, a request for information response, a supplier assessment profile, a supplier questionnaire assessment, and/or a supplier transaction assessment business object.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: A business object model, which reflects data that used during a given business transaction, is utilized to generate interfaces This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.