INVOICE PROCESSING
Normalize S3-dropped vendor invoices to base currency before Snowflake load
Watches an S3 bucket for new vendor invoice files, converts each invoice total to your reporting currency at the invoice date's FX rate.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice file lands in S3 bucketAWS S3
- ActionRead and parse vendor, currency, amount, dateAWS S3
- ActionFetch FX rate for invoice-date currency pairHTTP webhook
- LogicCompute base-currency total; flag missing rates
- OutputInsert normalized row into Snowflake staging tableSnowflake
What it does
When finance receives multi-currency vendor invoices into an S3 bucket, this workflow reads each file, looks up the FX rate for the invoice date, computes the base-currency amount, and writes a clean normalized record to a Snowflake staging table that your ERP picks up.
When to use it
Use it when vendors email or upload invoices that land in S3 across many currencies (EUR, GBP, JPY, etc.) and your ledger only accepts a single reporting currency. It removes manual FX lookups and keeps every staged row auditable with the rate used.
How it works
- 1An S3 object-created event fires when a new invoice file lands in the watched prefix.
- 2The file is read and parsed to extract vendor, currency, original amount, and invoice date.
- 3An HTTP call fetches the daily FX rate for that currency pair on the invoice date.
- 4A logic step computes base-currency total and flags any invoice missing a rate.
- 5The normalized row, including original amount, rate, and converted total, is inserted into the Snowflake staging table for ledger import.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SnowflakeWarehouses, queries, shares.
- 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.