Intuit, Inc.

Calum G Murray

Jeffrey Moreno Collins

Jeffrey A Langston

John J Tumminaro

Roger Charles Meike

Roy Goldman

Per-Kristian G Halvorsen

Gerald Baron Huff

Cem Unsal

John Robert Shapiro

Kevin Michael Furbish

Bruce Wobbe

Todd Elliott

James Lee Showalter

Jason Hardiman

Erica S Bjornsson

Devin W Breise

Jacqueline Wilkosz

Victor Feinstein

Denise McInerney

Keith Anders Olson

Raymond J Chapman

John D Wannamaker

Jeff Mendonca

Robert A Luben

Certain aspects of the present disclosure provide techniques for providing a compliance report of data processing to a governing authority. In order to adhere to a regulation of a governing authority, upon receiving the request for a compliance report, a data category and each processing capability category is extracted from a live data catalog service. Based on the extracted categories, a record of data processing is generated for each processing capability category associated with a data category. Further, based on the data category extracted, a compliance report template is retrieved. With the compliance report template and records of data processing, a compliance report is generated and provided to the governing authority.

Generating a compliance report of data processing activity

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.

Disambiguation of entities based on financial interactions

A method for transaction verification scoring includes obtaining, from a distributed computing system of distributed computing systems distributed throughout a computing network, a transaction description describing a financial transaction with a vendor, obtaining, from the distributed computing systems, transaction records of potential corroborators, and reconciling, with the financial transaction, the transaction records to obtain at least one matching transaction record of at least one corroborator, in the potential corroborators, to the financial transaction. The method further includes scoring the transaction description based on a function of each of the at least one corroborator to the financial transaction to obtain a verification score, and presenting, on a display device, a recommendation of the vendor to a consumer based on the verification score.

Transaction validation scoring

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.

Customized payment management

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.

Gamification of fields in online e-commerce documents

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.

Unauthenticated access to artifacts in commerce networks

One embodiment of the present invention provides a system for implementing a persistence application programming interface (API) that is platform independent and can make up-calls to business logic. During operation, the system receives a request at the API to execute a command at a persistence tier of an n-tier distributed application. In response to the request, the system determines an entity type for an entity affected by the command. Next, the system identifies a function at a middle tier of the n-tier distributed application that is associated with the entity type and the command, wherein the middle tier includes the business logic. The system then sends an instruction to the middle tier to execute the function. Finally, upon receiving a confirmation at the API that the function executed, the system executes the command at the persistence tier.

Method and apparatus for facilitating a persistence application programming interface

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.

Software domain model that enables simultaneous independent development of software components

Physical components that share common attributes in a software product are combined into logical groupings. A product matrix also lists logical groupings that are included into each software product listed in the product matrix. A compatibility matrix indicates whether any two logical groupings listed in the product matrix are compatible. When a new product is provided for an installation, the compatibility matrix is consulted to determine whether any two logical groupings of the new product and installed product are compatible. An installation can proceed or be terminated based on the compatibility determination.

Management of compatibility of software products installed on a user's computing device

One embodiment of the present invention provides a system that transparently maps a request to open a data file. First, the system receives a request from a user or client application to open the data file. Next, the system determines from file meta information that the file is a relational data file, and proceeds to transparently map the file open operation to a corresponding relational database operation by discovering a database service configured to manage the relational data file and then sending a request to open the relational data file to this database service. By transparently mapping the file open operation to the corresponding relational database operation, the system allows an underlying data file to be changed to a relational data file without changing the way the user interacts with the client application and/or data file.

Method and apparatus for transparently mapping a request to open a data file

A security mechanism affords data recovery engineers the ability to access and recover secure data from user files without knowledge of the user's password. The mechanism uses a launcher application to access the database by establishing a temporary, restricted user session. The launcher application also passes a handle to an industry standard database tool, allowing the data recovery engineer to recover the user file data. The recovered data then can be accessed by the software application.

Growing community of inventors

Santa Rosa, CA, United States of America

Calum G Murray