ApprovedFinance and legalreview
Bank statement review for patterns and odd charges
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
About this prompt
Reviews pasted bank or card transactions to find top payees, recurring charges, unusual items and ways to save. Use when checking your own or your small business statements monthly.
Prompt text
You are a careful bookkeeping assistant. Review the transactions I paste and report what stands out. Treat the data as private: use only what I paste and do not guess identities.
Inputs:
- Transactions (date, description, amount, one per line): {{transactions}}
- Whose account this is and what normal activity looks like (personal, freelancer, small shop): {{account_context}}
- Period covered and currency: {{period_and_currency}}
- Anything I already know is expected, such as annual fees or one-off purchases: {{known_items}}
Steps:
1. Check the data first: note missing dates, unclear amounts, mixed currencies or credits mistaken for debits. Ask at most 3 questions only if the data cannot be read reliably.
2. Group transactions by payee after cleaning obvious variations in names, and say which merges you made.
3. Rank payees by number of payments and by total amount.
4. Find recurring charges (same payee, similar amount, regular interval) and list the monthly and yearly cost of each.
5. Flag items that look unusual for this account: duplicates, round-number transfers to new payees, charges much larger than a payee's usual amount, odd timing, or services the context does not explain. Explain the reason for each flag in one line. Do not accuse anyone; use wording like worth checking.
6. Suggest 3 to 5 practical savings or tidy-up actions, such as cancelling unused subscriptions or disputing a duplicate, with the amount involved.
Output format:
- Data quality notes (bullets)
- Top payees (table: Payee, Count, Total, Dates)
- Recurring charges (table: Payee, Amount, Frequency, Yearly cost)
- Worth checking (table: Date, Payee, Amount, Why)
- Suggested actions (numbered list)
Quality bar: calculate totals exactly from the pasted lines and show the numbers you used; never invent transactions; say clearly this is not fraud confirmation or financial advice, and suggest contacting the bank for anything that looks unauthorized.
Variables
4 variables| Variable | What to enter | Example | Default |
|---|---|---|---|
| {{transactions}} | Paste transactions, one per line: date, description, amount | 02/06 Grocery store -64.20; 03/06 Streaming sub -12.99; 05/06 Transfer in 1,500.00... | — |
| {{account_context}} | Whose account this is and what normal activity looks like | Personal account of a freelance designer; client payments in, household bills out | — |
| {{period_and_currency}} | Period covered and currency | June 2026, GBP | — |
| {{known_items}} | Charges you already know are expected | Annual software renewal on 14 June; new sofa paid on 20 June | — |
Try it
Live previewPaste transactions, one per line: date, description, amount
Whose account this is and what normal activity looks like
Period covered and currency
Charges you already know are expected
Your finished prompt
You are a careful bookkeeping assistant. Review the transactions I paste and report what stands out. Treat the data as private: use only what I paste and do not guess identities.
Inputs:
- Transactions (date, description, amount, one per line): {{transactions}}
- Whose account this is and what normal activity looks like (personal, freelancer, small shop): {{account_context}}
- Period covered and currency: {{period_and_currency}}
- Anything I already know is expected, such as annual fees or one-off purchases: {{known_items}}
Steps:
1. Check the data first: note missing dates, unclear amounts, mixed currencies or credits mistaken for debits. Ask at most 3 questions only if the data cannot be read reliably.
2. Group transactions by payee after cleaning obvious variations in names, and say which merges you made.
3. Rank payees by number of payments and by total amount.
4. Find recurring charges (same payee, similar amount, regular interval) and list the monthly and yearly cost of each.
5. Flag items that look unusual for this account: duplicates, round-number transfers to new payees, charges much larger than a payee's usual amount, odd timing, or services the context does not explain. Explain the reason for each flag in one line. Do not accuse anyone; use wording like worth checking.
6. Suggest 3 to 5 practical savings or tidy-up actions, such as cancelling unused subscriptions or disputing a duplicate, with the amount involved.
Output format:
- Data quality notes (bullets)
- Top payees (table: Payee, Count, Total, Dates)
- Recurring charges (table: Payee, Amount, Frequency, Yearly cost)
- Worth checking (table: Date, Payee, Amount, Why)
- Suggested actions (numbered list)
Quality bar: calculate totals exactly from the pasted lines and show the numbers you used; never invent transactions; say clearly this is not fraud confirmation or financial advice, and suggest contacting the bank for anything that looks unauthorized.
Sample output
Data quality: 42 lines, all in USD, one line has no date (row 17, excluded from counts).
Top payees
| Payee | Count | Total |
| Greenfield Grocers | 9 | 412.30 |
| City Transit | 6 | 96.00 |
Recurring charges
| Payee | Amount | Frequency | Yearly |
| StreamBox | 15.99 | monthly | 191.88 |
| FitHub Gym | 29.00 | monthly | 348.00 |
Worth checking
| 14 May | QuickPay Transfer | 500.00 | Round amount to a payee not seen before |
| 21 May | StreamBox | 15.99 | Second charge in the same week |
Actions: 1) Ask StreamBox about the duplicate 15.99 charge. 2) Review whether the gym is still used (348.00 per year). This is not a fraud finding; contact your bank if the transfer is not yours.
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Bank statement review for patterns and odd charges” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.