Key takeaways
- A phantom vendor is a supplier record with no real business behind it, set up so ordinary payments go somewhere they should not.
- The control point is vendor onboarding, not payment: once the record exists, every payment afterwards looks routine.
- Check three things before a new supplier is approved: a verifiable registration, a contactable address and phone number found independently, and bank details confirmed by callback.
- Watch for suppliers whose invoices are always round numbers, always just under an approval limit, or lack normal detail.
- Review the vendor master list twice a year and deactivate anything dormant — old records are the easiest to reuse.
- The person who creates or edits vendor records should not be able to approve payments to them.
Most purchasing fraud in small businesses is not clever. It works because the accounting system cannot tell the difference between a supplier that exists and one that does not — both are simply rows in the vendor list, and both produce payments that pass through the normal process without anything looking wrong.
A phantom vendor is exactly that: a supplier record with no real business behind it. The invoices are legitimate-looking, the approvals are genuine, and the money goes out the front door with full paperwork. The whole defence sits at one point — the moment the vendor record is created.
How it works
The mechanism has three variants, in rough order of how often they turn up in small businesses.
The invented supplier. A new vendor is created with a plausible name, an address that is really a house, and a personal bank account. Invoices are raised for services that are hard to inspect afterwards — consulting, cleaning, maintenance, delivery charges — at amounts small enough to pass without a second look.
The compromised real supplier. The company is real and the trading relationship is genuine, but the bank details on the record have been changed. Payments for real deliveries go to the wrong account. This one is usually external, and it is the reason bank-detail changes deserve callback verification, as covered in the procure-to-pay SOP.
The revived dormant record. An old supplier you stopped using still sits in the list, approved, with a payment history. Activity on it attracts less scrutiny than a new name would, because the record itself looks established.
The invoice matches the order because the same person created both. The approval is real because the approver has no reason to doubt a supplier already in the system. The payment is ordinary. This is why onboarding is the control point — everything after it is downstream of a decision already made.
The three-point check at onboarding
Before a new supplier can be paid, confirm three things and record who confirmed each:
| Check | What good looks like | Common failure |
|---|---|---|
| Legal identity | A registration or tax number you verified against a public register | A number supplied on the invoice, never checked |
| Contactability | Address and phone found independently, and someone has actually called it | Details taken only from the supplier's own letterhead |
| Bank account | Confirmed by calling a number you already held on file | Confirmed using the number in the request itself |
The third row is the one that fails most often, and the failure is always the same: the verification call goes to a number provided by whoever wants the change. Use a number from an earlier contract, an old invoice, or the supplier's published contact details.
For a genuinely small supplier — a local tradesperson, a market supplier — a full registration check may not be realistic. Then compensate: keep those suppliers below a stated value limit, pay them from petty cash or a separate low-value route, and review the list of them quarterly.
Warning signs in the data
Once suppliers are in the system, four patterns are worth a look. None is proof; each is a reason to check the master record.
- Round numbers, repeatedly. Real invoices have odd totals — tax, freight, part quantities. A supplier whose invoices are always exact round amounts is billing from a template, not from a transaction.
- Amounts consistently just under an approval limit. Someone knows the threshold. That is worth understanding regardless of who it is.
- Invoices with no line detail. "Services rendered" with no quantity, rate, or period, month after month.
- Address or bank account shared with an employee record. The simplest query in this list and the most decisive one.
The vendor list of a long-running small business is full of duplicates: the same supplier entered three times with slight spelling differences, and a dozen records last used years ago. Almost always this is administrative mess, not fraud — but the mess is exactly the cover a phantom record needs, and cleaning it is what makes an unusual entry visible.
Keeping the list clean
Twice a year, review the vendor master list:
- Deactivate anything with no activity for a year. Deactivating preserves the history; deleting does not.
- Merge obvious duplicates so payment history is consolidated and comparable.
- Check that bank details on frequently-paid records still match your verification notes.
- Cross-check supplier addresses and bank accounts against employee records.
Supplier records in Reyuko sit alongside purchases and payments in the same ledger, so reviewing what each supplier has been paid — and when they were last used — is a report rather than an export-and-compare exercise. Reyuko also blocks a hard delete of master data that transactions still reference, and offers to mark the record inactive instead, so cleaning your vendor list cannot quietly break the history behind old payments.
Access to the supplier list and to payments is set separately through the preset roles, so the person who maintains vendor records need not be the person who releases money to them. Reyuko does not itself verify a supplier's registration or bank account — the three-point check above is a human routine, and no accounting package can do it for you.
Close the phantom vendor route
- Name who may create or edit a supplier record — someone who cannot approve payments.
- Require the three-point check before the first payment, with each check initialled and dated.
- Treat every later bank-detail change as a new verification, by callback to a number you already had.
- Run the four warning-sign queries once a quarter.
- Review and deactivate dormant supplier records twice a year.
Phantom vendors take money on the way out. The next lesson covers the patterns that take it on the way in — skimming, lapping and inventory leakage.
Reyuko