Streamlining the Expense Approval Process
We just saw how Audit Rules can compare the amounts on an expense report to those on the associated request. In our example, if these rules are violated, the expense report will get tagged with the Exception Codes associated with those rules: OVERREQ and OVERREQ2. In the Workflow, we can evaluate which Exception Codes are on an expense report and take appropriate action.
In this case, we'll create a Workflow Rule to confirm these codes are NOT present. If this is true, it means the expense report and all of the request-related line items are less than the associated request and its line items. Since the actuals are less than the estimate, we can configure the Workflow to bypass some of the approval process, such as the Expense Processor step.
Workflow RuleStart by creating a new Workflow Rule on the step you want to skip. In this case, we are creating the rule on the Approval for Processing step because we will skip that step if the expense is less than the request.
Create a rule with the two conditions, as shown in the image.
Rule ActionNext, create a new Rule Action. Set the Action Name to Skip Step and enter an appropriate message to appear in the Audit Trail. See the image below for an example.

You now know some areas you can configure to integrate Concur Request with Concur Expense.