No Per-User Pricing!

Scale your entire team without your software bill going up. Flat-rate means you pay one price, no matter how many users you add.

Back to Knowledge Base Vendors

The Vendor Approval Gate: No Payee Enters Unverified

A vendor approval gate is the control where new payees wait in a verification queue — reviewed by named approvers, bank details confirmed against independent contact — before the vendor master file accepts them. Nothing enters unverified; nothing gets paid that didn't pass the gate.

Vendor fraud doesn't kick the door in — it fills out a vendor form. Fake suppliers and diverted bank details both enter through the onboarding step, which is exactly where the gate stands. This guide covers the queue, the verification, and the fraud economics. Part of the Vendors cluster; the scheme-by-scheme view: How to Prevent Vendor Fraud.

The onboarding process, step by step

  1. Submission — vendor details and documentation enter the queue: name, category, banking, trade license, tax registration
  2. Review — a named approver (finance, never the requester) examines the submission for completeness and near-duplicates: "Acme Ltd" vs. "Acme Limited" flags here
  3. The callback — bank details confirmed by phone on a number sourced independently — not from the invoice, not from the email signature. Most bank-diversion fraud dies at this step
  4. Approval or rejection — the decision, the reviewer, and the reason recorded on the audit trail
  5. Master file entry — the verified vendor becomes available to requesters, payment data read-only

Why the callback is the gate's heart

Every document in a vendor submission can be forged by a determined fraudster — the trade license, the tax form, the bank letter. What can't be forged is the phone on the other end of an independently sourced number. The callback works because it verifies through a different channel than the one the vendor used to reach you. An email scam can fake paperwork; it can't answer the real company's phone.

The fraud it stops — before a first invoice exists

  • Shell vendors — fake suppliers created by insiders never reach the master file; the gate's approval and callback block them at the entrance
  • Bank-detail diversion — a fraudster posing as a real vendor fails the independent callback
  • Duplicate schemes — near-duplicate entries caught at review, before a second "version" of a real supplier can collect double payments

The gate is also the cheapest place to stop any of this: catching a fake vendor at onboarding costs minutes; catching a fraudulent payment costs the payment. The control layering continues in segregation of duties and bank detail verification.

Frequently Asked Questions

What is a vendor approval gate?

A verification queue in front of the vendor master: new payees wait for named-approver review and independent bank-detail confirmation before they can receive payments.

Who should approve new vendors?

Finance-authorized approvers — never the requester who submitted the vendor, and never the same person who will approve that vendor's invoices.

How do you verify a new vendor's bank details?

Call back on an independently sourced number and confirm the account — the number comes from the vendor's official registration or prior records, never from the documents being verified.

Approvdit's vendor gate puts every new payee in a verification queue with named approvers, deadlines, and the decision recorded — before the master file accepts anything. Book a live demo to see the gate working.