Skip to main content
Question

Cannot Remove Hold on Subcontract when a Project is Completed

  • September 24, 2026
  • 3 replies
  • 33 views

Forum|alt.badge.img

Hi everyone 

I hope you're having a great week! I'm running into an issue with Subcontracts and Projects in our system, and I'd love to get some advice from the community.

Here is our current process:
We have a 1-year Subcontract with a Vendor that covers multiple Projects. Each month, we:
1. Reopen the main Subcontract.
2. Add a new line for the current month's payment (linked to an active Project).
3. Click Remove Hold to process it.
4. Create an AP Bill to pay the vendor.

The Problem:
Over time, some older Projects on earlier lines have been marked as Completed. Now, whenever we Reopen the Subcontract to add a line for a new month, the system blocks us from clicking 'Remove Hold' because of those Completed Projects—even though the old lines linked to them are already Closed.

What we expect:
The system should only check the Project status for Open lines, and ignore Closed lines so we can keep processing the main Subcontract.

Has anyone faced this issue before? Is there a recommended setup or workaround for this, or do we need to customize the system logic?

Thanks a lot for your help!

3 replies

nhatnghetinh
Captain II
Forum|alt.badge.img+13
  • Captain II
  • September 24, 2026

Hi ​@nomii 

A practical workaround is to use separate Subcontracts for Projects with different lifecycles, rather than keeping completed and active Projects on the same long-term Subcontract. If the business requires keeping one Subcontract, then customization may be required to change the validation so that closed/completed lines are ignored.

 

Best Regards,

NNT


mohammadnawaz51
Varsity I
Forum|alt.badge.img+7

​@nomii 

There is also precedent in Acumatica's documented workflow for keeping an existing subcontract and modifying commitments through change-order processes rather than continuously replacing the commitment; existing commitments can be selected and changed through Construction Change Orders

 

The safest short-term workaround is not to temporarily reopen the completed projects every month unless absolutely necessary. That changes project lifecycle status simply to get around document validation.

I confirms the behavior is by design, then a customization would be reasonable. 


Steve Milner
Varsity III
Forum|alt.badge.img+4
  • Varsity III
  • September 24, 2026

@nomii The check isn't looking at line status at all. Reopen puts the subcontract on hold, which deletes the project commitment on every line, closed ones included. Remove Hold rebuilds them all, and a commitment can't be created on a Completed project. No setting skips closed lines, so keeping your Reopen process as is would take a customization. While it sits on hold, those closed lines also drop out of the completed projects' committed amounts.

If yours is stuck on hold now, activate the completed project, then run Activate Tasks on its Tasks tab (the project alone still fails on the completed task). Remove Hold, then complete the tasks and the project again.

Going forward, @nhatnghetinh's separate subcontracts avoid this completely. If your projects use Change Order Workflow, @mohammadnawaz51's change order route keeps one subcontract. Add a change order on the active project with a Commitments line where Commitment Type is Subcontract, Commitment Nbr. is your subcontract, and Commitment Line Nbr. is blank (status New Line). Releasing it adds the line without putting the subcontract on hold, so the old lines are never rebuilt. Joel's walkthrough: https://community.acumatica.com/construction-120/adding-a-line-to-a-purchase-order-via-a-change-order-30210

Try that on a test copy first. Once a change order touches a subcontract, Hold and Reopen are disabled on it, so later changes go through change orders too. Tested on 2026 R1.