Executive Summary (TL;DR) Sleeve pendings help ensure transactions and assets are applied to the correct sleeve, reducing reconciliation issues and manual corrections. This article explains why sleeve pendings matter, outlines best practices for creating pendings for external sleeve trades, and reviews the available options for correcting transactions that post to the wrong sleeve.

 

 

What Does This Article Help Solve?

Common Real-Life Questions Users Ask About Sleeve Pendings

"How do I know whether a missing pending caused a sleeve allocation issue?"

"What happens if Data Reconciliation receives a transaction without a pending trade?"

"I forgot to create a pending before the trade posted. What are my options for correcting the sleeve assignment?"

"Why did a transaction get split across multiple sleeves, and how do I prevent that from happening in the future?"

 

 

Why Sleeve Pendings Drive Accuracy and Efficiency?

• Create sleeve pendings before transactions post to keep assets mapped to the correct sleeve from the start.
  
  
• Reduce manual sleeve maintenance by giving the Data Reconciliation team clear instructions on where transactions belong.
  
  
• Prevent misallocated transactions and assets that lead to time-consuming corrections and operational risks
  
  
• Keep portfolio data accurate by avoiding default placement in custodial accounts or unintended share splits across sleeves.
  
  
• Streamline reconciliation workflows by processing trades through Orion and automatically generating pendings for every trade.

 

 

What Are the Consequences of Missing Sleeve Pendings?

Pendings for sleeves are essential because they tell the Data Reconciliation team where to put the transactions and assets. When the team doesn't have a pending to tell them which sleeve to put the new transaction, they may put it in the incorrect sleeve. This directly affects the amount of effort sleeve maintenance is for your team. 


The Data Reconciliation team has two options for applying a transaction that does not have a pending:

• When the sleeves do not have an asset that matches the transaction, the transaction/asset is created in the custodial account.
  
  
• When there are sleeves in the registration that currently hold the associated asset, the shares for that transaction get split across those sleeves based on the current percent that each one holds.

Review How to Review, Troubleshoot, and Reject Pending Trades for more information on why pendings might not complete.

How to Create Pendings for External Sleeve Trades

It is best practice to run all trades through Orion because this creates pendings for every trade and transactions map to the correct assets. In the event you must trade with the custodian, follow these steps to create pendings manually. Otherwise, you must move the transactions manually. 

To create pendings in Orion Trading for external sleeve trades:

• Import the trades you created at the custodian. Follow How to Import Trades in the Orion Trading Platform (Eclipse) for instructions.
  
  
• Turn your FIX Connection off. Review the How to Turn a FIX Connection off section in How to Use FIX Connection Best Practices.
  
  
• Navigate back to the Trade Orders Grid
  
  
• Highlight all the orders > right-click  > select process selected
  
  
• This drops the orders into a trade file AND creates pending trades for each trade processed

Action Steps when Transactions end up in the Wrong Sleeve

If a transaction ends up in the wrong sleeve, you have some options to correct this. The below table explains your options for moving those assets. It is important to pick the option based on where your asset is currently held. The When to Use explains which parts of the sleeved registration you are able to use with each option. For example, the Rebalancer does not include the custodial account and does not transfer assets from the custodial account to the tradeable sleeves. Therefore, it only works with sleeve assets. 

 

Option	Additional Information	When To Use
Sleeve Transfer Tool	Review the article How to Use the Sleeve (UMAs or Unified Managed Accounts) Transfer Tool for more information on transferring assets from one sleeve to another	Works for sleeves and custodial account assets
Rebalancer	Run a full portfolio level rebalance or a journal only rebalance. For more information on this, review the article How to Rebalance Sleeves and Sleeved Portfolios (UMAs or Unified Managed Accounts).	Only works on sleeve assets
Transaction Import	Use the Transaction Add Custom Import to transfer assets between sleeves. For more information review the article How-To and Troubleshooting: Transaction Add Import.	Works for sleeves and custodial account assets

 

 

In Summary Run trades through Orion whenever possible to automatically generate pendings and maintain accurate transaction mapping. Import and process custodian trades promptly when trading outside Orion to create the required pending trades. Monitor pending trade completion and investigate exceptions before transactions post to accounts. Select the appropriate correction method based on asset location, whether in a sleeve or the custodial account. Resolve misplaced transactions quickly to maintain accurate sleeve allocations and reduce downstream cleanup efforts.