Disassociate a sub-account

Description

A main account can end the Billing Association with a linked sub-account.

Procedure

1. Sign in to your main account. Navigate to Billing Management > Enterprise Finance > Billing Association. Find the sub-account that you want to disassociate and click "Disassociate".

2. In the confirmation dialog box, review the risks, select the "I have read and understood the risks" checkbox, and click "Disassociate". The prompt states that any funds (cash or coupons) allocated to the sub-account cannot be reclaimed after disassociation, and that the action takes effect immediately without requiring confirmation from the sub-account.

Notes

1. Only a main account can disassociate a sub-account.

2. To prevent service interruptions for the sub-account after disassociation, ensure that it has a sufficient available balance before you proceed.

Limitations

1. If a financial management relationship exists, the main account must reclaim the credit limit allocated to the sub-account before disassociation. However, if the account uses entity-level credit control, where the total credit limit is managed at the enterprise level, you do not need to reclaim the limit. (For more information, see the Announcement on the Feature Upgrade of Credit Limit Settings.)

2. If a financial hosting relationship exists, the sub-account cannot have any outstanding historical debt. Historical debt refers to unpaid bills for users who are not on a real-time settlement plan.

3. If a financial hosting relationship exists, the sub-account cannot have any pending operations at the time of disassociation. This includes orders with a "pending payment" or "payment in progress" status, as well as active or pending renewal, modify configuration, or temporary upgrade operations.

Effects of disassociation

1. If the main account's authorization settings include the "Allow to synchronize the credit control identity of the master account to the associated account" permission, the sub-account's credit limit is cleared after disassociation. The sub-account must reapply for a credit limit if needed.

2. If a sub-account was upgraded from a financial management relationship to a financial hosting relationship and the "Allow to synchronize the credit control identity of the master account to the associated account" permission was enabled under the original relationship, its credit limit is cleared after disassociation.

3. After a sub-account in a financial hosting relationship is disassociated, no refunds are provided for subsequent modify configuration, refund, or downgrade operations on an instance that was purchased during the hosting period.