Spend crosses the budget line in Business Central. Nobody sees it until close.
The G/L has the transaction. The budget has the threshold. Business Central shows actual against budget whenever someone opens the G/L Balance/Budget page, and raises no alert when spend crosses the line. Its purchase approval limits check each PO’s own amount, not the budget it lands in.
This capability is on the OpsGrid roadmap, not shipped in the active beta today. The plan: G/L-to-budget threshold alerts, ranked and routed to a named owner. Tell us what you need and we’ll scope it against your BC data first.
Budgets set at last year’s input prices are meeting this year’s costs. In NAM’s Q3 2026 Manufacturers’ Outlook Survey, “increased raw material costs remained manufacturers’ top business challenge for the second consecutive quarter” (DC Velocity, 16 September 2026). CFOs in The CFO Survey expect unit costs to grow 4.8% in 2026, up from 4.5% a quarter earlier (Duke Fuqua, Richmond Fed and Atlanta Fed, 23 September 2026).
Two budget signals, on the roadmap for Business Central.
Not live in the beta today. This is the design for G/L-to-budget alerts. It reuses the named-owner Teams routing that runs today for inventory and supplier signals.
- Spend approaching a G/L budget threshold Ranked by how close to breach and how much is already committed
- Budget already breached, no documented approval Flagged at the next scheduled check, not at the month-end variance review
How this will work.
Even Signal isn’t there yet for this one.
Business Central raises no alert when spend crosses a G/L budget threshold. For this exception type, that alert is the first layer on the roadmap.
OpsGrid's live signals (stockout risk, stuck POs, supplier OTD) already run on the same named-owner architecture this capability will use.