100 Best Gemini Excel Data Analysis Prompts for Banks

Direct Answer

The best Gemini prompts for Excel data analysis for banks are designed to extract actionable insights from banking data in Excel, verify data quality, and support risk, compliance, and operations decisions. Each prompt is role-based, context-rich, and specifies outputs and constraints to ensure repeatable results, with placeholders for bank data. Use them as-is or tailor placeholders to your dataset.

Introduction

This page is a practical prompt library for Excel data analysis in banking contexts. It provides 100 copy-ready Gemini prompts you can run on bank datasets in Excel to generate insights, dashboards, and reports.

The prompts are written for bank data analysts, risk managers, compliance teams, and operations staff who want repeatable, auditable Excel-based analysis without coding.

How to Use These Gemini Prompts

• Replace placeholders like [dataset], [role], and [constraints] with your bank's actual data and requirements.
• Add constraints such as time range, data freshness, and regulatory needs to tailor results to your environment.
• Request outputs in Excel-friendly formats like tables, CSV snippets, or pivot-ready layouts.
• Verify outputs by cross-checking with source data and running a small sample before full deployment.
• Iterate by merging prompts to build multi-step analyses, ensuring outputs are auditable and reproducible.

100 Best Gemini Excel Data Analysis Prompts for Banks

1. Data quality audit kickoff: Role: Data analyst for a bank. Task: Assess data quality in the provided Excel workbook. Context: The dataset contains customer, transaction, and account tables with key fields. Output format: a data quality report in bullets and a summary table. Constraints: identify missing values, duplicates, outliers, and inconsistent data types. Provide remediation steps and a data quality score for each table.
2. Transaction anomaly detector: Role: Fraud analyst in a bank. Task: Scan the Excel dataset for anomalous transactions using statistical thresholds. Context: Transaction table includes date, amount, merchant, and location. Output: a list of anomalies with reasons and suggested investigations. Constraints: flag high-amount, unusual locations, or rapid repeat transactions. Include a three-bullet summary per anomaly.
3. Customer risk segmentation: Role: Risk analyst. Task: Segment customers into risk tiers based on transaction velocity, balance volatility, and credit utilization. Context: Use a compact dataset with customer_id, daily_balance, mv_ratio, and credit_limit. Output: a tiered list with rationale and recommended actions for each segment. Constraints: provide at least three segments and ensure reproducibility with a seed value.
4. Mobile app engagement mapping: Role: Product analyst. Task: Map customer engagement indicators to banking app usage. Context: Include fields for customer_id, login_count, feature_active, and churn_risk. Output: a heatmap-like table in Excel-friendly format and a brief interpretation. Constraints: use conditional formatting hints and provide a downloadable CSV snippet.
5. Deposit trend forecasting: Role: Treasury analyst. Task: Forecast deposits for the next quarter using historical monthly balances. Context: Columns: month, deposits, rate, promo_flag. Output: forecast values with confidence interval and a short narrative. Constraints: use a simple ARIMA-like approach described in steps and present results in an Excel-friendly table.
6. Credit utilization dashboard: Role: Credit risk manager. Task: Create a compact dashboard plan to monitor credit utilization across customer segments. Context: Tables: accounts, credit_limit, outstanding_balance, utilization_rate. Output: an outline of chart choices, filters, and computed fields. Constraints: include at least three visualizations and an interactive slicer plan.
7. KYC completeness check: Role: Compliance analyst. Task: Verify KYC data completeness and flag gaps in the Excel dataset. Context: Fields: customer_id, id_verification, address_verification, risk_score. Output: a checklist of missing verifications and recommended remediation steps. Constraints: produce a prioritized remediation order.
8. AML screening summary: Role: Compliance officer. Task: Summarize AML screening results from the dataset. Context: Fields: customer_id, screen_result, last_checked, risk_label. Output: a compact summary with counts by risk_label and suggested follow-up actions.
9. Fraud hotspot analysis: Role: Fraud prevention analyst. Task: Identify transaction hotspots by geography and merchant category. Context: Columns: geozone, merchant_category, transaction_amount. Output: ranked hotspot list with metric explanations and suggested controls. Constraints: provide top five hotspots.
10. Chargeback pattern finder: Role: Operations manager. Task: Detect recurring chargeback patterns in card transactions. Context: Fields: card_id, date, merchant, chargeback_flag. Output: a report with recurring patterns, impact estimates, and remedy recommendations.
11. Cost-to-income drilldown: Role: Finance analyst. Task: Compute cost-to-income ratio by department from payroll and expense data in Excel. Context: Tables: departments, payroll, expenses. Output: a pivotable summary with trends and a narrative interpretation. Constraints: show year-over-year changes.
12. Product holding period: Role: Product manager. Task: Analyze average holding period for customer products. Context: Tables: product_id, customer_id, hold_days, activation_date. Output: distribution stats and a recommended action plan for promotions.
13. Deposit churn insights: Role: Retail banking analyst. Task: Identify drivers of deposit churn using customer attributes and balance changes. Context: Fields: customer_id, churn_flag, balance, tenure, product_type. Output: a causal-ish set of factors with recommended retention actions.
14. Loan portfolio health: Role: Portfolio manager. Task: Assess loan portfolio health by aging buckets and delinquency rate. Context: Tables: loan_id, status, due_date, balance, PD. Output: a risk heatmap and action plan for high-risk cohorts.
15. Interest rate sensitivity: Role: Actuary. Task: Model sensitivity of net interest income to rate changes. Context: Fields: loan_rate, deposit_rate, volume, rate_change_scenario. Output: table of NII impact under scenarios and a short interpretation.
16. ATM cash optimization: Role: Operations planner. Task: Optimize cash distribution across ATMs using historical withdrawal data. Context: Columns: atm_id, date, withdrawals, cash_inventory. Output: recommended top-up schedule and a summary KPI list.
17. Vendor spend audit: Role: Procurement analyst. Task: Audit vendor payments for banking operations. Context: Fields: vendor_id, payment_date, amount, category. Output: discrepancy report and recommended controls in a clear Excel table.
18. Fraud risk scoring: Role: Fraud risk modeller. Task: Build a lightweight risk score for each customer based on transaction features. Context: customer_id, features: [freq, avg_amount, orig_country, merchant_risk]. Output: per-customer score with interpretation and cautions.
19. Exposure concentration: Role: Risk manager. Task: Compute concentration risk across large exposures. Context: Table: exposures, borrower, amount, industry. Output: concentration report with Gini-like dispersion measure and flags.
20. Regulatory reporting pack: Role: Reporting analyst. Task: Prepare a compact Excel-ready regulatory pack from the dataset. Context: Required fields: customer_id, report_date, metric, value. Output: a ready-to-export report with a summary narrative.
21. Liquidity gap scan: Role: Treasury analyst. Task: Identify liquidity gaps using historical inflows and outflows. Context: Tables: inflows, outflows, date. Output: gap table with recommended funding actions.
22. Budget vs actual: Role: Controller. Task: Compare budget and actuals by department. Context: Fields: department, budget, actuals, variance, date. Output: variance report and a graphical summary.
23. Credit spread analyzer: Role: Risk analyst. Task: Analyze credit spread movements by product. Context: Fields: product, spread, date, rating. Output: trend report and a set of hedging ideas.
24. Customer profitability map: Role: Product controller. Task: Measure profitability by customer segment. Context: Tables: segment, revenue, cost, margin. Output: profitability chart plan and segment-level actions.
25. Operational efficiency check: Role: Ops analyst. Task: Assess process efficiency using time-to-close metrics. Context: Fields: process_id, start_date, end_date, status. Output: efficiency score and bottleneck list.
26. Fraud detection rules: Role: Fraud analyst. Task: Create a set of simple Excel-based fraud detection rules. Context: Columns: amount, frequency, geolocation, merchant. Output: rule table with triggers, thresholds, and expected outcomes.
27. Credit renewal readiness: Role: Credit ops. Task: Assess renewal readiness for revolving lines. Context: Fields: customer_id, limit, utilization, renewal_date. Output: renewal readiness score and recommended actions.
28. Spend trend analysis: Role: Financial analyst. Task: Analyze merchant category spend trends. Context: Fields: merchant_category, amount, date. Output: trend insights and a summary in bullet points.
29. Product uptake heatmap: Role: Marketing analyst. Task: Visualize product uptake by region. Context: Fields: region, product, activations, date. Output: heatmap plan and region-level actions.
30. Fraud investigation log: Role: Investigator. Task: Create a structured investigation log for suspected fraud cases. Context: Fields: case_id, verdict, evidence, timeline. Output: template with status tracker and links to anomalies.
31. Compliance risk score: Role: Compliance analyst. Task: Compute compliance risk score per customer. Context: Fields: customer_id, rules_passed, flags, risk_weight. Output: risk score and mitigations.
32. Loan delinquency forecast: Role: Credit risk analyst. Task: Forecast loan delinquencies for next quarter. Context: Fields: loan_id, status, balance, days_past_due. Output: forecast list with confidence and actions.
33. Customer lifetime value: Role: Marketing analyst. Task: Estimate CLV from transaction history. Context: Tables: customer_id, revenue, cost, churn. Output: CLV per cohort and retention tips.
34. Product risk scoring: Role: Risk manager. Task: Score products by risk level using historical outcomes. Context: Fields: product_id, loss_events, exposure, category. Output: risk tiering with monitoring plan.
35. Geography risk map: Role: Risk analyst. Task: Map risk by region using customer density and loss data. Context: Fields: region, customers, losses. Output: regional risk ranking and alert thresholds.
36. Operational backlog: Role: Ops lead. Task: Identify backlogs in processing queues. Context: Fields: queue_id, items_waiting, average_handle. Output: prioritized backlog fix list.
37. Settlement timing check: Role: treasury ops. Task: Check settlement timing against SLA. Context: Fields: settlement_id, scheduled, actual, delay. Output: SLA compliance table and alerts.
38. Account aging report: Role: Finance clerk. Task: Age accounts receivable/ payable. Context: Tables: account_id, due_date, amount, status. Output: aging buckets and recommendations.
39. Tax compliance prep: Role: Tax analyst. Task: Prepare tax-related figures from banking data. Context: Fields: tax_code, expense, deduction, date. Output: ready-to-file figures and notes.
40. Segmentation by tenure: Role: CRM analyst. Task: Segment customers by tenure for campaigns. Context: Fields: customer_id, tenure_days, mrr, churn_risk. Output: tenure-based segments and recommended offers.
41. Cost center performance: Role: Finance manager. Task: Compare cost centers on key metrics. Context: Tables: cost_center, revenue, cost, profit. Output: performance dashboard outline.
42. Recency analysis: Role: Marketing analyst. Task: Run RFM recency analysis on customers. Context: Fields: customer_id, last_purchase, frequency, monetary. Output: RFM groups and recommended actions.
43. Regulatory delta tracker: Role: Compliance lead. Task: Track changes in regulatory reporting requirements. Context: Fields: regulation_id, change_date, impact, status. Output: delta report and action items.
44. Cash flow projection: Role: Treasury analyst. Task: Project monthly cash flow with scenarios. Context: Fields: month, inflows, outflows, scenario. Output: forecast table and qualitative notes.
45. Product profitability by channel: Role: Product controller. Task: Compare profitability by channel for key products. Context: Fields: channel, product, revenue, cost. Output: channel profitability table and recommendations.
46. Inventory mismatch check: Role: Ops accountant. Task: Find inventory data mismatches in Excel sheets. Context: Fields: item_id, forecast_qty, actual_qty, variance. Output: mismatch report and reconciliation steps.
47. Pricing impact analysis: Role: Pricing analyst. Task: Assess pricing changes on demand. Context: Fields: product, price, demand, promo. Output: impact table and elasticity notes.
48. Liquidity stress test: Role: Treasury risk lead. Task: Run a liquidity stress test in Excel. Context: Fields: scenario, inflows, outflows, liquidity_ratio. Output: stress results and recommended buffers.
49. Branch performance score: Role: Store operations manager. Task: Score branches by performance metrics. Context: Fields: branch_id, visits, loans, deposits. Output: branch scorecard and improvement plan.
50. Compliance checklist: Role: Compliance officer. Task: Generate a compliance checklist from dataset fields. Context: Fields: regulation, requirement, status. Output: checklist with remediation steps and due dates.
51. Customer attrition drivers: Role: CRM specialist. Task: Identify drivers of customer attrition. Context: Fields: customer_id, churn, tenure, product_holdings. Output: driver list with actions to reduce churn.
52. Fraud case triage: Role: Analyst. Task: Triage fraud alerts into cases with severity. Context: Fields: alert_id, severity, evidence, status. Output: triage log and recommended next steps.
53. Data lineage tracker: Role: Data governance. Task: Create data lineage for key banking metrics. Context: Tables: source, transform, target. Output: lineage diagram description in text and remediation tips.
54. Expense forecast by department: Role: FP&A analyst. Task: Forecast expenses by department with confidence intervals. Context: Fields: department, month, forecast, confidence. Output: table plus notes.
55. Customer touchpoint map: Role: CX analyst. Task: Map touchpoints affecting retention. Context: Fields: cust_id, touchpoint, date, outcome. Output: touchpoint matrix and recommendations.
56. Product cross-sell scoring: Role: Sales strategist. Task: Score cross-sell potential by customer segment. Context: Fields: segment, product, cross_sell_score. Output: ranked list and suggested offers.
57. Regulatory data pack: Role: Compliance analyst. Task: Assemble regulatory data pack from sheets. Context: Fields: item, value, date. Output: ready-to-submit Excel pack and notes.
58. Payment timeline optimization: Role: Payments ops. Task: Optimize daily payment settlement timeline. Context: Fields: payment_id, submitted, settled, delay. Output: schedule plan and KPI targets.
59. Credit limit optimization: Role: Credit ops. Task: Propose dynamic credit limit rules. Context: Fields: customer_id, balance, utilization, history. Output: limit rules and expected outcomes.
60. Customer journey analysis: Role: CX researcher. Task: Analyze end-to-end customer journey from onboarding to activity. Context: Fields: step, timestamp, action, outcome. Output: journey map and improvement ideas.
61. Withdrawal pattern insights: Role: Branch analyst. Task: Analyze ATM withdrawal patterns by hour. Context: Fields: atm_id, hour, withdrawals. Output: hourly pattern table and staffing tips.
62. Vendor risk scoring: Role: Procurement risk lead. Task: Score vendors by risk indicators. Context: Fields: vendor_id, compliance, performance, spend. Output: risk tiered vendor list.
63. Interest margin analysis: Role: Banking analyst. Task: Assess net interest margin by product. Context: Fields: product, rate, volume, margin. Output: margin table and trend notes.
64. Product lifecycle heatmap: Role: Product owner. Task: Visualize product lifecycle stages across products. Context: Fields: product, stage, date. Output: lifecycle heatmap and actions.
65. Account remediation plan: Role: Support analyst. Task: Propose remediation actions for aging accounts. Context: Fields: account_id, status, due_date. Output: remediation list and owners.
66. Campaign ROI calculator: Role: Marketing analyst. Task: Calculate ROI for campaigns with Excel data. Context: Fields: campaign_id, spend, revenue, period. Output: ROI table and interpretation.
67. Loan portfolio concentration: Role: Credit risk manager. Task: Assess concentration in loan portfolios. Context: Fields: loan_id, borrower, amount, sector. Output: concentration metrics and diversification plan.
68. Product defect tracking: Role: Quality control. Task: Track product-related defects in financial apps. Context: Fields: defect_id, severity, status, date. Output: defect log and resolution plan.
69. Cash withdrawal forecast: Role: Branch ops. Task: Forecast cash needs by branch. Context: Fields: branch_id, day, withdrawals, cash_on_hand. Output: forecast and replenishment plan.
70. Risk appetite dashboard: Role: CRO. Task: Build a risk appetite dashboard outline. Context: Fields: risk_metric, threshold, actual. Output: dashboard structure and alert rules.
71. Fraud caseload prioritization: Role: Fraud team lead. Task: Prioritize cases by impact and likelihood. Context: Fields: case_id, impact, likelihood, status. Output: prioritization list and handling tips.
72. Data quality ruleset: Role: Data governance. Task: Define a reusable data quality ruleset for banking data. Context: Tables: all, rules: completeness, accuracy, timeliness. Output: rules table and examples.
73. Expense anomaly detector: Role: Finance auditor. Task: Detect expense anomalies in vendor expenses. Context: Fields: vendor_id, amount, date, category. Output: anomalies with justification and fixes.
74. Customer retention plan: Role: CRM manager. Task: Propose retention actions based on churn signals. Context: Fields: customer_id, churn_risk, tenure, last_purchase. Output: action plan with owners.
75. Delinquency root cause: Role: Credit risk. Task: Identify root causes for delinquencies. Context: Fields: loan_id, reasons, days_past_due, income. Output: root cause list and remediation ideas.
76. Regulatory audit trail: Role: Compliance auditor. Task: Create an audit trail for data changes. Context: Fields: change_id, user, timestamp, change_type. Output: audit log plan and sample entries.
77. Channel mix analysis: Role: Strategy analyst. Task: Analyze channel mix for deposits. Context: Fields: channel, deposits, date. Output: channel mix table and optimization suggestions.
78. Recovery forecast: Role: Credit operations. Task: Forecast recoveries on charged-off accounts. Context: Fields: account_id, expected_recovery, date. Output: recovery schedule and confidence notes.
79. Credit product comparison: Role: Product analyst. Task: Compare credit card products by key metrics. Context: Fields: product, annual_fee, APR, approval_rate. Output: comparison table and recommendations.
80. Liquidity coverage ratio: Role: Treasury risk. Task: Calculate LCR from cash flow data. Context: Fields: date, inflows, outflows, liquid_assets. Output: LCR value and interpretation.
81. Remittance route map: Role: Payments planner. Task: Map remittance routes and costs. Context: Fields: route, cost, volume, date. Output: route map and optimization tips.
82. Forecast accuracy review: Role: FP&A lead. Task: Review forecast accuracy by period. Context: Fields: period, forecast, actual, variance. Output: accuracy score and improvement steps.
83. Portfolio diversification: Role: Portfolio manager. Task: Assess diversification across borrowers. Context: Fields: borrower, exposure, sector. Output: diversification score and rebalancing plan.
84. Data dictionary generator: Role: Data steward. Task: Generate a dictionary for bank data fields. Context: Tables: all, fields: name, type, description, constraints. Output: dictionary with examples.
85. Branch footfall analysis: Role: Ops analytics. Task: Analyze branch footfall vs sales. Context: Fields: branch_id, date, footfall, sales. Output: correlation insights and suggestions.
86. Product launch readiness: Role: Project manager. Task: Assess readiness of a new product launch. Context: Fields: milestone, status, date, risk. Output: readiness score and action plan.
87. Cost recovery planning: Role: Finance controller. Task: Plan cost recovery for a financed project. Context: Fields: project, cost, recovery_rate, timeline. Output: cost recovery schedule.
88. Alerts and thresholds: Role: Analytics engineer. Task: Define alerts for critical metrics. Context: Fields: metric, threshold, severity, contact. Output: alert rules and sample notifications.
89. Customer segmentation by product: Role: Marketing analyst. Task: Segment customers by product holdings. Context: Fields: product, customer_count, revenue. Output: segment table and marketing actions.
90. Regulatory impact simulation: Role: Compliance strategist. Task: Simulate regulatory changes on metrics. Context: Fields: regulation, impact, period. Output: impact table and mitigation options.
91. Data smoothing plan: Role: Data analyst. Task: Apply smoothing to noisy time series data. Context: Fields: date, value, window. Output: smoothed series and notes.
92. Fraud response playbook: Role: Fraud ops. Task: Create a response playbook for detected fraud. Context: Fields: scenario, action, escalation, owner. Output: step-by-step playbook.
93. Receivable timing model: Role: AR analyst. Task: Model receivable timing across customers. Context: Fields: customer_id, due_date, amount, terms. Output: timing forecast and actions.
94. Credit limit utilization drill: Role: Credit risk. Task: Drill utilization by customer segment. Context: Fields: segment, utilization, limit. Output: utilization heatmap and alerts.
95. Expense categorization rule: Role: Controller. Task: Create rules to categorize expenses in Excel. Context: Fields: expense_id, amount, category, date. Output: categorization rules and examples.
96. Regulatory appendix builder: Role: Compliance officer. Task: Build an appendix for regulatory submissions. Context: Fields: item, description, evidence. Output: ready-to-submit appendix.
97. Customer scorable model: Role: Analytics lead. Task: Build a simple scoring model for customer propensity. Context: Fields: customer_id, features, label. Output: scoring formula and interpretation notes.
98. Payments reconciliation: Role: Payments specialist. Task: Reconcile transaction records across systems in Excel. Context: Fields: tx_id, amount_source, amount_target, status. Output: reconciliation table and discrepancy guide.
99. Product return analytics: Role: Ops analyst. Task: Analyze product returns and impact on revenue. Context: Fields: product, return_rate, amount, date. Output: insights and recommended fixes.
100. Scenario planning library: Role: Strategy planner. Task: Build scenario plans for macro conditions affecting banking metrics. Context: Fields: scenario_name, assumptions, impact. Output: a library of scenario summaries and action hints.

Best Practices

• Keep prompts anchored to a banking objective (risk, compliance, or operations) and test on a small subset first.
• Standardize field names and data types across prompts to improve reusability and reduce context drift.
• Document assumptions and provide versioned data sources to enable audit trails.
• Use explicit output formats (tables, bullet lists, or CSV snippets) to simplify downstream tooling.
• Regularly review prompts to align with evolving Gemini capabilities and banking regulations.

Common Mistakes to Avoid

• Using vague goals like analyze the data without specifying outputs or constraints.
• Omitting placeholders or assuming missing fields, which leads to errors in execution.
• Not specifying data quality or privacy constraints, risking incomplete or unsafe outputs.
• Overloading prompts with too many tasks, causing unclear results.
• Relying on a single prompt for multiple complex analyses without breaking into steps.

FAQ

What are Gemini prompts for Excel data analysis in banks?

Gemini prompts are structured tasks designed to run in Gemini to analyze banking data in Excel, delivering defined outputs such as reports, dashboards, and insights.

How do I adapt prompts to my bank dataset?

Replace placeholders like [dataset], [department], and [date] with your bank's actual worksheet names, columns, and time ranges.

Can prompts create dashboards in Excel?

Yes. Many prompts specify dashboard outlines, charts, and slicers that can be built directly in Excel.

How do I ensure outputs are auditable?

Include outputs that reference source fields, add data quality checks, and share a reproducible seed and version for data.

Are these prompts suitable for risk teams?

Yes. There are prompts focused on credit risk, AML, KYC, and liquidity that deliver risk metrics, scores, and action plans.

What formats do prompts return?

Prompts can return tables, CSV snippets, pivot-ready layouts, and short narrative interpretations.