INVOICE PROCESSING
Inbound Invoice Terms Parser to Discount Tracker (Outlook + Postgres)
Reads new vendor invoice emails in Outlook, extracts the early-payment discount terms and due date with AI.
How it runs
The automated pipeline, trigger to output.
- TriggerNew invoice email in OutlookOutlook
- ActionExtract terms and dates with OpenAIOpenAI
- LogicValidate fields and compute discount-expiry date
- ActionUpsert record into Postgres discount_trackerPostgres
- OutputStructured tracked invoice row
What it does
When a vendor invoice lands in a monitored Outlook mailbox, this workflow extracts the invoice number, amount, issue date, and any early-payment discount terms from the email and its attachment using an AI extraction step. It computes the exact date the discount expires and inserts a structured record into a Postgres tracking table that downstream workflows and dashboards read from.
When to use it
Use it as the ingestion front-end for a discount-capture program when invoices arrive as PDFs by email with inconsistent formatting. It turns messy inbound mail into clean, queryable rows so you never lose track of a discount window again.
How it works
- 1A new-email trigger fires on the AP Outlook inbox.
- 2An OpenAI extraction step parses vendor, invoice number, amount, issue date, and discount terms from the body and attachment.
- 3A logic step validates the fields and computes the discount-expiry date from issue date plus the discount-day count.
- 4An action inserts (or upserts on invoice number) the record into the Postgres `discount_tracker` table.
- 5Output: the new row, ready for the expiry-scanner workflow to monitor.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect OpenAIModels, embeddings, files.
- 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.