What happens when a transaction violates a policy rule?

Short answer

The system flags the transaction, blocks it or routes it for review depending on the violation’s severity, notifies relevant parties, and requires correction or approval before processing. All actions are logged for audit purposes.

On Ramp, policy violations trigger automatic responses based on how you've configured your controls: transactions may be declined at authorization, flagged for cardholder correction, or routed to managers for exception approval.

How Ramp responds to policy violations

Ramp's response depends on the violation type and your policy settings:

Declined at authorization

  • Card transactions that exceed spending limits or use blocked merchant categories are declined before completing
  • The cardholder receives an immediate notification explaining why the transaction was blocked
  • No funds are committed and no cleanup is required

Flagged for correction

  • Card transactions missing required receipts, memos, or categorization are flagged and the cardholder is notified to provide the needed information
  • The employee sees specific guidance about what needs to be added
  • The transaction remains flagged until the required items are provided for review

Routed for approval

  • Transactions can be routed for approval based on your configured expense approval policies, which may include conditions like amount thresholds, accounting coding, department, or expense type
  • Purchases from flagged merchants may require additional review even if under normal limits
  • The approval chain follows your configured hierarchy

Common policy violations Ramp detects

  • Spending limits: Individual transaction limits, daily limits, or monthly card limits exceeded
  • Merchant restrictions: Purchases from blocked merchant categories or specific vendors
  • Missing documentation: Receipts not uploaded within your required timeframe or missing itemization
  • Approval authority: Purchases made without required pre-approval or exceeding cardholder authority
  • Incomplete information: Missing memos, business purpose, or required custom fields

What happens after a violation is flagged

  1. Notification: The cardholder and relevant reviewers receive immediate alerts
  2. Investigation: Managers or admins review transaction details and supporting documentation
  3. Resolution: The transaction is either corrected, approved as an exception, or rejected
  4. Audit trail: Ramp maintains an audit trail for reviews, flags, and approvals for compliance records

If an exception is approved, the approver must document the business justification. If rejected, the cardholder may need to return items or reimburse the company depending on your policy.

Preventing violations before they happen

Ramp's real-time controls help employees stay compliant:

  • Pre-transaction limits: Card controls block unauthorized purchases at point-of-sale
  • Smart notifications: Employees receive reminders to upload receipts and add memos before violations occur
  • Policy visibility: Cardholders can see their limits and restrictions directly in the Ramp app
  • Automated validation: The system checks expense details against policy rules before submission
  • Policy Agent recommendations: Available as a Plus feature when enabled, providing AI-powered review assistance

Related questions

Are policy violations tracked over time?

Yes, policy violations are tracked over time through review queues and flagged transaction logs that capture non-compliant transactions, maintain audit trails, and provide visibility to identify repeat issues, spending patterns, and policy gaps across the organization.

Read more
Can policies be enforced differently by role or department?

Yes, spending policies can be configured with different limits, approval workflows, merchant restrictions, and visibility rules based on a user's department or team within the organization.

Read more
Can spending or expense policy violations be overridden or approved?

It depends on the type of control: hard controls (e.g., blocked merchant categories) decline transactions at purchase and cannot be overridden after the fact. Policy flags or out-of-policy indicators can be reviewed and approved as exceptions by authorized users with documented justification and higher-level approval, with an audit trail.

Read more

Don’t miss key shifts in business spend.