Home / Wiki / F / Funds Transfer Recordkeeping

Funds Transfer Recordkeeping

Compliance Risk and ControlsUpdated 15 Nov 2026

Funds transfer recordkeeping is the requirement that banks, money transmitters and other financial institutions collect and keep defined information about the funds transfers they handle, such as the names of the sender and recipient, the amount, the date and the institutions involved, and retrieve it quickly when authorities ask. The rules let investigators follow the money trail of a wire transfer through every institution in the chain.

The best-known version is the United States rule at 31 CFR 1010.410(e) and (f), issued under the Bank Secrecy Act. It has two parts: a recordkeeping rule, which says what each institution must record and keep, and the travel rule, which says what information must be passed along with the payment to the next institution. Comparable obligations exist in most countries under FATF Recommendation 16 and are often called wire transfer transparency rules.

01

Funds transfer recordkeeping in plain terms

When a parcel is shipped, each depot along the route scans it and keeps a log, so if something goes wrong anyone can see where it went and who sent it. Without the logs, a parcel could vanish between depots with no trace.

Funds transfer recordkeeping is the scanning log for money. Each bank that sends, relays or receives a transfer keeps a record of who sent it, who it was for, how much it was and where it went next. If investigators later suspect the money was linked to crime, they can follow it, step by step, from one bank to the next.

02

Requirements in the United States

The rules apply to funds transfers of $3,000 or more, mainly wire transfers through systems such as Fedwire, CHIPS and SWIFT, and to transmittals of funds by nonbank institutions.

  • Originator's institution. It must record the originator's name and address, the amount, the execution date, any payment instructions, the identity of the beneficiary's institution, and as many details about the beneficiary, such as name, address and account number, as it receives.
  • Non-established customers. If the originator does not have an account relationship, the institution must also verify identity and record details such as the type and number of the identification used and a taxpayer identification number where available.
  • Intermediary and beneficiary institutions. They must keep the payment order they receive, and the beneficiary's institution has added duties when the beneficiary is not an established customer.
  • Retention and retrieval. Records must be kept for five years and be retrievable, in some cases by the name of the originator or beneficiary.

The rules were adopted jointly by the Treasury and the Federal Reserve and took effect in 1996. FinCEN and the Federal Reserve proposed in 2020 to lower the threshold for cross-border transfers and to clarify how the rules apply to convertible virtual currency transactions.

03

Equivalent rules elsewhere

FATF Recommendation 16 requires countries to ensure that wire transfers carry accurate originator and beneficiary information throughout the payment chain, with a general threshold of no more than USD/EUR 1,000 for full verification, and that institutions keep it. In the European Union, the Transfer of Funds Regulation, recast as Regulation (EU) 2023/1113, sets the information that must accompany transfers, including transfers of crypto-assets from 30 December 2024, and requires records to be kept for five years. The United Kingdom applies equivalent rules through its Money Laundering Regulations. As with other recordkeeping requirements, national data protection laws also limit how long records can be kept after the retention period ends.

04

Compliance in practice

Institutions meet these obligations largely through their payment systems. Message formats such as SWIFT MT103 and ISO 20022 messages carry structured fields for originator and beneficiary data, and the move to ISO 20022 has improved the quality and consistency of the information. Firms set up controls to detect missing or meaningless information, decide whether to reject, suspend or query incomplete transfers, and feed the data into sanctions screening and transaction monitoring. Records are usually stored in archives that link the payment message with customer identification records and can be searched quickly when a subpoena or FinCEN request arrives. A data retention schedule sets when records can be deleted.

05

Enforcement and challenges

Regulators treat incomplete wire records and the stripping of information from payment messages as serious violations, and several large enforcement actions against banks have involved altered or missing originator details in transfers that evaded sanctions screening. Practical challenges include transfers that pass through several intermediaries, inconsistent data from foreign institutions, legacy systems with limited fields, and applying the same principles to instant payments and crypto-asset transfers.

Last updated 15 Nov 2026