Hi There,
I’ve encountered an issue with retainage behavior during AP bill reclassification in Acumatica ERP and would like to confirm whether this is expected or a configuration issue.
Scenario:
- An AP bill is created with a project, task, and retainage applied.
- The bill is released, and retainage is tracked correctly under the project.
- Later, I perform a reclassification on one of the bill lines to another project (using the reclass functionality). The original line was code to wrong project about (10% of total cost) The 90%cost is under project A, and AP retainage is under project A
Issue:
- The expense is reclassified correctly to the new project.
- In the AP Retainage Register, the original retainage disappear from Project A, but appears under a non-project code (empty project / X).
Expected Behavior:
I would not expect the AP Retainage register change the project code but remains under same project code
Questions:
- Is this the intended behavior in Acumatica?
- Are there specific configurations (e.g., account groups, retainage accounts) required to ensure retainage stays tied to the project during reclassification?
- How can I fix this now? Move the retainage appears under Project A in AP Retainage Registe.