FINANCE

Normalize Multi-Currency Expenses and Flag Policy Violations Before Approval

When a Stripe-captured expense lands, it converts the amount to your base currency at the transaction-date FX rate, checks it against per-category spend limits.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Stripe expense charge capturedStripeStripe
  • ActionFetch transaction-date FX rate and convert to base currencyHTTP webhook
  • LogicCheck normalized amount against category limits and receipt rules
  • LogicBranch: compliant (auto-approve) vs. violation (flag with reason)
  • OutputPost approve/flag decision to finance Slack channelSlack

What it does

Every expense charged through Stripe gets normalized to a single base currency and screened against your reimbursement policy before a human ever sees it. Compliant expenses are pre-approved; anything over a category cap or missing a receipt is flagged with the specific rule it broke.

When to use it

Use this when employees expense in multiple currencies and your finance team wastes time manually converting amounts and eyeballing policy limits. It removes the FX math and the first-pass rule check from the approver's job.

How it works

  1. 1A new Stripe charge tagged as an expense triggers the run.
  2. 2An HTTP call fetches the FX rate for the charge's currency on its transaction date and converts the amount to base currency.
  3. 3The normalized amount is checked against per-category limits and receipt requirements.
  4. 4A branch splits compliant expenses (auto-approve) from violations (flag with reason).
  5. 5The decision, original and normalized amounts, and any violated rule are posted to the finance Slack channel for final sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  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.