Topic: User Acceptance Testing vs. Acceptance Testing

Acceptance Testing (AT) is conducted by internal users (of the company providing the product) to ensure that the product meets customer requirements by use of scenario testing or "use-cases". It is distinct from QA testing because instead of validating technical specifications, it is validating business requirements.

User Acceptance Testing (UAT) is conducted by the end user/customer to ensure that the product meets their business needs and the application works as they intended. It is distinct from AT because it is performed from a customer perspective, and instead of validating business requirements, it is validating real world business scenarios and business needs, that the product providers cannot truly reproduce.

Is this accurate? I am in a position where people within my company do not fully understand what AT is and why it is needed, so I need to educate and guide them on this matter.