About TBA Processing
The general steps for processing TBAs follow:
The TBA security and the allocating TBA pools must have an established security master record created prior to attempting to process a transaction correctly.
The TBA must have an open lot available for allocation as TBA tax lots are closed by an Identified Lot (IDLOT) method.
When allocating a TBA turnaround, open underlying pools must be held securities,
When closing a TBA position, TBA Cashflow (tag 9406) must be set to the same value as the corresponding open position.
TBA Close transactions use settlement date logic. A TBA can be booked short, with a trade date prior to that of a long TBA position. The short being used against the long has the same Settlement Date, but the pools share the Trade Date of the TBA. The settlement date logic comes into play when allocating the TBA (Turnaround). If trade date logic was used, then when calling the pools back into the panel for the allocation of the short, the pools would not be found, because the TBA short's trade date is prior to that of the long position. So by using settlement date logic, the pools are found when allocating the TBA short position.
TBA Netting is available starting in V17 R2.48. When enabled, all inbound trades are processed as long positions, with short positions represented by negative units. This allows for improved straight-through processing because a single trade can take a position from long to short, or vice versa.
To improve processing times when allocating to underlying pools, you can use the Bypass Earnings Replay option. For more information, see Bypass Earnings during Rollback and Replay.