Pershing vs Fidelity Institutional: 2026 Custody Guide

Start with custody fit, then compare the operating experience

For an advisor comparing Pershing vs Fidelity Institutional, the first decision is whether the custodian can support the practice’s actual accounts and holdings. Shortlist Pershing when combining brokerage custody with bank trust custody is central to your operating model. Shortlist Fidelity when its Wealthscape account experience, investment access, and connections to your existing software match how your team works. These are fit recommendations, not a tested performance ranking.

A custodian is the institution that holds client assets and supports account administration, transaction processing, and related records.

The names still describe active offerings, but they are not equivalent software subscriptions. Pershing belongs to BNY and provides custody through distinct brokerage and bank entities. Its current technology includes NetX360+ and NetXInvestor; NetXServices has been renamed Wove Connect, and NetXInvestor offers 24/7 account access, according to BNY Pershing.

Fidelity Institutional is part of Fidelity’s FMR group, with securities brokerage and custody delivered through Fidelity Brokerage Services and National Financial Services. Wealthscape is its brokerage platform, with digital onboarding and 24/7 mobile check deposits, according to Fidelity. Compare the contracted custody relationship, platform entitlements, and optional services rather than assuming every Fidelity offering is included.

TL;DR: Prefer Pershing when your requirements emphasize coordinated brokerage and bank trust operations. Prefer Fidelity when the proposed Wealthscape configuration fits your accounts, investments, and staff. Reject either proposal if it cannot establish asset eligibility, a usable data path, and written economics.

Key Takeaways

• Pershing and Fidelity both warrant evaluation by an RIA; the decisive evidence is whether the proposed relationship supports your specific account registrations, securities, and daily tasks.

• Pershing’s bank trust and brokerage custody scope makes it relevant to practices with those combined needs, but the contracting entities and service responsibilities require separate confirmation.

• Fidelity’s Wealthscape experience supports an integrated custody workflow; optional advisory and planning services should be evaluated separately from core custody.

• Institutional custody pricing is Quote-based for this comparison. A public maximum-charge disclosure is useful context, but it is not your negotiated proposal.

• Run the same account-opening, transfer, reconciliation, and exception scenarios with both candidates before selecting one.

• Keep client authorization, trading decisions, and money movement under approved human controls when connecting custody data to other systems.

Who this is for

This guide is for an advisor selecting a primary custodian, adding another relationship, or planning a move from an existing institution. It is particularly useful when the decision involves account complexity, software dependencies, or a migration that could interrupt client service.

Red flags: A required holding lacks written eligibility confirmation; the proposed economics depend on commitments your firm cannot support; essential data access remains unapproved or undocumented.

Do not turn a vendor’s broad institutional capabilities into a staffing requirement for your practice. Advisers with at most 100 employees: 92.8% according to Investment Adviser Association (2025 data in its current industry snapshot). That describes the association’s adviser population, not either custodian’s customer base. It reinforces the need to evaluate who will own exceptions when your operations team is busy.

Your shortlist should reflect your investment approach and service model. A practice using straightforward accounts may value familiar workflows more than additional product breadth. A practice handling trusts, unusual holdings, or multiple custodians should put greater weight on entity responsibilities, asset treatment, and reconciliation.

How we evaluated the custody decision

This buyer’s guide uses public vendor documentation, public fee disclosures, industry association research, and transfer rules. It does not contain customer interviews, hands-on platform testing, or measured implementation results. The weights below are our proposed decision framework, not vendor scores or market statistics.

The proposed weights total 100%. Score each surviving candidate from 0 to 5 using evidence from your own diligence, then calculate weight multiplied by score divided by 5. These are suggested scoring choices, not observed vendor results. Leave unresolved items marked unknown; do not award points because a salesperson promises a future capability.

Apply disqualifiers before weighting. An attractive price cannot offset an account type the institution will not accept. Similarly, an extensive integration catalog cannot compensate for your firm lacking access to the required data. Adjust the weights before demonstrations so the preferred presentation does not quietly redefine your requirements.

Compare capabilities using the same questions

The matrix separates documented scope from matters that require confirmation. “Confirm” means public information does not establish suitability for your particular relationship; it does not mean the vendor lacks the capability.

Ask staff to perform the same representative tasks in each demonstration. Watch where they leave the custody interface, rekey information, wait for approval, or lose visibility into status. An advertised integration should earn credit only when it covers the data and permissions your workflow requires.

For both candidates, separate custody capability from discretionary investment services and third-party software. A shared brand or integrated screen does not prove that every module has the same contract, price, or support team. Record those boundaries in the comparison.

Pershing: evaluate breadth alongside operational ownership

Pershing deserves particular attention when bank trust custody and brokerage custody must coexist in your practice. Its published custody scope includes trust-related accounting and administration as well as brokerage services. That makes it a relevant candidate for complex relationships, subject to confirmation of the actual services and entities in your proposal.

The practical attraction is the possibility of coordinating related operations rather than asking staff to reconcile separate processes manually. Treat that as a hypothesis to demonstrate. Ask the vendor to show the journey from account registration through holdings, reporting, and an exception. Require clarity on where the bank relationship ends and brokerage responsibilities begin.

NetX360+ is the custodial workspace to evaluate; Wove components should enter the assessment where your proposed architecture needs them. Do not assume a Wove demonstration establishes that the same functionality is included with custody. Request an entitlement map that names each relevant product, its purpose, and the team responsible for supporting it.

Best fit: A practice whose account structures, trust needs, or custody architecture justify evaluating the broader BNY offering. Existing staff experience with Pershing may also matter, but it should be demonstrated through task completion rather than assumed to eliminate training.

Limitations to investigate: Additional breadth can create additional decisions about contracting entities, modules, permissions, and support ownership. Public descriptions do not establish the negotiated cost or exact configuration your firm will receive.

Implementation approach: Inventory registrations and holdings, obtain written acceptance, map users to approved roles, and identify the feeds needed by your reporting software. Have operations review account setup and compliance review the authority model before committing to the migration.

Choose another option if the required arrangement adds complexity without solving an actual client or operational need. Also pause if an essential integration is described in general terms but its scope, authorization process, and production support remain unresolved.

Fidelity Institutional: evaluate the Wealthscape configuration

Fidelity is a credible candidate when you want custody operations organized around Wealthscape and the proposed integrations fit your existing reporting and CRM environment. Its documented advisor experience includes account onboarding, cash management, money movement controls, trading access, and mobile account information. Those capabilities provide a starting point for diligence, not proof of your firm’s implementation.

Investment breadth needs position-level verification. Fidelity describes custody and servicing for 4,000+ non-exchange-traded alternatives across retirement and non-retirement accounts, according to Fidelity. That count does not establish eligibility for any particular fund, share class, account, or investor.

Best fit: A practice whose approved accounts and investment approach align with Wealthscape and whose staff can demonstrate the required daily tasks in the proposed configuration. Familiarity with Fidelity elsewhere in a client’s financial life may be relevant, but retail account familiarity does not establish institutional workflow suitability.

Limitations to investigate: Fidelity’s custody, investment, planning, and advisory offerings have distinct functions. Evaluate optional services separately. Confirm which permissions and connectors the firm will receive, how external applications get data, and where responsibility sits when a connection fails.

Implementation approach: Map account-opening requirements, approved user roles, client authorization, and reporting dependencies. Ask the team to show an incomplete application, a rejected transfer, and an unresolved cash discrepancy. Successful handling of those cases is more informative than a presentation showing only the expected path.

Do not choose Fidelity solely because a retail brokerage page advertises attractive trading costs. Request institutional terms for your relationship. Likewise, do not reject Pershing on the strength of a fee maximum that may differ from a negotiated arrangement.

If a required holding is ineligible, a registration is unsupported, or an essential export cannot be authorized, treat that as a disqualifier until resolved in writing.

Pricing and TCO: normalize the proposals before comparing

Pricing checked October 10, 2026.

The institutional custody relationship is Quote-based for both vendors in this guide. Neither public material reviewed supplied a firm-wide tariff that could be applied reliably to this advisor’s proposed relationship. Fidelity’s public retail trading pricing is a different scope and should not substitute for institutional terms.

Pershing does publish a maximum-charge schedule for brokerage accounts served through Pershing Advisor Solutions. The document says negotiated charges may be lower. It is a disclosure ceiling for the specified services, not a universal price for hiring Pershing.

Build separate firm-cost and client-cost views. Firm costs can include contracted services, software dependencies, training, migration labor, and ongoing administration. Client costs require account-level analysis of applicable transaction charges, service fees, and cash arrangements. Avoid collapsing the views into a single headline number.

Use the same holdings and transaction assumptions for both proposals. Distinguish recurring charges from transition expenses, and ask how discounts change if the relationship changes. Identify minimum commitments and any conditions attached to assistance or concessions without assuming either vendor’s standard terms.

Evaluate cash arrangements separately from explicit fees. Request the available choices, relevant disclosures, and the process for changing instructions. A fee comparison alone does not capture the economic consequences of client cash handling.

A proposal wins on cost only when it is cheaper for the same required scope under your documented assumptions. Missing line items should remain unknown rather than becoming an implied free service.

Prove the migration path before committing client assets

Transfer timing is a useful diligence anchor, but it does not describe the entire conversion project. Transfer completion rule: 3 business days after validation according to FINRA. The rule contains qualifications, including provisions for nontransferable assets, and notes that the stated timeframe can change through NSCC publications. Have the transfer team confirm the applicable process; do not promise a universal client migration deadline.

Create a holdings inventory with registrations, account restrictions, pending activity, and tax-lot requirements. Ask each candidate to identify assets that cannot move in kind and the authorized disposition choices. Do not authorize liquidation simply to make the implementation schedule easier.

The table below is a proposed acceptance exercise using synthetic records. Its counts are deliberately chosen test inputs and expected outputs, not vendor benchmarks or reported customer results.

Here, “held” means awaiting mapping or approval; it is not necessarily an error. Reviewers should inspect the resulting cases and reasons, not just the totals. Run the exercise in an approved test environment with suitable data protection before using client information.

Agree on evidence for positions, balances, tax lots, client access, and unresolved exceptions. A transfer status alone should not close the conversion task. Keep the original and destination records available to authorized reviewers until discrepancies are resolved.

For a practice adding another custodian, also decide which system owns consolidated reporting. Confirm how late corrections arrive and how staff distinguish stale information from an actual balance discrepancy. A migration is operationally acceptable when the team can explain the residual exceptions and their owners.

Keep cross-system exceptions visible

A proposed US Tech Automations workflow could start when an authorized custodian export arrives. It would validate the file, match account identifiers to the CRM, and create or update an exception case for missing mappings or incomplete statuses. The output would be a review queue with source timestamps and links to authorized records. Prerequisites include an approved API or export, documented field mappings, CRM write permissions, and a retention policy. Operations would review ambiguous matches; compliance would approve the data-access design.

A second proposed US Tech Automations workflow could begin when a permitted account-status update indicates a transfer exception. It would compare that status with the firm’s checklist, assign an internal task, and prepare a client-update draft for human review. The output would be an accountable case and supporting evidence. This requires authorized status access and agreed exception definitions; staff would approve client communications and resolve discrepancies before any account action.

If Salesforce is part of the approved stack, plan for recovery rather than assuming an event bus is a permanent archive. Salesforce event retention: 72 hours according to Salesforce. A proposed consumer should preserve checkpoints and reconcile against an authorized source after an interruption.

For a clearly illustrative example, assume a test sends 12 Salesforce platform-event deliveries representing 9 unique transfer exceptions, including 3 repeat deliveries. Salesforce documents the replay position as ConsumerEvent.replay_id and the platform-event identity as ConsumerEvent.event.id, according to Salesforce. A configured identity check would therefore aim for 12 − 3 = 9 cases, with repeats representing 3 ÷ 12 = 25% of deliveries. These are hypothetical inputs and arithmetic, not observed results; replay positions must not be treated as unique business identifiers.

Zapier, Make, n8n, or an in-house service can be reasonable alternatives. They can support run histories, retries, error branches, and audit evidence when configured appropriately. The buyer still needs to design and own observability, idempotency, escalation, access controls, and maintenance. Custodian access must be authorized regardless of the orchestration tool.

A proposed US Tech Automations design could configure shared exception definitions, account-mapping checks, recovery checkpoints, and a human approval queue around the chosen custodian. Suitability depends on approved interfaces, maintainable mappings, and an internal owner. It cannot supply permissions the custodian has not granted or replace fiduciary judgment.

For adjacent workflow examples outside financial services, the campaign exception recipe illustrates a trigger-to-review approach, while the dental membership platform comparison and SaaS tool comparison provide other buying-guide contexts. They are not custody evidence.

Questions to settle before the final selection

Is Pershing better than Fidelity Institutional for an RIA?

Pershing is the stronger candidate when its proposed custody scope fits requirements that your Fidelity proposal cannot satisfy. In particular, evaluate its bank trust and brokerage arrangements when both matter to your practice. If those needs are absent, let demonstrated staff workflows, written economics, and authorized data access determine the choice.

Is Fidelity Institutional the same as a retail Fidelity account?

No, an institutional custody relationship has its own service scope, entities, permissions, and commercial terms. Retail familiarity may help clients recognize the brand, but it does not establish institutional pricing or account administration capabilities. Evaluate Wealthscape and the custody proposal directly.

Which custodian costs less?

The cheaper custodian depends on the negotiated proposal and your actual service requirements. Request comparable schedules and use the same account, holdings, and transaction assumptions. Keep client charges separate from firm expenses and record exclusions. Public maximum charges and retail commission pages cannot settle the comparison.

Can a firm use both custodians?

A firm can evaluate a multiple-custodian model, subject to acceptance and the terms of each relationship. Decide why the additional relationship is necessary and how staff will handle consolidated reporting, client authorization, permissions, and exceptions. Additional choice needs an operating owner; it should not become an unmanaged reporting burden.

Should automation replace the custodian’s native workflow?

No, native custody controls should remain authoritative for account approval, trading, and money movement. Use orchestration where permitted to coordinate information and internal review across systems. Validate the data source and authority boundaries before allowing a status update to create a downstream task.

When NOT to use US Tech Automations?

Use the custodian’s existing tool, a maintained connector, or a simple checklist when it already covers the required workflow. Additional orchestration is unnecessary when there is no cross-system exception to solve, when a capable internal team maintains the connection, or when approved API/export access is unavailable. Preserve the simpler arrangement when it offers adequate visibility and accountable review.

Make the choice with a documented decision checklist

Before signing, confirm asset and registration eligibility, obtain relationship-specific pricing, approve the data path, assign service escalation owners, and agree on migration acceptance evidence. Have the staff who will operate the relationship review the same exception scenarios with both candidates.

Choose Pershing when its custody breadth solves a documented requirement and the proposed operating arrangement remains manageable. Choose Fidelity when Wealthscape and the contracted custody services fit your practice with acceptable economics and support. Keep unresolved requirements visible rather than averaging them away in a score.

If cross-system coordination remains a requirement after that choice, review how US Tech Automations could configure exception routing around authorized data and human review. The custodian decision comes first; orchestration should support the relationship you can justify.