Beacon MFP Frequently Asked Questions

What is Beacon?
​

Beacon is an innovative technology platform that enables the Maximum Fair Price (MFP) program by ingesting, validating, pricing and transmitting MFP rebate requests. Dispensing entities utilize Beacon to research MFP rebate status, reconcile MFP refund payments and initiate good faith inquiries (GFI). Beacon is made available to dispensing entities at no cost by pharmaceutical manufacturers and is a distinct technology platform from the Medicare Transaction Facilitator (MTF).

How is the Beacon platform different from the MTF platform and does my dispensing entity need to utilize both platforms?

The MTF is a technology platform operated by a government contractor that originates MFP rebate requests and facilitates payment of MFP refunds to dispensing entities. Dispensing entities must register with the MTF and provide payment details in order to receive MFP refund payments.

Beacon is a technology platform made available to dispensing entities at no cost to support the effectuation of the MFP as a rebate payment. Dispensing entities can register with Beacon and view the current status of MFP rebates for MFP eligible prescriptions fulfilled by the dispensing entity. Beacon provides dispensing entities detailed information on the rebate status and basis of pricing for the MFP refund amount. Dispensing entities can also use Beacon to initiate good faith inquiries related to the MFP rebate amount for specific MFP rebate requests

Does Beacon facilitate payment of MFP refunds?

No, Beacon does not process MFP refund payments and dispensing entities do not need to provide bank account information to Beacon as part of the registration process. Beacon processes MFP rebate requests originated by the MTF, validates the MFP rebate request for eligibility, determines the MFP refund amount and transmits the adjudicated MFP rebate to the MTF. Using the adjudicated MFP rebate record transmitted by Beacon, the MTF withdraws funds from the appropriate pharmaceutical manufacturer account(s) and processes payment to the dispensing entity.
​

Does my dispensing entity need to register an account with Beacon if it already has an account with the MTF?

Dispensing entities are not required to register an account with Beacon in order to receive MFP refund payments. Account registration is required if the dispensing entity elects to submit a GFI regarding a specific MFP rebate request as Beacon processes all GFIs for pharmaceutical manufacturers. Dispensing entities may also choose to register a Beacon account in order to access more detailed information on the MFP rebate status and basis of pricing.

How do Beacon’s MFP and 340B rebate model platforms interact with each other?
​
Beacon supports both the MFP program and the 340B rebate model pilot program through distinct but related technologies. Because the underlying user base is different (i.e. MFP applies to any dispensing entity that dispenses a Part D prescription for an MFP eligible patient and drug while the 340B rebate model applies solely to 340B covered entities that purchase a 340B rebate eligible drug). Because the technologies perform very different functions (i.e. Beacon MFP processes MFP rebate requests while Beacon 340B processes 340B rebate payments), users register for and engage with each platform independently. However, data submitted to Beacon’s 340B rebate model platform is integrated into Beacon’s MFP platform and utilized to appropriately price MFP rebate requests.

I have already registered for Beacon’s 340B rebate model platform. Can I use my Beacon 340B rebate model credentials to log in to Beacon’s MFP platform?

Dispensing entities must register with Beacon’s MFP platform regardless of their enrollment status with Beacon’s 340B rebate model platform or any other Second Sight technology. Registration with Beacon’s MFP platform requires much of the same documentation utilized with the 340B rebate model platform so Beacon 340B rebate model users should be able to readily complete the registration process.

How do I register a Beacon account?
​
Dispensing entities can register a Beacon account by navigating to the registration page at mfp.beaconchannelmanagement.com. Registering users are first asked to provide basic contact information and select one or multiple dispensing entities that they are authorized to register. Following verification of the provided contact details, registering users provide documentation to establish registration authorization. After verification of the documentation, the registered administrator can invite other users and perform other account configurations. For a step-by-step tutorial on successfully completing the Beacon registration, visit the Beacon Support Center.

Does Second Sight require that my entity registers for the Beacon MFP and 340B rebate model platforms with the same authorized user?

Second Sight recognizes that organizations may be structured such that different individuals are responsible for administering the MFP and 340B rebate model programs. As a result, the same individual that registered an account on Beacon’s 340B rebate model platform is not required to register the account with Beacon MFP. However, there is no requirement that different individuals register each account and a dispensing entity may chose to have the same individual register both the Beacon MFP and Beacon 340B rebate model accounts.

Can my consultant or TPSE complete the Beacon registration on my dispensing entity’s behalf?

Dispensing entities may have a third party register an account on their behalf assuming appropriate authorization has been established between the dispensing entity and third party. The individual registering an account for a dispensing entity must have all required information and documentation in order to successfully complete the registration process. Additional information regarding what is required to complete the Beacon registration process is available in the Beacon Support Center as well as in the following FAQs.

What information is required to register an account with Beacon and how long does it take?

Dispensing entities can register an account with Beacon free of charge. A registering user must first establish affiliation with the dispensing entity by providing an EIN, IRS letter (CP575) with the entity address, and Articles of Incorporation (or similar documentation) for the dispensing entity. This information is validated by a third party adhering to Know Your Business standards, typically within 5 business days of submission. Once validated, the registering user establishes their Beacon account credentials and sets up their Multi Factor Authentication (MFA). Following successful enrollment of a dispensing entity, the registering user or another user established as an Administrator on the enrollment can invite other individuals to register for the account without providing the documentation noted above.

Does my dispensing entity have to register each dispensing pharmacy location independently if they are all part of the same organization?

Consistent with how CMS has communicated it manages enrollment with the MTF, Beacon relies on the NCPDP Relationship ID to determine which pharmacy locations must be registered individually. If a pharmacy location is registered with NCPDP without a Relationship ID, the dispensing entity must register independently. However, if multiple pharmacy locations are all registered with NCPDP under the same Relationship ID, all of the pharmacy locations are registered at once as a single entity.

Once a dispensing entity is registered, an account administrator can group together multiple dispensing entities under a single account. Within Beacon, a single NCPDP Relationship ID necessitates a single registration and is referred to as a ‘Corporation’. A Corporation may have a single pharmacy location or multiple pharmacy locations depending on whether pharmacy locations have been logically grouped together in NCPDP using the Relationship ID. A single user can register multiple Corporations and then group them together in Beacon as an ‘Organization’. Depending on the complexity of any particular chain of pharmacies, a single registered user can establish multiple Organizations in Beacon, each with multiple Corporations. Once established, an administrator user can move Corporations across Organizations within their account for purposes of managing their administration of the MFP program within Beacon.

How do I find my dispensing entity within Beacon for registration?
​
Beacon relies on NCPDP registration information to establish the Corporations within Beacon that a user may register. Pharmacies with distinct national provider IDs (NPIs) that are registered individually within NCPDP and do not have a Relationship ID are listed as distinct Corporations within Beacon and can be searched for using either the pharmacy name or the NPI as listed in NCPDP. These Corporations must be registered individually in Beacon even if there is a legal relationship between the pharmacies that is not reflected in NCPDP through the use of a common Relationship ID.
​

Pharmacies that are logically grouped together within NCPDP using the Relationship ID are listed as a single Corporation in Beacon and can be searched for using the pharmacy name or Relationship ID. Users that register a Corporation within Beacon that equates to a single Relationship ID in NCPDP will automatically register all of the individual pharmacy locations that are grouped together in NCPDP under the single Relationship ID.

How are MFP rebate requests originated?

The MTF originates all MFP rebate requests based on Medicare Part D utilization data that are provided by Part D plan sponsors to CMS. The MTF determines which Part D utilization data are MFP rebate eligible and transmits MFP rebate requests to the pharmaceutical manufacturers or directly to Beacon. Neither the dispensing entity nor the pharmaceutical manufacturer is directly involved in the creation of MFP rebate requests.

How does the MFP rebate data in Beacon differ from the MFP rebate data made available by the MTF?

Beacon receives MFP rebate data either directly from the MTF or via the pharmaceutical manufacturer. In its processing, Beacon determines MFP rebate eligibility and the MFP refund amount based on various criteria. Beacon returns processed MFP rebate to the MTF according to the requirements outlined by the MTF. Processed MFP rebate data include all of the original data elements in the MFP rebate request transmitted by the MTF as well as additional fields pertaining to the processing status and refund amount as required by the MTF.

Beacon also makes certain information available to dispensing entities that may not be available through the MTF. Beacon provides detailed information on rebate validation status and the basis of pricing. Dispensing entities can also see the MFP rebate history including dates on which MFP rebate data was received, processed and transmitted back to the MTF. Beacon does not have information on when the MFP rebate payment is actually received by a dispensing entity.

How does Beacon determine MFP rebate eligibility?

Beacon administers pharmaceutical manufacturer policies for MFP rebate eligibility. MFP rebate requests are assessed to ensure all required data elements are properly transmitted by the MTF. Certain data elements may be evaluated to determine MFP rebate eligibility. For example, the national drug code (NDC) may be evaluated to ensure the MFP rebate request is for an NDC subject to the MFP or the date of service may be evaluated to ensure it falls within the MFP eligibility period. Additional information on pharmaceutical manufacturer MFP policies is available in Beacon’s Support Center.

What if my dispensing entity disagrees with an MFP eligibility determination processed in Beacon?

CMS expects that dispensing entities and pharmaceutical manufacturers engage in good faith to resolve any inquiries pertaining to MFP availability. If a dispensing entity disagrees with the MFP eligibility determination processed in Beacon, the dispensing entity should utilize Beacon’s Resolution Center to initiate a GFI. Additional information on initiating a GFI and the Resolution Center generally is available in Beacon and additional FAQs on GFIs are available in this document.

What MFP rebate request data is accessible in Beacon?

Dispensing entities that have registered with Beacon can access all MFP rebate data associated with their registered pharmacy locations. Dispensing entities can see a list of all NPIs registered with their account by navigating to the Organizations module, selecting an Organization profile and viewing the list of pharmacies in the Pharmacies tab. Beacon is used for all of the products selected for inclusion in the MFP program for 2026 and MFP rebate data is accessible for each of these products in Beacon. MFP rebate data is available for rebate requests that are in process as well as rebate requests that have been approved or denied.

Can dispensing entities reverse MFP rebate requests in Beacon?
​
Beacon does not provide functionality that allows a dispensing entity to reverse an MFP rebate request. Dispensing entities should instead process a claims reversal directly with the Part D plan sponsor. This claim reversal should be transmitted by the Part D plan sponsor to CMS at which point the MTF will initiate a reversal of the MFP rebate request.

Does Beacon support updates to inaccurate MFP rebate data?
​
Beacon does not provide functionality that allows a dispensing entity to update inaccurate data elements of an MFP rebate request. The MTF does not permit pharmaceutical manufacturers or Beacon to modify any data element of an MFP rebate request. Dispensing entities should instead engage directly with the MTF to correct any data elements that it believes are inaccurate.

What data and reporting is available in Beacon MFP for dispensing entities and how frequently is it updated?

Rebate details such as the total rebates, processing status, and basis of pricing will be available to download in reports where users can interact with the rebate data. For data elements that manufacturers or Beacon originate (e.g., 340B information, payment data elements, basis of pricing, etc.), the Beacon platform is updated in near real-time. For data the MTF originates (e.g., initial rebate data, MRR), Beacon relies on the MTF’s timeline for updating the information. Additionally, information about the corporation, organization structure, and users is available in the platform in real time.

How are MFP rebate payments effectuated?

CMS has authorized the MTF to make MFP rebate payments to dispensing entities on behalf of pharmaceutical manufacturers. Dispensing entities can register with the MTF and provide information necessary to facilitate electronic MFP rebate payments. Dispensing entities that elect not to provide electronic payment information to the MTF will receive MFP rebate payments by check using the address information provided by the dispensing entity.

How are MFP refund amounts calculated?
​
​CMS guidance obligates pharmaceutical manufacturers to ensure that the MFP is made available to dispensing entities and permits the manufacturers to make the MFP available via an MFP rebate payment. Pharmaceutical manufacturers must determine the MFP refund amount in order to ensure that the MFP is made available to the dispensing entity taking into account any discounts that may have already been made available to the dispensing entity (e.g. 340B). Beacon effectuates pharmaceutical manufacturer policies pertaining to determining the MFP refund amount and information is made available to the dispensing entity in Beacon on the basis of price.

What are the different basis of price methods that are supported in Beacon?

Beacon calculates the per unit MFP refund amount using pricing data provided by the pharmaceutical manufacturer. The per unit refund amount may be based on the wholesale acquisition cost (WAC), a contract price made available via the dispensing entity’s wholesaler or the 340B price. In the event that the WAC, contract price or 340B price is equal to or less than the MFP, the per unit MFP refund amount is set to $0. In the event that the WAC, contract price or 340B price is greater than the MFP, the per unit MFP refund amount reflects the difference between the basis of price and the MFP.

Pharmaceutical manufacturer policy establishes whether the basis of price is WAC, a contract price or the 340B price for any specific MFP rebate request. Dispensing entities can search for an MFP rebate request in Beacon and see the basis of price used to determine the MFP refund amount.

What if my dispensing entity disagrees with the basis of price used by Beacon to calculate the MFP refund amount?

CMS expects dispensing entities and pharmaceutical manufacturers engage in good faith to resolve any inquiries pertaining to MFP availability. If a dispensing entity disagrees with the basis of price used in Beacon to calculate the MFP refund amount, the dispensing entity should utilize Beacon’s Resolution Center to initiate a GFI. Additional information on initiating a GFI and the Resolution Center generally is available in Beacon and additional FAQs on GFIs are available in this document.

What if my dispensing entity disagrees with the unit amount used to calculate the MFP refund amount?

The unit amount is provided by the MTF and Beacon does not adjust the unit amount included in the original MFP rebate request transmitted by the MTF. Dispensing entities should engage directly with the MTF if it believes that the incorrect unit amount was included in the MTF rebate request.

What is a good faith inquiry (GFI)?

CMS expects dispensing entities and pharmaceutical manufacturers to engage in good faith to resolve an issue prior to submitting a complaint to the MTF. CMS specifically states that proof of any efforts to resolve the issue should be submitted to CMS, if a complaint is filed. Dispensing entities that believe the MFP was not made available by a pharmaceutical manufacturer for a specific MFP rebate request, either because the MFP rebate request is denied or because the MFP refund amount is less than the dispensing entity expects, will utilize Beacon to initiate a GFI.

How does my dispensing entity initiate a GFI in Beacon?

CMS guidance states that dispensing entities and manufacturers can submit complaints on an ICN by ICN basis. Beacon mirrors this guidance and enables GFIs to be initiated for individual ICNs. Dispensing entities will first navigate to the Resolution Center in Beacon and initiate the GFI process by searching for an ICN. Users will follow a series of prompts in a “wizard” format to identify the issue pertaining to the specific MFP rebate and submit any required documentation to support the dispensing entity’s position pertaining to the validation status and pricing of the MFP rebate. Beacon’s support team will review the GFI and any supporting documentation and respond to the dispensing entity with any additional questions or documentation requests. In some instances, the GFI may be escalated to the pharmaceutical manufacturer for completion. Dispensing entities will be able to see the current status of the GFI and all associated communication in Beacon.

What happens if my GFI is approved in Beacon?

Following a review of the GFI and supporting documentation, Beacon’s support team may determine that the GFI is approved. For MFP rebate requests that were originally denied, the approval of the GFI will trigger the payment of the entire MFP refund amount which will be processed by the MTF similar to other MFP rebate payments. For MFP rebate requests that were originally approved but at a lower refund amount than the dispensing entity expected, an incremental MFP refund amount will be paid to the dispensing entity via the MTF. In either scenario, the dispensing entity does not need to take further action.

What happens if my GFI is denied in Beacon?

Following a review of the GFI and supporting documentation, Beacon’s support team may determine that the GFI is not approved. Beacon’s support team will update the GFI to provide the rationale for the denial and no action will be taken to update the status or refund amount of the specific MFP rebate request in question. Dispensing entities will continue to have access to the GFI information in Beacon and may elect to pursue a complaint with the MTF. Any communication and documentation reflected in the GFI may be provided to the MTF by the pharmaceutical manufacturer in response to a request for additional information by the MTF.

Can my dispensing entity initiate a GFI utilizing some method other than Beacon?

For products included in the MFP program for 2026, all pharmaceutical manufacturers are utilizing Beacon to support the GFI process. Beacon’s Resolution Center will support all GFIs and dispensing entities will need to register an account with Beacon in order to initiate a GFI.

If my GFI is denied, can my dispensing entity resubmit a GFI for the same MFP rebate request?

Following the denial of a GFI, dispensing entities may elect to submit a complaint with the MTF. If a dispensing entity gains access to additional information that supports the GFI, the dispensing entity should notify Beacon’s support team so that the original GFI can be reopened at which point the dispensing entity may submit the additional documentation for consideration. Dispensing entities will not be able to open a second GFI in Beacon for the same MFP rebate request.

Are there available resources for educating my dispensing entity?

The Beacon Support Center hosts an array of content including educational videos that range in topics from account registration to GFIs, step-by-step guides on utilizing Beacon, and articles that help further elucidate Beacon functionality. Visit the Beacon Support Center to learn more.

How should my dispensing entity educate our TPSEs regarding Beacon?

Dispensing entities should encourage their TPSEs to review the Beacon Support Center. Beacon also hosts recurring working sessions with TPSEs to address questions specific to those entities that are supporting dispensing entities in the effectuation of the MFP program. Second Sight has a dedicated support team that engages directly with TPSEs which can be reached via email at [email protected].

When should my dispensing entity contact Beacon support versus contacting the MTF’s support team?

The Beacon platform is a resource for dispensing entities that enables research into the MFP rebate status and basis of pricing as well as the timing of overall MFP rebate processing. Dispensing entities should utilize Beacon’s Resolution Center to initiate good faith inquiries into specific MFP rebates. Beacon also administers pharmaceutical manufacturer policies pertaining to MFP rebate eligibility and pricing and dispensing entities should contact Beacon with questions related to MFP rebate eligibility and pricing.

The MTF originates all MFP rebates and dispensing entities should engage directly with the MTF in instances where no MFP rebate exists but the dispensing entity believes a prescription was MFP eligible. Similarly, dispensing entities should engage directly with the MTF if the dispensing entity believes certain data elements are incorrect (e.g. quantity dispensed, dispensing pharmacy, date of service, etc.) and to address any questions related to registration with the MTF. After first initiating a GFI in Beacon, dispensing entities should submit any complaints to the MTF regarding the availability of the MFP or the MFP refund amount.

How can my dispensing entity contact Beacon if there are questions?

The Beacon Support team is available via email, phone, or Beacon’s in-platform support messenger. To reach the team by email, please utilize [email protected]. To reach the team by phone Monday to Friday 9am-9pm ET, dial (878)-788-8980. For real-time responses from the Beacon Support team Monday to Friday 9am-9pm ET, utilize Beacon’s in-platform support messenger. This is available in the bottom right corner of the Beacon platform. For inquiries outside of Monday to Friday 9am-9pm ET, users can email the support inbox or create a ticket utilizing the in-platform messenger on Beacon.

How does Beacon ensure the security of submitted data?
​

Beacon supports physical, technical, and operational security protocols that are consistent with industry standard security best practices. This includes secure transfer of data from clients to Beacon (e.g., data-in-transit encryption), secure storage of that data once in Beacon (e.g., data-at-rest encryption), and secure network segmentation designed to ensure that data is protected in the inner most security ring of the Beacon environment. All of that is coupled with a least privilege access control model designed to limit access to data based on need alone. Visit The Beacon Trust Center to learn more about the security protocols in place today.

What type of data encryption does Beacon utilize?

Beacon encrypts all data throughout its lifecycle to ensure data integrity and confidentiality. All data is encrypted at rest with AES-256 encryption using Azure managed keys. Data in Beacon cloud products is encrypted in transit over public networks using TLS 1.2+.

How does Beacon manage access control?

Before registering administrators are associated with a Beacon account, administrators must demonstrate authenticity by providing supporting documentation. This documentation undergoes a third-party review adhering to Know Your Business standards. Once approved, registering users establish a password and a Multi-Factor Authentication that meets Beacon’s stringent criteria.

How does Beacon manage data deletion and retention?

All data associated with Beacon will be retained indefinitely. Any data purge or deletion requests from dispensing entities will be discussed and only approved after written authorization from all impacted parties. Visit The Beacon Trust Center to learn more about Beacon’s data deletion and retention policies.

What technology requirements are necessary to successfully upload data to Beacon?

Users will need an internet connection and access to a supported browser to successfully upload data. Beacon is compatible with most internet browsers including Microsoft Edge, Google Chrome, Safari, and Firefox. However, Beacon strongly recommends using Google Chrome for the best user experience.

How does Beacon protect privacy?

Beacon enforces a robust privacy policy and data safeguard management program to ensure data safety. For more information, visit Beacon’s Privacy Policy.

Are native prescription numbers rendered in Beacon?

The MTF includes native prescription numbers in the MFP rebate data transmitted to pharmaceutical manufacturers via Beacon. Although our system maintains these native data, Beacon does not render the native prescription number to dispensing entities. Instead, Beacon relies on the internal control number (ICN) to uniquely identify an MFP rebate request. Dispensing entities have access to the same ICN data from the MTF and can search for MFP rebates in Beacon using the ICN.