The Microsoft 365 Copilot Prompt Pack for Finance is a collection of ready-to-use example prompts designed specifically for finance professionals. It helps teams use Microsoft 365 Copilot across common finance workflows, so they can reimagine how they handle recurring analysis and reporting tasks.

The pack focuses on five core finance areas:

• Financial closing and reporting – organizing and summarizing close data, standardizing inputs, and drafting leadership-ready materials.
• Forecasting, variance analysis, and performance insights – summarizing forecast outlooks, visualizing trends, and explaining model movements.
• Risk, compliance, and audit readiness – interpreting regulations, updating policy language, and preparing audit-ready documentation.
• Contract and supplier decision support – comparing planned vs. actual spend, reviewing contract terms, and highlighting negotiation risks.
• Collections and cash flow acceleration – identifying overdue invoices, estimating near-term cash inflows, and surfacing recurring dispute drivers.

The prompts are meant to:

• Inspire and guide how you write your own Copilot prompts.
• Show how to ground Copilot in your files (e.g., forecast models, policy docs, contracts, receivables reports).
• Help teams operate more like a “Frontier Firm” by being more adaptable, informed, and effective while still protecting organizational data.

It’s important to note that outputs from these prompts are intended to support productivity and analysis. They are not financial, accounting, investment, or legal advice and are not tailored to your specific organization. Teams should apply professional judgment, follow internal policies, and consult qualified experts where needed.

When you use the Finance Prompt Pack, Microsoft 365 Copilot is powered by an intelligence layer called Work IQ. This layer helps Copilot understand:

• You – your role and the way you work.
• Your organization – shared knowledge, documents, and context.
• Your workflows – how information flows across apps like Excel, PowerPoint, Teams, and email.

Instead of relying only on connectors, Copilot connects individual and organizational knowledge to deliver more relevant and secure experiences in the flow of work. For finance, that often means grounding prompts in items like:

• Close data (e.g., Aggregate sales invoice and payment data, reconciliation reports).
• Forecast models and planning files (e.g., Forecast model, Sentinel revenue planning model).
• Risk and policy content (e.g., leadership meeting notes, policy documents, risk logs).
• Contracts and procurement data (e.g., Contracts cube, Invoice cube, supplier emails).
• Collections and receivables data (e.g., Aging receivables report, dispute logs, customer correspondence).

There are several governance and compliance points to keep in mind:

• Results vary based on your configuration, permissions, data quality, and product availability.
• The examples in the pack are illustrative and may not cover all governance, privacy, compliance, or financial requirements for your organization.
• You should ensure your use of Copilot aligns with internal policies, applicable laws, and the Microsoft 365 Copilot Transparency Note, including guidance on appropriate use cases and meaningful human oversight.
• Outputs should support your work, not replace professional judgment. They should not be treated as formal financial, accounting, investment, or legal advice.

In practice, this means finance leaders should:

• Define which data sources are appropriate to use with Copilot.
• Clarify review and approval steps before AI-generated content is shared externally or used in official reporting.
• Reinforce that teams must refer to internal guidance and regulatory requirements when making decisions.

The Finance Prompt Pack is organized around real finance scenarios, each with specific use cases your team can adapt. Here are some practical examples:

1. Financial closing and reporting

• Standardize close data: Ask Copilot to scan an Aggregate sales invoice and payment data file, find formatting inconsistencies (e.g., date formats, text vs. numeric values, negative signs), and propose Excel formulas or transformations to normalize the data.
• Explain revenue trends: Use a Reconciliation report to identify the top three product categories by revenue over the past three years, summarize growth or decline patterns, and output a short summary plus a table and graph.
• Draft leadership materials: Turn a Variance analysis summary into a 4–6 slide PowerPoint outline with key variances, drivers, implications, and a short talk track for each slide.

2. Forecasting, variance analysis, and performance insights

• Summarize forecast outlook: From a Forecast model, generate a one-page briefing on the outlook for the top three product categories, highlighting assumptions, changes vs. prior forecast, and emerging risks or opportunities.
• Visualize trends: Use structured forecast data to create charts showing forecasted revenue by product category over the next two years, with a short explanation of what the trends suggest for planning.
• Explain model movements: From the Sentinel revenue planning model, summarize month-over-month changes in ARR, consumption, seat growth, and credits usage, then convert that into an executive-level narrative for a weekly forecast call.

3. Risk, compliance, and audit readiness

• Update policy guidance: Summarize leadership meeting feedback into 6–10 bullets (decisions, requested changes, open questions, owners/next steps), then draft updated wording for the impacted sections of a policy document.
• Compare regulations: Compare two accounting amendments in a simple table and add a concise paragraph summarizing the key differences.
• Clarify finance terms: Rewrite technical finance terms and formulas into plain language with simple examples for non-finance stakeholders.

4. Contract and supplier decision support

• Spot spend variances: Compare Contracts cube (planned/committed spend) with Invoice cube (actual invoiced/paid spend) to highlight variances by vendor, including a table with planned vs. actual and variance notes.
• Prepare for negotiations: Summarize recent emails, prior contracts, and invoice data for a supplier to surface renewal dates, payment patterns, and issues that may affect negotiation.
• Flag risky clauses: Review a contract to identify clauses that may require deeper review (e.g., unilateral changes, autorenewals, broad limitations of liability) and explain why each could create financial or contractual risk.

5. Collections and cash flow acceleration

• Prioritize overdue invoices: From an Aging receivables report and recent customer emails, identify the most overdue invoices by balance, summarize issues, and recommend next steps in a structured table.
• Estimate near-term cash inflow: Use aging data and customer payment history to estimate expected cash receipts over the next 30 days and flag invoices at risk of delay, then recommend targeted actions with confidence levels.
• Reduce recurring disputes: Analyze a dispute log, invoice data, and customer correspondence to identify the most common dispute reasons by value and frequency, then recommend preventive actions (process, policy, or upstream fixes).

Across these scenarios, the Prompt Pack helps finance teams rethink how they use their existing files and data with Copilot to get to clearer summaries, structured outputs, and decision-ready materials faster—while still keeping humans in the loop for review and judgment.