PromptSharp › Daily briefs › Finance › October 15, 2026

Finance prompt of the day

October 15, 2026 · for Investment banking, sales & trading, equity research, FP&A. One sharp, copy-paste prompt — free, every weekday.

You are a controller running a month-end flux review for [ENTITY] on the trial balance or account-level figures I paste below (this month, last month, same month last year). Produce:
1. A FLUX TABLE by account: current, prior month, prior year, change in currency and percent, computed only from my figures.
2. FLAGS: every account that crosses the threshold I set (default: 10% and [AMOUNT]) plus any account that changed sign, went to zero, or appeared for the first time.
3. For each flag: the most likely explanation category (volume, timing of an accrual, reclassification, one-off, error) and the single document or report that would confirm it.
4. PAIRS THAT SHOULD MOVE TOGETHER: accounts whose movements usually offset (for example accruals and the related expense) where one moved and the other did not.
5. A draft explanation line for each flag in the style a reviewer expects, clearly marked DRAFT where the cause is not confirmed.
Here is my data:
[PASTE: account-level balances for the three periods, the threshold, any known one-offs]

Rules: Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it. Mark every claim I should verify externally before relying on it. Never use, infer, or request material non-public information (MNPI) or client-confidential data.

What changed for Finance

How to run “Month-end flux analysis: which moves need an explanation”, step by step

The situation this prompt is built for: Before the books close you need to find which account movements are unusual enough to explain, and draft the explanations reviewers will ask for. Below is exactly what to feed it and what comes back — no model-specific tricks, it runs the same in any chat AI.

What each placeholder does

Demo profile for the example fills: an equity research associate on a mid-cap sector coverage team, working in Excel, a chat AI model, and your firm's data terminal. Swap in your own context — or save it once at /profile and copied prompts arrive pre-filled.

• [ENTITY] — this is the input the whole output quality hangs on. Demo fill: your own entity — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.
• [AMOUNT] — this is the input the whole output quality hangs on. Demo fill: your own amount — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.
• [PASTE: account-level balances for the three periods, the threshold, any known one-offs] — this is the input the whole output quality hangs on. Each part narrows the answer: paste: account-level balances for the three periods; the threshold; any known one-offs. Demo fill: your own paste: account-level balances for the three periods, the threshold, any known one-offs — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.

What the model hands back

The prompt forces a fixed deliverable shape, so you get a document, not a ramble:

1. A FLUX TABLE by account: current, prior month, prior year, change in currency and percent, computed only from my figures.
2. FLAGS: every account that crosses the threshold I set (default: 10% and [AMOUNT]) plus any account that changed sign, went to zero, or appeared for the first time.
3. For each flag: the most likely explanation category (volume, timing of an accrual, reclassification, one-off, error) and the single document or report that would confirm it.
4. PAIRS THAT SHOULD MOVE TOGETHER: accounts whose movements usually offset (for example accruals and the related expense) where one moved and the other did not.
5. A draft explanation line for each flag in the style a reviewer expects, clearly marked DRAFT where the cause is not confirmed.

Why this structure works

Reviewers ask about the same things every month: big moves, sign flips and pairs that stopped moving together. Screening for exactly those and drafting explanations marked as unconfirmed saves the back-and-forth without pretending a guess is a finding.

On Pro, the account groupings, thresholds and explanation style follow your chart of accounts and close calendar from your profile.

When to use it — and when not to

Reach for it when

• Before the books close you need to find which account movements are unusual enough to explain, and draft the explanations reviewers will ask for.
• You can actually supply the inputs it asks for ([ENTITY] and 2 more) — this prompt is an amplifier for real context, not a substitute for it.
• You need the output in a shape you can forward as-is — the fixed structure above is the point.

Skip it when

• You don’t yet have the source material — the prompt is built to refuse to fake it. Its own guardrail: “Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it.” With nothing to work from, you’ll get a list of “not provided” flags, which is honest but not useful. Collect the inputs first.
• The task is genuinely one sentence long — a structured prompt earns its overhead when the output has parts. For quick one-off questions, just ask.

Adapting today’s prompt for adjacent roles

“Month-end flux analysis: which moves need an explanation” sits in the Financial Analysis & Modeling lane of the finance pool. If your seat is one desk over, these are the same craft-move rebuilt for the neighbouring workflow — pulled from the same curated pool, each free in full at its permalink:

You are a defense advisor stress-testing a company through an ACTIVIST'S EYES. Company: [DESCRIBE: business, segments, balance sheet, governance, recent performance I…

You are a trader assessing SQUEEZE / CROWDING RISK in [NAME]. Using only data I paste (short interest, days-to-cover, borrow rate/availability, float, options…

You are a buy-side analyst building a THESIS-MONITORING TRACKER for a position: [NAME + my thesis in 2-3 sentences + the numbers I'm underwriting]. Produce: 1. A KPI…

Common failure modes (and the fixes)

• Failure: letting the model drift past the prompt’s own guardrail — “Do not invent, estimate, or extrapolate any figure — if a number is not in what I give you, write "not provided" and flag it.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Mark every claim I should verify externally before relying on it.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Never use, infer, or request material non-public information (MNPI) or client-confidential data.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: filling [ENTITY] with a vague summary. The output can only be as specific as this input — generic context in, generic deliverable out. Fix: paste raw specifics (real names, real numbers, real constraints), then trim the model’s output, not your input.
• Failure: accepting the first pass. Fix: reply with one line — “now cut everything that is generic to any company and keep only what is specific to mine” — the cheapest quality doubling available.

Where AI is landing for investment banking right now

Context for today’s prompt, from the same screened sources the daily brief reads. Our read, with sources linked — the pattern across items like these is consistent: the professionals getting leverage from AI are the ones feeding it real working context, which is exactly the muscle today’s prompt trains.

• [No Priors] Revolutionizing Cybersecurity and AI-Driven Science with OpenAI President Greg Brockman (podcast) — Technology has always been the fundamental driver of improvement for human quality of life. And with the recent rollout of advanced frontier models, like OpenAI’s GPT-6, humanity…
• [a16z Podcast] When AI Agents Start Spending Your Money | Alex Rampell & Terry Angelos (podcast) — a16z General Partner Alex Rampell sits down with VGS Executive Board Member, Terry Angelos, to unpack what happens to payments when AI agents go from recommending what to buy to…

Quick answers

Is “Month-end flux analysis: which moves need an explanation” free to use?

Yes — every weekday issue of the PromptSharp Finance publishes one full pool prompt free on the web, and it stays free in the archive. Pro is the daily full prompt set, personalization, and MCP delivery — not a paywall on this page.

Which AI model does this prompt work with?

Any of them. Every PromptSharp prompt is model-agnostic plain text — ChatGPT, Claude, Gemini, Copilot, or a local model. No plugins, no custom GPTs; paste and run.

How is the finance prompt of the day chosen?

Deterministic rotation over the curated finance pool — currently 80 prompts across 5 sections — the same single source the paid brief reads. Same date, same prompt: the archive never silently changes under you.

What goes in the [BRACKETED] placeholders?

Your context — the walkthrough above covers each one. The short rule: the more concrete the fill (real names, numbers, constraints), the sharper the output. Save your details once at /profile and web copies arrive pre-filled.

How do I get this in my inbox instead?

The capture form above. The PromptSharp Finance email edition lands most weekday mornings, plus a Sunday roundup; the web issue stays free here either way.

More daily AI prompt briefs

The same free weekday format, tuned to other crafts:

• PromptSharp CPG Brief — for Brand managers, category managers, insights & shopper teams
• PromptSharp Marketing Brief — for Brand and growth marketers, agency strategists, content leads
• PromptSharp Sales Brief — for AEs, SDRs, sales leaders, RevOps
• PromptSharp Consulting Brief — for Management consultants, corporate strategy, biz-ops
• PromptSharp Product Brief — for PMs, product ops, founders wearing the PM hat
• PromptSharp Dev Brief — for Software engineers, tech leads, engineering managers
• PromptSharp Vibe Coding Brief — for Founders, PMs, designers, analysts — anyone building real software with AI without an engineering background
• PromptSharp C-suite Brief — for CEOs, CFOs, CMOs, CTOs, COOs and their chiefs of staff
• PromptSharp Law Brief — for Solo & small-firm attorneys, litigation & transactional associates, in-house counsel
• PromptSharp Personal Finance Brief — for Anyone running their own money — budgets, investing, taxes, and the rent-vs-buy / home-buying decisions that dwarf every other line item
• PromptSharp Career Brief — for Job seekers, career changers, anyone negotiating an offer
• PromptSharp Focus Brief — for Anyone who wants external structure for deep work — ADHD-friendly by design
• PromptSharp Learning Brief — for Self-directed learners — languages, skills, certifications, exam prep
• PromptSharp Health & Fitness Brief — for Anyone training, eating better, or building durable habits
• PromptSharp Travel Brief — for Trip planners — itineraries, deals, points, family logistics
• PromptSharp Students — for College students (undergrad + grad) — study, research, essays with integrity, exam prep, applications
• PromptSharp Trading — for Self-directed retail traders and active investors — risk and position-sizing thinking, regime awareness, journal review, bias-checking, earnings prep. Your own account, your own process.

← 2026-10-14 · All Finance issues