Installs in ~2 min· 3 assets · 5 steps

Read every receipt automatically and stop routing small claims to managers

The receipt is read for you, checked against the claim, and small claims never reach a manager at all.

Most expense claims are routine, and most manager time spent on them is wasted. This recipe uses TinyVision to actually read the uploaded receipt (merchant, date, amount, category) then has AI cross-check that against what the employee typed and flag anything out of policy. Claims under their department's limit with no flag are approved automatically. Everything else goes to a manager with the summary already written. The employee always hears back.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Expense Claim Form is submitted
Every run starts from one submission.
Transform
Read Receipt
TinyVision reads the uploaded image and extracts the details.
Transform
AI Extract & Policy Check
AI reads the input and returns a structured result.
Logic
Department Auto-Approve?
Branches on the outcome, so each path is handled.
Action
Notify Finance & Email the Decision
What gets built

3 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormExpense Claim Form

Self-service intake where employees file a claim and attach the receipt. Publishing it auto-creates the Expense Claims response sheet, the single system of record.

EmailReimbursement Decision

Tells the employee the outcome (auto-approved, manager-approved, or rejected) with the AI summary and reasoning.

WorkflowProcess Expense Claims

Runs on every claim: logs it, reads the receipt with TinyVision, runs the AI cross-check, then auto-approves under the department threshold or routes to a manager, notifying finance and emailing the employee either way.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Approval And Notification
Slack *

Sends the manager approval request (with the AI summary and secure review link) and notifies the finance channel once a manager approves a claim. Swap for Telegram or Discord.

Employee Notification
Gmail *

Emails the employee the outcome: auto-approved, manager-approved, or rejected. Swap for Brevo.

How it works

Step by step, once it is running.

  1. 01
    An Employee Files a Claim

    The employee fills the Expense Claim Form (department, category, amount, expense date, business justification, reimbursement method) and attaches the receipt. Submitting fires the workflow and stores the claim with status Pending Review. One link, one submission, no email thread with an attachment nobody can find later.

  2. 02
    TinyVision Reads the Receipt, AI Cross-Checks It

    This is the part that's genuinely different: a TinyVision step reads the receipt image itself and extracts the merchant name, transaction date, amount, and category. Nobody retypes what's already printed on the receipt. An AI step then compares that extraction against what the employee claimed, flags anything outside the expense policy you set at install, and writes a one-line summary for the manager.

  3. 03
    Under the Department Limit? Auto-Approved.

    Sales, Marketing, and Engineering each get their own auto-approval threshold, all configurable. A claim under its department's limit with no policy flag is approved on the spot (no manager step, no queue) and the employee is emailed immediately. This is where the time actually comes back.

  4. 04
    Over the Limit? The Manager Decides.

    Claims above the department threshold, or flagged by the AI policy check, go to the right manager in Slack with the AI summary, the extracted receipt details, and a secure review link. One tap to approve or reject. The manager only sees the claims that genuinely need a person.

  5. 05
    Finance Is Notified, the Employee Always Hears Back

    Manager-approved claims post to the finance channel with the reimbursement method attached, so payout can be scheduled without a follow-up message. Auto-approved, manager-approved, or rejected, the employee is emailed the outcome every time, with the AI policy notes included on a rejection so they know exactly what went wrong.

What you walk away with
FAQ

Questions about Expense Reimbursement Workflow.

Does someone have to type the receipt details?
No. A TinyVision step reads the uploaded receipt image and extracts the merchant, date and amount, then AI cross-checks those against what the employee typed. Mismatches surface before anyone approves the claim.
How do the auto-approval limits work?
Each department has its own threshold, configured separately for sales, marketing and engineering at install. Claims under a department's limit are approved automatically, and only claims over it pause for a manager decision.
What do I need to connect?
Slack and Gmail. Slack carries the manager approval request to a named approver, and Gmail sends the reimbursement decision to the employee. Telegram, Discord, Google Chat, Brevo and Microsoft Outlook are supported swaps.
Does the employee always find out what happened?
Yes. Approved or rejected, the decision is emailed to the employee and finance is notified in the same run. The Reimbursement Decision email is a workspace asset you can reword to match your policy language.
Can I encode our expense policy?
The expense_policy value is set at install and is what the AI cross-check evaluates against, so the policy text you paste is the standard each claim is measured by rather than a generic default.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.