--- name: cash-flow-snapshot-1e5584378c58 description: > Reads AR/AP, historical cash timing, and known fixed costs from the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) or from PayPal, Square, or Stripe — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live. compatibility: "Requires one or more of: a ledger MCP (MYOB, NetSuite, QuickBooks, Xero, Zoho Books), PayPal MCP, Shopify MCP, Square MCP, Stripe MCP, file upload (CSV fallback). Output uses xlsx skill." allowed-tools: Read, WebFetch --- # Cash Flow Snapshot Produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a two-part output: a concise chat summary and a downloadable XLSX workbook. **Quick start** > "Will I make payroll next month?" Claude pulls the current bank balance, AR/AP, and fixed costs from connected sources, calculates expected inflows and outflows across 30, 60, and 90-day windows, applies confidence bands from each customer's payment variance, and flags specific risks by name. --- ## Workflow ### Step 1 — Identify available data sources Check which connectors are live. Pull from every one that is, in one batch: 1. The ledger — MYOB, NetSuite, QuickBooks, Xero, or Zoho Books, whichever is connected — for AR aging, AP, fixed costs, and the cash balance. Ledgers are peers (`../../shared/connector-neutrality.md`); if two are connected, ask which is the source of record and take totals from that one only 2. PayPal — transaction history and settlement timing 3. Square — sales and payout history 4. Stripe — charge and payout history 5. Shopify — orders (`list-orders`) as the inflow, plus payout timing. Shopify on its own is enough to run: for a commerce business it is often the largest inflow. The payout read may fail because the connector's scopes exclude Shopify Payments — then ask the owner for their payout schedule and model from that; never infer a lag (`reference/v2_sources.md`) 6. CSV upload — when no connector is connected If no connector is live and no file is attached, ask the user to either connect a source or upload a CSV (income/expense tabular data, any reasonable format). Note which sources were used in the output — this affects confidence band width. **Always establish the starting cash balance** — "will I make payroll" is a question about the balance, not the net. Pull it in Step 2, or ask: "What's in the business account right now, and as of what date?" **Never assume one.** If nobody knows, head the output "no opening balance — net change only" and drop cash-on-hand from the risk flags. ### Step 2 — Pull the data **From the ledger:** - Balance sheet: bank and cash balances with the as-of date — the opening balance (MYOB holds none; see `reference/v2_sources.md`) - AR aging report: customer name, invoice amount, invoice date, due date, days outstanding - AP: vendor name, amount due, due date - Recurring fixed costs: rent, payroll, subscriptions (look for recurring transactions) **From Gusto, when connected:** - The next payroll run's date and expected amount, and the regular pay-schedule cadence — the real numbers for the biggest fixed cost, instead of inferring payroll from recurring transactions. When Gusto and the ledger disagree on payroll, trust Gusto for timing and amount and say so in the output **From PayPal / Stripe / Square:** - Settlement history: transaction date, amount, settlement date - Use settlement lag (transaction date → payout date) to compute each source's average and variance payment delay **From CSV upload:** - Parse as income/expense tabular data - Required columns (flexible naming): date, amount, type (income or expense), description - If columns are ambiguous, show the header row and ask the user to confirm mapping ### Step 3 — Compute historical payment timing For each AR customer (or income source from CSV), calculate: - **Mean payment lag** — average days from invoice/transaction date to receipt - **Payment variance** — standard deviation of payment lag across last 6–12 payments - Use variance to set confidence band width (see Step 4) If fewer than 3 payments exist for a customer, use the population mean as the point estimate and apply a ±30% variance band as the default. When running on CSV data with sufficient history (≥3 payments per source), compute the band from the actual payment variance — do not assume ±30%. ### Step 4 — Build the 30/60/90-day forecast Produce three time windows: 0–30 days, 31–60 days, 61–90 days. For each window, compute: | Line | Method | |---|---| | Expected inflows | AR due in window, adjusted for mean payment lag | | Expected outflows | AP due in window + fixed costs falling in window | | Net cash position | Inflows − Outflows | | Confidence band | ± weighted average payment variance as a % of expected inflows | Confidence band formula: ``` band_pct = weighted_avg_stddev_days / avg_payment_lag_days low = net_cash × (1 − band_pct) high = net_cash × (1 + band_pct) ``` Round band_pct to one decimal place. Cap at ±50% — higher variance means the data is too thin to model; flag it instead (see Step 5). ### Step 5 — Flag named risks Scan for conditions that push the low-band estimate negative or create a liquidity crunch. For each risk found, produce a one-line flag: - **Late-payer risk:** "Customer X historically pays 18 days late; that shifts their USD 8,400 invoice out of the 30-day window into day 48." - **Payroll crunch:** "Payroll (USD 22,000) hits April 15. Opening balance USD 31,000 on April 1, plus inflows, minus outflows, puts low-band cash on hand April 14 at USD 19,200. Shortfall risk: USD 2,800." Needs a sourced balance. - **Thin data warning:** "Only 2 payments on record for Customer Y — confidence band set to default ±30%." - **No-connector warning:** "Running on CSV data only — no real-time AP or recurring cost data. Confidence bands are wider than normal." Limit to the top 5 risks by severity (largest dollar impact first). ### Step 6 — Deliver outputs **Chat summary** (always). Use a markdown table for the forecast, not a fenced code block — the chat surface renders markdown tables; a fenced block shows up as raw monospace text. Shape: - Title line: Cash Flow Snapshot — - Source(s): - Opening balance: AUD X,XXX as of (or: none on file — net change only) Then the forecast as a markdown table, amounts carrying the business's currency code (`../../shared/currency-and-locale.md`), never a bare symbol: | Window | Expected | Low | High | |---|---|---|---| | 30-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX | | 60-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX | | 90-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX | Then risks as a short bulleted list under "⚠ Risks flagged: ". **XLSX workbook** (always): read `xlsx/SKILL.md` first, then produce three sheets: 1. **Summary** — the 30/60/90 forecast table with confidence bands. Beneath each window row, expand inline sub-rows showing the individual transactions that make up its inflows (green) and outflows (red). This makes the estimates auditable without leaving the Summary sheet. 2. **Detail** — all transactions grouped by window, sorted by date within each group. Include a running net column (cumulative inflows minus outflows within the window) and a subtotal row at the bottom of each window showing total inflows, total outflows, and net. Grey out past transactions in a separate section at the bottom for reference. Ensure all three windows have rows even if one is empty — show a "No transactions in this window" placeholder row. 3. **Risks** — the flagged risks with dollar impact and affected window. Save as `cash-flow-snapshot-[YYYY-MM-DD].xlsx`. **The forecast page** (always, alongside the chat summary — never instead of it), delivered per the owner's stored output preference — never default to a markdown file. Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`): - **Visual artifact (the default):** render the full forecast as an HTML page in the house style. The 30/60/90-day nets are stat tiles with the confidence range as each tile's context line; the transaction detail is a table with right-aligned tabular-nums amounts; each risk flag carries a status pill — critical for a projected shortfall, warn for late-payer and thin-data flags; sources and opening balance sit in a small header panel. - **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why. The XLSX still ships alongside. - **Best for skill:** use the visual artifact — a forecast is read at a glance and re-run often. --- ## After the run One line on what just happened: the forecast is built and the risks are named. Then offer the single most relevant next step, plus at most two others nearby: - If a payroll crunch was flagged: "can I make payroll" runs `/plan-payroll`. - "Who owes me money?" runs `invoice-chase` to pull collections forward. - "Close the month" runs `/close-month` so next forecast runs on clean books. Max three offers, and never repeat an offer the owner declined this session. ## Approval gates This skill is read-only — no approval gate before generating the forecast. Remind the user after delivery: > "This forecast is based on [sources listed]. It is not a substitute for > accounting advice — verify with your bookkeeper before making financing decisions." --- ## More sources, and a schedule Read `reference/v2_sources.md` for the full mapping: - **Shopify** — payments inflow timing, which is often the largest single inflow for a commerce business and settles on a delay worth modeling - **NetSuite** — a ledger of record, common at the larger end of the segment: AR, AP, fixed costs, and the cash balance via reports and SuiteQL - **Xero** — a ledger of record: aged receivables, bills, bank balances, and the organisation's currency and financial year - **Ramp** — card spend that hasn't hit the books yet, which is the most common reason a forecast is quietly optimistic - **Ramp balances** — real business and treasury account balances with history. When the owner banks with Ramp this is a sourced opening balance rather than a number they had to remember - **MYOB** — AR and AP legs for MYOB shops. Read-only, and it holds **no bank or cash balances at all** — never source an opening balance from it Nothing about the forecast logic changes. These are additional legs into the same model. ### Running on a schedule This skill is schedulable. The monthly preset is a cash heads-up before the month turns. Offer it once, after a forecast the owner found useful: ``` Want this monthly, a few days before month end? That's when it's most useful, and it's the same forecast you just got. ``` Scheduling is a property of this skill. There is no separate command for it. **QuickBooks summary fields lie.** Read `../../shared/quickbooks-report-traps.md` before quoting any total from a QuickBooks summary object: the AP aging summary nets vendor credits into its buckets and can show a negative overdue figure, and the P&L summary can report expenses as zero against real rows. Total the rows, or use the detail call. ## Reference files | File | Load when | |---|---| | `reference/gotchas.md` | When a connector returns unexpected data or variance is extreme | | `reference/examples/worked-example.md` | When modeling the output format for a new data shape | ## Using a tool that isn't listed The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates. --- Source attribution: anthropics Original project: https://github.com/anthropics/knowledge-work-plugins/blob/c75fda00ff0e41c8ee331ae312c8a07f1967653b/small-business/skills/cash-flow-snapshot/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Syntax-file, code seperations,code vault integeted with css definition. Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [ pre-requisites, statements, recorded-cams , cams-data , data, input() ] # Dave AI resource metadata Creator / publisher: anthropics Original project: https://github.com/anthropics/knowledge-work-plugins/blob/c75fda00ff0e41c8ee331ae312c8a07f1967653b/small-business/skills/cash-flow-snapshot/SKILL.md Attribution basis: Source repository record Fields of work: Finance & Accounting, Sales Roles: Accountant, Business Development, CFO / FP&A, Financial Analyst, Sales Operations Specialties: API, Excel Tools: Csv Upload, PayPal, QuickBooks, Square, Stripe Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 9ee199842d886af2ae2d2bd1d9d0c5c60915eddbf482afc10981d2c24b80b5cb