INVOICE PROCESSING
Discount Capture Approval Router (Postgres + MS Teams)
When a tracked invoice's discount window is closing, routes it for fast approval in MS Teams with an approve/skip decision.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule every few hours
- ActionQuery invoices entering decision windowPostgres
- LogicRoute by amount: auto-approve vs human sign-off
- ActionRequest approve/skip decision via MS Teams cardMicrosoft Teams
- ActionWrite decision and savings back to PostgresPostgres
- OutputUpdated tracker with approval outcome
What it does
This workflow watches the Postgres discount tracker for invoices whose early-payment window opens within its actionable range and routes each one to the right approver in MS Teams. The approver gets an adaptive card showing vendor, amount, discount rate, savings, and deadline, and chooses to capture or skip. The decision and projected savings are written back to Postgres for reporting.
When to use it
Use it when capturing a discount requires sign-off above a dollar threshold and you need an auditable yes/no decision before AP releases payment, without leaving the chat tool the team already lives in.
How it works
- 1A schedule fires every few hours.
- 2A Postgres query selects tracked invoices entering their decision window with no recorded decision yet.
- 3A logic step routes each by amount: small invoices auto-approve, larger ones need a human approver.
- 4An MS Teams adaptive card requests the capture/skip decision for routed invoices.
- 5The decision and projected savings are written back to Postgres.
- 6Output: an updated tracker reflecting each approval outcome.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.