Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
Why do I receive the error "You can only join an organization whose Seller of Record is same as your account" when I try to join an organization?
When I try to join an organization in AWS Organizations, I receive the error "You can only join an organization whose Seller of Record is same as your account."
Resolution
This error occurs because your seller of record (SOR) isn't in the same partition as the AWS organization that you want to join. Because of legal and billing constraints, an account can't join an organization if it's in a different partition than the organization's management account. An AWS partition is a cluster of AWS Regions that are physically and logically isolated.
The supported partitions are:
- AWS Regions
- AWS China Regions
- AWS GovCloud (US) Regions
For example, accounts in the AWS Regions partition can only be in an organization with accounts that are also in the AWS Regions partition.
Your AWS partition is determined by the location selection that you made when you created your account. The AWS partition determines the SOR of the account. For more information, see How does AWS determine the location of your account?
An SOR in AWS is the legal entity that's responsible for selling AWS services to customers in a particular Region or country. Some of the SORs include:
- Amazon Web Services, Inc. (AWS Inc.)
- Amazon Web Services EMEA SARL (AWS Europe)
- Amazon Web Services India Private Limited (AWS India)
- Others
For more information, see Finding the seller of record.
Related information
Why can't I join an organization in AWS Organizations?
There is no resolution given, only explanation. Then, how to resolve?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Echoing the comment that this is an excellent description of the problem, but there is no discussion of how to resolve the issue.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Is there any solution to resolve the issue?
Apparently, if you are facing this issue in India... there is an internal problem at AWS where they have "AWS India" and "Amazon Web Services India Private Limited" - 2 distinct SORs. Even if its shows the same SOR on payment preferences, if there is different Seller name on Tax settings for the accounts in question - this problem happens. The support team was of no help when contacted in this situation.
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
