# Revenue Share Transactions report (/platforms/reports/partner-merchant-reconciliation/revenue-share-transactions)
This report provides details about the revenue share that a partner earns from each transaction and the corresponding payout that settled to your PayPal or bank account. The report supports reconciliation and enables you to validate each transaction's contribution to your total revenue share payout for a specific period.
You can access this report through PayPal's SFTP server. For more information, see [Access SFTP reports](/reports/access/).
Check out this video on reconciling revenue share using the Revenue Share Transactions report:
Sample reports are available for each revenue share model.
| Revenue share model | Description | Sample report |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| Net TPV | PayPal shares a portion of Total Payments Volume (TPV) with the partner. | [Download sample](/reports/REVSHARE_TXN_REPORT_nTPV.csv) |
| Net Revenue | PayPal shares a portion of net revenue earned with the partner after deducting costs (for example, interchange and network fees) and losses (for example, chargebacks and negative balances). | [Download sample](/reports/REVSHARE_TXN_REPORT_NREV.csv) |
| Buy-Sell | PayPal collects the transaction fee (sell rate) from the merchant and retains the platform fee (buy rate). For [interchange plus plus (IC++)](https://www.paypal.com/brc/article/what-is-interchange-plus-plus) use cases, processing costs (interchange and assessment) are also passed to the partner. | [Download sample](/reports/REVSHARE_TXN_REPORT_BuySell.csv) |
For tips on reconciling your Revenue Share Transactions report data, see [Reconciliations](#reconciliation).
## Before you begin [#before-you-begin]
Before using this report, review the following requirements and considerations:
* This report is available to partners who have enabled revenue share payouts with PayPal.
* You must have access to the SFTP server. Reports are automatically delivered to your designated SFTP location after each revenue share payout cycle.
* The report format is comma-separated values (CSV) with UTF-8 encoding.
* Currency amounts in this report are expressed in major currency units (for example, dollars for USD, yen for JPY).
* Negative amounts are indicated with a minus sign (for example, `-1000.00` for refunds).
* Reports are limited to 1 million records in each file. Larger reports are split across multiple files.
> **Warning:** We improve reports on an ongoing basis, which could include adding attributes. Read the report data by column header name instead of by column index, and use column names when you integrate with these reports, so that your integrations do not break when we add new columns.
## Report file name [#report-file-name]
The file name of the Revenue Share Transactions report follows this convention:
```
${encryptedSubscriptionId}-{NodeIdentifier}-{subfamily}-{templateName}-{dateCadence}-{fileNumber}-{totalFile}-{genDateTime}.{extension}
```
The `templateName` field identifies the revenue share model: `REVSHARE_TXN_REPORT_nTPV`, `REVSHARE_TXN_REPORT_NREV`, or `REVSHARE_TXN_REPORT_BuySell`.
For more information, see [Terminology](/platforms/reports/reference/terminology).
The following examples illustrate how the file name convention applies to different report files.
**Net TPV**
```
0000001-E7Q5P8YQHH5ZA-RST-REVSHARE_TXN_REPORT_nTPV-20250101-20250131-1-1-20250101000000.CSV
```
**Net Revenue**
```
0000001-8549P8GMXS3X2-RST-REVSHARE_TXN_REPORT_NREV-20250919-20250921-1-1-2025110600000.CSV
```
**Buy-Sell**
```
0000001-E7Q5P8YQHH5ZA-RST-REVSHARE_TXN_REPORT_BuySell-20250801-20250831-1-1-20250903000000.CSV
```
## Report format [#report-format]
Each report includes the following sections. Within each section, rows are categorized by type, which is indicated in the first column of each row. The following table lists the valid row types and the sections that describe the data for that row type.
| Code | Description |
| ---- | --------------------------------- |
| `RH` | [Report header](#report-header) |
| `RS` | [Report summary](#report-summary) |
| `RD` | [Report details](#report-details) |
| `RF` | [Report footer](#report-footer) |
## Report header [#report-header]
The report header contains metadata about the report, including the report name, status, date range, generation time, account hierarchy, and time zone.
| Position | Column name | Required | Data type | Description |
| -------- | --------------------------------- | -------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | `RH` | Required | Static, 2 characters | Indicates that this row contains report header data. |
| 2 | `Report Name` | Required | `Varchar(256)` | The name of the report: `REVSHARE_TXN_REPORT_nTPV` (Net TPV), `REVSHARE_TXN_REPORT_NREV` (Net Revenue), or `REVSHARE_TXN_REPORT_BuySell` (Buy-Sell) |
| 3 | `Report Status` | Required | `Varchar` | The report generation status: `Success` or `Error` |
| 4 | `Report Start Date and Time` | Required | `Date-time` | The start date and time for the data in the report, in this format: `YYYY/MM/DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 5 | `Report End Date and Time` | Required | `Date-time` | The end date and time for the data in the report, in this format: `YYYY/MM/DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 6 | `Report Generation Date and Time` | Required | `Date-time` | The date and time when the report file was generated, in this format: `YYYY/MM/DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 7 | `Hierarchy` | Required | `Varchar(256)` | The encrypted PayPal account number |
| 8 | `Timezone` | Optional | `Varchar(256)` | The time zone of the report |
## Report summary [#report-summary]
The report summary provides payout-level details, including payout IDs, period, amount, currency, payment instrument, and program name.
| Position | Column name | Required | Data type | Description |
| -------- | -------------------------- | -------- | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | `RS` | Required | Static, 2 characters | The row type (`RS`) |
| 2 | `Record ID` | Optional | `Varchar(256)` | The PayPal-generated unique identifier for the payout transaction |
| 3 | `Transfer ID` | Optional | `Varchar(256)` | The unique, external reference number for the payout transaction |
| 4 | `Payout Period Start Date` | Optional | `Date-time` | The start date of the period for which the revenue share payout is calculated, in this format: `YYYY-MM-DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 5 | `Payout Period End Date` | Optional | `Date-time` | The end date of the period for which the revenue share payout is calculated, in this format: `YYYY-MM-DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 6 | `Timezone` | Optional | `Varchar(256)` | The time zone of the user. Transactions included in the payout are based on this time zone. |
| 7 | `Payout Amount` | Optional | `Numeric(23,2)` | The total amount disbursed to your account for this payout |
| 8 | `Payout Currency` | Optional | 3-character currency code | The currency in which the payout is processed. See [PayPal-supported currencies](/reports/reference/supported-currencies) for possible values. |
| 9 | `Payout Instrument` | Optional | `Varchar(256)` | The payment instrument to which the payout was made |
| 10 | `Account Number` | Optional | `Varchar(256)` | The account number that is associated with the payment instrument |
| 11 | `Revenue Share Program` | Optional | `Varchar(256)` | The revenue share program name that is defined in PayPal for configuring the revenue share arrangement |
## Report details [#report-details]
The report details section contains one row for each transaction and includes relevant information about the transaction, such as merchant account, region, type, integration product, transaction IDs, amounts, currencies, payment methods, fee breakdowns, and revenue share calculations.
| Position | Column name | Required | Data type | Description |
| -------- | -------------------------- | -------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | `RD` | Required | Static, 2 characters | The row type (`RD`) |
| 2 | `Merchant Account ID` | Required | `Varchar(256)` | The encrypted account number of the merchant |
| 3 | `Merchant Region` | Required | `Varchar(256)` | The merchant's country code of residence. For a list of possible values, see the [Market Code Table](https://www.paypal.com/business/paypal-business-fees). |
| 4 | `Merchant Type` | Optional | `Varchar(256)` | For the Net TPV model, indicates whether the merchant is classified as `New` or `Existing` for revenue share eligibility. Not applicable for the Buy-Sell model. |
| 5 | `Integration Product` | Optional | `Varchar(256)` | For the Net TPV and Net Revenue models, the integration product used to process the transaction with PayPal. For more information, see [Terminology](/platforms/reports/reference/terminology). Not applicable for the Buy-Sell model. |
| 6 | `Integration Sub Product` | Optional | `Varchar(256)` | Not applicable for the Net TPV or Buy-Sell models |
| 7 | `Integration Identifier` | Optional | `Varchar(256)` | The BN code from PayPal that is associated with the transaction |
| 8 | `Record ID` | Required | `Varchar(256)` | The PayPal-generated unique identifier for this transaction |
| 9 | `Related Record ID` | Required | `Varchar(256)` | The transaction ID for the immediate parent transaction |
| 10 | `Description` | Optional | `Varchar(256)` | Provides a description of the event fees and value-added services. |
| 11 | `Record Type` | Required | `Varchar(256)` | The type of transaction. For a list of possible values, see [Terminology](/platforms/reports/reference/terminology). |
| 12 | `Record Subtype` | Optional | `Varchar(256)` | The subtype of the transaction. For a list of possible values, see [Terminology](/platforms/reports/reference/terminology). |
| 13 | `Created At` | Required | `Date-time` | The date and time when the transaction was initiated, in this format: `YYYY-MM-DD HH:MM:SS offset`. `offset` is the 5-character signed offset from GMT, for example `+0800`. |
| 14 | `Gross Transaction Amount` | Required | `Numeric(23,2)` | The total amount of the transaction before deducting fees |
| 15 | `Transaction Currency` | Required | 3-character currency code | The [currency](/reports/reference/supported-currencies) of the transaction. |
| 16 | `Payment Method` | Optional | `Varchar(256)` | The method of payment that was used to process the transaction. For more information, see [Terminology](/platforms/reports/reference/terminology). |
| 17 | `Payment Method Subtype` | Optional | `Varchar(256)` | The specific tender that was used to process the transaction. For more information, see [Terminology](/platforms/reports/reference/terminology). |
| 18 | `Invoice ID` | Optional | `Varchar(256)` | The invoice ID that was passed at the time of the transaction |
| 19 | `Custom Field` | Optional | `Varchar(256)` | A field for custom data |
| 20 | `Merchant Pricing Model` | Optional | `Varchar(256)` | For the Buy-Sell model, this value specifies the pricing structure that was applied when charging the merchant: `FLAT` (fixed fee per transaction) or `IC_PLUS` (interchange pass-through fee plus a fixed markup fee). Not applicable for the Net TPV model. |
| 21 | `Transaction Meta Data` | Optional | `Varchar(256)` | Additional transaction details in JSON format, primarily applicable for the Buy-Sell model. For more information, see the [transaction meta data](#transaction-meta-data). |
| 22 | `Revshare Eligible` | Required | `Varchar(256)` | Indicates whether the transaction qualifies for revenue share: `YES` or `NO` |
| 23 | `Revshare Model` | Optional | `Varchar(256)` | The primary revenue share model that was applied to the transaction: `NET_TPV`, `NET_REVENUE`, or `BUY_SELL` |
| 24 | `Total Processing Fee` | Optional | `Varchar(256)` | For the Net Revenue model, the fees charged to process the transaction. For the Buy-Sell model, the total fee collected from the merchant in transaction currency for revenue-share-eligible fee components. Not applicable for the Net TPV model. For more information, see the [Attribute reference](#attribute-reference). |
| 25 | `Total Processing Cost` | Optional | `Varchar(256)` | For the Net Revenue model, the costs that were associated with processing the transaction. For the Buy-Sell model, the total processing costs (interchange, assessments, and so on) in the transaction currency. Not applicable for the Net TPV model. For more information, see the [Attribute reference](#attribute-reference). |
| 26 | `Processing Losses` | Optional | `Varchar(256)` | For the Net Revenue model, losses that were incurred as part of the transaction (for example, chargebacks and bank returns). Not applicable for the Net TPV or Buy-Sell models. For more information, see the [Attribute reference](#attribute-reference). |
| 27 | `Platform Fee` | Optional | `Varchar(256)` | For the Net Revenue model, the fees that PayPal charged as part of the PayPal markup. For the Buy-Sell model, the portion of the processing fee that PayPal retained in the transaction currency for the revenue-share-eligible components. Not applicable for the Net TPV model. |
| 28 | `Partner Revshare` | Optional | `Numeric(23,2)` | The revenue share that was earned from the transaction in the record currency, rounded to 2 decimal places |
| 29 | `Fee Details` | Optional | `Varchar(256)` | A JSON object that breaks down revenue share from eligible transaction and value-added-service components, with detailed fee and cost sub-components. For more information, see the [Attribute reference](#attribute-reference). |
| 30 | `Payout Currency` | Required | 3-character currency code | The [currency](/reports/reference/supported-currencies) of the revenue share payout. |
| 31 | `Revshare Payout` | Required | `Numeric(23,2)` | The revenue share that was earned from the transaction in payout currency, rounded to 6 decimal places |
| 32 | `Transfer ID` | Required | `Varchar(256)` | The unique external reference number that was assigned to the payout transaction |
| 33 | `Revshare Remarks` | Optional | `Varchar(256)` | Additional remarks about the revenue share for this transaction |
| 34 | `Payment Channel` | Optional | `Varchar(256)` | The channel through which the payment transaction was processed. |
| 35 | `Fee Period Start` | Optional | `YYYY-MM-DD` | The start date of the period in which the fee-incurring transaction took place. |
| 36 | `Fee Period End` | Optional | `YYYY-MM-DD` | The end date of the period in which the fee-incurring transaction took place. |
| 37 | `Count` | Optional | `Numeric(23,2)` | The count value in this record. This value indicates the number of transactions the fee applies to. |
## Report footer [#report-footer]
The report footer indicates the file number and total record count for the file.
| Position | Column name | Required | Data type | Description |
| -------- | --------------- | -------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | `RF` | Required | Static, 2 characters | Indicates that this row contains report footer data. |
| 2 | `File Number` | Required | `Numeric(23,2)` | The current file number. This corresponds to the file number in the file naming convention. |
| 3 | `Total Records` | Required | `Numeric(23,2)` | The total number of transactions that the report details (`RD`) section includes. This field appears only when transactional details are present. |
| 4 | `Total Files` | Required | `Numeric(23,2)` | The total number of files generated for the report. |
## Reconciliation [#reconciliation]
Use the following table to reconcile payouts against your bank statement, PayPal account, and transaction-level data.
| Use case | How to reconcile |
| --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Trace a revenue share payout in your bank statement or PayPal account | Match the `Transfer ID` in the report summary section to the payout in your bank or PayPal account. |
| Reconcile payouts with contributing transactions | For each `Transfer ID`, the `Payout Amount` in the report summary section must equal the sum of `REVSHARE_PAYOUT` (in `PAYOUT_CURRENCY`) across all contributing transactions in the report details section. |
| Calculate revenue share per transaction | Revenue share is calculated differently by model:
**Net TPV:** Revenue share = TPV \* Margin
**Net Revenue:** Revenue share = (Transaction fee - Processing cost - Processing losses) \* Margin
**Buy-Sell:** Revenue share = Transaction fee - Platform fee - Processing costs (if applicable) |
## Attribute reference [#attribute-reference]
The following examples show the JSON objects that are returned in the `FEE_DETAILS` and `TRANSACTION_META_DATA` columns of the report details section with examples.
### Fee Details [#fee-details]
The following examples show the `FEE_DETAILS` JSON objects for transactions that are eligible for each revenue share model. The `revshare_model` parameter indicates which revenue share model was applied to the transaction, and the `partner_revshare` parameter indicates the revenue share amount that was earned from the transaction in the record currency. The JSON object also includes a breakdown of the various fee components, processing costs, and losses that were incurred for this transaction, depending on the revenue share model.
**Net TPV**
This example shows the `FEE_DETAILS` JSON object for a transaction that is eligible for the Net TPV revenue share model. The `revshare_model` parameter indicates that the Net TPV model was applied, and the `partner_revshare` parameter indicates the revenue share amount that was earned from this transaction in the record currency.
```json
{"transaction_processing": {"standard_rate": {"revshare_model": "NET_TPV","partner_revshare": "0.028800","revshare_rate": 0.0012}},"value_added_services": {}}
```
**Net Revenue**
This example shows the `FEE_DETAILS` JSON object for a transaction that is eligible for the Net Revenue share model. The `revshare_model` parameter indicates that the Net Revenue model was applied, and the `partner_revshare` parameter indicates the revenue share amount that was earned from this transaction in the record currency. The JSON object also includes a breakdown of the various fee components, processing costs, and losses that were incurred for this transaction.
```json
{"transaction_processing": {"revshare_model": "net_revenue","revshare_rate": 0.5,"partner_revshare": 1.17,"platform_fee": 1.17,"processing_losses": 5,"processing_fee": {"standard_fee": {"processing_fee_amount": 2.35,"processing_fee_percentage": 0.0049,"processing_fee_fixed": 0.39},"passthrough_fee": {"interchange_fee": {"interchange_fee_amount": 6,"interchange_fee_percentage": 0.015,"interchange_fee_fixed": 0},"assessment_fee": {"assessment_fee_amount": 0.6,"assessment_fee_percentage": 0.0015,"assessment_fee_fixed": 0}}},"processing_cost": {"bank_ach_cost": {"bank_ach_cost_amount": 6.6,"bank_ach_cost_percentage": 0.0165,"bank_ach_cost_fixed": 0},"chargeback_cost": {"chargeback_cost_amount": 10,"chargeback_cost_percentage": 0,"chargeback_cost_fixed": 10},"interchange_cost": {"interchange_cost_amount": 6,"interchange_cost_percentage": 0.015,"interchange_cost_fixed": 0},"assessment_cost": {"assessment_cost_amount": 0.6,"assessment_cost_percentage": 0.0015,"assessment_cost_fixed": 0}},"processing_losses": null},"value_added_services": {}}
```
**Buy-Sell**
This example shows the `FEE_DETAILS` and `TRANSACTION_META_DATA` JSON objects for a transaction that is eligible for the Buy-Sell revenue share model. The `revshare_model` parameter indicates that the Buy-Sell model was applied, and the `partner_revshare` parameter indicates the revenue share amount that was earned from this transaction in the record currency. The `FEE_DETAILS` JSON object also includes a breakdown of the buy rate and sell rate applied at the transaction level and the processing fees and costs that were incurred for this transaction.
```json
{"transaction_processing": {"standard_rate": {"revshare_model": "BUY_SELL","partner_revshare": "0.36","platform_fee": {"platform_fee_amount": "0.05","platform_fee_percentage": 0,"platform_fee_fixed": "0.05"},"processing_fee": {"processing_fee_amount": "0.41","processing_fee_percentage": "0.011","processing_fee_fixed": "0.3"},"passthrough_fee": {"interchange_fee": {"interchange_fee_amount": null,"interchange_fee_percentage": null,"interchange_fee_fixed": null},"scheme_fee": {"scheme_fee_amount": null,"scheme_fee_percentage": null,"scheme_fee_fixed": null}},"processing_cost": {"interchange_fee": {"interchange_fee_amount": null,"interchange_fee_percentage": null,"interchange_fee_fixed": null},"scheme_fee": {"scheme_fee_amount": null,"scheme_fee_percentage": null,"scheme_fee_fixed": null}}},"processing_losses": null},"cross_border": {"revshare_model": "BUY_SELL","platform_fee": {"platform_fee_amount": 0,"platform_fee_percentage": 0,"platform_fee_fixed": 0},"processing_fee": {"processing_fee_amount": 0,"processing_fee_percentage": 0,"processing_fee_fixed": 0}},"value_added_services": {"cbp_adj": {"revshare_model": "BUY_SELL","partner_revshare": "0.04","platform_fee": {"platform_fee_amount": "-0.04","platform_fee_percentage": "0.0035","platform_fee_fixed": 0},"processing_fee": {"processing_fee_amount": 0,"processing_fee_percentage": 0,"processing_fee_fixed": 0}}}}
```
### Fee details parameter reference [#fee-details-parameter-reference]
The following table describes the parameters in the `FEE_DETAILS` JSON object.
| Parameter | Data type | Description |
| ---------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `revshare_model` | `Varchar(256)` | The primary revenue share model applied to the transaction. For example, the `revshare_model` for the Net Revenue model is `net_revenue`. |
| `revshare_rate` | `Numeric(23,2)` | The revenue share rate applied to net revenue per transaction, expressed as a decimal. |
| `partner_revshare` | `Numeric(23,2)` | The revenue share earned from the transaction in the record currency, rounded to 2 decimal places. |
| `platform_fee` | `Numeric(23,2)` | Fees charged by PayPal to meet the costs associated with processing the transaction, rounded to 2 decimal places. |
| `processing_losses` | `Numeric(23,2)` | Any losses incurred due to chargebacks or bank returns, rounded to 2 decimal places. |
| `processing_fee` | `Varchar(256)` (JSON object) | A JSON object providing a breakdown of fee components charged to process the transaction. For standard transactions, includes the standard fee charged by PayPal. For IC++ card transactions, also includes interchange and assessment fees charged by processors. |
| `processing_cost` | `Varchar(256)` (JSON object) | A JSON object providing a breakdown of costs associated with the transaction, such as interchange and assessment charges. Each fee or cost type includes a total amount and fixed and variable components. |
| `value_added_services` | `Varchar(256)` (JSON object) | Fees charged as part of value-added services opted into by the merchant, such as foreign exchange or fraud protection. Each fee or cost type includes a total amount and fixed and variable components. |
### Transaction metadata [#transaction-metadata]
The `TRANSACTION_META_DATA` JSON object provides FX details for currency conversion transactions.
```json
{"fx_details": {"base_transaction_amount": -160.75,"transaction_currency": "MXN"}}
```
The following table describes the parameters in the `TRANSACTION_META_DATA` JSON object.
| Parameter | Description |
| ------------------------- | ----------------------------------------------------------------------------------------------- |
| `base_transaction_amount` | The base amount on which buy and sell rates or markups are applied. |
| `transaction_currency` | The currency of the base transaction amount in which buy and sell rates or markups are applied. |