Abstract: During an analysis technique, information associated with two entities may be compared to determine a similarity metric. For example, a string distance between the information may be computed. Then, an association metric between financial-transaction histories for the two entities may be calculated. This calculation may involve comparing the nodes and branches in a commerce graph that represents financial interrelationships among a set of entities, including inputs received by the set of entities, outputs provided by the set of entities, and financial transactions among the set of entities. Next, a determination of whether the entities are likely to be a same entity may be based on the similarity metric and/or the association metric. If the entities are likely to be the same entity, the entities may be combined in a data structure. Alternatively, if the entities are not likely to be the same, they may remain separate.

Abstract: A method for payment management includes identifying an invoice for a target financial transaction between a customer and a target vendor, and obtaining financial transaction records for completed financial transactions between the customer and vendors. The vendors include comparable vendors and the target vendor. The method further includes generating, using the financial transaction records, a payment prediction for the customer to pay the target vendor, analyzing a subset of the financial transaction records for the comparable vendors to generate a recommendation, and presenting, in a graphical user interface, the payment prediction and the recommendation.

Abstract: A method for collecting a payment. The method includes sending, to a payor, a request for the payment, wherein the request comprises an original payment amount and an original payment due date, generating, based on a set of payment collection records from an online financial management application used by payees, a payment statistical measure representing a payment behavior of payors paying the payees, generating, based on the payment statistical measure, the original payment amount, and the original payment due date, an adjusted payment amount and a condition to qualify the adjusted payment amount for completing the payment, enabling, prior to the payor completing the payment, the payor to view the adjusted payment amount and the condition, wherein the payor completes the payment in response to at least the payor viewing the adjusted payment amount and the condition, and collecting the payment completed by the payor.

Abstract: The disclosed embodiments provide a system that facilitates business interaction. During operation, the system identifies a non-registered entity associated with an interaction within a commerce network. Next, the system enables, for the non-registered entity, access to an artifact associated with the interaction without requiring authentication of the non-registered entity.

Abstract: The disclosed embodiments provide a system that facilitates business interaction. During operation, the system obtains a model of a commerce network containing a set of entities, a set of relationships among the entities, a set of interactions related to commerce among the entities, and a set of activities associated with the entities. Next, the system uses the model to enable an interaction among two or more entities from the set of entities independently of a set of endpoints used by the entities to access the commerce network.

Abstract: The disclosed embodiments provide a system that facilitates business interaction. During operation, the system identifies a non-registered entity associated with an interaction within a commerce network. Next, the system enables, for the non-registered entity, access to an artifact associated with the interaction without requiring authentication of the non-registered entity.

Abstract: One embodiment of the present invention provides a software domain model that enables simultaneous independent development of software components. A system using this model includes a first component, a second component, and a core layer that defines an item that can be accessed by the first and second components. Both components are able to independently and separately extend the definition of the item. A high-level software layer uses a set of micro-orchestrations to perform a holistic task, with each micro-orchestration invoking a piece of functionality in a component, the core layer, and/or the software layer.

Abstract: One embodiment of the present invention provides a software domain model that enables simultaneous independent development of software components. A system using this model includes a first component, a second component, and a core layer that defines an item that can be accessed by the first and second components. Both components are able to independently and separately extend the definition of the item. A high-level software layer uses a set of micro-orchestrations to perform a holistic task, with each micro-orchestration invoking a piece of functionality in a component, the core layer, and/or the software layer.