receipt-compliance

Non-Negotiables

• Scope to the user's own transactions unless they explicitly request broader access.
• Never upload a receipt without confirming the match — wrong receipt on wrong transaction is worse than no receipt.
• When running in sweep mode, present the plan before uploading. Let the user confirm.
• Use ramp transactions missing {uuid} as the reliable check for whether a receipt is attached — it returns missing_receipt: true/false in real time. The receipt_uuids field in the list response can be used as a quick filter, but it may be stale (e.g., remaining null even after a successful upload+attach).
• Receipts must be base64-encoded for upload. Accepted types: PNG, JPEG, PDF, HEIC, WEBP.
• All CLI flags use underscores, not hyphens (e.g., --from_date, --transaction_uuid).

Workflow

Mode 1: Upload a specific receipt

When the user has a receipt file and wants to attach it to a transaction:

# Find the transaction
ramp transactions list --transactions_to_retrieve my_transactions \
  --from_date {date} --state cleared --agent --page_size 20

# Base64 encode the file (agent does this)
# For a file at /path/to/receipt.pdf:
base64 -i /path/to/receipt.pdf | tr -d '\n'

# Upload and auto-attach in one step
ramp receipts upload \
  --content_type "application/pdf" \
  --filename "receipt.pdf" \
  --file_content_base64 "{base64_string}" \
  --transaction_uuid {txn_uuid}

The response returns receipt_uuid and attached_to_transaction: true/false.

If --transaction_uuid is omitted, the receipt is uploaded but not attached. You can attach later with:

ramp receipts attach {receipt_uuid} {transaction_uuid}

Mode 2: Compliance sweep — find all missing receipts

ramp transactions list --transactions_to_retrieve my_transactions \
  --from_date {start} --to_date {end} --state cleared --agent --page_size 50

Filter results for transactions where receipt_uuids is null or empty. You can also check missing_items on individual transactions: