← Glossary

Devancore Post-Trade Glossary

DTC Delivery Orders

A DTC book-entry instruction used to move securities between participant accounts through valued or free delivery workflows.

Definition

A DTC Delivery Order is a book-entry settlement instruction used to move securities between participant accounts at The Depository Trust Company. DTC materials may also call it a Deliver Order or DO. The name sounds simple, but the object is central to U.S. securities operations. It is the instruction that turns a trade, allocation, stock loan, account movement, collateral transfer, or other obligation into a depository-level securities movement.

A delivery order identifies the security, quantity, delivering participant, receiving participant, delivery type, and value amount where applicable. In a valued delivery, the securities movement is paired with a payment amount. In a free delivery, the securities move without DTC settling a linked cash amount through the same instruction. Both forms still need control. A free movement can still create custody, ownership, collateral, books-and-records, tax lot, corporate action, and client reporting effects.

DTC Delivery Order — fields, controls, and record impact

Element Purpose Control point Record impact
Security and quantity identify what moves CUSIP, position, eligibility, available inventory position record and custody ledger update
Deliverer and receiver identify the DTC participant accounts participant number, counterparty, account mapping settlement instruction and counterparty evidence
Valued or free determine whether DTC cash settlement applies DVP/RVP amount or FOP movement reason cash projection, liquidity, and settlement record
IMS state stage and prioritize the instruction inventory, queue, priority, authorization state pending, recycled, made, dropped, or exception status
RAD outcome control receiver acceptance accept, reject, DK, threshold, manual review receiver decision and fail-risk evidence

The controlled instruction

A delivery order should be understood as a controlled settlement primitive. It is not just a row in a file or a message sent to a utility. It is a live instruction with state. It can be submitted, staged, authorized, recycled, held for receiver review, accepted, rejected, dropped, made, or failed. Each state matters because each one changes what the firm can say about its positions and obligations.

The instruction also sits between systems. Upstream, it may come from NSCC CNS, institutional trade matching, same-day affirmation, a settlement instruction engine, a stock loan desk, a custody movement, or a manual operations workflow. Downstream, it affects DTC participant positions, custody records, cash projections, fail monitoring, reconciliation, and regulatory books and records.

Valued and free delivery

Valued delivery orders support delivery-versus-payment or receipt-versus-payment logic. The securities and cash economics are connected, so the instruction affects liquidity projections, participant debit exposure, collateral usage, and end-of-day money settlement. A valued DO cannot be treated as only a position movement because the cash side can determine whether the delivery can complete.

Free delivery orders move securities without the same DTC-valued cash settlement leg. They are useful for movements where the cash consideration is absent, separate, or settled through another process. The absence of a DTC cash leg does not make the instruction low-risk. Free deliveries still need authorization, entitlement awareness, account mapping, custody reconciliation, and evidence. A free transfer of the wrong quantity, wrong CUSIP, or wrong account can create the same operational damage as a failed valued settlement.

IMS, RAD, and recycle

The DTC Inventory Management System, or IMS, is where delivery orders become operationally visible as queued instructions. IMS helps participants stage, authorize, prioritize, and monitor settlement activity. This matters when several obligations compete for the same securities inventory. A firm may need to prioritize CNS settlement obligations over bilateral movements, stock loan activity, or other discretionary transfers.

If the instruction cannot post cleanly, it may recycle. Recycling is not final failure. It is a blocked or waiting state. The cause may be insufficient inventory, risk-control status, receiver review, or another operational condition. A recycled instruction deserves immediate attention because it can become a settlement fail if the condition is not resolved before the relevant processing window closes.

Receiver Authorized Delivery, or RAD, adds the receiver-side control. A receiving participant may need to accept the incoming delivery before it posts, depending on the profile, threshold, counterparty, and delivery characteristics. A delivery that is perfectly valid from the deliverer's perspective can still wait in RAD on the receiver side. If the receiver does not recognize the delivery, the item can be rejected or DK'd. That status needs to flow back into the firm's exception workflow, not sit outside the operating record.

Books-and-records importance

A delivery order is depository evidence. Broker-dealer and custody systems should be able to show the source instruction, CUSIP, quantity, deliverer, receiver, delivery type, value amount if any, IMS status, risk-control result, RAD outcome, DK reason, recycle history, settlement confirmation, and correction trail. Without that chain, the firm may know that its position changed, but not why, when, through which instruction, or under whose approval.

This is why a DTC Delivery Order belongs in the same control family as standing settlement instructions, same-day affirmation, trade matching, DTC RAD, failed trade settlement, and custody reconciliation. Each one answers a different part of the same question: can the firm prove that the settlement record is complete, current, authorized, and reconcilable?

How it works

1. Originate the instruction

A delivery order begins when a settlement obligation or custody movement is translated into an executable DTC instruction. The source may be an NSCC CNS obligation, an institutional trade workflow, a manual participant entry, a stock loan movement, an account transfer, or another DTC-eligible movement. The instruction should include the security identifier, quantity, deliverer, receiver, delivery type, and value amount where applicable.

2. Stage the DO in IMS

The delivery order enters an operational state where the participant can manage priority and availability. IMS is the practical staging layer. It shows whether the instruction is authorized, queued, unprocessed, made, dropped, or otherwise not ready to post. For a participant managing scarce inventory, this is not administrative detail. It determines which obligations consume available securities first.

3. Check inventory and risk controls

The delivery cannot settle if the delivering participant lacks available position in the relevant security. For valued delivery orders, cash and risk controls also matter because the instruction can increase a participant's net debit exposure. DTC controls such as Collateral Monitor and Net Debit Cap are designed to prevent settlement activity from creating uncovered exposure inside the depository system.

4. Route receiver review

Where Receiver Authorized Delivery applies, the receiving participant has a gate before the delivery posts. The receiver can accept the instruction, reject it, or mark it DK when it does not recognize the delivery. This is a control against unwanted or mismatched deliveries, but it can also create a settlement bottleneck if the status is not visible to the delivering side.

5. Post or recycle

If inventory, risk, and receiver controls are satisfied, DTC posts the book-entry movement. The delivering participant's position decreases and the receiving participant's position increases. If a condition is not satisfied, the instruction may recycle or remain pending. The firm should treat that status as an owned exception with cause, owner, deadline, and next action.

6. Update records and retain evidence

Once made, the delivery order should update the firm's custody record, position record, cash projection or cash ledger where applicable, exception queue, and audit trail. If the instruction fails or is rejected, the failure state should be retained with the same discipline. A complete DO history shows the instruction as it moved from source to state changes to final outcome.

DTC Delivery Order — operating states

Devancore · message matrix

Rail Message Purpose Record
Submitted DO created start settlement movement source instruction, CUSIP, quantity, deliverer, receiver, and delivery type
Staged IMS state prioritize inventory use queue status, priority, available position, and authorization history
Recycled blocked instruction prevent unsafe posting inventory, risk, RAD, or operational reason attached to the exception
Accepted RAD pass receiver allows posting receiver action, timestamp, and counterparty evidence
Made book-entry posted complete securities movement DTC confirmation updates custody, position, cash, and audit records

In Devancore™

Devancore models a DTC Delivery Order as a stateful settlement object. The platform does not wait for end-of-day reconciliation to discover whether a delivery posted. It records the instruction, maps it to the trade, account, security, counterparty, and settlement path, and tracks each operational state as the DO moves through inventory, risk, receiver, recycle, and final posting.

In a Devancore workflow, a valued DO and a free DO follow different control paths. A valued delivery feeds liquidity, cash, collateral, and debit exposure monitoring. A free delivery still feeds custody, ownership, account, and authorization controls. Both update the operating record only when the underlying evidence supports the change.

Devancore also connects DTC Delivery Orders to exception management. A recycled item is classified by cause. A RAD hold is routed to the receiver-action queue. A DK is tied to counterparty communication and trade evidence. A risk-control block is tied to liquidity or collateral monitoring. The user sees the live reason the instruction has not become a settled position.

The result is an examination-ready chain from intent to settlement. Operations can answer which delivery order moved the security, which controls it passed, where it waited, who acted, what changed in the books, and whether the final DTC position reconciles with the internal custody and accounting record.