Comments
I do not agree with this functionality. I would like to suggest that for specific Posting Groups (such Customer, Vendor, Banking, Inventory, Fixed Assets). Once a posting has been done, the system should block you when you are trying to post to another GL account. The problem could raise that your subledgers (example Customer Ledger Entries - AR Aging) doesn't match the GL accounts - Accounts Receivable.
I would suggest to have at least the option in the setup to choose that you want to avoid, to post to multiple posting groups on a customer, vendor, bank, inventory and fixed asset.
The "centralized" gl accounts should also been setup "Direct Posting = No"
In order to guarantee the data compliance
The approval workflow currently does not support handling multicurrency purchases effectively. I highly recommend implementing this feature, as it would provide us with the flexibility to map the workflow based on either the amount in the purchase order/sales order header currency or the amount in the local currency (LCY). This feature is essential for the product to remain competitive with other ERP systems.
I am based in New Zealand and we have successfully implemented the voice channel with our local voice provider using our local existing phone number (country code being +64), so it is possible.
You could reach out to your local phone providers and ask if any of them are Microsoft Teams Phone Partners?