> ## Documentation Index > Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Types of Differences and Actions Needed The [Differences Report](reconciliationReport) shows any differences that exist between the Merchant's data and Partner Ecosystem Management's (MarketONE OpenAPI) data. The report also indicates if any action is required to resolve the differences. This page explains the types of issues and differences in the report as well as the actions that need to be taken to resolve them. ## Missing Partner Subscriptions * **Partner Subscriptions missing from the Merchant**: This scenario occurs when the MarketONE API has a Partner subscription entry but the Merchant doesn't have one. This often indicates the MarketONE API did not send the callback event or the Merchant didn't process the event. MarketONE will re-send the [Add Subscription callback](https://docs.saas.amdocs.com/bundle/MarketONEOTTServiceCallbacks/page/index.html#tag/Add-Subscription-callback) to the Merchant when this occurs. The Merchant should accept the callback and update the entry on their side. **Note:** If the subscription entry was missing because the Partner subscription was in a CANCELLED state, the Merchant should still accept the Add Subscription callback and update the entry on their side. * **Partner Subscriptions missing from MarketONE**: This scenario rarely occurs because the MarketONE API always initiates Partner subscription provisioning. If this scenario happens, the Merchant should remove the entry, or the Merchant should contact Partner Ecosystem Management Customer Technical Support to discuss the steps that need to be taken. ## Differences in Partner Subscription Data This happens when the Partner subscription exists in both the Merchant's and Partner Ecosystem Management's systems, but the data the Merchant provided for the Partner subscription is incorrect. Partner Ecosystem Management only requires the Merchant to correct Product Code mismatches and certain Partner Subscription Status mismatches so that Partner Ecosystem Management's system stays synchronized. Partner Ecosystem Management doesn't require any action for differences in dates (that is, dates created, activated, updated, or canceled). The types of differences in Partner Subscription data include: * **Differences in External Partner Subscription ID**: The Merchant is the source of truth for the External Partner Subscription ID. If the value is different between the two systems, MarketONE will change the value to what the Merchant provided in the Reconciliation Report. No action is required by the Merchant. * **Differences in Product Code**: The MarketONE API is the source of truth for the Product Code unless the Merchant allows product updates from their side. The Merchant needs to change their Product Code to match the value in the MarketONE API or request that MarketONE resend an update request. * **Differences in Partner Subscription Status**: | Merchant Status | MarketONE OpenAPI Status | Merchant Action Required | Resolution | | - | - | - | - | | ACTIVE | INACTIVE | Yes | The Merchant should re-send the Activation call to the MarketONE API. This will ensure that the Partner subscription status is captured accurately on Partner Ecosystem Management's side. | | ACTIVE | CANCELLED | No | MarketONE will re-send the Delete Subscription callback to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | ACTIVE | PAUSED | No | MarketONE will re-send the Pause Subscription callback to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | INACTIVE | ACTIVE | No | MarketONE will change their status to reflect the Merchant's status. | | INACTIVE | CANCELLED | No | MarketONE will re-send the Delete Subscription callback to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | INACTIVE | PAUSED | No | MarketONE will re-send the Pause Subscription callback to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | CANCELLED | ACTIVE | Yes | The Merchant should re-enable the Partner subscription/user entitlement.**Note:** This scenario may occur when Merchant-initiated cancellations are supported. If Merchant-initiated cancellations aren't supported, this state should generally not occur. | | CANCELLED | INACTIVE | Yes | The Merchant should re-enable the Partner subscription/user entitlement.**Note:** This scenario may occur when Merchant-initiated cancellations are supported. If Merchant-initiated cancellations aren't supported, this state should generally not occur. | | CANCELLED | PAUSED | No | MarketONE will update their status to reflect the Merchant's status.**Note:** This scenario may occur when Merchant-initiated cancellations are supported. If Merchant-initiated cancellations aren't supported, this state should generally not occur. | | PAUSED | ACTIVE | No | MarketONE will re-send the [Resume Subscription callback](https://docs.saas.amdocs.com/bundle/MarketONEOTTServiceCallbacks/page/index.html#tag/Resume-Subscription-callback) to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | PAUSED | INACTIVE | Yes | The Merchant should re-enable the Partner subscription/user entitlement.**Note:** This scenario may occur when Merchant-initiated suspensions are supported. If Merchant-initiated suspensions aren't supported, this state should generally not occur. | | PAUSED | CANCELLED | No | MarketONE will re-send the Delete Subscription callback to the Merchant for this Partner subscription. The Merchant should accept the callback and update their status accordingly. | | CANCELLED | CANCELLATION-IN-PROGRESS | No | MarketONE will update their status to reflect the Merchant's status. | | PAUSED | PAUSE-IN-PROGRESS | No | MarketONE will update their status to reflect the Merchant's status. | | ACTIVE | RESUME-IN-PROGRESS | No | MarketONE will update their status to reflect the Merchant's status. | | INACTIVE | RESUME-IN-PROGRESS | No | MarketONE will update their status to reflect the Merchant's status. | | INACTIVE | UNPROVISIONED | No | MarketONE will update their status to reflect the Merchant's status. | | ACTIVE | UNPROVISIONED | No | MarketONE will update their status to reflect the Merchant's status. | | **Parent topic:**[Reconciliation and Differences Reports](reconciliationReport) | | | | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.