The 2018 bank ownership rule tied the check to each new account, and that trigger gave way first
On May 11, 2018, banks and broker-dealers had to start identifying the owners of business customers at every new account. The rule’s content held up. Its account trigger was relaxed for renewals that month and, in 2026, for repeat accounts generally.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
On May 11, 2018, banks and broker-dealers had to start identifying the owners of business customers at every new account. The rule’s content held up. Its account trigger was relaxed for renewals that month and, in 2026, for repeat accounts generally.
- The week Friday, May 11, 2018, was the day covered financial institutions had to start identifying and verifying who owned and controlled their business customers.
- Who: a definition built on public filings The rule’s definition of a legal entity customer started from how an entity was created.
- When: each new account, by design The trigger is the part of the rule we think drove cost, and FinCEN’s reasoning for it is on the record.
- What: two prongs, a certification and verification of identity The content of the requirement was simpler than its timing.
- After: event-driven updating, not periodic refresh The fourth part answered what happened once the information was on file.
- The certification as a customer document The certification form in Appendix A was optional.
- Who did the work inside an institution The four parts landed on different people, which is why the compliance date felt different depending on where one sat.
- How the four parts fell on different institutions The rule applied to banks, broker-dealers, mutual funds and futures firms.
- Objections to reading the trigger as the weak point Four objections deserve a reply.
- What a BSA and operations leader could check The four parts translate into checks that remain useful under any later version of the rule.
- With hindsight The account trigger began to give way that same month.
The week
Friday, May 11, 2018, was the day covered financial institutions had to start identifying and verifying who owned and controlled their business customers. The obligation came from the Financial Crimes Enforcement Network’s final rule on Customer Due Diligence Requirements for Financial Institutions, published in the Federal Register on May 11, 2016. The rule took effect on July 11, 2016, but its dates section added: “Covered financial institutions must comply with these rules by May 11, 2018.” It applied to banks, brokers or dealers in securities, mutual funds, and futures commission merchants and introducing brokers in commodities.
The agency described four core elements of customer due diligence that it wanted written into anti-money laundering programs. They were customer identification and verification, identification and verification of the people who own or control a legal entity, and understanding the nature and purpose of customer relationships to develop a customer risk profile. The fourth was ongoing monitoring. The monitoring element covered reporting suspicious transactions and, on a risk basis, maintaining and updating customer information. It said the first element was already required, the rule added the second, and the third and fourth were already implicit in suspicious activity reporting duties.
The text that took effect for compliance purposes, 31 CFR 1010.230, defined the people to be identified in two prongs. The first was each individual, if any, who directly or indirectly owns 25 percent or more of the equity interests of a legal entity customer. The second was a single individual with significant responsibility to control, manage or direct the customer, such as a chief executive or treasurer. Institutions had to identify these people “at the time a new account is opened.” They could use the certification form in the rule’s Appendix A or collect the same information another way, provided the person opening the account certified its accuracy to the best of their knowledge.
Verification followed risk-based procedures that had to contain, at a minimum, the elements institutions already used to verify individual customers under their customer identification programs. The rule defined a legal entity customer as a corporation, limited liability company or other entity created by a public filing, a general partnership, or a similar foreign entity. It excluded regulated financial institutions, SEC-registered issuers and several other categories. It exempted four kinds of accounts, among them point-of-sale retail credit up to $50,000 and certain equipment financing. A “new account” meant “each account opened at a covered financial institution by a legal entity customer on or after the applicability date.” Identification records had to be kept for five years after the account closed.
Ahead of the compliance date, on April 3, 2018, the agency issued 37 frequently asked questions, numbered FIN-2018-G001. They settled several operational points. Institutions generally had to identify and verify owners for each new account, but could rely on an earlier certification if the customer confirmed it was still accurate. A loan renewal or certificate of deposit rollover created a new account. Institutions did not have to collect it retroactively for accounts opened before May 11, 2018. Routine periodic reviews were not, by themselves, a trigger for updating it. The guidance opened with a warning: an institution with notice or reasonable suspicion that a customer was evading the requirements should consider not opening an account, closing one or filing a suspicious activity report.
The beneficial ownership rule is commonly summarized by its threshold: 25 percent equity, plus one controller. That description is correct and incomplete. A rule that tells a bank to collect information has to say four things. It has to say about whom, at what moment, how much proof, and what happens afterward. The CDD rule answered each one, and the answers carried different operational costs. On May 11, 2018, institutions met all four at once in their onboarding queues.
We take the rule in those four parts, which together cover what a compliance or operations leader had to build:
- Who: which customers counted as legal entity customers, and which were excluded or exempted.
- When: the trigger, which the rule tied to each new account.
- What: the two ownership prongs, the certification, and what verification required.
- After: how the information was kept current once collected.
Our argument is that the second part, the account trigger, decided where the work fell. FinCEN chose it deliberately in 2016, and the April 2018 guidance applied it strictly. It was also the part of the rule that gave way, first for renewals in 2018 and then broadly in 2026. After the four parts we look at the certification as a document customers saw, who did the work inside an institution, and how the parts fell on different institutions. We close with the objections to our reading and what a leader can check.
Who: a definition built on public filings
The rule’s definition of a legal entity customer started from how an entity was created. It covered corporations, limited liability companies and other entities created by filing a public document with a Secretary of State or similar office, plus general partnerships and similar foreign entities. An entity that existed because it filed paperwork was in scope. An arrangement that did not, such as a sole proprietorship, was not.
The April 2018 FAQs confirmed the edges. Sole proprietorships, including spousal ones, and unincorporated associations were not legal entity customers, even if they filed with a Secretary of State to register a trade name. FinCEN explained that neither was a separate legal entity from its owners, so ownership was not inherently obscured. Nonprofit entities were excluded from the ownership prong, because they generally lack ownership interests, but institutions still had to collect a control person.
The exclusions removed categories already subject to other disclosure or supervision. Banks and other regulated financial institutions, issuers with securities registered under the Exchange Act, registered investment companies and advisers, registered exchanges and clearing agencies, and several others fell outside. The exemptions worked differently. They did not exclude a customer type. They exempted certain account types, such as point-of-sale retail credit up to $50,000, postage financing, insurance premium financing and equipment finance, with limits if the account allowed payments to third parties or cash refunds.
Why classification was an operations task
Deciding whether a customer was in scope took judgment and data. An account-opening system had to capture the entity type, its formation documents and, for exclusions, evidence such as an exchange listing or registration. The FAQs said institutions could rely on information the customer provided about exclusions, absent knowledge of facts calling it into question, and that their written procedures had to specify what information they would rely on. A misclassified customer was either an unnecessary certification or a missing one. For a bank opening business accounts through branches, the classification step fell on whoever sat across the desk.
The classification also had to work across product lines. A commercial loan system, a treasury management platform and a branch deposit system might each have its own entity-type field, with its own values. The rule did not care which system opened the account. It cared whether the customer was a legal entity customer. Institutions with several origination systems had to make the same classification consistently in each, or route all of them through one.
Trusts, pooled vehicles and the independence of the prongs
The FAQs showed how far the definition reached into ownership chains. Where a trust owned 25 percent or more of a legal entity customer, the ownership-prong beneficial owner was the trustee. That was true whether the trustee was a person or an entity such as a law firm. Where there were co-trustees, institutions were expected to collect and verify at least one. Pooled investment vehicles were treated differently. Because their ownership fluctuates, FinCEN said institutions generally did not have to look through them to individual investors, but still had to collect a control person such as a portfolio manager or general partner.
The FAQs also made a structural point that mattered for system design. The ownership and control prongs “are independent requirements.” Satisfying or being excluded from one did not satisfy or exclude the other. An account-opening workflow therefore needed two separate checks, each able to stop the process, rather than one ownership question with the control person as an afterthought. A nonprofit with no owners still needed a controller. A trust-owned company might have a legal entity as its ownership-prong owner and a natural person as its controller.
When: each new account, by design
The trigger is the part of the rule we think drove cost, and FinCEN’s reasoning for it is on the record. The 2016 preamble described the question commenters had raised. Should a customer provide ownership information “each time it opens a new account at the institution after the rule’s compliance deadline,” or only the first time. FinCEN chose each time. It said it was not requiring periodic updates at set intervals. But it added that “the opening of a new account is a relatively convenient and otherwise appropriate occasion to obtain current information regarding a customer’s beneficial owners.” It then added the definition of new account to the rule.
The same choice protected existing accounts. FinCEN’s proposal had applied the requirement only to new accounts going forward, and the preamble reported that a large majority of commenters on the issue opposed retroactive collection. The final rule kept that approach. Accounts opened before May 11, 2018, were not swept in, and the April 2018 FAQs confirmed that no retroactive review was required.
So the trigger was a compromise with two faces. It spared existing accounts, and it attached the duty to every opening after the compliance date. For a customer with one operating account, the difference was small. Consider a business customer that opened accounts frequently, such as a property manager with an account per building. For that customer, the trigger meant a certification or confirmation at each opening.
Where the trigger met digital onboarding
Where an institution opened business accounts online or through mobile channels as well as branches, the account trigger applied in every channel. A digital flow had to classify the customer, present the ownership questions, capture the certification from the person opening the account and collect each owner’s identifying information. It also had to decide, at the moment of opening, whether an earlier certification existed that the customer could confirm instead.
That last decision can be harder online than at a desk. A banker can look up a customer and ask whether anything has changed. A digital flow needs a reliable match between the applicant and the existing customer record. It also needs a screen that shows prior ownership information for confirmation without exposing it to someone unauthorized. Institutions that could not build that match safely had a simple fallback: collect a new certification every time. The trigger made the fallback compliant and the friction permanent.
Accounts that straddled the date
The applicability date created two populations of business customers. Those whose accounts all predated May 11, 2018, had no certification on file and no obligation to provide one, unless monitoring prompted an update. Those who opened an account on or after that date had to certify. The same customer could move from the first group to the second simply by opening a new account, at which point the institution collected information it had not needed the day before.
For institutions, the split meant that ownership coverage of the commercial book would grow with account activity, not with risk. Long-standing customers with stable account structures could remain without certifications indefinitely. Institutions could choose to collect from them anyway, and the FAQs said collection beyond the rule’s triggers was at the institution’s discretion. Whether to do so was a resourcing and risk decision, and the rule left it with each institution.
Renewals were new accounts
The April 2018 FAQs then answered a question that turned the trigger into a project. Question 12 asked whether customers had to certify beneficial owners during a product renewal, such as a loan renewal or certificate of deposit. The answer was yes. Consistent with the definition of account in the customer identification program rules and 2005 interagency guidance, FinCEN said, each renewal or rollover established another formal banking relationship and a new account. For products established before May 11, 2018, institutions had to obtain certified ownership information at the first renewal after that date.
The answer had a softer second half. For later renewals of the same product, an institution could rely on the earlier certification if the customer confirmed it was accurate. For loan renewals and CD rollovers specifically, FinCEN went further. A customer’s agreement to notify the institution of ownership changes could serve as the confirmation while the loan or CD was outstanding. But the first renewal after May 11, 2018, still required a certification, and FinCEN noted that the industry did not generally treat these products as new accounts.
That mismatch is the core of the operational problem. A certificate of deposit that rolls over automatically has no meeting, no application and no banker in the loop. A rule that treats the rollover as an account opening asks for a step in a process designed to have none. Institutions had from April 3 to May 11 to decide how to insert one.
Multiple accounts and the confirmation shortcut
Question 10 addressed customers who opened several accounts. Generally, FinCEN said, institutions had to identify and verify ownership for each new account, regardless of the number opened or over what period. An institution that already held a certification could rely on it for later accounts. The customer had to certify or confirm, verbally or in writing, that it was still accurate, and the institution had to have no contrary knowledge. The institution had to keep a record of that confirmation.
The shortcut reduced the paperwork but not the event. Each opening still required a confirmation, a record and a check that nothing known contradicted it. Question 9 added that institutions had to retain all sets of beneficial ownership information collected about a customer, including each confirmation, for the applicable retention periods. The account trigger therefore produced a growing file per customer, keyed to accounts rather than to the customer.
What: two prongs, a certification and verification of identity
The content of the requirement was simpler than its timing. The ownership prong could name up to four individuals, since each must hold at least 25 percent. The control prong named exactly one. For each, the institution collected identifying information and verified it.
The FAQs addressed indirect ownership with a worked diagram. Ownership had to be traced through intermediate companies, so that a person holding 30 percent indirectly through one company counted, and a person reaching 25 percent only by adding holdings through two companies also counted. But the FAQs also said institutions could accept and reasonably rely on the information about beneficial owners that the customer’s representative presented, absent knowledge of facts that would reasonably call it into question.
Verification was of identity, not of ownership. The rule required risk-based procedures containing at least the customer identification program elements for individuals. An institution had to confirm that the named people were real and were who the certification said. It did not have to prove that they held the stated percentages. That distinction kept the cost of verification bounded. It also meant the quality of ownership data depended on the honesty of the person certifying, which is why the rule placed weight on the certification itself and on the institution’s knowledge.
The control prong and who signs
The control prong named one individual with significant responsibility to control, manage or direct the customer. The rule listed examples: a chief executive, chief financial or operating officer, managing member, general partner, president, vice president or treasurer, or any other individual who regularly performs similar functions. The person named came from the customer’s representative, who certified the information.
That arrangement put weight on the person signing. The certification was made to the best of that person’s knowledge, and the institution could rely on it absent contrary knowledge. A careful onboarding process therefore recorded who certified, in what capacity, and on what date, alongside the owners and controller named. If the information later proved false, the record showed what the institution had been told and by whom. That record was the institution’s evidence that its reliance was reasonable.
Existing customers as owners
Question 7 handled a common case. Suppose a named beneficial owner already had a personal account at the institution. The institution could rely on its existing identification and verification of that person, if the information was current and the entity’s representative confirmed it. The beneficial ownership record could cross-reference the existing customer identification record. That answer only helped institutions whose systems could link a person’s retail record to a business customer’s ownership record. Where the systems were separate, the institution collected the same person twice.
Records as the evidence for each part
The rule’s recordkeeping section tied the four parts together. Identification records, including any certification, had to be kept for five years after the account closed. Verification records, describing the documents or non-documentary methods used and the resolution of any substantive discrepancy, had to be kept for five years after the record was made. Question 9 of the FAQs added that institutions had to keep every set of ownership information collected about a customer, including updates and confirmations.
The two clocks ran on different events. One ran from account closure, the other from record creation. For a customer with several accounts opened at different times, each relying on confirmations of an earlier certification, the retention schedule became a matrix. An institution that stored certifications only at the customer level, without linking them to each account they supported, could struggle to show which record covered which account and when it could be destroyed.
After: event-driven updating, not periodic refresh
The fourth part answered what happened once the information was on file. The rule did not require periodic refresh. It required, as part of ongoing monitoring, that institutions maintain and update customer information on a risk basis, including beneficial ownership information.
The April 2018 FAQs made the trigger explicit. Question 14 said institutions had no obligation to update beneficial ownership information as a matter of course during regular or periodic reviews, absent specific risk-based concerns. The obligation arose when, in normal monitoring, the institution learned of information relevant to reassessing the customer’s risk, including a possible change of ownership. Question 13 applied the same trigger to accounts opened before the compliance date. Question 15 said existing monitoring processes could satisfy the requirement if they already met it, quoting the preamble’s view that practice for suspicious activity reporting should already be enough.
Question 16 drew a practical line. A change of address for a known beneficial owner could be updated through ordinary processes, perhaps with a verbal confirmation. A change of beneficial owner required collecting, certifying and verifying the new person. The update rules thus distinguished between correcting a record and replacing a person.
Signals that should reopen the record
Because updating depended on what monitoring noticed, the practical question was which signals counted. The FAQs spoke of information relevant to reassessing the customer’s risk, including a possible change of beneficial ownership. They did not list signals, and the right list depends on the institution. Examples a bank might adopt include a request to change authorized signers, a new controlling officer named in correspondence, and news of an acquisition or merger. A change of registered agent or formation state, or payment patterns inconsistent with the risk profile, could also count.
Each signal arrives in a different place. Signer changes arrive at a branch or a treasury services desk. Acquisition news reaches a relationship manager. Payment patterns surface in transaction monitoring. A process that relied on transaction monitoring alone could miss the first two. The rule’s risk-based updating standard worked only if the institution connected the places where ownership changes become visible to the people who could reopen the record.
The asymmetry between the trigger and the update
Put the second and fourth parts side by side and an asymmetry appears. For a customer that opened no new accounts, ownership information could sit unchanged until monitoring surfaced a reason to revisit it. For a customer that opened accounts frequently, the same information was reconfirmed at each opening, whether or not anything suggested a change. The frequency of review depended on the customer’s product activity, not on its risk.
In our reading, that is the design flaw the account trigger carried from the start. FinCEN had chosen the account opening because it was a convenient moment to ask. Convenience is a property of the institution’s process, not of the customer’s risk. The rule’s own updating standard was risk-based. The trigger was not.
The certification as a customer document
The certification form in Appendix A was optional. Question 8 of the FAQs said institutions could use their own forms or any other means that met the substantive requirements, and should keep the form rather than file it with FinCEN. Each institution still had to decide how the request would look to a customer, because for small business owners it was a new question from their bank.
The request asked for each owner’s name, address, date of birth and identification number, and the controller’s. For a small company, the person opening the account might be both owner and controller, and the form was quick. For a company with layered ownership, the representative might not know the answer without asking lawyers or parent companies. The rule allowed the institution to rely on the representative’s certification. It did not oblige the representative to investigate, beyond certifying to the best of their knowledge.
The FAQs’ opening caution applied here. An institution with notice of, or a reasonable suspicion of, evasion was told to consider declining the account, closing it or filing a suspicious activity report, regardless of the interpretations that followed. A certification process that recorded refusals and inconsistent answers gave the institution what it needed to act on that caution. One that simply stalled an application did not.
What the certification could not tell an institution
A certification captured the customer’s account of its owners on one date. It did not show how the ownership was structured below the named people, whether nominee arrangements existed, or whether the 25 percent threshold had been engineered to keep someone off the form. The rule did not require institutions to find those things out. It did require them to act on what they knew. In our reading, the certification was a floor, and an institution’s customer risk profile, built under the third core element, decided when it should ask for more.
Who did the work inside an institution
The four parts landed on different people, which is why the compliance date felt different depending on where one sat.
Classification and certification fell on whoever opened accounts. In a community bank, that would typically be branch staff and commercial lenders. In a larger bank, it could be treasury management onboarding teams and relationship managers, sometimes supported by a central account-opening unit. Each needed training on entity types, exclusions, the two prongs and the certification form, and each needed a way to stop an account opening when the certification was missing.
Verification fell on the same customer identification processes used for individuals, and therefore on the systems that ran them. Records fell on document management and on the core or customer information system, which had to store certifications, link them to accounts and keep them for five years after closure.
Renewals fell on product operations. Automatic CD rollovers and loan renewals often ran in batch jobs owned by deposit and lending operations, not by compliance. Making them comply meant finding every renewing product, identifying which customers were legal entity customers, and either collecting certifications before renewal or obtaining an agreement to notify of changes. That work had to be done between the FAQs and the compliance date, or the institution would face renewals it could not process in compliance.
Systems fell, in part, outside the institution. Banks that ran core processing or account opening on vendor platforms would have needed those vendors to add fields for the certification, the two prongs and the link between a business customer and its owners. They also needed vendor changes to renewal batch jobs. An institution’s readiness for the compliance date was therefore partly a function of its vendors’ release schedules, and its contracts determined how much say it had in them.
Updating fell on monitoring: the BSA/AML function, its alert reviewers and the customer due diligence refresh teams. Their job was to recognize information suggesting an ownership change and route it back to collection. That handoff, from monitoring to onboarding, needed a defined path.
Training and quality control
The rule changed what front-line staff had to know. A banker opening a business account needed to recognize entity types, know the exclusions and exemptions, explain the certification, and spot answers that did not add up. The FAQs’ caution about evasion assumed someone would notice. Training was the main way that assumption could hold across branches and channels.
Quality control then checked whether training worked. A sample of business accounts opened after May 11, 2018 could be reviewed for a complete certification, a named controller, verification records for each person and correct handling of exclusions. Renewals could be sampled the same way. Findings from those samples showed where the process broke, whether at a channel, a product or a team. Independent testing of the AML program, which institutions already conducted, could include the new requirement in its scope.
Quality control also had a feedback role. If reviewers found that one origination system routinely produced incomplete certifications, the fix might be a required field rather than more training. The rule’s operational cost depended heavily on that kind of system change, made early.
How the four parts fell on different institutions
The rule applied to banks, broker-dealers, mutual funds and futures firms. The parts weighed differently on each.
Community banks and credit unions
For a community bank or a federally insured credit union, business customers could be small companies with one or two owners. The ownership prong was simple. The control prong named the same person. The burden lay in volume of training relative to staff, in branch processes and in renewals of small business loans and CDs. In our reading, credit unions fall within the rule’s definition of a bank, so the same trigger applied to each new account for a business member.
Regional and large banks
For larger banks, the weight lay in the account trigger and in system integration. Commercial customers opened accounts across lines of business. Each line had its own platform. Reusing a certification across them required a shared customer record, which a bank either had or had to build. The confirmation shortcut in the FAQs was only as useful as the bank’s ability to find the previous certification at the moment of opening.
Broker-dealers and wealth managers
For broker-dealers, the customer identification program was already familiar, but account structures differed. Institutional customers might open accounts per strategy or per fund. Introducing and clearing firms had to decide who collected the certification, and the rule’s reliance provision allowed one regulated institution to rely on another only under conditions, including a contract and an annual certification. A wealth manager affiliated with a broker-dealer had to map which entity opened which account for which client entity.
Mutual funds and futures firms
The rule also reached mutual funds and futures commission merchants and introducing brokers. Their customer bases and account structures differ from banks’. A fund may hold accounts opened through intermediaries rather than directly, and a futures firm’s legal entity customers may include pooled vehicles, for which the FAQs required only a control person. For these firms, the classification step and the pooled-vehicle answer carried more weight than the renewal question, which mattered chiefly to deposit and lending products.
Objections to reading the trigger as the weak point
Four objections deserve a reply.
The first is that the trigger was the point. FinCEN wanted current ownership information, and asking at each account opening was a way to refresh it without imposing periodic reviews. That is a fair statement of the 2016 reasoning. Our reply is that the refresh it produced was uneven. Customers that opened accounts frequently were refreshed frequently, regardless of risk. Customers that opened none were refreshed only through monitoring. A rule that wanted current information on higher-risk customers had a better tool in its own updating provision.
The second is that the burden was manageable. The confirmation shortcut meant a returning customer only had to say nothing had changed. That reduced the paperwork. It did not reduce the steps. Each confirmation had to be obtained, recorded and retained, and each had to be checked against what the institution knew. Across a large commercial book, those steps added up. FinCEN’s 2026 order recorded that some institutions and trade associations kept arguing, including in comment letters it cited, that the requirement imposed burdens without corresponding benefits.
The third is that the renewals answer was simply correct as a reading of the account definition. FinCEN tied it to the customer identification program’s definition and 2005 interagency guidance. We do not dispute the reading. We note that FinCEN itself acknowledged that the industry did not generally treat renewals as new accounts, and that it relaxed the answer within days of the compliance date. As we see it, an interpretation suspended days after it took effect was mismatched to the operations it governed.
A fourth objection concerns value. The 2016 preamble said law enforcement had advised FinCEN that ownership information could be useful in investigations even when an illicit actor supplied false information. On that view, more frequent collection yields more records, and more records help investigators. We accept that the records have value. The question the account trigger raised was whether the marginal record, collected because a known customer opened another account, added enough to justify the step. FinCEN’s own later actions answered that question for renewals in 2018 and for repeat accounts in 2026.
What a BSA and operations leader could check
The four parts translate into checks that remain useful under any later version of the rule.
- Confirm that every system that opens accounts for business customers applies the same legal entity classification and exclusion logic, and that its results agree.
- Map every event the institution treats as a beneficial ownership trigger, including renewals, rollovers and additional accounts, and record which rule or relief supports each.
- Check that a certification collected in one line of business can be found and reused in another, with the customer’s confirmation recorded.
- Define the path by which monitoring sends a possible ownership change back to collection, and test it with a sample of past alerts.
- Keep identification records for five years after account closure and verification records for five years after creation, and confirm the systems can produce both.
Each check produces evidence: a mapping, a test result or a record. Together they show an examiner that the institution knows where the obligation falls, which is the question each later change to the rule has asked again.
With hindsight
The account trigger began to give way that same month. On May 16, 2018, FinCEN issued ruling FIN-2018-R002. It granted 90 days of limited exceptive relief for certain products that roll over or renew automatically, such as CDs and loans, that had been established before May 11, 2018. The relief applied retroactively from May 11 and was set to expire on August 9, 2018. The ruling restated the April FAQ answer that each renewal created a new account. It said FinCEN understood that some institutions had not treated rollovers or renewals as new accounts and had set up automatic processes to continue the relationship.
On September 7, 2018, FinCEN replaced the temporary relief with a permanent exception in ruling FIN-2018-R004. Institutions no longer had to identify and verify beneficial owners when a new account arose from a CD rollover. The same applied to a renewal, modification or extension of a loan, commercial line of credit or credit card account that needed no underwriting review and approval. Safe deposit box renewals were also covered. The exception did not apply to the initial opening of those accounts.
The broader trigger stood for longer. On February 13, 2026, FinCEN issued order FIN-2026-R001, “Exceptive Relief from Requirement to Identify and Verify Beneficial Owners at Each Account Opening.” It allowed covered institutions to limit identification and verification to three circumstances. The first was when a legal entity customer first opens an account. The second was any later time when the institution knows facts that would reasonably call the earlier information into question. The third was as needed under its risk-based ongoing due diligence procedures.
The order’s background section told the history from FinCEN’s side. It quoted the 2016 preamble’s “relatively convenient” reasoning. It said some institutions and trade associations had disagreed at the time and continued to argue that the requirement imposed burdens without corresponding benefits. It cited the 2018 FAQ shortcut and the 2018 exception as earlier attempts to reduce burden. It cited Executive Order 14192, the January 31, 2025 order on deregulation. It said the relief was also part of FinCEN’s obligations under the Corporate Transparency Act to revise the 2016 rule, and that FinCEN anticipated further changes through rulemaking. Using the relief was at each institution’s discretion.
As checked on November 15, 2026, we did not find a final rule revising the 2016 CDD rule in the Federal Register. On April 10, 2026, FinCEN proposed a broad reform of anti-money laundering program requirements. On August 14, 2026, it finalized changes exempting reporting companies from reporting the beneficial ownership information of U.S. persons under the Corporate Transparency Act. In our reading, that second change means a bank cannot expect a federal registry to hold ownership data for its domestic business customers. Its own collection remains the source.
What held up was the substance of the 2016 rule. The two prongs, the certification, identity verification and risk-based updating all survived. What did not hold up was the choice of trigger. The 2026 order adopted, as an option, the alternative the 2016 preamble had considered and rejected: asking the first time, then relying on monitoring and knowledge. Institutions that built their processes around customers rather than accounts were positioned to use it.
Spotted an error? Tell us and we will check it and correct the article where needed.