Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Ability to change budget coding (both revenue and cost) on Change Orders when Change requests are used

When recording Change Requests, being just contemplated change, it is not known (or certain) what will be exact impact on the cost budget and how it will reflect billing schedule (if new revenue item on SOV will be required or future CO will be associated with one of the existing items on SOV). It is also common practice that multiple CRs are approved by one CO and that only at that time we know for sure how billing (and cost) schedules will be affected. For example, if CO is significant, it is very likely that it will be billed as a separate item on SOV. Therefore, we should have ability to change coding on Change Orders form before it is released (changes would need to update underlying change requests as well). It will be also logical to allow creation of new project tasks from CO screen. If CO needs to be aligned with the new project tasks, it makes no sense to have to close CO, go to Projects, setup new task and then go back to CO

  • Guest
  • May 1 2020
  • Attach files