Configuring Audit Rules

Objectives

After completing this lesson, you will be able to:
  • Access audit rules.
  • Discuss conditions and exceptions.
  • Explain triggers.
  • Describe the use of multiple expense types for audit rules.
  • Discuss the use of multi-level lists for audit rules.
  • Add a new audit rule.
  • Edit an existing audit rule.
  • Activate/deactivate an audit rule.

Path to Access Audit Rules

How to Access Audit Rules

From the Expense Settings page, under the Policy section, select Edit from Expense Compliance.

The images shows a screenshot of the SAP Concur Settings page under the Expense Settings section. The page is titled Settings and includes a Policy section with five options: Expense Approvals, Travel Allowances, Expense Compliance, Policy Groups, and Cash Advances. Each option has a brief description and an Edit button. The Edit for the Expense Compliance option is highlighted with a yellow border. The top right corner shows the selected product as Expense with an option to View Basic Settings.

Conditions and Exceptions for Audit Rules

General concepts about Conditions

Custom audit rules are if/then statements meaning that if the defined conditions are met, then an exception is created. When creating or editing a custom audit rule, you must define the conditional expressions - the if portion of the rule.

The expression can contain one or more conditions separated by and or or.

When you create or edit a custom audit rule, you must assign an exception - the then portion of the if/then statement. All exceptions contain the following:

  • Exception code - this is the company-defined code for the exception, up to eight alphanumeric characters, all uppercase.
  • Exception level - company decides either to block or warn.

Examples of Conditions for Audit Rules

Examples of Conditions

  • Assume that you want to monitor all car rentals involving a vendor other than the company's preferred vendor, which is Avis. The condition for the expense-related rule for car rental from a vendor other than Avis is: (Expense Type equals Car Rental) and (Vendor is not equal to Avis). In the Audit Rule tool, it appears as: The image shows a screenshot of a user interface for setting audit rule conditions. The interface is divided into three main steps: Audit Rule, Conditions, and Exception. The current step highlighted is 2 Conditions. There are options to insert or remove conditions. The first condition is set to check if the Expense Type field in the Entry data object equals Car Rental. The second condition, connected with an And operator, checks if the Vendor field in the Entry data object does not equal Avis. Buttons at the bottom allow the user to cancel, go to the previous step, or proceed to the next step.ssuAssume
  • Assume that you want to monitor all expense reports submitted by one employee. The condition for the employee-related rule for review all expense reports submitted by Jack Aranda (whose employee ID is xxx). In the Audit Rule tool, it appears as: The image shows a screenshot of an audit rule configuration interface. The interface has three tabs at the top: Audit Rule, Conditions (highlighted in yellow), and Exception. Below, there are Insert and Remove buttons. The main section is divided into columns: Data Object/Operator, Field/Value, and Operation. The Data Object/Operator dropdown is set to Employee, the Field/Value dropdown is set to Employee ID, and the Operation dropdown is set to Equal. A text box next to Value contains xxx. At the bottom, there are Cancel, <<Previous, and Next>>buttons.

Triggers for Audit Rules

Audit rules are triggered when certain conditions meet predefined criteria. These criteria are designed to automatically flag non-compliant , suspicious, or erroneous expense transactions or reports for review. When you create or edit a custom audit rule, you must specify the event that triggers the rule.

EventDescription
Allocation SaveThe rule is triggered as each individual allocation line item is saved.
Entry Attendee SubmitThe rule is triggered when the expense is submitted.
Entry SaveThe rule is triggered when an expense is saved, whether by the user, approver, or processor.

Caution

If a rule that is triggered at Entry Save contains a report field in its condition, then the rule is also triggered at Report Save.
Entry SubmitThe rule is triggered when the expense is submitted.

Caution

Entry Submit rules are processed before Report Submit rules.
Post Report SubmitThe rule is triggered immediately after a report enters the first step of workflow. Any exceptions generated will not prevent the report from being submitted.
Report SaveThe rule is triggered immediately after the report header information is saved whether by the user, approver, or processor.
Report SubmitThe rule is triggered when the report is submitted.

Caution

If there are exceptions generated that are above the exception level limit (that is, prevents report submission), then the report will not be submitted and will not enter the first step of a workflow.

Examples of common triggers for audit rules include:

  • Missing or incomplete receipts
  • Duplicate expenses
  • Out-of-Pocket expenses
  • Currency conversion errors

Use of multiple expense types for Audit Rules

In/Not and Equal/Not Equal

Assume you want to create a custom audit rule that includes several expense types. When you select Entry form the Data Object list on the Conditions page, the choices of In, Not In, Equal and Not Equal appear in the Selected Operator helper pane.

If you select In or Not In, then you can select more than one expense type to include in or exclude from the audit rule.

The image shows a screenshot of a user interface for setting up an audit rule with conditions and exceptions. The interface is divided into three main sections: Audit Rule, Conditions, and Exception. The Conditions section is currently active. In the Conditions section, there are options to Insert or Remove a condition. The condition being set up involves selecting a Data Object/Operator, Field/Value, and Operation. The Data Object/Operator is set to Entry. The Field/Value is set to Expense Type. The Operation is set to In. The Value field is populated with Airfare, Car Rental, Hotel, indicating that the condition will apply to these specific expense types. On the right side of the interface, there is an Expense Type Helper panel, which lists various expense types. The expense types Airfare, Car Rental and Hotel are checked, matching the values entered in the. Value field. At the bottom of the interface, there are buttons for navigation: Cancel, Previous, and Next.

If you select Equal or Not Equal, then only one expense type can be selected.

Caution

This option of selecting multiple objects applies only to expense types.

Use of multi-level lists for Audit Rules

You can create rules based on data in multi-level lists. To do this, select the appropriate level in the list. In this example, the rule is based on the first level of a multi-level list, which is Department.

The image shows a screenshot of a user interface for setting audit rule conditions. The interface has three tabs at the top: Audit Rule, Conditions, and Exception, with the Conditions tab selected. Below, there are Insert and Remove buttons. The main section has columns labeled Data Object/Operator, Field/Value, and Operation. The Data Object/Operator dropdown is set to Entry Allocation, and Field/Value is set to Department. The Operation dropdown is set to ANY, Equal. There is a text box labeled Value for entering a value. On the right side, there is a section titled Connected Lists with a description and a link labeled Division-Company-Department highlighted in yellow.

When you select Department, then the name of the list appears, which in this case is Division-Company-Department. You must select the connected list. Next, you must choose the appropriate department from the choices, which in this case is Corporate.

The image shows a screenshot of a user interface for setting audit rules conditions. The interface has three tabs at the top: Audit Rule, Conditions, and Exception, with the Conditions tab selected. Below, there are Insert and Remove buttons. The main section has columns labeled Data Object/Operator, Field/Value, and Operation. The Data Object/Operator dropdown is set to Entry Allocation, and Field/Value is set to Department. The Operation dropdown is set to ANY, Equal. There is a text box labeled Value for entering a value. On the right side of the interface, there is a section titled Items for Connected List: Division-Company-Department. This section includes a search text box and a Search button. Below the search text, there are three options listed: Corporate, Electric, and Solar. The Corporate option is highlighted in yellow.

How to Add a New Audit Rule

Follow these steps to create a new audit rule. We'll walk you through each part of the process, complete with detailed instructions and screenshots to help you along the way.

Once you complete these steps, a demo video will be available to reinforce what you've learned and provide a quick recap.

Steps

  1. Once you navigate to the Compliance Control - Custom Audit Rules page, select New.

    The Audit Rule step appears.

    The image shows a screenshot of a section of the SAP Concur user interface titled Compliance Controls - Custom Audit Rules. Below the title, a description reads, This is where you define custom audit rules to evaluate your expenses. Underneath, there is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. The main section includes a search area with fields to find audit rules based on specific criteria, along with a Search button. Below the search area, there are several action buttons: New, Modify, Copy, Activate, Deactivate, and Remove, with the New button highlighted in yellow. Further down, a table lists existing audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes two entries.
  2. Complete the appropriate fields on the Audit Rule step:

    • Name (required) - type a unique name.
    • Event (required) - select the event that triggers the rule: Allocation Save, Entry Save, Entry Submit, Report Save, Report Submit.
    • Applies To: (required) - select the appropriate group(s). The groups that you see here are the groups that you added on the Policy Groups page, in addition to the default groups.
    • Active: (optional) - select Yes to activate the rule upon completion or leave it as No, and you can activate the rule later.
    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focused on creating or editing an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Audit Rule sub-tab selected and highlighted in yellow. The main form area contains fields for defining the audit rule. These fields include: Name, Event, Applies To, and Active. At the bottom right of the form are two buttons: Cancel in blue and Next in gray, indicating that it is currently not active.
  3. Select Next. The Conditions step appear.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focused on creating or editing an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Audit Rule sub-tab selected and highlighted in yellow. The main form area contains fields for defining the audit rule. These fields include: Name, Event, Applies To, and Active. At the bottom right of the form are two buttons: Cancel in blue and Next highlighted in yellow.
  4. Complete the appropriate fields, making selections from the helper pane. On the Conditions tab, insert the conditions for the audit rule, using:

    • Insert - to add conditions
    • Data Object/Operator
    • Field/Value
    • And, Or
    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focused on setting conditions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Conditions sub-tab selected and highlighted. The main form area is designed to define conditions for the audit rule. At the top, there are Insert and Remove buttons. Below these buttons is a table with columns labeled Data Object/Operator, Field/Value, and Operation. Two conditions are defined in the table. At the bottom right of the form are three buttons: Cancel, Previous and Next.

    Note

    If you select Insert, the new condition is added at the bottom. To insert a new condition between existing conditions, select the condition that will be below the new condition. Once you select Insert, a new blank row appears.
  5. When all conditions have been added, select Next. The Exception step appears.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focused on setting conditions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Conditions sub-tab selected and highlighted. The main form area is designed to define conditions for the audit rule. At the top, there are Insert and Remove buttons. Below these buttons is a table with columns labeled Data Object/Operator, Field/Value, and Operation. Two conditions are defined in the table. At the bottom right of the form are three buttons: Cancel, Previous and Next highlighted in yellow).
  6. From the Exception Visibility list, select the users who are able to see the exception message by selecting on of the following:

    • Traveler, Approver, and Expense Processor
    • Approver and Expense Processor
    • Processor
    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focused on defining exceptions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Exception sub-tab selected and highlighted in yellow. The main form area is designed to define exceptions for the audit rule. At the top, there is a dropdown menu labeled Exception Visibility, which is set to Expense Processor. Below this dropdown, there is a table with columns labeled Exception Code, Exception Level, and Exception Text.
  7. For the exception, you can either:

    • Use an existing exception.
    • Create a new exception.

    To use an existing exception, select the desired exception. It appears in the Exception Code, Exception Level and Exception Text fields at the top of the page.

    To create a new exception, select New. The New Exception window appears.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining exceptions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Exception sub-tab selected and highlighted in yellow. The main form area includes a row of input fields labeled Exception Code, Exception Level, and Exception Text, which are currently empty. Below these fields, there are three buttons: New, Modify, and Remove. Further down, there is a table that lists existing exceptions with columns labeled Code(s), Level, and Message. At the bottom right of the form are three buttons: Cancel, Previous, and Done.

  8. Complete the appropriate fields.

    FieldDescription
    Exception CodeEnter a unique identifier for this exception. For example:
    Exception LevelSelect one of the following:
    • Warn - allows users to complete the event.
    • Block - prevents users from completing the event.
    MessageEnter a message that will be displayed to the user if the exception is triggered by an event.
    The image shows a screenshot of a dialog box within the SAP Concur user interface for creating a new exception. The dialog box is titled New Exception. It contains three input fields: Exception Code, Exception Level, and Message. At the bottom right of the dialog box, there are two buttons: Save and Cancel.
  9. Select Save to save the new Exception.

    The image shows a screenshot of a dialog box within the SAP Concur user interface for creating a new exception. The dialog box is titled New Exception. It contains three input fields: Exception Code, Exception Level, and Message. At the bottom right of the dialog box, there are two buttons: Save (highlighted in yellow) and Cancel.
  10. Select Done to save the audit rule.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining exceptions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Exception sub-tab selected. The main form area includes a row of input fields labeled Exception Code, Exception Level, and Exception Text, which are currently empty. Below these fields, there are three buttons: New, Modify, and Remove. Further down, there is a table that lists existing exceptions with columns labeled Code(s), Level, and Message. At the bottom right of the form are three buttons: Cancel, Previous, and Done (highlighted in yellow).

Result

How to Modify an Existing Audit Rule

Follow these steps to modify an audit rule. We'll walk you through each part of the process, complete with detailed instructions and screenshots to help you along the way.

Once you complete these steps, a demo video will be available to reinforce what you've learned and provide a quick recap.

Steps

  1. On the Custom Audit Rules page, select the rule you want to edit. Select Modify.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected and highlighted in yellow. Below the navigation bar, there are search fields with a Search button to find specific audit rules based on given criteria. Below the search area, there are action buttons: New, Modify (highlighted in yellow), Copy, Activate, Deactivate, and Remove, with the Modify button highlighted in blue and outlined in yellow. The main content area displays a table listing various audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes multiple entries.
  2. The Audit Rule step appears.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining or editing an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected and highlighted in yellow. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Audit Rule sub-tab selected and highlighted in yellow. The main form area includes fields for defining the details of the audit rule: Name, Event, Applies To, and Active. At the bottom right of the form are two buttons: Cancel and Next.
  3. Make any desired changes. Choose Next.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining or editing an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected and highlighted in yellow. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Audit Rule sub-tab selected and highlighted in yellow. The main form area includes fields for defining the details of the audit rule: Name, Event, Applies To, and Active. At the bottom right of the form are two buttons: Cancel and Next.
  4. The Conditions step appears.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on setting conditions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Conditions sub-tab selected and highlighted in yellow. Two conditions are defined in the table, each set up with Data Object/Operator, Field/Value, and Operation. Between the two conditions, there is a radio button selection for And or Or to determine how the conditions are combined. At the bottom right of the form are three buttons: Cancel, Previous, and Next.
  5. Edit the condition(s) as needed. Choose Next.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on setting conditions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Conditions sub-tab selected and highlighted in yellow. Two conditions are defined in the table, each set up with Data Object/Operator, Field/Value, and Operation. Between the two conditions, there is a radio button selection for And or Or to determine how the conditions are combined. At the bottom right of the form are three buttons: Cancel, Previous, and Next.
  6. The Exception step appears.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining exceptions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Exception sub-tab selected and highlighted in yellow. The main form area includes a row of input fields labeled Exception Code, Exception Level, and Exception Text, which are currently empty. Below these fields, there are three buttons: New, Modify, and Remove. Further down, there is a table that lists existing exceptions with columns labeled Code(s), Level, and Message. At the bottom right of the form are three buttons: Cancel, Previous, and Done.
  7. Make any selections and desired changes. Select Done to save these changes.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area, specifically focusing on defining exceptions for an audit rule. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below this navigation bar, there are three sub-tabs: Audit Rule, Conditions, and Exception, with the Exception sub-tab selected and highlighted in yellow. The main form area includes a row of input fields labeled Exception Code, Exception Level, and Exception Text, which are currently empty. Below these fields, there are three buttons: New, Modify, and Remove. Further down, there is a table that lists existing exceptions with columns labeled Code(s), Level, and Message. At the bottom right of the form are three buttons: Cancel, Previous, and Done(highlighted in yellow).

    Hint

    If you want to keep the original custom audit rule as it was created by default without modifying it, you can first copy the rule and then make edits to the copy.
    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected and highlighted in yellow. Below the navigation bar, there are search fields with a Search button to find specific audit rules based on given criteria. Below the search area, there are action buttons: New, Modify, Copy (highlighted in yellow), Activate, Deactivate, and Remove, with the Modify button highlighted in blue and outlined in yellow. The main content area displays a table listing various audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes multiple entries.

Result

How to Activate/Deactivate an Audit Rule

Activate a rule with you are ready to use it.

Follow these steps to activate an audit rule. We'll walk you through each part of the process, complete with detailed instructions and screenshots to help you along the way.

Once you complete these steps, a demo video will be available to reinforce what you've learned and provide a quick recap.

Steps

  1. On the Custom Audit Rules page, select the rule you want to activate.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected and highlighted in yellow. Below the navigation bar, there are search fields with a Search button to find specific audit rules based on given criteria. Below the search area, there are action buttons: New, Modify, Copy, Activate, Deactivate, and Remove.The main content area displays a table listing various audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes multiple entries. One of the entries is highlighted in yellow.
  2. Choose Activate.

    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below the navigation bar, there are search fields with a Search button to find specific audit rules based on given criteria. Below the search area, there are action buttons: New, Modify, Copy, Activate (highlighted in yellow), Deactivate, and Remove. The main content area displays a table listing various audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes multiple entries.

    Hint

    Rather than deleting a rule, you can choose to deactivate it. This keeps the rule available for future use if needed. However, if you prefer to permanently delete the rule, select Remove.
    The image shows a screenshot of the SAP Concur user interface within the Custom Audit Rules area. At the top of the section is a navigation bar with four tabs: Compliance Rules, Receipt Handling Options, Expense Limits, and Custom Audit Rules, with the Custom Audit Rules tab selected. Below the navigation bar, there are search fields with a Search button to find specific audit rules based on given criteria. Below the search area, there are action buttons: New, Modify, Copy, Activate, Deactivate (highlighted in yellow), and Remove. The main content area displays a table listing various audit rules with columns labeled Name(s), Event, Exception Code, Applies To, and Active. The table includes multiple entries. One of the entries is highlighted in yellow.

Result

Summary

Thank you for completing this unit!

Throughout the lessons, you have gained a solid understanding on how to work with audit rules in Concur Expense. This unit provided a detailed overview of audit rules basics, including how to create, modify, activate and deactivate them to ensure compliance and streamline your organization's expense management process.

Before you move on from this unit, there is a knowledge check to help reinforce and assess what you've learned.

Log in to track your progress & complete quizzes