This sounds like a bug. The trick with these is reproduction - if you can come up with a scenario where the issue consistently occurs then it should be fairly easy to fix. For an issue like this, it might even be possible to work around it in the immediate term using a table level script - essentially, we could modify the CRM data as we insert the new billing address.

I'd suggest trying something like the following:

1: Create a new (fake/test) company in Sage 200.

2: Set the billing address.

3: Synch with CRM.

4: Set a new billing address in 200.

5: Synch.

6: Check if you're seeing the expected issue.

Of course, the issue might only occur if the address is updated on the CRM side, or through some other set of steps. If you log a case with your support team, they will try as many permutations that they can think of, or what's most sensible based on a look at your database. However, you'll find if you know *how* to cause the issue to occur, then the issue will be resolved much more quickly. I'd ask someone who worked on one of those accounts recently, to see if they remember what updates they mode.

Thanks,

Rob