Skip to content

Flux analysis for monthly close

Identify P&L line items with month-over-month changes above a threshold and surface plausible explanations to investigate.

Workflow · Close & Reporting | Role · Accounting Manager | Intermediate | 5 min | Updated Apr 15, 2026
The prompt

Copy and customize

prompt.txt
You are a senior Accounting Manager producing the following deliverable: flux analysis for monthly close.

Context
- Workflow: Close & Reporting
- Inputs available: {paste the data here}
- Period: {month / quarter}
- Audience: {who reads this}

What to produce
1. The headline takeaway in one sentence.
2. The three things that materially moved the result, with quantified contribution.
3. The one risk or anomaly worth flagging.
4. A short forward-looking note: what to watch next period.

Guardrails
- Use only the numbers provided; do not invent values.
- Cite a row reference for every claim.
- Flag anything you cannot reconcile rather than smoothing it over.
Open in
We’ll copy the prompt and open the chat.
How to use

Run it in four steps

  1. Pull the trial balance for the close period and the prior period, with account-level descriptions so the flags are actionable.
  2. Paste both into {paste the data here}, set {month / quarter}, and state your materiality threshold.
  3. Run it to surface the accounts that moved beyond threshold.
  4. Treat every explanation it offers as a lead to verify in the GL, not a finding.
When to use

When to reach for this prompt

Run before the controller's close review meeting. Surfaces items the team needs to investigate before sign-off — it doesn't replace the tie-out work.

Example output

What you can expect back

Material flux items (>10% MoM or >$25K)

  1. Professional Services revenue +$120K (+42%)Investigate: one-time deliverables?
  2. Hosting -$38K (-18%)Confirm: AWS RI credit applied this month
  3. Bad debt expense +$22KReview: aging for recent write-offs
  4. Stock-based comp +$15K (+5%)Verify: HRIS for new equity grants
Limitations · Worth knowing

This prompt has real limitations you should understand.

Threshold-based flagging misses small accounts that are systematically drifting. Use it as a starting point, not a complete close checklist.

01

Threshold blindness

Threshold-based flagging misses accounts that drift 2% per month for a year. The prompt will not surface them — but those are exactly the items that turn into a material restatement two quarters later.

02

Reclassifications look like variances

A line item that moved from one GL account to another shows up as a 100% flux on both sides. The prompt will dutifully report both as items to investigate, and the close team will waste a morning chasing nothing.

03

First-time accounts are noisy

Any account that did not exist in the prior period flags as infinite percentage change. Suppress them at the prompt level or you will get a flux list dominated by new-but-immaterial line items.

Prerequisites

What your data needs to look like

  • Trial balance for the close period and the prior period
  • A standing materiality threshold (typically larger of 5% or $25K)
  • Account-level descriptions for the GL so flags are actionable
See it run on real data

See how FinanceOS handles this prompt on real financial data.

Book a 20-minute walkthrough. We’ll run this exact prompt against a sample dataset reconciled through FinanceOS, and show you what changes when the data underneath is right.

Book a walkthrough
The Hub

Join the FinanceOS Hub.

Subscribe to get new sessions, use cases, and AI workflows for finance teams — straight to your inbox, every Monday.

  • Weekly · ~4 min read
  • No spam, unsubscribe anytime
  • 2,400+ finance leaders