Rate validation system and method

A computer-implemented method to facilitate auditing of rate data in a database, the method comprising:

• entering first rate data into a first database;
• entering second rate data into a at least one second database;
• creating an audit configuration including at least one audit parameter and an audit schedule,
• wherein the audit schedule indicates whether the audit is to be executed immediately upon the creating of the audit configuration or is to be executed at at least one predetermined date and time subsequent to the creating of the audit configuration, and
• wherein the audit schedule indicates whether the audit is a one-time audit or a recurring audit;
• executing the audit based at least in part on the audit configuration, wherein the executing of the audit includes:
• receiving screen data for navigating to a location of the first rate data;
• issuing a command for navigating to the location of the first rate data based on the screen data;
• and
• comparing the first rate data and the second rate data to determine if the first rate data and the second rate data are substantially similar prior to an authorization for a transaction.

A system configured to facilitate auditing of data in a database, the system comprising:

• a first database having first data;
• at least one second database having second data;
• and
• a rate tracking (RT) server configured to:
• facilitate creating an audit configuration including at least one audit parameter and an audit schedule,
• wherein the audit schedule indicates whether the audit is to be executed immediately upon the creating of the audit configuration or is to be executed at at least one predetermined date and time subsequent to the creating of the audit configuration, and
• wherein the audit schedule indicates whether the audit is a one-time audit or a recurring audit;
• and
• execute the audit based at least in part on the audit configuration, wherein execution of the audit includes:
• receiving screen data for navigating to a location of the first data,
• issuing a command for navigating to the location of the first data based on the screen data, and
• comparing the first data and the second data to determine if the first data and the second data are substantially similar prior to an authorization for a transaction.