Hi @lazylibrarian1993!
There is no out-of-the-box matching mechanism that synchronizes data between an already existing asset in AEM and a newly uploaded one.
A somewhat related feature is duplicate detection [1]. Once activated it works as follows:
"When a user attempts to upload an asset that exists in Experience Manager, the system checks for conflict and indicates it. The assets are identified using SHA-1 hash stored at jcr:content/metadata/dam:sha1, which means duplicate assets are detected irrespective of the filenames."
If a user tries to upload an asset that is already present in AEM, he will be presented with an according warning message:

(See [2])
For your use case you would need to build a custom solution.
You may want to check the blog post [3] linked on the above mentioned documentation page that provides some guidance on the implementation around duplicate detection.
[1] https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/duplicate-detection.html
[2] https://experienceleague.adobe.com/docs/experience-manager-64/assets/managing/managing-assets-touch-ui.html?lang=en#uploading-assets
[3] https://experience-aem.blogspot.com/2019/06/aem-65-find-duplicate-assets-binaries-in-existing-repository.html
Hope that helps!