Skip to content
Month-End Close

Auto-draft month-end flux explanations with Numeric and Claude

View source

What the source describes

Numeric documents an MCP use case where Claude loops through every pending flux task assigned to you, pulls six months of transaction lines per account, groups them by dimensions such as vendor, customer, department, class and location, and drafts conclusion-first variance explanations. Each draft leads with the total variance and primary driver, followed by supporting bullets with dollar breakdowns. Claude drafts and can post the explanation, but does not submit the task; you review and submit.

Result or outcome

According to the source, the skill produces first-pass flux commentary ready for the preparer to review, adjust and submit, uses whatever history is available if six months is not, and can fan out sub-agents to work on accounts in parallel.

How to run it

  1. Connect the Numeric MCP to Claude, install the Numeric Toolkit, and confirm you are preparer on pending flux tasks with a saved flux report.
  2. Ask Claude to write your flux explanations; it pulls up to six months of transaction lines per account and groups them by available dimensions.
  3. If you are not using Numeric, run the prompt on this page against your variance table and transaction detail for accounts over your threshold.
  4. Review each conclusion-first draft, and add a flux template override in the task description if the grouping dimension is wrong, then rerun.
  5. Edit the explanations as needed and submit each flux task yourself, since the skill drafts and posts but never submits.

Try it yourself

Copyable prompt

Draft month-end flux explanations for [company name] for [month and year] compared with [prior month or same month last year]. Below is the account-level variance table and the transaction detail for each account over the variance threshold of [amount or percent]. For each account, write a conclusion-first explanation: total change, the main driver, and how concentrated it is, followed by two to four bullets breaking down the change by vendor, customer or department with dollar amounts. Flag any change that looks like a missing accrual, misposting, or one-time item that I should investigate before sign-off.

[paste variance table]
[paste transaction detail]

Replace the [bracketed] placeholders. Remove client names, account numbers, and personal data before pasting into any AI tool.

What to review

Check that each draft's total variance and dollar breakdowns tie to the flux report and the underlying transactions. Remove any speculation about headcount, one-time events or org changes the ledger does not support, and investigate possible missing accruals or misposts before sign-off. The skill appends rather than overwrites, so delete old explanations first to avoid duplicate commentary.

Related free download: Month-End Close Checklist for Small Business Bookkeepers (Printable checklist (PDF))

Source: Numeric (MCP use case documentation)

Not professional advice. This is general information, not accounting, tax, legal or financial advice. Check AI output yourself and consult a licensed professional for your situation. See our Terms of Use.

This entry summarizes a public source. Features, plans, and availability change, so confirm details with the vendor. Tool names are trademarks of their respective owners.

Related workflows

  • Month-End Close

    Draft Adjusting Journal Entries for Review with Claude

    Anthropic's prompt engineering overview says to start with three things: a clear definition of the success criteria for your use case, some way to test against those criteria, and a first draft prompt you want to improve. It points to Anthropic's prompting best practices for the techniques themselves, from clarity and examples to XML structuring, role prompting, thinking and prompt chaining. It also notes that not every failing result is best solved by prompt engineering. For adjusting entries, the success criteria are easy to write down: every entry balances, uses only accounts on the chart, and names its support.

    Claude

    Claude Docs (Prompt engineering overview)
  • Month-End Close

    Track period-close status with Sage Copilot Close Assistant in Sage Intacct

    Sage Intacct's help documentation explains that Close Assistant, part of Sage Intacct Close Automation, shows which applications are closed and which tasks need attention in the Sage Copilot panel. You open Copilot, select Run Close Assistant, pick the reporting period, and it lists tasks such as reviewing unposted bills and invoices, preparing AP and AR reconciliations, reviewing bank reconciliations, reviewing unposted journal entries and running variance analysis, with links to close each subledger and the general ledger.

    Sage Intacct, Sage Copilot +1

    Sage Intacct Help Center
  • Reconciliations

    Build reconciliation working papers from a bank statement and invoice folder with Claude

    A finance educator and former auditor, writing in the Tips & Insights on Finance & AI newsletter, describes dropping 100 invoices and a bank statement into Claude Cowork and running the reconciliation skill from Anthropic's Finance plugin. The post lays out six steps: install the plugin, create Bank_Statement and Invoices subfolders, create a Cowork project, call the skill, ask Claude to add a verification tab, and review only the exceptions. The author stresses that messy inputs still produce poor results.

    Claude Cowork, Anthropic Finance plugin +1

    Tips & Insights on Finance & AI (newsletter)
  • Receipts and Expenses

    Keep Each Client's Coding Rules in a Claude Project

    Anthropic's help center describes Projects as self-contained workspaces with their own chat histories and knowledge bases. Anything uploaded to a project's knowledge base is used across all chats in that project, and project instructions tell Claude how to behave and respond in every chat there. Projects are available on free accounts, which can create up to five. Context is not shared across chats within a project unless it is added to the project knowledge, and on paid plans Claude automatically enables RAG mode when project knowledge approaches the context window limit.

    Claude, Claude Projects

    Claude Help Center (What are projects?)