The Best Claude Prompts for Financial Controllers Who Actually Use ERP Systems

I'm pasting a trial balance export from [SAP/Oracle/NetSuite] for the period ending [MM/YYYY]. The format is [account number, account name, prior period balance, current period balance, variance]. 

For every account with a variance exceeding $[threshold], provide:
1. The percentage change from prior period
2. A plain-English explanation of what typically drives movement in that account category
3. Whether this variance pattern suggests a timing issue, a volume change, or a potential misposting
4. Which journal entry source I should check first in [T-code FBL3N / Oracle GL inquiry / NetSuite transaction search]

Sort results by absolute dollar variance, largest first. Flag anything that looks like it could be a reclassification entry that was booked to the wrong period

Here is our month-end close checklist with status updates as of [date]. Format: [task name, owner, status, due date, dependencies]. 

Identify: (1) any tasks marked complete whose dependent tasks are still open, which may indicate premature sign-off, (2) tasks that are past due and blocking downstream activities, (3) the critical path to completing the close assuming all remaining tasks are started now. 

Our ERP is [system] and our close target is day [X]. Based on the dependency chain, what is the realistic earliest completion date

I have two datasets. Dataset 1 is a bank statement export (columns: date, description, amount, reference). Dataset 2 is an SAP/Oracle/NetSuite cash receipts ledger (columns: posting date, document number, amount, clearing reference, business partner).

Match transactions between the two datasets using amount and date proximity (within 3 business days). For unmatched items, categorize them as: (a) likely timing differences where the bank posted but ERP has not yet, (b) likely timing differences where ERP posted but bank has not yet, (c) potential discrepancies requiring investigation.

For category (c), suggest the most likely cause based on the description field and amount pattern. List results in a format I can paste into our reconciliation workpaper

I'm pasting intercompany balance confirmations from [number] entities. Format per entity: [entity code, entity name, receivable balance per their books, payable balance per our books, difference].

For each entity pair with a non-zero difference: (1) calculate the net discrepancy, (2) check if the discrepancy could be explained by a foreign currency translation difference using today's rate vs. month-end rate, (3) identify if the discrepancy amount matches any common intercompany transaction types (management fees, royalties, cost allocations) that might indicate a booking timing difference, (4) suggest which entity likely has the correct balance based on the pattern of differences.

Our intercompany elimination entries are booked in [SAP company code/Oracle ledger/NetSuite subsidiary]. Flag any discrepancy over $[threshold] as requiring a formal reconciliation memo

Here is our budget vs. actual report for [cost center/department] for [period]. Format: [line item, budget amount, actual amount, variance, variance %].

For each variance exceeding [threshold or %], provide: (1) a categorization as either volume variance, rate/price variance, timing variance, or one-time/non-recurring, (2) the questions I should ask the cost center manager to confirm the root cause, (3) the specific ERP report or transaction listing I should pull to verify (use [SAP report names like S_ALR_87013611 / Oracle Financial Analyzer paths / NetSuite saved searches]).

Separate truly concerning variances from those that are simply timing or seasonality. I do not want to raise flags in the management report for items that will self-correct next month

I need to write the revenue variance section of our monthly management report. Here are the inputs:

- Prior month revenue by product line/region: [paste data]
- Current month revenue by product line/region: [paste data]
- Known factors: [e.g., "new customer onboarded in EMEA," "price increase effective mid-month," "one large deal slipped to next month"]

Write a 3-4 paragraph variance narrative that explains the month-over-month movement in plain business language. Use a waterfall structure: start with prior month, walk through each major driver (volume, price, mix, FX, one-time items), and arrive at current month. Do not use accounting jargon that a non-finance executive would need to look up

I'm pasting a list of all manual journal entries posted during [period] from [SAP T-code SM35/Oracle GL journal report/NetSuite journal entry search]. Format: [document number, posting date, entered by, amount, description, account debited, account credited].

Auditors typically test manual journals using these criteria: (a) entries posted by senior management, (b) entries posted on weekends or after business hours, (c) round-dollar entries above $[materiality threshold], (d) entries with vague descriptions like "adjustment" or "reclassification," (e) entries debiting revenue or crediting expense accounts.

Screen this list against all five criteria and flag any entries that match one or more. For each flagged entry, note which criteria it triggered and suggest what supporting documentation I should pull before the auditors ask for it

Here is our lease schedule export from [SAP RE-FX/Oracle Property Manager/NetSuite lease module or spreadsheet]. Format: [lease ID, commencement date, term months, monthly payment, discount rate, ROU asset balance, lease liability balance].

For each lease: (1) recalculate the present value of remaining lease payments using the stated discount rate and compare to the recorded liability, (2) flag any lease where the ROU asset and lease liability have diverged by more than $[threshold], which may indicate a missed reassessment or modification, (3) identify leases expiring within 90 days that may need a renewal or termination entry, (4) check if any leases appear to be short-term or low-value exceptions that might be incorrectly capitalized.

Output a summary table I can use as a working paper for the ASC 842 disclosure footnote review

Here is our monthly cost allocation output from [SAP cost center accounting/Oracle Allocations/NetSuite custom allocation journal]. Format: [source cost center, target cost center, allocation basis, allocation percentage, allocated amount].

Review the allocation results for: (1) any target cost center receiving an unusually large or small share compared to prior months (I will paste prior month data below), (2) allocation bases that may be stale (e.g., headcount-based allocations where headcount has changed significantly), (3) circular allocations where cost center A allocates to B and B allocates back to A, (4) total allocated amounts that do not equal the source pool, indicating a rounding or configuration error.

Prior month allocation data: [paste]
Current headcount by cost center: [paste if available]

I'm pasting a T&E report export from [SAP Concur integration/Oracle iExpense/NetSuite expense reports] for [period]. Format: [employee name, department, expense type, amount, date, vendor, description, approval status].

Flag the following patterns: (1) individual expenses just below our approval threshold of $[amount], especially if the same employee has multiple such entries, (2) weekend or holiday expenses that lack a business justification in the description, (3) duplicate submissions where amount, vendor, and date match across multiple reports, (4) expenses categorized as "miscellaneous" or "other" above $[amount], (5) vendors that appear only once across the entire dataset, which may indicate personal expenses or fictitious vendors.

Group findings by employee and rank by total flagged dollar amount. For each finding, note the specific expense report line so I can pull the receipt in [system]

Here is our fixed asset register export from [SAP AS01-AS03/Oracle Fixed Assets/NetSuite FAM]. Format: [asset ID, description, acquisition date, cost basis, useful life, depreciation method, accumulated depreciation, net book value, current period depreciation].

For each asset: (1) recalculate expected accumulated depreciation based on acquisition date, cost basis, useful life, and method, then compare to the recorded balance, (2) flag any asset where recorded depreciation deviates from calculated by more than $[threshold], (3) identify fully depreciated assets with a net book value of zero that are still in service, as these may need disclosure, (4) flag any assets acquired more than [X] months ago with zero accumulated depreciation, which may indicate a configuration error or suspended depreciation.

Summarize discrepancies in a table format suitable for a fixed asset reconciliation workpaper

I'm pasting a list of all entries posted to our capital expenditure accounts during [period] from [ERP system]. Format: [document number, description, amount, vendor, posting date, WBS element or project code if applicable].

Our capitalization threshold is $[amount]. Review each entry and flag: (1) items below the threshold that may have been incorrectly capitalized, (2) items that based on their description appear to be repairs or maintenance rather than capital improvements (apply the IAS 16/ASC 360 "future economic benefit" test based on the description), (3) items without a project code that may indicate ad hoc capitalization outside normal procurement, (4) items with descriptions suggesting they are recurring costs (e.g., annual license fees) that should be expensed.

Separate findings into "likely correct," "needs review," and "likely misclassified" categories