Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Modifying Regulation E at the claim level

Updated on March 21, 2023

You can have disputes that have a 45-day final date and disputes that have a 90-day final date on one claim. If so, you can either manage by dispute, or by the claim. If you manage by the claim, you must manage by the most restrictive date, therefore you must override the 90-day claim-level date.

Pega Smart Dispute for Issuers Implementation Guide

If you manage by dispute, you must leave the claim itself open until all disputes have been resolved.

Regulation E (Reg E) dates for each dispute are set after transaction selection, along with claim-level RegEPC, WaitForRegEFinal45 and WaitForRegEFinal90 dates. Service-level agreements are set for each claim-level Reg E date, so that the claims can be managed from the user’s worklist. If a set of disputes in a claim include no disputes with a Reg E final date of 90 days, then that property and service-level agreement are not set.

  1. In the Dev Studio header search text field, enter WaitForRegEFinal45 or WaitForRegEFinal90 and then select the service-level agreement rule from the results.
  2. Click Save as.
  3. In the Apply to field, enter the appropriate implementation class for your application.
  4. In the Add to ruleset list, select the ruleset for your application.
  5. Click Create and open.
  6. Review the WaitForRegEFinal45 or WaitForRegEFinal90 dates and modify the goal dates if needed.
    Caution: Do not modify the deadline dates.
  7. Click Save.
  • Previous topic Modifying Regulation E document receipt service-level agreement rules
  • Next topic Modifying the reverse provisional credit service-level agreement

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us