FINANCE

Detect duplicate and split expense charges for review

Scans the latest Stripe charges for duplicate submissions and amounts split to stay under approval limits, logs the suspected pairs to Notion.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled scan begins
  • ActionFetch recent Stripe chargesStripeStripe
  • LogicCluster duplicates and split charges
  • ActionLog suspected cases to NotionNotionNotion
  • OutputEmail approver consolidated listGmailGmail

What it does

Looks for two common expense problems: the same charge submitted twice, and a large purchase split into several smaller charges to slip under a per-transaction approval ceiling. It clusters charges by merchant, amount, and time window, flags suspicious groupings, and stages them for an approver rather than auto-rejecting.

When to use it

Use this to catch accidental double-submissions and deliberate threshold-gaming before reimbursement. Useful for finance teams that have a single-charge approval limit and want a safety net against split spending.

How it works

  1. 1A schedule starts the scan.
  2. 2Fetch recent charges from Stripe over the lookback window.
  3. 3A logic step clusters charges by merchant and timeframe, marking exact duplicates and clusters that together exceed a limit while individually staying under it.
  4. 4Each suspected case is written to a Notion database with the linked charges and a flag type.
  5. 5Gmail sends the approver one email listing every cluster to confirm or dismiss.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect GmailRead, draft, send, label.
  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.