INVOICE PROCESSING
Suggest GL codes from a vendor's historical coding in Snowflake
For each new invoice line, queries Snowflake for how that vendor and similar line descriptions were coded before.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice received via webhookHTTP webhook
- ActionQuery Snowflake for vendor coding historySnowflake
- ActionReconcile history with current line textOpenAI
- LogicSplit into auto-suggest vs needs-review
- OutputWrite recommended codes to AirtableAirtable
What it does
Gives each invoice line a GL-code suggestion grounded in your own ledger history. Rather than guessing from text alone, it asks Snowflake how the same vendor and similar descriptions were coded in prior periods and recommends the dominant account.
When to use it
Use it when you have years of coded invoice history in a warehouse and want suggestions that match how your team actually codes, not generic guesses. Ideal for high-volume recurring vendors.
How it works
- 1A new invoice record (via webhook from your intake system) triggers the run.
- 2For each line, a Snowflake query pulls historical GL codings for the same vendor and fuzzy-matched line descriptions.
- 3An OpenAI step reconciles the history with the current line text, picking the most consistent account and explaining the choice.
- 4A logic step splits lines into auto-suggest (clear historical match) and needs-review (new or ambiguous).
- 5The recommended codes and rationale are written back to Airtable for the AP team to confirm.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect AirtableBases, tables, views, automations.
- 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
Dollar-Threshold Match Variance Escalation Chain
Routes three-way match variances up an approval ladder by dollar size — small ones to the line manager, large ones to the controller.
Front vendor invoice to Airtable approval packet with line-item parse
Watches a Front inbox for vendor invoice emails, extracts header and line-item data from the body and PDF attachment, and writes a structured.
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.
Three-Way Match Exception Router by Variance Type
When a new invoice fails three-way match against its PO and receiving record, this workflow classifies the mismatch (price, quantity, or missing receipt) and routes each variance…
Route parsed Front invoices to the right Slack approver by amount
Parses an incoming Front vendor invoice and posts an interactive Slack approval card to the approver whose spending threshold matches the invoice total.
Three-way match Front invoices against purchase orders in Postgres
Parses a Front vendor invoice and runs a three-way match against the matching purchase order and receipt records in Postgres, posting pass or exception results to Slack.
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.