@rena98 are subaccounts different from project to project?
Hi there,
Yes, they differ from project to project. They have a three-segment subaccount structure and any of the three segments can be different per project. It would not be practical to setup a reason code for each variation of the subaccount structure.
It is related to this issue: Allow Reason Code to choose Project Task subaccount in Inventory Issue screen | Community (acumatica.com)
I was curious how other people were navigating around it while we wait for the solution to be implemented.
Rena
@rena98 thats where i was going too, possibly creating different reason codes for the different variations but that sounds clunky for sure!
I would upvote that idea if you haven’t already but it sounds like the only option would be customizing the system to include project subaccount.
could you possibly set up a business event to reclassify the transaction lines to the correct subaccount from the project after the initial transaction has posted? only thing is, i dont think this would update the project transaction
This is the reply that I got from support:
We added this possibility to 24R2.
1. Reason Codes (CS211000)
- J - From a subaccount associated with the project.
- T - From a subaccount associated with the project task
2. Posting Classes (IN206000) form