Every receipt audited. Only the arguments reach you.

What happens to a receipt

Four steps, and only one of them is a model

Reading a crumpled bill is a job for a model. Deciding what your company owes is not.

How receipts arrive

Three ways in, one pipeline

Staff use whatever they already have open, and nobody is trained on anything. Every route lands on the same audit.

A caption or an email body is read too, so “dinner for four” answers the question a receipt rarely prints.

Control without a bottleneck

Budgets that warn you, not ones that stop your staff

A budget that blocks submissions does not reduce spending — it moves the receipt into a drawer until you find out later. Expenze never refuses a receipt; it tells the people whose job it is to act.

Pricing

For the systems you already run

Push a receipt on someone's behalf

# One receipt, one credit. Your base URL is in
# the console under Channels & API.
curl -X POST $EXPENZE_BASE_URL/intake/api \
  -H "Authorization: Bearer $EXPENZE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "staff_id": "M80-4417",
    "idempotency_key": "trip-8821-dinner",
    "image_url": "https://.../receipt.jpg"
  }'

# => { "submission_id": "sub_9f2c...",
#      "status": "auditing",
#      "credits_remaining": 4821 }