Scenario: A user with an Administrator role noticed that the Global Account Mapping set up for their Secondary Book is not working in some Journal Entries even though the same source account was used. The Account Type is Accounts Payable.
The user configured the mapping in Setup > Accounting > Global Account Mapping as follows:
He then created two Journal Entries with the following details:
First Journal: Without Entity tagged in Name field
Second Journal: With Entity tagged in Name field
In the above screenshots, you will observe the following:
- Same information were entered in the two journals, except that the second Journal Entry has an Entity tagged in the Name field.
- The first Journal Entry Accounts Payable_Source line (Primary Accounting Book) was successfully mapped to Accounts Payable_Destination (Secondary Book) while the second Journal Entry was not.
Conclusion: The described behavior above is standard. The ability to use Global Account Mapping for Accounts Receivable/Accounts Payable lines associated to Entities is currently a system limitation and an Enhancement is logged for it: Enhancement 363121 Ability to use Global Account Mapping for Accounts Receivable/Accounts Payable lines associated to Entities. Said behavior also applies to other transactions such as Vendor Bills, etc. As long as the Accounts Receivable or Accounts Payable line is associated to an Entity, the system will not use the Destination Account in the GL Impact of the Secondary Book.
The workaround documented in the said Enhancement record is to utilize the Accounting Context Preference. For more information, you may refer to the following SuiteAnswers articles: