11228441

System for Automated Data Verification

PublishedJanuary 18, 2022
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
20 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

1. A system for automated data verification across multiple sets of source data, the system comprising one or more computers and one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to: receive a first set of source data and a second set of source data; convert the first set of source data into a first spreadsheet, the first spreadsheet including a first column name row and one or more rows of first data, and the converting the first spreadsheet performed using a first input positioning reference spreadsheet; convert the second set of source data into a second spreadsheet, the second spreadsheet including a second column name row and one or more rows of second data, and the converting the second spreadsheet performed using a second input positioning reference spreadsheet; filter the first spreadsheet using a filter function to identify a first single row of data in the first spreadsheet and filter the second spreadsheet using the filter function to identify a second single row of data in the second spreadsheet, wherein the first single row of data and the second single row of data are corresponding data to be verified against each other; create a first hashmap containing one or more key and value pairs, wherein: the first column name row is converted into the one or more keys, and the first single row of data is converted into the one or more paired values; create a second hashmap containing one or more key and value pairs, wherein: the second column name row is converted into the one or more keys, and the second single row of data is converted into the one or more paired values; compare the first hashmap to the second hashmap, the comparing comprising: matching one or more keys in the first hashmap to one or more identical keys in the second hashmap, and determining if a value paired with a key in the first hashmap is identical to a value paired with the key in the second hashmap; and generate an output report, the output report identifying whether the determining indicates that the value paired with the key in the first hashmap is identical to the value paired with the key in the second hashmap; and wherein the method includes performing data verification across several sets of source data by: receiving several sets of source data, the several sets of source data including: a bank input fixed length flat format file including data descriptive of at least one transaction, a bank output fixed length flat format file that is generated based on the bank input file and includes data descriptive of the at least one transaction, a database file generated by querying a database and exporting the query results and includes data descriptive of the at least one transaction, a payment output file fixed length flat format file that is generated based on the bank output file and information from the database, and includes data descriptive of the at least one transaction, and a payment input fixed length flat format file that is generated based on the payment output file and includes data descriptive of the at least one transaction; converting the several sets of source data into respective spreadsheets by converting the bank input file into a bank input spreadsheet, converting the bank output file into a bank output spreadsheet, converting the database file into a database spreadsheet, converting the payment output file into a payment output spreadsheet, and converting the payment input file into a payment input spreadsheet; and performing data validation across the several sets of source data by repeating the method of automated data verification for multiple pairs of the spreadsheets with: the bank input spreadsheet as the first spreadsheet and the bank output spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the database spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the payment output spreadsheet as the first spreadsheet and the payment input spreadsheet as the second spreadsheet, and the payment input spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet.

2

2. The system of claim 1 , wherein the step of filtering the first spreadsheet and filtering the second spreadsheet includes: identifying a column that is present within both the first spreadsheet and the second spreadsheet, for which each row associated with the said column has a unique data value; and filtering each of the first spreadsheet and the second spreadsheet by the unique data value.

3

3. The system of claim 1 , wherein the system receives the first input positioning reference spreadsheet and the second input positioning reference spreadsheet from a user.

4

4. The system of claim 1 , wherein the first input positioning reference spreadsheet includes: a field names column including one or more rows of data descriptive of one or more names of types of data contained in the first set of source data that are to be imported into the first spreadsheet; a start position column including, for each type of data named in the field names column, a row of data descriptive of where within the first set of source data the type of data to be imported into the first spreadsheet begins; and an end position column including, for each type of data named in the field names column, a row of data descriptive of where within the first set of source data the type of data to be imported into the first spreadsheet ends; and wherein: the field names column in the first input positioning reference spreadsheet is converted into the first column name row in the first spreadsheet; and the start position column and the end position column define which data in the first set of source data becomes associated with which column in the first spreadsheet.

5

5. The system of claim 1 , wherein a user defines which data within the first set of source data and the second set of source data will be verified by: entering field name, start position, and end position data into the first input positioning reference spreadsheet that is descriptive of which data fields in the first set of source data will be imported into the first spreadsheet and where within the first set of source data said data fields are located; and entering field name, start position, and end position data into the second input positioning reference spreadsheet that is descriptive of which data fields in the second set of source data will be imported into the second spreadsheet and where within the second set of source data said data fields are located.

6

6. The system of claim 1 , wherein the system: repeats the steps of filtering the first spreadsheet and the second spreadsheet, creating the first hashmap and second hashmap, and comparing the first hashmap to the second hashmap, for each row of data in the first spreadsheet.

7

7. A method of automated data verification across multiple sets of data, the method comprising: receiving a first spreadsheet including a first column name row and one or more first data rows; receiving a second spreadsheet including a second column name row and one or more second data rows; filtering the first spreadsheet using a filter function to identify a first single row of data in the first spreadsheet, and filtering the second spreadsheet using the filter function to identify a second single row of data in the second spreadsheet, wherein the first single row of data and the second single row of data are corresponding data to be verified against each other; creating a first hashmap containing one or more key and value pairs, wherein the first column name row is converted into the one or more keys and the first single row of data is converted into the one or more paired values; creating a second hashmap containing one or more key and value pairs, wherein the second column name row is converted into the one or more keys and the second single row of data is converted into the one or more paired values; comparing the first hashmap to the second hashmap, by matching one or more keys in the first hashmap to one or more identical keys in the second hashmap then determining if a value paired with a key in the first hashmap is identical to a value paired with said key in the second hashmap; and generating an output report identifying whether the values for each said key match or do not match; wherein: the step of filtering the first spreadsheet and filtering the second spreadsheet includes: identifying a column that is present within both the first spreadsheet and the second spreadsheet, for which each row associated with the said column has a unique data value; and filtering each of the first spreadsheet and the second spreadsheet by the unique data value; wherein: the system repeats the steps of filtering the first spreadsheet and the second spreadsheet, creating the first hashmap and second hashmap, comparing the first hashmap to the second hashmap, and generating an output report for each row of data in the first spreadsheet; and wherein the method includes performing data verification across several sets of source data by: receiving several sets of source data, the several sets of source data including: a bank input fixed length flat format file including data descriptive of at least one transaction, a bank output fixed length flat format file that is generated based on the bank input file and includes data descriptive of the at least one transaction, a database file generated by querying a database and exporting the query results and includes data descriptive of the at least one transaction, a payment output file fixed length flat format file that is generated based on the bank output file and information from the database, and includes data descriptive of the at least one transaction, and a payment input fixed length flat format file that is generated based on the payment output file and includes data descriptive of the at least one transaction; converting the several sets of source data into respective spreadsheets by converting the bank input file into a bank input spreadsheet, converting the bank output file into a bank output spreadsheet, converting the database file into a database spreadsheet, converting the payment output file into a payment output spreadsheet, and converting the payment input file into a payment input spreadsheet; and performing data validation across the several sets of source data by repeating the method of automated data verification for multiple pairs of the spreadsheets with: the bank input spreadsheet as the first spreadsheet and the bank output spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the database spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the payment output spreadsheet as the first spreadsheet and the payment input spreadsheet as the second spreadsheet, and the payment input spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet.

8

8. The method of claim 7 , wherein the method further comprises generating the first spreadsheet and second spreadsheet by: receiving at least a first set of source data and a second set of source data; converting the first set of source data into a first spreadsheet including a first column name row and one or more rows of first data, using a first input positioning reference spreadsheet; and converting the second set of source data into a second spreadsheet including a second column name row and one or more rows of second data, using a second input positioning reference spreadsheet.

9

9. The method of claim 8 , wherein the system receives the first input positioning reference spreadsheet and the second input positioning reference spreadsheet from a user.

10

10. The method of claim 8 , wherein a user defines which data within the first set of source data and the second set of source data will be verified by: entering field name, start position, and end position data into the first input positioning reference spreadsheet that is descriptive of which data fields in the first set of source data will be imported into the first spreadsheet and where within the first set of source data said data fields are located; and entering field name, start position, and end position data into the second input positioning reference spreadsheet that is descriptive of which data fields in the second set of source data will be imported into the second spreadsheet and where within the second set of source data said data fields are located.

11

11. The method of claim 7 , wherein the method further comprises: generating one of the first spreadsheet and second spreadsheet by querying a database to produce query results, and converting the query results into a spreadsheet format; generating one of the first spreadsheet and the second spreadsheet by receiving a fixed length flat format file and converting the fixed length flat format file to a spreadsheet format using an input positioning reference spreadsheet.

12

12. The method of claim 7 , wherein the method verifies credit card data on transaction data that is passed between several parties in a credit card payment network.

13

13. The method of claim 12 , wherein the method includes performing data verification across several credit card sets of source data by: receiving several credit card sets of source data, the several credit card sets of source data including: the bank input fixed length flat format file including data descriptive of at least one credit card transaction, the bank output fixed length flat format file that is generated based on the bank input file and includes data descriptive of the at least one credit card transaction, the database file generated by querying the database and exporting the query results and includes data descriptive of the at least one credit card transaction, the payment output file fixed length flat format file that is generated based on the bank output file and information from the database, and includes data descriptive of the at least one credit card transaction, and the payment input fixed length flat format file that is generated based on the payment output file and includes data descriptive of the at least one credit card transaction.

14

14. One or more non-transitory computer readable storage media encoded with instructions that, when executed by a processor of a computing device, causes the processor to perform data verification across several credit card sets of source data by: receiving first credit card source data set including data descriptive of at least one credit card transaction; receiving second credit card source data set including data descriptive of the at least one credit card transaction; converting the first credit card source data set into a first spreadsheet; converting second credit card source data set into a second spreadsheet; using a filter function on the first spreadsheet to filter all but one row of credit card transaction data, and using a filter function on the second spreadsheet to filter all but one row of credit card transaction data, the one row in the first spreadsheet and the one row in the second spreadsheet being descriptive of the same credit card transaction; creating a first hashmap from the one row in the first spreadsheet, and creating a hashmap from the one row in the second spreadsheet; comparing the first hashmap to the second hashmap; generating an output report identifying when any value of data descriptive of the credit card transaction in the first spreadsheet does not match a value of corresponding data descriptive of the same credit card transaction in the second spreadsheet; wherein the processor performs data verification across several credit card sets of source data by: receiving several credit card sets of source data, the several credit card sets of source data including: a bank input fixed length flat format file including data descriptive of at least one credit card transaction, a bank output fixed length flat format file that is generated based on the bank input file and includes data descriptive of the at least one credit card transaction, a database file generated by querying a database and exporting the query results and includes data descriptive of the at least one credit card transaction, a payment output file fixed length flat format file that is generated based on the bank output file and information from the database, and includes data descriptive of the at least one credit card transaction, and a payment input fixed length flat format file that is generated based on the payment output file and includes data descriptive of the at least one credit card transaction; converting the several credit card sets of source data into respective credit card spreadsheets by converting the bank input file into a bank input spreadsheet, converting the bank output file into a bank output spreadsheet, converting the database file into a database spreadsheet, converting the payment output file into a payment output spreadsheet, and converting the payment input file into a payment input spreadsheet; and performing data validation across the several credit card sets of source data by repeating the steps of using the filter function, creating the hashmaps, and comparing the hashmap for multiple pairs of the credit card spreadsheets with: the bank input spreadsheet as the first spreadsheet and the bank output spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet, the bank output spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the database spreadsheet as the first spreadsheet and the payment output spreadsheet as the second spreadsheet, the payment output spreadsheet as the first spreadsheet and the payment input spreadsheet as the second spreadsheet, and the payment input spreadsheet as the first spreadsheet and the database spreadsheet as the second spreadsheet.

15

15. The non-transitory computer readable storage media of claim 14 , wherein the step of converting the first credit card source data set into the first spreadsheet includes converting a first credit card fixed length flat format file into the first spreadsheet by: mapping a set of field names, a set of start positions, and a set of end positions with an input positioning reference spreadsheet for each type of credit card transaction data in the first credit card data file that is to be imported into the first spreadsheet.

16

16. The non-transitory computer readable storage media of claim 14 , wherein the first credit card source data set includes data descriptive of a plurality of credit card transactions; the second credit card source data set includes data descriptive of the same plurality of credit card transactions; and wherein the steps of filtering the first spreadsheet and the second spreadsheet, creating the first hashmap and second hashmap, and comparing the first hashmap to the second hashmap, are repeated for each row of data in the first spreadsheet.

17

17. The non-transitory computer readable storage media of claim 14 , wherein the processor performs data verification across several credit card sets of source data by receiving a plurality of credit card sets of source data; verifying any one of the plurality of plurality of credit card sets of source data against any other of the plurality of credit card sets of source data by designating the one of the plurality of credit card sets of source data as the first credit card source data set, and designating another of the plurality of credit card sets of source data as the second credit card source data set; and repeating this process until each of the plurality of credit card sets of source data has been verified against each of the others of the plurality of credit card sets of source data.

18

18. The non-transitory computer readable storage media of claim 15 , wherein the processor receives each input positioning reference spreadsheet from a user.

19

19. The non-transitory computer readable storage media of claim 14 , wherein the first spreadsheet includes a first column name row, and the second spreadsheet includes a second column name row; the step of creating the first hashmap includes: converting each of one or more fields in the first column name row into one or more first hashmap keys, converting each of one or more fields in the one row in the first spreadsheet generated by the filter function into one or more first hashmap values, the first hashmap values corresponding to the first hashmap keys based on the column location of the fields in the one row of the first spreadsheet; the step of creating the second hashmap includes: converting each of one or more fields in the second column name row into one or more second hashmap keys, converting each of one or more fields in the one row in the second spreadsheet generated by the filter function into one or more second hashmap values, the second hashmap values corresponding to the second hashmap keys based on the column location of the fields in the one row of the second spreadsheet; and the step of comparing the first hashmap to the second hashmap includes: matching each of one or more first hashmap keys to each of one or more identical second hashmap keys then determining if the first hashmap value paired with that key is identical to the second hashmap value paired with said key.

20

20. The method of claim 14 , wherein the processor performs data verification across several credit card sets of source data by: receiving several credit card sets of source data, the several credit card sets of source data including: the bank input fixed length flat format file including data descriptive of at least one credit card transaction, the bank output fixed length flat format file that is generated based on the bank input file and includes data descriptive of the at least one credit card transaction, the database file generated by querying the database and exporting the query results and includes data descriptive of the at least one credit card transaction, the payment output file fixed length flat format file that is generated based on the bank output file and information from the database, and includes data descriptive of the at least one credit card transaction, and the payment input fixed length flat format file that is generated based on the payment output file and includes data descriptive of the at least one credit card transaction.

Patent Metadata

Filing Date

Unknown

Publication Date

January 18, 2022

Inventors

Atmaj Bhushan
Nitin Porwal
Aniruddha Vijayprakash Sarag
Rajesh Kumar Soni

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “SYSTEM FOR AUTOMATED DATA VERIFICATION” (11228441). https://patentable.app/patents/11228441

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.