Finance & Accounting Prompts to Build or Create Something

You are a technical accounting specialist. Draft a financial statement footnote for [topic]. Topic: [e.g., revenue recognition policy, lease commitments, stock compensation, debt covenants, subsequent events] Data: [Paste: relevant financial data, contract terms, or disclosure requirements] Applicable standard: [ASC topic number or IFRS standard] Draft the footnote including: 1) Policy description (how we account for this item) 2) Quantitative disclosures (required amounts, tables, schedules) 3) Qualitative disclosures (judgments made, risks, commitments) 4) Year-over-year comparison (changes from prior period) 5) Required tabular data (formatted for financial statements) Tone: Technical but readable. Auditor should be able to verify each statement. Format: Footnote format ready for insertion into financial statements.

You are a Controller building a monthly financial reporting package for leadership. Company details: - Revenue range: [Approximate annual revenue] - Industry: [Industry] - Number of business units/segments: [Number] - Board reporting: [Yes/No — monthly or quarterly?] - Key stakeholders: [CEO, Board, Investors, Lenders?] Design a reporting package that includes: 1) Executive summary page (key metrics at a glance) 2) Income statement with variance analysis (actual vs. budget vs. prior year) 3) Balance sheet with flux analysis 4) Cash flow statement with commentary 5) Revenue analysis (by product/service, customer, geography as relevant) 6) Operating expense detail (by department or cost center) 7) KPI dashboard (financial and operational metrics) 8) Headcount and labor cost summary 9) Capital expenditure tracking (actual vs. budget) 10) Appendix: detailed schedules as needed For each section, specify: what data is needed, who prepares it, and the close day it should be ready. Format: Reporting package outline with timeline and responsibilities.

You are an accounting policy writer. Draft an accounting policy for [topic]. Requirements: - Objective (what problem does this policy solve?) - Scope (which accounts/transactions does it cover?) - Guidance (step-by-step how to account for this) - Examples (3-4 scenarios: what you do in each) - Exceptions (when does this NOT apply?) - Effective date & approval - Owner / questions contact Topic: [Paste policy need here - e.g., "How to account for customer rebates"] Tone: Professional, clear, no jargon. Assume accountants with 2-3 years experience.

You are an internal auditor. Create a testing workpaper for this control. Control description: [Paste the control narrative — what the control does, who, how often] Testing approach: - Control frequency: [daily/weekly/monthly/quarterly/annually] - Suggested sample size: [Based on frequency and risk] - Testing period: [Date range] Design the workpaper: 1) Control objective (what risk is being addressed?) 2) Test procedure (step-by-step what the tester will do) 3) Population description (total items subject to the control) 4) Sample selection method (random, haphazard, specific items) 5) Test attributes (what specifically is being checked for each sample item?) 6) Expected evidence (what documentation should exist?) 7) Exception definition (what constitutes a failure?) 8) Results matrix: Sample # | Item Description | Attribute 1 Pass/Fail | Attribute 2 Pass/Fail | Notes 9) Conclusion template Format: Testing workpaper template ready for the tester to complete.

You are a risk management analyst. Build a risk assessment for the finance department. Context: - Company size: [Revenue, employees] - Industry: [Industry and any specific regulatory environment] - Recent changes: [New systems, reorganizations, M&A, leadership changes] - Known issues: [Any recent audit findings, errors, or incidents] Assess risks across these categories: 1) Financial reporting risks (misstatement, fraud, estimation error) 2) Operational risks (process failures, key person dependency, system outages) 3) Compliance risks (tax, regulatory, SOX, data privacy) 4) Technology risks (cybersecurity, ERP stability, data integrity) 5) People risks (turnover, skills gaps, capacity constraints) For each risk: - Likelihood (high/medium/low) - Impact (high/medium/low) - Current mitigation (what controls exist today?) - Residual risk (after mitigation, what's the remaining exposure?) - Recommended action (accept, mitigate further, transfer, or avoid) Format: Risk register matrix. Sort by residual risk (highest first).

You are a SOX auditor. Document a process walkthrough for this business cycle. Process: [e.g., Order-to-Cash, Procure-to-Pay, Hire-to-Retire, Record-to-Report] Document the end-to-end process: 1) Process initiation (what triggers this process?) 2) Key steps (numbered, in sequence) - For each step: who does it, what system, what happens 3) Key controls (where are the control points?) - For each control: what it prevents/detects, how it operates, evidence generated 4) System interfaces (data flowing between systems) 5) Reports used (who generates, who reviews, how often) 6) Segregation of duties (who can't do what) 7) Key accounts impacted (which GL accounts are affected) 8) Risk of material misstatement (what could go wrong at each step) Format: Flowchart-ready narrative. Each step numbered and cross-referenced to controls.

You are an internal controls analyst. Build a segregation of duties (SoD) matrix for our finance processes. Roles in the finance team: [Paste: role titles and primary responsibilities] Build a matrix for these processes: 1) Procure-to-Pay (requisition, PO approval, receipt, invoice, payment) 2) Order-to-Cash (order entry, credit approval, shipping, invoicing, cash application) 3) Payroll (timesheet approval, pay rate changes, payroll processing, bank release) 4) General Ledger (JE entry, JE approval, period close, reconciliation) For each process: - List the key duties that must be separated - Map which roles currently perform each duty - Flag conflicts (same person performing incompatible duties) - Recommend remediation for each conflict (reassign, add compensating control, system restriction) Format: Matrix table. Rows = duties, Columns = roles. Color code: Green (appropriate), Red (conflict), Yellow (compensating control needed).

You are a compliance manager. Build a remediation plan for this control deficiency. Deficiency: [Paste: description of the control deficiency or material weakness] Severity: [Deficiency / Significant deficiency / Material weakness] Identified by: [Internal audit / External audit / Self-identified] Date identified: [Date] Build a remediation plan: 1) Root cause analysis (why did this deficiency occur?) - Process gap? People gap? Technology gap? Design vs. operating effectiveness? 2) Immediate actions (what can be done within 30 days to mitigate risk?) 3) Long-term remediation steps (numbered, with specific deliverables) 4) Timeline (Gantt-chart style: action | owner | start | end | status) 5) Resources required (people, budget, systems, external help) 6) Testing plan (how will we verify the remediation is effective?) 7) Monitoring plan (how will we ensure the control stays effective going forward?) 8) Reporting cadence (status updates to audit committee — monthly? quarterly?) Format: Remediation plan document suitable for audit committee presentation.

You are a systems analyst. Write a report specification for a new financial report in our ERP. Report name: [Name] Requested by: [Role] Purpose: [What business question does this report answer?] Define: 1) Data source (which tables/modules — GL, AP, AR, etc.) 2) Filters/parameters (date range, entity, department, account range) 3) Columns needed (field name, format, sort order) 4) Grouping and subtotals 5) Calculations (formulas, derived fields, running totals) 6) Output format (PDF, Excel, dashboard widget) 7) Distribution (who gets it, how often, automated or on-demand) 8) Security (who can access this report?) Also include: - Sample output mockup (text-based table showing expected layout) - Acceptance criteria - Testing approach Format: Formal specification document.

You are a systems administrator. Document the current configuration of our financial system. System: [ERP/module name] Module being documented: [GL, AP, AR, FA, etc.] Document these settings: 1) Company/entity setup (legal entities, intercompany relationships) 2) Calendar/periods (fiscal year, open/closed periods) 3) Currency settings (functional currency, foreign currencies, revaluation) 4) Account structure (segments, cost centers, dimensions) 5) Approval workflows (who approves what, dollar thresholds) 6) Automatic entries (recurring JEs, allocations, accruals) 7) Integration points (connections to other systems, data flow) 8) Security settings (roles, permissions, sensitive functions) 9) Report configuration (standard reports, custom reports, distribution lists) 10) Key control settings (duplicate invoice checking, tolerance limits, matching rules) Format: Configuration reference document. Include current setting values and the business reason for each setting.

You are an HR partner for the finance team. Draft a job description for a [role title]. Details: - Company size: [employees] / [revenue range] - Industry: [industry] - Reports to: [title] - Team size: [number on finance team] - ERP system: [system name] - Remote/hybrid/onsite: [preference] Include: 1) Role summary (3-4 sentences — what does this person DO day-to-day?) 2) Key responsibilities (8-10 bullet points, specific not generic) 3) Must-have qualifications (realistic — don't ask for 10 years for a staff role) 4) Nice-to-have qualifications 5) What success looks like in the first 90 days 6) Compensation range guidance (if appropriate) Tone: Human and specific. Avoid corporate jargon. Make a good candidate say "that sounds like a real job."

You are a process documentation specialist. Write a Standard Operating Procedure (SOP) for [process name]. Process: [e.g., monthly bank reconciliation, new vendor setup, expense report approval] Performed by: [role] Frequency: [daily, weekly, monthly, as-needed] Systems used: [ERP, banking portal, etc.] Document: 1) Purpose — why does this process exist? 2) Scope — what's included and NOT included 3) Prerequisites — what must be done before starting? 4) Step-by-step instructions (numbered, specific, include system navigation) 5) Decision points — where does the person make a judgment call? 6) Common errors and how to avoid them 7) Escalation — when should you stop and ask your manager? 8) Output — what does the finished work product look like? Tone: Written for a new hire with 1-2 years experience. Clear enough to follow on day one.

You are a compliance officer. Draft an AI usage policy for our accounting department. Company context: - Company size: [employees] - Industry: [industry and any regulatory requirements] - Current AI tools in use: [list tools] - Data sensitivity: [types of data the team handles] Policy must cover: 1) Approved tools (which AI tools are sanctioned?) 2) Approved use cases (what can/cannot be done with AI?) 3) Data classification (what data can/cannot be entered?) 4) PII rules (no SSNs, bank accounts, etc. in prompts) 5) Output review requirements (who reviews before use?) 6) Documentation requirements (log what AI was used for) 7) Training requirements (who, how often) 8) Violation consequences (escalation path) 9) Exception process (requesting non-approved tools) 10) Review cadence (how often is policy updated?) Tone: Practical, not scary. Enable smart AI use while managing risk.

You are a QA analyst. Create a checklist for reviewing AI-generated financial content before use. Content type: [variance explanation, forecast commentary, board narrative, policy draft, etc.] Validation checklist: 1) Factual accuracy — do all numbers match source data? 2) Calculation check — are derived numbers correct? (recalculate manually) 3) Completeness — are all required items addressed? 4) Tone and audience — is it appropriate for the reader? 5) Hallucination check — anything stated that wasn't in the input data? 6) Bias check — does narrative lean too positive or negative? 7) Confidentiality — does output contain PII or sensitive data? 8) Consistency — aligns with prior period's language and approach? 9) Judgment calls — are opinions clearly marked vs. stated as facts? 10) Attribution — can every claim be traced to source data? For each item: - What to look for (specific examples of problems) - Time estimate (seconds or minutes) - If it fails: what to do Format: Printable checklist with checkboxes.

You are a technology procurement analyst. Create an evaluation framework for an AI tool. Tool being evaluated: [Name and category] Intended use case: [What will we use it for?] Data involved: [What financial data will the tool access?] Evaluation criteria: 1) Security (SOC 2, data residency, encryption, access controls) 2) Data handling (does data leave our environment? Used for training?) 3) Accuracy (error rates, hallucination frequency) 4) Integration (ERP compatible? API? SSO?) 5) Audit trail (can we log who used it and what was generated?) 6) Cost model (per-user, per-transaction, flat fee) 7) Vendor stability (funding, customer base, longevity) 8) Support (implementation, training, ongoing) 9) Customization (can we tune for accounting terminology?) 10) Exit strategy (can we get our data out?) Format: Scorecard (1-5 rating per criterion). Include weighted total and demo questions.

You are an AI implementation specialist. Create a testing framework for prompts before deploying them to the team. Prompt to test: [Paste the prompt you want to validate] Intended use: [What will the output be used for?] Risk level: [Low (internal use only) / Medium (management review) / High (external reporting or audit)] Test plan: 1) Accuracy test — run the prompt with known data where you know the correct answer. Does AI get it right? 2) Consistency test — run the same prompt 3 times. Do you get substantially similar outputs? 3) Edge case test — try with incomplete data, unusual formats, or extreme values. Does it handle gracefully? 4) Hallucination test — does AI add information not in the input? (Run with minimal input and check for fabrication) 5) Sensitivity test — change one number slightly. Does the narrative change appropriately? 6) Security test — does the prompt ask for or expose sensitive data it shouldn't? 7) Tone test — is the output appropriate for the intended audience? 8) Handoff test — give the output to a colleague without context. Can they use it? Document results: - Pass/fail for each test - Issues found and fixes applied - Final approved prompt version - Review date and approver Format: Test documentation template.

You are a finance process manager building a standardized close checklist. Business context: [DESCRIBE: Company type, number of entities, key business lines, ERP system in use, approximate team size] Build a period-end close checklist with: 1) Pre-close tasks (days -3 to 0): cutoff procedures, sub-ledger locks, accrual submissions 2) Close tasks by day (Day 1, Day 2, Day 3...): reconciliations, JEs, reviews — ordered by dependency 3) Post-close tasks: flux reviews, reporting package, management review, financial statement sign-off 4) For each task: owner role, estimated time, dependency (what must be done first), and system/tool involved Output: Checklist table — Task | Owner | Day | Estimated Time | Dependencies | System. Suitable for use in a project management tool.

You are an FP&A analyst building financial scenarios for a key business decision. Base case data: [PASTE: Current revenue run rate | Current cost structure | Key business drivers (volume, price, headcount)] Decision or risk being modeled: [DESCRIBE: What are you modeling? Examples: entering a new market, losing a major customer, a pricing change, a cost reduction program] Build 3 scenarios: 1) Base case — current trajectory, no major changes 2) Upside — most favorable realistic outcome; state assumptions 3) Downside — adverse outcome; state assumptions and what would trigger it For each scenario, show: - Revenue impact ($) - Margin impact (% and $) - Cash impact - Break-even point (if relevant) - Key decision trigger: at what point does this scenario change the recommended course of action? Output: Scenario comparison table + narrative summary suitable for executive decision-making.