Tax preparation software on SharePoint: CCH, UltraTax, Lacerte, Drake
SOLUTION GUIDE
The four dominant US tax-preparation desktop packages (CCH ProSystem fx from Wolters Kluwer, UltraTax CS from Thomson Reuters, Lacerte from Intuit, and Drake Tax from Drake Software) share the same workflow pattern: client-organised folders holding working papers, source documents, prior-year returns and current-year tax files, all opened by desktop clients that expect a real Windows file path and exclusive locks. Tax season concurrency peaks amplify every friction point in a sync-client model. Cloud Drive Mapper presents SharePoint as a mapped drive so tax prep runs cleanly on Microsoft 365 storage through peak weeks and beyond.
Why all four packages share the same story
Tax preparation software has converged on a common architecture over the past two decades. Each of the four packages differs on its user interface, its jurisdiction coverage and its integration surface, but they all treat client data the same way at the filesystem level: a client-organised folder tree holding source documents (W-2s, 1099s, K-1s), working papers, and the current-year return file, with the prior-year return file referenced by path when the new-year working file is created. The desktop client opens the current-year file exclusively, writes to it continuously as the preparer works, and releases the lock only when the file is closed.
That pattern is the same whether the preparer is working in CCH ProSystem fx, UltraTax CS, Lacerte or Drake Tax. It is also the same pattern that causes friction with OneDrive sync in all four cases.
What breaks when tax-prep software runs on OneDrive-synced storage?
Conflict copies of client return files
When two preparers (or a preparer and a reviewer) open the same client return at once, OneDrive cannot reconcile concurrent writes to the file and produces a conflict copy. Merging two working versions of a tax return by hand is not a workflow any firm wants to run during season.
Partial-sync corruption during a preparation session
The tax software writes to the client file continuously. OneDrive sees the changes and tries to upload mid-session. A partial upload can result in a cloud copy that is internally inconsistent, and when another workstation later downloads that version the software may refuse to open it or may open it and produce calculation errors.
Cross-year references break
Creating a new-year working file typically references the prior-year return by path. If the prior-year file is a cached stub not yet hydrated (or if OneDrive has moved it during a rebuild), the reference fails and the preparer has to locate the file by hand before the new-year working paper can populate.
Peak-season concurrency amplifies every friction point
Tax season is when a firm's file system is under maximum load: dozens of preparers touching dozens of client files concurrently, reviewers layering on top, admin staff filing signed source documents. Every sync-timing artefact that shows up once or twice a month in slow season shows up ten times a day in peak weeks. Support tickets pile up when firm capacity is already stretched.
How Cloud Drive Mapper fits
Consistent drive letters across the whole firm
CDM maps SharePoint document libraries as Windows drive letters that are the same for every preparer, reviewer, partner and admin. The client-folder structure resolves identically across the firm. Prior-year cross-references stored inside tax software configuration continue to resolve because the drive letter and the path structure beneath it stay stable.
SharePoint check-out replaces conflict copies
When a preparer opens a client return through the mapped drive, CDM triggers a SharePoint check-out. A second person opening the same file sees it as checked out and receives a read-only copy. There is no scenario in which concurrent writes to the same client return produce a conflict copy.
No sync-client interference during writes
CDM does not maintain a persistent local mirror, so there is no sync client scanning the client return file while the tax software is writing to it. Save operations write through to SharePoint cleanly; partial-state uploads and the corruption they can cause are not part of the CDM model.
Concurrency scales with Microsoft 365, not with the middleware
Each preparer's CDM mount is per-user and independent. Concurrency at peak scales with the underlying Microsoft 365 tenant capacity, not through any middleware bottleneck. Bandwidth per preparer stays proportional to the files they have open, not the size of the whole firm's client base.
Excel and PDF exports write cleanly
Excel schedules, PDF-generated returns and other exports configured to write to the mapped drive land in SharePoint the same way they would land on a network share. Reviewers and admin staff access the same files through the same drive letter without waiting for a sync cycle.
Setup notes for tax-prep environments
- Standardise the CDM drive letter across the whole firm so client-folder paths and cross-year references resolve identically.
- Move the firm's client-folder structure onto SharePoint document libraries mapped through CDM. Keep the folder hierarchy the firm already uses; there is no need to restructure.
- Update tax software configuration (client-file default location, prior-year lookup path, export destinations) from OneDrive-synced folders to the CDM drive.
- If migrating from an existing OneDrive-synced setup, run the tax software's file-integrity check on any client returns that showed calculation anomalies before moving them to the CDM path.
- Plan the migration outside tax season if possible. Migrating in mid-March is a live-fire exercise nobody enjoys.
CDM supports tax-prep software in the following deployment models:
- Windows desktops (direct)
- Citrix Virtual Apps and Desktops
- Citrix DaaS
- Azure Virtual Desktop (AVD)
- Windows 365 Cloud PC
- Omnissa Horizon (formerly VMware Horizon)
Cloud Drive Mapper is used across accounting practices to keep tax-preparation software running cleanly against Microsoft 365 storage through tax season.
Frequently asked questions
Which tax-preparation packages does this apply to?
The pattern applies to any desktop-installed tax preparation software that stores client data as files on a Windows filesystem. That includes CCH ProSystem fx (Wolters Kluwer), UltraTax CS (Thomson Reuters), Lacerte (Intuit) and Drake Tax (Drake Software) as the four dominant US packages. It also applies to firm-specific and jurisdiction-specific tax software that follows the same architecture. It does not apply to purely cloud-native tax tools (CCH Axcess Tax in its cloud mode, or online-only preparation tools) which run in the browser and do not touch the Windows filesystem for client data.
Does OneDrive sync cause data-file corruption in tax software?
It can. Tax preparation software takes exclusive locks on client data files during a preparation session, writes continuously, and expects the file to be untouched by any other process. OneDrive sync interferes with this pattern in two ways: it can upload a partial state of a file mid-write, producing a corrupt copy in the cloud; and it can create conflict copies of a client return if the same file is opened from two workstations. Both are recoverable if caught early and cost real time when they happen during tax season.
Does Cloud Drive Mapper handle multi-user access to a shared client-folder structure?
Yes. CDM presents SharePoint document libraries as consistent drive letters across all users in the firm. Preparers, reviewers, admin and partners all see the same client-folder structure at the same drive letter. When a preparer opens a client return, CDM triggers a SharePoint check-out; a reviewer opening the same file simultaneously sees it as checked out and receives read-only access. This mirrors the exclusive-lock model tax software expects.
Do cross-year references (this year's return pulling data from last year's file) work through CDM?
Yes. Tax software commonly references the prior-year return when creating the current-year working file. Those references are stored as paths. Because the CDM drive letter is stable across sessions and across users, the paths resolve consistently. Prior-year files stay reachable at the same path they were saved to originally.
Can Cloud Drive Mapper handle tax season concurrency?
Yes. CDM streams file content on demand and adds no queueing between the tax software and Microsoft 365. Peaks come from more preparers touching more client files at once; each preparer's CDM mount is per-user and independent, so concurrency scales with the underlying Microsoft 365 tenant rather than through any middleware bottleneck. Bandwidth per preparer stays proportional to the files they have open, not the size of the firm's whole client base.
Does IAM Cloud have access to our client tax data?
No. Cloud Drive Mapper operates purely with delegated permissions inside your Microsoft 365 tenant. IAM Cloud holds no credentials that would authenticate to your tenant. Only your firm's signed-in users can access content through CDM, and only within their existing M365 permissions. See Zero-access architecture for the design detail.
Related solutions
Try it before next tax season
The fastest way to see if CDM fits your tax-prep environment is to try it for 30 days, free. Point one preparer's workstation at a mapped drive and run a real client return through it.