Exceptions to BillingCenter synchronization updates

There are some cases in which BillingCenter cannot perform a contact change or update:

• ContactManager notifies BillingCenter that a contact has been deleted, but the contact is being used on at least one account in BillingCenter.

  This case is not likely to happen, because ContactManager checks to see if a contact can be deleted before it sends the request to delete the contact to BillingCenter. However, if this case does happen, BillingCenter unlinks the contact and does not delete the local instance.

• BillingCenter sends changes to a contact’s data to ContactManager, but the contact’s data was changed previously by another application or directly in ContactManager. The original data for the contact in BillingCenter, prior to the change, must match the data currently in ContactManager for the change to be accepted. Since the original data that BillingCenter sent does not match, ContactManager sends an exception to BillingCenter and does not update the contact’s data.

  In this case, BillingCenter creates an activity for a user to reapply the updates to the contact's data. The activity contains information about the contact and the data that could not be applied in ContactManager.