Can users see why a transaction was marked as non-compliant?
Short answer
Yes. Users receive specific explanations for non-compliant transactions, including which rule was triggered, what information is missing, and what action is required to resolve the issue.
On Ramp, cardholders and reviewers see detailed reasons directly on the transaction, including the specific policy rule or requirement triggered, required documentation, and what needs to be completed for review or approval.
How flagged transactions appear
When a transaction requires attention due to company policy or missing information, Ramp flags it immediately and communicates the specific issue:
- Policy rule or flag type: The specific policy or requirement that was triggered (e.g., "Meals over $50 require itemized receipt," "Weekend spend," "Blocked category")
- Flag details: What triggered the flag (amount limits, missing receipt, restricted merchant, duplicate receipt)
- Required action: What the user must do to resolve it (upload receipt, add memo, provide accounting fields)
- Review requirements: Whether the transaction requires manager review or approval
Flags appear as visual indicators on the transaction card, with full explanations available when you click into the transaction details.
Common flags
Ramp identifies several types of issues that require attention:
- Spending limits: Transaction exceeds category or merchant limits
- Missing required fields: Receipt, memo, category, or accounting fields required but not provided
- Restricted merchants: Purchase from a blocked vendor category
- Approval requirements: Transaction requires pre-approval or manager review
- Receipt issues: Missing, non-itemized, or duplicate receipts
Each flag includes specific guidance on how to address the issue.
How flagged transactions are resolved
The resolution process depends on the type of flag and your company's workflow configuration:
- Review-required transactions: Transaction can move forward but requires manager review. The flag remains visible to approvers with full context about the policy concern or missing information.
- Required fields: Transaction needs certain information completed (receipt upload, memo, accounting fields) before it can be fully processed. The user must provide the required information for the expense to move forward.
- Employee context: Employees can provide context through memos and comments that reviewers can see when evaluating flagged transactions. This helps managers understand the business justification when reviewing exceptions.
Audit trail and visibility
Ramp maintains a complete record of transaction flags and actions:
- Flag history: When the flag was triggered and what rule or requirement caused it
- User actions: What the cardholder did to address the issue
- Approval decisions: Whether managers approved the transaction and any notes provided
- Policy changes: If the transaction was retroactively affected by policy updates
Finance teams can review patterns in flagged transactions to identify whether policies need adjustment or whether additional training is needed.
Related questions
If an employee uploads the wrong receipt, the receipt should be flagged as incorrect, and the employee must provide the correct documentation. The incorrect and corrected receipts should both remain tied to the transaction so there is a full record for audits.
Read moreCompliance rules translate broad regulatory requirements into specific, enforceable procedures that employees and systems can follow. They define spending limits, approval workflows, documentation standards, and monitoring thresholds that ensure regulatory obligations are met consistently across all transactions.
Read moreReimbursement disputes during audits are resolved by submitting complete supporting documentation—receipts, invoices, and transaction records—within audit deadlines, reconciling internal records against external statements to identify discrepancies, and maintaining clear approval trails that substantiate each claim.
Read more