Skip to main content

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

Setting up account step rules

Updated on March 21, 2023

The accounting automatic flows and flow actions use a specific action of a rule class, such as Open Payable (Open action of the Payable rule) or Adjustment (Adjust action of the Adjustment rule). Smart Dispute supports Adjust and WriteOff adjustment actions and Open, Close, Lower, and WriteOff suspense actions.

Pega Smart Dispute for Issuers Implementation Guide
Before you begin:

Automatic flows require a parameter specifying the appropriate rule to use. The parameter specifies the Type property and the flow determines the other key parts (RuleClass, action, and work object class). Manual flow actions can also determine these key parts and display Short Descriptions from every step rule that the flow action can use, including security validation. By default, Smart Dispute uses the transaction information from the rule with the highest likelihood and lets you select any other valid step rules from a list of rules and their short descriptions.

Use the account step rule decisions that you made in the Defining accounting step rules task.

  1. In the Application Explorer, search for the Rule-PegaAcct-Financial-Adjustment, Rule- PegaAcct-Financial-Payable, or Rule-PegaAcct-Financial-Receivable class, and select a rule to edit, such as WriteOffCrCardHolder.
  2. Click Save As.
  3. In the Apply to field, select 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. On the Transactions tab, edit values for DR/ CR, Label, PymtType, and so on, if necessary.
  7. Click Save.
What to do next: For more information, see Fields on the Adjustment Rule form.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us