INVOICE PROCESSING
Validate FX rates with stale-rate and tolerance guardrails before ledger posting
Receives normalized invoices via webhook, re-verifies each FX rate against a trusted source, blocks invoices using stale or out-of-tolerance rates.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives normalized invoiceHTTP webhook
- ActionFetch trusted reference rate for pair and dateHTTP webhook
- LogicCheck rate freshness and deviation tolerance
- ActionInsert passing invoices into Snowflake stagingSnowflake
- OutputQuarantine failures and post violation to SlackSlack
What it does
This workflow acts as a quality gate between upstream normalization and the ledger. For every incoming normalized invoice it independently re-checks the applied FX rate, rejecting any rate that is older than your freshness window or that deviates beyond a tolerance band from the trusted reference.
When to use it
Use it when multiple upstream systems normalize currency and you need one enforcement point to guarantee no invoice posts with a stale, manually overridden, or anomalous FX rate. It protects ledger integrity at month-end audit.
How it works
- 1A webhook receives a normalized invoice with its currency, amount, applied rate, and rate date.
- 2An HTTP call fetches the trusted reference rate for that currency pair and date.
- 3A logic step checks rate freshness and percentage deviation against configured tolerances.
- 4Invoices that pass are inserted into the Snowflake ledger staging table.
- 5Invoices that fail are quarantined and a violation notice with the offending rate is posted to Slack for review.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 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 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.