finance_ops · finance · workflow
Ramp AI agent autonomously fixes merchant classifications in under 10 seconds
Incorrect merchant classifications frustrated Ramp customers, and the manual process of fixing them — handled by customer support, finance, and engineering teams — took hours per request and could not scale as Ramp grew.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User submits correction request
A Ramp user reports an incorrect merchant classification by providing a new merchant name, website, and category via the transaction UI.
Tools used
LLMembeddingsOLAPRAGStripe
Outcome
The AI agent handles close to 100% of merchant classification fix requests autonomously, resolving them in less than 10 seconds instead of hours, while improving nearly 99% of transaction classifications. Before the agent, manual teams could service only 3% of requests in 2023 and 1.5% in 2024; resolution costs dropped from hundreds of dollars per request to cents.
Results
Time savedless than 10 seconds
Volumefewer than 10%
Cost replacedhundreds of dollars
Grounding & classification
Source type: technical build writeup
42 fields verified against source quotes.
agentic workflowai agentdata extractionragform submissionreceiptfailure mode describedhuman review describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedfinancial servicessoftwareaccuracy improvementautomation ratecost reductioncustomer satisfactioncycle time reductiontechnical build writeupcustomer supportdata entry opsfinance opsautonomous resolutionextract classify routerag answering