FINANCE
Detect Duplicate and Suspicious Expense Claims
On each new expense, scans Postgres for matching amount, merchant, and date from the same employee to catch duplicates and split-charge patterns.
How it runs
The automated pipeline, trigger to output.
- TriggerNew expense record createdPostgres
- ActionQuery employee's recent expensesPostgres
- LogicScore for duplicates and split patterns
- LogicBranch: clean vs. suspicious
- ActionOpen Linear investigation taskLinear
- OutputAlert finance review channel in SlackSlack
What it does
Every new expense is checked against recent claims from the same employee for duplicates (same merchant, amount, and date) and for split-charge patterns that dodge approval caps. Suspicious claims are held, a structured investigation task is opened in Linear, and finance is pinged in Slack with the matching records side by side.
When to use it
Use it when accidental double-submissions or deliberate split charges are slipping through. It adds a fraud-and-duplicate gate before reimbursement without slowing down clean claims.
How it works
- 1A new expense record triggers the flow from Postgres.
- 2A query pulls the employee's recent expenses within a configurable lookback window.
- 3A logic step scores the new claim for exact duplicates and near-cap split patterns.
- 4A branch lets clean claims pass straight through with no action.
- 5For a suspected duplicate or split, the flow marks the claim On-Hold in Postgres.
- 6It opens a Linear task with the matched records and the detection reason.
- 7It alerts the finance review channel in Slack linking the task.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Detect Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Overdue Accrual Escalation Emails to Owners and Managers
On a schedule it flags uncoded spend that has stayed open past the chase deadline and emails each delinquent owner via Gmail.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.