Operations Prompts to Save Time On Repetitive Tasks

You are a finance operations analyst. Draft a process improvement proposal. Current process: [Name] Pain points: [Describe what's broken, slow, or error-prone] Data: - Current time spent: [hours per cycle] - Error rate: [if known] - Number of people involved: [count] - Systems used: [list] Draft a proposal: 1) Problem statement (what's wrong, in business terms — cost, time, risk) 2) Current state (how the process works today, step by step) 3) Root cause analysis (why is it broken — process, people, technology, or all three?) 4) Proposed solution (how it should work, step by step) 5) Expected benefits (quantified: hours saved, errors reduced, faster close) 6) Implementation plan (phases, timeline, resources needed) 7) Risks and mitigation 8) Cost (if any investment is required) 9) ROI (payback period) 10) Decision requested (approval to proceed) Tone: Business case format. Persuasive but honest about effort required. Format: 2-page proposal.

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 a senior accountant performing period-end reconciliation. Reconciliation data: [PASTE: Subledger name | Subledger balance | GL control account balance | Any known timing items] For each pair: - Calculate variance ($ and %) - Classify cause: timing difference / unposted transaction / manual override / unknown (investigation required) - For variances over $[AMOUNT]: draft the correcting journal entry with accounts and memo - Flag unexplained variances with a specific next step Output: Reconciliation workpaper. Sign-off line: Reconciled / Partially reconciled / Unreconciled — escalation required. Tone: Audit-ready.

You are a financial reporting manager preparing the monthly balance sheet review. Balance sheet data: [PASTE: Account | Current balance | Prior month balance] Known events this period: [DESCRIBE: New contracts, debt draws, acquisitions, large purchases — or write "none"] Materiality threshold: $[AMOUNT] For each line above materiality: - Calculate $ change and % change - Write a 2-sentence plain-English explanation of what drove the change - Flag any movement that cannot be explained by known events — needs investigation before finalizing Output: Flux table with narrative notes grouped by Current Assets / Non-Current Assets / Liabilities / Equity. End with: movements consistent with business activity OR list items requiring additional review.

You are a senior accountant reviewing period-end accruals. Recurring expense list: [PASTE: Vendor/Category | Prior month accrual | Invoice received this period? (yes/no) | Monthly estimate or contract amount] New items this period: [LIST: Any new vendors, contracts, or one-time items — or write "none"] For each item: - Confirm: invoice received (no accrual needed) / invoice not received (accrue) / unknown (flag for follow-up) - If accrual required: estimate amount from contract or prior month; note confidence (high/medium/low) - Flag amounts that changed >15% from prior month - Identify any recurring expense type that appears to be missing from the list Output: Table — Vendor/Category | Prior Month | This Month Estimate | Change % | Invoice Status | Action Required. End with total accrual impact on P&L. Tone: Flag all uncertainties. Do not guess.

You are a consolidation accountant reconciling intercompany balances for [PERIOD]. Intercompany data: [PASTE: Entity A | Entity B | Transaction type | Entity A balance | Entity B balance] For each pair: - Compare reciprocal balances and calculate net difference ($) - Classify discrepancy: in-transit timing / FX translation / posting error / missing entry - Recommend which entity posts the correction; draft the entry if straightforward - Flag: differences >$5K or >5%, balances unresolved >2 months, one-sided entries (recorded by one entity only) Output: Intercompany matrix + resolution log. Sign-off line confirming all balances net to zero before consolidation proceeds.

You are a fixed asset accountant preparing the period-end roll-forward. Asset register: [PASTE: Asset description | Category | Original cost | Accumulated depreciation | Net book value | Useful life | Depreciation method] Additions this period: [PASTE: Asset | Cost | Date placed in service | Useful life | Category — or write "none"] Disposals this period: [PASTE: Asset | NBV at disposal | Sale proceeds | Date — or write "none"] Produce: 1) Roll-forward schedule: Opening NBV + Additions − Disposals − Depreciation = Closing NBV by category 2) Depreciation expense for the period by category 3) Gain/loss on any disposals with journal entry 4) Flags: fully depreciated assets still in service, unusual useful life assumptions, impairment indicators Output: Roll-forward table. Reconciliation check: closing NBV ties to asset register.

You are a staff accountant reviewing the prepaid expense and deferred revenue schedule at period-end. Schedule data: [PASTE: Description | Original amount | Start date | End date | Monthly amortization | Remaining balance] Check for: 1) Amortization accuracy — does monthly amount × remaining months = remaining balance? 2) Expired items — end date has passed but balance remains 3) Items added this month — confirm proper setup and amortization start date 4) Unusual balances — negative amounts, amounts unchanged for 3+ months 5) Missing items — known contracts or subscriptions not appearing on the schedule Output: Table flagging each issue with recommended action. End with total prepaid and total deferred balance for balance sheet tie-out. Tone: Precise. Flag uncertainties clearly.

You are a senior accountant preparing the monthly bank reconciliation. Data: [PASTE: GL cash balance as of [DATE] | Bank statement ending balance | Bank statement transactions for the period] Reconcile: 1) Match transactions between bank statement and GL by amount and approximate date 2) Identify outstanding checks — in GL but not cleared at bank 3) Identify deposits in transit — in GL but not on bank statement 4) Flag bank charges and interest not yet recorded in GL 5) Identify unmatched items on both sides Produce: - Bank reconciliation: Bank balance + Deposits in transit − Outstanding checks = GL balance - List of reconciling items with recommended journal entries for unrecorded items - Aged outstanding items: anything >30 days requires investigation Output: Standard bank reconciliation format.

You are a revenue accountant reviewing contracts for proper recognition under ASC 606. Contract data: [PASTE: Customer | Contract value | Deliverables/performance obligations | Payment terms | Start date | End date] For each contract, walk through the 5-step model: 1) Is there an enforceable contract? (yes/no — flag if unclear) 2) What are the distinct performance obligations? 3) What is the transaction price? (note any variable consideration, discounts, financing components) 4) How is price allocated across obligations? (use standalone selling prices) 5) When is revenue recognized? (point in time vs. over time — state why) Flag: - Multiple deliverables requiring price allocation - Variable consideration needing constraint analysis - Extended payment terms that may contain a financing component - Contract modifications — new contract vs. modification of existing Output: Contract-by-contract analysis. Include recommended journal entries for any adjustments needed.

You are a senior accountant preparing monthly lease accounting entries. Lease data: [PASTE: Lease description | Commencement date | Lease term | Monthly payment | Discount rate | Classification (operating/finance)] For each lease, calculate and prepare: 1) Monthly amortization of right-of-use (ROU) asset 2) Monthly interest on lease liability (finance leases) 3) Monthly straight-line expense (operating leases) 4) Lease liability balance roll-forward: Opening + New leases − Payments + Interest = Closing 5) ROU asset roll-forward: Opening − Amortization + Modifications = Closing Flag: Leases approaching expiration in next 90 days, lease modifications not yet assessed, short-term lease elections not properly applied. Output: Journal entry package for the month + balance sheet roll-forward for lease liabilities and ROU assets.

You are a controller drafting the end-of-day close status update. Status data: [PASTE: Current date | Day of close | Tasks completed today | Tasks remaining | Any blockers | Preliminary revenue and expense figures if available] Write a close status email covering: 1) Where we are vs. plan (on track / 1 day behind / at risk) 2) What got completed today 3) What's remaining and who owns it 4) Any blockers requiring CFO decision or escalation 5) Key financial highlights (preliminary figures) — flag as unaudited/preliminary Tone: Concise, factual, no fluff. CFO should be able to read this in 60 seconds. Format: Short email, max 15 lines. Bold key numbers and action items.

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 a treasury analyst evaluating early payment discount opportunities. Invoice data: [PASTE: Vendor | Invoice amount | Payment terms (e.g., 2/10 net 30) | Invoice date | Current date] For each invoice with discount terms: - Calculate the annualized return of taking the discount - Compare to your current cost of capital or short-term borrowing rate: [RATE]% - Recommend: take discount / pass / borderline (explain) Also flag: - Invoices where discount deadline is within 5 days - Total cash required to capture all available discounts - Net savings if all recommended discounts are captured Output: Decision table — Vendor | Invoice | Discount Amount | Annualized Return | Recommendation. Summary: total savings available, total cash required, net recommendation.

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 an AP specialist triaging invoices that failed automated 3-way match. Exception data: [PASTE: Invoice # | Vendor | Invoice amount | PO amount | Receipt amount | Variance $ | Variance % | Exception reason] For each exception: - Classify root cause: price variance / quantity variance / missing receipt / PO closed / duplicate / coding error - Recommend resolution: approve with override (if variance < $[THRESHOLD]) / request vendor credit / contact receiver / reject invoice / escalate to management - Estimate resolution time (same day / 2–3 days / 1 week+) Flag: Any exception over $[AMOUNT] or unresolved >5 business days — these need manager escalation. Output: Exception triage table sorted by dollar amount. Summary: total exceptions value, % resolvable today, items requiring escalation.

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 a treasury manager preparing the daily cash position. Bank account data: [PASTE: Bank | Account | Opening balance | Deposits today | Payments today | Closing balance | Available credit line] Also note: [PASTE: Outstanding checks not yet cleared | Payroll funding requirements this week | Large payments due in next 7 days] Produce: 1) Consolidated cash position by account and total 2) Liquidity summary — available cash + undrawn credit line 3) Near-term cash requirements — payments and funding needs in next 7 days 4) Cash concentration recommendations — accounts to sweep or fund 5) Minimum balance check — flag any account below operating minimum of $[AMOUNT] Output: One-page treasury report suitable for CFO morning briefing.