US remittance errors when a Philippine payout partner fails

On a qualifying notice of error from the sender, the US remittance rule requires the covered provider to investigate and give the applicable remedy. It should appoint one case owner, secure recipient-level evidence and fund required redress while resolving contractual responsibility with its partner. An offshore agreement cannot remove the sender's statutory rights. (12 CFR §§ 1005.33, 1005.35; 15 USC § 1693l.)

• Check coverage first: the sender's purpose and location, transfer amount and provider's business activity determine whether Subpart B of Regulation E applies. The small-provider safe harbour requires 500 or fewer transfers in both the previous and current calendar years. (12 CFR § 1005.30(e)-(g).)
• A short payout, late delivery and defective sender information can require different remedies. A description such as “local fee” or “beneficiary error” does not establish an exception. (12 CFR § 1005.33(a), (c), (h).)
• The usual notice period is 180 days from disclosed availability. Investigation must be prompt and completed within 90 days after notice; results follow within three business days after completion. (12 CFR § 1005.33(b)-(c).)
• Revise the payout agreement around evidence, refund funding, foreign exchange (FX) losses and agent oversight. Philippine execution and complaint duties must run alongside the US process. (12 CFR §§ 1005.33, 1005.35; MORNBFI §§ 104-M, 301-M, 1003-Q.)

Establish whose transfer and obligation are involved

Subpart B generally covers an electronic transfer requested by a consumer in a State within Regulation E's definition, primarily for personal, family or household purposes, to a recipient abroad. The provider must supply remittances in the normal course of business. An account relationship is unnecessary. Transfers with a principal amount of $15 or less and specified securities or commodities transfers are excluded. (12 CFR § 1005.30(e)-(g).)

Count the provider's transfers across its business when testing the 500-transfer safe harbour. Exceeding that threshold requires the normal-course assessment; an applicable reasonable compliance transition cannot exceed six months. Falling within the safe harbour later does not erase duties for earlier covered transfers. (12 CFR § 1005.30(f)(2).)

The France-to-Morocco sender-contract analysis addresses choosing the regulated principal. Here, that choice must already be clear: identify the provider that accepted the sender's remittance and issued the receipt. Its own error-resolution duties continue when another business performs the payout. Where the partner is its agent under applicable law, the provider also answers for that agent's Subpart B violations. (12 CFR §§ 1005.30(a), 1005.33, 1005.35.)

Classify the shortfall against the disclosed promise

Start with the receipt: the sender's payment, exchange rate, fees, recipient amount and availability date. Compare those entries with the instruction transmitted to the Philippines and the actual payout. Wrong sender amounts, calculation errors and failure to make the disclosed recipient amount available are separate error categories. A partial short payment normally belongs in the amount category. (12 CFR §§ 1005.31(b), 1005.33(a)(1)(i)-(iii); official interpretation 33(a)-5.)

A cash-pickup agent's fee is a covered third-party fee. The narrower non-covered category concerns qualifying incoming account fees charged by the recipient's institution when that institution is not the provider's agent. A non-bank mobile wallet does not qualify as that account merely because it holds value. The relevant shortfall exception also requires the prescribed warning about possible deductions. (12 CFR §§ 1005.30(h), 1005.31(b)(1)(viii), 1005.33(a)(1)(iii)(C); official interpretations 30(h)-2 and -3.)

An exchange-rate movement does not automatically excuse paying fewer pesos than promised. A difference attributable to a permitted estimate may fall outside the error definition, but the provider must establish the applicable conditions under § 1005.32. The former temporary estimate exception expired in July 2020. Ordinary corrective redelivery uses the original disclosed exchange rate, fees and taxes. (12 CFR §§ 1005.32, 1005.33(a)(1)(iii)(A); official interpretation 33(c)-3.)

Require the partner to identify each deduction, its recipient and legal or contractual basis. Then compare the resulting amount with the US disclosure. A downstream charge being lawful locally does not, by itself, establish compliance with the sender-facing promise.

Separate non-delivery from a justified delay

Funds must be available by the disclosed date. Cash available for collection but left uncollected is different from cash the recipient cannot obtain. Payment to a fraudster, a wrong account or a partner that retains the money can establish non-availability, subject to the specific exceptions. (12 CFR § 1005.33(a)(1)(iv); official interpretation 33(a)-5.)

Fraud screening or action required by anti-money-laundering or sanctions law may explain a necessary delay. The exception requires that the provider did not, and could not reasonably, foresee that delay when giving the receipt. Routine screening time belongs in the promised availability date. Obtain the trigger, legal basis, timestamps and reason the investigation was necessary. (12 CFR § 1005.33(a)(1)(iv)(B); official interpretation 33(a)-7.)

Extraordinary circumstances require events outside the provider's control that it could not reasonably anticipate, causing the failure. Ordinary partner liquidity or processing problems do not establish those conditions. The same discipline applies to an asserted sender-fraud exception: the rule concerns fraudulent intent by the sender or someone acting in concert. (12 CFR § 1005.33(a)(1)(iii)(B), (iv)(A)-(C); official interpretations 33(a)-4 and -6.)

If a binding restriction prevents release, establish its precise scope and lawful response. Neither provider should use an unexplained “compliance hold” status to close the investigation.

Treat beneficiary-information errors precisely

Missing or incorrect sender information generally changes the remedy rather than removing the error. If that information caused non-delivery, the provider normally refunds the required funds and its own fee within three business days after reporting the investigation results. It may deduct qualifying third-party fees and taxes actually incurred, subject to the rule's limits, and must identify each deduction and its reason in the investigation-results notice. It cannot retain amounts ultimately refunded to it. (12 CFR § 1005.33(c)(2)(iii); official interpretation 33(c)-12.)

After receiving the results, the sender may request another transfer before the refund is processed. If the provider agrees, that is a new transfer with fresh disclosures and applicable cancellation rights. This differs from ordinary corrective redelivery at the original terms. (Official interpretations 33(c)-3, -11 and -12.)

The wrong-account exception is narrower. It concerns asset accounts held by banks, savings associations, credit unions or equivalent institutions. The term excludes credit cards, prepaid cards and virtual accounts held by Internet or mobile companies outside those institution types. (Official interpretation 33(a)-9.) All five conditions must be met:

1. The provider proves that the sender supplied the wrong account number or recipient-institution identifier.
2. For a wrong institution identifier, the provider used reasonably available means to check its correspondence with the institution name before or when sending the transfer.
3. The required warning about possible loss was given before payment, in the required form.
4. The funds were actually deposited into another customer's account.
5. The provider promptly made reasonable recovery efforts. (12 CFR § 1005.33(a)(1)(iv)(D), (h).)

A rejected account number or an incorrect beneficiary name alone does not satisfy that test. Nor can the provider attribute its own mistranscription or faulty payout instructions to the sender. Preserve the original customer entry, transmitted message, validation record, warning and recovery attempts. (Official interpretations 33(a)-8 and -9, 33(c)-2 and 33(h)-3.)

Run the complaint and remedy clocks correctly

Accept oral or written error notices containing the information the rule requires, to the extent specified. Do not postpone intake until the sender completes a special form or supplies proof. The usual 180-day period starts on the disclosed availability date. A qualifying request for documentation or clarification can extend the notice window until 60 days after the provider sends the information, if later. Notice to the provider's agent counts when that agent receives it. A recipient-only complaint does not itself constitute the sender's notice, but should trigger escalation. (12 CFR § 1005.33(b); official interpretations 33(b)-1 and -5.)

Investigate promptly, determine the outcome within 90 days after notice, and report the result and available remedies within three business days after completing the investigation. The outer limit does not authorise routine delay while the partner debates liability. (12 CFR § 1005.33(c)(1).)

For an ordinary amount error, the sender may choose a refund sufficient to resolve it or delivery of the correct amount without additional cost. For ordinary non-availability, the remedies include refunding the unprovided funds or redelivery without additional cost, together with refunding imposed fees and taxes to the extent tax refunds are legally permitted. A late payout can remove the need to repay principal while leaving the fee-and-tax remedy. (12 CFR § 1005.33(c)(2)(i)-(ii); official interpretations 33(c)-5 and -8.)

Carry out ordinary corrections within one business day, or as soon as reasonably practicable, after receiving the sender's instructions. Keep the separate three-business-day sender-information refund rule distinct. “Business day” uses the provider's public opening for substantially all business functions, not a universal weekday calendar. (12 CFR §§ 1005.30(b), 1005.33(c)(2).)

If the provider finds no error or a different error, send a written explanation addressing the complaint. Notify the sender of the right to request the documents relied upon and supply copies promptly on request. Keep the error file under the applicable retention rules, including any longer regulatory or litigation hold. (12 CFR §§ 1005.33(d), (g), 1005.13(b).)

Apply the Philippine rules to the actual payout model

Identify whether the partner is a bank, remittance and transfer company, subagent or e-money issuer. For non-bank money service businesses, the M Regulations of the Manual of Regulations for Non-Bank Financial Institutions (MORNBFI) govern the relevant registration, tie-up and oversight questions. A remittance and transfer company needs prior Bangko Sentral ng Pilipinas (BSP) registration. A genuine subagent has a different status; an entity actually conducting remittance-agent business cannot avoid registration by also calling itself a subagent. (MORNBFI §§ 101-M(c)-(d), 102-M; BSP Circular No. 1206, series of 2024.)

The registered company's foreign tie-up and subagent arrangements require documented responsibilities and regulatory oversight. Its subagent agreement must address anti-money-laundering, counter-terrorist-financing and consumer-protection duties and BSP access to relevant systems and records. (MORNBFI §§ 103-M, 104-M.)

Philippine overseas-remittance disclosures include fees, the exchange rate and spread, other charges, exact payout amount and currency, and delivery time. If the local leg is a qualifying National Retail Payment System (NRPS) person-to-person electronic fund transfer, the recipient must receive full account credit without charges or deductions. Establish that classification before applying this additional rule. (MORNBFI § 202-N; BSP Circular No. 534, series of 2006; BSP Circular No. 1238, series of 2026, § 2.)

Beneficiary institutions must address identification and missing transfer information through the applicable risk-based procedures. Those procedures determine when to execute, reject or suspend and what follow-up is necessary. A missing field does not automatically prove that the sender caused the failure or lost the US remedy. (MORNBFI §§ 201-M, 923-Q, Fund/Wire transfer(c).)

Run the local consumer complaint process concurrently. The applicable BSP framework requires free assistance and a documented complaint process with appropriate turnaround times. Philippine law also preserves responsibility for agents and accredited service providers within its specified relationships. The US 90-day investigation period is not a universal Philippine deadline. (RA 11765, §§ 8(f), 13; MORNBFI §§ 301-M, 1003-Q.)

Where the Philippine leg is a domestic peso account-to-account electronic fund transfer under NRPS, apply the separate return rules to the originating institution and local sender account. Specified rejected, returned or timed-out instant payments require return within one hour after receipt of the local sender's payment instruction; rejected or returned batch payments use two hours after receipt of the clearing switch operator's settlement report. These automatic-return rules exclude unauthorised and sender-encoded erroneous transactions. Qualifying fee refunds follow the applicable return timetable. Establish the local rail and failure category before applying these clocks to the payout arrangement. (BSP Circular No. 1195, series of 2024, § 2; MORPS §§ 201.2, 1104.2–1104.3(b)-(c).)

Make the payout agreement support the remedy

The UK-to-Kenya settlement analysis also distinguishes settlement arrangements from recipient delivery. For this corridor, require proof of the recipient's credit or cash availability and collection status. A wholesale settlement acknowledgment alone cannot establish who received the remittance.

Revise the operating schedule and payout agreement in five areas:

1. Preserve the instruction and promise. Keep the quote, receipt, FX fixing time, permitted fees, beneficiary data and every transformation between systems. Specify who can approve a changed payout amount.
2. Secure evidence promptly. Require transaction-level payout, rejection, hold and reversal records, with named escalation owners and contractual response times that support the US investigation and any applicable local return deadline. Define lawful, secure access to necessary personal information.
3. Fund consumer redress. Provide a reserve, prefunding or reimbursement mechanism suitable for the model. Required refunds must proceed on the applicable timetable while the providers resolve fault.
4. Allocate the loss. Address unauthorised deductions, FX differences, instruction defects, execution failures and repeat payment. Preserve recovery and indemnity rights without making them conditions of the sender's remedy.
5. Control the network. Flow relevant duties to subagents, reconcile undelivered funds, retain evidence and preserve access after termination. Repeated failures should trigger corrective action and an agreed suspension process.

These are proposed contract controls supporting the legal duties, not prescribed reserve amounts or statutory response hours. Their design follows the investigation and remedy requirements and the Philippine oversight, record-keeping and consumer-protection rules. (12 CFR §§ 1005.33, 1005.35; MORNBFI §§ 104-M, 201-M, 301-M, 924-Q, 1003-Q.)

Where identifying each party's role reveals a wider permissions issue, Payment & E-Money Licensing provides the related licensing context. The immediate sequence remains: confirm coverage, preserve the evidence, classify the error, deliver the required remedy, and then settle the providers' allocation of loss.

Review your payout agreement

To review a cross-border remittance and payout agreement, contact Licentium.