Context I work in sales for Agave, the leading ERP integration partner for Autodesk Build clients. We’re working with a Canadian general contractor who is implementing Cost Management and needs financial data to sync accurately with their ERP, Viewpoint Vista.   Issue In Vista, users can apply unique tax codes and amounts at the line item level on invoices and purchase orders. This is critical for construction accounting and billing, especially for Canadian firms with complex tax requirements.   Autodesk Build’s Cost Management, however, only exposes tax amounts at the header level through the API. This prevents our integration from passing tax codes and amounts line by line. As a result, our client’s accounting team would need to manually reapply correct tax codes in Vista - adding unnecessary work, increasing the risk of errors, and breaking data consistency.   Impact This limitation makes it difficult for clients to confidently move invoice and PO workflows from Vista into Autodesk Build, even though that shift would otherwise allow project managers to own the process and realize the broader benefits of Cost Management.   Requested Improvement Enable Autodesk Build’s API to support tax codes and amounts at the line item level. This would: Allow seamless, accurate sync between Autodesk Build and Vista (and other ERPs) Reduce manual rework and data entry errors Support compliance with Canadian tax reporting requirements Increase confidence for customers adopting Cost Management Closing We understand this may require additional development, but believe it would be a valuable enhancement for many construction customers with sophisticated tax needs. Please let me know if we can provide more detail as you evaluate this request.   Thank you, Vincent Agave Show More

Description: When iterating through {#oco.costItems} to display the budget code, the OCO number is repeated for each cost item, even if they belong to the same change order. This leads to redundant data in the report. Example Use Case: For an OCO with multiple cost items, the current output is: {#oco.costItems} {oco.number} - {budgetCode.formatted} {/oco.costItems} Which results in: OCO-001 - BGT-1234 OCO-001 - BGT-5678 It would be more efficient and create a cleaner report if there were a way to consolidate or select a primary budget code. A new function or variable could allow for this, for example: A variable that returns a comma-separated list of all budget codes for a single OCO. A variable that returns only the first or primary budget code for the OCO. This would significantly improve the readability of templates that need to show budget codes for change orders. Show More

A recent release in the Cost Management added budget amounts to the Change Order tools when selecting budgets- this way when you are selecting a budget you can see how much money is remaining in the budget. Currently it shows Revised Budget less Actual Cost. Can we change this to be Revised Budget minus projected cost?  This way we are moving money around based on what we think we will spend instead of what have spent.    Show More

As we undergo digital transformation, we need to transfer all our data into the web platform. One key feature we would like to have is the capability to import our Master VO Lists (currently stored in Excel files) directly into the Cost Items section of Change Orders within the Cost Management system. This functionality would facilitate our smooth transition to a digital environment.    Thank you.  Show More

It will beneficial to have additional functionality that allows us to feature/highlight/filter specific item by code or name within the breakdown of the contract (refer to the screenshot below).      The enhancement would help us better manage and track the various components of our contracts, making it easier to identify or manage the key items and improve our overall project oversight.  Show More

Ability for Subcontractors who are collaborators to create unattached cost items on project. This feature would allow General Contractor to have ability to review, approve, or reject submitted cost items not associated with an RFQ. Once the cost item is approved, the general contractor can either create new PCO or attach to an existing PCO.   This would allow sub contractors to submit change orders that are not necessarily associated with RFQs but it informs General Contractor of all open and outstanding change orders from the subcontractor's log. Provides full picture of all potential costs. Show More

Default CC people in cost when sending contracts/invoices/etc. Each time we send a contract we have to manually CC people and remember to do that. We want to be able to set default people for the CC line so we only have to set this up once. If we forget to CC someone on a contract, we don’t get the information we need to people that need it and it slows workflows. We are manually copying people. Show More

Currently there are uncountable limitations in the cost management module. If possible, I would like to break them down and hope from Autodesk Team to solve them as soon as possible as these are already hurting operations. Budget:  1- Budget limitation of 10,000 budgets per project. Most mega projects have at least 5000 Bill of quantities line items. Just imagine the number of budget line items associated to those. make the limit to be at least 50,000 budget line items. 2-Budget subitems. Currently budget sub items follow the hierarchy of the budget line item, what is need that the subitem to have fixed classification code as its main item, or to have at least the option to make it available from the account admin. 3- Mapping budget to BOQ line item in SOV of the main contract. What the system is missing is a better way to have a direct and easy comparisons between BOQ selling/ Budget / Cost. linking them (as sum(if)) in excel would make the software applicable to use. 4-Importing Custom Attributes. I don't know about this but having to use APS or manually entering Mutiple custom attributes for Mutiple budgets/contracts doesn't make the cost management module applicable to use, also having the ability to have calculations on numeric field in custom attributes is a must.   There are many needed customizations needed for the cost management module, but I think from my perspective that those are the most needed to be applied right now. Show More

In projects typically project risks are identified in the early stages of the project and may materialise into a PCO / CO and then ultimately a project cost. It would be great if this workflow stream was considered within the Cost module.    One thing that would be required for this would be to introduce formulas into the metadata / custom attributes for things like risk score and calculating the risk cost  Show More

ACC already has snapshoto function on Budget section. It would be great if ACC can also have the same function on Cost and Change Order section as well to ensmooth the audit. Show More

Currently we would like to setup Change request workflows so they go to the appropriate team members for each review type.    Our CRs are split into cost banding which is easy to do but then they are further split down into the CR type, which is a current metadata field we have added e.g. Design, Operations, Customer change etc...    At the moment there is no field we can select to further split these out. If custom metadata fields could be added this would really enhance the CR customisation and make it easier to direct the CRs to the appropriate technical reviewers Show More

The first document in the Document Package is always the commitment document and does not need to be listed as an Exhibit. Show More

We rely heavily on the project number. It would very beneficial to have the project number under the name. While in Cost you have to navigate into Build then in to settings to find the number. Which is time consuming.  Show More

We are using the Signing feature through Autodesk but realized that suppliers can still invoice against change orders that are not fully executed. That should not be the case. Once executed they should be able to bill against it, but not before that.  Show More

We have very large change orders sometimes with several (sometimes 100+) budget codes. We need an easy way to export all budget codes at once to build the SOV import (like how commitments SOVs Excel import work in Cost)  instead of having to export each budget codes one at a time. Show More

When exporting our schedule of values from Cost and Change Orders to build the commitment in Excel, we would like the ability to include custom attributes in the export. For our case it would be an address field so the supplier would know where to ship the material.  Show More

For certain change order types (owner), for example contingency types that transfer budget, we would like the option to restrict setting the status to executed if the sum of the lines do not net $0.    Show More

Description: The current payment.totalApprovedChangeOrders variable returns a single numeric value, making it impossible to filter by attributes like ccoType. It would be very useful for creating detailed payment applications to be able to sum approved change orders of a specific type (e.g., "Owner Unit Selection") directly within a single cell.   Example Use Case: We need to display the sum of all "Owner Unit Selection" change orders in a payment application. A variable structure like {payment.totalApprovedChangeOrders | filter:"ccoType":"Owner Unit Selection" | sumBy:'approved'} would provide this functionality, but it currently does not work because totalApprovedChangeOrders is a number, not a collection.   This feature would allow for more precise financial reporting and customization within payment application templates without requiring complex workarounds. Show More

Description: The current system does not provide a direct, iterable collection of all change orders linked to a payment application with type-filtering support. This makes it difficult to create custom report sheets that only display change orders of a specific type (e.g., "Owner Unit Selection"). Example Use Case: We need to generate a separate sheet in our payment application template that exclusively lists all OCOs of the type "Owner Unit Selection" along with their details (name, number, approved total, and cost items). Currently, the standard variables do not expose the change order type in a way that allows for this specific filtering. This feature would enable greater customization and allow us to create focused, type-specific reports for our clients and internal teams without manual data manipulation. Show More