FINANCE

Triage emailed expense receipts against policy

Watches a shared finance inbox for emailed receipts, extracts amount, vendor, and category.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew receipt email in finance inboxGmailGmail
  • ActionExtract vendor, total, and line items from receiptOpenAI
  • LogicCheck charges against spend policy rules
  • ActionPost compliant expenses to approvals channelSlack
  • OutputFlag violations with the broken rule to submitter channelSlack

What it does

Monitors a dedicated finance inbox for incoming expense receipts (forwarded emails with PDF or image attachments), reads the receipt with an LLM, and validates each charge against your written spend policy — per-meal caps, alcohol restrictions, missing itemization, and category limits. Clean expenses are posted to an approvals channel ready to sign off; policy violations are flagged with the exact rule they break.

When to use it

Use this when employees email or forward receipts to a central address and your AP team is manually opening each one. It removes the read-and-check step so reviewers only see a structured summary and a clear verdict.

How it works

  1. 1A new email lands in the monitored finance inbox.
  2. 2The flow downloads the receipt attachment and extracts vendor, date, line items, and total via OpenAI.
  3. 3Policy logic compares the extracted fields to your spend rules and tags the expense compliant or non-compliant with a reason.
  4. 4Compliant expenses post to a Slack approvals channel with an approve action.
  5. 5Violations post to a separate Slack channel naming the broken rule for the submitter to fix.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  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.