Finance ops · Production

Liquid Measurement Systems reduces fraud, improves UX, and drives efficiency with Ramp

The problem

LMS was locked into an archaic corporate spend program with a legacy banking partner that lacked mobile receipt tools, had poor customer service with slow response times for card issues, and allowed frequent fraudulent charges on the business development team's cards.

First attempt

The legacy provider lacked mobile functionality for receipt uploads, had unresponsive customer service for card statement issues, and failed to prevent frequent fraudulent charges.

Workflow diagram · grounded in source
1
Mobile receipt submission
Trigger
Employees submit receipts and manage expenses directly from their phones.
▾ source quote
“They do everything through their phones now”
2
Real-time expense coding
Integration
Employees code their expenses in real-time within Ramp's platform.
▾ source quote
“Because people can do their own receipts so easily and code in real-time”
3
AI chatbot support
Ai action
Ramp's AI chatbot provides instant feedback to users during setup and training.
▾ source quote
“I could also ask for instant feedback from Ramp's AI chatbot. That was phenomenal”
4
Accountant end-of-month review
Human review
The accountant has minimal work to do at the end of the month.
▾ source quote
“our accountant has minimal work to do at the end of the month”
5
Virtual card fraud protection
Validation
Users hold both a virtual and physical card to protect against card compromise.
▾ source quote
“The majority of users have both a virtual and physical card. That's a great thing for security protection -- if the physical card gets compromised, they still have access to the virtual card”
Reported outcome

After switching to Ramp, one team member saved 4-5 hours per month previously spent chasing receipts, employees now self-manage expenses entirely via phone, the accountant has minimal end-of-month work, and the team has freed capacity to refocus on strategic projects.

Reported metrics
Time saved per month chasing receipts4-5 hours per month
Platform activation timetwo-day activation
General ledger import timeless than five minutes
Accountant end-of-month workloadminimal work to do at the end of the month
Show all 5 reported metrics
time saved per month chasing receipts4-5 hours per month
platform activation timetwo-day activation
general ledger import timeless than five minutes
accountant end-of-month workloadminimal work to do at the end of the month
overall time savingssignificant time-savings
Reported stack
RampRamp's AI chatbot
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://ramp.com/customers/liquid-measurement-sytems
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

After switching to Ramp, one team member saved 4-5 hours per month previously spent chasing receipts, employees now self-manage expenses entirely via phone, the accountant has minimal end-of-month work, and the team h…

What tools did this team use?

Ramp, Ramp's AI chatbot.

What results were reported?

Time saved per month chasing receipts: 4-5 hours per month; Platform activation time: two-day activation; General ledger import time: less than five minutes; Accountant end-of-month workload: minimal work to do at the end of the month (source-reported, not independently verified).

What failed first in this deployment?

The legacy provider lacked mobile functionality for receipt uploads, had unresponsive customer service for card statement issues, and failed to prevent frequent fraudulent charges.

How is this finance ops AI workflow structured?

Mobile receipt submission → Real-time expense coding → AI chatbot support → Accountant end-of-month review → Virtual card fraud protection.

Related finance ops cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Finance ops cases →