Process

From Chat to Structured Data in Seconds

Four sequential steps turn a raw broker message into a clean, OMS-ready record. No manual re-keying. No spreadsheet intermediary.

  1. Message Ingestion

    TwoWay connects to your existing broker messaging platforms via approved API channels. Messages arrive in real time from Bloomberg Messenger, ICE Chat, Symphony, and Refinitiv. No forwarding rules or manual exports required on the counterparty side.

    Messages are deduplicated and queued for parsing, preserving original source metadata including platform, sender context, and receipt timestamp for MiFID II audit purposes.

  2. NLP Field Extraction

    Broker messages arrive in free-form language: abbreviations, shorthand conventions, and trader idiom. The TwoWay parse engine extracts directional intent (bid, offer, or axe), instrument reference, notional size, price type, and price value without requiring any change to how brokers write.

    Confidence scores are assigned per field. Records below a threshold are flagged for review rather than silently passed through to the OMS.

  3. ISIN and Reference Data Enrichment

    Partial identifiers and ticker aliases are resolved to canonical ISINs and CUSIPs via reference data. Pricing convention is detected (yield, spread-to-benchmark, discount margin) and settlement date is normalised using T+N conventions or explicit date parsing.

    Currency normalisation handles multi-currency deals. The enrichment step produces a record ready for OMS import without further transformation by the desk.

  4. Structured Feed Delivery

    Normalised records are delivered via JSON API for OMS direct import, CSV for Bloomberg PORT and Excel, or FpML-adjacent format for downstream systems. Each record carries its full parse provenance and is retained in the audit log for the regulatory review period.

    Delivery latency from message receipt to available output is typically under three seconds on the production pipeline.

Before and After

Raw Message to Structured Record

The same broker communication, before and after TwoWay. No change to how the broker writes; no manual re-entry at the desk.

Raw broker message
From: GS Rates Desk [ICE Chat]
09:14:22 GMT

hey axe on FR0013451670
5mm offer at +42 for T+2
can do 4.5mm if needed
clean price basis
Structured output record
{
  "isin": "FR0013451670",
  "direction": "OFFER",
  "notional": 5000000,
  "price_type": "SPREAD",
  "price_value": 42,
  "settlement": "2026-10-08",
  "source": "ICE Chat",
  "confidence": 0.97
}

Downstream Systems

Where the Data Goes Next

Structured records from TwoWay connect directly to the systems your desk already uses. No new infrastructure required beyond the TwoWay API endpoint.

OMS Direct Import

Records delivered via REST API in a format compatible with standard order management systems. Your operations team receives clean data without the copy-paste step from chat to system.

Bloomberg PORT

Structured records export in Bloomberg PORT-compatible format. Pre-trade data enters your portfolio system at the point of broker communication rather than post-confirmation entry.

Excel and CSV Export

Where OMS integration is not the first step, structured data is available as a clean CSV feed for Excel-based workflows. Each row maps directly to one parsed broker communication.

Processing Broker Communications Under GDPR

Broker chat messages are communications data covered by GDPR. TwoWay processes this data as a data processor under a formal Data Processing Agreement. All processing occurs within EU infrastructure. Source messages are retained for the MiFID II regulatory review period and are never used for model training.

For details on encryption standards, access controls, and compliance posture, see our Security page. Floor and Enterprise tiers include a signed DPA template.

See the pipeline running on your data environment

Pilot onboarding takes one to two weeks. We work with your IT and compliance teams on integration scope.

Request a Pilot See Pricing