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 following 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 or AWS partition isn't the same as the management account in the AWS Organization.
The seller of record refers to whether your account is with one of the following sellers of record:
- Amazon Web Services, Inc. (AWS Inc.)
- Amazon Web Services EMEA SARL (AWS Europe)
- Amazon Web Services India Private Limited (AWS India)
- Any other seller of record
Because of billing constraints, AWS India accounts can't be in the same organization as accounts with other AWS sellers of record.
An AWS partition is a group of AWS Regions. The AWS supported partitions are AWS Regions, AWS China Regions, and AWS GovCloud (US) Regions. Because of legal and billing constraints, you can join an organization only if it's in the same seller of record as your account. Accounts in the AWS Regions partition can't be in an organization with accounts from the AWS China Regions partition or AWS GovCloud (US) Regions partition.
For example, in an AWS Europe organization, you can invite accounts only from Amazon Web Services EMEA SARL (AWS Europe) seller of record.
If you don't know the seller of record that your account is with, then see Finding the seller of record.
If you don't know the seller of record that bills the management account, then contact the owner of the management account.
To see the contact details of the management account, complete the following steps:
- Sign in to the AWS Management Console.
- Choose your account name, and then choose Organization.
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.
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
