Finance & Accounting Prompts to Manage Your Team and Business

You are an AR specialist. Organize and prioritize these customer billing disputes. Dispute data: [Paste: customer, invoice #, amount, dispute reason, date opened, current status] For each dispute: 1) Categorize the dispute type: - Pricing error (invoice doesn't match quote/contract) - Quantity discrepancy (customer says they received less) - Quality/return issue (product or service problem) - Duplicate billing - Missing PO or authorization - Tax or freight dispute 2) Determine likely resolution (credit memo, rebill, investigation needed) 3) Estimate financial impact (full credit, partial credit, no credit) 4) Assign priority (high = large $ or key customer, medium, low) 5) Suggest next action and responsible person Format: Dispute tracker with columns: Dispute # | Customer | Amount | Type | Priority | Next Action | Owner | Target Resolution Date

You are an accounting manager. Organize and track this audit request list (PBC list). Audit requests: [Paste the auditor's PBC list — items requested, descriptions] For each request: - Assign to team member (suggest based on request type) - Estimate preparation time (hours) - Identify source system (ERP, bank, payroll, manual) - Flag dependencies ("need close to complete before preparing") - Set priority (critical path items first) - Note if same as prior year (reuse template) Produce: 1) Tracker: Item # | Description | Owner | Source | Hours | Due Date | Status 2) Timeline: critical path items first 3) Total estimated hours by team member (workload distribution) Format: Structured table + workload summary.

You are an IT auditor. Review ERP user access for appropriateness. User access data: [Paste: user name, role, department, access level, last login date, permissions/modules] Review for: 1) Terminated employees still with active access (compare to HR termination list) 2) Excessive access (users with admin/superuser roles who shouldn't have them) 3) Segregation of duties violations (users who can create AND approve, entry AND posting) 4) Dormant accounts (no login in 90+ days — should access be suspended?) 5) Generic or shared accounts (security risk — who is actually using them?) 6) Access misalignment (access doesn't match current job role — role change without access update) 7) Privileged access monitoring (who has access to sensitive functions like bank account changes?) Produce: - Exception list by category - Risk rating for each exception (high/medium/low) - Recommended action for each - Statistics: total users, % with exceptions, comparison to prior review Format: Access review report suitable for audit documentation.

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 Controller. Build a comprehensive month-end close checklist. Team size: [number] ERP: [system] Industry: [industry] Typical close timeline: [X business days] Build a checklist organized by: 1) Day 1-2: Initial tasks (sub-ledger closes, bank recs, cutoff procedures) 2) Day 3-4: Core tasks (JEs, accruals, reconciliations, intercompany) 3) Day 5-6: Review tasks (flux analysis, variance explanations, management review) 4) Day 7+: Finalization (reporting package, distribution, archive) For each item: - Task description (specific, not generic) - Owner (by role) - Estimated time - Dependencies (what must be done first?) - Deliverable (what does "done" look like?) Format: Numbered checklist. Include "Day 0" pre-close preparation.

You are a finance manager. Draft a performance review for a [role title] team member. Team member's role: [Title] Review period: [Date range] Key metrics/results: [Paste: close time, error rates, process improvements, projects completed] Structure the review: 1) Overall performance summary (2-3 sentences) 2) Key accomplishments (3-5 specific achievements with quantified impact) 3) Areas for development (2-3 specific, constructive) 4) Goals for next period (3-5 SMART goals) 5) Career development recommendations (training, exposure, stretch assignments) 6) Rating recommendation: [Exceeds / Meets / Developing] For development areas: - Be specific about the gap - Provide an example - Suggest a specific action to improve - Offer support (training, mentoring, resources) Tone: Balanced, fair, specific. Focus on behaviors and results, not personality.

You are a Controller. Build a cross-training plan for the finance team to reduce key-person dependency. Team members: [Paste: name/role, primary responsibilities, backup (if any)] Identify: 1) Single points of failure (tasks only one person can do) 2) Critical processes during close (what breaks if someone is out during close?) 3) High-risk knowledge gaps (tribal knowledge not documented) Build a cross-training plan: - Priority processes to cross-train (ranked by risk) - Primary owner and backup trainee for each - Training method (shadow, SOP + practice, formal training) - Timeline (realistic — don't overload people) - Validation (how do we know the backup can actually do it?) - Documentation requirements (SOPs, checklists, video recordings) Also include: - Rotation schedule (if applicable — switch responsibilities periodically) - Emergency runbook (if someone leaves suddenly, what are the first 48 hours?) Format: Cross-training matrix + timeline + emergency runbook.

You are a Controller planning team capacity for next fiscal year. Current team: [Paste: role, name, FTE %, primary responsibilities, estimated hours per month by activity] Anticipated changes: [New projects, system implementations, regulatory changes, growth plans, departures] Analyze: 1) Current utilization by team member (how loaded is everyone?) 2) Peak period analysis (close week, audit season, budget season, tax deadlines) 3) Capacity gaps (where do we not have enough people?) 4) Excess capacity (where are we overstaffed or could automate?) 5) Impact of anticipated changes (what's changing and how does it affect workload?) Recommend: - Staffing needs (new hires, contractors, outsourcing) - Automation opportunities (which manual tasks should be eliminated?) - Rebalancing opportunities (redistribute work more evenly) - Training needs (upskill existing team) - Risk assessment (what happens if we DON'T add capacity?) Format: Capacity analysis table + hiring/automation recommendation memo.

You are a risk manager. Assess AI-specific risks for finance department operations. Current AI usage: [Paste: tool name, use case, data accessed, frequency of use, users] Assess each risk category: 1) Data leakage — could sensitive financial data end up in AI training data or third-party systems? 2) Accuracy — what's the financial impact if AI output is wrong and not caught? 3) Dependency — what happens if the AI tool goes down during close? 4) Compliance — does AI usage comply with SOX, data privacy, and industry regulations? 5) Bias — could AI systematically skew financial analysis in one direction? 6) Audit trail — can we prove to auditors what was AI-generated vs. human-reviewed? 7) Vendor risk — what if the AI vendor is acquired, pivots, or goes out of business? 8) Skills atrophy — are team members losing the ability to do tasks manually? For each risk: - Likelihood and impact rating - Current controls in place - Recommended additional controls - Monitoring metrics Format: AI risk register. Priority-ranked.

You are an L&D specialist for a finance team. Build an AI training curriculum. Team profile: - Team size: [Number] - Roles: [List roles on the team] - Current AI literacy: [Beginner / Some exposure / Moderate / Advanced] - Approved AI tools: [List tools] - Available training time: [Hours per month] Build a training plan: Module 1: AI Fundamentals (2 hours) - What AI can and cannot do for accounting - Our approved tools and use cases - Data safety rules (what never goes into AI) Module 2: Prompt Engineering Basics (2 hours) - How to write effective prompts for financial tasks - Common mistakes and how to fix them - Practice exercises with our actual workflows Module 3: Hands-On Workshops (4 hours) - Walk through each approved use case with real examples - Practice with sample data (not production data) - Review and validate AI outputs Module 4: Advanced Applications (2 hours) - Building custom prompts for your specific tasks - Chaining prompts for complex analyses - When NOT to use AI Module 5: Governance and Compliance (1 hour) - Our AI usage policy review - Documentation requirements - Escalation procedures For each module: - Learning objectives - Delivery method (live, self-paced, hands-on) - Assessment method (quiz, demonstration, peer review) - Suggested resources Format: Training curriculum with schedule and materials list.

You are an organizational change specialist. Build a change management plan for introducing AI tools to the finance team. Context: - Team size: [Number] - AI tools being introduced: [List tools and use cases] - Timeline: [Rollout over how many months?] - Team sentiment: [Excited / Cautious / Resistant / Mixed] - Leadership support: [Strong / Moderate / Unclear] Build a change management plan: 1) Stakeholder analysis - Champions (who's excited and influential?) - Skeptics (who needs convincing and what are their concerns?) - Impacted roles (whose daily work changes most?) 2) Communication plan - Announcement (the "why" — what problem are we solving, not just "AI is cool") - Regular updates (weekly during rollout) - Feedback channels (how do people raise concerns?) 3) Training and support - Pre-launch training (before tools go live) - Office hours (ongoing support during adoption) - Super-user network (trained power users who help colleagues) 4) Resistance management - Common fears and how to address each - Quick wins to demonstrate value early - "No one loses their job" messaging (if true) 5) Success metrics - Adoption rate (% of team actively using tools) - Satisfaction score (survey at 30/60/90 days) - Productivity metrics (close time, error rates) - Escalation count (problems reported) Format: Change management plan document with timeline and RACI matrix.

You are a controller managing month-end close. Close checklist: [PASTE: Task | Owner | Status | Due date] Produce: 1) Completion scorecard — % complete, tasks remaining by owner, estimated hours to finish 2) Subledger-to-GL mismatches — show variance $ and which team owns resolution 3) GL accounts with >15% balance swing vs. prior month — plain-English explanation for each 4) Journal entries pending >3 days — list by preparer and days waiting 5) Top 5 blockers — with named owner and specific resolution step Output: CFO-ready status report. End with projected close completion date. Tone: Factual, no filler.

You are an AP manager reviewing the weekly payment run before release. Payment batch data: [PASTE: Vendor | Invoice # | Amount | Due date | Payment method | Bank account on file] Review for: 1) Payments to vendors not in the approved vendor master — flag for confirmation 2) Payments where bank account changed in the last 30 days — high fraud risk, require secondary approval 3) Invoices without a matching approved PO — flag with amount 4) Duplicate payments — same vendor + same amount within 60 days 5) Early payments where no early payment discount applies — potential cash optimization opportunity 6) Payments over $[THRESHOLD] — confirm secondary approval is on file Output: Payment run approval report. Clear section for: Approved / Requires review before release / Do not pay (reason).

You are an AP supervisor reviewing the vendor master for data quality issues. Vendor master export: [PASTE: Vendor ID | Vendor name | Address | Tax ID | Bank account | Payment terms | Last invoice date | Status (active/inactive)] Flag: 1) Duplicate vendors — same name (including variations like "Inc" vs. "Incorporated"), same tax ID, or same bank account number 2) Inactive vendors with open balances — no invoice in 12+ months but balance outstanding 3) Missing critical data — no tax ID, no bank account, no address 4) Vendors with recent bank account changes — flag for fraud review 5) Vendors with unusual payment terms vs. your standard (net 30) Output: Cleanup priority list — High priority (fraud risk or compliance issue) / Medium (data quality) / Low (housekeeping). Include recommended action for each.

You are a procurement manager preparing for vendor payment terms discussions. Vendor data: [PASTE: Vendor | Annual spend | Current payment terms | Industry standard terms | Years as vendor | Any disputes or quality issues] For each vendor: - Assess negotiation leverage: spending volume / length of relationship / alternative suppliers available - Recommend target terms: current terms → proposed terms - Calculate cash flow impact of proposed change (annual $ improvement) - Note any trade-offs: risk of pricing increase if terms extended Prioritize: Vendors where cash flow improvement is largest relative to relationship risk. Output: Negotiation prep table — Vendor | Current Terms | Target Terms | Annual Cash Impact | Leverage Level | Talking Points. End with total cash flow improvement if all proposals succeed.

You are an AP manager preparing for 1099 filing. Vendor payment data: [PASTE: Vendor name | Tax ID | Total payments YTD | Payment type (services/rent/other) | W-9 on file? (yes/no) | Vendor type (individual/corporation/LLC/other)] Identify: 1) Vendors requiring 1099-NEC — US non-corporations paid $600+ for services 2) Vendors requiring 1099-MISC — rent payments $600+, royalties $10+, other applicable payments 3) Missing W-9s — vendors requiring a 1099 but no W-9 on file; flag for immediate follow-up 4) Incorrect tax IDs — format check (should be XX-XXXXXXX) 5) Threshold exceptions — payments close to but under $600 that may have been split across invoices Output: 1099 filing preparation checklist — Vendor | Form Type | Total Payments | W-9 Status | Action Required. Flag: total vendors requiring forms, total missing W-9s, deadline for correction.

You are an AR manager reviewing open customer disputes. Dispute log: [PASTE: Customer | Invoice # | Disputed amount | Dispute reason | Date opened | Owner | Last action | Days open] For each dispute: - Assess status: likely to resolve in customer's favor / likely to collect in full / negotiate partial / escalate - Recommend specific next action with a deadline - Flag: disputes open >30 days without a clear resolution path - Estimate cash impact: expected collection amount vs. dispute amount Also flag: - Recurring dispute reasons (same issue appearing with multiple customers — systemic problem) - Customers with multiple open disputes — relationship risk Output: Dispute resolution action plan — prioritized by dollar amount. Total dispute exposure and expected recovery %.

You are a senior FP&A analyst structuring the annual budget process. Business context: [DESCRIBE: Company size, number of departments, ERP system, key revenue and cost drivers, timeline for board approval] Build an annual budget process plan covering: 1) Budget calendar — key dates from kickoff to board approval (work backward from approval date) 2) Department submission templates — what data each department needs to provide and in what format 3) Assumptions to set centrally — headcount rates, benefits load, inflation factors, FX rates 4) Review milestones — who reviews what and when before final submission 5) Common budget mistakes to avoid — over-optimistic revenue, missing one-time costs, ignoring seasonality Output: Budget process guide + calendar table. Suitable for distributing to all department heads at budget kickoff.