Why this memo.
ProSystem fx Tax remains the backbone tax-prep stack at a meaningful slice of mid-market CPA firms, especially those who deferred the Axcess migration during 2020-2024 and built their workflow muscle around the desktop product. Wolters Kluwer's official roadmap is to move firms onto Axcess; their AI investment is concentrated there. Firms still on ProSystem fx are correctly worried about being on a deprecation path.
Custom AI on top of ProSystem fx is the alternative for firms that want leverage now without committing to a 12-18 month migration first. The architecture: AI reads ProSystem fx data through the firm's existing reporting and export interfaces, delivers value immediately, and is migration-portable to Axcess when the firm eventually moves.
The ProSystem fx surface area we touch.
ProSystem fx exposes a narrower API surface than Axcess. We integrate primarily through ProSystem fx's PDF and XML export pipelines for return data, the firm's document management system (FileCabinet CS, NetClient CS, or third-party DMS) for workpapers, and Outlook + Microsoft Graph for client communication.
The integration is read-heavy. We do not write back into ProSystem fx in most workflows. The AI assists the preparer; the preparer enters the return.
Workflow I: PBC chase & binder build, season after season.
Same workflow as the CCH Axcess version, adapted to ProSystem fx's binder structure. AI handles document chase, categorization, and binder build through the firm's DMS; pings the partner for material missing items.
Workflow II: Tie-out & review-pass AI.
The custom AI reads the in-progress return + workpapers, compares line-by-line against prior year + the firm's tie-out checklist, surfaces flags in a reviewer-facing summary. Recovery: 30-50% of preparer-to-reviewer cycle time at audited firms.
Workflow III: Migration-ready architecture.
The unique ask for ProSystem fx firms. Most are running ProSystem fx and planning a future Axcess migration. Custom AI built today should not become technical debt during the migration. We architect the AI layer to abstract ProSystem fx vs Axcess access via a thin interface; when the firm migrates, we re-wire the data layer to Axcess in 1-2 weeks rather than rebuilding the AI logic.
This is meaningful. Firms that commission AI without migration-portability re-spend the engagement budget when they move to Axcess. Firms that commission with portability in mind get value through migration and beyond.