FINANCE

Catch expense charges with missing or mismatched receipts

When a new expense row lands in Airtable, it cross-checks the claimed amount against the matching Stripe charge and routes any missing-receipt or amount-mismatch cases…

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew expense row in AirtableAirtableAirtable
  • ActionFind matching Stripe chargeStripeStripe
  • LogicCheck receipt + amount tolerance
  • ActionUpdate Airtable row with review statusAirtableAirtable
  • OutputNotify approver in SlackSlack

What it does

Reconciles employee-submitted expense rows against actual Stripe charges. For each new Airtable submission it finds the corresponding card transaction, compares amounts, and checks whether a receipt is attached. Clean matches auto-clear; anything missing a receipt or off by more than a tolerance is marked for review.

When to use it

Use this when employees log expenses in Airtable and you want to stop chasing receipts manually. It surfaces exactly the rows that need human eyes — missing documentation or amounts that don't line up with the card record.

How it works

  1. 1A new or updated Airtable expense row triggers the run.
  2. 2Look up the matching charge in Stripe by amount, date, and merchant.
  3. 3A logic step decides: receipt present and amount within tolerance clears automatically; otherwise it is a review case.
  4. 4Flagged rows are updated in Airtable with a status and the discrepancy reason, landing them in the approver's review view.
  5. 5Slack posts the approver a message naming the employee, amount, and what failed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect StripeCustomers, subscriptions, payments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.