Catena on Operations
Written for ops desks, not for traders.
Practical analysis of confirm handling, break patterns, settlement workflows, and reconciliation logic. Written by the Catena team from direct post-trade operations experience.
All articles
Settlement Fail Patterns Ops Desks Miss
A recurring price tolerance slip looks identical to a one-off ISIN mismatch on the morning break report, but they need different responses. Here are the four fail patterns that show up most often and the signals that distinguish them before the cutoff.
Reconciliation Bottlenecks: OTC Versus Exchange
OTC fixed income confirms arrive bilaterally, carry accrued interest fields, and settle on non-standard cycles. Exchange-traded confirms come through DTCC with netting. The same reconciliation logic cannot handle both without creating false breaks on one side.
T+1 Settlement Cycle: What Ops Desks Need
T+1 settlement compresses the reconciliation window from two days to one. For desks still running email-to-spreadsheet matching, the morning routine that used to have slack now has none. Here is what needs to change operationally, not just on paper.
Reducing Manual Breaks Management in Fixed Income
A fixed income desk running repo, corporates, and structured products simultaneously receives confirms in at least three distinct formats. Manual scanning for breaks across all three before the 4pm cutoff is not a workflow problem, it is a volume problem. Here is how desks are solving it.
Why Spreadsheet-Based Recon Breaks at Scale
At 50 trades a day a shared Excel file is manageable. At 300 it becomes a version control problem. At 500 it is a compliance risk. The failure modes are predictable and they happen in the same order on every desk.
Matching Logic for Equity Versus Bond Confirms
Equity confirms settle on CUSIP with a clean price and a quantity. Bond confirms add accrued interest, a yield, a face value, and a day-count convention that varies by counterparty. Using the same matching tolerance for both produces false breaks on bonds and misses real ones on equities.
Counterparty Confirm Mismatch: Root Causes
Across the desks we have worked with, confirm mismatches cluster around four causes: price rounding at the last decimal, settlement date calendar differences between counterparty systems, ISIN versus CUSIP identifier inconsistency, and quantity expressed in face value versus units. Each needs a different fix.
Post-Trade Ops Automation: Where to Start
Most post-trade automation projects start at the wrong point. Automating settlement instructions before you have reliable break detection just moves the problem downstream. Here is the sequence that saves the most time per dollar of automation effort.
DTCC Versus Bilateral Settlement: A Comparison
DTC-eligible positions net at DTCC and settle through a central counterparty. Bilateral OTC transactions confirm and settle directly between counterparties with no netting. The reconciliation logic, the break triggers, and the escalation paths are different for each, and a single spreadsheet cannot handle both without confusion.
Building the Ops Desk for the AI Era
When AI handles routine confirm matching, the ops desk does not shrink. It shifts. The hours spent rekeying confirms and hunting breaks become hours spent on genuine exceptions, counterparty escalation, and audit review. Here is what that transition looks like in practice.
Trade Life Cycle: From Execution to Settlement
From execution to final settlement, a trade passes through at least six distinct handoffs: execution, confirmation, affirmation, clearing, settlement instruction, and settlement confirmation. Each handoff is a point where a manual ops desk can introduce or miss an error. This article maps the full chain with the common failure modes at each step.