Margin Call Tracking.
From CSA to collateral, automated.
Leah ingests Credit Support Annexes, monitors exposure against thresholds, computes margin calls, tracks responses and substitutions, and resolves disputes. One continuous record across every counterparty.
The CSA is the source of truth. Most margin workflows treat it like a filing cabinet.
CSA terms buried in PDFs
Threshold, minimum transfer amount, independent amount, eligible collateral, haircuts, and notification timing all live inside scanned ISDA Credit Support Annexes. Operations teams re-key them into spreadsheets and the spreadsheet becomes the source of truth that nobody trusts.
Threshold breaches discovered late
Exposure moves intraday, but breach detection happens at end of day after the risk system reconciles. By the time collateral ops sees the breach, the call window is already tight and the counterparty has the same data you do.
Call computations manual and error-prone
Variation margin, initial margin under uncleared margin rules, threshold offsets, and minimum transfer amounts get computed in spreadsheets stitched across desks. One stale CSA term or one wrong haircut and the call is wrong.
Collateral substitutions mis-tracked
When a counterparty substitutes Treasuries for cash, or pledges a new security, the eligibility check, haircut, and concentration limit need to be reapplied. Substitutions are reconciled by hand and frequently drift from the CSA.
Dispute trails emailed not logged
Counterparty disputes happen over email, Bloomberg chat, and phone. The reasoning, the counter-calculation, and the resolution sit in inboxes. Audit, regulators, and the next person on the desk have no continuous record.
Cross-counterparty visibility absent
Each counterparty is managed in its own spreadsheet or workflow. Risk leadership cannot see, in one place, where the firm stands across CSAs, who has open calls, who has pending disputes, and where collateral is concentrated.
Every CSA, parsed and live
Leah reads every ISDA Master Agreement, Credit Support Annex, and amendment in your population. Threshold, MTA, independent amount, eligible collateral schedules, haircuts, valuation agent, notification timing, and dispute resolution clauses are extracted as structured rules the calculation engine can apply directly.
“We had eleven hundred CSAs across two legacy books. Leah parsed every one and surfaced thirty where the threshold in the spreadsheet did not match the executed annex.”
Head of Counterparty Risk, Asset Manager
Five steps to continuous margin call workflow
Leah integrates with the CLM, risk, and collateral systems you already run. No rip and replace. Value from the first daily call cycle.
Connect
Leah integrates with your CLM, risk system, collateral management platform, and communication channels. CSAs, exposures, positions, and counterparty messages flow into a single intelligence layer.
Extract CSA Terms
Every ISDA Master, CSA, IM CSA, and amendment is parsed. Threshold, MTA, independent amount, eligible collateral, and haircuts become structured, queryable rules.
Monitor Exposure
Exposure is evaluated continuously against CSA terms. Threshold breaches, MTA crossings, and IA adjustments are flagged in real time and queued for calculation.
Compute and Issue Calls
Variation margin and initial margin calls are computed using the actual CSA terms, drafted in the counterparty's expected format, issued, and tracked against the response window.
Track Collateral
Pledges, substitutions, and concentration limits are reconciled. Disputes are captured with full reasoning. Every event lives in one continuous, audit-ready record.
Got Questions? Get Answers.
Traditional collateral management systems compute calls, but they assume the CSA terms have been correctly entered and maintained in a separate static configuration. Leah reads the executed CSA itself, keeps it in sync as amendments arrive, and applies the actual contractual terms to the calculation. The system of record for the terms is the document, not a re-keyed spreadsheet.
No. Leah operates on top of your CLM, risk engine, and collateral management platform. CSAs continue to live where they live today. Exposure continues to be calculated by your risk system. Leah reads from those systems, applies the structured CSA terms, and writes back computed calls, dispute records, and audit trail.
Amendments, side letters, and the additional IM CSAs put in place under uncleared margin requirements all flow into the same structured layer with effective dates preserved. When a call is computed, Leah applies the version of the CSA that was in force on the valuation date, not the original signed version. New IM CSAs added to existing relationships are recognized and computed independently of the VM CSA.
Yes. Leah reads the actual document, not a structured template. Asymmetric thresholds, custom eligible collateral schedules, bespoke haircut grids, and unusual dispute resolution clauses are all extracted with audit-grade accuracy. Where extraction confidence is below threshold, the term is flagged for human review before it enters the calculation engine.
When a counterparty disputes a call, Leah captures their counter-number, the supporting reasoning, and the channel it arrived on. The dispute is reconciled line by line against Leah's calculation, with the relevant CSA clause attached, and routed to the desk that owns the resolution. Every step is timestamped, so the dispute history is one continuous record rather than an email thread.
Yes. Leah is deployed at major asset managers, banking groups, and hedge funds with strict data security requirements. CSA content does not train Leah's underlying models. Customer data is encrypted in transit and at rest. SOC 2 Type II, GDPR, CCPA, and ISO 27001 aligned. Private instance deployment is available for customers with strict data isolation requirements.
