How CTFM Keeps You Audit-Ready for Sunshine Act Reporting, All Year

Every payment a sponsor makes to a physician or teaching hospital in the US eventually has to be reported to CMS under the Sunshine Act. Most clinical finance teams know that much. Fewer know the actual mechanics well enough to see where their own reporting risk really sits so before getting to how CTFM handles it, it's worth being precise about what the requirement actually is.

What the Sunshine Act actually requires

The Physician Payments Sunshine Act became law in 2010, as Section 6002 of the Affordable Care Act, and CMS administers it through the Open Payments program. It applies to "applicable manufacturers" of drugs, devices, biologics, and medical supplies covered by Medicare, Medicaid, or CHIP, along with group purchasing organizations. The list of who counts as a "covered recipient" has grown over time: it started with physicians and teaching hospitals, and now also includes physician assistants, nurse practitioners, clinical nurse specialists, certified registered nurse anesthetists, anesthesiologist assistants, and certified nurse-midwives.

What counts as a reportable payment is broad — consulting fees, compensation for services, gifts, meals and entertainment, travel and lodging, education, royalties, ownership or investment interests, and research payments all fall under it. Manufacturers collect this data across the calendar year, submit it to CMS by the following March, and CMS makes it public not long after — with a window beforehand where physicians can review and dispute what's been reported about them before it goes live.

Why research payments are treated differently

This is the part that matters most for clinical trial finance specifically. A research payment isn't reported the same way as a speaking fee or a dinner. It's listed separately on the public Open Payments site, with extra context attached: the name of the study, the product or products under investigation, and optionally the ClinicalTrials.gov identifier. That separation exists on purpose a well-documented investigator payment for running a rigorous, IRB-approved trial shouldn't read, to a member of the public browsing the database, the same way a gift or a consulting fee does.

The tradeoff is that research payments carry a heavier documentary burden than other categories. It's not enough to report an amount. You have to be able to show which study, which product, and which specific clinical event justified that payment for every site, for every payment, for the entire reporting year.

It doesn't stop at the federal requirement

Some states layer their own transparency rules on top of the federal one. Vermont's gift ban and disclosure law actually predates the Sunshine Act. Minnesota, Massachusetts, West Virginia, Nevada, Washington D.C., California, and Connecticut all have their own additional requirements, some covering payment categories the federal rule doesn't. For a sponsor running a multi-site U.S. trial, "Sunshine Act compliance" is rarely just one report — it's a small patchwork of overlapping obligations, each with its own detail requirements.

The pain: reconstructing a year of payments at reporting time

Here's where the requirement collides with how most systems are actually built. Showing that a payment traces back to a specific clinical event — the visit, the milestone, the study requires payment data and clinical data to already be connected. On most stacks, they aren't. Payments live in one system, the clinical activity that triggered them lives in another, and by the time the annual reporting deadline arrives, someone has to manually stitch the two back together — payment by payment, site by site, across a full year of activity. It's slow, it's error-prone, and it turns a routine compliance requirement into a once-a-year fire drill.

What CTFM does

Every site payment traces back to the clinical event that triggered it, because CTMS and CTFM share one record instead of two disconnected ones. Nothing needs to be reconstructed at reporting time because the connection was never lost in the first place — it's built in, from accrual through payment, with a complete audit trail attached to every financial action along the way.

That same traceability supports more than just Sunshine Act. Global regulations from FDA's 21 CFR Part 11 to EU transparency equivalents all demand the same thing: documentation and real-time auditability, not a reconstruction exercise after the fact.

Why this matters beyond the deadline

A transparency report built from a system that already knows the answer isn't really a report — it's an export. The alternative is a report built under deadline pressure, assembled from memory and disconnected spreadsheets, with all the risk that implies if a number doesn't hold up to scrutiny.

Transparency shouldn't be something you produce once a year. It should be something the system already has, all year round.

See how CTFM keeps you audit-ready for Sunshine Act reporting, continuously. [Book a demo →]