Rule 17a-3
The SEC rule requiring registered broker-dealers to create and maintain current books and records for every securities transaction - including the blotter, general ledger, customer account ledgers, order tickets, and net capital computation.
Definition
What is Rule 17a-3?
Rule 17a-3, Records to Be Made by Certain Exchange Members, Brokers and Dealers, is the SEC rule that defines the core books and records every registered broker-dealer must create and maintain as current — including the blotter, general ledger, customer account ledgers, order tickets, and net capital computation. Rule 17a-3 governs the creation side of the broker-dealer recordkeeping obligation. Its companion, Rule 17a-4, governs the preservation side: how long each record must be retained, in what format, and with what retrieval capability. If Rule 17a-3 is the obligation to write down every transaction, Rule 17a-4 is the obligation to store what was written in a tamper-evident, retrievable form — typically WORM-compliant archival storage — for a defined period, generally three to six years. The 2023 SEC Recordkeeping Rule amendments reinforced that firms must maintain the technology to produce these records in a readily readable format on examination request, a standard that applies equally to records created in digital asset and on-chain settlement environments.
The obligation runs broadly. Rule 17a-3 applies to every registered broker-dealer, every member of a national securities exchange that transacts securities business directly with non-members, and every security-based swap dealer that is also a registered broker-dealer. The SEC's enforcement position is consistent across instrument types: digital asset transactions, USDC-denominated settlements, and on-chain deliveries trigger Rule 17a-3 requirements the same way traditional securities transactions do. The nature of the settlement rail does not change the recordkeeping obligation; it changes the complexity of satisfying it.
Why Rule 17a-3 matters for broker-dealer operations
Rule 17a-3 compliance is the foundation of every broker-dealer examination. FINRA examiners use the required records to reconstruct individual trades — tracing from the order ticket through the blotter entry to the customer ledger and the general ledger impact. Records that cannot be produced in this sequence signal a breakdown in operational controls. Beyond examination readiness, the required records support trade surveillance (detecting unusual patterns across blotter entries), capital monitoring (the general ledger feeds the net capital computation under Rule 15c3-1), customer protection (the customer account ledger underpins the reserve formula under Rule 15c3-3), and regulatory reporting. FINRA recordkeeping violations are among the most common enforcement actions against broker-dealers, and digital asset operations have emerged as a new concentration of Rule 17a-3 examination findings — particularly failures at the blotter level where on-chain data is logged without the counterparty identity enrichment the rule requires.
The blotter — the foundational record of original entry
The most important record under Rule 17a-3 is the blotter, defined under Rule 17a-3(a)(1) as the record of original entry — the itemized daily record of every purchase and sale of securities, every receipt and delivery, every cash receipt and disbursement, and every other debit and credit at the firm. All other required records — customer ledgers, securities records, confirmations — trace back to the blotter as the source document.
The required fields are specific: the account for which the transaction was effected, the name and amount of the security, the unit and aggregate purchase or sale price, the trade date, and the name or other designation of the person from whom the security was purchased or to whom it was delivered. For security-based swaps, the rule adds the date and time of execution and the unique transaction identifier. The blotter must be posted no later than the first business day following the transaction.
The counterparty identity requirement is the most consequential element for digital asset compliance. A blockchain transaction records sending and receiving wallet addresses — but wallet addresses are not counterparty identities. A Rule 17a-3(a)(1) compliant blotter entry for a digital asset transaction requires the legal identity of the counterparty, derived from the firm's KYC records and order management system and linked to the on-chain event. This is the address attribution requirement: the firm must maintain a verified mapping from each on-chain wallet address to the corresponding legal entity identifier (LEI) or KYC-verified counterparty name. The transaction hash is a supporting reference; it is not the record. SEC staff guidance and enforcement actions have consistently emphasized that a transaction hash alone does not satisfy Rule 17a-3(a)(1) blotter requirements — firms that log only on-chain events without the required enrichment fields have Rule 17a-3(a)(1) deficiencies regardless of how complete their blockchain data is. FINRA examiners approach this directly: they will select a trade from the blockchain and ask the firm to produce the corresponding blotter entry. If the firm cannot link the on-chain transaction to a compliant record showing counterparty identity, price, and account designation, that is an examination deficiency.
The general ledger and net capital compliance
Rule 17a-3(a)(2) requires broker-dealers to maintain ledgers reflecting all assets and liabilities, income and expense, and capital accounts — the general ledger of the firm. All registered broker-dealers must use the accrual method of accounting to ensure proper matching of revenues and expenses and an accurate reflection of financial condition. The specific current standard for the general ledger is functional rather than calendar-fixed: it must be maintained in a form that facilitates posting as frequently as necessary to ascertain compliance with Rule 15c3-1 (the Net Capital Rule) and Rule 15c3-3 (the Customer Protection Rule). If the general ledger is not current enough to support a net capital calculation on demand, the firm is in deficiency on Rule 17a-3(a)(2).
For USDC-denominated settlements, the general ledger entry benefits from what practitioners call accounting neutrality. USDC is designed to maintain a 1:1 dollar peg through reserves primarily composed of short-term Treasury obligations and cash equivalents — it does not produce the unrealized gain/loss noise that volatile crypto assets or foreign fiat settlements create on the general ledger. A USDC settlement amount is the USD amount: the general ledger entry maps directly from the on-chain confirmation without currency conversion, mark-to-market adjustment, or the accrual complexity of cross-currency settlement. This accounting neutrality means that the blotter entry and the general ledger entry match exactly — reducing reconciliation breaks during FINRA examination of USDC-settled trades and simplifying Rule 17a-3(a)(2) general ledger maintenance compared to cross-border or volatile-asset equivalents.
Memoranda of brokerage orders
Rule 17a-3(a)(6) requires the maintenance of memoranda of brokerage orders — order tickets — that must be prepared at the time of the transaction, not by the following business day. The order ticket must show the account for which the order was entered, whether the order was a buy or sell, the security, the amount, the price or the basis for price determination, the time the order was received, and the time of execution. The contemporaneous requirement is the critical distinction from the blotter's T+1 posting window: the ticket must exist as a record created at the moment of order placement and execution, not as a reconstruction created in an overnight batch. For digital asset orders, the OMS must generate the order ticket at the moment the order is placed and stamp it with the execution time at the moment the trade executes on-chain.
Trial balance and net capital computation
Rule 17a-3(a)(11) requires the periodic computation and maintenance of trial balances and the net capital computation required under Rule 15c3-1. These records must be prepared within 10 business days after the end of each accounting period. The trial balance confirms the general ledger is in balance; the net capital computation confirms the firm meets its minimum capital requirement. Both records flow from the general ledger maintained under Rule 17a-3(a)(2) — which is why the functional current standard for the general ledger is framed around net capital compliance. The trial balance also links directly to the broker-dealer net capital rule obligations: the periodic computation is the firm's own verification that its capital position satisfies the regulatory minimum.
Digital asset records and the enrichment requirement
Digital asset transactions create a structural gap between the on-chain data produced by settlement and the data required by Rule 17a-3. A blockchain confirms the transaction, the wallet addresses, the asset transferred, the amount, and the block timestamp. It does not confirm the legal identity of the counterparty, the agreed trade price in cases where the OTC negotiated price differs from the on-chain settlement amount, or the account designation required by the blotter. Deterministic enrichment — automatically linking each on-chain wallet address to a verified legal entity identifier or KYC-confirmed counterparty name, and appending price, account, and authorization data from the OMS — is the required step between blockchain confirmation and Rule 17a-3 compliance. Address attribution is the foundation of this process: without a verified wallet-address-to-legal-identity mapping, no on-chain settlement event can be converted into a compliant Rule 17a-3(a)(1) blotter entry.
Compliance alert: Firms operating on T+0 digital settlement rails using T+1 legacy recordkeeping systems face an inherent risk of Rule 17a-3(a)(6) deficiencies. The order ticket requirement is contemporaneous — prepared at the time of the transaction. A batch system that reconstructs order tickets at 23:00 for trades executed throughout the day does not produce contemporaneous records. In a T+0 settlement environment, this gap is not hours but potentially spans multiple settlement cycles within the same business day.
The make-and-keep-current standard compounds this requirement across the full record set. T+0 settlement on-chain can confirm in seconds; the order ticket requirement is preparation at the time of the transaction. Recordkeeping systems designed for T+1 settlement need to be re-examined for adequacy in T+0 environments. The digital asset recordkeeping infrastructure must operate at settlement speed, not at batch-processing speed.
Rule 17a-3 required records — what each captures and when it must be current
| Record Type | Rule Subpart | What It Captures | Current Deadline |
|---|---|---|---|
| Blotter (record of original entry) | 17a-3(a)(1) | Every purchase, sale, receipt, delivery, and cash movement — with counterparty identity, price, trade date, and account | Posted by T+1 business day |
| General ledger | 17a-3(a)(2) | All assets, liabilities, income, expense, and capital accounts — accrual basis | As frequently as needed for net capital compliance |
| Customer account ledger | 17a-3(a)(3) | All purchases, sales, receipts, and deliveries per individual customer account | Posted by T+1 business day |
| Memoranda of brokerage orders | 17a-3(a)(6) | Order tickets — time received, price, account, direction, time of execution | Prepared at time of transaction |
| Trial balance and net capital | 17a-3(a)(11) | Balance sheet positions and net capital computation under Rule 15c3-1 | Within 10 business days of accounting period end |
Rule 17a-3 — records creation workflow
Devancore Glossary · devancore.com
Rule 17a-3 — records creation workflow
Devancore Glossary · devancore.com
How it works
1. Order placement — memoranda of brokerage orders created
At the moment a trade order is placed, Rule 17a-3(a)(6) requires preparation of the memorandum of brokerage orders — the order ticket — contemporaneously with the order. For digital asset orders, the OMS must generate the order ticket at the moment of order entry, capturing the account designation, the digital asset, the order direction, the amount, the agreed price or basis for pricing, and the timestamp of order receipt. At execution, the ticket is stamped with the execution time and price. The order ticket cannot be created after the fact as a batch reconstruction — it must exist as a contemporaneous record of the order at the moment it is placed and filled.
2. Trade execution — blotter entry enriched and posted
After execution, the blotter entry under Rule 17a-3(a)(1) is prepared. For traditional securities, the blotter must be posted by T+1 business day. For digital asset trades settling on-chain, the enrichment workflow runs immediately: the on-chain event (transaction hash, asset, amount, wallet addresses, block timestamp) is linked to the OMS trade record, and the required fields — counterparty legal identity from KYC records, agreed price from the OMS, account designation from the account system — are appended to the blockchain data. The enriched record is posted to the blotter with the transaction hash as a supporting reference field, not as the primary record. A blotter entry showing only the transaction hash, without counterparty identity and price, does not satisfy Rule 17a-3(a)(1).
3. General ledger updated — net capital impact captured
The general ledger under Rule 17a-3(a)(2) is updated with the trade's financial impact using the accrual method of accounting. For broker-dealers computing net capital daily or on demand, the general ledger must be current enough to support the computation at any point during the business day. For USDC-denominated trades, the general ledger entry maps directly from the on-chain settlement confirmation — the USDC amount is the USD amount, with no FX conversion required. For traditional securities settled through DTC, the ledger reflects the accrual impact of the trade from trade date, with the settlement-date cash movement updated on settlement.
4. Customer account ledger updated
Rule 17a-3(a)(3) requires a separate ledger entry for each customer account, reflecting all purchases, sales, receipts, and deliveries for that account. The customer account ledger is the per-account record that supports both the reserve formula calculation under Rule 15c3-3 and the client's account statement. For digital asset accounts, the customer ledger reflects the post-settlement position, linked to the on-chain wallet address and the blotter entry establishing the transaction record. The customer account ledger must be posted by T+1 business day.
5. Securities record updated — position reconciliation
Rule 17a-3(a)(5) requires maintenance of the securities record — the firm's position record showing long and short positions by security as of the clearance date. For traditional securities, the securities record reconciles against the DTC participant account balance. For digital assets, the securities record reconciles against the custodied wallet balance for each on-chain address. Position differences between the securities record and the custodian record constitute a possession and control deficit under Rule 15c3-3 that must be resolved within one business day. The securities record must be posted by T+1 business day.
6. Trial balance and net capital computation
Within 10 business days after the end of each accounting period, Rule 17a-3(a)(11) requires computation and maintenance of the trial balance and net capital figure. The trial balance confirms the general ledger is in balance — every debit entry has a matching credit, every position is accounted for, every customer obligation is captured. The net capital computation confirms the firm meets its minimum capital requirement under Rule 15c3-1. Both records are produced from the general ledger maintained under Rule 17a-3(a)(2), which is why the functional current standard for the general ledger is tied directly to net capital compliance: the ledger must be current enough to support the computation whenever it is needed, not just at the periodic reporting deadline.
Digital asset trade — 17a-3 enrichment requirement
Devancore Glossary · devancore.com
Digital asset trade — 17a-3 enrichment requirement
Devancore Glossary · devancore.com
In Devancore™
Devancore recordkeeping engine — Rule 17a-3 compliance
Devancore Glossary · devancore.com
Devancore's recordkeeping engine is built on the principle that blockchain finality is the beginning of the compliance workflow, not the end. On-chain settlement confirmation is the input; a Rule 17a-3 compliant record — with counterparty identity, price, account designation, and authorization chain — is the output. The enrichment layer between the two is where the compliance gap exists, and where Devancore operates.
Unified blotter — deterministic enrichment from on-chain event to 17a-3(a)(1) record
When a trade settles on the digital rail — on the Arc Network, Ethereum, or another settlement layer — Devancore ingests the on-chain event and initiates the deterministic enrichment workflow immediately. The blockchain event provides the asset, amount, wallet addresses, block timestamp, and transaction hash. Devancore's address attribution layer resolves each wallet address against the firm's verified KYC database, producing the legal entity identifier (LEI) or KYC-confirmed counterparty name required by Rule 17a-3(a)(1). The system then appends the agreed trade price from the OMS and the account designation from the account record system — converting the pseudonymous on-chain event into a fully enriched, examination-ready blotter entry. The enriched record is posted to the blotter in real time: when a trade settles in milliseconds on the Arc Network, the blotter entry is prepared in the same settlement cycle, not in an overnight batch. For USDC-denominated settlements, accounting neutrality applies — USDC's 1:1 dollar peg means the settlement amount maps directly to the USD blotter entry without FX adjustment or mark-to-market noise, providing the clean audit trail that makes FINRA examination of stablecoin-settled trades substantially simpler than cross-currency equivalents. The transaction hash is preserved as a supporting reference field in the blotter record, providing the on-chain verification anchor alongside the compliance metadata that satisfies the full Rule 17a-3(a)(1) record requirement.
Automated general ledger — net capital ready
Devancore maps every settlement confirmation to the general ledger under Rule 17a-3(a)(2) using the accrual method, posting in real time rather than in overnight batch windows. For broker-dealers computing net capital daily — as required for firms meeting specified aggregate indebtedness thresholds — Devancore's real-time ledger ensures the net capital computation under Rule 15c3-1 is supportable at any point during the business day. The general ledger feed directly powers the Rule 15c3-3 reserve formula: free credit balances, unsettled amounts, and securities positions are maintained in real time, enabling the daily reserve computation to reflect current positions rather than T-1 batch data. When the trading day ends, the trial balance under Rule 17a-3(a)(11) is produced automatically from the real-time ledger, and the net capital computation is generated without a manual assembly step.
Audit-ready metadata — the complete authorization chain
For digital asset transactions, Devancore archives not just the transaction hash but the complete authorization chain: the maker-checker approval log confirming the trade was reviewed and authorized according to the firm's written supervisory procedures, the counterparty KYC record linking the wallet address to a verified legal identity, the OMS order ticket confirming time of order receipt and execution, and the enriched blotter entry showing all required Rule 17a-3(a)(1) fields. When a FINRA examiner requests the records supporting a specific on-chain transaction, Devancore produces a single export: the transaction hash, the enriched blotter entry, the contemporaneous order ticket, the customer ledger entry, and the maker-checker authorization log. This package satisfies the documentation expectation the SEC's Crypto Task Force has established for digital asset broker-dealer examination readiness — the on-chain event is fully traceable from blockchain confirmation through the firm's internal authorization controls to the regulatory record.
Real-time blotter for T+0 settlement environments
The make-and-keep-current standard of Rule 17a-3 requires recordkeeping infrastructure to operate at settlement speed in T+0 environments. Devancore's integration with digital settlement rails processes on-chain confirmation events and completes the enrichment workflow within the settlement cycle: when a trade settles in 350 milliseconds on the Arc Network, the order ticket is stamped at execution time, and the blotter entry is posted immediately — not in the next overnight batch. This eliminates the compliance gap that exists when T+0 settlement infrastructure is attached to T+1 recordkeeping systems. The firm's Rule 17a-3(a)(6) order tickets are contemporaneous; the Rule 17a-3(a)(1) blotter entries are current; the Rule 17a-3(a)(2) general ledger reflects positions as soon as the on-chain block is confirmed.