Reference verification
What it does
Before a high-value action completes, the call is checked against the system of record: a payment's payee must match the SAP vendor master. A mismatch is held; a match flows through.
Before the action executes, the payee is checked against the SAP vendor master; a match flows through and a mismatch is held for a person, with the check failing closed to a hold if the reference source is unavailable.
When it applies
Before a high-value action such as a payment completes.
How it works
For a high-value action the gateway reads the customer's system of record and checks the counterparty before the write. A payment's payee account and name must match the SAP vendor master. A clean match proceeds, a mismatch or a changed bank detail is held for review.
In practice
A payment to account DE1234 is checked against the vendor master, which holds DE9999 for that vendor; the mismatch is quarantined for a human, catching a swapped bank account that amount thresholds and rubber-stamp approvals would miss.
What you get
The verification result and the held action are recorded as evidence.
Why it matters
Catches money going to a swapped or unknown account, verified against the business's own truth, not just the agent's word.
Agents can be tricked into paying a plausible-looking but wrong payee. Reference verification checks the action against your system of record, so a payment cannot go to an account that is not in the vendor master, the difference between trusting the agent and trusting the books.