INVOICE PROCESSING
Capture Invoice-Date FX Rate from Dropped PDFs into Snowflake
Triggers when an invoice PDF is added to a Google Drive folder, reads vendor, currency, amount, and date from the document, locks in the FX rate for that date.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice PDF added to Drive folderGoogle Drive
- ActionExtract fields from PDFOpenAI
- ActionFetch FX rate for invoice dateHTTP webhook
- LogicCompute base amount, stamp rate-date
- OutputWrite FX-stamped row to SnowflakeSnowflake
What it does
Drop a vendor PDF into a watched Drive folder and it becomes a fully FX-stamped row in your warehouse. The flow reads the document, identifies the currency and invoice date, captures the matching historical rate, and stores the original amount, rate, rate-date, and base-currency equivalent in Snowflake.
When to use it
Use it when invoices arrive as PDFs (scanned or vendor-issued) rather than structured data, and your analytics team needs them normalized in the warehouse without manual data entry or after-the-fact rate lookups.
How it works
- 1A new file in the monitored Google Drive folder fires the trigger.
- 2An OpenAI document-extraction step reads vendor, invoice number, amount, currency, and invoice date from the PDF.
- 3An HTTP call fetches the FX rate for that currency as of the invoice date.
- 4A logic step computes the base-currency amount and stamps the rate-date onto the record.
- 5The FX-normalized row is written to Snowflake for cross-border AP reporting and analytics.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect SnowflakeWarehouses, queries, shares.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Invoice Processing workflows
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.
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.
AI agent that investigates suspected duplicate invoices
When a new invoice can't be cleared by exact-match rules, an AI agent reviews paid history for near-duplicates (split bills, renamed vendors, rounding) and recommends pay, hold…
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.
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.
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.
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.