Can admins view a history of changes to an expense policy or restore a previous version?

Short answer

Most expense management platforms don’t provide built-in version control or restoration for expense policy changes, so organizations typically rely on manual change logs or external documentation.

On Ramp, policy change history and version restoration are not currently available as built-in features. Admins can edit policies at any time using the Workflow Builder, but previous versions cannot be automatically restored.

What happens when you edit a policy on Ramp

When you modify an expense policy in Ramp:

  • Changes take effect immediately for future transactions
  • Existing or pending transactions continue to follow the policy that was active when they occurred
  • The system does not automatically create snapshots of previous policy configurations
  • Audit logging for expense policy and workflow edits is limited or not available, though Ramp does provide a consolidated Audit Log feature in Company Settings for Plus and Enterprise plans that covers other administrative actions

How to track policy changes

Since Ramp does not maintain comprehensive automatic version history for policy changes, consider these approaches:

Document changes externally

  • Maintain a change log in a shared document or wik
  • Record the date, admin who made the change, and what was modified
  • Include the business reason for each policy update

Test before publishing

  • Use the Workflow Builder's testing simulator to validate changes before saving
  • Review the policy with stakeholders before implementation
  • Take screenshots of the current policy before making significant changes

Use undo/redo during editing

  • The Simplified Workflow Builder includes undo and redo buttons while you're actively editing
  • These only work during the current editing session and are lost once you save and exit

Editing policies on Ramp

To modify an expense policy:

  1. Navigate to Company > Expense policy
  2. Select the policy category (Expenses, Reimbursements, etc.)
  3. Click Edit to open the Workflow Builder
  4. Make your changes using the condition and step management tools
  5. Use the testing panel to validate the updated workflow
  6. Click Save to publish changes

Changes apply only to new transactions. Transactions already in progress continue following the original policy rules.

Best practices

  • Document before changing. Export or screenshot your current policy configuration before making updates.
  • Communicate changes. Notify managers and employees when approval workflows or requirements change.
  • Review quarterly. Audit your policies regularly to ensure they still align with business needs.
  • Limit editors. Restrict policy editing permissions to a small group of admins to maintain consistency.
  • Test thoroughly. Use the simulator to confirm new workflows route approvals correctly before publishing.

If you need to reference how a policy was configured at a specific point in the past, you'll need to rely on external documentation or contact Ramp support to discuss your specific compliance requirements.

Related questions

How are policy violations surfaced to the employee at the time a transaction occurs?

Policy violations are surfaced through in-app alerts, email notifications, and visible flags on the transaction itself that explain which policy rule was violated and what action is required. Some violations result in real-time transaction declines at the point of sale through spending controls.

Read more

Don’t miss key shifts in business spend.