Copilot prompts for finance: 8 ready-to-copy examples

Eight Copilot Chat prompts for finance: invoice reminder, expense claims, budget variances and cash flow, from Beginner to Expert level.

By QDNA · Published on September 10, 2026 · Updated on September 10, 2026

In brief. Finance produces reminders, checks and analyses where a wrong figure is costly. These eight prompts range from the invoice reminder to the cash flow forecast, with two prompts per level of the course. They follow three rules: the source is a clean attached file, never a description; hypotheses are separated from facts in a section of their own; a human validates every figure before it leaves the department.

When to use it

Copilot Chat has a Python interpreter to analyse an attached file, run in an isolated environment without network access. It replaces neither your accounting tool nor your validation: cross-check at least one total by hand.

To adapt one of these prompts, open the composer and choose the "Finance" template in the list of job templates.

Beginner

1. Reminder for an unpaid invoice (Beginner)

BeginnerContext. An invoice has been overdue for twelve days with a loyal client and you want a firm but courteous reminder.

Write a reminder email for an unpaid invoice. Context: invoice [number] of [amount] euros, overdue by [number] days, loyal client. Expectations: 90 words, firm and courteous tone, reminder of the number and the amount, request for payment within eight days, one sentence offering a contact in case of dispute. Mention no penalty. Answer in English.

Expected result. A crisp reminder, with the exact number and amount, ready to send after proofreading.

Mistake to avoid. Letting Copilot threaten late payment penalties without having checked the contractual terms: the reminder becomes a risk.

Related lesson. Writing a good prompt: the four ingredients

2. Explain an accounting term to a manager (Beginner)

BeginnerContext. An operational manager asks what a term in the monthly reporting means.

Explain what [term, for instance: working capital requirement] is to an operational manager with no accounting training. 120 words at most, everyday vocabulary, one simple worked example taken from the life of a production team. End with the sentence "In practice, for you, this means that..." completed in one line.

Expected result. An explanation in everyday language with a concrete example, reusable in an email or a meeting.

Mistake to avoid. Asking "explain working capital" with no audience or length: the reply is an accounting lecture the manager will not read.

Intermediate

3. Check an expense claim against the attached policy (Intermediate)

IntermediateContext. The expense policy and an anonymised claim are attached; Copilot prepares the check, you validate.

From the two attached files only, expense_policy.pdf and expense_claim.xlsx: Step 1: list the non-compliant lines with the rule breached, citing the article of the policy. Step 2: calculate the amount to refuse and show the detail of the calculation. Step 3: write the explanatory email to the employee, 100 words, neutral tone. If a rule does not cover a case, write "to be decided" rather than ruling. Format: table line, rule, article, amount, then email.

Expected result. A check justified line by line, every refusal tied to an article, and an email ready after validation.

Mistake to avoid. Describing the expense policy instead of attaching it: Copilot applies generic rules that are not yours.

4. Tighten a budget summary with a precise follow-up (Intermediate)

IntermediateContext. The first summary is too long and too technical; you follow up saying what to keep and what to change.

Keep the structure and the first paragraph of your answer. Rewrite the rest in 120 words at most for the executive committee: each paragraph starts with the key figure, the three main variances are kept, technical explanations go in brackets. Delete any sentence that contains neither a figure nor a decision.

Expected result. A shorter summary that keeps the three variances and opens each paragraph with a figure.

Mistake to avoid. Following up with "it is too long": Copilot cuts at random and an important variance disappears.

Related lesson. Iterating: the first answer is a draft

Advanced

5. Budget variances with hypotheses separated from facts (Advanced)

AdvancedContext. The quarterly budget and actuals are attached as one clean sheet; the analysis goes through the Python interpreter.

Attached file budget_actual_Q3.xlsx: one sheet, row 1 = headers (Item, Budget in euros, Actual in euros), one row per item, no total row. Before calculating, describe your method in three lines. Step 1: calculate the variance per item in value and in percentage. Step 2: identify the three most significant variances in absolute value. Step 3: for each, formulate an explanatory hypothesis, marking it "hypothesis to be validated". State the number of rows taken into account. Format: table item, budget, actual, variance, percentage, then hypotheses separately.

Expected result. A verifiable variance table, with the hypotheses clearly separated from the figures.

Mistake to avoid. Letting Copilot mix facts and hypotheses in the same column: management reads a hypothesis as an established cause.

6. Review of a financial note with a grid (Advanced)

AdvancedContext. In a new conversation, you have a note evaluated before sending it to management.

You are a reviewer. Evaluate the note below against this grid, with a score from 0 to 2 and a one-sentence justification per criterion: 1) every figure is tied to a named file or table, 2) hypotheses are distinguished from facts, 3) the final recommendation says who, what, when, 4) no sentence exceeds 25 words, 5) the amounts are consistent between the text and the tables. End with the three priority corrections, phrased as rewriting instructions.
Note: [pasted text]

Expected result. A verdict per criterion and three concrete corrections; you apply, run again, and the score rises.

Mistake to avoid. Asking "is it good?": the reply is a compliment. A grid of criteria produces a useful judgement.

Expert

7. Three-scenario cash flow forecast (Expert)

ExpertContext. The trial balances of the last eight months are attached; you require scenarios, explicit hypotheses and an arithmetic check.

Act as a senior management controller. From the eight attached trial balance files only, proceed in four steps. Step 1: identify the seasonal patterns by billing cycle, with figures. Step 2: propose a three-month forecast with a high, central and low scenario. Step 3: state the hypotheses of each scenario and the data in the file that supports them. Step 4: check the arithmetic consistency of the totals and flag any break in the series or missing data. Format: forecast table, then hypotheses, then limits. State your confidence level (high, medium, low) for each scenario.

Expected result. A scenario-based forecast, arithmetically checked, with traceable hypotheses and a displayed confidence level.

Mistake to avoid. Presenting a single scenario as a certainty: Copilot's confident tone is no indicator of reliability.

8. Write the Copilot usage rules for the finance team (Expert)

ExpertContext. You are preparing your department's usage policy: what may be pasted, what may not, and how to check.

Write a Copilot Chat usage policy for a finance team of [number] people, in one page. Sections: 1) authorised data (anonymised files, internal policies, email templates), 2) forbidden data (bank identifiers, named remuneration data, documents classified confidential), 3) mandatory verification rule before any figure is sent to management, 4) log of shared prompts and the person responsible for updating it, 5) what to do in case of doubt. Phrase each rule positively and in a checkable way. Context: conversations are logged by the organisation and attached files are stored in the work OneDrive.

Expected result. A one-page policy, in positive and checkable rules, ready to discuss with management and the legal department.

Mistake to avoid. Writing a list of vague prohibitions ("do not paste sensitive data"): nobody knows what is sensitive.

Related lesson. Writing your team's AI usage policy

Frequently asked questions

Can Copilot Chat calculate without error?

Not in natural language on a long table. For a calculation, attach a clean file and explicitly ask for the analysis: Copilot Chat then runs Python code in an isolated environment. Always cross-check at least one figure by hand in Excel.

Can I attach a trial balance or a general ledger?

First check the file's sensitivity label and the internal policy. Attached files are stored in your work OneDrive and are not used to train the models, but conversations are logged and accessible to the administrator. Anonymise third parties if the file leaves your perimeter.