Reconciliation and Differences Reports

Reconciliation Report

The Reconciliation Report contains a snapshot of all the subscriptions Partner Ecosystem Management manages on behalf of the Reseller (that is, Platform-Managed subscriptions). Merchants can generate and send the file to Partner Ecosystem Management via SFTP. Merchants can set a daily, weekly, or monthly schedule for Partner Ecosystem Management to process the file. The Reconciliation Report is a CSV file with the following naming convention: PartnerReconciliation_<Merchant_code>_<Reseller_code>_<StartDate>_<EndDate>_v1.csv where <StartDate> and <EndDate> are in the format of yyyymmddThhmmssZ. This file name is case-sensitive. The start date and end date in the file name indicate the period for which the report is generated (for example, from first to last day of a month). The report contains all the subscriptions that were created, modified, canceled, paused, and resumed in the time period. See the table below for information about report fields. Reconciliation Report Fields The Reconciliation Report has the following fields:

Field Name	Field Format	Field Description	Required or Optional
Aggregator Code	Alphanumeric string	The Reseller’s Organization Code in Partner Ecosystem Management. Partner Ecosystem Management provides this information to the Merchant.	Required
Partner Subscription ID	Alphanumeric string	The subscription’s unique ID in Partner Ecosystem Management.	Required if no Partner Customer ID is provided
External Partner Subscription ID	Alphanumeric string	The subscription ID on the Merchant’s side. Merchants manage this ID and send it back to Partner Ecosystem Management as part of provisioning API response sync call. This ID is only displayed if the Merchant supports the ID.	Optional
Partner Product Code	Alphanumeric string	The product code the Merchant provided. The Merchant provides this code during onboarding.	Optional
Partner Subscription Status	String	The Merchant subscription’s provisioning status as it appears on the Merchant’s side. Valid values include: - INACTIVE - ACTIVE - CANCELLED - PAUSED	Required
Created Date	Date and time (ISO 8601)	The date and time the subscription was created on the Merchant’s side. The format is UTC.	Optional
Last Updated Date	Date and time (ISO 8601)	The date and time the subscription was last updated on the Merchant’s side. The format is UTC.	Optional
Partner Customer ID	Alphanumeric string	The customer’s unique ID in Partner Ecosystem Management.	Required if no Partner Subscription ID is provided
Activated Date	Date and time (ISO 8601)	The date and time the subscription was activated on the Merchant’s side. The format is UTC.	Optional

Differences Report

After a Merchant generates a Reconciliation Report and sends it to Partner Ecosystem Management, Partner Ecosystem Management sends back a Differences Report within 24 hours. The Differences Report shows the differences in subscription data between the Merchant’s system and Partner Ecosystem Management’s system. The Merchant can download the Differences Report from the provided SFTP location. If the report is empty, the systems are synchronized and there are no differences. Otherwise, the Differences Report contains records that differ on Partner Ecosystem Management’s side (for example: differences in status, product, or time) and reasons for flagging the records. Partner Ecosystem Management also indicates whether any action needs to be taken to resolve the difference. See Types of Differences for information about differences and actions needed. Within 48 hours of receiving the Differences File, the Merchant should make all the required updates on their side and generate and send a new Reconciliation Report to Partner Ecosystem Management. This process allows the Merchant to confirm the updated status of the data. This Differences Report is a CSV file. The naming convention is PartnerReconciliationDifferences_<Merchant_code>_<Reseller_code>_<StartDate>_<EndDate>_v1.csv where <StartDate> and <EndDate> are in the format of yyyymmddThhmmssZ. Differences Report Fields The Differences Report has the following fields:

Field Name	Field Format	Field Description
Aggregator Code	Alphanumeric string	The Reseller’s (Service Provider’s) Organization Code in Partner Ecosystem Management. Partner Ecosystem Management provides this information to the Merchant.
Partner Product Code	Alphanumeric string	The product code the Merchant provided. The Merchant provides this code during onboarding.
MarketONE Product Code	Alphanumeric string	The product code Partner Ecosystem Management provided.
Partner Customer ID	Alphanumeric string	The customer’s unique ID in Partner Ecosystem Management.
Partner Subscription ID	Alphanumeric string	The subscription’s unique ID in Partner Ecosystem Management.
Created Date	Date and time (ISO 8601)	The date and time the subscription was created on the Merchant’s side. The format is UTC.
Activated Date	Date and time (ISO 8601)	The date and time the subscription was activated on the Merchant’s side. The format is UTC.
Partner Last updated Date	Date and time (ISO 8601)	The date and time the subscription was last updated on the Merchant’s side. The format is UTC.
MarketONE Last updated Date	Date and time (ISO 8601)	The date and time the subscription was last updated by Partner Ecosystem Management. The format is UTC.
External Partner Subscription ID	Alphanumeric string	The subscription ID on the Merchant’s side. Merchants manage this ID and send it back to Partner Ecosystem Management as part of provisioning API response sync call. This ID is only displayed if the Merchant supports the ID.
Partner Subscription Status	String	The Partner subscription’s provisioning status as it appears on the Merchant’s side. Valid values include: - INACTIVE - ACTIVE - CANCELLED - PAUSED
MarketONE Partner Subscription Status	String	The Partner subscription’s provisioning status as it appears in Partner Ecosystem Management. Valid values include: - INACTIVE - ACTIVE - CANCELLED - PAUSED
Reason	Alphanumeric string	The reason why the record appears in the Differences File. Reasons that can appear include: - Product Mismatch: There is a difference in product data. - Status Mismatch: There is a difference in status data. - <<specific date>> Mismatch: There is a difference in dates. The type of date is specified, such as Created Date or Last Updated Date. - Partner subscription not found at partner record: The Partner subscription exists in Partner Ecosystem Management’s system but is missing in the Merchant’s system.
Action Needed	Alphanumeric string	This field indicates whether action needs to be taken.One of the following values appears: - N: No action is required. This appears in case of a <<specific date>> Mismatch. - Y: Action is needed. This appears in the case of a Product Mismatch, a Status Mismatch, or Partner Ecosystem Management automatically reconciling a difference. See Types of Differences for information about differences and actions needed.

Types of Differences and Actions Needed

Parent topic:Reconciliation

Home

Introduction

For Merchants

For Resellers

Partner Ecosystem Management

Commerce Engine

Storefront Experience

APIs

Reconciliation Report

Differences Report

​Reconciliation Report

​Differences Report

Reconciliation Report

Differences Report