Skip to main content
Solved

COST CODES

  • Aug 24, 2023 4:13 PM UTC
  • 2 replies
  • 201 views
  • Translate All

Is there a way to limit who is able to add cost codes to the job? Like admin rights for cost codes?

I am trying to customize this so no one in the company can invoice to a cost code that wasn't used within the job. 

Best answer by valentynbeznosiuk

Hi ​@AP13 

Out of the box, Acumatica can warn users when they post to a cost code that isn't in the job's budget, but it can't stop them. By default, if someone enters a bill or PO with a project task/cost code combination that doesn't exist in the cost budget, the system just adds a new budget line for it when the document is released.

In Project Preferences, you can set Budget Control to "Show a Warning." Users will then see a warning on Bills and Adjustments, Purchase Orders, and similar screens when a line has no budget (or exceeds it). It won't block the save, but it does make it obvious that something's off. If you want it to actually block such documents, you'd need a customization for that — it could potentially turn this warning into an error that prevents the document from saving, or allow the save but prevent the document from moving further through the workflow.

View original

2 replies

Forum|alt.badge.img
  • Jr Varsity II
  • Sep 25, 2026 6:26 PM UTC

Did you find a solution for this issue? 

Translate

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

Hi ​@AP13 

Out of the box, Acumatica can warn users when they post to a cost code that isn't in the job's budget, but it can't stop them. By default, if someone enters a bill or PO with a project task/cost code combination that doesn't exist in the cost budget, the system just adds a new budget line for it when the document is released.

In Project Preferences, you can set Budget Control to "Show a Warning." Users will then see a warning on Bills and Adjustments, Purchase Orders, and similar screens when a line has no budget (or exceeds it). It won't block the save, but it does make it obvious that something's off. If you want it to actually block such documents, you'd need a customization for that — it could potentially turn this warning into an error that prevents the document from saving, or allow the save but prevent the document from moving further through the workflow.

Translate