The *charges and usage report* provides details of your revenue and your
customers' usage of your products for the previous month. To access your charges
and usage reports, visit the destination that you specified when you
[set up to receive reports](https://docs.cloud.google.com/marketplace/docs/partners/reports/set-up-reports.md.txt).

By default, the charges and usage report is broken down by the SKU, Google
entity, and resource. When you set up your reports, you can choose these
additional breakdowns:

- By account: This method adds **Account ID** and **Insights Account ID**
  columns to the report, which show a billing ID for the customer. You can use
  this ID to track metrics like churn or trial conversions. The Account ID
  isn't the customer's Google Cloud billing ID, but it is specific to
  the customer's Cloud Billing account. There are two forms of obscured
  account ID in the report because, for historical reasons, the two reports
  use different algorithms to obscure the actual account ID. For more
  information about matching disbursements to customers, see
  [Determine the customer for a specific disbursement](https://docs.cloud.google.com/marketplace/docs/partners/reports/report-charges-usage.md.txt#match-customer) in
  this document.

- By location: This adds a **Location** column to the report, which holds the
  country code for the customer's location. If the customer is in the US or
  Canada, the column includes the country and state code, separated by a `/`.

## Determine the customer for a specific disbursement

To match a disbursement in the charges and usage report to the name of the
customer for that disbursement, complete the following steps:

1. Turn on `by account` reporting.

2. Set up [Customer insights reports](https://docs.cloud.google.com/marketplace/docs/partners/reports/report-customer-insight.md.txt).

3. Find the value of the disbursement's `Insights Account Id` in this report.

4. Find the row in the customer insights report whose value for
   `external_account_id` matches the `Insights Account Id` value that you
   found.

## Report frequency

This report is generated by the tenth business day of every month in the
destination that you set up. It includes the details of usage and revenue for
the previous month. Its name uses the following format:
`YYYYMMDD Charges and Usage`

For example, a report named `20210401` means the report is for the usage that
happened in April 2021.

### Report fields

The report contains the following content. For any questions about the
report, open a support ticket. For information on how to get support, see
[Get support for Marketplace partners](https://docs.cloud.google.com/marketplace/docs/partners/get-support.md.txt).

- **SKU**: The description of the Cloud Marketplace product. If any
  extraordinary payments were processed, they're reflected here.

- **Google Entity**: The Google corporation that received the payment from
  customers.

- **Resource** : The resource for which the customer was charged. For virtual
  machine (VM) products, this depends on your product's
  [pricing model](https://docs.cloud.google.com/marketplace/docs/partners/vm/select-pricing.md.txt).
  For software as a service (SaaS) and Kubernetes products, this is the usage
  metric.

- **Usage**: The quantity of the resource used by deployments of the product.

- **Units**: The unit in which the Usage column is measured, such as hours,
  core-hours, or gibibyte-hours, depending on your pricing model.

- **Currency**: The currency in which the following three columns are measured.

- **Charges**: The customer's costs for using your product. Starting with
  April 2021's report, if you are paid in a currency other than USD, this field
  uses your payment currency.

- **Trial Use** : The cost that was covered by product trial credits,
  coupon-created credits, and
  [product testing](https://docs.cloud.google.com/marketplace/docs/partners/testing-products.md.txt#set-up-test-billing-account).
  Starting with April 2021's report, if you're paid in a currency other than
  USD, this field uses your payment currency.

- **Due Partner** : Payment accrued for you, calculated as
  `(Charges - Trial Use + Prepay Credits + Postpay Credits + Reseller Discount) * revenue share`.

  For this calculation, we add the *prepay credits* , *postpay credits* , and
  *reseller discount* instead of subtracting them because their values are
  negative numbers. We subtract *trial use* because its value is a positive
  number.
- **Payment Type** : The means by which you will receive the
  disbursement: If it is `old`, you receive payments from Google US or a
  regional Google entity to your US-based bank account. If it is `new`,
  you receive a single payment to your local bank account.

- **Withheld**: If a Google Cloud customer's Cloud Billing account is
  placed on probation for nonpayment, Google withholds disbursements until the
  account is back in good standing.

  This column tells you how much we would have paid you if we
  had collected it from the customer.

  When the billing account is back in good standing, we release the withheld
  funds in the next payment to you. If it never returns to good standing, we
  abandon the withheld funds.
- **Released**: If Google had withheld funds, this column shows the total of
  the funds that are now released to you because the customer's billing account
  is back in good standing.

- **Abandoned**: If Google had withheld funds, this column shows the total of
  the funds abandoned because we have terminated the billing account.

- **Probation Start** : The first day that Google started withholding funds,
  in `YYYY-MM-DD` format. If we are releasing or abandoning funds, this may be
  in an earlier month. If the account is still on probation, this is the first
  day in the current month where we withheld funds (which may not be the very
  first day on which we withheld funds).

- **Probation End** : The last day that Google withheld funds, in `YYYY-MM-DD`
  format. The day after this, the account either returned to good standing, or
  we closed it. If this is blank, then the account is still on probation.

- **Refund Start**: The first day that Google refunded a customer's usage, in
  YYYY-MM-DD format.

- **Refund End**: The last day that Google refunded a customer's usage, in
  YYYY-MM-DD format.

- **Refund Balance Deducted This Month**: The amount of payout Google subtracted
  during the month related to a customer refund.

- **Refund Balance Outstanding**: If the offset related to a customer's
  refund is greater than the month's payout, the remaining offset due to your
  future payout.

- **Refund Reason**: The reason why a customer received the refund.

- **Postpay Credits** : The amount by which `Charges` were reduced by credit
  purchased through a commitment-based private offer with a postpay payment
  schedule, before the `Due Partner` amount was computed.

If you create private offers, the following additional fields might be present:

- **Prepay Credits** : The amount by which `Charges` were reduced by credit
  purchased through a commitment-based private offer with a prepay payment
  schedule, before the `Due Partner` amount was computed.

- **Billing frequency** : Describes the recurring billing interval selected at
  the time of offer creation. Can have the value `monthly`, `quarterly`,
  `yearly`, `pay_go`, or `custom`.

  > [!NOTE]
  > **Note:** For offers created before March 11, 2024, which used payment schedules instead of billing frequency, this has the value `prepay` or `postpay`.

- **Payment Schedule** : For offers created before February 23, 2024, which used
  payment schedules instead of billing frequency, this indicates the offer's
  payment schedule. Has a value of `Prepay` if this is a prepaid installment
  charge, or `Postpay` if it's a postpaid charge, or a charge that's covered by
  a credit purchased through a prepaid commitment charge.

  > [!NOTE]
  > **Note:** For offers created after February 23, 2024, which use billing frequency instead of payment schedules, this field is blank.

> [!NOTE]
> **Note:** As we add features and make improvements to Cloud Marketplace, we add columns as needed to existing reports. If you set up any automated processing of your reports, you should configure it so that it operates based on the names of the columns, and doesn't depend on the total number of columns staying the same.