submit-reimbursement

Non-Negotiables

• Never submit without confirming the details with the user first. Show amount, merchant, memo, fund, and accounting categories before submitting.
• Receipts must be base64-encoded for upload. Accepted types: PNG, JPEG, PDF, HEIC, WEBP.
• All CLI flags use underscores, not hyphens (e.g., --fund_uuid, --page_size).
• Reimbursement amounts are in dollars (not cents).
• After editing, always check missing_items in the response. Do not submit until all required items are resolved.

Workflow

Step 1: Upload the receipt

The user must provide a receipt file. Base64-encode and upload it:

# Encode the file
base64 -i /path/to/receipt.pdf | tr -d '\n'

# Upload (no --transaction_uuid — this is for a new reimbursement, not a card transaction)
ramp receipts upload \
  --content_type "application/pdf" \
  --filename "receipt.pdf" \
  --file_content_base64 "{base64_string}"

Response returns receipt_uuid. Save it for the next step.

Step 2: Create a draft reimbursement from the receipt

ramp reimbursements create {receipt_uuid}

Response returns:

• reimbursement_uuid — the draft reimbursement ID
• suggested_memos — AI-generated memo suggestions based on the receipt
• suggested_codings — suggested accounting category selections
• suggested_funds — suggested spend allocations to charge
• missing_items — what still needs to be filled in before submission
• reimbursement_link — direct link to view in the Ramp app

Step 3: Fill in required fields

Check missing_items from the create response. Common required fields:

Missing item	How to fill
missing_memo: true	Edit with --memo
missing_fund: true	Edit with --fund_uuid (pick from suggested_funds or list funds)
missing_tracking_categories (non-empty)	Edit with --json to set category selections
missing_receipt: true	Should not happen if you created from a receipt

Use suggestions from the create response when available: