Open Fails, Stock Loans, and the Reconciliation Challenge Nobody Talks About

Beyond Quarterly Counts: Continuous Position Verification That Actually Works

When a contra firm sends you a response to your quarterly broker statement request containing 10,000 positions—and you only asked about 47—the reconciliation team’s collective groan is audible down the hall.

This happens constantly. And it’s just one symptom of a broader challenge: position reconciliation across open fails, borrows, loans, and repos is complex, ongoing, and poorly served by tools designed for simpler problems.

THE RECONCILIATION REALITY

SEC Rule 17a-13(b)(3) requires quarterly verification, but the underlying position data doesn’t sit still between quarters. Open fails age. Stock loan positions change daily. Repo agreements mature and roll. The positions you’re verifying today may have different characteristics tomorrow.

The real operational challenges:

Open fail aging. A fail that’s 3 days old is different from one that’s 30 days old. The former is probably a timing issue; the latter needs investigation. Tracking age and escalating appropriately requires systems, not spreadsheets.

Stock loan complexity. Borrow and loan positions have counterparty risk, rate negotiations, and recall provisions. Reconciling these isn’t just matching quantities—it’s confirming terms.

Repo and reverse repo tracking. Collateral changes. Rates adjust. Maturities extend or terminate. The position you thought you had may have different economics than what’s on the books.

Multi-counterparty reconciliation. The same security might be held, borrowed, loaned, and failed across multiple counterparties simultaneously. Netting to a single view requires aggregation your spreadsheet wasn’t designed for.

THE ‘MASS RESPONSE’ PROBLEM

Here’s a scenario every reconciliation team knows:

You send a quarterly confirmation request for 47 specific positions to Counterparty X. Instead of confirming those 47 positions, they send back an Excel export of their entire position book—10,000 rows of data covering every security they hold across all counterparties.

Your 47 positions are in there somewhere. Finding them requires: Parsing their file format (which doesn’t match yours). Filtering to your firm identifier (if they even included it consistently). Matching security identifiers (CUSIP vs. SEDOL vs. internal codes). Comparing quantities (did they send settled or trade date positions?). Documenting what matched and what didn’t.

This takes hours. Per counterparty. Per quarter.

CONTINUOUS VS. QUARTERLY: THE EVOLUTION

Smart operations teams are moving beyond quarterly-only reconciliation. The reasoning:

Discrepancies discovered quarterly are already old. A position that went wrong in week 3 but wasn’t discovered until week 12 has been wrong for two months. Unwinding and correcting is harder.

Daily or weekly reconciliation catches problems when they’re small. A break that surfaces on day 2 is easier to fix than one discovered on day 60.

Continuous monitoring reduces quarter-end crunch. If you’re reconciling throughout the quarter, quarter-end becomes a validation exercise rather than a discovery process.

WHAT MODERN RECONCILIATION LOOKS LIKE

Effective position reconciliation—whether quarterly, monthly, or continuous—requires:

Flexible matching logic. Positions don’t always match exactly. Settlement date vs. trade date differences, share quantity rounding, corporate action adjustments—the system needs to handle near-matches intelligently.

Exception categorization. Not all breaks are equal. Quantity mismatches need different handling than completely unknown positions. The system should route exceptions to appropriate workflows.

Counterparty normalization. Different counterparties send data in different formats. The system needs to normalize incoming data to a common structure for comparison.

Audit trail preservation. Every match, every exception, every resolution—captured for examination readiness.

HOW QBS ADDRESSES POSITION VERIFICATION

Loffa’s QBS platform goes beyond basic quarterly confirmation to address the real complexity of position reconciliation.

For the mass response problem: QBS Mass Response uses AI to parse large response files and identify which positions match your original request. Instead of manually searching through 10,000 rows, the system extracts matches and flags discrepancies automatically.

For internal efficiency: QBS Pair and Match identifies when two QBS-S customers hold offsetting positions with each other. The system automatically marks these as matched, eliminating the need for external confirmation requests that would just confirm what the system already knows.

For inbound request handling: QBS Pre-Answer checks incoming confirmation requests against your position data before anyone manually reviews them. Matches get identified instantly. Only items with discrepancies or unknown positions require human attention.

For continuous monitoring: While QBS handles the quarterly SEC Rule 17a-13(b)(3) requirement, the platform’s capabilities extend to more frequent reconciliation cycles for firms that want continuous position verification.

PRACTICAL IMPLEMENTATION

For operations teams considering reconciliation improvements:

1. Map your current pain points. Where does staff spend the most time? Mass response parsing? Counterparty contact hunting? Discrepancy investigation?
2. Quantify the volume. How many positions? How many counterparties? How many exceptions per quarter? The numbers drive the automation ROI.
3. Consider frequency. Would weekly position checks reduce quarter-end pressure? Would daily monitoring catch problems earlier?
4. Evaluate integration needs. Does your reconciliation platform need to connect to position systems, clearing systems, stock loan systems?
5. Plan the transition. Moving from manual to automated reconciliation isn’t flip-a-switch. Build parallel processes, validate matching logic, train staff on exception handling.

The firms with smooth quarter-ends aren’t working harder. They’re working on the right things—exceptions that actually need judgment—while automation handles the routine matching that used to consume most of their time.

DISCLAIMER: This post is for informational purposes only and does not constitute legal advice. For guidance on specific regulatory obligations, consult your counsel or compliance advisor.