INVOICE PROCESSING
Price-Tolerance Three-Way Match with Tiered Approval Routing
Matches each invoice against its PO and receipt, auto-approves price variances under a small tolerance.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice in staging tableSnowflake
- ActionLoad matching PO and goods receiptSnowflake
- LogicCompute price variance and pick tier
- ActionSend tiered approval to Slack approverSlack
- OutputWrite final status and approver to ledgerSnowflake
What it does
This applies graduated tolerance to price matching. Tiny rounding-level differences clear automatically, mid-size variances go to a line manager, and large overages escalate to a controller, so approval effort scales with financial risk instead of treating every penny the same.
When to use it
Use this when strict exact-match matching creates noise from freight, rounding, or contracted price drift, but you still need real sign-off on meaningful overcharges. It encodes your delegation-of-authority thresholds directly into the flow.
How it works
- 1A new invoice row appears in the Snowflake staging table.
- 2The matching PO and goods receipt are loaded by PO number.
- 3The per-line and total price variance is computed against the PO.
- 4A tiered branch decides routing: within tolerance auto-approves; a mid-tier gap requests manager sign-off; a high-tier gap requests controller sign-off.
- 5Approval requests post as interactive Slack messages to the right approver tier.
- 6The approver's decision writes the final status and approver name back to Snowflake.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
Catch duplicate invoices as they hit your AP inbox
Watches your accounts-payable Gmail inbox for incoming invoice emails, fingerprints each one, and routes likely duplicates to a review label instead of into the approval queue.
Gate invoice approvals on a duplicate cross-check
When an approver clicks Approve in your AP system, a webhook re-validates the invoice against paid history in Postgres and Stripe charges.
Nightly audit that flags duplicate payments already made
Runs every night to scan the last 90 days of Stripe payments against your Postgres invoice ledger.
Block duplicate Stripe payouts before they send
When a new vendor invoice is queued for payment in Stripe, cross-check it against your paid-invoice history in Postgres and halt any payout that matches an already-paid invoice.
Agent that codes Front invoices to GL accounts and drafts a bill
An agent reads each Front vendor invoice, assigns GL account codes per line item using your chart of accounts and past coding history.
Detect duplicate Front invoices and archive originals to S3
Parses each Front vendor invoice, checks it against a history table for duplicates, archives the source PDF to S3 with a normalized key, and alerts AP when a duplicate is caught.
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.