Skip to main content

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

Setting up verification levels

Updated on March 21, 2023

Your organization can have a policy stating that adjustments above a certain amount must be verified by a manager. For example, you can choose not to require verification for credits below $100 but require a senior review and verification for accounting credits of more than $5,000.

By default, no accounting steps require verification; however, you can configure up to three levels of verification based on value. The verification levels are the number of times an item is verified. The privileges assigned to users determine the top level at which a user can verify. A user can only verify an accounting step once, regardless of their privileges.

To include verification in your business flows, you must configure step rules to specify a value of FinVerifyByAmount in the Activity for Verification Flow field on the Step tab. This activity uses the FinVerificationFlowByAmount map value, in the PegaAcct-Step class, to determine the verification levels based on the amount thresholds. If you review these values and find them suitable for your organization, you can use the rule as is.

Pega Smart Dispute for Issuers Implementation Guide
  1. In the Dev Studio header search text field, enter FinVerificationFlowByAmount and select the PegaAcct-Step class map value rule from the results.
  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. Configure the verification levels, if needed.
  7. Click Save.

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