ok yes, the expected output does not have the local currency identified. the reason for this is, this information is going to a third party application that accounts use to create monthly account reconciliations. the application has a master table and the entity local currency is identified in this master table. So when this data is loaded and combined with the static master table data the accountants now know, the entity, the account, the USD balance, and the local Balance and local currently because the local currency is identified from this master table.
this data is being used as a feed to a third party application. We had to meet their specifications. I thought no local currency was weird as well, but it is what it is.
Glad you were able to get this figured out. In the future it would be nice to either post the final version of your code or mark the post that most closely matches you final SQL as the right answer. That way anyone who comes across this post later with a similar issue knows what the 'right' answer was.
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.