CPC G06Q 30/0239 (2013.01) [G06Q 30/02 (2013.01); G06Q 30/0222 (2013.01); G06Q 30/0224 (2013.01); G06Q 30/0236 (2013.01); G06Q 50/06 (2013.01); G06F 16/9535 (2019.01); H04L 12/2838 (2013.01); H04L 67/1006 (2013.01)] | 19 Claims |
1. A method for reducing latency in product rebate eligibility, the method comprising:
providing, via one or more frontend systems, utility raw data to a rebate system;
parsing and standardizing the utility raw data to form standardized customer data and standardized rebate data;
validating, via a validation module, the standardized customer data and the standardized rebate data by analyzing and comparing fields in the standardized customer data and the standardized rebate data to a set of minimum fields, wherein if one of the set of minimum fields is not met an error log will be generated and returned to the one or more frontend systems to request correction, and wherein if the set of minimum fields is met an error log will not be generated and returned to the one or more frontend systems to request correction;
applying, via a rules engine, persistent utility rebate rules to the standardized customer data and the standardized rebate data to generate utility-specific rebate profiles, wherein the utility-specific rebate profiles comprise a plurality of rebate eligibilities for a plurality of redemption scenarios;
storing, via an admin interface, the persistent utility rebate rules in a rebate database, wherein the persistent utility rebate rules constitute rebate eligibility parameters; and then,
querying, via the rules engine, the utility-specific rebate profiles for one or more utility companies;
applying, via the rules engine, runtime rebate rules to the utility-specific rebate profiles to identify one or more customer-specific rebates; and
returning, via the rules engine, the one or more customer-specific rebates to the one or more frontend systems.
|