Avalara, Inc.

Systems and methods electronically provide information regarding digital rules related to a potential relationship instance. Users often wish to know which digital rules apply to a specified item before engaging in a relationship instance with a host entity regarding the item. The system and methods described herein allow a computing facility to identify an item and receive resource information related to the item and the digital rules applicable to the item.

Systems and methods electronically tag received data associated with an entity with an electronic tag including an identifier uniquely associated with the entity. The system may electronically store the received data such that the received data is identifiable via the electronic tag. Then, when a request for deletion of all the entity's data is made by the particular entity, it is fulfilled with much less effort, namely by searching for elements with that entity's tag. Whenever that data is copied, transformed, or derivative data is made, the system copies the electronic tag with it. Thus, even when the data is copied or modified, it can be more efficiently identified as being associated with the particular entity. In some embodiments, the tagging includes electronically recording an association of the electronic tag with the received data as a transaction on a blockchain, the transaction on the blockchain being associated with the electronic tag and with the received data.

An embodiment is a method performed by a computer system of an online software platform (OSP). The method includes receiving, via a network, a set of datasets of relationship instances that are associated with a primary entity, a domain from a plurality of domains, and a time period and maintaining a cumulative base value associated with the primary entity, the domain, and the time period. The method further includes responsive to determining that the cumulative base value exceeds a predefined threshold value, changing a reporting period length associated with the primary entity and the domain from a first reporting period length to a second reporting period length that is shorter than the first reporting period length and causing a report to be prepared and transmitted via the network to a computer system of the domain using the second reporting period length.

A method performed by a computer system of an online software platform (OSP). The method includes receiving, via a network, a first set of datasets of relationship instances that are associated with a domain from a plurality of domains and a first time period, identifying patterns in the first set of datasets with respect to one or more monitored parameters, receiving, via the network, a second set of datasets of relationship instances that are associated with an entity, the domain, and a second time period that comes after the first time period, determining whether a discontinuity exists in the second set of datasets with respect to the one or more monitored parameters based on comparing values corresponding to the one or more monitored parameters in the second set of datasets against the patterns, and performing a reactive action responsive to determining that the discontinuity exists.

In embodiments, in processes that can be repeated numerous times, relationship instance data is inputted, of relationship instances between primary entities and secondary entities. For a relationship instance, an outbound dataset is constructed that has dataset parameters with respective dataset values. One of the dataset values characterizes an attribute of one of the entities, and another encodes a base value for the relationship instance data. The outbound dataset is transmitted across a network to an Online Software Platform (OSP) computer system. The OSP computer system produces, according to digital rules, two or more resources for the dataset, and an inbound dataset is returned with the results, for forwarding to an output device. Handling settings are also inputted by a UI. Depending on the handling settings, one of the resources is added, or not, to the base value for a user as part of forwarded results.

A specialized service engine receives data from an entity located in one domain about transactions performed by the entity with other entities from another domain. The service engine determines if the entity must follow the rules regarding selected resources in the other domain. The service engine then determines which of the rules established by the other domain the entity must follow. The service engine then determines and communicates to another computer of the entity the burden of complying with the rules of the other domain. The service engine then further computes the cost of the burden, and communicates the computed cost to the other computer.

An Online Software Platform (OSP) may receive a first dataset from a remote client device, and compute an estimated resource, from the first dataset and also per stored digital rules. The OSP may then communicate an aspect of the resource to the remote client device and receive a confirmation of the first dataset. The OSP may then process the first dataset, for matching it with another dataset, either internally or by outsourcing. Either way, the OSP may establish that the first dataset has been matched with a compatible second dataset. The OSP may then input a resource for the first dataset, which is determined according to stored digital rules. The OSP may further create one or more notifications and documents about the matching and the resource, and make them available to the remote client device or even to the device of another remote entity.

In embodiments, given a surface that has domains on it and a first location, a second location is generated in the surface. The second location belongs in the same domains as the first location, and does not belong in the same domains as the second location. An advantage can be that, in embodiments, the second location can be used in lieu of the first location. A use case can be where it is desired to protect the privacy of location data of an entity, such as its address.

In embodiments, computer systems, computer-readable media, and methods perform operations such as deliver, on behalf of a primary entity, data reports to domains. However, before delivering, they check to see if such a data report has already taken delivered, perhaps inadvertently, in case the primary entity had given duplicative instructions for the delivery. The checking can start either directly with a domain online space of the domain itself, or by exploring a partner online space of a partner entity. In each case, the primary entity provides credentials for access to an online space, and of course permission. Access to the online space is accomplished via the credentials, an inquiry is transmitted to the online space, and inquiry results are received in response to the transmitted inquiry. The inquiry results are analyzed and, if it is determined that such a delivery has taken place, the primary entity is notified.

Some embodiments of the present disclosure may relate generally to software-based service platforms and graphical user interface (GUI) architectures for determining and presenting rule-based conclusions, along with explanations identifying the factor or factors influencing the conclusions. Other embodiments may be disclosed and/or claimed.