Validation Options (Expense)

The validation options screen gives administrators various choices on how to deal with such issues as advance amounts, duplicate charges, invalid expense types, incomplete reports, invalid organizational attributes, and invalid WBS codes. Below is a description of these out of the box options

Name	Validation Options	Flag As: this option is primarily for the approvers and for reporting purposes
Report has invalid WBS	Validation Failed (Notes Might be Required): will prevent users from submitting a report if the WBS attributes are invalid. A WBS may become invalid if it is marked inactive, closed or no longer assigned to the Expense Type chosen. Validation Warning: warns the user that the WBS is invalid, but will not prevent submission. Ignore: skips WBS validation.	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains Future Charges (Non TA Reports)	If a non-Travel Authorization report includes an expense line item with a future date: Validation Failed (Notes Might be Required): prevents user from submitting a report with a future dates charge Validation Warning: warns a user that an expense report includes a future dated charge, but does not prevent user from submitting another request. Ignore: skips this validation.	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report has invalid OBS	Validation Failed (Notes Might be Required): will prevent users from releasing a report if their organization attributes have become inactive since they created the report. Users will have to delete the report and recreate a new one to reflect the new changes in their organizational attributes such as operating unit, department or location, etc. Validation Warning: warns the users that the organization attributes have changes since the report was first created. Ignore: skips OBS validation.	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains possible duplicate charges	Validation Failed (Notes Might be Required): prevents user from submitting a report with possible duplicate entries within the same report. Unless notes provided. Validation Warning: warns the user and flags the line. Ignore: skips any duplicate validation This validation can be enabled to apply to all expense types, but specific expense types can be excluded from Exclude from Duplicate page	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Reimbursement Policy	Validation Failed: triggers validation against any expense policy created. Ignore: allows ignoring the expense policy validations.	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains modified lines different from preauthorized report	Validation Warning: flag an expense report if the an expense report is based on the pre-approved travel authorization and the expense lines are different than what was approved on the corresponding TA Ignore: ignores the validation above	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report is Incomplete	During the validation process, if this option is set to Validation Failed the system will check the following details on the report being submitted for completeness: The required additional fields are provided on the report cover page Confirm the values selected in the drop down fields on the cover page are still active Make sure the WBS distribution on the cover page is valid (in case the WBS has expired or unassigned) and adds up to 100% Confirm credit card transaction(s) are not applied on another report Check the line level required notes are provided Confirm the attendees are provided when required Check if the per diem dates are overlapping Check if a per diem expense includes more than one traveled to city in the same date Confirm the payment type is valid Confirm the required cities are provided Confirm the line level additional fields are provided and the values in the drop down list of options are still active Confirm the required itemization is completed and accurate Confirm the WBS selections are accurate Validation Failed: If any of the above details are missing or incomplete, the validation will fail. Ignore: Ignores the details above
WBS Policy	Validation Failed : triggers validation against any expense WBS policy created. Ignore: allows ignoring the WBS policy validations	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains possible duplicate across Approved reports	Validation Failed (Notes Might be Required): prevents user from submitting a report with possible duplicate entries across the current and other approved reports. Unless notes provided. Validation Warning: warns the user and flags the line. Ignore: skips any duplicate validation This validation can be enabled to apply to all expense types, but specific expense types can be excluded from Exclude from Duplicate page	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Advance based on preauthorization not paid yet	Validation Failed (Notes Might be Required): Fails validation if a user tries to create an expense report based on an approved authorization report, but a cash advance payment was requested on that pre-authorization and that advance is not yet paid. Validation Warning: Generates a validation warning but will not stop a user from submitting the report Ignore: ignores this case scenario	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Custom Validation	Validation Failed: triggers custom validation event, if any have been created on the customer database Ignore: Allows ignoring and bypassing the custom validations created on the customer database, if any	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains advance request while other requests are still outstanding	Validation Failed (Notes Might be Required):prevents user from submitting a request for a cash advance while other requests are still pending. Validation Warning: warns user that a previous request for advance is pending, but does not prevent user from submitting another request. Ignore: Skips the validation above	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Trip and TA are not matching (This option is no longer used, it used to apply to the booking data vs TA)	Validation Failed (Notes Might be Required): prevents user from submitting a and expense report if the approved travel authorization and the expense report are not matching. Validation Warning: warns user that the TA and the report are not matching, but will not stop a user from submitting the report. Ignore: Skips the validation above	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains possible duplicate charges with credit card transaction	Validation Failed (Notes Might be Required): prevents user from submitting a report with out of pocket reimbursable charges that are possible duplicates of unapplied credit card charges. Unless notes provided. Validation Warning: warns the user and flag the line for this validation. Ignore: skips any duplicate validation	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line
Report contains invalid expense type	Validation Failed (Notes Might be Required): prevents user from submitting a report if any Expense Types are invalid. Expense Types may become invalid if they are marked inactive or are no longer assigned to the WBS chosen. Validation Warning: warns user that the Expense Type is no longer valid, but does not prevent the user from submitting the report. Ignore: Skips the validation above	High Warning high importance validation flag will be attached to the flagged line Information Only attaches a validation for information purposes Low Warning low importance flag will be attached to the flagged line