Set Default Cost Budget Fields in POs, Receipts, and Bills
Starting September 22, 2026, this functionality will gradually roll out to all customers. No action is required.
We’ve made creating purchase orders faster, easier, and more consistent.
You can now set cost budget fields such as Project, Project Phase, Department, Cost Code, Cost Type, and Revenue Type at the header level in Step 1 of the PO creation workflow. Once entered, these values automatically carry over to all line items in Step 2, reducing the need for repetitive manual entry and ensuring every line item stays aligned with your cost allocation rules.
This update not only speeds up your PO process but also reduces the chance of errors and inconsistencies.
Important: If you return to Step 1 and change a cost budget attribute, BuildOps will update the corresponding Step 2 line items. A warning will appear before any manual line-item changes are replaced.
More flexibility with Procurement Settings
We’ve added a new setting in Procurement Settings called “Do Not Default Project Cost Attributes”. This allows you to control whether these fields are automatically populated or left blank for manual entry.
Admins can manage this setting from Procurement Settings → General → Do Not Default Project Cost Attributes. Turn it on if your team prefers to enter these cost attributes manually.
Toggle OFF (default): Cost budget attributes will auto-fill where applicable.
Toggle ON: Fields remain blank, unless there is only one valid option available.
This setting also affects bill read-backs from connected accounting systems, including Intacct, NetSuite, and Spectrum.
With this improvement, you can:
Save time by setting budget attributes once, instead of for each line item.
Maintain consistency across your procurement documents.
Control how much automation is applied, depending on your workflow needs.