Configuring Random Audit Rules

Objective

After completing this lesson, you will be able to configure and manage random audit rules.

Random Audit Rules Overview

Random audit rules audit selected expense reports in two ways:

  • As a percentage of reports submitted (for example, 10% of submitted reports are audited)
  • As a specific sequential number of reports (for example, every 10th expense report submitted is audited)
The image displays an “Audit Rules” page. It shows tabs labeled Custom, Random, and Validation. Action buttons include Save, Activate, Deactivate, and Remove. A table lists rules with columns Name, Type, Event, Exception Code, Editable By, Applies To, and Active. One row shows “Random Audit” with type Sequential, event Post Report Submit, exception code RANDOM, editable by Global, applies to Global, and active set to No. Another row lists type Percentage, event Report Submit, editable by Global, applies to Global, and active set to No.

Configure a Random Audit Rule

To configure a random audit rule:

Steps

  1. On the Random tab of the Audit Rules page, select the Name field of the highlighted row and then enter the rule name.

    The image displays an Audit Rules page in Expense Admin. The tabs show Custom, Random, and Validation. A table lists two rules. The Sample rule is highlighted with type Percentage and event Report Submit. Random Audit uses type Sequential and event Post Report Submit with exception code RANDOM. Both rules are editable by Global and have Active set to No. Action buttons Save, Activate, Deactivate, and Remove sit above the table.

  2. Select the Type field. In the Rule Type window, select either Percentage or Sequential, enter the appropriate amount, and then select Save.

    The image displays the Audit Rules page with a Rule Type dialog open. The dialog offers Percentage and Sequential options. Percentage is selected with 1 percent of all expense reports submitted entered. The Sequential field is empty. Save and Cancel buttons appear. The Sample rule in the table shows type Percentage.

  3. In the Event field, select either Report Submit or Post Report Submit. Report Submittriggers the rule when the report is submitted; if there are exceptions generated above the limit, the report won’t submit and won’t enter the first step of a workflow. Post Report Submittriggers the rule immediately after a report enters the first step of the workflow; any exceptions that are generated don’t prevent the report from being submitted.

    The image displays the Audit Rules page with the Event drop-down open for the Sample rule. The menu lists Post Report Submit and Report Submit. Report Submit is selected. The table shows the Sample rule with type Percentage and Active set to No, and a Random Audit rule below.

  4. Select the Exception Code field. In the Exceptions window, designate the exception visibility and code, and then select Save.

    The image displays the Audit Rules page with an Exceptions dialog open. The dialog shows Exception Visibility set to Expense Processor. Fields for Exception Code, Exception Level, and Exception Text are visible. Buttons New, Modify, and Remove appear above a table of exception codes and messages, including 60DAYS, ACCTCODE, ATMCHECK, AUDIT, and BANKINFO.

  5. Select Editable By and Applies To to specify which groups can edit the rule and which groups the rule applies to, and then select Save.

    The image displays the Audit Rules page after adding an exception. The Sample rule shows Type Percentage, Event Report Submit, and Exception Code BANKINFO. Editable By and Applies To show Global. The Save button is highlighted. The Active column shows No.

  6. Select Activate to turn on the rule.

    The image displays the Audit Rules page with the Sample rule selected. The rule shows Type Percentage, Event Report Submit, and Exception Code BANKINFO. The Activate button is highlighted. Both rules show Active set to No.

Summary

  • Set up random audits based on percentage or sequential.
  • Select when the rule triggers (submission or post-submission).
  • Select an exception code and visibility.
  • Specify who can edit and which groups it applies to.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn