Perhaps the number formatting is better done in the Acoustic UI? Or is that very difficult?

Our acoustic export is sending both_funds_latest_native_amount as a number, currency code as a 3 letter ISO code, and then separately the currency symbol.

Since we send both_funds_latest_native_amount as a number, it's possible for the email team to use it as a segmentation option (i.e. target a group with that number > 10). If we switch to sending it as a localized string we would have to calculate the localization in SQL and it would no longer be usable on the email side for targeting.

@Ejegg you are right. And actually now that I'm digging deeper I see that this issue is actually just specific to Belgium because we do format our code to not include the decimal points for our amounts. So we can actually close this task as we currently have a fix in place and will just need to update it for the specific email that was sent to Belgium.