Is there a way to limit a Project Task and Cost Code combination to only those that exist on a Project Cost Budget?

  • 5 November 2020
  • 3 replies

In many screens, such as PO, Issue, AP Bill, Receipt, even Project Transactions, the system allows a user to choose an existing Project Task and then apply any Cost Code existing on the project to that Task even if that combination of Project Task/Cost Code does not exist on the Project Cost Budget.

The system currently adds a new row in the Cost Budget, which to my client is a real issue.

Furthermore, it would be additionally helpful to NOT allow new Task/Cost Code/Account Group combinations beyond what exists on the Cost Budget.

Has anyone else ran across this issue and were you able to prevent it from happening?

3 replies

Userlevel 4
Badge +4

Hi @tsnyder16 

Here is the Budget control option what we have on Document entry (documentation link below). You may post a feature request on our Product idea page ( to extend the functionality to meet your requirement. I don't see an option to restrict use of Project Task/Cost Code combination based on budget.


Hope this helps,


Userlevel 2

I agree that this would be very convenient. In fact, I have noticed this myself during demos and I’ve had questions about it.

This would require a controlled addition of a task, phase, cost code and perhaps start the change order process.

Please upvote this ‘idea’!


About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2020  Acumatica, Inc. All rights reserved