Cash flow forecasting assistant

Requirements describe capabilities the pattern needs in your environment, not the vendors you must buy. Any system that fills a requirement satisfies it — that’s what makes the catalog portable across the long tail of SMB tooling.

1. cash_position_source

   REQUIREDREADrequest

   Current cash and equivalents across all accounts.

   DATA SHAPE

   Per-account balance with last-update timestamp, currency, restrictions if any.
   COMMONLY FILLED BY

   • bank account balances from the bank feed
   • treasury management system
   • accounting system cash accounts
2. ar_pipeline

   REQUIREDREADrequest

   Expected inflows from open invoices and recurring revenue.

   DATA SHAPE

   Per-invoice or per-contract expected receipt with date estimate, amount, and confidence per customer payment behavior.
   COMMONLY FILLED BY

   • AR module of the accounting system
   • subscription billing system for recurring revenue
   • data from E20 AR follow-up pattern if live
3. ap_pipeline

   REQUIREDREADrequest

   Expected outflows from open bills, recurring commitments, scheduled payments.

   DATA SHAPE

   Per-bill or per-commitment expected payment with date, amount, payment terms.
   COMMONLY FILLED BY

   • AP module of the accounting system
   • payroll schedule from HR/payroll system
   • recurring vendor commitments tracked in a structured list
4. sales_pipeline_source

   REQUIREDREADrequest

   Future revenue not yet billed: deals in pipeline with expected close and bill timing.

   DATA SHAPE

   Per-deal expected revenue with close-date estimate, probability, billing terms.
   COMMONLY FILLED BY

   • CRM pipeline with deal stages and amounts
   • sales forecasting tool
   • structured forecast maintained by RevOps
5. scenario_inputs

   RECOMMENDEDREADcorpus

   Variables the finance team wants to model: alternative pipeline conversion rates, delayed receipts, accelerated hiring.

   DATA SHAPE

   Per-scenario assumption set with deltas from base case.
   IF MISSING

   Pattern produces single-line forecast without scenarios. Useful but less valuable for risk decisions.
   COMMONLY FILLED BY

   • scenario definitions maintained by the controller
   • small admin UI for scenario authoring
   • monthly review where scenarios get refreshed
6. forecast_destination

   REQUIREDWRITEevent

   Where the forecast lives for the team to consult: dashboard, weekly report, finance team workspace.

   DATA SHAPE

   Forecast with line-of-business detail, scenarios, key risks highlighted, recent changes from prior view.
   COMMONLY FILLED BY

   • dashboard accessible to finance and executive team
   • weekly cash flow report distributed to leadership
   • embedded view in the controller's working tools
7. alert_route

   REQUIREDWRITEevent

   Where material changes to the forecast get pushed to the CFO or controller proactively.

   DATA SHAPE

   Alert with the change, the cause, the implications, suggested actions.
   COMMONLY FILLED BY

   • chat alert to the CFO and controller
   • email digest of material movements
   • escalation when forecast crosses thresholds (e.g. cash floor)