Treasury Cash Liquidity Planner

The Treasury Cash Balance & Minimum Liquidity Buffer Planner calculates the "safe" amount of cash a business needs to survive shocks without disrupting operations. It moves beyond "gut feel" to a component-based approach. ## Concept Overview Liquidity planning balances **safety** (having enough cash) with **efficiency** (not hoarding cash). The model stacks three buffers: 1. **Operational:** Keep the lights on (Payroll, Rent). 2. **Volatility:** Absorb AR delays or sales dips. 3. **Strategic:** Capital for unexpected opportunities or shocks. ## Key Variables & Intuition * **Burn Rate (OpEx):** The base outflow. Higher burn = higher required buffer. * **Revenue Volatility:** Stable subscription revenue requires a smaller buffer than lumpy project revenue. * **Cash Conversion Cycle:** If it takes 90 days to get paid, you need 90 days of cash to bridge the gap. * **Access to Capital:** If you can raise money easily, you might hold less cash. If credit is tight, hold more. ## Assumptions * OpEx is relatively constant. * The "One Time Shock" captures the single largest risk event (e.g., server outage, lawsuit settlement). * Liquid assets are truly liquid (T+0 or T+1 access). ## Limitations & Edge Cases * **Black Swans:** No buffer protects against total market collapse; that requires business pivots. * **Hypergrowth:** Rapid hiring consumes cash faster than historical OpEx suggests. * **Seasonality:** Averages mask seasonal cash crunches (e.g., retail before holidays). ## Practical Tips * **Ladder your Cash:** Keep 1 month in Checking, 2 months in High Yield Savings, 3+ months in T-Bills. * **Stress Test:** Ask "What if our biggest client pays 30 days late?" * **Monitor Covenants:** Know your bank loan requirements. * **Don't count uncollected AR:** Revenue is vanity, cash is sanity. ## Common Mistakes * Using tax money (VAT/Sales Tax) as operating cash. * Ignoring annual lump sums (insurance, software renewals). * Confusing personal credit limits with business liquidity.

Treasury and liquidity management has evolved from simple checkbook balancing to complex, algorithmic risk management strategies used by businesses of all sizes. ## Origins & Why It Emerged In the pre-digital era, "cash management" meant literally managing physical cash and ensuring enough was in the bank for payroll checks to clear. The high interest rates of the 1980s made idle cash expensive (high opportunity cost), driving the development of "sweep accounts" and sophisticated treasury functions. The 2008 financial crisis highlighted that "profitable" companies could die overnight from liquidity freezes, cementing liquidity risk management as a board-level priority. ## How It Evolved in Practice Initially, only large corporations had "Treasury Departments." Mid-market firms relied on controllers. Excel was the primary tool. As supply chains globalized, cash cycles lengthened, increasing risk. The introduction of TMS (Treasury Management Systems) in the 2000s allowed real-time visibility into global cash positions. ## Modern Usage Today Today, even startups plan "runway" and "buffers" meticulously. The collapse of Silicon Valley Bank (2023) was a stark reminder of counterparty risk, leading modern treasury policies to diversify holdings across multiple banks and instruments (e.g., money market funds). API-driven banking now allows real-time liquidity forecasting. ## Common Misconceptions * **Profit = Cash:** A profitable company can go bankrupt if it runs out of cash (e.g., waiting for AR). * **Credit lines = Cash:** Relying solely on lines of credit is risky; banks can cut them in a downturn. * **Cash is safe:** Inflation erodes cash; bank failures threaten it. Cash needs active management.