How to Build a Client Folder Structure in SharePoint for a Financial Services Firm

If your financial services firm is still managing client files on a shared drive — or on a SharePoint that's essentially a shared drive with a cloud address — you're carrying more operational risk than you need to. Here's what a properly built client folder structure in SharePoint looks like for an IFA or wealth management practice, and why it matters for both your team and your FCA obligations.

Why the shared drive approach fails financial services

A shared drive can hold files. It cannot:

• Show an adviser only their own clients without browsing
• Surface every client due for an annual review in the next 60 days
• Flag documents where required compliance fields haven't been completed
• Automatically generate review documents from client data
• Restrict access to sensitive data based on role rather than folder knowledge
• Connect to your CRM so client status changes are reflected in your documents

SharePoint, properly built, does all of these. The difference between a shared drive and a properly built SharePoint environment for an IFA practice is the difference between a filing cabinet and an operational platform.

The library structure

The foundation is getting the library structure right. For a wealth management firm we'd typically recommend:

• Active Clients — one folder per client relationship, with subfolders for Suitability, KYC, Correspondence, Meeting Notes, Annual Reviews, and Completed
• Prospects — same structure, separate library. Keeps active clients clean and allows different permissions and retention rules
• Trusts & Companies — separate area for non-individual clients with different metadata requirements
• Templates — firm-wide document templates in a controlled library
• Inactive / Archive — clients who've left, with appropriate retention policies

The metadata model

The columns that make the views work — and that your Power Automate flows will populate and maintain:

• Client Status — Active, Inactive, Prospect, Suspended. Drives the primary view filtering.
• Adviser — person column, links to your Microsoft 365 user directory. Drives My Clients view.
• Client Type — Individual, Joint, Trust, Company, Corporate. Affects how matching and display works.
• Enable Reference / CRM Reference — your CRM's client identifier. Links SharePoint folders to CRM records.
• Review Date — date of next scheduled annual review. Drives the Reviews Due view.
• Review Status — Not Started, In Progress, Complete, Overdue. Updated by flows.

Connecting to your CRM

Most CRM systems used in financial services — Enable, Salesforce, Dynamics, Intelliflo — either have a Power Automate connector or export data to Excel. Either way, we can build a flow that reads your CRM data and populates or updates SharePoint metadata columns.

For the wealth management firm we're currently working with, the CRM data comes from an Excel export. A Power Automate flow reads the export, matches client folders using name fields and CRM references with XLOOKUP, and writes the current client status, adviser, and review date back to SharePoint. The matching logic handles joint clients, shortened names, and company names correctly.

The annual review automation

This is the capability that saves the most time in practice. Annual review documents — suitability letters, review reports — are typically prepared manually from a combination of client data, investment information, and meeting notes. A document that takes an adviser or paraplanner an hour to prepare can be generated in seconds when the data is already in SharePoint and Excel.

The flow works like this: a Word template with placeholders for client name, adviser, review date, Enable reference, current holdings summary, and recommended actions. When the review is ready to prepare, a Power Automate flow reads the client's SharePoint metadata and CRM data, populates the template, saves the completed document to the client's Annual Reviews subfolder, and links it back to the review record. The adviser's job is to review and personalise — not to copy data from a spreadsheet into a Word document.