# Pricing Summary report (/platforms/reports/partner-merchant-reconciliation/pricing-summary) This report provides a summary of transaction pricing and related costs. It includes aggregated metrics such as transaction volume, PayPal fees, processing costs, interchange and assessment costs, and payout or invoice amounts by partner, pricing model, and currency. Use this report to understand your overall costs and fees for transactions, identify trends in your transaction costs, and reconcile your costs with your financial statements. To see what's in this report, [download a sample](https://www.paypalobjects.com/ppdevdocs/report/sample/PRICING_SUMMARY_Report.csv) in CSV format. This sample may vary from your actual report, depending on your settings. > **Success:** For information about reconciliation, see the [Reconciliation > section](#reconciliation) at the end of this page. ## Before you begin [#before-you-begin] Before using this report, review the following requirements and considerations: * Ensure you are an approved partner to use this report. * This report is only available to partners on gross billing fees or a net settlement revenue share model. * PayPal generates reports for partners on [interchange plus plus (IC++)](https://www.paypal.com/brc/article/what-is-interchange-plus-plus) pricing and places them on the SFTP server by the 7th day of each month before 9:00 AM in the leading time zone of the reporting window. * PayPal generates reports for all other partners and places them on the SFTP server by the 2nd day of each month before 9:00 AM in the leading time zone of the reporting window. * This report includes [alternative payment methods (APMs)](/platforms/checkout/apm/). * You can generate this report for a single account or a set of accounts. To include data from multiple accounts in a single report, all accounts must belong to the same time zone. > **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 Pricing Summary report for a single account follows this naming convention: ``` PRICING_SUMMARY....... ``` | Field | Description | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `PRICING_SUMMARY` | The report type | | `yyyymm` | The month for the data in the report | | `ReportIdentifier` | A unique value that identifies the report, such as the BN code or organization name. If you want to generate multiple reports, each containing data for a unique set of accounts, use this field to differentiate the reports. | | `ReportingWindow` | The time window in which the report was generated:
- `A`: America/New York to America/Los Angeles
- `H`: America/Los Angeles to Asia/Hong Kong
- `R`: Asia/Hong Kong to Europe/London
- `X`: Europe/London to America/New York | | `SequenceNumber` | The sequence number of the report file. The sequence number begins with `0` and continues until all parts of the report are recorded in files. The sequence number is always present in the report file name, even if there is only 1 file. | | `MajorVersion` | The major version of the report. This number increments when there are significant changes to the report. | | `MinorVersion` | The minor version of the report. This number increments with any change to the report. If there are no changes, it is `0`. | | `Format` | The report format is `CSV` (comma-separated values). | For more information about report file naming conventions, see [Terminology](/platforms/reports/reference/terminology). ## Report format [#report-format] Each row of the report consists of a 2-letter row type, followed by the details for that row type. The following table lists the valid row types and the sections that describe the data for that row type. | Code | Description | | ---- | -------------------------------------- | | `FH` | [File header](#file-header-data) | | `SH` | [Section header](#section-header-data) | | `CH` | [Column header](#column-header-data) | | `SB` | [Section body](#section-body-data) | | `SF` | [Section footer](#section-footer-data) | | `TB` | [Total body](#total-body-data) | | `TF` | [Total footer](#total-footer-data) | | `FF` | [File footer](#file-footer-data) | ### File header data [#file-header-data] The file header contains report metadata and configuration information. | Position | Column name | Data type | Description | | -------- | -------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | `Column Type` | `Literal` | The column type (file header, `FH`) | | 2 | `Report Generation Date` | `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`. | | 3 | `Reporting Window` | `Varchar` | The time window in which the report was generated:
- `A`: America/New York to America/Los Angeles
- `H`: America/Los Angeles to Asia/Hong Kong
- `R`: Asia/Hong Kong to Europe/London
- `X`: Europe/London to America/New York | | 4 | `Report Period Start Date` | `Date-time` | The beginning date and time of transactions to include 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 Period End Date` | `Date-time` | The final date and time of transactions to include 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`. | ### Section header data [#section-header-data] This report contains multiple sections. Each section is a unique combination of partner identifier (button source code or organization name), payout or invoice account email address, and pricing model. The section header identifies the start of a new data section and specifies the partner and pricing context for the rows that follow. | Position | Column name | Data type | Description | | -------- | ------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | `Column Type` | `Literal` | The column type (section header, `SH`) | | 2 | `Partner Identifier` | `Varchar` | The button source code or organization name of the partner | | 3 | `Payout Account Email` or `Invoice Account Email` | `Varchar` | The email address of the account to receive the revenue share payout if the pricing model is `REVSHARE`, or the email address of the account to receive the invoice if the pricing model is `GROSS_BILLING` | | 4 | `PRICING_MODEL` | `Varchar` | Indicates whether there is a revenue share on the transaction or if fees are gross billed through invoices: `GROSS_BILLING` or `REVSHARE` | ### Section body data [#section-body-data] The section body contains the detailed pricing and cost data for each combination of fee type, payment instrument, and currency. | Position | Column name | Data type | Description | | -------- | ------------------------------------- | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | `Column Type` | `Literal` | The column type (section body, `SB`) | | 2 | `PRICING_FEE_TYPE` | `Varchar` | The fee type, based on the transaction and direction of money movement: `SALE`, `REFUND`, or `CHARGEBACK` | | 3 | `PAYMENT_INSTRUMENT_TYPE` | `Varchar` | A high-level classification of the financial instrument used to fund the payment, such as `PAYPAL`, `CREDIT_CARD`, `DEBIT_CARD`, `DIRECT DEBIT`, `VENMO`, `Apple Pay`, `Google Pay`, `Network Token`, or a [supported APM](/platforms/checkout/apm/) | | 4 | `PAYMENT_INSTRUMENT_SUBTYPE` | `Varchar` | A detailed classification of the financial instrument used to fund the payment: `AMEX`, `CARTE_BANCAIRE`, `CETELEM`, `COFIDIS`, `COFINOGA`, `CHINA_UNION_PAY`, `DELTA`, `DINERS`, `DISCOVER`, `ELECTRON`, `ELO`, `HIPER`, `HIPERCARD`, `JCB`, `MAESTRO`, `MASTER_CARD`, `RUPAY`, `SOLO`, `STAR`, `SWITCH`, or `VISA`

For wallets and network tokens, this field shows the card type and brand that funded the transaction, for example `CREDIT_CARD-VISA` or `DEBIT_CARD-MASTER_CARD`. | | 5 | `TRANSACTION_CURRENCY` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the transaction (for example, `USD`) | | 6 | `UNITS` | `Varchar` | The number of units for the current month's transactions | | 7 | `VOLUME` | `Money` | The transaction volume for the current month, rounded to 2 decimal places | | 8 | `PP_FEES` | `Money` | The PayPal fees charged to sellers for the current month's transactions, rounded to 2 decimal places | | 9 | `PROCESSING_COST` | `Money` | The total PayPal markup for the current month's transactions, rounded to 2 decimal places | | 10 | `INTERCHANGE_COST` | `Money` | The total interchange cost for the current month's transactions, rounded to 5 decimal places | | 11 | `ASSESSMENT_COST` | `Money` | The total assessment cost for the current month's transactions, rounded to 5 decimal places | | 12 | `REVISION_UNITS` | `Money` | The total number of units that received revised costs. This is applicable only when the partner is on IC++ pricing. | | 13 | `REVISION_PRIOR_INTERCHANGE_COST` | `Money` | The prior interchange cost for units that received revisions, rounded to 5 decimal places | | 14 | `REVISION_REVISED_INTERCHANGE_COST` | `Money` | The revised interchange cost for units that received revisions, rounded to 5 decimal places | | 15 | `REVISION_REVISED_ASSESSMENT_COST` | `Money` | The assessment costs that were received in the current month for transactions that occurred in a prior month, rounded to 5 decimal places | | 16 | `PAYOUT_AMT_IN_TRANSACTION_CURRENCY` | `Money` | The calculated revenue share payout amount in the transaction currency, rounded to 5 decimal places. If the payout account's primary currency differs, see `PAYOUT_AMT_IN_PAYOUT_CURRENCY` for this amount converted to the payout account currency. | | 17 | `PAYOUT_AMT_IN_PAYOUT_CURRENCY` | `Money` | The converted revenue share payout amount in the payout account's currency, rounded to 5 decimal places. Use the sum of this amount across all rows and sections for each payout account to reconcile with your received revenue share payout. | | 18 | `PAYOUT_CURRENCY` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the payout account currency (for example, `USD`) | | 19 | `INVOICE_AMT_IN_TRANSACTION_CURRENCY` | `Money` | The calculated invoice amount in the transaction currency, rounded to 5 decimal places. If the invoice account's primary currency differs, see `INVOICE_AMT_IN_INVOICE_CURRENCY` for the amount converted to the invoice account currency. | | 20 | `INVOICE_AMT_IN_INVOICE_CURRENCY` | `Money` | The converted invoice amount in the invoice account's primary currency, rounded to 5 decimal places. Use the sum of this amount across all rows and sections for each invoice account to reconcile with the invoice that you received. | | 21 | `INVOICE_CURRENCY` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the invoice account currency (for example, `USD`) | | 22 | `PP_FX_MARKUP_AMOUNT` | `Money` | The PayPal markup amount for FX Optimizer-enabled currency conversion transactions | | 23 | `PARTNER_FX_MARKUP_AMOUNT` | `Money` | A partner's markup amount for FX Optimizer-enabled currency conversion transactions | ### Section footer data [#section-footer-data] The section footer provides aggregate totals for the section's payout and invoice amounts. | Position | Column name | Data type | Description | | -------- | -------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------------- | | 1 | `Column Type` | `Literal` | The column type (section footer, `SF`) | | 2 | `Total` | `Literal` | Indicates this is a total row | | 17 | `Total Payout Amount` | `Money` | The total payout amount for this section in the payout account's currency, rounded to 2 decimal places | | 18 | `Payout Currency` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the payout account currency (for example, `USD`) | | 20 | `Total Invoice Amount` | `Money` | The total invoice amount for this section in the invoice account's currency, rounded to 2 decimal places | | 21 | `INVOICE_CURRENCY` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the invoice account currency (for example, `USD`) | | 22 | `PP_FX_MARKUP_AMOUNT` | `Money` | The total PayPal markup amount for FX Optimizer-enabled currency conversion transactions | | 23 | `PARTNER_FX_MARKUP_AMOUNT` | `Money` | The total partner markup amount for FX Optimizer-enabled currency conversion transactions | ### Total body data [#total-body-data] This report can have multiple total sections, depending on the aggregate parameters that are supported. The total body provides aggregated amounts by currency and account across the full report. | Position | Column name | Data type | Description | | -------- | ------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------- | | 1 | `Column Type` | `Literal` | The column type (total body, `TB`) | | 2 | `CURRENCY` | 3-character currency code | The [3-character currency code](/api/codes/currency) for the amount in the `AMOUNT` column (for example, `USD`) | | 3 | `AMOUNT` | `Money` | The total aggregated amount | | 4 | `ACCOUNT_ID` | `Varchar` | The encrypted PayPal account number for the account | | 5 | `EMAIL` | `Varchar` | The email address for the PayPal account | ### Total footer data [#total-footer-data] The total footer marks the end of a total section. | Position | Column name | Data type | Description | | -------- | ------------- | --------- | ------------------------------------ | | 1 | `Column Type` | `Literal` | The column type (total footer, `TF`) | ### File footer data [#file-footer-data] The file footer indicates the end of the report file. | Position | Column name | Data type | Description | | -------- | ------------- | --------- | ----------------------------------- | | 1 | `Column Type` | `Literal` | The column type (file footer, `FF`) | ## Reconciliation [#reconciliation] You can use this report to reconcile data across the Pricing Transaction report (`PRICING_TXN`), the Pricing Transaction Revision report (`PRICING_TXN_REVISION`), and this Pricing Summary report (`PRICING_SUMMARY`). ### Reconciliation with Pricing Transaction reports [#reconciliation-with-pricing-transaction-reports] To reconcile against the Pricing Transaction (`PRICING_TXN`) report, use the following checks: * The sum of `PP_FEES` in `PRICING_TXN` matches the sum of `PP_FEES` in `PRICING_SUMMARY` for each partner identifier. * The sum of `PROCESSING_COST` in `PRICING_TXN` matches the sum of `PROCESSING_COST` in `PRICING_SUMMARY` for each partner identifier. * The total number of records in `PRICING_TXN` matches the total of the `UNITS` column in `PRICING_SUMMARY` for each partner identifier. * The sum of `INTERCHANGE_COST` in `PRICING_TXN` matches the sum of `INTERCHANGE_COST` in `PRICING_SUMMARY` for each partner identifier. * The sum of `TRANSACTION_AMOUNT` where `TRANSACTION_DEBIT_CREDIT_CODE` is `CR`, minus the sum where it is `DR`, in `PRICING_TXN` matches the total `VOLUME` in `PRICING_SUMMARY` for each partner identifier. For more information about the `PRICING_TXN` report, see the [Pricing Transaction report documentation](./pricing-transaction). ### Reconciliation with Pricing Transaction Revision report [#reconciliation-with-pricing-transaction-revision-report] To reconcile against the Pricing Transaction Revision (`PRICING_TXN_REVISION`) report, use the following checks: * The sum of `INTERCHANGE_COST` in `PRICING_TXN_REVISION` matches the sum of `REVISION_REVISED_ASSESSMENT_COST` in `PRICING_SUMMARY` for each partner identifier. * The total number of records in `PRICING_TXN_REVISION` matches the total of `REVISION_UNITS` in `PRICING_SUMMARY` for each partner identifier. ### Reconciliation with Pricing Program Summary report [#reconciliation-with-pricing-program-summary-report] To reconcile against the Pricing Program Summary (`PRICING_PROGRAM_SUMMARY`) report, use the following checks: * The sum of `COST` in `PRICING_PROGRAM_SUMMARY` matches the sum of `INTERCHANGE_COST` and `ASSESSMENT_COST` in `PRICING_SUMMARY` for each partner identifier. * The sum of `REVISION_REVISED_COST` in `PRICING_PROGRAM_SUMMARY` matches the sum of `REVISION_REVISED_INTERCHANGE_COST` and `REVISION_REVISED_ASSESSMENT_COST` in `PRICING_SUMMARY` for each partner identifier. * The sum of `REVISION_PRIOR_COST` in `PRICING_PROGRAM_SUMMARY` matches the sum of `REVISION_PRIOR_INTERCHANGE_COST` in `PRICING_SUMMARY` for each partner identifier. For more information about the `PRICING_PROGRAM_SUMMARY` report, see the [Pricing Program Summary report documentation](./pricing-program-summary).