US-20260127601-A1 - DIRECT TRANSACTION DATA ENTRY CODING AND INTEGRATION

US20260127601A1US 20260127601 A1US20260127601 A1US 20260127601A1US-20260127601-A1

Abstract

A system for annotating transactions includes a computing server configured to retrieve annotation requirements for transaction accounts of an organization client, where the annotation requirements specify a data field of a third-party platform's schema that is used to organize transaction data. The organization client may further specify which transactions need to be annotated using selection criteria. The computing server processes transactions incurred using the transaction accounts and identifies unannotated transactions using the selection criteria. End users who are responsible for annotating the unannotated transactions are provided direct links to annotate the unannotated transactions. Upon receiving annotations from the responsible end users, the computing server can display annotated transaction data for an administrator of the organization client.

Inventors

Veeral Dilip Patel
John Sarihan
Jaein Lee
Calvin Jun-Gong Lee
Geoffrey Jacques Charles
Jared Robert Wasserman
Diego D. Zaks Barrios
Ori Ephraim Goldfield
Serge Nasr
Tae Kyung KONG

Assignees

RAMP BUSINESS CORPORATION

Dates

Publication Date: 20260507
Application Date: 20251218

Claims (20)

1 . A computer-implemented method for reducing server-side processing resources in annotating schema-specific transaction data, comprising: receiving annotation requirements from an organization client, the requirements identifying a third-party platform and at least one data field of a data schema used by the platform; identifying, by a server, unannotated transactions of the organization client using selection criteria specified by the client; distributing annotation workload from the server to end users by: determining a responsible end user for a particular unannotated transaction associated with a particular data schema, generating an annotation user interface exposing input elements for data fields required by the particular data schema, transmitting a direct link to the responsible end user that opens the annotation user interface specific to the unannotated transaction, and guiding the responsible end user to supply data field values that comply with the particular data schema; receiving, from the responsible end user via the annotation user interface, annotation data including values for the identified data fields; storing the received annotation data in association with the transaction; and exporting annotated transaction data, comprising the stored annotation data, to the third-party platform, wherein distributing the annotation workload as described reduces server-side processing resources used for annotating schema-specific transaction data.
2 . The computer-implemented method of claim 1 , wherein receiving annotation requirements from the organization client comprises: receiving, from the third-party platform, available data fields of the platform's schema; and receiving, from the organization client via a graphical user interface, a selection of one or more of the available data fields to be required for annotating the organization client's transactions.
3 . The computer-implemented method of claim 1 , wherein identifying unannotated transactions using selection criteria specified by the client comprises: receiving, from the organization client via a graphical user interface, the selection criteria defining parameters of transactions to be annotated; and comparing transaction data stored by the server to the selection criteria to flag transactions that match the selection criteria as unannotated transactions requiring annotation.
4 . The computer-implemented method of claim 1 , wherein determining the responsible end user comprises: querying using an account number associated with the unannotated transaction to retrieve a profile of a corresponding end user; and identifying, from the profile, a user identifier for contacting the end user via one or more communication channels.
5 . The computer-implemented method of claim 1 , wherein transmitting the direct link to the responsible end user comprises: generating, by the server, the direct link to an annotation webpage specific to the unannotated transaction; and sending the direct link via a communication channel selected from the group consisting of email, short message service, or a SaaS platform webpage.
6 . The computer-implemented method of claim 1 , wherein transmitting the direct link further comprises: embedding authentication information in the direct link; and allowing the responsible end user to access the annotation user interface without providing login credentials upon verifying the authentication information from a token stored on an end user device.
7 . The computer-implemented method of claim 1 , wherein generating the annotation user interface comprises: determining, from the annotation requirements, the data fields required for the particular data schema; and generating input elements within the annotation user interface corresponding to each of the required data fields.
8 . The computer-implemented method of claim 1 , wherein guiding the responsible end user to supply data field values comprises: presenting example annotation data values for at least one of the required data fields based on parsed transaction data including merchant category, receipt image data, or memo text; and prompting the responsible end user to select or confirm from the presented example annotation data values.
9 . The computer-implemented method of claim 1 , wherein storing the received annotation data in association with the transaction comprises: updating a standardized data entry corresponding to the transaction with the values for the identified data fields; and mapping different data field names of various third-party platforms'schemas to a common or standardized data structure to reduce redundant data storage.
10 . The computer-implemented method of claim 1 , wherein exporting the annotated transaction data to the third-party platform comprises: converting a data structure containing the annotated transaction data to a format corresponding to the schema of the third-party platform; and transmitting the converted data in batch to the third-party platform via the server's interface.
11 . A non-transitory computer-readable medium configured to store code comprising instructions for reducing server-side processing resources in annotating schema-specific transaction data, wherein the instructions, when executed by one or more processors, cause the one or more processors to: receive annotation requirements from an organization client, the requirements identifying a third-party platform and at least one data field of a data schema used by the platform; identify, by a server, unannotated transactions of the organization client using selection criteria specified by the client; distribute annotation workload from the server to end users by: determining a responsible end user for a particular unannotated transaction associated with a particular data schema, generating an annotation user interface exposing input elements for data fields required by the particular data schema, transmitting a direct link to the responsible end user that opens the annotation user interface specific to the unannotated transaction, and guiding the responsible end user to supply data field values that comply with the particular data schema; receive, from the responsible end user via the annotation user interface, annotation data including values for the identified data fields; store the received annotation data in association with the transaction; and export annotated transaction data, comprising the stored annotation data, to the third-party platform, wherein distributing the annotation workload as described reduces server-side processing resources used for annotating schema-specific transaction data.
12 . The non-transitory computer-readable medium of claim 11 , wherein receiving annotation requirements from the organization client comprises: receiving, from the third-party platform, available data fields of the platform's schema; and receiving, from the organization client via a graphical user interface, a selection of one or more of the available data fields to be required for annotating the organization client's transactions.
13 . The non-transitory computer-readable medium of claim 11 , wherein identifying unannotated transactions using selection criteria specified by the client comprises: receiving, from the organization client via a graphical user interface, the selection criteria defining parameters of transactions to be annotated; and comparing transaction data stored by the server to the selection criteria to flag transactions that match the selection criteria as unannotated transactions requiring annotation.
14 . The non-transitory computer-readable medium of claim 11 , wherein determining the responsible end user comprises: querying using an account number associated with the unannotated transaction to retrieve a profile of a corresponding end user; and identifying, from the profile, a user identifier for contacting the end user via one or more communication channels.
15 . The non-transitory computer-readable medium of claim 11 , wherein transmitting the direct link to the responsible end user comprises: generating, by the server, the direct link to an annotation webpage specific to the unannotated transaction; and sending the direct link via a communication channel selected from the group consisting of email, short message service, or a SaaS platform webpage.
16 . The non-transitory computer-readable medium of claim 11 , wherein transmitting the direct link further comprises: embedding authentication information in the direct link; and allowing the responsible end user to access the annotation user interface without providing login credentials upon verifying the authentication information from a token stored on an end user device.
17 . The non-transitory computer-readable medium of claim 11 , wherein generating the annotation user interface comprises: determining, from the annotation requirements, the data fields required for the particular data schema; and generating input elements within the annotation user interface corresponding to each of the required data fields.
18 . The non-transitory computer-readable medium of claim 11 , wherein guiding the responsible end user to supply data field values comprises: presenting example annotation data values for at least one of the required data fields based on parsed transaction data including merchant category, receipt image data, or memo text; and prompting the responsible end user to select or confirm from the presented example annotation data values.
19 . The non-transitory computer-readable medium of claim 11 , wherein storing the received annotation data in association with the transaction comprises: updating a standardized data entry corresponding to the transaction with the values for the identified data fields; and mapping different data field names of various third-party platforms'schemas to a common or standardized data structure to reduce redundant data storage.
20 . A system comprising: one or more processors; and memory storing code comprising instructions for reducing server-side processing resources in annotating schema-specific transaction data, wherein the instructions, when executed by the one or more processors, cause the one or more processors to: receive annotation requirements from an organization client, the requirements identifying a third-party platform and at least one data field of a data schema used by the platform; identify, by a server, unannotated transactions of the organization client using selection criteria specified by the client; distribute annotation workload from the server to end users by: determining a responsible end user for a particular unannotated transaction associated with a particular data schema, generating an annotation user interface exposing input elements for data fields required by the particular data schema, transmitting a direct link to the responsible end user that opens the annotation user interface specific to the unannotated transaction, and guiding the responsible end user to supply data field values that comply with the particular data schema; receive, from the responsible end user via the annotation user interface, annotation data including values for the identified data fields; store the received annotation data in association with the transaction; and export annotated transaction data, comprising the stored annotation data, to the third-party platform, wherein distributing the annotation workload as described reduces server-side processing resources used for annotating schema-specific transaction data.

Description

CROSS REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. patent application Ser. No. 17/589,837, filed on Jan. 31, 2022, which is incorporated herein by reference in its entirety for all purposes. TECHNICAL FIELD The present disclosure generally relates to managing transactions in network communications and, particularly, annotating transactions according to schemas of third-party platforms. BACKGROUND Monitoring transactions is valuable for fraud prevention, resource allocation, budgeting, diagnostics, and more. To monitor transactions, data about the transactions are gathered and maintained using various software platforms that may be designed by different third parties. Various third-party software platforms have their own data schemas for organizing the transaction data. Those software platforms often use different schemas such as different metadata tags and data fields to annotate transactions. As an example, hundreds of thousands of annotations can be generated when monitoring and organizing tens of thousands of transactions that can happen in a day. A server charged with determining annotations can thus expend immense processing and storage resources determining and storing many annotations for the various software platforms'schemas. The server may be tasked with analyzing a transaction to determine annotations that likely characterize the transaction, inferring various metadata tags from scant information such as a date, amount, and entities involved in the transaction. The annotation can thus be inaccurate in addition to processing intensive. The server may also be tasked with storing the metadata tags used for annotation, but due to the lack of standardized schema for annotating transactions, may create different data structures for each schema despite similar or the same metadata tags being stored. Accordingly, conventional systems for annotating transactions consume many processing and storage resources. SUMMARY Embodiments are related to transaction verification processes and architectures that reduce the processing and network bandwidth resource consumption by a computing server handling the transaction verification. In one embodiment, a computing server creates transaction accounts for an organization client. A transaction account may allow an owner of the account to perform transaction with third-party named entities. The organization client can manage how the transactions are annotated by providing the computing server with annotation requirements and selection criteria. The annotation requirements can specify a data field of a third-party platform's schema with which transactions are to be annotated. The schema may be used by the third-party platform to organize transaction data (e.g., annotating with metadata tags such as entity categories and locations). The selection criteria may specify which transactions need to be annotated (e.g., transactions over a certain amount or incurred during a certain time window). The computing server can process transactions on behalf of the organization client and identify unannotated transactions using the selection criteria. The computing server may request certain end users annotate the unannotated transactions by identifying the responsible end user associated with the unannotated transactions (e.g., end users who incurred the transactions) and transmitting a direct link to those responsible end users. The direct link can bring responsible end users directly to respective annotation pages specific to the unannotated transactions. The annotation pages allow the responsible end users to annotate the unannotated transactions. The computing server receives annotations of the unannotated transactions, including data field values of the third-party platforms'schemas. The computing server can then display, at a graphical user interface (GUI) for an administrator of the organization client, entries of annotated transaction data that include the data field values. The graphical user interface may allow the administrator to export the annotated transaction data to the third-party platform. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram illustrating an example system environment, in accordance with an embodiment. FIG. 2 is a block diagram illustrating components of an example computing server, in accordance with an embodiment. FIG. 3 is an interaction diagram depicting a computer-implemented process for annotating transactions, in accordance with an embodiment. FIG. 4 depicts example transaction annotation interactions using a device of an end user, in accordance with an embodiment. FIGS. 5A-H depict example user interfaces for annotating a transaction using a device of an end user, in accordance with an embodiment. FIG. 6 illustrates a transaction data collection management portal, in accordance with an embodiment. FIG. 7 illustrates a card management portal, in accordance with an embodiment. FIG. 8 illustrates an interfac