The Hidden Interval: How the Beneficiary Leg Works
This chapter follows the beneficiary leg of a cross-border payment: the process that begins when the receiving bank gets the payment and ends when the end-customer can use the funds. The practical question is what changes in the payment’s state during that interval, and why a complete, familiar transaction may be credited quickly while another remains pending. The answer lies in the interaction of information, local rules, operating workflow, and the bank’s position in a longer cross-border chain.
The word “received” describes an event, not a final outcome. Once the beneficiary bank has the payment, it can begin deciding whether the transaction is sufficiently identified, permitted, and documented to be credited. Until that decision is complete, the payment may be visible in the bank’s systems without being part of the customer’s usable balance. A helpful way to understand the process is to follow the state transitions rather than imagine a single switch from “sent” to “delivered.”
From receipt to a local credit decision
State 1: The payment enters the beneficiary bank’s process
The beneficiary leg starts when the beneficiary bank receives the payment, either directly from the originating bank or through one or more intermediaries or a payment-market infrastructure. The transaction is no longer waiting for the international message to reach that institution. It has entered the receiving bank’s own workflow, where the incoming payment has to be connected to an account and assessed under the rules that apply in that jurisdiction.
That first transition is easy to overlook because a payment network can provide tracking across several stages. Swift’s Global Payments Innovation system, for example, uses a Unique End-to-End Transaction Reference to capture timestamps through the payment’s life. A timestamp showing receipt at the beneficiary bank is valuable: it separates time spent reaching the bank from time spent after the bank has the payment. But the timestamp does not mean that the funds have passed every local condition for credit. It identifies the beginning of a new state.
At this point, some information persists. The payment instruction, its transaction reference, the beneficiary details, the purpose information, and supporting material supplied through the chain can be available for review. What has not yet happened is the state change that matters to the customer: the bank has not necessarily credited the end-customer’s account. The receiving institution must decide whether the information is sufficient and what action its rules require.
State 2: The bank establishes what the payment represents
For inflows, the IMF working paper describes several kinds of checks that may be required before disbursement. The bank may verify information about the beneficiary, including the type of beneficiary, the activity associated with them, and the accuracy of a tax identity number. It may examine the payment’s purpose, whether that purpose is expressed through a code or in text. It may also request or review documents such as a contract, invoice, or export bill.
These are not interchangeable fields on a generic checklist. Each answers a different question. Beneficiary information addresses who is receiving the money and, in some settings, what kind of activity they conduct. A purpose code or written explanation addresses why the funds are being transferred. A contract or invoice can provide evidence that the stated purpose corresponds to an underlying transaction. If one piece is missing or inconsistent with another, the bank may not be able to complete the decision merely by reading the payment message again.
Some jurisdictions add further conditions. They may impose limits on the amount that can be received, restrict foreign transfers to particular account types, or require the beneficiary bank to report transfers to a local regulator. These requirements mean that the bank is not simply matching a name to an account. It is connecting an incoming payment to a local legal and administrative context. The exact combination varies by jurisdiction and payment type; the process described here is a model of the kinds of dependencies that can exist, not a universal sequence used by every bank.
Capital-flow management is one source of these dependencies. It is not the only one. Anti-money-laundering and countering-the-financing-of-terrorism procedures, sanctions screening, tax reporting, fraud controls, and ordinary internal bank procedures can overlap with capital-control checks. A payment may therefore enter a review process for more than one reason, or a single missing field may matter to several control functions. Treating all of these as one undifferentiated “regulatory hold” hides the decision the bank is actually trying to make.
State 3: Complete information and an exception take different paths
The next transition depends on whether the information needed for the decision is available and intelligible. When the payment is familiar, the customer relationship is established, and the information is complete and accurate, the bank may be able to validate it with little manual intervention. The IMF paper says that such processing can take minutes. In that path, the incoming transaction moves through checks, the bank records the credit, and the end-customer can use the funds.
An exception path begins when the bank cannot complete one of those steps. The purpose may be unclear. The tax identity number or beneficiary information may not match what the bank expects. A contract, invoice, or export bill may be absent. The account may not be an eligible type, or the amount may require additional handling. The bank may need to contact the customer, obtain information from another institution, or send the item to a reviewer with authority to resolve the exception. The payment remains pending while that dependency is open.
The important state change in this path is not that the money has vanished. It is that the customer’s access remains conditional. A request for information can move the payment toward resolution, but it also creates another transition: the customer or an intermediary must provide material in a form the bank can evaluate. If the response is incomplete, the case can return to review. If it is adequate, the bank can complete its decision and credit the account. The same payment can therefore move through several review states even though its international transmission ended earlier.
The bank’s process may not be a neat line. Checks can occur in a different order, run partly in parallel, or be repeated when new information changes the assessment. The state model is useful because it preserves the distinction between the information already received and the decision still outstanding. It also explains why a faster message does not necessarily shorten the full wait: it may bring the payment to the front of the local queue sooner without removing the work required at that queue.
The sequence is a teaching model, not a claim that every jurisdiction inserts the same authority interaction or follows the same order. Its purpose is to show the ownership of the post-arrival decision. The beneficiary bank receives the transaction, applies the checks required in its environment, may communicate with the customer or a local authority, and ultimately controls the transition to customer credit. The international route can be functioning normally while this local transition is still unresolved.
Why the same process takes minutes or days
Data completeness is a timing variable
A payment carries more than an amount and an account number. At the beneficiary leg, the usefulness of its data depends on whether the receiving bank can interpret the beneficiary, purpose, account, and supporting evidence in the way its own controls require. If the relevant information arrives in a compatible, complete form, the bank has fewer reasons to stop and ask for clarification. If it arrives in an unfamiliar format, uses an ambiguous purpose description, or omits a document, the bank’s next action may depend on a person or institution outside the immediate payment path.
This is why “automation” needs a careful definition. A system can automate the comparison of fields, route a familiar transaction, or flag an exception. It cannot make an incomplete document complete, establish an account’s legal eligibility without a rule to evaluate, or decide that a jurisdiction’s reporting requirement no longer applies. Automation can shorten avoidable work around a control; it does not abolish the control’s underlying decision. When systems cannot exchange the same data reliably, a bank may repeat a question that another institution has already answered, not because the question is substantively new but because the answer is not usable at the next interface.
The difference becomes visible in ordinary situations. A recurring business payment may contain a recognizable counterparty, a consistent purpose, and documentation that the bank has seen before. A one-off transfer may involve a new customer, an unfamiliar description, or a payment whose supporting material has not travelled with the instruction. These examples are illustrative rather than documented cases from the IMF study. They show how familiarity and completeness can alter the path without changing the fact that both payments have reached the same beneficiary bank.
Time zones and operating windows can turn a short check into a long wait
A review does not happen in an abstract 24-hour space. Banks and market infrastructures may operate according to local hours, holidays, or batch schedules. A payment that arrives after a cut-off can wait for the next processing window even when the substantive check is brief. A question sent to a customer or another institution can wait across a time-zone difference. Currency conversion may introduce another institutional handoff around the payment, with its own operating rules and availability.
These timing factors can compound an information problem. Suppose a payment requires one missing document. If the customer can provide it immediately and the receiving bank is operating with staff and systems available, the exception may be resolved quickly. If the request is generated after local hours, passes through a different time zone, or enters a batch queue, the elapsed time includes the waiting period before anyone can act. A record of the final review may make the decision look short while the customer’s total wait is long.
The wider correspondent chain adds another layer. Cross-border payments often involve multiple institutions, and the BIS review describes two to four intermediaries as common in a typical transaction, with more in complex cases. Each intermediary may use different technologies, account relationships, compliance procedures, or operating schedules. Those institutions can be essential to reaching a jurisdiction where the originating bank has no physical presence. They can also create more points for reconciliation, currency conversion, and repeated screening. Once the payment arrives at the beneficiary bank, the last-mile queue is local, but its inputs may have been shaped by the whole chain.
This is also why a beneficiary-leg measurement should not be read as a list of individual causes. An elapsed-time statistic can show that time accumulated after receipt, but it does not tell us whether the decisive event was a document request, a reporting rule, a batch window, an internal exception, or the interaction of several of them. The IMF study’s timestamp-based measure locates the interval precisely enough to study it; it does not open every bank’s workflow and label each waiting period.
Necessary control and avoidable friction are different problems
A fair diagnosis has to hold two ideas together. First, the receiving bank may be required to establish facts about a payment before crediting it. Removing that work indiscriminately could weaken financial integrity, violate local law, or undermine a country’s macroeconomic policy. Second, a necessary check can still be implemented badly. Repeated data entry, incompatible identifiers, unclear purpose information, manual review of routine cases, and narrow operating windows can add delay without adding equivalent protection.
The distinction is practical. If a payment is held because the bank must verify a beneficiary’s eligibility and the required evidence is absent, the remedy may involve obtaining better information or clarifying the rule—not simply demanding that the bank credit the account immediately. If the same information has already been collected and is reliable but cannot be transferred into the receiving bank’s system, the problem is more likely one of interoperability or workflow. If a routine case waits because the relevant function operates only in a limited window, the problem concerns operating design. Different causes call for different responses.
The categories can coexist. A payment may contain complete information but still be subject to sanctions screening. A compliant control may be slowed by a poor data interface. A bank may need to report a transfer while also checking the account type. The goal is not to draw a clean line between “regulation” and “technology” when the process uses both. It is to ask which decision is pending, what evidence that decision needs, who owns the next transition, and whether the surrounding system makes the transition needlessly repetitive.
That question matters most for retail transfers and remittances. A large institutional payment between familiar counterparties may justify dedicated relationships and receive experienced handling. A smaller transfer may be more occasional, may involve a user with limited access to formal financial services, or may enter the system through cash-in and cash-out steps. A delay at the beneficiary leg then becomes part of a broader access problem. The recipient may not have the information, time, or institutional contact needed to resolve an exception as easily as a corporate treasury department can.
The beneficiary leg is therefore best understood as a controlled state transition, not as an empty space after the network has done its job. Receipt supplies the bank with a transaction to assess. Local rules determine what must be established. Data completeness, familiarity, automation, operating windows, time zones, currency conversion, and intermediary handoffs influence how quickly the assessment can finish. A customer receives usable funds only when those dependencies line up and the bank records the final credit.
This process model establishes a plausible mechanism for post-arrival delay. It does not yet establish how strongly any one factor is associated with longer elapsed time across countries. That is the next evidentiary question: what can a country-level study show about the relationship between financial-account restrictions and the time between beneficiary-bank receipt and customer credit?