Why the Retirement Industry Is Finally Moving Past SFTP
For decades, moving retirement data between payroll and recordkeepers has meant one thing: generate a file, drop it on an SFTP server, wait for someone to reconcile it. In 2025, the SPARK Institute released voluntary API guidelines to replace that model — and 2026 is the year the industry starts building toward it.
The Problem With Files
File-based transfer has three structural weaknesses:
No standardization. Nearly 6,000 payroll providers in the U.S. each store the same general data — census, contributions, loans, vesting — in their own proprietary format.
Batch delays. Files move on a schedule, not in real time, so a recordkeeper's view of a plan is often days old.
Manual reconciliation. When a file doesn't match expected formatting, which is a very common issue, given the lack of standards — a person has to catch and fix it before the data is usable.
What APIs Change
SPARK's framework replaces one-way file drops with structured, real-time exchange. Instead of resending an entire census every time, a proper API sends only what changed (a new hire, an updated deferral, a loan repayment), pushing to the recordkeeper the moment payroll closes.
A standardized Census API went live in 2025, with loan, distribution, and balance APIs following as adoption grows. The goal isn't one company's proprietary system, it's a shared blueprint any recordkeeper, TPA, or payroll provider can build to.
Why It Matters Beyond IT
Compliance gets easier. Roth catch-up and part-time eligibility rules depend on accurate, timely payroll data — real-time exchange reduces the chance of failures tracing back to a stale file.
Security improves. Modern APIs support encrypted, authenticated, auditable transfers — a huge upgrade over shared SFTP credentials.
Small plans become viable to serve. Custom-building integrations for every small payroll provider doesn't scale; a shared standard lowers that barrier as SECURE 2.0 helps more small employers offer plans to support their employees retirement goals.
Clean data enables smarter tools. Real-time, structured data is also the foundation for reliable AI-assisted plan administration, helping detect errors, reducing costs, and simplifying compliance monitoring.
The Transition Won't Happen Overnight
These are voluntary guidelines, not a mandate, and thousands of payroll providers still run legacy systems. SFTP isn't disappearing soon. Recordkeepers,TPAs, and employers that want standardized data now need platforms that can meet data where it lives today — legacy exports, homegrown formats — and transform it into whatever standard a downstream system requires. Todays Pension has developed a platform to help all the stakeholders in this process simplify, standardize, and securely transmit the data they have today with no system changes.
The Takeaway
The shift away from SFTP is one of the more consequential changes happening quietly in plan administration. It won't be fast or uniform, but the direction is clear: real-time, standardized, less manual. Plan sponsors, TPAs, and recordkeepers building for that future now — while still supporting the legacy formats most of the industry runs on — will be best positioned as adoption accelerates.
Want to know how your payroll-to-recordkeeper data flow stacks up? Contact us at sales@todayspension.com or (720) 799-1000.