Why hard caps are mostly wrong
A hard cap of "$500/month per agent" creates two failure modes: (a) the cap is set too high → spend balloons without anyone noticing; (b) the cap is set too low → engineers hit it doing legitimate work and switch to their personal API key (now the org has no audit trail at all). The pragmatic alternative: attributed alerts that fire well before the spend is critical, with the data to investigate why.
Tiered alert thresholds
Default thresholds: 80% of monthly budget → notify the agent owner. 100% of monthly budget → notify the org admin. 150% of monthly budget → notify the CFO + the org admin (yes, AI spend can blow past budget — this is a warning signal worth escalating). Each threshold ships with the receipt evidence so the recipient can immediately see what drove the spend.
Per-employee budgets vs per-team budgets
Some orgs prefer per-employee budgets (Bob has £200/month); others prefer per-team budgets (the eng team has £5k/month, divide as you see fit). GenZAgents supports both — set the budget at any level (agent, project, team, org) and the alert fires when that level's spend crosses the threshold. The dashboard rolls up correctly at each level.
Currency normalisation
For globally-distributed orgs the budgets live in your reporting currency (typically GBP / EUR / USD). Receipts in any currency normalise on issuance using the daily FX rate. Quarterly spend reports are in your reporting currency end-to-end.
Anomaly + budget — complementary controls
Budget alerts fire on threshold crossings against expected baseline. Anomaly alerts fire on patterns deviating from baseline. They complement each other: budget tells you "you're spending more than planned"; anomaly tells you "the spend pattern is suspicious right now". Most incidents trigger one or the other; severe ones trigger both simultaneously.
Forecasting
The dashboard projects month-end spend from current-month trajectory. "If trend continues you'll hit £18k this month vs £12k budget". This forward-looking view lets finance teams act before the month closes, not after. Most CFOs we talk to find this more useful than the per-receipt detail.