Cloud Migration Under Rule 17a-4 and a Rule 8210 Request
Trexler Financial, a three-branch broker-dealer, is migrating its email, order tickets, blotters, customer account records and general ledger to a cloud vendor. The vendor's system allows any administrator to overwrite or delete a record, stores a single copy, and offers no third-party download capability. Trexler plans to shut down its legacy archive, which was non-rewritable and non-erasable, and rely on a global three-year retention setting. In August, FINRA staff serve a Rule 8210 request for all email from a former registered representative's account for a four-year-old period. The representative left in March and was named in a customer arbitration filed in July.
1. Which parts of the retention plan fail Rule 17a-4, and why?
Read the worked answer
Retention periods. A blanket three-year setting is wrong. Minimums: blotters, general ledger and customer account records - six years (account records for six years after the account closes); order tickets and correspondence - three years; the first two years must be kept in an easily accessible place. Records supporting the FOCUS report and the net capital and reserve computations - six years.
Format. Rule 17a-4(f) requires records be preserved in a non-rewritable, non-erasable format, or, under the audit-trail alternative, that the system verify the quality and completeness of the recording, serialize records, time and date stamp them, prevent alteration of the original, maintain a duplicate copy, and provide a third-party downloader. Administrator overwrite and delete rights, a single copy, and no downloader fail both routes.
Process. The firm must give notice to FINRA before relying on the audit-trail alternative, and must be able to produce the records on demand.
2. How should the firm respond to the Rule 8210 request, and what effect does the arbitration have?
Read the worked answer
Produce the records within the time FINRA specifies. A Rule 8210 request is enforceable; failure to comply is an independent violation, separate from any recordkeeping failure, and can be charged even where the underlying conduct was minor.
The arbitration filed in July, and the 8210 request itself, trigger a preservation obligation. A litigation hold suspends routine destruction of the former representative's emails, notes, order tickets and account records - including material already past its six-year period if it is relevant to the matter. Practical steps: image or copy the rep's mailbox and files before the migration touches them; send the hold notice to the vendor in writing; confirm in writing that the vendor will not overwrite or expire those records; restore from the legacy archive anything already moved. Do not let the migration's retention setting quietly delete responsive material.
3. What must the firm do before and during the migration, and who owns the fix?
Read the worked answer
Freeze the cutover: do not decommission the compliant legacy archive until the replacement is verified against Rule 17a-4(f).
- Obtain vendor representations and an independent audit report (SOC 1 or 2) covering non-rewritability or the audit-trail elements, including the third-party downloader.
- Reconfigure retention by record class (six years, first two accessible; account records six years post-closing) and implement legal holds that override expiry.
- Update the records-retention schedule and the recordkeeping written supervisory procedures; train branch staff on what may and may not be deleted.
- Notify FINRA, and self-report any records already lost, with the categories and dates affected.
The financial and operations principal owns the review. The firm's periodic reports and supervisory certifications rest on the assumption that the records exist and can be retrieved; a vendor contract is not a substitute for that verification.