Abstract: In some implementations, techniques may include accessing stored payment data. For each payment term of a plurality of payment terms, the techniques may include calculating a distribution of payment dates before, on, and after a due date. The techniques may include determining the effectiveness of each of a plurality of payment terms based in part on the distribution of payment dates, where effectiveness is defined as a time difference between a payment due date and a payment date. The techniques may include determining a recommended payment term based at least in part on the effectiveness of each of the plurality of payment terms and an objective. The techniques may include generating an invoice including the recommended payment term.

Abstract: Each event type in a business process is represented by a node in a process discovery graph. Semantic clustering merges nodes based on a commonality between them. As a result, a graphical user interface (GUI) may be presented that shows fewer nodes. This process may be repeated, using different commonalities at each level. A user may select a node to zoom in, showing the constituent nodes. The frequency of an event or its other attribute values may be compared to a predetermined threshold to determine if the event is a blocking event. The GUI may indicate that the node for an event is a blocking event. When the node for the event is merged with other nodes using semantic clustering, the blocking status of the node is transferred to the merged node. After zooming in on the blocking event, the GUI allows the user to select the blocking event to cause display of a recommendation.

Abstract: The present disclosure provides techniques and solutions for benchmarking process models by evaluating characteristics of the model, such as those reflecting model complexity. Metrics can include the number of elements in a model, the number of roles, and the number of handoffs between roles, as a few examples. Metrics for a model can be compared with reference metrics, such as those calculated from a set of other models, which can be for the same modeled process or different processes. Collections of process models can be evaluated in a similar manner, including for a set of related models that may be expressed at different levels of specificity. Metrics for individual models in the collection can be evaluated and aggregated, and then compared with aggregated metric values of other model collections, for the same or different modeled processes.

Abstract: In an example embodiment, a machine learning model is trained to predict one or more transportation modes for a portion of a process flow (such as a shipment). This prediction may be based on, for example, the size and weight of the shipment, the distance and geographical features of the distance between the pickup location for the shipment and the delivery location for the shipment. Based on the prediction as well as a calculated metric called “risk of inaccuracy”, a sustainability score may be calculated for the shipment. The sustainability score may then be used to recommend one or more actions to adjust a process flow that includes the shipment to reduce environmental impact of the shipment and future similar shipments.

Abstract: The present disclosure provides techniques and solutions for improving computer-implemented processes. Process mining is performed to identifying processes of a first entity. Characteristics of the first entity at a first time are used to identify a set of reference entities having similar characteristics to the first entity at a second, earlier time. Process mining is performed for the set of reference entities to identify process changes that led to process improvements for the set of reference entities. These process changes are used to suggest process changes to the first entity that may improve performance of the process.

Abstract: The example embodiments are directed to systems and methods which may provide a guided user interface session for user input to a software process based on annotations added to a process model of the software process. In one example, a method may include receiving runtime data of an instance of software process from a workflow engine that is executing the instance of the software process, determining a process activity that is excepted to happen next within the running instance of the software process, identifying GUI and a subset of input elements within the GUI which are mapped to the determined process activity based on annotations within a process model of the software process, highlighting the identified subset of input elements and disabling any remaining input elements within the GUI to generate a guided GUI, and displaying the guided GUI via a computing system of a user.

Abstract: Provided is a system and method for filtering data records via user interaction on a user interface. During the filtering process, the user interface can provide insights into the next filtering step by displaying additional insight on the user interface. In one example, the method may include displaying a user interface comprising interactive controls, receiving a selection of a filtering condition based on input on the user interface, in response to the selection, filtering a plurality of data records based on the selected filtering condition to identify a subset of data records that satisfy the filtering condition from among the plurality of data records, identifying a subset of filtering conditions from among the plurality of filtering conditions that are available for the subset of data records, and displaying an identifier of the subset of data records and identifiers of the subset of filtering conditions on the user interface.

Abstract: The example embodiments are directed to systems and methods which may provide a guided user interface session for user input to a software process based on annotations added to a process model of the software process. In one example, a method may include receiving runtime data of an instance of software process from a workflow engine that is executing the instance of the software process, determining a process activity that is excepted to happen next within the running instance of the software process, identifying GUI and a subset of input elements within the GUI which are mapped to the determined process activity based on annotations within a process model of the software process, highlighting the identified subset of input elements and disabling any remaining input elements within the GUI to generate a guided GUI, and displaying the guided GUI via a computing system of a user.

Abstract: An access management system comprises one or more databases and one or more computers. The one or more databases may store access data, accessor data, restriction data, and/or biometric data. The one or more computers may comprise an account identifier management computer, an authorization server computer, and/or an account management server computer. The account identifier management computer may generate account identifiers for physical or virtual cards. The cards may have interface-specific account identifiers. The authorization server computer may be communicatively coupled to an account access system that is used to obtain account identifiers as input. The authorization server computer may apply one or more restrictions to an account identifier. The account identifier management server computer may enable monitoring account activity and/or generate ephemeral phone numbers that can be used to authenticate callers to call recipients.

Abstract: An access management system includes a database configured to store access data including account identifiers and accessor identifiers, wherein the access data indicates particular accounts that have been accessed by particular accessors. The access management system also includes a computer system that receives a reservation request comprising an account identifier and an accessor identifier and determines whether the account identifier is included in the database. The computer system also determines, in response to the account identifier being present in the database, whether the access data correlates the account identifier to the accessor and authorizes the reservation of the one or more resources in the account by the accessor in response to the access data correlating the account identifier to the accessor.

Abstract: An access management system includes a database configured to store access data including account identifiers and accessor identifiers, wherein the access data indicates particular accounts that have been accessed by particular accessors. The access management system also includes a computer system that receives a reservation request comprising an account identifier and an accessor identifier and determines whether the account identifier is included in the database. The computer system also determines, in response to the account identifier being present in the database, whether the access data correlates the account identifier to the accessor and authorizes the reservation of the one or more resources in the account by the accessor in response to the access data correlating the account identifier to the accessor.

Abstract: An access management system comprises one or more databases and one or more computers. The one or more databases may store access data, accessor data, restriction data, and/or biometric data. The one or more computers may comprise an account identifier management computer, an authorization server computer, and/or an account management server computer. The account identifier management computer may generate account identifiers for physical or virtual cards. The cards may have interface-specific account identifiers. The authorization server computer may be communicatively coupled to an account access system that is used to obtain account identifiers as input. The authorization server computer may apply one or more restrictions to an account identifier. The account identifier management server computer may enable monitoring account activity and/or generate ephemeral phone numbers that can be used to authenticate callers to call recipients.

Abstract: An access management system includes a database configured to store access data including account identifiers and accessor identifiers, wherein the access data indicates particular accounts that have been accessed by particular accessors. The access management system also includes a computer system that receives a reservation request comprising an account identifier and an accessor identifier and determines whether the account identifier is included in the database. The computer system also determines, in response to the account identifier being present in the database, whether the access data correlates the account identifier to the accessor and authorizes the reservation of the one or more resources in the account by the accessor in response to the access data correlating the account identifier to the accessor.