Have To Save New User Twice

We have connections from Drupal to an AD and a LDAP for different user groups and different purposes. The AD is for employees and controls network access and all sorts of stuff, where their record is created by an admin. They can log into the Drupal site using their network password for authentication. When they log in, a Drupal account is created and synched, roles assigned, and it all works fine.

Then we have public access available for clients. They sign up on the Drupal registration form. When they do, an admin processes their request and approves the account in Drupal. As I understand it, when the account gets moved from 'blocked' to 'approved,' Drupal (LDAP module) provisions the account using Drupal data out to the LDAP. This also works, except for one point. That is that for some reason the user account has to be saved twice. The first time, you set the account status and user roles and save, and it doesn't actually save it in Drupal. The account shows the original values on those fields. However, the account is at that point provisioned out to LDAP. If you make the same updates and save the Drupal account again, it updates the LDAP record (if you made any changes) and saves the proper values in Drupal. This is a minor nuisance for the admin, but the problem is that the 'welcome' email is generated twice, with different single-use logins that both work, and has caused confusion for at least one customer who has reported it.

As I understand it, our setup and processes are fairly unique, and perhaps the LDAP module is not the issue here. However, I've traced out the Drupal account creation process as best I can and this is as far as I've gotten. Can anyone make a suggestion as to how the duplicate welcome emails might be solved, or, even better, how to the eliminate the need to save each new account twice? I'm not sure if something in LDAP is getting in the way of Drupal's saving the data, or why it would only happen the first time, but it seems to point to the provisioning happening between the account edit form being submitted and the actual save, at which point the process is stopped.

PS: I thought there was already an issue created on this topic, but can't find it; if anyone can find that thread, I'd appreciate it.