Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud partner program
  • Getting started
    • Overview
      • Creating a customer account
      • Adding a customer subaccount
      • Granting access to a partner account
      • Viewing usage details for subaccounts
      • Exporting extended usage details
      • Suspending services to customers
      • Linking a cloud to a subaccount
      • Adding a user to a subaccount
      • Setting up customer quotas
      • Registering a deal
      • Registering a project
      • Requesting a presale
    • Access management
    • Release notes
  • Terms and definitions

In this article:

  • One-time export
  • Setting up regular export
  • Getting started
  • Get the expense details
  • Expense details file format
  1. Partner portal
  2. Step-by-step guides
  3. Exporting extended usage details

Exporting spending details for a partner account and subaccounts

Written by
Yandex Cloud
Updated at March 19, 2026
  • One-time export
  • Setting up regular export
    • Getting started
    • Get the expense details
  • Expense details file format

You can get a CSV file with spending details for a partner account and subaccounts. You can either download the file once or set up its regular export.

One-time exportOne-time export

Partner portal
  1. Go to the partner portal.
  2. In the left-hand panel, select Finance.
  3. Go to the Subaccount details tab.
  4. Click Export as CSV at the top right.
  5. Select the time period to get the details for.
  6. Click Download.

Note

A single CSV export disregards the current filter settings in the details. It covers the entire consumption for the specified period.

Setting up regular exportSetting up regular export

Getting startedGetting started

  1. If you do not have any folders yet, create one. In the folder name, specify the project or client to use the folder.

  2. Create a bucket in Yandex Object Storage. Yandex Cloud will save the files with details to this bucket. You can save your details in multiple buckets.

    Alert

    Bucket requirements.

    • Do not make your bucket public; otherwise, anyone will be able to download your expense details using the bucket link.
    • Do not add encryption to the bucket.
    • Do not configure an access policy for the bucket.

    You pay for the size of the detail files stored in Yandex Object Storage as per the relevant pricing policy.

  3. Make sure you have one of the following roles: billing.accounts.owner, billing.accounts.admin, billing.accounts.editor, billing.accounts.partnerAdmin.

Get the expense detailsGet the expense details

Partner portal
  1. Go to the partner portal.

  2. In the left-hand panel, select Finance.

  3. Go to the Subaccount details tab.

  4. At the top right, click Create regular export.

  5. In the Create regular export window that opens:

    • In the Bucket field, enter the name of the bucket to store the CSV file with details.

    • In the Path within the bucket field, enter the directory name for the file. It must end with the / character.

    • In the Language field, select the file language.

    • In the Details field, select the type of details: General or Resource.

      Tip

      If you select Resource for regular export of details, the resource_id field will allow you to view, among others, the Yandex DataLens, Yandex Tracker, and DataSphere resources (e.g., DataSphere community IDs).

  6. Optionally, to export data for the previous period, enable the relevant option. In the Export reports starting from field that appears, select the start date for exporting reports.

  7. Click Create.

A new file with details is created in the bucket daily. The file name contains the prefix and date that details are collected for. The file is overwritten and updated with new data every hour.

The information can be updated in any daily file within a month.

Tip

Files with details from buckets are not deleted automatically, but you can configure scheduled deletion. For more information, see Object lifecycle (Object Storage refers to files in a bucket as objects).

Expense details file formatExpense details file format

An uploaded file with details is a CSV table with comma-separated columns. Each row shows the product consumption level per day for the specified folder.

Note

The export contains data both for subaccounts and the current partner account.

The table contains the following columns:

  • billing_account_id: Billing account and subaccount ID.
  • billing_account_id: Billing account and subaccount name.
  • cloud_id: ID of the cloud covered by the details.
  • cloud_name: Cloud name.
  • folder_id: Folder ID.
  • folder_name: Name of the folder at the time of exporting the details. This field may be empty if you deleted the folder before exporting the details.
  • resource_id: Resource ID, resource name, or subscription ID. Use only for regular export. The value of this field may be empty if the use of the service refers to the entire folder or it does not contain any resources. The services and resource_id column values are mapped as follows:
    • Compute Cloud and Cloud Marketplace: ID of the VM, disk snapshot, disk image, or other resource installed using Cloud Marketplace.
    • Object Storage: Bucket name.
    • Virtual Private Cloud: ID of the resource that processes incoming or outgoing traffic.
    • KMS: Key ID.
    • Network Load Balancer: Load balancer ID.
    • Container Registry: Container ID.
    • Kubernetes and Yandex Data Processing: Cluster ID.
    • Managed Service for PostgreSQL, Managed Service for ClickHouse®, Yandex StoreDoc, Managed Service for MySQL®, Yandex Managed Service for Valkey™, and Managed Service for Apache Kafka®: Host ID in the cluster.
    • Message Queue: Request ID.
    • Cloud Functions: Function ID.
    • Monitoring, Yandex IoT Core, SpeechKit, Translate, and Vision OCR: Empty value.
    • DataLens: DataLens instance ID.
    • Technical support: Subscription ID.
  • service_id: ID of the service the consumed product belongs to.
  • service_name: Name of the service the consumed product belongs to.
  • sku_id: Consumed product ID.
  • sku_name: Product name.
  • date: Consumption charge date. A date is set as an interval from 0:00 to 23:59 (UTC+3).
  • currency: Billing account currency. Possible values: RUB, USD, and KZT.
  • pricing_quantity: Number of product units consumed. The decimal separator is a period.
  • pricing_unit: Product consumption unit.
  • cost: Total cost of consumption. The decimal separator is a period.
  • credit: Total discounts. Not included in the total cost of consumption (credit). Always negative. The decimal separator is a period.
  • monetary_grant_credit: Grant discount, including the platform introduction grant. The decimal separator is a period.
  • volume_incentive_credit: Consumption volume discount. The decimal separator is a period.
  • cud_credit: Discount for the committed resource volume. The cost of the consumption volume above the committed one equals the sum of the cost and credit column values. The decimal separator is a period.
  • misc_credit: Other types of discounts, including discounts for consumption after the platform introduction grant expires but before switching to the paid version. The decimal separator is a period.
  • reward: Partner discount amount. The decimal separator is a period.
  • label.user_labels.<label_name>: Labels added to the resources. For information about how to manage labels, see Managing labels.
  • locale: Language of each exported line. This field's value determines the sku_name column language. The possible values are en and ru.
  • updated_at: Date and time of the last line update in Unix Timestamp format.
  • exported_at: Date and time when the line was added to the details file.

Note

Exports made before January 17, 2026 do not contain partner premium data (reward).

See alsoSee also
  • Viewing usage details for subaccounts

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Viewing usage details for subaccounts
Next
Suspending services to customers
© 2026 Direct Cursus Technology L.L.C.