Budget control that never blocks, grant limits and a year-end purchase freeze

Work from the budget register outward, because that is where the evidence points.

1. Budget register entries in Draft do not provide budget funds available. Draft entries must be completed for the budget model and budget type that the budget control configuration uses. Verify the entries for the current fiscal year are completed and that the model and type match what budget control reads.
2. Configuration activated. A configuration that exists but is not activated does not check anything. Confirm the budget control configuration is activated for the legal entity, and that the budget funds available definition includes the sources you expect (original budget, transfers, actual expenditure, and whether draft or unposted items should count).
3. Source documents and posting types. Budget control only runs for the documents and posting types enabled in the configuration. If purchase requisitions are enabled but vendor invoices and ledger journals are not, purchasing-card spend and manual journals bypass it entirely.
4. Over-budget permission. Confirm which user groups hold permission to exceed budget and whether the setting warns or blocks. A warning that everyone dismisses is the same as no control.

Only after these are true should anyone discuss tightening the budget itself.

Grants need budget control at the dimension combination level, not at main account only. If budget control checks only main accounts, a grant can overspend while the department's overall main account balance still looks fine until year end.

Design:

• Include the grant dimension in the budget control dimension set that is used for checking, so available funds are evaluated for the specific grant combination.
• Create completed budget register entries per grant combination, matching the award letter, and record amendments as budget revisions with an audit trail.
• Use budget control statistics and budget analysis inquiries so grant managers can see available funds per grant in the finance app instead of a spreadsheet.
• Restrict over-budget permission to a named group, and require a documented award amendment before posting beyond the grant amount.
• For grants that span fiscal years, align the budget cycle to the award period and plan carry-forward rather than re-entering the budget each July.

Judgement point: a single county-wide budget with grant tracking outside the system is what produced the spreadsheet, so the control must sit on the dimension combination itself.

Purchasing cards. Because the spend enters through the vendor invoice journal, budget control must be enabled for that document and its posting types, otherwise the check happens after the money is gone. Better, route card spend through purchase requisitions or a dedicated purchasing policy so it is checked at commitment. At minimum, check at invoice and report the gap between check time and commitment time to the audit committee rather than describing it as prevention.

Carry-forward. Use budget control carry-forward rules rather than manual transfers: define the rule for the three departments and the supply main accounts, and confirm the rule keys on the accounts and dimensions you actually use. A manual transfer is invisible to the next budget cycle and erodes trust in the numbers.

June freeze. Budget control has no date-based block, so do not try to force it there. Use a purchase order approval workflow with a conditional decision on accounting date plus main account or procurement category, so capital orders in the last two weeks require an extra approval that other orders do not. Alternatively reduce the capital accounts' remaining budget by a documented budget transfer, which is auditable and shows in budget analysis. Do not block vendors globally; that stops unrelated departments.