Distributed computing entity for detecting discrepancies between calculations performed by various processing instances
A distributed transaction management computing system is configured for detecting transaction-specific data discrepancies that result from data calculations performed by different processing instances executing on geographically-distributed computing entities. The transaction-specific data discrepancies are identified via a network-accessible operations computing entity in electronic communication with a plurality of geographically-distributed edge computing entities. The operations computing entity defines at least two separate processing instances, wherein a first processing instance is configured to generate secondary data for individual transactions in the event that the edge computing entities do not themselves generate the transaction-specific secondary data; and wherein a second processing instance is configured to generate audit data for individual transactions. The operations computing entity compares the audit data and the secondary data for individual transactions to identify discrepancies therebetween that may arise from differences in data generation methodologies performed by the edge computing entities and the multiple operations computing entity processing instances.
1. A method for detecting transaction-specific data discrepancies among processing instances executing on geographically-distributed computing entities, the method comprising:
receiving transaction-specific data via a first network communications channel associated with a first processing instance operating on an operations computing entity, wherein the transaction-specific data is generated by an edge computing entity that is geographically-spaced from the operations computing entity;
generating, via the first processing instance of the operations computing entity executing a first instance of a sales tax calculation engine, secondary transaction-specific data for the transaction based at least in part on a tax data matrix stored in a non-transitory memory storage area;
generating, via the first processing instance, completed transaction data based at least in part on the transaction specific data and the secondary transaction specific data;
transmitting, via the first processing instance, at least a portion of the completed transaction data for delivery to the edge computing entity;
receiving at least a portion of the completed transaction data from the edge computing entity at a second processing instance operating on the operations computing entity via a second network communications channel, wherein the second network communications channel is distinct from the first network communications channel and the second processing instance is distinct from the first processing instance operating on the operations computing entity;
generating, via the second processing instance of the operations computing entity executing a second instance of the sales tax calculation engine, audit data for the transaction;
identifying, via the second processing instance of the operations computing entity, one or more discrepancies between the secondary transaction-specific data and the audit data; and
generating, via the second processing instance of the operations computing entity, a record upon the detection of a discrepancy between the secondary transaction-specific data and the audit data.
2. The method for detecting transaction-specific data discrepancies of claim 1 , wherein:
generating the secondary transaction-specific data for the transaction via the first processing instance of the operations computing entity comprises executing a first copy of programming instructions; and
generating the audit data for the transaction via the second processing instance of the operations computing entity comprises executing a second copy of programming instructions, wherein the first copy and the second copy include identical programming instruction portions.
3. The method for detecting transaction-specific data discrepancies of claim 1 , wherein:
receiving transaction-specific data comprises receiving transaction-specific data generated during initiation of a transaction via the edge computing entity; and
generating the secondary transaction-specific data and generating the audit data each comprise generating tax data identifying tax amounts due for corresponding sales transactions.
4. The method for detecting transaction-specific data discrepancies of claim 1 , wherein:
receiving transaction-specific data comprises receiving a transaction data file corresponding to a transaction, wherein the transaction data file is generated at the edge computing entity;
and
generating secondary transaction-specific data for the transaction comprises:
detecting the occurrence of a trigger event; and
generating the secondary transaction-specific data for the transaction.
5. The method for detecting transaction-specific data discrepancies of claim 4 , wherein the trigger event is an elapsed period of time.
6. The method for detecting transaction-specific data discrepancies of claim 1 , wherein:
receiving the transaction-specific data at a first processing instance comprises receiving the transaction-specific data transmitted to a first Uniform Resource Locator (URL); and
receiving at least a portion of the completed transaction data at a second processing instance comprises receiving the at least a portion of the completed transaction data transmitted to a second URL.