INVOICE PROCESSING
Open a Linear Ticket When a Vendor's Cumulative Creep Crosses a Cap
Runs weekly, tracks each recurring vendor's cumulative price increase since a fixed contract anchor date.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the creep check
- ActionPull vendor invoices since contract anchor datePostgres
- LogicCompute cumulative creep and compare to renegotiation cap
- OutputOpen Linear ticket for vendors over the capLinear
What it does
Small per-invoice increases are easy to wave through, but they compound. This workflow watches the cumulative drift since each vendor's contract anchor date rather than just the latest jump. Every week it recomputes how far above baseline each vendor now sits in total. When a vendor's accumulated creep crosses your cap, it opens a Linear ticket assigned to the contract owner so the increase gets formally reviewed and renegotiated rather than quietly normalized.
When to use it
Use this when individual increases stay under per-invoice alert thresholds but add up over months. Best for teams managing renewals and vendor contracts who want action items, not just notifications.
How it works
- 1A weekly schedule triggers the run.
- 2The workflow pulls each recurring vendor's invoices since their anchor date from Postgres.
- 3It computes cumulative drift from the anchor baseline to the latest invoice.
- 4A logic step compares cumulative creep against the renegotiation cap.
- 5Vendors under the cap are skipped to avoid ticket spam.
- 6For vendors over the cap with no open ticket, a Linear issue is created with the creep history and contract owner as assignee.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.