📦 Purchase Order Update

Built from your feedback We have rolled out a major upgrade to the Purchase Orders, shaped directly by customer feedback from live projects. Over the past few months, we heard consistent themes: Coding needed to be clearer and more enforceable Draft POs needed proper edit capability Ex-GST visibility needed to align with budgeting and forecasting Cost code and cost type behaviour needed to be explicit, not implied This release addresses those directly. 🔄 Clearer Coding Mode Behaviour Many of you highlighted confusion around header versus per-line coding. Per-line mode was still forcing a header-level cost code selection, which created unnecessary friction and defeated the purpose of line-level control. That is now fixed. Header mode applies one cost code across the entire PO Per-line mode applies cost codes at the individual line level No conflicting requirements No hidden logic Each mode now behaves exactly as expected. 🛡 Cost Type Selection Now Enforced When Required With Cost Types now live, several teams asked for stronger enforcement to prevent incorrect reporting. If a Cost Code has multiple Cost Types attached, you must now explicitly select the correct Cost Type when creating or editing a PO. This removes ambiguity and protects reporting accuracy. If only one Cost Type exists, it auto-selects. If multiple exist, you choose. This improves: Forecast accuracy Margin visibility Delivery method reporting Cost breakdown clarity You no longer need to rely on memory or naming conventions. ✏️ Proper Edit Capability for Draft POs Another consistent request was the ability to correct draft POs without workarounds. You can now: Edit header information Modify scope and dates Add, remove, or adjust line items Update quantities, rates, and coding Switch coding mode on draft POs with clear confirmation prompts Approved POs remain protected to maintain financial integrity. This closes a real operational gap and removes dependency on support intervention. 👀 Cost Code Visibility Where You Need It Several users flagged that verifying coding required too many clicks. The PO detail view now clearly displays cost codes against each line item, including readable identifiers. You can instantly confirm: Which cost code is applied Whether coding is header or per-line If anything is unassigned This makes month-end review and audit prep significantly easier. 💰 Ex-GST Alignment at Register Level Commercial builders in AU and NZ manage commitments and margin on an ex-GST basis. The PO Register now displays ex-GST totals at summary and table level, aligning with: Budget registers Forecasts Margin analysis Xero financial data GST breakdown remains available in the detail view. No more ambiguity in committed cost positions. 🏢 Supplier Consistency Improved Supplier selection now pulls from the same Shared Companies directory used across the platform. This ensures: Cleaner reconciliation No mismatched supplier references Alignment with Xero integration ⚙️ Stability Improvements We also resolved several issues raised by users: Payments tab crash fixed Xero date formatting corrected Variation value colour indicators restored Drawer refresh stability improved Clearer API error messaging These are quiet fixes that improve daily reliability. Why This Matters Purchase Orders sit at the centre of cost control. Small inconsistencies in coding, editing, or financial visibility can create downstream reporting issues that compound over time. This update strengthens the PO Register as a reliable commercial control surface: Coding is explicit Cost Types are enforced Draft POs are editable Approved POs remain protected Financial values align with how builders actually track costs We appreciate the feedback that led to this release. It directly shaped what was prioritised. More Commercial improvements are coming. If there are further edge cases you want us to pressure-test, keep them coming.