2025.10: Transfer of value

Unless mentioned otherwise, the below updates will be available starting October 7, 2025.

Onomi 360

Transfer of value (v1.0)

Every transfer of value (ToV) your events create, a dinner, a flight, a speaker fee, ends up in a disclosure.

Onomi 360 attributes each amount to the individual healthcare professional (HCP) who received it. It does so at the point when the cost is known.

The disclosure you file downstream rests on a record that never needed rebuilding.

New

• Attribution at source, from budget actuals. Onomi's ToV per-attendee allocation attributes every unit of hospitality, travel, and fees to the individual HCP. It works directly from the budget actuals recorded on the event. Every cost that is not attributed to a disclosable recipient goes to the event's unattributed remainder. You can see it in review, and it is never silently distributed. The remainder includes:
  • A no-show's cancellation fee.
  • An individual cost booked for someone who did not attend.
  • An individual cost line with nobody named on it.
  • A line excluded with a recorded reason.
  • The costs of attendees outside the ToV-relevant types.
  • The share of a shared cost falling to an attendee with an unresolved identity.
  • The whole of a shared cost on an event where no attendee recorded present has a ToV-relevant registrant type.
• Virtual meetings on the same terms. A virtual advisory board or a webinar speaker fee creates transfers of value exactly as a dinner does. Onomi allocates them the same way: per attendee, from the same budget, into the same reporting. No separate process and no separate record applies to them.
• Identity resolved underneath. Onomi resolves registrants and captured leads to one master HCP identity. It does this at registration and at the point of capture. It matches against the IDs you already trust: Veeva ID, OneKey, and NPI. The person behind each record is established when the record is created, not reconciled when the report is due. For how this works today, see Quicker, enriched, CRM-ready registrations with HCP identity resolution. For capture at congresses, see SpotMe/Onomi CongressIQ: Universal lead capture and completing captured lead profiles via real-time identity resolution. Our implementation team sets up resolution against your HCP master. Contact your SpotMe Account Manager to set it up for your program.
• Structured for the systems you disclose from. The allocation sorts each amount into the platform's three cost categories. They are hospitality, travel and accommodation, and fees for service. You get each amount with the recipient it is filed on, the attendance record behind it, and the cost line it came from. Your transparency system maps those three onto the disclosure categories of the frameworks you file under. Those are the itemisation the EFPIA disclosure code works in, or the nature-of-payment values US Open Payments requires.
• Confirmed by finance, corrected in versions. The event's finance owner confirms the allocation. Confirmation is blocked while any line rests on an unresolved identity. The line is resolved, or the finance owner excludes it with a recorded reason. An excluded amount moves into the unattributed remainder. You can see the reason and the user who excluded it in review, as well as on the audit trail.
• Consolidated per-country handoff. The disclosure handoff delivers allocated spend to your finance team. It also feeds the transparency systems that file your country disclosures. The spend rests on the recorded attendance behind it. It is consolidated per country, on the disclosure basis your transparency process defines. Every row shows the HCP's country of practice and the event country. Amounts are in the event currency, with conversion downstream. The handoff arrives complete with its audit trail (Available December 10, 2025).

Important: Onomi does not generate country disclosure filings. Publishing belongs in the transparency systems you already run and have validated.

The platform delivers structured, allocated cost and attendee data to those systems over integration. The filing step then consumes a finished record instead of assembling one.

For an overview and step-by-step setup, see How to manage transfer of value on your events.

* Onomi 360 MeetingsEQ exclusive capabilities.