A forgotten detail in Acumatica Inventory Management ended with a sizable ripple effect to one of our customer’s GL. It is the Reason Code.
For inventory transactions that are related to buying (inventory receipt from purchasing) or selling (inventory issue for sales), Acumatica applies default accounts for AP bills and AR invoices without user intervention. Direct inventory transactions do not contain information about why inventory items are being processed. To track them properly, users must specify a reason code. It is customary to put in a set of reason codes during initial deployment for inventory issue, adjustment, transfer, disassembly and/or vendor return, and Acumatica associates them by ‘usage’ to the forms that execute these transactions.
Things went off script when there were multiple reason codes with the same usage type. For example, ‘Issue’ is used to decrement inventory for projects as well as for inventory write-off. When an inventory issue record is missing a reason code on release, Acumatica chooses the first reason code with the ‘issue’ usage in ascending order.
For the time being, users have been reminded to use reason codes and asked to move the ‘Reason Code’ column in the Transaction Details tab to left of the grid for better visibility. For a permanent fix, we will configure the condition for reason code in a customization project. That will be the topic of another blogpost.
Any questions? Give us a call.
Eric.