During the import, the system verifies that the account name or the ID provided in the import file is actually in the repository. If the account name or ID in the given row is found, the repository item is updated with the data provided in the import file. If no data is found in the repository, a new account is created.
The following validations are performed for accounts:
The DUNS number contains 9 digits.
The account logo is valid.
The contract ID is valid.
Members added to the account have the profile type
b2b_user.The phone number, company, address, city, state, country, and postal code have been provided.
The postal code is valid.
The country and state combination are valid.
The name of the account cannot be “root.”
The ID of the parent organization is valid.
All site level fields are valid.
The shipping and payment methods are valid and are associated with the site.
Approval settings during import
When accounts are configured with a list of approvers, specific validations occurs:
A member cannot be removed from an organization if that member is the last active approver in the organization and approval is required, or the organization has at least one order that is either in the
pending_approvalor thepending_approval_templatestate.An organization’s order price limit cannot be updated when delegated approval management is active and the current value of the order’s price limit is different than the repository data.
An organization’s approval required attribute cannot be updated if delegated approval management is active and the current value of the approval required is different than the repository data.
You cannot activate an organization’s approval required attribute if no member of the organization has approval authorization.
Approvals are site-specific and must reference a valid site.
