To Whom Would You Forward a Request for an Advance Decision When Faced With a Questionable Payment

You forward the request to the person who holds budget authority for that expense and owns the financial-controls process, typically the department head who approved the vendor relationship plus a finance or compliance reviewer, and you document the question before the payment runs. In practice that means escalating one level above whoever initiated the payment if that initiator cannot independently verify it. The exact recipient depends on three variables: who requested the payment, whether a contract or purchase order exists, and whether fraud is suspected. Get the routing wrong and you either stall an urgent wire or bury a control failure.

The phrase "advance decision" is doing quiet work here. It usually means a decision made before funds leave, not a decision about an advance payment, though the two overlap whenever a vendor demands money up front. The question is fundamentally about sequencing authority: who decides, and against what evidence, before the transaction becomes irreversible.

What the escalation mechanism actually does

Payment controls exist because disbursement is the moment money becomes unrecoverable. A request for an advance decision inserts a checkpoint before that point. The mechanism has three parts: evidence collection, authority matching, and documented disposition.

Evidence collection means assembling what the payment claims to be and what the records say it is. A vendor invoice references a purchase order, a goods-receipt record, or a contract clause. A questionable payment typically fails one of those matches. Maybe the vendor is not in the approved master file, maybe the invoice number duplicates a prior one, or maybe the bank details changed since the last payment.

Authority matching means routing to the person whose approval limit covers the amount. Most organizations set tiered limits, and a common structure puts routine payments below a low threshold with the initiating manager and escalates above it. Approval limits vary widely by organization size, so treat any specific dollar figure as illustrative rather than universal.

Documented disposition means the decision is recorded, not verbal. A controller who later faces an audit needs to show who approved a questionable payment and on what basis. Verbal clearance collapses under scrutiny.

The counterintuitive detail: the person who asked for the payment is usually the worst person to decide whether it is legitimate. They have an interest in the transaction proceeding, and their belief that the vendor is real is precisely what needs independent testing.

How much money and time is at stake

Fraud losses from payment manipulation are not marginal. The Association of Certified Fraud Examiners has repeatedly found that billing schemes and payment tampering are among the most common occupational fraud categories, and the median loss for billing fraud runs well into six figures in US dollars across surveyed cases. The exact figure shifts by year and sample, so the durable point is the order of magnitude.

Recovery is the harder number. Once a wire leaves and lands in a fraudulent account, recovery within 24 hours is possible in some cases; after 72 hours it becomes unlikely, and after a week it is effectively gone in most cross-border scenarios. The Federal Bureau of Investigation has documented that business email compromise losses run into the billions annually in the United States.

The time cost of escalation is real too. A legitimate but poorly documented payment might sit for two to five business days while the reviewer reconstructs the paper trail. That delay is the price of the control, and it is usually cheaper than the loss.

Plainly: the escalation costs hours, and the skipped escalation can cost six figures.

Where the standard routing breaks down

Edge cases matter because they determine whether you escalate to a person, a committee, or an external body.

A payment to a government official overseas routes differently from a domestic vendor payment. The Foreign Corrupt Practices Act and equivalent statutes make facilitation payments a legal question, not just an accounting one, so the request goes to legal counsel and the compliance function, not just finance.

A payment where the requester is also the approver, a common failure in small organizations, requires escalation to a board member or an external accountant. The control that normally catches problems is the one that is absent.

A payment that is questionable because the underlying contract was never signed goes to whoever holds contract authority, which is often procurement rather than finance.

A payment during a merger or an ownership transition may need dual sign-off from both legacy and new authorities.

A payment where fraud is already suspected should not be discussed with the suspected party at all. It goes to internal audit or an external forensic investigator, and the routine routing is bypassed deliberately.

The misconceptions that cause failures

The most common misconception is that forwarding the question to your own manager discharges your responsibility. It does not. Forwarding is escalation, not delegation, and you remain the person who raised it. If the payment proceeds and the loss materializes, "I forwarded it" is not a control.

The second is that a vendor's insistence on speed is evidence of legitimacy. Urgency is a manipulation tactic, and treating a same-day demand as a reason to skip review is exactly the behavior the control exists to resist.

The third is that a valid-looking invoice proves a valid payment. Invoice templates are trivially spoofed, and a document that reproduces a known vendor's letterhead tells you nothing about whether the bank account on it belongs to that vendor.

The fourth is that advance decisions are only about large amounts. Low-value fraudulent payments are common precisely because they fly under approval thresholds. A pattern of small payments to a new vendor is a red flag even when each one clears on its own.

Comparison of escalation routes

The table below summarizes where different payment questions should go, with the caveat that your organization's delegation-of-authority document overrides any general pattern.

Timeline of an advance-decision escalation

The sequence below reflects a typical mid-size organization. Timelines vary with complexity, and the point is the order, not the exact days.

The reconciliation point deserves emphasis. Organizations commonly set a low-value threshold below which no escalation is required. That threshold and the fraud-risk threshold are different numbers serving different purposes. A payment can be below the escalation threshold and still be high risk. When the two conflict, risk wins, and the reviewer should escalate anyway.

Practical actions and thresholds

Concrete steps, in order, when you face a questionable payment.

First, stop the payment if it has not run. A hold costs nothing; a recall costs days and often fails.

Second, write down what is questionable in one sentence. If you cannot state the concern precisely, you cannot route it correctly.

Third, identify the requester and check whether they can independently verify the payment. If they cannot, escalate one level above them.

Fourth, match the amount to the delegation-of-authority schedule and route to the approver whose limit covers it.

Fifth, for any bank-detail change, verify by callback to a phone number you already have on file, never a number supplied in the request itself. This single step blocks most impersonation fraud.

Sixth, document the decision, the person who made it, and the evidence reviewed. Store it with the payment record.

Red-flag warnings to escalate immediately rather than resolve locally:

A demand for same-day or immediate wire transfer, especially with a stated penalty for delay. Bank account details that differ from prior payments, particularly a change arriving by email. A vendor name that closely resembles an existing approved vendor but is not identical. Pressure to bypass normal approval, framed as an exception or a favor. A requester who is also the approver, or who resists documentation. Communication that moves from a corporate channel to a personal email or messaging account.

What the escalation cannot do

An advance decision is a control, not a guarantee. It reduces the probability of loss and creates a record, but a determined fraudster who compromises both the vendor and the approver defeats it. The control also depends on the approver actually reviewing rather than rubber-stamping, and approval fatigue is a documented failure mode where high volumes of routine requests train reviewers to sign without reading.

The mechanism also cannot resolve legal questions. Whether a payment is lawful, whether it constitutes a bribe, and whether it triggers reporting obligations are questions for counsel. Finance can hold the payment; only legal can answer the legal question.

Finally, escalation cannot fix a broken delegation schedule. If the organization has never defined who approves what above a certain amount, the reviewer is guessing. The first practical action in that case is to get the schedule in writing before the next questionable payment arrives.

This article is general educational information about payment controls and escalation routing, not legal, financial, or compliance advice. It does not create an approval authority or replace your organization's delegation-of-authority policy, and it promises no outcome in any specific transaction. Consult a qualified professional, such as legal counsel, a certified public accountant, or your organization's compliance officer, for advice on a specific payment or suspected fraud; if you believe a fraud is in progress, contact your local law enforcement or financial-crimes reporting authority immediately.