Skip to content

Duplicate vendor payment check with a payment hold on approval

Answers back office questions like whether a vendor was paid twice. A code based tool finds the duplicates, high dollar exposure pauses the run for a person, and only an approved result places a payment hold. Every step lands in an audit trail.

OperationsWorks with LangGraph · OpenAI Agents SDK+2Community example
Build your promptSee requirements

What it does

  • Classifies the request into a few allowed routes and sends anything else to a person
  • Runs a code based duplicate invoice check that never changes source data
  • Pauses on high dollar exposure or any access anomaly and saves state so the pause survives a restart
  • Logs each step with a timestamp
  • Uses an idempotency key so a replayed run never acts twice

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Placing a payment hold
  • Opening a security ticket for an access anomaly
  • Any request outside the allowed routes

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it classifies the request into a few allowed routes and sends anything else to a person. Next, it runs a code based duplicate invoice check that never changes source data. Then it pauses on high dollar exposure or any access anomaly and saves state so the pause survives a restart. After that, it logs each step with a timestamp. Finally, it uses an idempotency key so a replayed run never acts twice. It works with your accounting app and database, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before placing a payment hold, opening a security ticket for an access anomaly and any request outside the allowed routes, and says plainly if a step cannot be undone.

“Numbers come from code, not generated text”
Achintya Vamshi Nudurupati achux11 on GitHub · Oct 15, 2026
Before you startAccounting app · Database accessScoped permissionsLangGraph or OpenAI Agents SDK
Explore required tools and model recommendations

Tools and access

  • QuickBooks

    Handles the accounting app part of this job. Grant accounting data, no payments.

    API required: Yes. Needs an Intuit developer app with OAuth.

    Sign up: Intuit Developer

  • Supabase

    Handles the database part of this job. Grant a role limited to one table.

    API required: Yes. Needs a Supabase project and an API key. Give the agent a role limited to one table.

    Sign up: Supabase

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

export or accounting app

2Your prompt

4 of 4 still empty
Fill these in before you run it: [INVOICE SOURCE: export or accounting app] [DOLLAR EXPOSURE LINE THAT NEEDS A PERSON] [WHO REVIEWS PAUSED RUNS] [POLICY DOCUMENTS FOR LOOKUPS] You are the Duplicate vendor payment check with a payment hold on approval agent. Answers back office questions like whether a vendor was paid twice. A code based tool finds the duplicates, high dollar exposure pauses the run for a person, and only an approved result places a payment hold. Every step lands in an audit trail. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Classifies the request into a few allowed routes and sends anything else to a person - Runs a code based duplicate invoice check that never changes source data - Pauses on high dollar exposure or any access anomaly and saves state so the pause survives a restart - Logs each step with a timestamp - Uses an idempotency key so a replayed run never acts twice What you must never do without a yes from a person: - Placing a payment hold - Opening a security ticket for an access anomaly - Any request outside the allowed routes Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: LangGraph, OpenAI Agents SDK, Claude Code, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect QuickBooks with its own login, not yours. Grant accounting data, no payments.
  2. 2Connect Supabase with its own login, not yours. Grant a role limited to one table.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: placing a payment hold, opening a security ticket for an access anomaly, any request outside the allowed routes.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 83.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Duplicate vendor payment check with a payment hold on approval](https://trustcase.dev/badge/duplicate-vendor-payment-check-with-a-payment-hold-on-approval.svg)](https://trustcase.dev/use-cases/duplicate-vendor-payment-check-with-a-payment-hold-on-approval)
HTML
<a href="https://trustcase.dev/use-cases/duplicate-vendor-payment-check-with-a-payment-hold-on-approval"><img src="https://trustcase.dev/badge/duplicate-vendor-payment-check-with-a-payment-hold-on-approval.svg" alt="Trustcase trust score for Duplicate vendor payment check with a payment hold on approval" height="20"></a>

More operations workflows

  • Farm advisory drafts with cited sources and officer sign off

    For an agricultural extension office, it reads the week's rainfall forecast, pest alerts and market prices against each household's crop stage and drafts a plain advisory. Every recommendation cites its bulletin, and the officer signs off before anything goes to a farmer.

  • Purchase request review packs with role based sign offs

    Takes an internal purchase request, classifies it, pulls supplier evidence and policy snippets, and prepares a review pack and draft documents. Logistics, finance, legal and the department head each make their own decision, and the agent cannot approve or pick a supplier.

  • Supplier overpayment claims checked against the contract

    Audits each supplier invoice against the negotiated contract and finds prices above contract, missed volume discounts and duplicate invoices. Plain code works out every amount, the agent drafts a recovery claim with the contract clause attached, and a person approves it before anything goes to the supplier.

  • Invoice exceptions settled against the PO and receiving log

    Takes supplier invoices that do not match their purchase order or what arrived, and works out what is really owed. Plain rules do the math and the agent cites its evidence. Anything that pays more than the records prove waits for a person.

Other workflows that use the same tools

  • Local B2B lead finder

    Sales. Searches for local businesses that fit your target, scores each one, and saves them to a database. Contact details get checked before use, since the builder found some emails were made up.

  • Daily cancellation review

    Support. Each morning it looks at every customer who canceled in the last day and works out why. It checks payments, usage and what they did right before canceling.

  • Chargeback evidence pack

    Support. When a customer files a card dispute, it gathers proof they used what they paid for and builds the evidence pack. A person checks it before anything is submitted.