Explaining Audit Rules

Audit Rules can be a powerful tool. You've learned that they can warn users who are pushing the bounds of business policies. You also know they can block users from submitting if they are too far outside the policies.

What many administrators may not know is that Audit Rules can also compare the amounts on two objects that are associated with each other. When integrating Concur Request and Concur Expense, we can use this feature to compare amounts on an expense report to amounts on an associated request.

This rule flags any expense report where the total on the report is greater than the total on the associated request. It already exists in many Concur Expense sites. It is called Request - Report Total exceeds Request Total and must be activated for you to take advantage of it.

If the site does not already have this rule, you can create it using the conditions in the image below. This rule should be configured to use the Report Submit Event. It is recommended to use an Exception Level less than 99; in this scenario, we'll say we used OVERREQ as the Exception Code. We'll use that code in the next lesson.

This rule flags any expense entry that has an amount greater than the amount on the associated request entry. It already exists in many Concur Expense sites. It is called Request - Expense Entry Amount exceeds approved Request Entry Amount and must be activated for you to take advantage of it.

If the site does not already have this rule, you can create it using the conditions in the image below. This rule should be configured to use the Entry Save Event. It is recommended to use an Exception Level less than 99; in this scenario, we'll say we used OVERREQ2 as the Exception Code. We'll use that code in the next lesson.

This rule prevents the user from submitting an expense report unless a request has been attached. It already exists in many Concur Expense sites. It is called Request - Must attach request to expense report and must be activated for you to take advantage of it.

If the site does not already have this rule, you can create it using the conditions in the image below. This rule should be configured to use the Report Submit Event and utilize an Exception Level of 99.

Only use this rule if every expense report MUST have a request attached. If that is not the case in the environment, you can lower the Exception Level or leave the rule inactive.

You have learned that allocations can automatically copy from the request to the expense report. There may be some instances where the allocations on the expense report are not valid after the copy. This rule allows users to submit an expense report if the allocations are correct. It already exists in many Concur Expense sites. It is called Fully Allocated and must be activated for you to take advantage of it.

If the site does not already have this rule, you can create it using the conditions in the image below. This rule should be configured to use the Report Submit Event and an Exception Level of 99.

In this lesson, you learned how Audit Rules can be used in the integration. In the next lesson, you'll take a look at how Workflows can impact the integration.