What problem does it solve? Answering "how much did we spend on X" requires pulling data from two separate Ramp resources — card transactions and bill payments — with no unified spend endpoint, plus handling inconsistent amount formats, pagination, and vendor name variants. This Skill provides a complete workflow for producing accurate vendor spend reports without double-counting or missing pages. ## Core Features & Use Cases - Vendor Spend Analysis: Query card transactions and bill payments for a specific vendor or all vendors over a date range, then aggregate into a spend table. - AI and Token Spend Reporting: Combine financial spend with estimated token cost via ramp ai-spend commands, reported separately to avoid overlap. - Data Integrity Guardrails: Handles string vs numeric amount formats, refunds, pagination via next_page_cursor, vendor name variant detection, and the rule that bill invoice amounts are not paid-in-period spend. - Use Case: A finance lead asks for a full SaaS vendor breakdown for Q1. The Skill pulls all transactions and bills with payment activity, paginates to completion, groups by merchant, flags name variants like "Delta Air Lines" vs "Delta Airlines", and presents a table separating confirmed card spend from bills requiring payment-allocation data. ## Quick Start Ask the agent to analyze how much your company spent on a specific vendor this quarter, including both card transactions and bill payments.
