How do you analyze Ramp spend data in Metabase?

{
  "mcpServers": {
    "ramp": {
      "type": "http",
      "url": "https://mcp.ramp.com/mcp"
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a scoped Ramp export - creates a table and a model
mb upload csv --file ramp-export.csv --collection "Finance & Accounting"

# Refresh the same table later
mb upload replace <table-id> --file ramp-export.csv

Create a polished Metabase dashboard for Ramp finance analytics.
Work end to end: find existing modeled data first; if none exists, load a minimal
read-only snapshot or describe the warehouse sync required.

Goal: Connect Ramp to Metabase for card spend, bills, reimbursements, vendor concentration, policy compliance, and accounting-close dashboards.

Inspect before querying:
- Inspect actual tables, column names, currencies, status values, and timestamps.
- Do not assume the source schema matches this guide exactly.
- Reconcile source totals before publishing any finance KPI.

Important:
- Do not claim Metabase connects natively to Ramp; it reads a
  supported database or CLI-uploaded tables.
- Keep native amount, native currency, and reporting-currency amount separate.
- Distinguish authorization, posting, payment, settlement, and reconciliation
  states where the source exposes them.
- Use stable business keys and apply updates/deletes during incremental syncs.
- Exclude account numbers, personal data, and secrets from broad dashboards.
- Only build cards whose required fields and history are actually present.

Dashboard sections:
1. Finance overview: Month-to-date spend; Spend vs. budget; Top vendors; Card, bill, and reimbursement mix.
2. Operations: Transactions awaiting review; Missing receipts; Bills due; Reimbursements awaiting approval.
3. Controls and reconciliation: Out-of-policy transactions; Missing GL or department coding; Duplicate vendor candidates; ERP sync failures.
4. Planning and trends: Department run rate; Vendor renewal exposure; Committed vs. actual spend; Savings and consolidation opportunities.

Suggested models: modeled_ramp_spend, modeled_ramp_policy_exceptions, modeled_ramp_bills, modeled_ramp_budget_actuals.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. State refresh time, reporting
currency, accounting basis, and any reconciliation caveats.

SELECT
  date_trunc('month', transaction_date) AS month,
  department_name,
  SUM(amount) AS spend
FROM modeled_ramp_spend
WHERE transaction_state = 'CLEARED'
GROUP BY 1, 2
ORDER BY 1, 3 DESC;

Turn uncoded transactions and missing receipts into a finance operations queue.

SELECT
  department_name,
  COUNT(*) AS transactions_to_review,
  SUM(amount) AS spend_to_review
FROM modeled_ramp_spend
WHERE transaction_state = 'CLEARED'
  AND (gl_account_id IS NULL OR receipt_status <> 'RECEIVED')
GROUP BY 1
ORDER BY spend_to_review DESC;