INVOICE PROCESSING
FX-Normalize and Route Large Foreign Invoices for Slack Approval
Receives invoices via webhook, normalizes the amount to base currency at the invoice-date rate.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice posted to webhookHTTP webhook
- ActionFetch invoice-date FX rateHTTP webhook
- LogicBase-currency total over threshold?
- ActionPost to Slack approval channelSlack
- OutputBook normalized invoice to PostgresPostgres
What it does
Incoming invoices hit a webhook, get converted to your base currency using the rate effective on the invoice date, and are then gated by size. Small invoices book automatically; large ones (measured in normalized base currency, so a weak-currency invoice can't sneak past) wait for explicit Slack approval.
When to use it
Use this when approval thresholds must be enforced in a single currency across all vendors, regardless of what currency the invoice arrived in. It stops the loophole where a large foreign-currency bill slips under a native-currency limit.
How it works
- 1An invoice POST to the webhook fires the trigger with structured invoice fields.
- 2An HTTP call fetches the FX rate for the invoice's currency on its invoice date.
- 3A logic step computes the base-currency total and checks it against the approval threshold.
- 4Above threshold, a Slack message with vendor, original amount, rate-date, and normalized total is posted to the approvals channel.
- 5Once approved (or if below threshold), the normalized invoice is inserted into Postgres.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.