Transaction
Catch booking errors and unusual trading activity in a fund's transactions.
Transaction scans a fund's trades, corporate actions, and instrument expiries to catch anomalies and booking errors. It cross-checks that recorded transactions actually match how the portfolio changed. It answers: were the fund's transactions booked correctly, and is any trading activity unusual?
How it works
It scans trades, corporate actions, and expiries from three angles: cross-checking that day-to-day position changes match the registered transactions (flagging quantity and price mismatches), studying historical patterns for unusual behavior, and targeting error-prone events such as late-booked trades and unusual paydowns. To decide what is abnormal it uses statistical anomaly detection scaled to the fund's size and history, rather than fixed rules, so genuinely unusual activity stands out.
What you get
- Mismatches between traded quantities or prices and the portfolio's actual holdings and prices.
- Late trades (booked after the day they happened) and their count.
- Turnover by instrument type, sector, or currency, with alerts when it looks abnormally high or low.
- Corporate actions detected (dividends, coupons, splits) and unusual paydowns flagged.
How to use it in Spark
The checks and alerts arrive as data in your workspace. Review them in a data view, and when a mismatch or an abnormal-turnover alert fires, let a workflow or the Agent open a task so it gets investigated.