Can Mesh flag anomalies related to expenses?

Mesh identifies and reports various anomalies upon submission of reimbursement requests. These anomalies are presented in a tabular view on the 'Expenses' page and are accessible to users with an Employee profile, as well as to power users, such as those with Admin or Pro profiles.

The anomalies are presented under the 'All' tab in the 'Review Status' column for expenses in status 'Pending' or 'In-Review'. 

When the user clicks the expense, the same information is presented on the upper left side.

Note: Power users have access to a 'Flags' filter to help them identify specific anomalies. 

The following list provides explanations of the available flags:

Action: The platform will flag an expense as	Flag Name	Reason
	Over Budget	A user submits an expense and associates it with a budget named 'other'. Please refer to the reimbursement policy for more details.
	Out of policy	If the expense is assigned to a travel policy, Mesh will first check for Out Of Policy (OOP). If it is OOP, the expense will be flagged as 'Over budget'.  If the expense is not assigned to a travel policy, Mesh will check if the 'Other' budget was selected. If 'Other' was selected, the expense will be flagged as 'Over budget'.
	Duplicate Receipt	A user transacts with a Mesh card, uploads a receipt, and then submits an expense using the same receipt.
	Duplicate Expense	A user submits an expense and then submits the exact same expense again.
	Old Expense	A user submits an expense older than the number of days set in the reimbursement policy.
	Amount Discrepancy	A user submits an expense, uploads a receipt that is scanned by Mesh OCR, and then modifies the amount so it no longer matches the amount detected by the OCR.
	Details Discrepancy	A user submits an expense, uploads a receipt that is scanned by Mesh OCR, and then modifies the details (e.g., merchant, date) so it no longer matches the info detected by the OCR.
	Resubmitted Expense	An expense got declined and the user resubmitted the expense
	Missing Details	The expenses was forcefully submitted without details.

Important: Flags may be used as conditional triggers within the expense approval workflow to determine the appropriate approvers when an expense violates company policy.