INVOICE PROCESSING
Tolerance-Breach Invoice Escalation to MS Teams
When a matched invoice exceeds its PO by more than the approved tolerance, this routes it through a tiered approval flow in MS Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerInvoice matched with variance in PostgresPostgres
- LogicRead variance amount and percentage
- LogicRoute to buyer or controller by tier
- ActionSend approval card in MS TeamsMicrosoft Teams
- OutputWrite payment decision and audit trailPostgres
What it does
Handles the money side of three-way matching. Once an invoice is matched to its PO, this checks the dollar and percentage overage and applies your approval hierarchy: small variances go to the buyer, large ones go straight to the controller, holding payment until someone signs off.
When to use it
When a flat single-approver process is too loose, and you need overage size to decide who must approve before an invoice can pay.
How it works
- 1An invoice is marked matched-with-variance in Postgres, firing the trigger.
- 2The flow reads the variance amount and percentage from the match record.
- 3A logic step routes by tier: under threshold to buyer approval, over threshold to controller approval.
- 4An adaptive card posts to the assigned approver in MS Teams with line-level variance detail.
- 5On approval the invoice is set to release-for-payment in Postgres; on rejection it is flagged for vendor dispute.
- 6The outcome and approver are written back as an audit trail entry.
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.