> ## 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. # Settlement Report Use the Settlement Report to determine the amounts owed to Merchants from product subscription sales on a monthly basis. This report enables Merchants and Resellers (Service Providers) to see payout results in a central and transparent location. In addition to processing settlements, Partner Ecosystem Management does the work of reporting for you. Payouts are determined in the agreement between the Merchant and Reseller (Service Provider). When a Reseller creates an agreement and enables a settlement model, the Reseller chooses a settlement type for payouts. The available settlement types are: * Fixed Amount (flat fee) * Revenue Share (percentage) The Reseller enters the flat fee or percentage the Merchant will receive in the agreement. The actual payments to the Merchant are the responsibility of the Reseller. Settlements are either based on monthly calculations of active subscriptions, or on monthly calculations of transactions (that is, new activations and renewals). This calculation depends on the product lifecycle the Merchant chose for the product, which can be Merchant-Managed or Platform-Managed. **Note:** An agreement must be active, have an enabled settlement model, and have active subscriptions or active billing entitlements to generate data in the Settlement Report. * **[Settlement Processing](r_settlementReportAbout#settlement-processing)** * **[Settlement Report File](r_settlementReportAbout#settlement-report-file)** **Parent topic:**[Reports](r_reportingAbout) ## Settlement Processing ### Fixed Amount Processing The Reseller (Service Provider) and the Merchant can establish a Fixed Amount settlement in an agreement. Once the agreement is approved, the Merchant receives a flat fee for every new subscription activation or renewal. The settlement process varies depending on whether a product is [Merchant-Managed or Platform-Managed](managedFlows). **Settlement Process for Merchant-Managed Products** Fixed Amount settlements are initiated and processed for Merchant-Managed products as follows: 1. Using the Reseller's [statement billing](g_statementBilling), a customer buys or renews a subscription at the Merchant's store. 2. The Merchant's system sends a transaction to Partner Ecosystem Management for the new subscription or renewal. 3. In accordance with the agreement, the fixed amount settlement model is applied to the transaction. 4. The Merchant receives the fixed amount for every new subscription and renewal. For refund transactions, Partner Ecosystem Management will reverse the settlement amount from the Merchant. These transactions are visible in the Settlement Report. **Note:** Refunds may occur months after activations. In such cases, the monthly settlement may not reconcile with activations and renewals for the Merchant's product. **Settlement Process for Platform-Managed Products** Fixed Amount settlements are initiated and processed for Platform-Managed products as follows: 1. Customers buy subscriptions at the Reseller's store. 2. The Merchant receives the fixed amount for every active subscription in a given month. This will include any subscriptions that were active but also canceled within the same month. Partner Ecosystem Management looks for any subscriptions that were active in the prior month, and applies the fixed amount defined in the agreement. ### Revenue Share Processing The Reseller (Service Provider) and the Merchant can establish a revenue share settlement in an agreement. Once the agreement is approved, the Merchant receives the designated percentage for every subscription purchase and renewal. If the Reseller provides a minimum price for a revenue share and the charge amount is lower or missing, the minimum price will be used in place of the charge amount. The settlement process varies depending on whether a product is [Merchant-Managed or Platform-Managed](managedFlows). **Settlement Process for Merchant-Managed Products** Revenue Share settlements are initiated and processed for Merchant-Managed products as follows: 1. Using the Reseller's [statement billing](g_statementBilling), a customer buys or renews a subscription at the Merchant's store. 2. The Merchant's system sends a transaction to Partner Ecosystem Management for the new subscription or renewal. The transaction contains the subscription price that will be used to determine the revenue share amount. 3. In accordance with the agreement, the revenue share settlement model is applied to the transaction. 4. The Merchant receives the revenue share percentage for every new subscription and renewal. For refund transactions, Partner Ecosystem Management will reverse the settlement amount from the Merchant. These transactions are visible in the Settlement Report. **Note:** Refunds may occur months after activations. In such cases, the monthly settlement may not reconcile with activations and renewals for the Merchant's product. **Settlement Process for Platform-Managed Products** Revenue Share settlements are initiated and processed for Platform-Managed products as follows: 1. A customer buys or renews a subscription at the Reseller's store. 2. The billing system (Commerce Engine or an external system) sends the price paid for the subscription to Partner Ecosystem Management. This process is also applied to any subscriptions that were active but also canceled within the same month. 3. Partner Ecosystem Management calculates the percentage owed to the Merchant. 4. In accordance with the agreement, the revenue share model is applied to the subscription. 5. The Merchant receives the Revenue Share percentage for the new subscription or renewal. **Note:** If you're using your own subscription billing platform, the offer charge and the price paid need to be provided to Partner Ecosystem Management to process revenue share settlements. **Parent topic:**[Settlement Report](r_settlementReportAbout) ## Settlement Report File The Settlement Report is a CSV file with this naming convention: **MarketONE.Settlement.Report\_\\_\.CSV** where: * **\**: The day and hour the report was generated. * **\**: The Reseller's Organization Code. * **\**: The Merchant's Organization Code. The Settlement Report is generated every month based on the Reseller's time zone. It contains data for the previous month. The Settlement Report has the following fields: | Field Name | Format | Description | | - | - | - | | Line Number | Decimal | The line item number. Each number is a whole number unless the settlement is volume-based. In that case, the number will have a decimal. For example: **3.1, 3.2, 3.3**. | | Billing Period Start Date | Date (yyyy/mm/dd) | The billing period start date, which is always the first day of the month. | | Billing Period End Date | Date (yyyy/mm/dd) | The billing period end date, which is always the last day of the month. | | Org Code CSP | Alphanumeric string | The Reseller's (Service Provider's) organization code. | | Org Code OTT | Alphanumeric string | The Merchant's organization code. | | Org Name CSP | Alphanumeric string | The Reseller's (Service Provider's) organization name. For example: **International Telco**. | | Org Name OTT | Alphanumeric string | The Merchant's organization name. For example: **Amazing Entertainment**. | | Product Code OTT | Alphanumeric string | The Merchant organization's product code. For example: **STREAMING\_SERVICE**. | | Product Name OTT | Alphanumeric string | The Merchant organization's product name. For example: **Awesome Streaming Service**. | | Settlement Model | String | The settlement model used. Valid values are:- **Fixed** - **Revenue Share** **Fixed** stands for fixed amount. Revenue share is based on the price paid by the customer. The customer price is split based on a defined percentage for the Merchant. | | Settlement Events | Integer | The total of settlement events used for settlement calculations, such as the total of active subscriptions or activations and renewals. This can be any numeric value greater than or equal to zero. | | Total Quantity | Integer | If the product is a quantity product, this field provides the total quantity that is used with the fixed amount to determine the total settlement amount. If the product isn't a quantity product, the field is empty. | | Total Amount to Settle | Decimal | This field only applies to settlements with the **Revenue Share** model. This is the amount used in the equation to calculate the settlement amount for the Merchant. To get the settlement amount, the **Total Amount to Settle**value is multiplied by the **Settlement Value**. | | Settlement Event Type | String | The settlement event type.Settlement event types include: - **TRX Events**: This a transaction (a new activation or renewal) for a [Merchant-Managed](managedFlows) product that has a fixed amount settlement model. - **TRX Amount**: This a transaction for a [Merchant-Managed](managedFlows) product that has a revenue share settlement model. - **MAS Events**: This is a monthly active subscription for a [Platform-Managed](managedFlows) product with a fixed amount settlement model. - **MAS Amount**: This is a monthly active subscription for a [Platform-Managed](managedFlows) product with a revenue share. - **MAS Quantity Events**: This is a monthly active subscription for a [Platform-Managed](managedFlows) and quantity-based product with a fixed amount settlement model. | | Settlement Currency | ISO 4217 | The currency code, if available. Example: **USD**. | | Settlement Value | Decimal | The value used to calculate fixed amount or revenue share settlements. The value is defined in the agreement. A valid value can be one of the following: - An amount with two decimal places (for example: **20.45**) - A percentage in decimal format (for example: 25% would be shown as **0.25**) | | Settlement Amount | Decimal | The settlement amount that is intended to be paid to the Merchant. It's rounded up to 2 decimal places. This is a pre-tax or non-tax value. Example:**3456.78**. | | Tax Amount | Decimal | The amount of tax if tax applies. This value is rounded up to 2 decimal places. This value is in the Settlement Report for accounting purposes when tax is present. Example: **46.96**. | | Entitlement Type | String | The product entitlement type.Possible values are: - **Standard**: For the standard entitlement type, customers on the Reseller's storefront are buying a single entitlement to the product. - **Quantity**: The quantity entitlement type supports various use cases, including numbers of seat licenses. | | **Parent topic:**[Settlement Report](r_settlementReportAbout) | | | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.