> ## 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.

# Reconciliation

## Overview

Reconciliation is a process that allows Merchants to view and resolve differences in subscription data that exist between the Merchant's and Partner Ecosystem Management's systems. Reconciliation helps the Merchant's system get back to a synced state after issues have occurred. Reconciliation Reports can also help Merchants gain insight into product sales trends.

**Note:** This process is available to Merchants who partner with Resellers (Service Providers), enabling Resellers to sell their products on their behalf.

## Files Involved in Reconciliation

Reconciliation involves an exchange of the following files via SFTP:

1. [Reconciliation Report](reconciliationReport): This file contains product subscription data. The Merchant generates and uploads this file for Partner Ecosystem Management.
2. [Differences Report](reconciliationReport): The Differences Report lists any differences found in Partner Ecosystem Management's system. The report also indicates whether action needs to be taken to resolve the difference. An empty Differences Report is generated if no differences are found. The Merchant receives this file from Partner Ecosystem Management within 24 hours of uploading the Reconciliation Report. See [Types of Differences and Actions Needed](reconciliationDifferences) for information about differences and actions needed.

## Steps to Complete Reconciliation

## Recommendations for Adoption

Our team strongly recommends that new Merchants adopt the Reconciliation process as part of their onboarding certification to Partner Ecosystem Management. It is also strongly recommended for existing Merchants to adopt the Reconciliation process as part of their upcoming releases. Exceptions may apply and are determined on a case-by-case basis.

Though Resellers (Service Providers) don't directly use Reconciliation, they rely on Merchants' regular completion of this process. Reconciliation ensures Partner Ecosystem Management manages customer subscription statuses as expected. The process ensures that related entitlements are managed correctly and subscription status is correct for accounting purposes.

## Detailed Reconciliation Process

<img src="https://mintcdn.com/amdocs-spbu/iaNCbihVGQakUR0-/marketONE/userGuideForResellers/images/ReconciliationWorkflow.png?fit=max&auto=format&n=iaNCbihVGQakUR0-&q=85&s=0f43861014d8a32e4c6ff4b234429a1a" alt="Reconciliation Process" width="1573" height="1060" data-path="marketONE/userGuideForResellers/images/ReconciliationWorkflow.png" />

The steps in the Reconciliation process are:

1. The Merchant and a Reseller (Service Provider) establish a partnership and create an agreement. Customers buy subscriptions.
2. The Merchant configures their SFTP settings
3. The Merchant creates a Reconciliation schedule
4. The Merchant reconciles the data via SFTP, which involves the following:
   1. The Merchant generates a Reconciliation Report
   2. The Merchant uploads the report to the designated SFTP location
   3. Partner Ecosystem Management generates a Differences Report within 24 hours. The Differences Report shows any differences in subscription data that exist between the Merchant's system and Partner Ecosystem Management's system. The Merchant needs to download this report from the provided SFTP endpoint.
   4. One of the following outcomes occurs:
      1. If the file contains differences, the Merchant and/or Partner Ecosystem Management need to take action to resolve the differences.
      2. If the file is empty, there are no differences and no further action is required.
   5. Within 48 hours of receiving the Differences Report, the Merchant should make all the required updates on their side.
   6. The Merchant repeats steps A-F until the Differences Report is empty and no further action is required.

* **[Reconciliation and Differences Reports](reconciliationReport)**

**Parent topic:**[Platform Settings](r_platformSettingsAbout)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.