Skip to content

Vendor bank change fraud check

Checks new supplier forms and bank detail change letters before they reach the vendor master. It reads the IBAN, tax ID and registry number from the PDF, runs them against master data and a sanctions list, and routes anything risky to a two person approval where the approver must call the phone number already on file.

OperationsWorks with n8n · Make+1Community example

What it does

  • Takes the request and PDF from a webhook and reads the IBAN, VAT ID and registry number
  • Checks for duplicate vendors, an IBAN already stored for another partner and a mismatched sender domain
  • Flags changes within two days of a payment run and pressure words in the letter
  • Screens the name against the EU sanctions list
  • Writes every action to a signed audit log

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Any bank detail change, which always needs an approver who calls the number on file
  • Two approvers for sanctions hits, foreign sender domains or changes close to a payment run
  • Rejecting a request, with the reason sent to the requester

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 takes the request and PDF from a webhook and reads the IBAN, VAT ID and registry number. Next, it checks for duplicate vendors, an IBAN already stored for another partner and a mismatched sender domain. Then it flags changes within two days of a payment run and pressure words in the letter. After that, it screens the name against the EU sanctions list. Finally, it writes every action to a signed audit log. It works with your automation platform, accounting app and email, 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 any bank detail change, which always needs an approver who calls the number on file, two approvers for sanctions hits, foreign sender domains or changes close to a payment run and rejecting a request, with the reason sent to the requester, and says plainly if a step cannot be undone.

“forces the second look exactly where it matters”
abdallahaneed abdallahaneed on GitHub · Oct 28, 2026
Before you startAutomation platform · Accounting app accessScoped permissionsn8n or Make
Explore required tools and model recommendations

Tools and access

  • n8n

    Handles the automation platform part of this job. Grant create workflows, left inactive until reviewed.

    API required: Yes. Needs an n8n API key from settings. New workflows should stay inactive until you review them.

  • QuickBooks

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

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

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

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.

vendors, customers and their ibans

who receives the signed links

eu consolidated list

2Your prompt

4 of 4 still empty
Fill these in before you run it: [MASTER DATA SOURCE: vendors, customers and their ibans] [PAYMENT RUN CALENDAR] [APPROVERS: who receives the signed links] [SANCTIONS LIST: eu consolidated list] You are the Vendor bank change fraud check agent. Checks new supplier forms and bank detail change letters before they reach the vendor master. It reads the IBAN, tax ID and registry number from the PDF, runs them against master data and a sanctions list, and routes anything risky to a two person approval where the approver must call the phone number already on file. 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: - Takes the request and PDF from a webhook and reads the IBAN, VAT ID and registry number - Checks for duplicate vendors, an IBAN already stored for another partner and a mismatched sender domain - Flags changes within two days of a payment run and pressure words in the letter - Screens the name against the EU sanctions list - Writes every action to a signed audit log What you must never do without a yes from a person: - Any bank detail change, which always needs an approver who calls the number on file - Two approvers for sanctions hits, foreign sender domains or changes close to a payment run - Rejecting a request, with the reason sent to the requester 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: n8n, Make, Claude Code

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 n8n with its own login, not yours. Grant create workflows, left inactive until reviewed.
  2. 2Connect QuickBooks with its own login, not yours. Grant accounting data, no payments.
  3. 3Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do 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.
  6. 6Read 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: any bank detail change, which always needs an approver who calls the number on file, two approvers for sanctions hits, foreign sender domains or changes close to a payment run, rejecting a request, with the reason sent to the requester.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 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
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

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 Vendor bank change fraud check](https://trustcase.dev/badge/vendor-bank-change-fraud-check.svg)](https://trustcase.dev/use-cases/vendor-bank-change-fraud-check)
HTML
<a href="https://trustcase.dev/use-cases/vendor-bank-change-fraud-check"><img src="https://trustcase.dev/badge/vendor-bank-change-fraud-check.svg" alt="Trustcase trust score for Vendor bank change fraud check" height="20"></a>
  • Service shop invoice drafts from job notes

    A tech marks a job done with a plain note and the agent turns it into invoice line items from the shop's own price book. Lines that do not match stay at zero until a person prices them, invoices over a threshold wait for approval, and reminders go out on a fixed schedule without skipping ahead.

  • Invoice inbox

    Reads bills that land in email and gets them ready to pay.

  • Weekly ops report

    Writes the Monday numbers summary so you do not build it by hand.

  • Vendor quote compare

    Lines up quotes from several vendors side by side.

Other workflows that use the same tools

  • Follow up drafter

    Sales. Writes the follow up email after a sales call so nothing goes cold.

  • Pipeline cleanup

    Sales. Finds stale deals and tells you which ones to close or chase.

  • Meeting prep

    Sales. Gives you a short brief on everyone in tomorrow's sales meetings.