Unit 4 / 12

Budgeting and Cash Flow Management

Gains:

  • Ability to have AI set up annual budget and weekly/monthly cash flow projections along with their assumptions
  • Ability to analyze budget-realization variances with AI and categorize their reasons
  • Ability to design AI-supported cash flow alert logic to see cash crunch scenarios early

A budget is a company's monetary plan for the future: how much income we expect in the coming period, how much we will spend, and what will be left over as a result. Cash flow management is the most critical and cruelest aspect of this plan; Because even when a company is making a profit, it can not make its payments and go bankrupt when it runs out of cash. There is a common saying in finance: “Profit is an opinion, cash is a fact.” AI plays two powerful roles in budgeting and cash management: on the one hand, it quickly establishes projections from assumptions, and on the other hand, it analyzes variances between budget and actualization and categorizes their causes. But a budget is only as good as the assumptions underlying it; The assumptions of every projection AI establishes must be clearly visible and owned.

In this unit, we will learn to set up the annual budget and short-term cash flow projection with AI, analyze budget-realization deviation, and design a warning logic that detects cash crunch early.

Concepts: Budget: Income/expense plan for the upcoming period. Projection: A forward-looking estimate based on assumptions. Variance: The difference between actual and budgeted. Cash flow projection: A forward-looking estimate of weekly/monthly cash inflow and outflow. Cash crunch: No cash left to meet due payments.

Establishing the Budget with Assumptions

A good budget starts with assumptions before numbers. It is not enough to say "turnover grows by 15%"; Whether this growth comes from price increase or volume increase should be seen separately. Requiring assumptions as a separate layer when having AI set up a budget provides transparency and makes it easier to change a single assumption and see the impact later.

layer

Content

Why is it kept separate?

Assumptions

Growth, price, collection term, cost ratio

Can be changed from one place

income plan

Turnover by product/channel

Derive from assumption

expense plan

Fixed and variable expenses

See its relationship with turnover

cash plan

Collection/payment timing

Build a bridge from profit to cash

Budget setting prompt: "Set a 2025 monthly income-expense budget for a service company. Assumptions: 2024 monthly turnover average is 500 thousand TL, annual growth of 12%, sales cost is 55% of the turnover, fixed expense is 120 thousand TL per month, 70% of the collection in the same month and 30% in the next month. First list the assumptions separately, then give the monthly table."

Variance analysis prompt: "Below are the 2024 3rd quarter budget and realization figures on an item basis (thousand TL). Calculate the variance for each item and calculate it as a percentage. Group the variances according to 'positive/negative' and possible cause category (volume, price, timing, one-time). Highlight the 3 biggest negative deviations. [budget and realization]"

Cash flow projection prompt: "Set up a 12-week cash flow projection. Starting cash is 800 thousand TL. Each week: expected collections, salary payment (300 thousand every 4th week), supplier payments and fixed expenses. Calculate the cash balance each weekend and mark the weeks when it falls below the critical threshold of 200 thousand TL."

Scenario cash prompt: "Give the same 12-week projection in three scenarios: base (collection plan is realized), pessimistic (20% of collections are delayed by one week), optimistic (collections are brought forward 3 days). In each scenario, specify the week when cash bottoms and the minimum balance."

Weak Prompt / Strong Prompt

WEAK: "Make us a cash flow statement." (Result: a no-assumption, no-schedule, useless template.) STRONG: "Set up an 8-week cash projection given starting cash, weekly collection plan, salary, and supplier payment timing; show the balance each week, mark the week the critical threshold was reached, and suggest three concrete actions for that week (collections acceleration, payment deferral, short-term financing)."

Mini Cases

Case 1 — Hidden cash pit. A company seems to close the year with profit, but AI points out that in the 7th week of the 12-week cash projection, the balance falls below the 200 thousand TL threshold or even negative. Why: a large collection falls in the 9th week and payroll falls in the 7th week. Solution: bring forward collection or arrange short-term financing for week 7. Without early warning, the company would have been in a difficult situation on the maturity date.

Case 2 — The real reason for the deviation. A retailer's 3rd quarter turnover is 8% below budget. Management thinks "demand has dropped." When AI separates the deviation into volume and price, it is seen that the volume is actually on target, and the deviation comes from the average price falling with the discount campaign. The action becomes different: the problem is not demand but pricing discipline.

Case 3 — Assumption overlooked. An analyst has the AI ​​set up a budget but forgets to give the collection maturity assumption. The AI ​​counts the entire sale as being collected in the same month and the cash projection turns out to be too optimistic. The analyst realizes the error because he has the assumptions listed separately: 40% of the collection actually arrives the following month. Once the assumption is corrected, the cash statement becomes realistic.

Attention: The most fragile point of cash projection is collection timing. If the assumption about when the money from the sale will arrive is too optimistic, the projection gives you confidence you don't have. Be sure to test the collection delay in a pessimistic scenario.

Early Warning Logic

The purpose of cash management is not to summarize the past, but to see the future. You can ask the AI ​​to set up an “early warning” logic: generate signals when certain thresholds are exceeded.

  • Threshold warning: In which week if the cash balance will fall below the critical level?
  • Trend warning: If receivables have been increasing for three periods, collections are deteriorating.
  • Concentration warning: Be careful if more than one large payment overlaps in a week.

Common mistakes

  • Hiding assumptions. If the assumption underlying the numbers is not visible, the budget cannot be audited.
  • Equalizing profit and cash. Even a profitable company can get cash strapped due to timing.
  • Setting up a single scenario. If collection delay is not tested, the projection will be deceiving.
  • Attributing deviation to a single cause. If the deviation is interpreted without breaking it down into volume, price and timing, the wrong action will be taken.
  • Not defining a threshold. If the "critical cash level" is not determined, the alert cannot be generated.

In summary

The budget is the monetary plan of the future, and cash management is the harshest reality of this plan. AI quickly establishes the projection and analyzes the deviation for reasons. But a budget is only as good as its assumptions: keep the assumptions in a separate layer, test collection timing pessimistically, and set up alert logic to anticipate the week when the cash balance will fall below a critical threshold. Do not interpret divergence without breaking it down into volume, price and timing.

Application task

Have AI build an 8-12 week cash flow projection for a company; Provide starting cash, weekly collection schedule, and timing of major payments (salary, taxes, supplier). Ask the AI ​​to mark weeks where the critical threshold is below and suggest three actions for those weeks. Then run the pessimistic scenario where 20% of collections are a week late and compare it to the week when cash bottoms out. Have the assumptions listed separately and review each one.

checklist

  • [ ] I had the budget/projection assumptions listed on a separate layer.
  • [ ] I have clearly defined the collection timing.
  • [ ] I determined a critical threshold for cash and marked the week below which it was reached.
  • [ ] I tested at least one pessimistic collection scenario.
  • [ ] I broke down deviations into volume/price/timing.
  • [ ] I wanted concrete action for the weeks when the warning was issued.
  • [ ] I did not miss the difference between profit and cash.