WorkflowPayments Operations

Remittance Transfer Rule Compliance

The remittance transfer rule, worked claim by claim: what the receipt promised beside what was delivered, every exception tested, every refund approved by a second person

Transfer errors resolved in days, with every promise checked against delivery.

See one case, screen by screen ↓
demo9elementsof the sample transfer compared, promised against delivered, each with its source: 3 differences, 2 errors
demo4daysfrom the member’s call to an approved refund on the sample claim: day 4 of the rule’s 90
demo214transferschecked for every disclosure element before release on the sample morning, 3 held and fixed
target100%of prepayment disclosures and receipts checked for every required element before the transfer leaves
In short

What is Remittance Transfer Rule Compliance?

Remittance transfer rule compliance is how a bank or credit union handles consumer international transfer disclosures, cancellations and errors under Reg E. The remittance transfer rule is Subpart B of Regulation E, 12 CFR 1005.30–1005.36. It requires a bank or credit union that sends consumer international transfers to give a prepayment disclosure and a receipt, honor cancellations made within 30 minutes, and investigate and fix errors on a 90-day clock. Remittance Transfer Rule Compliance puts what the receipt promised beside what was delivered; its agents trace the transfer, test every exception and draft the remedy for a specialist to sign and a supervisor to approve.

AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →

Updated

The problem

Why the remittance transfer rule turns one late transfer into weeks of work

Under the remittance transfer rule, a member’s receipt is a promise: an exact amount in pesos, an exchange rate, the fees and the date the money will be there. Subpart B of Regulation E makes the credit union answer for it, although a remittance provider, a correspondent and a payout bank in another country move the money. When a member says it arrived short or late, the credit union has 90 days to find out what happened, three business days to tell the member and one business day to put it right, and it may not keep the fee on a transfer that was late.

Today a Member Payments Specialist logs into the provider portal, opens a trace, waits for the correspondent’s answer by email and compares the payout confirmation with the receipt in a spreadsheet. The exceptions the rule allows, an estimate, extraordinary circumstances, a fraud, BSA or OFAC hold, the member’s wrong account number, are argued from memory, and fee refunds on late transfers are the most common miss. The letter goes out in English to a member who complained in Spanish, and a changed receipt template can drop a required element from every receipt for a month before the compliance sample finds it.

demo63noticesof error in one month at the sample credit union, each on a 90-day legal clock
typical$1.6Mpenaltypaid by one provider in the CFPB’s 2020 remittance actions, over error resolution, cancellations and refunds
typical$300,000penaltypaid by another for not refunding fees when the money was not available by the disclosed date
Where an error claim’s days goestimated
By hand19 days
With the solution4 days
  • Taking the notice and recording what the rule needs0.5 → 0.1 d
  • Tracing the transfer and waiting for the correspondent9 → 2 d
  • Comparing the payout confirmation with the receipt2 → 0.1 d
  • Testing the exceptions and deciding3 → 0.5 d
  • Computing the remedy and writing the letter2 → 0.3 d
  • Posting the refund, the ledger entries and the approval2.5 → 1 d

Estimated split of a typical remittance error claim at the sample credit union: a 19-day median to a finding by hand, estimated from its case log, and the 4-day target with the solution.

How it works

How a claim moves

Seven agents read the notice, trace the money, test the rule and draft the remedy; a specialist signs and a supervisor approves.

What comes in
Transfer in6 sources a claim · receipt, provider log, correspondent, payout bank, call, account
Agents at work
Intake agentnotice read, clock started
Disclosure agentevery element, before release
Then
Trace agentprovider, correspondent, payout bank
Then
Error agentpromised against delivered
Then
Remedy agentrefund or resend, the letter
A person decides
Specialist and supervisorthe specialist signs; the supervisor approves
What comes out
Refund or resend, fee included when late
Letter in the member's language
Audit trail and examiner pack
One case, step by step

One claim under the remittance transfer rule, from the call to the refund

Héctor Villaseñor, a member of Norrell Federal Credit Union in Aurora, Colorado, sent USD 1,200.00 to Guadalajara on Thursday, October 1, 2026. His receipt promised MXN 21,540.00 by Saturday, October 3. Here is what happens when he calls, screen by screen, in the working solution.

  1. 01Monday, October 19 · 11:06 MT

    The member’s call, read in the language he used

    Luis Carrasco · Member Services Representative

    Héctor calls the Member Contact Center in Spanish: the pesos he sent to Marisela Villaseñor Ruiz arrived short, and late. The intake agent reads the call and ticks the five elements a notice must contain under 1005.33(b)(1), each with its source line. It is on time, day 16 of 180, and a notice of error rather than a status inquiry. He wants a refund to Checking ••6620, with letters in Spanish, and the 90-day clock starts: a finding is due by January 17, 2027.

    “Prefiero que me lo devuelvan a mi cuenta.”

  2. 02October 20

    Where the money went, and why it changed

    Trace agent

    The trace agent pulls the provider platform’s log, the rate contract, the correspondent’s messages and the payout confirmation into twelve events, each with its source. The provider platform sent the recipient’s name without the ñ, and Banco Cerro Azul held the money on October 1 at 13:20 over VILLASENOR against VILLASEÑOR. The repair was answered on October 5, after the 72-hour rate contract at 17.9500 had expired, so Halvorsen Clearing Bank re-quoted at 17.4000. MXN 20,880.00 was credited on October 6 at 14:32.

    Root cause, 95%: the correspondent agreement makes Halvorsen Clearing Bank reimburse the rate difference.

  3. 03Thursday morning

    What the receipt promised, beside what was delivered

    Graciela Ponce · Member Payments Specialist

    Graciela opens claim RT-2026-1204. One line holds the Reg E clock: reported on day 16 of 180, the investigation on day 4 of 90, the letter due 3 business days after the finding and the remedy 1 business day after his instructions. Below, nine elements in two columns. The receipt promised 17.9500, MXN 21,540.00 and Saturday, October 3; Banco Cerro Azul delivered 17.4000, MXN 20,880.00 and Tuesday, October 6. The other six elements match.

    MXN 660.00 short · 3 days late

  4. 04One click

    Every value opens the passage it came from

    Graciela Ponce · Member Payments Specialist

    She clicks the source beside the promised pesos. The member’s receipt opens in Spanish as the agents read it: Monto de la transferencia USD 1,200.00, Cargo USD 12.00, Tipo de cambio 1 USD = 17.9500 MXN, with the total for the recipient and the date available highlighted. Any source can be added to the claim’s evidence pack.

    “Total para el destinatario: MXN 21,540.00”

  5. 05Before any finding

    Every exception the rule allows, tested on the evidence

    Error agent

    The error agent tests 7 exceptions and 2 exclusions before an error stands. No estimate: Norrell sent 31,880 transfers to Mexico in 2025, more than 1,000, so it may not estimate the rate there. No extraordinary circumstances: a name held for repair is ordinary processing. No fraud, BSA or OFAC review: screening cleared automatically at 10:51 on October 1. No wrong account number. Each row can be overridden only with a reason code.

    “Amount error stands — 97%” · “Timing error stands — 98%”

  6. 06The remedy

    The refund to the cent, and the letter in Spanish

    Remedy agent

    Héctor chose a refund: USD 48.77. That is USD 36.77 for the MXN 660.00 at the receipt’s rate, plus the USD 12.00 fee, which comes back because the money was late. The core and general ledger entries are prepared with a USD 36.77 recovery claim on Halvorsen Clearing Bank, and post only after a checker approves. The results letter is drafted in Spanish, with an English copy, due by Tuesday, October 27. Graciela signs as maker.

    The remedy agent never posts money or sends a letter: a maker signs and a checker approves.

  7. 07Day 4 of 90

    A second person approves the refund

    Owen Haddad · Member Payments Supervisor

    The refund reaches Owen’s approvals queue with its evidence attached. He did not make it, so he can approve it: USD 48.77 posts to Checking ••6620 and the letter goes to the member notice service. Below wait a resend of MXN 1,150.00, a no-error letter for an estimate the law allows for the Philippines, a cancellation refund of USD 1,515.00 and a Spanish receipt template that needs Denise Kowal, VP Operations.

    “Approved — posted to Checking ••6620 and sent to the member notice service.”

  8. 08Before the money leaves

    Every receipt checked, in English and Spanish

    Disclosure agent

    By 10:40 that Thursday the disclosure agent has checked 214 transfers: 211 passed every element and 3 were held, fixed and released, 141 in English and 73 in Spanish. Two Spanish mobile receipts on template 4.2 lacked the rights statement required by 1005.31(b)(2)(iv) and were re-disclosed on template 4.1 before payment. A branch transfer to Guatemala showed an estimated rate where the rate must be exact.

    “Derechos de cancelación y de resolución de errores — Falta”

  9. 09Every month

    The September test, re-performed from the record

    Nadia Brennan · Compliance Officer

    The testing agent re-tested the September sample in 14 minutes: 65 items, 25 claims and 40 transfers, 412 checks, 410 passed. Two proposed findings: a results letter sent 4 business days after the finding, because no backup checker was named over Labor Day, and a Spanish branch receipt that printed the date available blank. Nadia accepts or rejects each with a reason, with an owner and a date for the fix, before she signs.

    The testing agent never accepts its own finding.

  10. 10Any day

    Who decided, when, on what evidence

    Martin Adeyemi · Internal Auditor

    Every action by people and agents is on one append-only trail, with when, who, what, why and the evidence, from Luis’s notice on October 19 to Owen’s approval on day 4. Martin filters by people, agents, decisions, disclosures or cancellations, and exports the pack for NCUA, the CFPB, internal audit, the Supervisory Committee or the BSA Officer, with account numbers masked.

Who it’s for

Built for everyone who answers for a remittance.

The same claim, seen by the people who take the call, work it, approve it, test it and own the service: what their day looked like, and what it looks like now.

GP
Graciela PonceMember Payments Specialist · signs as maker
Member Payments Specialist
Before
Waits on a correspondent’s email, compares the payout confirmation with the receipt in a spreadsheet and argues the rule’s exceptions from memory.
Now
Opens each claim with the promise and the delivery side by side, every difference named and every exception tested, then decides and signs.
OH
Owen HaddadMember Payments Supervisor · the checker
Member Payments Supervisor
Before
Refunds were keyed into the core and journaled to the general ledger by hand, with no second person checking.
Now
Approves or returns every refund, resend, member letter and cancellation refund with a reason, never one he made, with the evidence attached.
NB
Nadia BrennanCompliance Officer · owns the program and the monthly test
Compliance Officer
Before
Re-performs each element of the monthly sample on a paper worksheet; a broken template is found a month after it went live.
Now
The testing agent re-performs every element; she accepts or rejects each finding with a reason and signs the test. Receipts are checked before release.
LC
Luis CarrascoMember Services Representative · takes notices, often in Spanish
Member Services Representative
Before
Types a free-text note into case management; whether the notice is on time, an inquiry or names a remedy is rarely recorded.
Now
The call is read in the language the member used, every element the rule needs is ticked with its source, and the clock starts.
DK
Denise KowalVP Operations · second approver above USD 2,500
VP Operations
Before
Owns the service level and the escalations, and wants to know which claims are close to day 90 before they are.
Now
Sees every open claim on its clock, is told at day 60, and approves template changes and refunds above USD 2,500 as second approver.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents read the notice, trace the money, test the rule and draft the remedy; a specialist signs and a supervisor approves.

Intake agent

Reads a notice of error from a call, a digital banking message or a branch form, in English or Spanish; extracts the elements of 1005.33(b)(1); checks it is on time; tells a status inquiry from a notice of error; records the member’s chosen remedy and language; starts the 90-day clock.

  • Never decides that an error occurred
  • Never tells a member a result
  • Asks the representative when an element is missing
Disclosure agent

Checks every prepayment disclosure and receipt against the 1005.31(b) elements, including the error-resolution and cancellation rights statement, and whether an estimate is allowed for the country, before the transfer leaves.

  • Never changes a template
  • Never releases a held transfer — a person does
  • Checks every language the member sees
Trace agent

Follows a transfer through the provider platform, the correspondent and the payout bank, orders every event in time with its source and writes the root cause, naming who caused each change.

  • Never guesses a missing event — says “not received” and requests it
  • Never contacts the recipient
Error agent

Lays what the receipt promised beside what was delivered, names each difference as an error type under 1005.33(a)(1) and tests every exception and exclusion the rule allows against the evidence.

  • Never finds “no error” on an exception without the evidence that proves it
  • Below 88% confidence, asks the specialist
  • A person decides
Remedy agent

Computes the refund or resend under 1005.33(c)(2), including the fees on a late transfer, drafts the results or no-error letter in the member’s language and in English, and prepares the core and ledger entries and the correspondent recovery claim.

  • Never posts money or sends a letter
  • A maker signs and a checker approves
  • Every sentence of a letter traces to the finding
Cancellation agent

Watches every transfer’s 30-minute window, checks whether the money was picked up or deposited, and drafts the full refund with fees and its three-business-day due date, or a decline letter that explains why.

  • Never declines a request made inside the window
  • Never refunds without a checker
Testing agent

Draws the Compliance Officer’s monthly sample of claims and transfers, re-performs every element on each item and writes each failure as a proposed finding with its evidence.

  • Never accepts its own finding
  • The Compliance Officer accepts or rejects
Member Payments Specialist

Signs; a supervisor approves every refund. The agents propose; a named person decides.

Ask in plain words

Ask about any claim, transfer or rule

Ask about a claim, a transfer, a rule or a member letter, in plain words. Every answer points to its source and opens the screen it is about.

Why does the member get the $12 fee back?

Because the money was late. For a timing error under 1005.33(a)(1)(iv), the rule adds a second remedy on top of fixing the amount: refund the fees imposed and, where the law allows, the taxes. The receipt promised October 3; Banco Cerro Azul credited the funds on October 6, and none of the exceptions applies. So the refund is USD 36.77 for the shortfall plus the USD 12.00 fee: USD 48.77.

Could the delay have been a sanctions hold?

No. Screening cleared automatically on October 1 at 10:51:07, with no manual review. The payout bank’s hold reason is a name mismatch, VILLASENOR against VILLASEÑOR, and the provider platform’s own log shows it sent the name without the ñ. Exception (iv)(B) needs a real fraud, BSA or OFAC review; there was none, so it does not apply.

Which claims could miss the 90-day clock?

None is past day 60 yet, but two need you this week: RT-2026-1167, Ana Beltrán, Guatemala, at day 58, where the correspondent has not answered two traces, and RT-2026-1171, Rowena Dizon, Philippines, at day 53, where the estimate on her receipt needs the rate source. The VP Operations is told at day 60.

Show me the letter in Spanish

It follows the language Héctor used on the call, as 1005.31(g) requires for error-resolution disclosures, with an English copy for the file. It states both errors, the USD 48.77 refund and how it was worked out, and his right to the documents we relied on. It goes out only after Owen Haddad approves.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Promised and deliveredRemittance transfer error resolution on one page: the Reg E clock in one line, nine elements of the receipt beside what the payout bank delivered, each difference marked, every value with its source.
Every value, its sourceAny value opens the passage it came from, here the member’s Spanish receipt with the total for the recipient and the date available highlighted.
The member’s noticeA call taken in Spanish becomes a timely notice of error: the five elements of 1005.33(b)(1) ticked with their sources, the remedy the member chose and the 90-day clock started.
Delivery traceThe transfer’s path through the provider platform, the correspondent and the payout bank, twelve timed events with their sources, and the root cause.
Rule testEvery exception the remittance transfer rule allows, tested on the evidence before an error stands, with an override that needs a reason code.
Remedy and letterThe refund computed to the cent, the fee returned on a late transfer, the ledger entries and recovery claim, and the results letter in Spanish.
ApprovalsThe checker’s queue: refunds, resends, a no-error letter, a cancellation refund and a template change, each approved or returned with a reason.
Claims on their clocksEvery open claim with its day of 90, error type, status and owner; a delayed feed shown as it happens; restricted claims that never reveal a BSA review.
Disclosure checkRemittance transfer disclosure requirements checked before release: every prepayment disclosure and receipt, in English and Spanish, with held transfers fixed before payment.
CancellationsThe remittance transfer rule’s 30-minute cancellation window watched for every transfer: requests honored and refunded with fees, late ones declined with a drafted letter citing 1005.34.
Compliance testingThe monthly sample re-performed element by element, with each proposed finding accepted or rejected by the Compliance Officer before she signs.
Audit trailEvery action by people and agents with when, who, what, why and the evidence, and packs for NCUA, the CFPB, internal audit, the Supervisory Committee and the BSA Officer.
Roles and separation of dutiesWho can make, check and change what; the systems connected; five-year retention, access by role and redaction in every export.
Governance

Built for Regulation E: cited, checked by a second person, on the record.

Every value opens its sourceEvery value on the comparison, every agent statement and every sentence of a letter opens the passage it came from: the receipt, the payout confirmation, the correspondent’s message, the rate contract, the call transcript or the regulation.
A maker and a checker on money and lettersA specialist signs every refund, resend, results letter, no-error letter and cancellation refund as maker; a supervisor approves as checker and never their own. The VP Operations approves refunds above USD 2,500 and every template change.
Agents propose; people decideThe agents read, compare, draft and propose. They never decide an error, post money, send a letter, change a template or release a held transfer, and the error agent asks the specialist below 88% confidence.
A BSA review is never named to a memberWhen a delay was caused by a BSA review, the claim shows only “Restricted” and “a review required by law” to everyone but the BSA Officer, and the member’s letter says the same.
Every step on the record, kept five yearsWho, what, when, why and the evidence for every action by people and agents, append-only and kept five years from closure. Packs export for NCUA, the CFPB, internal audit, the Supervisory Committee and the BSA Officer, with account numbers masked.
Versioned agents, overrides with a reasonEach agent runs a pinned model and prompt version with its golden-set score. Every override needs a reason code, OV-01 to OV-05, and a change to an agent or a clock is proposed and approved before it takes effect.
Configuration

Your clocks and limits, inside the remittance transfer rule

What the rule sets is locked. What your credit union chooses is a setting, proposed and approved before it takes effect, and on the audit trail.

SettingDefaultChoose from
Member’s window to report an error180 days after the date availableSet by the rule, 1005.33(b)
Finding90 days from the noticeSet by the rule, 1005.33(c)(1)
Service target for a finding45 daysYour own target inside the rule, approved by the Compliance Officer
EscalationsSupervisor at day 45 · VP Operations at day 60, then daily from day 75Your days, proposed and approved before they take effect
Second approverVP Operations above USD 2,500 and on every template changeYour amount; a maker can never check
Error agent proposes at88% confidence; below it, asks the specialistRaised from 85% after the September golden-set review, approved by the VP Operations
Cancellation window30 minutes after payment30 minutes, or longer if your credit union allows it (1005.34)
Disclosure and letter languagesEnglish · Spanish, with an English copy of every letter for the fileEnglish, and Spanish where the member transacts in Spanish (1005.31(g))
Connections

Works with the systems a transfer already runs through

Remittance provider platformtransfers, status, rate contracts and screening results
Correspondent and payout bankthe correspondent’s messages and the payout bank’s confirmation
Digital banking platformprepayment disclosures, receipts and messages, in English and Spanish
Member contact centercall recordings and transcripts, where most notices start
Core banking system and general ledgermember accounts, refunds and the entries that post after approval
Case management and member notice serviceclaims and their documents, and letters in English and Spanish
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
Every
error claim reaches a finding inside the 90-day clock, with the rule paragraph, the evidence and two named people on the record
target
100%
of prepayment disclosures and receipts checked for every Subpart B element, in English and Spanish, before the transfer leaves
Checked before release
214 transfers on a Thursday at the demo credit union
target
4days
median from the member's notice to a finding, against the 90 days Regulation E allows
Found on day 4
the rule allows 90

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate: the 19-day median by hand and the split of a claim’s days · “typical” = published figures (CFPB, remittance transfer enforcement actions announced in 2020, consumerfinance.gov). Rules: Regulation E Subpart B, 12 CFR 1005.30–1005.36 with the official interpretations (consumerfinance.gov, ecfr.gov) · 31 CFR 1010.430 (BSA records, five years) · 31 CFR 1020.320(e) and 12 CFR 748.1 (SAR confidentiality). Norrell Federal Credit Union, Halvorsen Clearing Bank, Banco Cerro Azul, and the people, members, accounts and transfer references named on this page are fictional: characters and sample data in the working solution.

Questions

What banks and credit unions ask about the remittance transfer rule.

What is remittance transfer rule compliance?

Remittance transfer rule compliance is how a bank or credit union handles consumer international transfer disclosures, cancellations and errors under Reg E. The remittance transfer rule is Subpart B of Regulation E, 12 CFR 1005.30–1005.36. It requires a bank or credit union that sends consumer international transfers to give a prepayment disclosure and a receipt, honor cancellations made within 30 minutes, and investigate and fix errors on a 90-day clock. Remittance Transfer Rule Compliance puts what the receipt promised beside what was delivered; its agents trace the transfer, test every exception and draft the remedy for a specialist to sign and a supervisor to approve.

Who must comply with the remittance transfer rule?

A bank or credit union is outside the rule only if it sent 500 or fewer consumer remittance transfers in the previous calendar year and sends 500 or fewer in the current one (12 CFR 1005.30(f)(2)); that threshold rose from 100 to 500 in 2020. Separately, an insured institution may estimate the exchange rate for a country only if it sent 1,000 or fewer transfers there the year before (1005.32(b)(4)). The solution keeps those counts by country and warns before one crosses 1,000.

What are the remittance transfer disclosure requirements?

Before payment the member gets a prepayment disclosure with the transfer amount, fees and taxes, the exchange rate and the amount the recipient will receive. The receipt adds the date the money will be available and a statement of the member’s error-resolution and cancellation rights (12 CFR 1005.31(b)). The disclosure agent checks every disclosure and receipt, in English and Spanish, before the transfer leaves, and holds one that is missing an element for a person to fix and release.

How long does a provider have to resolve a remittance transfer error?

The member has 180 days after the disclosed date available to report an error. The provider then has 90 days to determine whether an error occurred, three business days to report the results and one business day after the member’s instructions to apply the remedy; when the money was late, the fees come back too (12 CFR 1005.33). The solution shows that clock in one line on every claim and tells the supervisor at day 45 and the VP Operations at day 60.

Can a member cancel a remittance transfer?

Yes, within 30 minutes of payment if the money has not been picked up or deposited, with a full refund, fees included, within three business days (12 CFR 1005.34). A transfer scheduled in advance can be canceled until three business days before its date (1005.36). The cancellation agent watches every window and drafts the refund or the decline letter; it never declines a request made inside the window, and a checker approves every refund.

Does it handle notices and letters in Spanish?

Yes. The intake agent reads a notice in the language the member used, and the remedy agent drafts the results or no-error letter in that language with an English copy for the file, as 1005.31(g) requires for error-resolution disclosures. Spanish disclosures and receipts are checked element by element, like English ones.

Do people stay in control of refunds and letters?

Yes. The agents read, compare, draft and propose; they never decide an error, post money, send a letter, change a template or release a held transfer. A specialist signs as maker, a supervisor approves as checker and never approves their own, and the VP Operations approves refunds above USD 2,500 and every template change. Overrides need a reason code and go on the audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your procedures, receipt and letter templates, correspondent agreements and a sample of past error claims, and it goes live once every quality gate has passed. We will walk you through it on your own claims first.

See it on
your error claims.

We'll run Remittance Transfer Rule Compliance on a sample of your own past error claims and receipts.