Books and Records: Electronic Retention Under Rule 17a-4 and Rule 204-2

In plain language

Regulators do not just require you to keep records. They require you to keep them in a form that cannot be quietly changed, to produce them quickly when asked, and to capture business communications wherever they happen — including on the messaging app someone uses because it is convenient. Most firms fail this on the last point, not the first.

Two rules, two populations

Broker-dealers and investment advisers are under different recordkeeping rules that ask similar operational questions.

Broker-dealers. 17 CFR 240.17a-3 says what records to make; 17 CFR 240.17a-4 says how long to keep them and what an electronic recordkeeping system must do. FINRA layers Rule 4511 on top, which requires members to make and preserve books and records as required by FINRA rules, the Exchange Act, and its rules, and to preserve records with no specified period for at least six years.

Investment advisers. 17 CFR 275.204-2 covers both what to keep and how long. The general period is five years from the end of the fiscal year in which the last entry was made, with the first two years in an appropriate office of the adviser — a phrase that predates cloud storage and is usually satisfied today by immediate accessibility rather than physical location.

Dually registered firms answer to both. The practical approach is to configure to the longer period per category rather than maintaining two parallel schedules.

The 2022 change to 17a-4: WORM is no longer the only way

For years, “17a-4 compliant” was shorthand for write-once-read-many storage. The SEC’s 2022 amendments to the electronic recordkeeping rules (Release 34-96034) added an alternative. An electronic recordkeeping system may now either:

  • preserve records in a non-rewriteable, non-erasable format — the traditional WORM approach; or
  • maintain an audit trail that permits the recreation of an original record if it is altered or erased.

This matters because it made mainstream cloud platforms viable for records that previously needed specialised storage. It did not make the requirements lighter. Whichever option a firm relies on, the surrounding conditions still apply: the system must serialise and index records, verify the quality and accuracy of the recording process, permit downloading of indexes and records in a readable form, and the firm must have the required undertakings in place from whoever can access the system.

The operational consequence is that a firm should be able to answer, in one sentence, which option it relies on. Firms that cannot answer usually discover that they assumed their platform’s default was one thing when it is the other.

Off-channel communications is where firms actually fail

The recordkeeping enforcement wave of recent years was not about storage technology. It was about communications that never reached the archive because they happened on personal devices and consumer messaging apps. The records were required; the systems captured email; the business happened in text messages.

The control has three parts, and all three are necessary:

  1. A stated list of approved channels. Specific applications, not “firm-approved systems.”
  2. Technical capture on each approved channel. Journaling at the server, so a user deleting a message on their phone does not remove the record.
  3. Enforcement against the rest. On managed devices, unapproved messaging applications are blocked or absent. A policy that says employees should not use them is not a control; it is a statement of preference.

The third part is the one firms skip, and it is the one that turns a policy violation by one person into a firm-level recordkeeping failure.

Prompt production

Rule 17a-4(j) requires a member, broker, or dealer to furnish promptly to a representative of the Commission legible, true, complete, and current copies of required records. Advisers face the equivalent expectation through examination requests.

Production is a capability, not a storage property, and it is tested the way an examiner would test it: name a person and a date range, and retrieve. Two failure modes recur.

  • Search does not span the whole corpus. Email is searchable; the chat archive is a separate product with its own console; the mobile capture is a third. A “complete” response requires three separate exercises and someone forgets one.
  • Only an administrator can run the search. The compliance user who receives the request has to route it through IT, which adds days and puts the record custodian outside the compliance function.

What to check before an exam

  • Which 17a-4 option does the archive rely on, and can you show it?
  • Can a compliance user search and export without an administrator?
  • Does the channel inventory have any entry that is neither captured nor blocked?
  • What happens to a departed employee’s messages — and to the mobile device they used?
  • Does a legal hold actually stop deletion, tested rather than assumed?

FINRA supervision and cybersecurity for the supervisory review that depends on captured communications, Advisers Act compliance for the 204-2(a)(17) record of the compliance program itself, and incident response and exam evidence for assembling a production under time pressure.

Pylon’s service view is on SEC & FINRA compliance.

Primary sources

Frequently Asked Questions

Is WORM storage still required under Rule 17a-4?

It is no longer the only option. The SEC's 2022 amendments added an audit-trail alternative: an electronic recordkeeping system may either preserve records in a non-rewriteable, non-erasable format, or maintain an audit trail that recreates an original record if it is altered or deleted. A firm picks one and has to meet that option's full conditions, including the notification and undertaking requirements.

How long do investment advisers have to keep records?

Rule 204-2 generally requires records to be kept for five years from the end of the fiscal year in which the last entry was made, with the first two years in an appropriate office of the adviser. Some categories, such as certain organizational records, run longer. Read the rule for the category you are asking about rather than applying five years to everything.

Do text messages have to be archived?

If a message is a business communication that falls within a required record category, the medium does not exempt it. That is the substance of the off-channel communications enforcement actions: the records existed, the firms' systems did not capture them, and supervision could not review what was never captured. The control is a stated policy about approved channels plus technical capture on those channels.

What does prompt production actually mean?

It means being able to hand over a readable, complete set of responsive records on request without rebuilding a system to do it. In practice examiners test it by asking for a specific date range or a specific person's communications, so the search itself — not just the storage — has to work.

Scheduled actions

The recurring work this section implies. Each action carries a stable action-id so it can be tracked in a compliance calendar and rolled up on all scheduled actions.

Review the retention schedule against the record categories the firm actually generates, and confirm each category maps to a system with the correct retention period.

Cadence:
Annually
Owner archetype:
CCO, IT
action-id:
act.books-records.retention-schedule-review

Run a production test: pick a person and a date range, retrieve the responsive communications, and time it. Record the result including anything that could not be retrieved.

Cadence:
Quarterly
Owner archetype:
CCO, MSP
action-id:
act.books-records.production-test

Re-inventory the communication channels in use — email, chat, SMS, collaboration tools, social — and confirm each is either captured or prohibited, with the prohibition enforced somewhere other than a policy document.

Cadence:
Quarterly
Owner archetype:
CCO, IT, MSP
action-id:
act.books-records.channel-inventory

Reconcile the archive against the mail and messaging systems for a sample period to confirm nothing is being dropped in transit.

Cadence:
Quarterly
Owner archetype:
IT, MSP
action-id:
act.books-records.archive-completeness-check

When someone joins or leaves, confirm their communications are brought into or preserved within the archive, including mobile devices used for business.

Cadence:
On change
Owner archetype:
IT, MSP
action-id:
act.books-records.onboarding-offboarding-capture

Confirm a legal hold can be applied and will actually suspend deletion, by testing it on a sample account rather than by reading the vendor's documentation.

Cadence:
Annually
Owner archetype:
CCO, IT
action-id:
act.books-records.legal-hold-drill

Configuration touchpoints

Where this section lands in a real environment. Each touchpoint is stated as a plain configuration rule — not a vendor setting — and carries a stable config-id.

Configuration ruleApplies toconfig-id
Each record category's retention period is configured in the system that holds it, rather than relying on nobody deleting anything.Archive, mail platform, document managementcfg.books-records.retention-period-set
The archive either prevents alteration and deletion outright or maintains an audit trail that would reconstruct an altered or deleted record, and the firm knows which of the two it relies on.Archive platform configurationcfg.books-records.immutability-or-audit-trail
Mail and messaging platforms journal to the archive at the server, so a user cannot prevent capture by deleting a message.Mail platform, collaboration platformcfg.books-records.journaling-enabled
Unapproved messaging channels are blocked or unavailable on firm-managed devices, not merely discouraged in the employee handbook.Mobile device management, endpoint policycfg.books-records.approved-channels-enforced
A compliance user can search the archive by person and date range and export results without administrator help.Archive access rolescfg.books-records.search-and-export
A legal hold overrides the retention schedule and suspends automated deletion for the accounts it covers.Archive retention policycfg.books-records.deletion-suspension

More in the Compliance Library

Rollups: all scheduled actions and monitor and review.

Author
Rachel Lannon and Byron Foley
Reviewed by
Tim Quinn
Last updated

This is operational technology guidance for regulated firms, not legal advice. Confirm how each requirement applies to your firm with your compliance counsel.