Managing SIA-150, SIA-151, and F1SA Documentation Across Counterparties

The Prime Brokerage Agreement Stack—and Why Spreadsheet Tracking Fails

A prime brokerage agreement arrives with an outdated signatory. The SIA-150 on file is from 2019. The F1SA references an account structure that changed eighteen months ago.

And you didn’t know until the trade failed.

Prime brokerage documentation isn’t glamorous work. But the consequences of getting it wrong—DK’d trades, settlement failures, examination findings—make it operationally critical. The challenge is that ‘critical’ doesn’t mean ‘simple.’ Managing the documentation stack across dozens or hundreds of counterparties is complex enough that most firms’ tracking systems weren’t designed for it.

THE DOCUMENTATION STACK

Prime brokerage relationships require multiple interconnected documents:

SIA-150 (Prime Broker Agreement): The foundational document establishing the prime brokerage relationship. Specifies terms, responsibilities, and authorizations between the prime broker and the executing broker.

SIA-151 (Supplemental Agreement): Amendments, additions, and modifications to the base SIA-150. Over time, these accumulate as terms change, contacts update, and account structures evolve.

F1SA (Form 1 Schedule A): The account-level documentation connecting specific accounts to the prime brokerage arrangement. Critical for trade execution—without current F1SA on file, trades get questioned or rejected.

These documents form a dependency chain. An F1SA shouldn’t be filed unless the underlying SIA-150 is current. Amendments via SIA-151 need to reference the correct base agreement. A change at one level may require updates at other levels.

WHY SPREADSHEET TRACKING BREAKS

Most firms start with a spreadsheet. It makes sense at first—list of counterparties, document types, filing dates, expiration dates. Simple.

Then reality intrudes:

Version control chaos. Which SIA-151 is the current amendment? The one saved as ‘FINAL’ or ‘FINAL_v2’ or ‘FINAL_REVISED’? The spreadsheet says filed in March, but the document on the shared drive says April.

Amendment tracking complexity. Counterparty X has one SIA-150 and seven SIA-151 amendments over four years. Understanding the current state of the agreement means reading all seven amendments in sequence. The spreadsheet just shows ‘7 amendments.’

Cross-reference failures. The F1SA references ‘Agreement dated January 15, 2021’ but your SIA-150 is dated January 22, 2021. Is that a typo or a different agreement? The spreadsheet can’t tell you.

Expiration management. Some documents have explicit expiration dates. Others have evergreen clauses with termination provisions. Tracking which agreements need renewal versus which need monitoring for termination notices requires more than a date column.

Contact decay. The authorized signatory listed on the 2019 SIA-150 left the firm in 2021. The counterparty contact who handles documentation changes moved departments. Your spreadsheet has the old names.

THE EXAMINATION PERSPECTIVE

When FINRA examines your prime brokerage operations, they’ll ask for documentation supporting specific relationships. They expect: Current SIA-150 for each prime brokerage relationship. Complete amendment history via SIA-151s. F1SA documentation for accounts referenced in prime broker transactions. Evidence that documentation was reviewed and updated appropriately. Proof that document dependencies were maintained (F1SA follows SIA-150).

Producing this from a spreadsheet and a shared drive under examination time pressure is… not ideal.

WHAT CENTRALIZED DOCUMENTATION PROVIDES

Purpose-built prime brokerage documentation platforms solve the problems spreadsheets create:

Single source of truth. One system holds the current agreement, all amendments, and account-level documentation. No version confusion.

Relationship mapping. The system understands that F1SA depends on SIA-150. If the SIA-150 changes, it flags F1SAs that may need review.

Change tracking. Every modification logged with timestamps and user attribution. Examination comes, you show the complete audit trail.

Workflow enforcement. Can’t file an F1SA without a current SIA-150? The system enforces it. Can’t accept an amendment without authorized signatory? The system checks.

Expiration and renewal management. Approaching expirations surface automatically. Renewal workflows trigger without manual calendar tracking.

HOW PBIN HANDLES PRIME BROKERAGE DOCUMENTATION

Loffa’s Prime Broker Interactive Network (PBIN) centralizes the prime brokerage documentation stack with validation workflows that prevent the common failure modes.

Document relationships enforced. PBIN validates that F1SA isn’t filed unless SIA-150 is verified first. The system knows the dependency chain and enforces it.

Change control with audit trail. Every agreement, amendment, and account document tracked with complete history. Who filed it, when, what changed.

Counterparty portal. Self-service access for counterparties to submit documentation, review status, and acknowledge changes. Reduces the back-and-forth that slows updates.

Integration with FVD. When F1SA is on file in PBIN for an account, FVD automatically suppresses Letter of Free Funds requests—eliminating redundant verification for documented prime brokerage accounts.

PRACTICAL ASSESSMENT

If you’re managing prime brokerage documentation through spreadsheets and shared drives: How many counterparties have current documentation? (If you’re not sure, that’s the problem.) Can you produce the complete document history for any counterparty in under an hour? Who maintains the tracking spreadsheet, and what happens when they’re unavailable? How do you know when amendments make earlier terms obsolete? When was the last time documentation issues caused a trade to DK?

The firms avoiding DKs and examination findings have systems that enforce documentation requirements—not spreadsheets that depend on someone remembering to update them.

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.