Cash budget: project inflows, outflows, and balance

A cash budget projects a company's future inflows, outflows, and balances. It shows whether enough money will be available when each obligation is due and when the business needs to borrow, invest, negotiate, or postpone a decision.

Unlike an income budget, which recognizes revenue and expense on an accrual basis, a cash budget follows collection and payment dates. A sale can improve the income statement today and reach cash only 60 days later.

This guide shows how to build an operating cash budget, connect it to automated cash flow, and turn it into a treasury routine.

What a cash budget is and is not

A cash budget organizes, by day, week, or month:

• opening balance;
• expected collections;
• committed payments;
• estimated outflows;
• investments and redemptions;
• borrowing and repayments;
• closing balance;
• distance from minimum cash.

It may cover 13 weeks for treasury and 12 months for planning. The horizon changes, but the logic is the same: convert business events into cash dates and make the assumptions behind every amount explicit.

A cash budget is also not the same as a generic forecast. A forecast may estimate sales, margin, or earnings without indicating in which account the money will settle. Nor is it an accrual budget, which allocates revenue and expense to the economic period. The cash budget receives assumptions from these tools but applies terms, due dates, taxes, withholding, and probabilities to determine financial availability.

Are a cash budget, cash flow, and cash flow statement the same?

No. The instruments are connected but answer different questions.

Instrument	Main question	Basis
Actual cash flow	What came in and went out?	Settled bank transactions
Cash budget	Will the balance be sufficient on each date?	Future events and probabilities
Cash flow statement	How did the company generate and use cash?	Accounting classification for the period
Generic forecast	What result or trend is expected?	Operating and financial assumptions
Accrual budget	Which revenue and expense belongs to the period?	Accrual accounting

An automated cash flow statement explains operating, investing, and financing activities. The cash budget guides daily collection, payment, and liquidity decisions.

Daily, weekly, and monthly structure

A combined structure avoids two extremes: excessive detail in the long term and insufficient detail in the short term.

• Daily, for 7 to 14 days: shows due dates, settlements, transfers between accounts, and bank cut-off times. This view supports decisions about what to pay and where to hold balances.
• Weekly, for 13 weeks: groups events by week, preserves significant items, and highlights the lowest liquidity position. It supports collection, funding, and negotiation.
• Monthly, for up to 12 months: connects seasonality, investments, debt, taxes, and annual budget assumptions. It anticipates structural needs without pretending to offer daily precision.

The last month should not simply repeat the first. Granularity decreases as uncertainty grows, and each layer must reconcile with the next one.

Direct method: from movement to balance

For liquidity management, the direct method lists collections and payments by type and date. The starting equation is:

available opening balance + inflows - outflows = available closing balance

The closing balance of one period becomes the opening balance of the next. Transfers between accounts belonging to the same entity are eliminated on consolidation because they do not create cash for the group. Immediately liquid investments may appear in a separate column so the availability policy remains visible.

The direct method differs from the indirect reconciliation used in accounting analysis, which starts with profit and adjusts noncash items and changes in working capital. Both are useful, but the direct method provides the date and amount needed for treasury operations.

Data sources and opening balance

Consolidate checking accounts, payment accounts, investments, acquirers, and other relevant balances. A bank balance is not automatically available cash. Separate:

• balances freely available for movement;
• investments redeemable within the horizon;
• cash restricted by contract, guarantee, or regulation;
• amounts in transit that have not been reconciled;
• unused credit facilities, without adding them to cash.

Typical sources include bank statements and APIs, ERP accounts receivable and payable, orders and billing, contracts, payroll, tax calendars, debt schedules, approved CAPEX, and sales projections. Each source should have an owner, update time, and rule for missing or duplicate data.

A composite key using entity, account, document, installment, and date helps prevent an item from being loaded twice. Reconciliation with bank balances confirms the starting point before the projection is recalculated.

How to project inflows with probability

Start with accounts-receivable items and adjust contractual terms, delay history, installments, withholding, taxes, card fees, and customer risk. Commercial revenue without a probable collection date should not be treated as committed cash.

A simple policy can separate:

• 100% or committed: confirmed, undisputed item with expected settlement;
• probable: issued item adjusted for customer behavior;
• possible: order or contractual milestone still subject to acceptance;
• scenario: sales opportunity kept outside the baseline.

Percentages should not be universal. They can vary by portfolio, aging range, payment method, and data quality. For a customer that usually pays eight days late, moving the date is often more informative than arbitrarily reducing the amount. Possible events must remain identifiable so the baseline does not blend with the optimistic scenario.

How to project outflows and priorities

Include accounts payable, payroll, taxes, suppliers, rent, debt, CAPEX, and recurring expenses. Classify each item as mandatory, approved, probable, or discretionary. Also record criticality, negotiation options, penalties, supplier, and owner.

A payment without an issued invoice may be probable when a contract and acceptance exist. CAPEX that has not been approved should remain in a scenario. This distinction supports prioritization without hiding commitments.

Taxes need their own calendar because accounting close and financial due dates are different. Payroll should include salaries, charges, and benefits. Debt should separate interest, principal, fees, and covenants that may restrict funds.

Multiple entities, currencies, and restricted cash

In corporate groups, build the view by legal entity first and consolidate it afterward. A positive balance in one entity does not automatically cover a shortage in another. Consider corporate, tax, regulatory, banking, and timing restrictions before planning intercompany loans or transfers.

For multiple currencies, retain original amount, currency, rate used, and equivalent in the reporting currency. Collections and payments in the same currency may provide a natural hedge, but should remain visible. Use an approved base rate and exchange-rate scenarios for material exposures. Currency effects must not be confused with operating inflows or outflows.

Restricted cash belongs in the financial position but outside the available balance. Record its reason, beneficiary, expected release date, and evidence. The same rule applies to court deposits, guarantees, and earmarked funds.

Spreadsheet or table model

A table-format database makes filtering, consolidation, and audit easier:

Date	Entity	Account	Currency	Category	Document	Inflow	Outflow	Probability	Status	Owner
Sep 21	Company A	Bank 1	BRL	Customers	INV-845	180,000	0	90%	Probable	Collections
Sep 22	Company A	Bank 1	BRL	Payroll	PAY-09	0	260,000	100%	Committed	HR
Sep 25	Company B	Bank 2	USD	Supplier	INV-31	0	40,000	100%	Committed	Procurement

In separate tabs or views, keep assumptions, exchange rates, account master data, calendars, imported actuals, daily summary, weekly summary, and change log. Formulas should reference the database, with no manually typed values inside totals.

Complete numerical example

A company begins Monday with BRL 500,000 available and BRL 120,000 restricted. The BRL 120,000 does not enter the available balance. For the week, it has:

• BRL 180,000 from a confirmed customer;
• BRL 150,000 from another customer at 80% probability, or BRL 120,000 in the probability-weighted view;
• BRL 260,000 in payroll;
• BRL 210,000 for suppliers;
• BRL 90,000 in taxes;
• BRL 90,000 in debt service.

Weighted inflows total BRL 300,000 and outflows total BRL 650,000. The projected closing balance is BRL 150,000. Because policy requires minimum cash of BRL 250,000, the gap is BRL 100,000.

The daily view shows that payroll is due before the BRL 180,000 collection, and the lowest intraweek balance would be BRL 40,000. Treasury therefore accelerates a BRL 60,000 collection to Tuesday and negotiates BRL 40,000 from a supplier into the following week. The weekly balance reaches the minimum, but daily control still verifies whether the collection settled. If the 80% customer is late, the stress scenario shows an additional BRL 120,000 requirement.

Minimum cash, gaps, and actions

Minimum cash is the threshold below which operations enter an attention zone. It can reflect payroll, taxes, collection volatility, customer concentration, and access to credit. It should be an approved policy, not a number chosen to make a chart green.

For each gap, assign an amount, date, action, owner, and deadline. Options include accelerating collection, postponing a negotiable payment, transferring permitted funds, redeeming an investment, or drawing a facility. The budget is incomplete if it identifies a shortage without recording the response.

Forecast-to-actual variance analysis

Freeze a baseline before each week begins and compare every event with bank actuals. Separate variance into:

• timing: occurred on another date;
• amount: occurred on the date but for a different amount;
• missing event: happened without a forecast;
• unrealized event: was forecast but did not happen;
• classification: occurred but was assigned to the wrong category.

Measure error in absolute and percentage terms, by category and horizon. Offsetting a delayed inflow with a smaller outflow can leave the total correct while hiding two problems. Root-cause analysis produces actions such as correcting ERP terms, revising a probability rule, or following up with the responsible team.

Governance, routines, and controls

Treasury can update balances and movements daily. In a weekly 30 to 60-minute meeting, treasury, accounts receivable, accounts payable, and FP&A review gaps, largest variances, low-confidence events, and actions. Monthly, finance connects the 13-week view with the annual budget, debt, and investments.

Essential controls include role-based access, a change trail, approval of critical assumptions, segregation between preparation and approval, bank reconciliation, and baseline locking. Every line should have a source and owner. Manual adjustments need a reason and expiration date.

Implementation plan

1. Define scope and policy: entities, accounts, currencies, horizon, minimum cash, and scenarios.
2. Map sources: record the owner, frequency, key, and quality of each data set.
3. Build the direct database: load balances, collections, and payments without premature aggregation.
4. Create rules: handle delays, recurrence, probability, currency, restrictions, and eliminations.
5. Validate in parallel: run for four to eight weeks and reconcile with actuals.
6. Establish routines: set cut-off time, meeting, approvals, and a plan for gaps.
7. Automate exceptions: after concepts stabilize, integrate sources and prioritize discrepancies.

Automation should update dates and statuses without removing judgment. An overdue invoice can use delay history, while an unbilled sale remains a scenario rather than a guaranteed inflow.

Metrics to track

• weekly forecast accuracy;
• absolute and percentage forecast-to-actual error;
• lowest projected balance;
• days below minimum cash;
• collection concentration by customer;
• payment concentration by date;
• funding requirement;
• restricted cash as a share of total cash;
• net exposure by currency;
• percentage of manual adjustments;
• items without an owner or source;
• funding and idle-cash costs.

Metrics need thresholds and actions. For example, weekly error above tolerance requires analysis of the three largest causes, while a balance below minimum cash requires an approved plan before the gap date.

Common mistakes

• treating accounting revenue as a cash inflow;
• ignoring customer delays;
• projecting tax only at month-end;
• mixing available and restricted cash;
• hiding CAPEX and discretionary payments;
• updating the file without recording variance;
• allowing treasury and FP&A to keep different versions.

Cash budget FAQ

What is the best horizon?

Thirteen weeks works well for liquidity management. The annual budget adds context but does not replace short-term detail.

Can a cash budget be built in a spreadsheet?

It can start there. When multiple accounts, entities, or thousands of items are involved, integrations and rules reduce delay and error.

How often should it be updated?

High-volume businesses may update daily. At a minimum, treasury should review inflows, outflows, gaps, and variances weekly.

How does it connect to the annual budget?

The annual budget supplies monthly assumptions. The cash budget converts them into collection and payment dates and refreshes them with actuals.

How should events without reliable probability be treated?

Keep them in a separate scenario with an amount, date window, condition for occurrence, and owner. This preserves visibility without contaminating the baseline.

Conclusion

A strong cash budget does not promise perfect accuracy. It shows where the balance may fall below the required level and which decision should happen first.

Abstra connects banks, ERP systems, and treasury rules to update inflows, outflows, balances, and exceptions without rebuilding the spreadsheet each cycle.

To structure an automated cash budget, talk to an expert.