transaction-cleanup

Non-Negotiables

• Scope to the user's own transactions by default (--transactions_to_retrieve my_transactions).
• Show the transaction details before editing. Never blind-edit.
• For bulk edits, present the plan and confirm before executing.
• The --user_submitted_fields flag tracks provenance — include it to mark which fields the user explicitly provided vs agent-inferred.
• All CLI flags use underscores, not hyphens.

Workflow

Step 1: Find transactions needing attention

# Transactions awaiting your action (usually means missing items)
ramp transactions list --transactions_to_retrieve my_transactions \
  --from_date {start} --state cleared --agent --page_size 50

For any transaction, check what's missing:

ramp transactions missing {transaction_uuid}

Returns: missing_receipt (bool), missing_memo (bool), missing_accounting_items (array of category names).

Step 2: Get AI-suggested memos

Before writing memos manually, check if Ramp has suggestions:

ramp transactions memo-suggestions {transaction_uuid}

Returns memos[] — an array of suggested memo strings based on the transaction context.

Step 3: Edit transactions

Set a memo

ramp transactions edit {transaction_uuid} --memo "Q2 team offsite catering"

To clear a memo, pass an empty string: --memo ""

Assign to a fund/spend allocation

ramp transactions edit {transaction_uuid} --fund_uuid {fund_uuid}

To find available funds:

ramp funds list --funds_to_retrieve MY_FUNDS --include_balance --agent

Set tracking categories (accounting codes)

First, get available categories and their options:

# List categories
ramp accounting categories --agent

# List options for a specific category (use UUID from above)
ramp accounting category-options {tracking_category_uuid} --agent --page_size 50

Then edit via --json (tracking categories aren't exposed as named flags).

Important: When using --json, you must include transaction_uuid in the body. The --json flag bypasses the CLI's automatic injection of the positional arg.