--- name: month-end-prep-b85d71e74a74 description: > Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month." allowed-tools: Read, WebFetch --- # Month End Prep ## Quick start Connect your bookkeeping ledger and at least one payment processor, then say "let's close the month." Claude walks you through each step of the checklist, pausing for your input at each gate before moving forward. Any connected ledger runs the close. Each has a reference file for its reads and its "needs attention" signal: [reference/quickbooks-reconcile.md](reference/quickbooks-reconcile.md), [reference/xero-reconcile.md](reference/xero-reconcile.md), [reference/zoho-books-reconcile.md](reference/zoho-books-reconcile.md); NetSuite and MYOB are in [reference/v2_sources.md](reference/v2_sources.md). Ledgers are peers (`../../shared/connector-neutrality.md`): if two are connected, ask which holds the books being closed, read the other only for what it uniquely holds, and never sum a figure across both. Every amount is in the business's currency (`../../shared/currency-and-locale.md`). The thresholds below (0.50, 0.01, 25) are in that currency. If a connector is missing, Claude falls back to asking for a CSV export — it won't silently skip a step. ## Workflow Work through these steps in order. Each step has a completion state; don't advance until the current step is settled. ### Step 1 — Agree on the target month Ask the user which month to close. Default to the prior calendar month if they don't specify. Confirm before pulling any data. ### Step 2 — Pull the ledger's P&L and register Fetch: - Profit & Loss report for the target month (revenue, COGS, gross margin, operating expenses, net income) - The register, as the ledger's reference file defines it. QuickBooks: the transaction list, every income and expense line. Xero: bills, invoices, and the bank-transaction queue, with that scope stated in the packet. Zoho Books: invoices, expenses, and purchase orders, with the P&L itself coming from an export because the connector has no report endpoint. Flag immediately, using the ledger's own "needs attention" signal: - **QuickBooks** — uncategorized lines ("Uncategorized," blank, "Ask My Accountant") and its Needs Review flag - **Xero** — bank lines still unreconciled at month end - **Zoho Books** — the `uncategorized_transactions` count on each bank account Present the count ("14 transactions need attention") and list them for the user to resolve in the ledger before proceeding. Don't advance with open items unless the user explicitly says "skip for now." See [reference/quickbooks-reconcile.md](reference/quickbooks-reconcile.md), [reference/xero-reconcile.md](reference/xero-reconcile.md), and [reference/zoho-books-reconcile.md](reference/zoho-books-reconcile.md) for field mappings and API notes. ### Step 3 — Pull payment processor settlements Fetch settlement reports from PayPal, Square, Stripe, or Shopify — whichever are connected — for the same calendar month. **Check the bank feed first.** When a processor pays out through a bank feed, the payout is already a ledger line and the question is whether it has been matched. Find unreconciled bank lines naming a processor and list them per processor as the action items before doing any CSV match. This applies to any ledger that carries a bank feed with a reconciled state — the usual case in Xero, and QuickBooks bank-feed lines when the connector exposes them. MYOB holds no bank side, and Zoho Books exposes balances but no bank-transaction list, so a MYOB or Zoho Books close goes straight to the CSV match below. **Compare net to net, or every line looks broken.** The ledger records the net bank deposit; the processor's report shows the gross sale. Match those directly and every row shows a discrepancy the exact size of the fee. Use the processor's **net payout** (gross minus fees) — see [reference/gotchas.md](reference/gotchas.md). Match each settlement deposit against the ledger's bank deposit line: - **Match** — amount and date agree within 2 days → mark as reconciled - **Difference < 0.50** — rounding/fee; note but don't flag - **Difference ≥ 0.50** — flag with the delta amount - **Settlement exists, no ledger deposit** — flag as "missing in the ledger" - **Ledger deposit exists, no settlement** — flag as "deposit not in processor data" See [reference/paypal-settlements.md](reference/paypal-settlements.md) for settlement report field mappings (PayPal, Square, Stripe) and [reference/v2_sources.md](reference/v2_sources.md) for Shopify. ### Step 4 — Detect suspicious duplicates Scan the register for likely duplicate charges or deposits. Flag a transaction as a suspicious duplicate when **all three** match: - Same amount (within 0.01) - Same vendor or customer name - Posted within 5 calendar days of each other Scan what the ledger actually holds. In QuickBooks that is the transaction list, with split rows grouped by transaction id first. In Xero a bill keyed twice makes two unpaid documents and no bank line, so scan bills and invoices (same contact, same total, within 5 days, both unpaid or one paid inside the window) rather than bank lines — the mapping is in [reference/xero-reconcile.md](reference/xero-reconcile.md). Zoho Books is the same shape: scan invoices and expenses as documents ([reference/zoho-books-reconcile.md](reference/zoho-books-reconcile.md)). Present flagged pairs to the user. They decide whether each is legitimate (e.g., a recurring weekly subscription) or a real duplicate to void. **The 5-day window is a filter, not a guarantee.** It catches the same charge keyed twice without drowning the owner in recurring weekly bills, but a real double payment three weeks apart slips through. Say what was scanned ("repeats within 5 days"), and widen the window for a vendor they're suspicious about rather than calling it clean. See [reference/gotchas.md](reference/gotchas.md) for common false-positive patterns and how to distinguish them. ### Step 5 — Receipts check Check the ledger first: an attachment on the transaction counts as a receipt on file (`AttachmentCount` in QuickBooks; `has_attachments` in Xero, returned only with `include_line_items=true`; `has_attachment` on Zoho Books invoices and expenses). Then, if the Desktop connector is available, scan the receipts folder (ask the user for the path; default `~/Documents/Receipts`) for the target month. For each expense transaction above 25 with no attached document: - Check for a matching receipt file (match by amount ± 0.50 and date within 3 days) - **Matched** → note as "receipt on file" - **Not matched** → flag as "missing receipt" List missing receipts. The user can supply the file or mark as "receipt not required" (e.g., a recurring auto-pay with no receipt). If Desktop connector is not available, ask the user to confirm which expenses they have receipts for — don't silently skip this step. ### Step 5a — Payroll cross-check Runs only when a payroll connector is connected (Gusto or QuickBooks Payroll — peers, whichever is connected). Otherwise skip it and say the packet carries no payroll column. Pull what was actually paid in the month, totals only: - **Gusto** — `list_payrolls` with `include=totals`, keeping the payrolls whose `check_date` falls in the target month. From each `totals`: `gross_pay`, `employer_taxes`, `employee_taxes`, `net_pay`. Then `list_contractor_payments` for the same date range with `group_by_date=true`, taking `total.wages` and `total.reimbursements`. Contractor totals cover US contractors only — say so in the packet footnote. - **QuickBooks Payroll** — `qbo_payroll_get_company_last_payroll_run` for the most recent run; earlier runs in the month come from the payroll summary export. (Confirm before the first close.) Cross-check against the ledger: net pay plus employer taxes plus contractor wages should appear as the month's payroll expense lines. A difference above 0.50 is a reconciliation item — usually a run posted to the wrong month, or a payroll journal not yet posted. **Totals only, never people.** The packet carries the month's totals and the count of runs. No employee name, rate, or per-person amount leaves the connector — that is payroll data, and `payroll-prep` is where it belongs. See [reference/v2_sources.md](reference/v2_sources.md) for the field mapping. ### Step 6 — Owner sign-off gate Present a summary before going further: ``` Needs attention (uncategorized or unreconciled): X of X resolved Settlement discrepancies: X flagged, X resolved Suspicious duplicates: X flagged, X cleared Missing receipts: X outstanding Payroll cross-check: matched / X difference / no payroll connector ``` Ask: "Ready to write the P&L summary and export the close packet?" **Do not proceed to Steps 7–8 without explicit confirmation.** ### Step 7 — Write the P&L narrative Write a plain-English summary of the month — the kind an owner would share with their spouse or accountant, not a CFO memo. Aim for 150–250 words. Structure: 1. **Headline** — one sentence: "March came in at AUD 12,400 net, up 6% from February." Currency code, never a bare symbol. 2. **Revenue** — what drove the number; name products, services, or customers if the data shows concentration. 3. **Gross margin** — whether it held, rose, or compressed, and the main reason why. 4. **Key expenses** — any line that moved more than 10% MoM or is outside the normal range; one sentence each. 5. **Bottom line** — net income vs. prior month; ask if they have a target to compare. 6. **Watch list** — 1–3 things to monitor next month. Avoid jargon; define anything that isn't plain English ("MoM" = month over month). See [reference/examples/pl-narrative.md](reference/examples/pl-narrative.md) for a worked example. ### Step 8 — Export the close packet Produce two files: **`close-packet-[YYYY-MM].xlsx`** — three sheets, four when a payroll connector is connected: - `P&L` — the ledger's P&L data, formatted - `Reconciliation` — matched and flagged transactions side by side - `Action Items` — any outstanding flags (uncategorized, missing receipts, etc.) - `Payroll` — the Step 5a totals beside the ledger's payroll expense, with the delta **`close-packet-[YYYY-MM]-summary.pdf`** — one page: - Month and business name at the top - Key figures (revenue, gross margin %, net income) - The P&L narrative from Step 7 - Count of open action items, if any Save both to the Desktop (or a path the user specifies). Confirm the file locations. See [reference/close-packet-format.md](reference/close-packet-format.md) for column specs and PDF layout details. Also deliver the close as a page, 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 close as an HTML page in the house style — additive to the chat summary and the files, never a replacement. Revenue, gross margin percent, and net income are stat tiles with their month-over-month change as context lines; the reconciliation results are a table with tabular-nums amounts; each flag carries a status pill — good for reconciled, warn for missing receipts and uncategorized items, critical for unresolved settlement gaps and duplicates; the P&L narrative and the open-items checklist each get a 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 packet xlsx and PDF keep their formats. - **Best for skill:** use the visual artifact — the close is reviewed on screen before the packet goes to the accountant. ### Step 9 — After the close Say in one line what closed and what is still open. Then offer the single most relevant next step, plus at most two others nearby: - "Cash forecast" runs `cash-flow-snapshot` off the freshly closed numbers. - "Build me a report" runs `report-builder` to publish and distribute the packet. - "Taxes" runs `/tax-prep` when quarter or year end is near — offered only when the business context says Country is US, since that chain's tax math is US federal. Max three offers. Never repeat an offer the owner declined this session. ## Approval gates - **Never run reconciliation on a month that has been filed.** Confirm the books are still open before pulling data. - **Never void or modify a ledger transaction directly.** Surface flags; the owner makes changes in the ledger. - **Always pause at Step 6** before producing outputs. Unresolved flags must be acknowledged or explicitly skipped. - **Never reproduce per-person pay, SSNs, or bank numbers** in the close package beyond the journal totals (`../../shared/personal-data.md`). ## Graceful degradation | Missing connector | Fallback | |---|---| | QuickBooks | Ask for **two separate exports** — the Profit & Loss report, and the Transaction Detail by Account report. One file will not carry both; asking for "a QB export" gets you one of them and a second round trip | | Xero | Ask for **two exports** — the Profit and Loss report, and the Account Transactions report with all accounts selected — plus the unreconciled line count from the bank reconciliation screen, which no export carries | | NetSuite or MYOB | Ask for the P&L and the transaction detail for the month as two exports; MYOB holds no bank balances, so the bank side comes from a statement | | Zoho Books | Even when connected, ask for the **Profit and Loss** export (no report endpoint) and a **bank statement** (no bank-transaction feed); the register and the uncategorised count come from the connector. Not connected: add the Account Transactions export | | Payment processor | Ask for a settlement CSV from the processor's website. It must include the fee column, not just the gross amount, or the net-to-net match in Step 3 can't be done | | Payment processor connected but returns zero payouts for the period | Treat as a data gap, not a clean zero. Say the connector returned nothing for the month, ask for the same settlement CSV (fee column included), and name the gap in the report rather than reconciling against an empty set | | Payroll connector (Gusto, QuickBooks Payroll) | Skip Step 5a. The packet has no Payroll sheet and the summary says "no payroll connector"; the ledger's payroll expense lines still appear in the P&L unchecked | | Desktop (receipts) | Ask the user to confirm receipt status for each flagged expense | ## More sources Read `reference/v2_sources.md` for the mapping: - **Shopify** — settlement reconciliation as a first-class leg. Orders, payouts, and fees each land differently, and it's a common source of unexplained gaps - **NetSuite** — a ledger of record, common at the larger end of the segment; reports and SuiteQL supply the P&L and register - **Xero** — a ledger of record with its own register shape (bills, invoices, bank queue) and its own attention signal (unreconciled bank lines); mapped in `reference/xero-reconcile.md` - **MYOB** — P&L and AR/AP balances; no bank balances, so the bank side of the close comes from a statement - **Zoho Books** — a ledger of record with a document register (invoices, expenses, purchase orders), bank balances with an uncategorised count as the attention signal, and no report or bank-feed endpoints, so the P&L and the payout match come from exports; mapped in `reference/zoho-books-reconcile.md` - **Ramp, Expensify** — card and expense detail, which closes the gap between what was spent and what was coded - **Gusto, QuickBooks Payroll** — payroll actually run: gross pay, employer taxes, net pay, and contractor payments as month totals, so Step 5a reconciles the ledger's payroll expense against what was paid rather than what was planned. Totals only; no per-person data enters the packet Same close sequence, same packet. More sources reconciled. **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 - [reference/quickbooks-reconcile.md](reference/quickbooks-reconcile.md) — QB field mappings, API pagination, common data issues - [reference/xero-reconcile.md](reference/xero-reconcile.md) — Xero register definition, unreconciled-line signal, document-level duplicate scan, attachments - [reference/zoho-books-reconcile.md](reference/zoho-books-reconcile.md) — Zoho Books register definition, uncategorised-count signal, what needs an export - [reference/paypal-settlements.md](reference/paypal-settlements.md) — settlement report structure for PayPal, Square, and Stripe - [reference/close-packet-format.md](reference/close-packet-format.md) — xlsx column specs, PDF layout, file naming convention - [reference/gotchas.md](reference/gotchas.md) — duplicate false positives, split transactions, partial-month edge cases - [reference/examples/pl-narrative.md](reference/examples/pl-narrative.md) — worked P&L narrative example ## 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/month-end-prep/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/month-end-prep/SKILL.md Attribution basis: Source repository record Fields of work: Finance & Accounting, Operations, Sales Roles: Accountant, Business Development, Customer Success Manager, Financial Analyst, Operations Manager Specialties: API, Backend Tools: PayPal, QuickBooks, Square, Stripe Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 2fd4475f46f2466f81c36f96edc5ce63092ce153cc731543d6029dbd0ffcce4e