FINRA’s 2016 WORM fines found alterable records across systems; the SEC later added an audit-trail option
On December 21, 2016, FINRA fined 12 firms $14.4 million for failing to keep electronic broker-dealer records in a format that prevents alteration. The deficiencies spanned multiple systems. In our reading, the test was whether a firm knew every system holding a required record.
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 December 21, 2016, FINRA fined 12 firms $14.4 million for failing to keep electronic broker-dealer records in a format that prevents alteration. The deficiencies spanned multiple systems. In our reading, the test was whether a firm knew every system holding a required record.
- The week The release listed eight sanctions.
- The records: what the rules require a firm to keep The SEC’s 2003 release set out the structure.
- The systems: where required records live FINRA said the deficiencies spanned multiple systems. [1] In our reading, that phrase is the key to the case.
- The protection: what made records unalterable The release also asked for accountability in configuration.
- The proof: procedures and supervision FINRA found that each firm had procedural and supervisory deficiencies related to preserving electronic records. [1] That finding is separate from the storage failures.
- How the issue reaches different firms Large firms tend to run more systems across business lines than small ones, which raises the inventory burden.
- Objections, in order FINRA paired the storage findings with procedural and supervisory deficiencies. [1] The storage problem lasted for prolonged periods in most cases. [1] A configuration error that a firm’s own supervision does not find is a compliance failure.
- What technology and compliance leaders could check Start with the inventory.
- With hindsight FINRA’s December 2016 matters were followed by a long rulemaking on how firms may preserve records.
The week
On Wednesday, December 21, 2016, the Financial Industry Regulatory Authority announced that it had fined 12 firms a total of $14.4 million. [1] The release said the fines were for significant deficiencies in preserving broker-dealer and customer records in a format that prevents alteration. [1] Its subheading said the matters reflected FINRA’s focus on cybersecurity. [1]
FINRA found that, at various times and in most cases for prolonged periods, the firms failed to keep electronic records in write once, read many format, known as WORM. [1] The release described WORM as a format that prevents the alteration or destruction of records stored electronically. [1]
The release listed eight sanctions. Some were imposed jointly on affiliated firms. [1] The largest was $4 million, imposed jointly on two affiliates, and the smallest was $500,000. [1] The amounts in the eight sanctions add to the $14.4 million total the release announced. [1]
FINRA said each of the 12 firms had WORM deficiencies that affected millions, and in some cases hundreds of millions, of records central to their brokerage businesses. [1] It said the deficiencies spanned multiple systems and categories of records. [1]
The release reported two further findings. Each firm had related procedural and supervisory deficiencies affecting its ability to retain and preserve broker-dealer records stored electronically. [1] Three of the firms failed to retain certain records they were required to keep under record retention rules. [1]
The firms settled without admitting or denying the charges and consented to the entry of FINRA’s findings. [1] The release said investors could find the disciplinary documents in FINRA’s Disciplinary Actions Online database. [1]
FINRA tied the requirement to federal law. It said federal securities laws and FINRA rules require business-related electronic records to be kept in WORM format to prevent alteration. [1] It cited the SEC’s statement that books and records are the primary means of monitoring compliance with securities laws, including antifraud provisions and financial responsibility standards. [1]
The SEC statement came from a 2003 interpretive release, Electronic Storage of Broker-Dealer Records. [2] That release explained that Rule 17a-3 requires broker-dealers to make certain records, and Rule 17a-4 sets how and for how long they must be preserved. [2] Records listed in Rule 17a-3 include trade blotters, ledgers, order tickets, trade confirmations and trial balances. [2]
The 2003 release recounted that the SEC had amended Rule 17a-4(f) in 1997 to allow electronic storage. [2] The rule required that electronic storage media preserve records exclusively in a non-rewriteable, non-erasable format. [2] It also required automatic verification of the recording process, serialization and time-dating, and the capacity to download indexes and records. [2]
In 2003, the SEC said the rule did not require a particular technology such as optical disks. [2] A broker-dealer could use a system that prevents overwriting, erasing or altering a record during its retention period through integrated hardware and software control codes. [2] The SEC said its interpretation did not include systems that only mitigate the risk that a record will be overwritten. [2]
The 2003 release also noted that recent events involving the deletion of emails by broker-dealers had affirmed the need for measures to protect record integrity. [2] FINRA’s December 2016 release added a newer concern. It said aggressive attempts to hack into electronic data repositories posed a threat to inadequately protected records, reinforcing the need for WORM storage. [1]
The December 2016 fines are easy to read as a storage problem: firms bought the wrong disks or set the wrong flags. FINRA’s own description points elsewhere. The deficiencies spanned multiple systems and categories of records, affected records central to the firms’ businesses, and came with supervisory gaps. [1] In our reading, that is a description of an inventory failure.
Our argument is that WORM compliance depended on four things a firm had to get right in sequence, and that the fines show where the sequence broke. We take them in order:
- The records: which records the rules required the firm to preserve.
- The systems: which of the firm’s systems created or held those records.
- The protection: what made each system’s records non-rewriteable and non-erasable for the retention period.
- The proof: how the firm showed, through procedures and supervision, that the first three were done.
The four parts are mutually exclusive. The first is a legal question, the second an architecture question, the third a technical question and the fourth a governance question. A firm can answer one well and fail another. After the four parts, we look at how the issue reaches different kinds of firms, take the strongest objections in order, and end with what technology and compliance leaders could check.
We explain public documents here. Nothing here is legal advice, and firms should confirm their obligations with counsel.
The records: what the rules require a firm to keep
The two rules
The SEC’s 2003 release set out the structure. Rule 17a-3 requires broker-dealers to make certain records. [2] Rule 17a-4 specifies how records created under Rule 17a-3, and certain other records, must be maintained, and for how long. [2] Together, the release said, the rules require a comprehensive record of each securities transaction and of the firm’s securities business in general. [2]
The two rules divide the work. Rule 17a-3 answers what must exist. Rule 17a-4 answers how long it must be kept and in what form. [2] A firm that gets the first wrong cannot get the second right, because it will not know which records the storage rules cover.
The release gave examples: trade blotters, asset and liability ledgers, income ledgers, customer account ledgers, securities records, order tickets, trade confirmations, trial balances and some employment records. [2] It said communications that relate to the firm’s business as such must be kept for three years, and some other records for longer periods. [2]
Why the scope is wide
The list is long, and it runs across functions. Trading desks create order tickets. Operations creates confirmations. Finance keeps ledgers and trial balances. Human resources keeps some employment records. Business communications come from every part of the firm. [2]
Each function chooses its own systems. A required record can therefore be born in a trading platform, a general ledger, a document management system or a messaging tool. The legal list does not map neatly to an application list. That gap is where the inventory problem begins.
The records FINRA named
The December 2016 release spoke of broker-dealer and customer records and of records central to the firms’ brokerage businesses. [1] It did not list record types in the release itself. It pointed readers to the disciplinary documents for detail. [1] Our analysis relies on the release and does not describe what the individual settlements said.
Retention as a separate failure
Three firms were also found to have failed to retain certain records they were required to keep. [1] That is a different failure from WORM storage. A record kept in an alterable format still exists. A record not retained does not. Both start from the same question: did the firm know what it had to keep?
Communications as records
The 2003 release said communications that relate to the firm’s business as such must be kept for three years. [2] That category reaches beyond formal records. It includes messages between employees and with customers about the business, whatever tool carries them.
Communications are where the inventory problem is hardest. A trade blotter lives in a known system. A business message can live in email, chat, a collaboration tool or a phone’s messaging app. Each channel the firm permits has to be captured and preserved. Each channel it does not permit has to be controlled, or the firm has records it cannot preserve.
Records created by systems, not people
Modern records are produced by systems as well as by people. An order management system writes an order record. A reconciliation tool writes a break report. A reporting job writes a file. Each output may be a required record or a working file, depending on the rules and the firm’s own determinations.
That determination is a legal and compliance judgment, and the firm has to make it in writing. Without it, engineers cannot know which outputs to send to compliant storage. The inventory in the next part depends on this list.
Writing the determinations down
A hypothetical firm shows the work. Say it runs an order management system, a client reporting portal and an analytics platform. Compliance reviews each output. Order records are required records. Client statements sent through the portal are required records. The analytics platform’s models are working files, and the firm records why.
That written determination becomes the input to the inventory. Engineering knows the first two systems must preserve their outputs in a compliant way. The third does not, unless it becomes the only home of required data. When the firm adds a fourth system, the same review happens before launch.
The systems: where required records live
Multiple systems per firm
FINRA said the deficiencies spanned multiple systems. [1] In our reading, that phrase is the key to the case. A firm with a compliant archive for email could still be out of compliance if trade records were kept in a separate database without WORM controls.
The pattern follows from how firms build. A firm buys an archive for one category of records and configures it carefully. Other systems that hold required records may not be connected to the archive, because no one listed them as record systems.
The inventory as the control
The control that prevents this outcome is an inventory: every system that creates or holds a required record, with the record type, the retention period and the storage method. Each entry needs an owner. Each new system needs a check against the list before it goes live.
The rule did not use the word inventory. It required the records to be preserved in a compliant way. [2] An inventory is the means by which a firm can show it knows where every required record is. In our view, the fines are best read as evidence that some firms lacked that means for some systems.
Change as a source of gaps
Systems change. A firm migrates a ledger, replaces a trading platform or adds a client portal. Each change can create a new place where required records live. If the change process does not ask whether the new system holds required records, the inventory falls out of date.
FINRA said the deficiencies lasted, in most cases, for prolonged periods. [1] That fits a gap that opened during a change and escaped later checks. It is also consistent with an inventory built once and not maintained, though the release does not say how each gap arose.
Building the inventory from two directions
An inventory built only from the records list misses systems no one thought to name. An inventory built only from the system catalog misses records produced outside cataloged systems. Building from both directions closes both gaps.
From the top, compliance takes each required record type and asks where it is created and stored. From the bottom, technology takes each system in the catalog and asks whether it creates or holds any required record. Where the two lists disagree, someone investigates. The disagreements are where findings like FINRA’s start. [1]
End-user tools
Spreadsheets, shared drives and personal folders also hold records. A trader’s spreadsheet of allocations or an operations analyst’s reconciliation file may be the only record of a decision. The firm’s determinations should say whether such files are required records and, if so, how they reach compliant storage.
Controls here are procedural as well as technical. Staff need to know where required records must be saved. Supervisors need to check. Technology can help by routing designated folders to compliant storage automatically.
Copies and derived data
Firms also create copies. Data warehouses, analytics platforms and reporting marts hold copies of trade and account data. Whether a copy is a required record depends on the rules and the firm’s determinations. If the original is preserved compliantly, the copy may not need to be. If the copy is the only complete version, it may.
Those questions belong in the inventory too. A firm that preserves the source system but deletes and rebuilds the source data regularly may find that its compliant record exists only in a downstream copy that was not designed for preservation.
Acquisitions and new business lines
An acquired firm brings its own systems. Some will hold required records. Its preservation methods may differ from the buyer’s. Until the systems are migrated or confirmed, the acquired records sit outside the buyer’s inventory.
A new business line has the same effect. A firm that starts offering a new product may add a vendor platform that creates new record types. The records review belongs in the launch checklist, alongside the legal and risk reviews.
Decommissioning
Retiring a system raises the opposite problem. Records in the old system may still be within their retention period. If the system is switched off before they are migrated to compliant storage, the firm loses them, which is the retention failure FINRA found at three firms. [1]
A decommissioning checklist should ask whether the system holds required records, where they will go and how the migration will be verified. The verification matters, because a migration can change formats or drop metadata such as dates that the rule requires the firm to preserve. [2]
Vendors and hosted systems
Some systems are run by vendors. The pre-2022 rule required broker-dealers that used electronic storage to engage a third party with access to and the ability to download the records. [3] That third party had to file written undertakings with the firm’s designated examining authority. [3] A hosted system that held required records needed to fit that arrangement.
In our reading, a vendor-hosted application was a plausible route for records to leave the firm’s controlled archive without anyone noticing. The firm owned the obligation. The vendor owned the system. The inventory has to include both.
The protection: what made records unalterable
The WORM requirement
Before 2022, Rule 17a-4(f) required electronic storage media to preserve records exclusively in a non-rewriteable, non-erasable format. [2] [3] The SEC had said in 2003 that this could be achieved with integrated hardware and software codes that prevent overwriting or erasure during the retention period. [2]
The 2003 release described one method: storing a retention period with each record and blocking deletion or alteration by any intervention until the period lapsed. [2] It described codes, intrinsic to the system, that could not be turned off. [2] It excluded systems that only mitigate the risk of overwriting or erasure, such as those relying on passwords or other extrinsic security controls. [2] The release said the ability to overwrite or erase records on such systems made them non-compliant. [2]
The release also asked for accountability in configuration. It said audit procedures for such a system should include senior management level approval of how it is configured to keep records for their retention periods. [2] It said it would be prudent to give records entered without a retention period a permanent retention period by default. [2]
Other requirements beside WORM
WORM was one of several requirements. The storage media also had to verify automatically the quality and accuracy of the recording process. [2] They had to serialize units of storage media and time-date the retention period, and to be able to download indexes and records to any medium acceptable under the rule. [2]
A system could meet the WORM requirement and fail another. For example, a store that prevents deletion but cannot export records in a usable form fails the download requirement. Each requirement has to be checked separately for each system.
Retention periods and disposal
The 2003 release said the requirement did not mean records must be kept indefinitely. [2] Electronic records need be kept only for the retention period the rule sets, like paper and microfilm. [2] The release described systems that store a retention period with each record and allow deletion once the period has lapsed. [2]
That design puts weight on getting the retention period right. A period set too short lets records go before the rule allows. A period set too long keeps data the firm may prefer to dispose of. Both errors start with the records list, which ties each record type to its period. [2]
Holds that outlast retention
Litigation and regulatory inquiries can require a firm to keep records beyond their normal retention period. A storage system with retention locks needs a way to extend retention for specific records when a hold applies. The legal team owns the hold. The system has to carry it out.
The 2003 release made the same point. It said circumstances such as a subpoena could require a broker-dealer to keep records beyond the rule’s retention periods. [2] It said the firm must take steps so those records are not deleted, and that its storage system must allow retention beyond the rule’s periods. [2]
In our reading, holds are a second reason the records list and the inventory must stay current. A hold that names a record type has to reach every system that holds it.
Configuration as a failure point
Software-based WORM depends on configuration. A retention setting has to be applied to the right storage locations. A compliance mode has to be enabled rather than a softer governance mode. Administrative privileges that could override the setting have to be controlled.
None of those settings is visible to a business user. A system can appear to work normally while its records remain alterable. That is why the protection has to be tested, not assumed. A test that tries to alter or delete a record during its retention period, and records the failure, is evidence that the control works.
The security angle
FINRA framed the matters as reflecting its focus on cybersecurity. [1] It said hacking attempts against electronic data repositories posed a threat to inadequately protected records. [1] In our reading, the link is direct. An attacker who gains administrative access to an alterable archive can change or delete records. A WORM store limits what that access can do.
That gives security teams a reason to care about records rules. The same control serves two purposes: regulatory preservation and protection against tampering. A security architecture that already separates administrative roles and protects backups can extend those practices to required records.
Separating administrators
Software-based WORM works only if no one can switch it off. The 2003 release described qualifying systems as ones whose integrated codes could not be turned off. [2] In a modern platform, that translates into controls over who can change retention settings and storage policies.
A practical design keeps the people who administer the storage platform apart from the people who can change retention rules, and logs every change to either. An attacker or insider who controls one role should not control the other. This is ordinary privileged-access practice applied to a records system.
Ransomware and preserved records
A records store that cannot be altered also resists encryption by an attacker, because the attacker cannot overwrite the protected data. In our reading, that makes a compliant records store a candidate recovery source after an attack, for the records it holds. It does not replace a firm’s backups, because it holds only required records and their indexes.
That dual use gives the records program and the resilience program a shared interest. The resilience team may want to know which data is held in locked storage. The records team benefits from the resilience team’s monitoring of the storage platform.
What WORM does not do
WORM prevents changes after a record is written. It does not ensure the record was correct when written, or that it was written at all. The archive’s settings cannot protect a trade record that does not reach the archive. That is why the inventory comes first.
WORM also does not make records easy to use. The SEC’s 2022 release recorded one commenter’s statement that WORM records were not easily searchable and that examiners typically requested data pulls from the original systems instead. [3] Another commenter described moving records from its business systems into a WORM-compliant system that was less user friendly. [3] In our reading, keeping records in two places created its own reconciliation problem.
The proof: procedures and supervision
Supervisory deficiencies
FINRA found that each firm had procedural and supervisory deficiencies related to preserving electronic records. [1] That finding is separate from the storage failures. It says the firms’ own controls did not catch the problem.
Supervision in this setting means written procedures that say who checks preservation, how and how often, and evidence that the checks happened. A firm that had such procedures and followed them would have had a chance to find its gaps before FINRA did.
The notice and the undertaking
Before 2022, Rule 17a-4 required a broker-dealer to notify its designated examining authority before employing an electronic recordkeeping system. [3] It also required the third-party undertaking described above. [3] Those filings created a record of what the firm said it would do.
In our reading, the notice also set a trap. A firm that filed for one system and later added another holding required records might not have filed again. The notice described the firm’s intent at one moment. The inventory described its reality over time.
What examiners can ask for
The release said these records are a primary means by which regulators examine for misconduct, and it repeated the SEC’s 2003 statement about books and records. [1] [2] The proof a firm can offer an examiner is concrete: the inventory, the configuration of each system, test results, the procedures and evidence of review.
A firm that can produce those quickly shows control. A firm that has to search for them shows the gap the December 2016 findings described.
The current rule states the production side plainly. A broker-dealer must be able to download and transfer copies of a record, and the information needed to locate it, as the SEC, its self-regulatory organizations or a state securities regulator require. [5] Speed of production is part of the proof. A record that is preserved but cannot be found and exported on request is of limited use to an examiner.
Testing cadence and evidence
A preservation test should run at set intervals and after each major change to a system. The test is simple to describe: attempt to modify a record, attempt to delete it, and record that both attempts failed. A second check confirms that the record can be exported with its index. [2]
The evidence of each test matters as much as the result. A dated log or screenshot, kept with the procedures, shows an examiner that supervision happened. A test that leaves no record leaves the firm unable to show it was done.
Internal audit’s role
Internal audit can test the chain end to end. It can pick a sample of required records, trace each to its system, check the system’s configuration and attempt alteration in a controlled way. Findings go back to the owners named in the procedures.
That independent check is well placed to find a system missing from the inventory, because auditors start from transactions rather than from the list.
Reporting to senior management
The supervisory findings reached the firms’ procedures and supervision. [1] Senior management owns the supervisory system. A short periodic report to them, covering inventory coverage, test results and open gaps, puts the program where they can see it.
That report also creates a record that management was informed. If a gap is found later, the firm can show when it was known and what was done.
Who owns the proof
The proof crosses functions. Compliance owns the list of required records. Technology owns the systems and their configuration. Operations owns some of the processes that create records. Internal audit can test the whole chain. Each has a part, and the procedure has to name each part.
A single owner for the whole chain, such as a records officer with authority across functions, can hold the parts together. Without one, each function can believe another is responsible.
How the issue reaches different firms
Large broker-dealers
Large firms tend to run more systems across business lines than small ones, which raises the inventory burden. The release’s description of deficiencies affecting hundreds of millions of records in some cases reflects that scale. [1] For these firms, the inventory has to be automated where possible, with new systems flagged at procurement.
Large firms also have more change. Platform migrations, cloud moves and acquisitions each reopen the inventory. A large firm’s records program needs a seat in architecture review, so that a design that creates or moves required records is caught before it is built rather than after an examination.
Smaller broker-dealers
Smaller firms may run fewer systems and rely more on vendor-hosted ones. Their inventory may be shorter, but their dependence on vendors can be greater. The undertaking and the vendor’s configuration become the main controls. [3] A small firm’s compliance officer may be the only person who knows which vendor systems hold required records.
That concentration is a risk of its own. A written inventory, kept where a successor can find it, protects the firm when that person leaves. Vendor contracts that state how records are preserved and exported, and that give the firm testing or attestation rights, make the vendor’s controls part of the firm’s evidence.
Broker-dealers inside banking groups
Broker-dealers affiliated with banks are subject to Rule 17a-4 for their broker-dealer records. [2] They may share systems with the bank, such as a general ledger or a data platform. A shared system that holds broker-dealer records needs to meet the broker-dealer’s requirements for those records, whatever the bank’s own records rules require. Counsel can confirm how the rules apply to shared infrastructure.
Introducing and clearing arrangements
Some broker-dealers rely on other firms to prepare or maintain records for them. The 2022 release described the long-standing requirement that a third party who prepares or maintains a broker-dealer’s regulatory records file a written undertaking, whether the records are on paper or electronic. [3] The undertaking includes permitting examination and furnishing copies. [3]
For a firm that relies on another to keep its records, the inventory has to include the other firm’s systems. The obligation stays with the broker-dealer. Its procedures should show how it confirms the other firm’s preservation, through reports, attestations or testing rights.
Firms that are not broker-dealers
Rule 17a-4 applies to exchange members, brokers and dealers, as its title states. [5] It does not apply to banks, credit unions or investment advisers as such. Those firms have their own recordkeeping rules. The inventory method in this article still applies to them, but the storage requirements differ, and they should not assume WORM is required of them.
Objections, in order
1. These were storage misconfigurations, not compliance failures
FINRA paired the storage findings with procedural and supervisory deficiencies. [1] The storage problem lasted for prolonged periods in most cases. [1] A configuration error that a firm’s own supervision does not find is a compliance failure.
2. No records were actually altered
FINRA’s release did not say records were altered. It said records were kept in a format that did not prevent alteration. [1] The rule required the format. [2] The point of WORM is that a firm can show records were not altered, which an alterable format cannot do.
3. The fines were small relative to the firms
The release reports the amounts; whether they were large or small is a judgment. [1] The remediation cost, the inventory, the migration to compliant storage and the new procedures, falls on the firm whatever the fine. The fines made the requirement visible across the industry.
4. WORM was an outdated technology mandate
Commenters on the SEC’s later proposal made a version of this point, and a 2017 trade association petition asked for a principles-based approach. [3] The SEC responded in 2022 by adding an audit-trail alternative, not by dropping the requirement. [3] In December 2016, WORM was the rule.
5. Examiners do not use WORM copies anyway
The SEC’s 2022 release recorded a commenter’s statement that examiners typically request data pulls from original systems. [3] That speaks to usability. It does not remove the need to show that preserved records are complete and unaltered when a dispute arises.
6. The rule has changed, so the case is history
The 2022 amendments changed how a firm can meet the requirement. [3] [5] They did not change the need to know which systems hold required records. The four parts in this article apply under either option.
7. Cloud storage solves the problem
Cloud storage services can offer retention locks. The firm still has to configure them, apply them to the right data and confirm they meet the rule. [2] [5] The 2022 release addressed how cloud providers give undertakings, which shows the SEC treated the arrangement as one to document rather than assume. [3]
8. Keeping two copies creates its own risk
Firms that keep records in a working system and a WORM archive have two versions to reconcile. A commenter on the 2021 proposal described transferring records from its native business systems into a WORM-compliant system because those systems did not meet the WORM standard. [3] The audit-trail option adopted in 2022 lets a firm meet the requirement in the working system, if that system keeps the required audit trail. [3] [5] In December 2016, the option did not exist.
What technology and compliance leaders could check
The four parts give a short list of checks:
- Keep a written list of required record types, mapped to the rule provision and retention period, approved by compliance.
- Keep an inventory of every system that creates or holds those records, with an owner for each.
- Add a records question to the change and procurement processes for new systems and migrations.
- For each system, record how preservation is achieved and test it by attempting to alter and delete a record.
- Check that each system can export records and their indexes in a usable form.
- Confirm vendor-hosted systems fit the current undertaking and access requirements.
- Write supervisory procedures naming who reviews preservation, how often, and where the evidence is kept.
Where to start
Start with the inventory. A firm that cannot list where its required records live cannot show they are preserved. The release’s phrase, multiple systems and categories of records, is the reason. [1] Build the list from both directions: from the record types down to systems, and from the system catalog up to record types.
Then test. A test that attempts to delete a record and fails, with a screenshot or log, is better evidence than a configuration document. Repeat the test after each major change.
Then write the procedures around what the inventory and tests show. Procedures that name systems, owners and test intervals are easier to follow and easier to examine than procedures that restate the rule.
Sequencing the work
The work has a natural order. First the records list, because nothing else can be checked without it. Then the inventory, built from both directions. Then the protection review and tests, system by system, starting with the systems that hold the highest volumes of required records. Then the procedures, written around the inventory.
Each stage produces a document that the next stage uses. A firm that starts with the procedures and leaves the inventory for later will write procedures about systems it has not listed.
Measures that show control
Four measures give leaders a view of the program. The share of systems in the catalog that have been reviewed for required records. The share of inventory systems tested in the last cycle. The number of open gaps and their age. The number of new systems that went live without a records review.
Each measure comes from records the program already keeps. Reported to a compliance committee each quarter, they show whether the inventory is current and the tests are happening. A rising count of systems launched without review is the early warning FINRA’s findings suggest firms lacked. [1]
What the checks will not do
These checks do not settle every question about which outputs are required records. Those are legal determinations. They make sure that, once the determination is made, the firm can find the records and show they are protected.
With hindsight
FINRA’s December 2016 matters were followed by a long rulemaking on how firms may preserve records. The SEC’s 2022 release recounted that a group of trade associations filed a petition on November 14, 2017, asking the Commission to replace the WORM requirement with principles-based requirements. [3] The petition pointed to the Commodity Futures Trading Commission’s 2017 amendments to its own recordkeeping rule. [3]
The SEC proposed amendments in a release published December 1, 2021, and adopted them in Release No. 34-96034, dated October 12, 2022. [3] The final rule was published on November 3, 2022, and took effect on January 3, 2023. [3] The compliance date for the amendments to Rule 17a-4 was May 3, 2023. [3]
The central change was an audit-trail alternative. As the SEC described it, a broker-dealer could use a system that preserves records in a manner that permits the re-creation of an original record if it is modified or deleted. [3] The current rule text requires a complete time-stamped audit trail of all modifications and deletions, their date and time, and, if applicable, who made them. [5] WORM remains the other option. [5]
The amendments made further changes. They removed the requirement to notify the designated examining authority before using an electronic recordkeeping system. [3] They let a designated executive officer give the undertakings in place of a third party. [3] They added an alternative undertaking for providers, such as cloud services, that hold records the broker-dealer can access independently. [3]
The current rule also requires a backup electronic recordkeeping system or other redundancy capabilities designed to ensure access to required records. [5] It requires the capacity to download records and audit trails in human readable and reasonably usable electronic formats. [5]
A 2022 enforcement case turned on records that never reached any archive. On September 27, 2022, the SEC charged 15 broker-dealers and one affiliated investment adviser with failures to maintain and preserve electronic communications. [4] The firms admitted the facts in their orders and agreed to combined penalties of more than $1.1 billion. [4]
The SEC said its investigation found that from January 2018 through September 2021, firm employees routinely communicated about business on text messaging applications on personal devices. [4] It said the firms did not maintain or preserve the substantial majority of those communications. [4] In our reading, this was the inventory problem of 2016 in a new form: required records held in systems the firm did not control.
The 2022 changes also moved who signs. A designated executive officer may now give the undertakings, with up to two designated officers and three specialists to help, according to the SEC’s description. [3] That puts a named member of senior management on the record for access to the firm’s electronic records.
What held up from December 2016 is the sequence. Firms still have to know which records they must keep and where those records live before any storage choice matters. [1] [5] What changed is the protection step, where the audit-trail option gives firms a second way to show records were not altered. [3] [5] As checked on November 15, 2026, the current text of Rule 17a-4(f) offers both options. [5]
Spotted an error? Tell us and we will check it and correct the article where needed.