Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Chat-Based Trade Capture
Chat-based trade capture converts trade details from messages into structured trade records with instrument resolution, account context, validation, review, and audit evidence.
Document source: https://devancore.com/glossary/chat-based-trade-capture/
Devancore Post-Trade Glossary
Chat-Based Trade Capture
Chat-based trade capture converts trade details from messages into structured trade records with instrument resolution, account context, validation, review, and audit evidence.
Definition
Chat-based trade capture is the controlled workflow that converts a trade message into a structured trade record. The message may arrive through chat, voice transcript, broker conversation, internal desk note, or another collaboration channel. The capture workflow turns that unstructured instruction into fields that a trade capture system, order management system, execution management system, brokerage API, or post-trade platform can validate.
This page is narrower than natural language trading. Natural language trading covers the broader path from plain-language intent to staged order, control review, routing, execution, and post-trade record formation. Chat-based trade capture focuses on the first operating problem: preserving the original message while creating a clean trade record from it.
Message to trade record fields
Message to trade record fields
Capture quality depends on resolving the text into controlled data, not only extracting words.
| Field group | Captured data | Control question |
|---|---|---|
| Source message | Channel, sender, timestamp, conversation ID, message text, attachment, and thread context | Can the trade record be traced to the original instruction? |
| Economics | Side, instrument wording, quantity, notional, price, currency, order type, and time condition | Are the economics complete enough for a structured draft? |
| Instrument identity | Ticker, ISIN, CUSIP, FIGI, DTI, issuer, maturity, option terms, or internal security ID | Has the intended instrument been resolved without ambiguity? |
| Account context | Fund, account, portfolio, sleeve, strategy, custodian, clearing account, and allocation method | Does the captured trade point to the right operating book? |
| Settlement intent | Counterparty, broker, SSI, settlement date, cash leg, security leg, delivery method, and fail risk | Can downstream post-trade enrichment proceed? |
| Review evidence | Parsed fields, missing data, reviewer, approval, correction, route, and final capture status | Can the capture decision be reconstructed later? |
The source message matters because it explains how the trade entered the workflow. A captured trade should retain the sender, timestamp, channel, thread, attachment, and source identifier. If the resulting record is later disputed, the firm should not need to reconstruct the original instruction from screenshots or separate communication archives.
Field extraction is only the first step. The workflow should identify side, quantity, notional, price, instrument wording, account clue, counterparty, trade date, settlement date, order type, and instruction type. Some messages contain exact trade economics. Others contain partial intent. The capture state should show what was explicit, what was inferred, and what is missing.
Instrument and account resolution are the highest-risk parts of the workflow. A short name can refer to a security, issuer, fund, strategy, account, counterparty, or internal code. The workflow should resolve against governed instrument master data and account records. When the match is ambiguous, the item should move to clarification or review rather than becoming a booked trade.
Chat capture also needs settlement context. A record that has side, quantity, and price may still be operationally incomplete if it lacks counterparty, custodian, SSI, settlement date, delivery method, cash leg, security leg, fee, tax-lot, or allocation data. Weak capture becomes a post-trade break when it reaches enrichment, confirmation, or settlement.
Chat-based trade capture — required field cluster
Devancore Glossary · devancore.com
How it works
Chat-based trade capture works by preserving a lineage chain from message to reviewed trade record. The workflow should show how the message was parsed, which fields were extracted, which masters were used, which exceptions were raised, who reviewed the record, and where the captured trade was published.
Chat capture workflow
Chat capture workflow
The workflow should move from message to reviewed record before downstream processing begins.
| Step | Record created | Failure mode |
|---|---|---|
| Ingest message | Original text, sender, timestamp, channel, thread, attachment, and source ID | The captured trade loses the message that created it |
| Extract fields | Side, quantity, price, instrument wording, account clue, counterparty, date, and instruction type | The system treats incomplete text as a complete record |
| Resolve identity | Instrument master match, account mapping, portfolio, strategy, custodian, and route context | A similar ticker, issuer, fund, or account is selected incorrectly |
| Enrich record | Allocation, SSI, settlement date, fees, tax-lot context, restrictions, and reference data | The trade reaches post-trade with missing settlement or accounting fields |
| Review exception | Missing fields, ambiguity, override, approval, correction, and owner | A weak extraction bypasses human review |
| Publish capture | Trade record, blotter entry, downstream ID, audit trail, and post-trade status | The booked record cannot be tied back to the chat instruction |
Message ingestion stores the raw instruction and source metadata. The channel can be a chat system, voice transcript, email-like message, broker note, or internal conversation. The capture event should carry a source ID so the final trade record can point back to the message.
Extraction converts language into proposed fields. The system should separate trade economics from commentary. "Buy 10mm five-year notes for income sleeve if price is inside limit" contains side, size, instrument clue, strategy context, and price condition. Each element should become a visible field or review item.
Resolution maps the proposed fields to governed records. Instrument identity should connect to the security master. Account and portfolio context should connect to internal books. Counterparty and broker context should connect to known relationships. Settlement fields should connect to standing settlement instructions and custody records.
Enrichment prepares the record for downstream processing. Allocation rules, settlement route, fees, tax-lot context, restrictions, confirmation fields, and reference data can be attached before the trade reaches post-trade operations. Early enrichment makes missing data visible while the trader or operations user still has context.
Review handles ambiguity. Missing quantity, unclear instrument, conflicting account name, uncertain allocation, stale SSI, or unsupported security type should create a pending state. A reviewer can confirm, correct, reject, or request clarification. The final record should preserve the original extraction, the correction, and the reviewer decision.
Publication closes the capture step. Once reviewed, the trade can enter the blotter, OMS, post-trade workflow, reconciliation queue, or downstream API. Execution report, confirmation, settlement instruction, and break status should remain linked back to the original message.
Chat capture — message to operating record
Devancore Glossary · devancore.com
In Devancore™
Devancore — chat capture evidence chain
Devancore · evidence stack
Message source
Original text, sender, timestamp, channel, thread, and source ID remain attached to the capture event.
Parsed fields
Side, quantity, price, instrument wording, account clue, counterparty, and instruction type are separated from free text.
Resolved record
Instrument master, account, portfolio, strategy, custodian, settlement route, and allocation context are matched or flagged.
Review state
Missing fields, ambiguity, correction, override, reviewer, and approval state remain visible before the trade is published.
Trade lifecycle
Published trade record, blotter entry, enrichment result, confirmation, settlement intent, and post-trade status point back to the message.
Devancore supports chat-based trade capture as a controlled operating-record workflow. It should be framed as the layer that preserves message source, parsed fields, enrichment context, review state, publication event, and downstream post-trade evidence.
Devancore should not be framed as a trading venue, broker, custodian, clearing broker, adviser, or autonomous execution system. The product value is in turning an unstructured instruction into a reviewable record that can feed trade capture, enrichment, confirmation, reconciliation, settlement, books-and-records evidence, and reporting inputs.
In a Devancore-style workflow, a chat message becomes a capture event. The platform can preserve the source message, identify proposed trade fields, connect the instrument to reference data, connect the account to the right operating book, attach settlement intent, flag missing or ambiguous data, and route the record for review.
That gives the front office and operations team a shared record. The trader sees what was captured. Operations sees what is missing before settlement pressure builds. Compliance and supervision can see the original message, parsed fields, reviewer decision, correction history, and final trade record.
Chat-based trade capture is therefore a bridge between conversational finance and the trade lifecycle. Conversational finance provides the interface. Natural language trading describes the broader order path. Chat-based trade capture defines how the message becomes a controlled trade record.
Related terms
- Natural Language Trading
https://devancore.com/glossary/natural-language-trading/
Natural language trading converts a user's plain-language trade intent into a structured order draft, validation record, human review step, routing instruction, and audit trail.
- Conversational Finance
https://devancore.com/glossary/conversational-finance/
Conversational finance is a controlled natural-language interface for financial records, workflow intent, approvals, and evidence across trading, post-trade, compliance, and reporting.
- Conversational Finance Ops
https://devancore.com/glossary/conversational-finance-ops/
Conversational finance for investment operations is a permissioned natural-language interface over operating records: the question, the entitled sources, the cited evidence, and a workflow action that still needs approval.
- AI Agent Post-Trade Ops
https://devancore.com/glossary/ai-agent-post-trade-operations/
AI agent post-trade operations use controlled agents to detect exceptions, assemble evidence, draft actions, route approvals, and record outcomes without bypassing human supervision.
- 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.
- Instrument Master Data
https://devancore.com/glossary/instrument-master-securities/
The authoritative golden record of reference data — identifiers, static attributes, and lifecycle parameters — for every instrument a firm can trade, settle, or report.
- Trade Lifecycle Management
https://devancore.com/glossary/trade-lifecycle-management/
The discipline of tracking a securities trade through every stage — from order and execution to settlement and position update — with exceptions detected at each handoff.
- 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 Break Management
https://devancore.com/glossary/trade-break-management/
The exception workflow for identifying, classifying, and resolving post-trade discrepancies before they breach the T+1 affirmation cutoff or trigger CSDR cash penalties.
- 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.
- Brokerage API Post Trade
https://devancore.com/glossary/brokerage-api-post-trade/
Brokerage API post trade integration turns API orders, fills, journals, transfers, and account events into a controlled operating record with mapping, status, exceptions, reconciliation, and evidence.
- FIX Protocol Trade Capture
https://devancore.com/glossary/fix-protocol-trade-capture/
Open financial messaging standard where MsgType 8 Execution Reports trigger real-time trade capture and settlement pipeline processing for broker-dealers.
- FIX Engine Connectivity for Broker-Dealers
https://devancore.com/glossary/fix-engine-connectivity/
The software layer managing FIX session state, message sequencing, heartbeats, and failover for broker-dealers connecting to brokers, venues, and ECNs.
- 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.
- 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.
- 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.
- System of Record Securities Operations
https://devancore.com/glossary/system-of-record-securities-operations/
The authoritative single source of truth for a firm's positions, trades, and accounts — the system of record that all other systems, reports, and compliance functions derive from.
- 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/