Credit Card Statement Date
Use this template to create a business rule which enforces that all credit card transactions for a statement period must be included in one expense report.
This business rule fires when an expense report is submitted.
Parameters
The template has these parameters.
- Check for transactions from mixed statement periods
- Select this check box to trigger the business rule if the credit card transactions in the expense report are from different statement periods.
- Check for unattached transactions from the same statement period as the attached
- Select this check box to trigger the business rule if duplicate unattached transactions are found for the same statement period.
- Use import date instead of statement date
- Select this check box to trigger the business rule if import date is used instead of statement date for the credit card transactions.
- Include attached but not submitted
- Select this check box to trigger the business rule if the credit card transactions are attached to an expense report but the report is not submitted.
Example: This example lists the possible values for this business rule:
| Fields | Value |
|---|---|
| Name | Credit Card Statement date |
| Severity | Explanation |
| Notification | Interactive and Report |
| Fire on Itemization | Submit ER |
| Fire Scope | Every Time |
| Status | Active |
| Policy Based routing | NA |