Verify the instruction, not the voice

We rebuild how your company verifies, approves and releases payments, then test it with realistic drills.

Part of
Fraud Risk & Ledger Analytics
Runs as
4 stages, from trace payment flows to drill and train
You receive
6 deliverables, listed below
Pricing
Quoted after a scoping call

Attackers aim at the payment instruction

The email looks like the CFO's and arrives while she is traveling. A vendor's receivables contact writes from what appears to be the usual domain to say the bank account has changed. A video call shows the CEO's face and voice asking for an urgent transfer to close an acquisition. Each attack needs one person to act on an instruction without checking it through a channel the attacker does not control.

The AFP's 2026 Payments Fraud and Control Survey found that 76% of organizations experienced attempted or actual payments fraud in 2025, and 74% were affected by business email compromise. FinCEN's November 2024 alert, FIN-2024-Alert004, described criminals using deepfake media to get past identity checks. In the widely reported Arup case that year, roughly $25 million left the company after a video call with fake executives.

Engraving of a featureless mask in profile at an antique telephone whose cord is cut, the cut end in magenta.
Hang up, then call back on a number you already trust.

Every route a payment can change

  • Payment instruction channels

    Every way a request to pay, or to change payment details, reaches finance, including email, portals, phone, chat, the AP inbox and vendor onboarding forms.
  • Callback verification

    A protocol for calling back on a number already on file, made by someone other than the person who received the request.
  • Vendor master hygiene

    Duplicate and dormant vendors, missing tax IDs, bank details with no verification record, and who can edit them.
  • Bank controls

    Dual release, payment limits by user, positive pay, ACH debit blocks and filters, and alerts on new payees, configured in each bank portal.
  • Executive impersonation

    Out-of-band checks for urgent requests from executives, and a written rule that no level of urgency overrides the protocol.
  • Drills

    Simulated email, voice and vendor bank-change attempts against the people who handle payments, with results reviewed together.

Protocols tested on your own staff

DeliverableWhat it isWhen
Payment verification protocolTwo-page procedure for bank changes, new payees and urgent requests, with a decision tree for APWeek 3
Cleaned vendor masterReport of duplicates, dormant records and unverified bank details, with each fix recordedWeek 4
Bank configuration checklistExact settings for dual release, limits, positive pay and alerts in each portal, verified after changesWeek 5
Drill resultsSummary of each simulated attempt, where the protocol held and where it broke, reported by processWeeks 6 to 7
Training session and desk cardNinety-minute session for AP, treasury and executive assistants, plus a one-page card for each deskWeek 7
Annual drill planSchedule and scripts so your team can repeat the drills without usWeek 8

Eight weeks to a tested protocol

  1. Weeks 1 to 2

    Trace payment flows

    We map every channel where payment instructions arrive and every user who can change a payee or release a payment.

  2. Weeks 2 to 5

    Clean and configure

    We analyze the vendor master and payment history, then specify the bank and system settings your team applies.

  3. Weeks 3 to 4

    Write the protocol

    We draft the verification protocol with AP and treasury, and agree the steps no one may skip, including the CEO.

  4. Weeks 6 to 8

    Drill and train

    We run simulated attempts with management's and HR's written approval, train the team on the results and hand over the drill plan.

What the project draws from you

  • A vendor master export with bank details and change history
  • A year of outgoing payment data and the user lists for each bank portal
  • Your AP inbox rules and current procedures for new vendors and bank changes
  • Contacts at your banks who can confirm which controls and settings are available
  • Written approval from management and HR before drills begin, including who may be tested
  • An hour each with AP, treasury and the executive assistants

Is this the right fit?

A good fit

  • Companies that have had a near miss or a successful payment fraud attempt
  • Finance teams where one person can change vendor bank details and release payment
  • Executives with public profiles whose voices and faces are easy to find online
  • Businesses that originate ACH payments and fall under Nacha's 2026 fraud monitoring rules

Not the right fit

  • Recovering money already sent; call your bank and law enforcement at once, then talk to us about prevention
  • Fraud against your own customers, such as card-not-present fraud or takeover of customer accounts

Five rules hold under pressure

A verification protocol only works if it is short enough to remember during a stressful call. Ours rests on five rules.

  1. A change request never verifies itself. A new phone number, a new email address or a letter on letterhead in the same message as a bank change proves nothing.
  2. Call a number you already had. Use the number in the vendor master or the signed contract, never the one in the request.
  3. Someone else makes the call. The person who received the request does not confirm it.
  4. Two people release. Any new payee, any changed bank account and any payment above a set threshold needs a second person to release it in the bank portal.
  5. Urgency means slow down. No executive can waive the protocol, and every executive agrees to that in writing.

The article on five controls that stop vendor bank-change fraud explains each control in more depth.

Executives sign the protocol too

Impersonation attacks borrow an executive's authority. The protocol only holds if executives accept that a payment they request will be called back like anyone else's, and that the AP specialist who delays an urgent wire to verify it has done the job right. We ask each executive to sign the rule, and we brief executive assistants separately, because requests often pass through them first.

The vendor master invites impersonation

A vendor master full of dormant records gives an attacker more names to impersonate and an insider more records to repurpose. We look for duplicates, vendors with no verified bank details, bank accounts shared between vendors or with employees, and changes made shortly before a large payment. Once the cleanup is done, the same tests can run every month through continuous controls monitoring.

Drills show where the protocol bends

Procedures read well on paper. A drill shows whether the AP specialist calls back when a convincing email arrives at 16:50 on the Friday before a holiday weekend. We script email, voice and vendor-portal attempts that resemble real attacks, run them with written approval from management and HR, and review the results with the team without naming individuals. Repeating the drills each year, using the plan we hand over, keeps the protocol in practice rather than in a folder. Our training programs can add payment-fraud drills as a recurring module.

What people ask before hiring us

We already require a callback. Why is that not enough?

Because the callback often goes to the number in the message that requested the change. A callback only works if the number comes from your vendor master or a signed contract, the call is made by someone other than the person who received the request, and the result is recorded before the change is approved.

Can a deepfake really fool our staff?

It can fool anyone who relies on recognizing a face or a voice. The defense does not depend on spotting fakes. It depends on a rule that any payment instruction, however senior or urgent the source, is confirmed through a separate channel the requester did not choose.

Are the drills fair to staff?

They are designed as training, not traps. Management and HR approve the scope in writing, nobody is disciplined for a drill result, and results are reported by process rather than by name. The point is to find where the protocol breaks before an attacker does.

What do Nacha's 2026 rules require of us?

By June 2026 the rules applied to every business that originates ACH entries. Each must have risk-based processes reasonably intended to identify entries suspected of being unauthorized or authorized under false pretenses, such as a payment to an impersonated vendor, and must review them at least once a year. Your bank can confirm how the rules apply to your accounts. We design the protocol with that requirement in mind.

Also in Fraud Risk & Ledger Analytics

Test every transaction for the patterns fraud leaves, assess where your company is exposed, and harden the payment process that outside criminals target most.

  • Full-Ledger Analytics

    A two-to-four-week diagnostic that runs a library of explainable tests and outlier models over every transaction in the period, then reports only the flags an analyst has reviewed.

  • Fraud Risk Assessment

    A four-week diagnostic that identifies how fraud could happen in your business, scores each scheme, maps it to the controls that should stop it, and tests the riskiest ones against your data.

Related work and reading

  • Training Programs

    Half-day sessions to six-week cohorts for managers, staff and boards, built on your policies, your approval limits and anonymized examples from your own ledger.

  • Counterparty & Vendor Due Diligence

    Sourced research on who owns and controls a counterparty, whether it is sanctioned or in adverse media, and whether its finances support the relationship, written up as a red-flag report.

  • Continuous Controls Monitoring

    Automated tests on your ledger, bank and access data every week or month, each exception reviewed by a person and routed to a named owner, run as a subscription after a six-week setup.

Tell us what you are seeing

A first conversation is a scoping call: what worries you, what you need to show, and to whom. You leave it with a view on where to start, whether or not you hire us.

Writehello@financeethics.com
Call(307) 365-5252
Office7124 Commons Dr, Cheyenne, WY 82009
HoursMonday to Friday, 9:00 to 17:00 Mountain Time