Transaction Document Verification Using Unique Dataset Codes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In transactional processes, ensuring the accuracy and consistency of data used to create documents with the data delivered post-transaction is challenging, as changes can occur before or after document creation, and multiple document sets may be generated, making it difficult to verify which set is correct.

Innovation Solution

A method and system that involve receiving a transaction dataset, generating a unique code for completed documents, comparing the original dataset with the current dataset using this code, and identifying inconsistencies, allowing for automated verification and reporting of accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual comparison of documents with system of record data is performed, then verification of data consistency can be conducted, but the process is time-consuming and prone to human error

Engineering Contradiction:

Improveverification accuracyVSAvoidreview time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical comparison with automated electronic verification. A verification code is generated from the system of record data and embedded in the document, then automatically compared against the document data using computational algorithms, eliminating manual review while maintaining high accuracy

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent creates a digital copy of the verification process by generating a verification code that represents the system of record data. This code is embedded in the document and can be automatically compared, replacing the need for manual copying and comparison of entire datasets

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If multiple document sets are generated prior to closing, then flexibility in document preparation is improved, but it becomes difficult to verify which document set is correct

Engineering Contradiction:

Improvedocument generation flexibilityVSAvoiddocument verification reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent performs preliminary verification by generating a verification code from the system of record data before document execution. This code is embedded in the document at the time of generation, allowing later verification of which document set corresponds to the correct system of record data without ambiguity

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the verification code embedded in each document set can be compared against the current system of record data to provide confirmation of correctness. This feedback loop ensures that even with multiple document sets generated, the correct one can be reliably identified

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If data is changed after creating documents, then adaptability to new information is improved, but data consistency and integrity are compromised

Engineering Contradiction:

Improvedata update capabilityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements continuous feedback verification where the verification code embedded in the document is compared against the current system of record data at the time of review. This feedback mechanism detects any changes that occurred after document creation, maintaining data consistency awareness while allowing necessary updates

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9928268B2System and method for verifying the contents of forms relative to a separate dataset

Publication Date: 2018.03.27 BESCH MARK

AI summary

A method is provided for verifying the contents of forms, comprising: receiving a dataset from a client, the dataset associated with a transaction; transmitting the dataset to a document vendor to be entered into and complete a transaction document form; receiving the completed transaction document form from the document vendor; generating a code uniquely associating the completed document with the dataset; printing the code onto the completed document; transmitting the completed document to the client; after the document has been executed, receiving the executed document from the client and separately the current dataset; using the code on the executed document, retrieving the stored transaction dataset; comparing the stored dataset with the dataset separately delivered as the current dataset; identifying all inconsistencies between the two datasets and storing these results as separate data; and transmitting a message to the client with the result of the comparison.