Resolving Error Message 'The contact name xxxxxxxxx is already assigned to another contact' when processing invoices to Xero from BMS

Created by Greg Lock - Innovative Solutions, Modified on Wed, 23 Apr at 9:19 PM by Greg Lock - Innovative Solutions

If you encounter the error message 'The contact name xxxxxxxxx is already assigned to another contact. The contact name must be unique across all active contacts.' in the BMS Log file when processing invoices to Xero, here are some steps you can take to resolve the issue:


1. Confirm Customer Code and Account Number: Check that the BMS Customer's Customer Code matches the Contact's Account number within Xero. If they do not match, update the Account number in Xero to match the Customer Code in BMS, or vise versa if the Account number in Xero must remain as is.


2. Sync Customer with Xero Contact: Click the 'Sync Customer with Xero Contact' button on any of the Customer Pages in BMS. This will ensure that the customer information in BMS is synchronized with the contact information in Xero.


3. Process the Invoice Again: After completing the above steps, process the invoice again (Billing Module > Invoices Tab, select the specific invoice/s > click Process Invoices > Process selected) and check the log to see if it states that it succeeded with an OK result.



If you have followed these steps and are still experiencing the error message, please contact our Support Team at support@innovativesolutions.co.za or call us at +27 61 542 7262. Our team will be happy to assist you in resolving the issue and ensuring smooth integration between BMS and Xero.


For more information and Support, please visit our website at www.innovativesolutions.co.za.




Innovative Solutions

www.innovativesolutions.co.za

support@innovativesolutions.co.za

+27 61 542 7262


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article