Budget control
Budgets by cost center that warn or stop spending before it happens, not after.
The problem
A budget built in a spreadsheet in January is forgotten by April. Spending is approved one purchase at a time with no view of what is left, and the overrun shows up in the quarterly numbers when it is too late to do anything about it.
How it runs in Sundial
1. Create budgets in Finance & Accounting for the fiscal year, by cost center or by project, against the expense accounts that matter. Spread them evenly or by a monthly distribution you define.
2. Choose what happens when a budget would be exceeded: stop the transaction, warn the person entering it, or ignore. You can set different actions for the monthly and annual limits.
3. Apply the check where spending starts. Budgets can be checked on material requests and purchase orders, as well as on actual expenses posted to the books.
4. When a buyer raises a purchase order that would cross the limit, Sundial warns or blocks it at that moment, before the commitment is made.
5. Review the budget variance report monthly: budget, actual and variance by cost center and account.
What the team sees
Department heads see what is left in their budget before they ask for anything. Buyers see the warning at the point of ordering. Finance sees budget against actual without building a spreadsheet, and the owner sees which cost centers are on track.
Sample for Kestrel Workspace: marketing at 82% of annual budget in November, one purchase order stopped this month, travel under budget by $18,600.
With AI (coming to Sundial)
Sundial is designed for an agent to project where each cost center will land by December at its current pace and flag the ones heading over. This is coming to Sundial; today the variance report shows the position to date.

