Devancore Inc.
Devancore Post-Trade Glossary
Glossary
RIA Trading Platform Post Trade
RIA trading platform post-trade is the adviser workflow that verifies model-driven trades after execution across client accounts, allocations, restrictions, custodian feeds, corrections, reconciliation, and audit evidence.
Document source: https://devancore.com/glossary/ria-trading-platform-post-trade/
Devancore Post-Trade Glossary
RIA Trading Platform Post Trade
RIA trading platform post-trade is the adviser workflow that verifies model-driven trades after execution across client accounts, allocations, restrictions, custodian feeds, corrections, reconciliation, and audit evidence.
Definition
RIA trading platform post-trade is the adviser workflow that verifies what happened after model-driven trading, rebalancing, order routing, or custodian execution. The term should be used carefully. The point is not generic RIA portfolio software. The point is the controlled operating record behind adviser trading workflows.
In an RIA setting, a single rebalance can create many account-level trades across households, sleeves, taxable accounts, retirement accounts, client restrictions, custodians, and cash needs. Post-trade control begins when the adviser needs to prove that the executed trades match the model intent, account instructions, restrictions, custodian records, and reconciliation outputs.
RIA post-trade record
RIA post-trade record
The adviser needs to prove how model intent became account-level trade evidence.
| Record area | What it tracks | Control question |
|---|---|---|
| Model intent | Model target, rebalance reason, household context, portfolio instruction, and account scope | Can the trade be traced to the model or adviser decision that created it? |
| Client account | Account number, registration type, sleeve, household, restriction, cash, tax-lot context, and custodian | Was the trade appropriate for the account-level instruction and restriction set? |
| Execution | Order, route, fill, price, quantity, trade date, settlement date, commission, and custodian execution record | Does the custodian record match the adviser trade record? |
| Allocation | Block, average price, account split, partial fill, correction, and approval history | Did each client account receive the intended allocation and economics? |
| Reconciliation | Custodian trade file, position feed, cash feed, internal blotter, and exception status | Which differences are timing items, breaks, corrections, or unresolved exceptions? |
| Evidence | Source files, comments, approval history, correction reasons, restriction review, and reporting references | Can an examiner or reviewer reconstruct the account-level workflow? |
Model intent matters because RIA trading is often generated from rebalancing logic. A trade should be traceable to a model target, portfolio instruction, household context, cash need, restriction review, tax-lot decision, or other adviser workflow input. If the trade cannot be tied back to its reason, the post-trade record is incomplete.
Account-level detail is the operating center. The same security may be bought for one client account, sold for another, restricted in a third, and avoided in a fourth because of tax or suitability context. A post-trade workflow should keep those account-level differences visible rather than collapse them into one aggregate trading result.
Custodian data gives external evidence. The adviser may send trade files, receive execution files, ingest position feeds, and reconcile cash and holdings against custodian records. The workflow should show whether the custodian record agrees with the adviser blotter and whether differences are timing items, breaks, corrections, or unresolved exceptions.
Allocation and correction controls are important because adviser workflows often involve block trading, average price allocation, partial fills, replacement trades, and account-level adjustments. A correction should carry reason, user, timestamp, approval status, and downstream impact.
Client restrictions and compliance evidence should remain attached to the event. Restrictions, do-not-buy lists, client preferences, account eligibility, cash constraints, and tax-lot context can affect whether a trade is acceptable for a specific account. Post-trade review should not require separate reconstruction from screenshots, files, and comments.
Reporting and billing depend on clean records. If trade data, cash, positions, and account-level holdings are wrong, client reporting and fee calculations may inherit the error. The post-trade workflow should make record quality visible before downstream outputs consume it.
RIA post-trade — model to account lineage
Devancore Glossary · devancore.com
How it works
RIA trading platform post-trade works by closing the loop between model intent and custodian-confirmed account state. The workflow starts with adviser trading intent and ends with reconciled records that can support client reporting, billing inputs, compliance review, and books-and-records evidence.
Adviser post-trade control flow
Adviser post-trade control flow
The workflow closes the loop between rebalance intent and custodian-confirmed account state.
| Step | Input | Controlled output |
|---|---|---|
| Create intent | Model target, rebalance instruction, account list, household context, restrictions, cash needs | Approved trade set with source rationale |
| Execute and capture | Orders, fills, custodian execution files, broker or platform trade IDs | Captured account-level trade records |
| Check allocation | Block trade, average price, partial fill, fund or account split, tax-lot and fee treatment | Allocation evidence and correction status |
| Validate restrictions | Do-not-buy list, account mandate, client preference, wash-sale or tax rule context, eligibility data | Restriction pass, exception, or review item |
| Reconcile custody | Custodian trade file, cash feed, position feed, internal blotter, settlement status | Matched state, timing item, break, or repair action |
| Retain evidence | Comments, approvals, source files, corrections, reports, and review history | Books-and-records support package |
The first step is capturing intent. The system should preserve the model, rebalance reason, account list, household relationship, client restrictions, cash needs, and adviser approval context that produced the trade set.
Execution and capture convert that intent into account-level trade records. The trade source may be a trading platform, custodian file, broker response, API, or manual correction. Each record should carry source identifier, timestamp, account, instrument, side, quantity, price, settlement date, and custodian path.
Allocation review checks whether block trades and account splits were applied correctly. This includes average price allocation, partial fills, account exclusions, cash constraints, tax-lot treatment, and fee handling. Corrections should be controlled because they can affect client statements, performance reporting, billing, and compliance review.
Restriction validation checks whether the executed trades respected client and account constraints. A restriction may be investment-related, tax-related, account-type-related, or operational. The workflow should show pass, exception, review, override, and approval status where relevant.
Custody reconciliation compares the adviser record against custodian trade, cash, and position records. Breaks should be classified by cause: timing, missing file, incorrect allocation, cancelled trade, stale cash, failed settlement, corporate action, or booking error.
Evidence retention closes the workflow. The record should preserve model context, source files, custodian responses, comments, corrections, approvals, restriction results, reconciliation status, and reporting references. That evidence should live with the trade record rather than in a disconnected folder.
In Devancore™
RIA post-trade — record quality
Devancore · control state
Before
Disconnected adviser workflow
- Model trade, custodian file, and reconciliation live in separate views
- Client restrictions are hard to tie to execution records
- Corrections and approvals require manual reconstruction
- Billing and reporting consume records with weak lineage
After
Controlled post-trade record
- Model intent, account trade, custodian file, and reconciliation state share lineage
- Restrictions, corrections, and approvals remain attached to the trade
- Breaks carry owner, reason, evidence, and downstream impact
- Client, compliance, and reporting outputs point back to the same event chain
Devancore supports RIA trading platform post-trade workflows by maintaining controlled operating records around adviser trading, allocations, custodian feeds, restrictions, corrections, reconciliation, and reporting inputs. The platform should not be framed as RIA portfolio management software, execution software, custody, tax advice, legal advice, or the party responsible for the adviser's compliance program.
In a Devancore-style workflow, a model trade, rebalance instruction, custodian trade file, account-level execution, allocation, correction, cash feed, position feed, restriction result, or reconciliation break enters as a source event. The record is mapped to account, household, portfolio, instrument, custodian, trade date, settlement date, workflow state, and evidence.
This gives teams a practical control surface. They can see which account trades came from a model rebalance, which client restrictions were checked, which custodian files were ingested, which allocations changed, which trades failed reconciliation, which cash or position records disagree, and which corrections require approval.
Conversational finance fits adviser operations because many questions are account-specific. A user may ask which accounts missed a rebalance, which trades violated a restriction review, which custodian files are missing, which corrections affect billing inputs, which client accounts have unresolved custody breaks, or which records support a compliance review. The answer should resolve to account-level records and evidence.
The practical value is a cleaner post-trade record. Adviser workflows can remain connected to client, account, custody, reconciliation, and reporting evidence without making each team rebuild the history separately.
Related terms
- Trade Allocation
https://devancore.com/glossary/trade-allocation/
Post-execution process that splits a block trade into account-level positions, each generating a separate confirmation and settlement obligation.
- Custody Reconciliation
https://devancore.com/glossary/custody-reconciliation/
Custody reconciliation is the daily match of internal positions and cash to the custodian statement: timing versus genuine breaks, owners, aging, and the evidence that holdings are actually safekept.
- Account Segregation
https://devancore.com/glossary/account-segregation-securities/
The requirement that broker-dealers keep client funds and securities strictly separate from firm assets under Rule 15c3-3 — enforced through the reserve formula, the Special Reserve Bank Account, and good control location requirements.
- Trade Break Resolution
https://devancore.com/glossary/trade-break-resolution/
The process of resolving data mismatches between trade counterparties before settlement cutoffs to prevent settlement fails.
- Trade Capture System
https://devancore.com/glossary/trade-capture-system/
The system that books an executed trade into the firm's official records and initiates the post-trade processing workflow from enrichment and matching through to settlement instruction.
- Trade Enrichment Automation
https://devancore.com/glossary/trade-enrichment-automation/
The automated augmentation of a raw trade capture with settlement instructions, counterparty identifiers, and regulatory fields required for clearing and settlement.
- Trade Confirmation Matching
https://devancore.com/glossary/trade-confirmation-matching/
The automated comparison of trade details between counterparties to verify both sides recorded the same economics before settlement instructions are generated.
- Trade Reconciliation
https://devancore.com/glossary/trade-reconciliation/
The systematic comparison of internal trade and position records against external sources to identify breaks and resolve them before they become settlement failures.
- Trade Blotter Post Trade Workflow
https://devancore.com/glossary/trade-blotter-post-trade-workflow/
A trade blotter post-trade workflow turns blotter rows into governed operating records for allocation, enrichment, confirmation, settlement instruction, exception management, reconciliation, supervision, and audit evidence.
- OMS To Post Trade Integration
https://devancore.com/glossary/oms-to-post-trade-integration/
OMS to post-trade integration is the controlled handoff from order and execution records into allocation, confirmation, enrichment, settlement instruction, reconciliation, supervision, and reporting workflows.
- Settlement Instruction Automation
https://devancore.com/glossary/settlement-instruction-automation/
Automatically generating and transmitting settlement instructions to custodians and CSDs using pre-loaded SSI data — replacing manual entry, enabling STP, and making T+1 compliance operationally viable.
- Standing Settlement Instructions
https://devancore.com/glossary/standing-settlement-instructions/
Pre-agreed instructions specifying how a counterparty's securities and cash should be delivered or received, applied automatically to every qualifying trade.
- Broker-Dealer Audit Trail
https://devancore.com/glossary/broker-dealer-audit-trail/
The immutable, chronologically linked record of every trade lifecycle event — from order receipt through settlement — maintained to satisfy SEC Rules 17a-3 and 17a-4, FINRA clock synchronization requirements, and CAT reporting obligations.
- Investment Book of Record
https://devancore.com/glossary/investment-book-of-record/
The IBOR — a real-time position record used by investment managers, capturing unsettled trades, accruals, and corporate actions ahead of custodian confirmation and ABOR settlement.
- Accounting Book of Record
https://devancore.com/glossary/accounting-book-of-record/
The ABOR: custodian-confirmed settled positions used as the authoritative basis for NAV calculation, financial statements, and regulatory reporting.
- Post-Trade Compliance Software
https://devancore.com/glossary/post-trade-compliance-software/
The technology layer that turns post-trade activity into an exam-ready compliance record: audit trail, supervisory controls, and books and records under SEC and FINRA rules.
- Operational Risk Management Securities
https://devancore.com/glossary/operational-risk-management-securities/
The identification and mitigation of risks from failed processes, human errors, technology failures, and external events that disrupt securities operations or cause financial loss.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/