End-of-Day Reconciliation and Break Management

Direct Answer

End-of-day reconciliation is the authoritative daily comparison of the OMS's position and cash records against the custodian's official end-of-day statements. It is more comprehensive than intraday reconciliation: it must account for all positions across all accounts, all cash balances and pending settlements, and the pricing applied to value each position. Every break detected at EOD that was not resolved intraday must be classified, assigned to an owner, and escalated per the firm's break management policy.

EOD reconciliation produces the official starting balances for the next trading day. Breaks carried forward into the next day compound: they affect risk limit calculations, compliance checks, and client reporting. An unresolved EOD break is not merely an operational nuisance. It is incorrect information propagating through every downstream system that consumes positions or cash data.

Key Takeaways

• EOD reconciliation covers positions, cash, pricing, and pending settlements: Each dimension can break independently and requires different investigation and resolution processes.
• Break classification determines escalation path: Quantity breaks, cash breaks, pricing breaks, and settlement breaks each have different owners, urgency, and resolution approaches.
• Closing price source must be documented and consistent: The OMS and custodian must agree in advance on which price source governs end-of-day valuation. Disagreement on the source is the most common cause of systematic pricing breaks.
• Settlement breaks have regulatory consequences: Fail-to-deliver positions beyond T+3 trigger mandatory close-out under Regulation SHO Rule 204 for broker-dealers. Investment advisers are also affected through their prime broker's fail management process.
• Unresolved breaks must not be rolled forward silently: Each break that cannot be resolved before the next market open must be explicitly marked as "carried forward," assigned to an owner, and reflected in the next day's starting reconciliation with its age counter incremented.
• EOD reconciliation feeds client reporting: NAV calculations, performance attribution, and regulatory capital computations all depend on clean EOD positions. A break that affects NAV computation must be escalated immediately.
• Reconciliation policy must specify materiality thresholds: Not every break of any size requires the same treatment. Document the size thresholds for each escalation tier and the maximum age before mandatory escalation.
• The break log is a regulatory record: The daily break log, what was found, who investigated, what the resolution was, and when it closed, is subject to regulatory examination. It must be maintained for the applicable retention period.

Core Concepts

The EOD reconciliation process flow

EOD reconciliation follows a structured sequence. After the market closes, the OMS takes a final position and cash snapshot, a definitive record of what the system believes is the end-of-day state. The custodian or prime broker generates their end-of-day statement, typically available between 6 PM and 10 PM. The reconciliation engine ingests both, aligns them by account and instrument, and computes differences.

Position matching: for each account and symbol, compare OMS long quantity to custodian long quantity, and OMS short quantity to custodian short quantity. Flag any difference as a quantity break. Price matching: for each position, compare the closing price the OMS applied to the price the custodian applied to value the position. A pricing break does not affect the quantity record, but it affects NAV and P&L calculations. Cash matching: compare settled cash, unsettled proceeds, margin balance, and any pending fees or interest.

Settlement matching: compare the OMS's list of trades expected to settle today (buys and sells from two trading days ago for T+2, or yesterday for T+1) against the custodian's settlement confirmation file. Any trade on the OMS list that does not appear as settled in the custodian file is a settlement break, likely a fail-to-deliver or fail-to-receive.

After initial matching, the engine applies known-difference rules (expected timing differences, agreed methodology differences for certain security types) to separate expected from unexpected breaks. The unexpected breaks are the investigation queue for the operations team.

Break classification and severity tiers

Break classification drives resource allocation. A well-designed break management system classifies each break along three dimensions: type, size, and age. Type determines who owns the investigation: quantity breaks are worked by the trade reconciliation team who coordinates with the prime broker; pricing breaks are worked by the data management team who coordinates with the data vendor; cash breaks are worked by the treasury/cash operations team; settlement breaks are worked by the settlement operations team.

Size (measured in absolute quantity or market value impact) determines escalation tier. A sample tiering: Tier 1 (under $50,000 market value impact), operations resolves independently with a 48-hour SLA. Tier 2 ($50,000 to $500,000), operations resolves with risk management notification within 24 hours. Tier 3 (over $500,000), immediate notification to head of operations and CFO, resolution plan required within 4 hours.

Age amplifies severity. A Tier 1 break that resolves within 24 hours is routine. A Tier 1 break that persists for 3 business days without resolution is escalated to Tier 2 treatment regardless of its size, because persistence indicates a systemic data quality problem that cannot self-resolve. The break management system must track age and trigger age-based re-escalation automatically.

Evidence to retain: every break must have a break record in the system from detection through resolution. The record must capture: discovery timestamp, break type and details (OMS value, custodian value, difference), initial classification, assigned investigator, investigation notes, resolution action, and resolution timestamp. This record is the audit trail for the break management process itself.

Pricing break mechanics and resolution

Pricing breaks occur when the OMS applies a different closing price to a position than the custodian applies. For liquid U.S. equities, the official closing price is the consolidated last sale price as of 4:00 PM ET, published by the exchanges. Both OMS and custodian should use this price; if they do, pricing breaks for liquid equities should be zero.

Pricing breaks are more common for: (1) less liquid securities where there was no last sale at close and different sources choose different pricing methodologies (last bid, mid, evaluated price); (2) foreign equities where the exchange close is in a different time zone and FX rates must be applied; (3) fixed income instruments where price is derived from a model or evaluated price rather than an observed last sale; (4) exchange-traded derivatives where the settlement price is determined by the exchange's official settlement procedure and may differ from the last trade price.

Resolution of pricing breaks requires agreeing on which price is "correct" for the purposes of NAV and P&L calculation. For most institutional purposes, the custodian's price governs, the official NAV is calculated using the custodian's prices. The OMS's price affects internal reports and may need to be corrected retroactively to match the custodian if a report has already been sent to a client or regulator using the wrong price.

Settlement breaks and regulatory obligations

Settlement breaks identify trades that were expected to settle on a given date but did not. For U.S. equities under T+1, a trade from Monday should settle on Tuesday. If Tuesday's settlement run does not include the trade, a settlement break exists. The most common causes: the selling party failed to deliver shares (FTD, fail to deliver), the buying party failed to deliver funds (FTR, fail to receive), or there was an error in the settlement instruction (wrong DTCC account number, mismatched security identifier).

For broker-dealers, Regulation SHO Rule 204 requires that FTDs in equity securities be closed out no later than the beginning of trading on the settlement day following the failed settlement date (T+1 of the failure). For investment advisers, the obligation falls on the prime broker, but the adviser must monitor and cooperate in resolution because a pending FTD affects the account's available shares for further selling.

Settlement breaks create a unique reconciliation problem: the position quantity may be correct (both OMS and custodian agree on what the position should be once settled) but the cash and the actual shareholding at DTC do not reflect it yet. The OMS must track the unsettled position separately from the settled position and mark down available-to-sell quantity for the unsettled shares until settlement completes.

Worked Scenario

At 8 PM, the EOD reconciliation engine compares OMS and custodian data. It finds five breaks across two accounts.

1. Break 1, Quantity, Account 31, AMZN: OMS=8,500 long, Custodian=8,500 long. No quantity break. Pricing: OMS used $185.40, custodian used $185.35. Pricing break: $0.05 × 8,500 = $425 valuation difference. Classified Tier 1, assigned to data team. Investigate price source discrepancy.
2. Break 2, Quantity, Account 31, COIN: OMS=12,000 long, Custodian=11,500 long. Quantity break: 500 shares. Market value: 500 × $231.00 = $115,500. Classified Tier 2. Assigned to reconciliation team. Check for trade booked in OMS but not settled at custodian.
3. Break 3, Settlement, Account 31: A 500-share COIN buy from yesterday expected to settle today. Custodian statement does not show it as settled. It is a fail-to-receive, the seller did not deliver. This explains Break 2: the custodian does not show the 500 shares because they have not been delivered. OMS and custodian actually agree on what the position should be; the issue is settlement timing. Custodian notified to pursue delivery.
4. Break 4, Cash, Account 44: OMS cash = $2,315,400, Custodian cash = $2,320,200. Break: $4,800 custodian shows more. Check dividend log: none expected. Check commissions: yesterday's sell had a $4,800 commission charged on settlement date (today). OMS had accrued it on trade date (yesterday). After applying the expected difference schedule: $4,800 is the commission timing difference. Expected break, no action needed, will self-resolve tomorrow.
5. Break 5, Quantity, Account 44, NVDA: OMS=25,000 long, Custodian=25,000 long. No break. All five items resolved or classified. Operations summary: 1 pending settlement break (Tier 2), 4 resolved or expected. Next-day carry-forward: Break 3 (settlement fail, 1 day old).

Measurement Framework

Common Failure Modes

Custodian statement received too late for same-night resolution

Some custodians deliver their EOD position files very late, after midnight or even after 2 AM. Operations teams working the night shift have insufficient time to investigate and resolve breaks before the next morning's trading begins. The following day starts with unresolved breaks affecting opening positions.

Mitigation: negotiate earlier delivery SLAs with the custodian, or use streaming confirmations during the day to maintain a near-real-time reconciled position so the EOD comparison focuses only on the items that were not already resolved intraday.

Price source not documented in the reconciliation configuration

If the reconciliation engine does not explicitly document which price source governs for each asset class, operations teams cannot definitively say whether a pricing break is an error or an expected methodology difference. Every pricing break then requires manual investigation to determine which system is right, even when the difference is a known methodology difference that both parties have agreed to accept.

Break management system not tracking age

Operations teams that manage breaks in spreadsheets often lose track of which breaks have been open for multiple days. Without automatic age tracking and age-triggered re-escalation, small breaks can persist for weeks, accumulating into a chronic backlog. A single-day break of $5,000 is routine; a break that has been open for 15 business days at $5,000 represents a systemic failure to investigate and is far more serious operationally and regulatorily.

EOD reconciliation not aligned with client reporting

When the client reporting system uses prices or positions that differ from what the EOD reconciliation confirms as agreed with the custodian, client reports are wrong even when the reconciliation itself is clean. This can happen when the reporting system draws data directly from the OMS before the reconciliation has updated the OMS with the reconciled (custodian-agreed) values. The reporting process must run after the reconciliation cycle has completed and applied any corrections to the OMS.

Settlement fail not propagating to next-day position available-to-sell

When a settlement fail is identified, the custodian did not receive shares from a buy, the affected position may not be fully held at DTC and may not be available for same-day delivery in a subsequent sell. If the OMS marks the position as available-to-sell based on the confirmed (but not yet settled) buy, a subsequent sell will generate a short position at settlement even though the account "owns" the shares in the OMS's view. The OMS must tag all unsettled shares as non-deliverable until settlement confirms.

Frequently Asked Questions

References

• SEC: Amendments to Regulation SHO (Rule 204 close-out requirement, Release No. 34-60388): Requires broker-dealers to close out fail-to-deliver positions in equity securities within specified timeframes.
• DTCC NSCC Settlement Process: Describes the netting, clearance, and settlement process for U.S. equity trades through the National Securities Clearing Corporation.
• SEC Advisers Act Rule 204-2 (17 CFR 275.204-2): Books and Records to Be Maintained by Investment Advisers: Requirements for maintaining accurate trade and position records including reconciliation documentation.
• FINRA Rule 4160: Verification of Assets: Requires periodic independent verification of customer assets, supporting the regulatory basis for EOD reconciliation.
• SIFMA Operations Best Practices: Industry documentation of reconciliation standards and settlement failure management procedures.

Educational Disclaimer

This guide is for educational purposes only and does not constitute legal, compliance, or financial advice. Reconciliation requirements vary by firm type, jurisdiction, and registration category. Consult qualified professionals before designing or implementing reconciliation workflows.