DTC FAST

The FAST balance

The FAST balance is the operating center of the program. It represents the quantity of an eligible security held by the FAST transfer agent for DTC. That position is generally tied to DTC's nominee structure, where Cede & Co. is the registered holder for securities held through the depository system. The transfer agent's record, DTC's depository record, and each participant's account record must remain aligned.

A balance certificate gives the position its control basis. Instead of moving individual certificates each time shares or bonds enter or leave the depository system, the agent adjusts the FAST balance and confirms the change through DTC connectivity. The result is a paperless movement workflow, but not a control-free workflow. The record still needs security identifiers, quantities, account references, approvals, timestamps, and reconciliation evidence.

The Fast Balance Confirmation System, or FBCS, is the operating control around that evidence chain. It gives DTC and FAST agents a structured way to confirm that the FAST balance shown by the agent agrees with the DTC position record for the issue. For a post-trade system, FBCS is not trivia. It is the named reconciliation layer that turns a balance certificate from static documentation into an ongoing control.

FAST agents and eligibility

A DTC FAST agent is an approved transfer agent that participates in the FAST program. The agent must have the operational connectivity and permissions needed to interact with DTC systems, confirm movements, and reconcile balances. A security must also be eligible for the relevant DTC service before the FAST workflow can be used. For operations teams, FAST eligibility is therefore an instrument-master attribute, not a footnote. It determines whether an issue can move electronically through DTC-facing workflows or whether a different handling path is required.

FAST does not make every security freely transferable through every workflow. Eligibility, issue type, transfer-agent participation, DTC rules, participant permissions, and service-specific requirements still matter. Money market instruments are handled through separate DTC infrastructure and should not be folded into a FAST assumption.

DWAC and DRS

FAST is often encountered through DWAC and DRS. DWAC, or Deposit and Withdrawal at Custodian, allows a DTC participant to make electronic deposits or withdrawals of eligible securities through the FAST transfer agent. DRS, or Direct Registration System, allows securities to be held in book-entry form directly on issuer or transfer-agent records and moved through DTC connectivity when appropriate.

The DRS Profile workflow adds a second layer of operational control. A transfer into or out of a broker-dealer account depends on registration details matching across the transfer-agent record and the participant request. Account name, taxpayer identifier, share quantity, registration format, surety or insurance information where required, and approval status can all become reject points. That is why a DRS movement can fail even when the security itself is FAST eligible.

The distinction is simple. FAST is the transfer-agent/depository infrastructure. DWAC is a deposit or withdrawal workflow that uses that infrastructure. DRS is a registration model that also relies on DTC connectivity with FAST transfer agents. A post-trade system should keep those concepts separate because they create different records, approval points, and exceptions.

Why FAST matters operationally

FAST turns physical custody movement into electronic position synchronization. That is useful only if the synchronization is controlled. If the transfer agent's FAST balance, DTC's depository position, participant account records, and internal books do not agree, the firm has a custody reconciliation problem. The issue may affect settlement, corporate action entitlement, client reporting, transfer processing, or books-and-records evidence.

A persistent FAST balance or eligibility problem can also create market-infrastructure consequences. Depending on the issue and DTC's procedures, processing limitations, chills, freezes, or other restrictions may be applied until the underlying condition is resolved. The article should be read through that lens: a FAST break is not just an internal back-office mismatch. It can become a security-level operational constraint.

The operational question is not only whether a movement completed. It is whether the right security moved, the correct quantity changed, the correct party approved the movement, the right account was credited or debited, and the resulting position reconciles across the transfer agent, DTC, participant, and internal records.