The Case for Continuous Transparency Reporting: Why Spreadsheets Don't Scale

Somewhere in the CMS Open Payments compliance process, most life sciences companies still run at least one critical step through a spreadsheet: reconciling source-system data against a submission, tracking disputes during the pre-publication review window, or mapping which state transparency statutes apply to which recipients. Each one works, individually, at the scale a single analyst can hold in their head. None of them was built for the scale the underlying data has actually reached.

The Scale Problem Spreadsheets Were Never Built For

General Payments alone totaled 46.4 million individual transfers of value across PY2023 to PY2025, $10.68 billion, sourced from CMS public-use files with 91 columns per record. Research Payments added another 2.84 million records and $27.08 billion, on a wider 252-column layout. A spreadsheet-based reconciliation process that works for a few thousand rows a quarter doesn't fail gracefully at tens of millions of rows a year; it fails silently, in the form of a manufacturer-name variant that never gets merged, a royalty payment that never gets separated from promotional spend, or a dispute that ages past the pre-publication window because nobody was tracking it in real time.

Two Datasets, Growing at Different Speeds, Same Company

The case for a unified system isn't just about volume. It's about two structurally different, independently growing datasets that most compliance programs still manage with separate processes, separate owners, and separate tools.

Chart placement: after the framing paragraph on managing both datasets together. Source: qordata analysis of CMS Open Payments General and Research Payments public-use files, PY2023-2025.

General Payment spend grew 14.6% over the period; Research Payment spend grew at roughly a 4.5% CAGR but on a much larger base, with the sharpest step into the preliminary 2025 year. Both are moving, in different directions, at different speeds, inside categories that follow different rules: General Payments organized by nature-of-payment category, Research Payments organized by recipient type, therapeutic area, and principal investigator. A reporting process built as two disconnected workflows, one per dataset, structurally can't produce the single, defensible view an audit response actually needs.

The ownership question compounds the problem. General Payments typically sit with commercial compliance and field-facing teams; Research Payments typically sit with medical affairs and clinical operations. Different owners, different source systems, and often different definitions of what counts as "reconciled," even before anyone touches a spreadsheet. A unified system doesn't just merge the data. It forces a single definition of done across teams that, in most organizations, have never had to agree on one before.

What "Continuous" Actually Means

Continuous doesn't mean more frequent spreadsheet updates. It means the reconciliation, the fair-market-value check, and the documentation link happen at the moment a record is created, not in a batch process the week before a deadline. The practical difference shows up in the data itself: payments of $10,000 or more make up only about 0.15% of all General Payment transactions but account for roughly half of all dollars every year, while 102,764 recipients received 40 or more separate meal payments in 2025 alone. Catching an error in either pattern, a misclassified high-dollar payment or an under-aggregated frequent-meal recipient, after the fact means unwinding a submission that's already gone to CMS. Catching it as the record is created means it never becomes a submission in the first place.

The Multi-Jurisdictional Layer

The federal Sunshine Act calendar is the floor, not the ceiling. States including Massachusetts, Vermont, Minnesota, and Nevada layer additional disclosure thresholds, gift restrictions, and separate annual certifications on top of the federal requirement, each on its own calendar. Manufacturers with a European footprint carry a parallel obligation under the EFPIA Disclosure Code. None of these run on the same schedule as the CMS Open Payments deadline, and a compliance calendar built around one federal date alone will reliably miss the state-level and EFPIA obligations that don't share it. A surge in General Payment spend in a state with its own gift-ban statute, for example Pennsylvania's 41.0% year-over-year growth in 2025, is a compliance-calendar event under that state's law regardless of where it falls on the federal timeline.

The Hidden Cost of a Fragmented Tool Stack

This isn't a claim that any specific point solution is poorly built or lacks its own internal data model; most are built well for the specific problem they were bought to solve. The issue is what happens at the seams between them, where a spreadsheet becomes the de facto integration layer connecting an expense platform to a CRM to a state-law tracker, and where the seams are exactly where reconciliation errors accumulate fastest.

Most compliance teams don't choose fragmentation; they accumulate it. An expense platform here, a CRM there, a standalone spreadsheet for state-law tracking, another for dispute resolution, each added to solve one problem at the time it appeared. The cost shows up later, at exactly the moment it's most expensive: when a CMS audit request asks for a reconciliation file connecting a submitted record back to its source documentation, and that chain runs through three disconnected systems that were never designed to talk to each other. Consolidating that chain into one system doesn't just save time. It's the difference between producing a reconciliation file in an afternoon and reconstructing one, system by system, inside a 30-day response window.

What a Unified System Changes at Audit Time

The teams that respond to a CMS request fastest aren't doing anything different in the moment; they did the work months earlier, continuously, in a system built to hold General Payments, Research Payments, state-law obligations, and the documentation behind every one of them in a single, queryable place. When a request arrives, the answer isn't a project. It's a query.

Compare the two versions of the same request. In a fragmented process, a CMS records request for a specific recipient means pulling the contract from a document repository, the expense receipts from an expense platform, the fair-market-value assessment from wherever legal filed it, and the approval trail from email, then manually confirming all four actually describe the same transaction before anyone can respond. In a unified system, that reconciliation already exists, because it was built at the moment the record was created rather than assembled after the fact. The 30-day response window proposed under CMS's 2026 rulemaking is workable in the second version. It's a scramble in the first.

Moving From Annual Project to Standing Capability

Transparency Reporting is built specifically to track federal Open Payments, state transparency and gift-ban statutes, and EFPIA obligations in one calendar rather than as parallel spreadsheets that drift out of sync with each other. Compliance Central centralizes the documentation trail across both General and Research Payment data, so every submitted record, and every correction, stays linked to its source. EngageAgent feeds clean HCP and grants engagement data into that same system at the point of creation, which is the only point at which fixing an error is actually cheap.