It’s time to rewrite your expense policy for AI: Insights from 10,000 expense policies

We read 10,000 expense policies. Most aren't ready for AI.

For decades, expense policies relied on human managers to fill in the blanks. A $150 client dinner? Use your judgment. A gray-area Uber charge? Approve it and move on. The result: inconsistent decisions, shadow spend, and a queue that didn't scale.

AI changed that.

Ramp's agents now review more than a million expenses a month. Three out of four in-policy expenses get approved without a human ever seeing them. The rest get pushed to a manager.

But here's the catch: AI can't approve what isn't clear. Companies with vaguely written policies see roughly twice the rate of expenses kicked back to a person. We call it the policy ambiguity gap.

We analyzed 10,000 real expense policies to understand (1) where the policy ambiguity gap is, (2) what it's costing companies, (3) how the gap is closing, and (4) the four key traits of a successful policy in the AI era.

Where the policy ambiguity gap is

Most expense policies cover the categorical rules: what types of expenses are off-limits and what general exceptions exist. For example, 54% prohibit vice purchases like alcohol, cigarettes, drugs, and gambling, and 63% list allowed exceptions like first-class or business-class upgrades on long flights.

What's almost always missing though is a dollar amount.

• Despite meals being the most common expense category, a daily meal cap is only specified in 66% of policies.
• Only 7% specify an allowable flight amount, the most costly expense category.

The operational rules are often missing too.

• Only 65% specify when a receipt is required.
• Only 48% specify a submission deadline for expenses and/or expense requirements.

Including "no first-class flights" doesn't tell you the maximum economy fare; “require receipts" doesn't tell you whether the threshold is $25 or $100.

What’s interesting is when companies do provide specifics, the numbers converge.

• The median meal cap is $70. Breakfast, lunch, and dinner land at $15, $20, and $35 across nearly every industry.
• Receipt requirement thresholds cluster at $25.
• Submission deadlines are usually around 14 days.

There's an invisible standard most companies follow; many just haven't documented it.

What unenforceable rules cost

An agent only makes a judgement call when it’s certain and escalates otherwise. Companies with vaguely written policies see roughly 100% more transactions flagged than those with clear policies. That’s twice as much manual review and twice as many "is this OK?" questions that distract from strategic work.

The other cost is spend that gets approved even when it shouldn't be. Approvers might sign off on a $200 dinner that violates a written $75 cap because nobody actually checks against the policy. That’s non-compliant spend that likely would never get uncovered. Other times, there may be no rule at all, so enforcement depends on the reviewer’s interpretation; one might approve a $150 client dinner, another might reject a $100 one.

How AI helps close the gap

Every time the agent escalates to a human, it's also a signal that the policy needs to be clearer.

Even in gray areas, it considers context a human reviewer rarely could at scale, like vendor history, submitter patterns, or past approvals. When it still can't make a call, it surfaces the ambiguity as a suggestion to tighten the rule, so the next similar expense doesn't need a human at all. The result is a self-enforcing loop:

• Finance refines what's vague. With the agent’s suggestions, the average customer updates their policy 2 or more times within six months and at 7x the rate of customers without it (44% vs 6.4%).
• The agent enforces what's tightened. Across customers on the agent for 6+ months, agent-unsure rates decline by roughly 60% from month one to month six.
• Employees’ behavior recalibrates. Agent-driven rejection rates peak in the first 30 days post-activation, then begin declining as employees adjust their spending.

Over time, the gap shrinks toward whatever residual ambiguity is genuinely irreducible, the true novel situations and edge cases that will always warrant human review.

Four traits of a policy AI can actually enforce

After nearly a year of Ramp's agent reviewing expenses, a clearer picture of AI-ready policies has emerged. They share four traits:

1. Specific rules, not vibes. The cleanest policies use explicit dollar amounts and categories rather than language like "reasonable" or "appropriate."
2. The right number of categories. Policies with too few categories treat distinct kinds of spend the same. Too many create distinctions that don't matter. Both extremes result in higher agent-unsure rates, so the sweet spot seems to be three to five with context-specific exceptions.
3. Flexibility built for the real world. Rigid caps that don't account for taxes, tips, or regional pricing wrongly flag transactions and create unnecessary back-and-forth. The cleanest policies bake the latest tolerance into the cap itself. Ramp's own policy, for example, uses the GSA per diem rate plus 10%, which auto-adjusts by city. The agents enforce the latest GSA per diem rates, lodging rates, and mileage reimbursement rates, so manual adjustments to hard-coded amounts aren’t necessary.
4. A review cadence. A meal per-diem set in 2024 is overly restrictive in 2026. The cleanest policies are refined as the agent surfaces patterns and benchmarks, not refreshed once a year and forgotten.

What that means in practice

Most teams we talk to aren’t stuck on understanding the value of an agent expense reviewer; they’re stuck on writing a defensible policy. They don’t know what "good" looks like for a company of their size and industry, what categories they should include, and what thresholds to set.

Ramp's Policy Builder generates a personalized expense policy from the same dataset that powers this analysis: basic questions about a company, every rule benchmarked against peers, and language an AI agent can reliably act on while escalating just the exceptions to human.

Make sure your policy isn't outdated.

Build a policy built from the best practices of 10,000+ peers.

Build my free policy.