The worst moment in a speaker bureau year is not a cancelled dinner program. It is the Thursday a compliance officer opens the quarterly spend file and finds a speaker who crossed their Fair Market Value (FMV) cap two events ago. The honorarium has already been paid. The Open Payments clock is already running. The only remaining job is reconstruction: which events, which invoices, which exception — and why nobody stopped the third booking.
That is a monitoring problem, not a rate-card problem. Most teams already have FMV rates. What they do not have is a way to see a speaker's remaining cap before the next contract is signed.
Quick answer. A speaker bureau is the operating system behind HCP speaker programs: who is contracted, which events they can take, what they are paid, and how that spend is documented. FMV monitoring is the part that keeps each speaker inside the company's annual, quarterly, and per-event caps. Spreadsheet audits find a breach after payment. A working bureau watches the cap in real time, warns before the line, and blocks the payment that would cross it.
What a pharma speaker bureau actually is
A speaker bureau is the contracted faculty a pharmaceutical, biotech, or medical device company uses for company-sponsored educational programs. The speakers are healthcare professionals. The company pays them an honorarium, often plus travel, and the attendees are other HCPs. The Office of Inspector General (OIG) uses that same definition in its November 2020 Special Fraud Alert on speaker programs.
The bureau is the roster plus the rules. Profiles, training status, contracts, event assignments, attendance, invoices, and spend against FMV all have to live in one place, or they get reconciled after the fact. Medical Affairs runs advisory boards, grand rounds, and scientific programs off a similar stack. Commercial teams run dinner programs and peer-to-peer speaker events. The event type changes. The payment physics do not.
That distinction matters for searchers too. "Speaker bureau" is the faculty and the rules. "Speaker program" is a single event. Software that only books rooms is not bureau software. Software that cannot see a speaker's year-to-date spend is not compliance software, even if the landing page says it is.
Why FMV is the part that actually fails
FMV is the documented rate a company will pay an HCP for a defined service — speaking time, prep hours, sometimes travel time — based on credentials and the work, not on prescribing volume. The PhRMA Code on Interactions with Health Care Professionals (Section 7, effective 1 January 2022) is explicit: speaker compensation must be fair market value, and it must not take into account the volume or value of past or potential business from that HCP. AdvaMed's code makes the same demand on the device side.
OIG listed "pays HCP speakers more than fair market value" as a suspect characteristic of a speaker program that could implicate the Anti-Kickback Statute. The same alert noted that drug and device companies reported nearly $2 billion in speaker-related HCP payments across 2017–2019 in the Open Payments category for non-consulting speaker compensation. That is not a 2026 run-rate. It is the number OIG used to explain why this channel is watched.
Setting the rate is the methodology problem. Consultancies write about that: specialty surveys, tiering, geographic adjustments. The operational failure is different. A speaker can be on a defensible rate card and still blow an annual cap because three brands, two agencies, and a Medical Affairs team each booked them without seeing the others' spend.
PhRMA's 2022 update also tightened the event itself — no company-provided alcohol, modest incidental meals, no luxury venues, no guests without an educational need, no repeat attendance at substantially the same program. Those rules are about the room. FMV monitoring is about the speaker's year. Teams that treat them as one spreadsheet line learn the difference at audit.
The quarterly file is a lagging indicator
Here is the sequence that produces the Thursday surprise.
A speaker is contracted in January at a tiered rate. Brand A books them for a February dinner program. Medical Affairs books them for a March advisory board. An agency running a launch series books them twice in April. Each booking looks fine in isolation. Honoraria are calculated correctly. Invoices go out. Finance pays. Nobody is looking at the running total against the annual cap, or they are looking at a shared sheet that was last updated after the previous event closed.
The cap is crossed on the third or fourth payment. The breach is discovered when someone compiles the quarter. By then the options are ugly: claw back a payment from an HCP, file an exception after the fact, or sit with a record that will have to be explained if anyone asks.
OIG's suspect list includes paying more than FMV and selecting speakers based on past or expected revenue. A cap breach is not automatically either of those. It is still the record you least want to reconstruct from email. CMS Open Payments will reflect the transfers of value you actually made. The reporting obligation does not wait for your quarterly cleanup.
This is why speaker bureau owners talk about FMV as a preventive control. A rate card is a policy. A dashboard that warns at 80% of cap and refuses the payment at 100% is the control. The exception, if there is one, should be a named compliance officer decision with a reason attached — not a silent overage that someone notices in July.
If the failure mode you just recognized is "we find the overage after we have paid," the useful next look is the workflow, not another rate-card workshop.
What real-time FMV monitoring has to do
A monitoring stack that is worth the login does five things. Miss one, and you are back to the quarterly file.
1. One running total per speaker, across every event type. Dinner programs, advisory boards, grand rounds, and conference faculty should hit the same cap. If Medical Affairs spend lives in one system and Commercial speaker spend lives in another, the cap is fictional.
2. Caps you can actually configure. Annual, quarterly, and per-event limits, by speaker tier. A Tier 1 national faculty member and a regional speaker should not share a hidden default. The rules have to be the company's rules, not the vendor's.
3. A warning before the line, and a block at the line. Soft warning around 80% of cap is enough time to reroute a booking or open an exception. A hard block at 100% is what stops Finance from paying a breach. Alerts that only email after the invoice is gone are reporting, not monitoring.
4. Honoraria that calculate from the contract, not from memory. Prep hours plus service hours at the contracted rate, plus the travel policy you actually use. If a coordinator is typing the fee into the invoice, the dashboard is only as honest as that typo.
5. An exception path with a name on it. Launch weeks produce legitimate "we need this speaker" cases. Those should be a compliance-officer review with a documented rationale, not a quiet override in a spreadsheet cell. If the platform cannot show who approved the exception, you do not have an audit trail. You have a story.
TikaMSL's speaker bureau module is built around that sequence: a real-time FMV dashboard with color-coded progress against the cap, configurable annual / quarterly / per-event thresholds by tier, a warning at 80% and a payment block at 100%, one-click invoices from completed events, and an HCP portal where the speaker confirms or disputes the invoice before Finance approves. Every action is written to an automatic audit log. Training-expiration alerts sit next to the spend view, because a speaker who is over cap and out of training is two problems, not one.
That is the product. It is not a claim that no other vendor tracks spend. ExtendMed, IQVIA Expert Events, and several HCP-engagement platforms describe FMV or aggregate-spend tracking on their own sites. The question to ask in a demo is narrower: does the system stop the payment, or does it export a file that tells you later?
What to ask before you trust a speaker bureau platform
Use these in a vendor meeting. They work whether you are looking at TikaMSL, a managed-service bureau, or a Veeva-adjacent events tool.
- When a speaker is at 82% of their annual cap, what happens on the next booking — a warning, a hard stop, or nothing until someone exports a report?
- Do Medical Affairs events and Commercial speaker programs share one cap, or do we reconcile two systems at quarter-end?
- Is the honorarium calculated from the contract (prep + service hours), or does a coordinator enter the fee?
- Can the speaker see and confirm the invoice themselves, or are we still emailing PDFs?
- If compliance approves an exception, where does that decision live, and who can see it later?
- What is live for Sunshine Act / Open Payments export today, versus on the roadmap? Ask for the current export, not the slide.
The last question is there on purpose. Several vendor pages blur "audit-ready spend data" with "we file Open Payments for you." Those are different jobs. Monitoring and a clean payment ledger are what make reporting possible. Automated CMS export is a separate capability. Treat a roadmap item as a roadmap item.
Where this still breaks even with software
Real-time caps do not fix a sloppy bureau. If speakers are selected because they write a lot of the product, the OIG problem is upstream of the dashboard. If the same HCP attends the same program twice, PhRMA's repeat-attendance rule is an event-design problem. If alcohol is on the tab, no FMV bar chart will help you.
There is also a capacity edge. A small biotech running twelve programs a year can survive a shared sheet if one person owns it and every booking goes through them. The sheet fails when a second brand, an agency, or a new Medical Affairs hire starts booking in parallel. That is usually the year someone asks for software — after the first messy quarter, not before.
Device programs have the same FMV math and a different code (AdvaMed). If the company sells both drugs and devices, confirm the platform can hold two policy sets without a second database.
How this connects to the rest of Medical Affairs
Speaker faculty are often the same people sitting in your KOL list. If the bureau roster and the KOL record disagree on tier, specialty, or whether training is current, field teams and the bureau will make different decisions about the same HCP. That is why speaker bureau operations belong next to KOL management, not in an events tool that never sees the relationship history.
The same argument showed up in TikaMobile's MSL CRM comparison: FMV and speaker-program compliance are part of whether a medical affairs platform is actually used, or whether the bureau keeps living in a side system. Teams that buy a CRM for KOL engagement and leave speaker logistics in a spreadsheet are running two truths about the same faculty.
Frequently asked questions
What is speaker bureau FMV monitoring?
Speaker bureau FMV monitoring is the practice of tracking each HCP speaker's payments — honoraria, and any other transfers of value the company counts toward the cap — against documented Fair Market Value limits in real time. The point is to warn or block a booking or payment before a cap is exceeded, rather than discovering the overage in a quarterly audit.
How is a speaker bureau different from a speaker program?
A speaker program is one event. A speaker bureau is the contracted faculty and the rules that govern every event those faculty can take: onboarding, training, FMV rates, caps, invoicing, and documentation. Software that schedules one dinner without a running spend total is program logistics, not bureau management.
What FMV caps do speaker bureau teams usually set?
Most companies set some mix of annual, quarterly, and per-event caps, often varied by speaker tier. The exact numbers are internal policy. What matters operationally is that every event type that pays the same HCP hits the same running total, and that someone is accountable for exceptions.
Does FMV monitoring replace Sunshine Act / Open Payments reporting?
No. Open Payments is the federal transparency report of transfers of value to certain HCPs and teaching hospitals. FMV monitoring is the internal control that keeps those payments inside company policy. You still have to report what you paid. Monitoring reduces the chance that what you paid is something you did not intend to pay.
When is a spreadsheet still acceptable?
When program volume is low, one person books every speaker, and Medical Affairs and Commercial are not independently contracting the same faculty. The sheet breaks as soon as two teams can create a paid event without seeing each other's spend.
See the monitoring workflow, not another rate card
If your current process finds cap issues after Finance has paid, a 20-minute walkthrough is the faster test than another policy review. TikaMSL's speaker bureau module shows the FMV dashboard, the 80%/100% guardrails, invoice confirmation through the HCP portal, and the exception path in one pass — next to the KOL record, not in a side database.
Book a 20-minute speaker bureau walkthrough →
Related: Speaker bureau software · KOL management · What is a KOL? · Best MSL CRM software (2026)
Citations
- U.S. Department of Health and Human Services, Office of Inspector General. Special Fraud Alert: Speaker Programs (16 November 2020). https://oig.hhs.gov/documents/special-fraud-alerts/865/SpecialFraudAlertSpeakerPrograms.pdf
- Pharmaceutical Research and Manufacturers of America. Code on Interactions with Health Care Professionals, Section 7 (effective 1 January 2022). https://cdn.aglty.io/phrma/global/resources/PhRMA%20Code%20-%20Final.pdf
- Sidley Austin LLP. "PhRMA Updates Code Principles on Company-Sponsored Speaker Programs" (August 2021). https://www.sidley.com/en/insights/newsupdates/2021/08/phrma-updates-code-principles-on-company-sponsored-speaker-programs
- Centers for Medicare & Medicaid Services. Open Payments. https://www.cms.gov/openpayments
- TikaMobile. Speaker Bureau & Event Management Software (product page, retrieved 14 September 2026). https://www.tikamobile.com/medical-affairs/speaker-bureau
