Billing accounts are used to identify the user paying for resources in Yandex.Cloud.
The relationship between clouds, billing accounts, personal accounts, and payment methods is shown in the diagram below.
The billing account is not used to manage Yandex.Cloud resources.
Types of billing accounts
The type of billing account determines the Yandex.Cloud resource payment method.
- Intended for residents of Russia and non-residents of Russia.
- Consumed resources are paid for by bank transfer from the business's bank account or bt corporate bank card.
- Payments for resources consumed are made based on the agreement and bank invoice, or the amount is debited automatically from the linked bank card. For more information, see Billing cycle for businesses.
- A report on the services rendered and an invoice (residents only) are sent to your email address at the beginning of the next reporting period. For more information, see Reporting documents.
Billing accounts don't expire.
However, if Yandex.Cloud services are suspended due to arrears and you fail to pay the outstanding amount within 30 days of suspension, all your data, including the billing account, will be permanently blocked and deleted.
Number of billing accounts
One client can create multiple billing accounts.
You can link a billing account to one or more clouds, but each cloud can only be linked to one billing account. If a cloud is already linked to another account, linking it to a new account unlinks it from the current one.
All billing accounts under one Yandex account must be registered as payers with the same residence status: the payers must be either residents of the Russian Federation or non-residents of the Russian Federation.
For example, you created a Business billing account type forRussia. The payer of this account is a business and resident of the Russian Federation. All your next billing accounts must also be created forRussiawith payers that are residents of the Russian Federation (businesses or individuals). Selecting another country creates an error.