SpendScope: Spending & Budgets has a specific starting point: import Chase credit-card CSV exports, then review how much of each purchase or credit belongs to you. Its official description is narrower than a universal bank dashboard. That focus is relevant to people whose statement totals mix personal and shared spending. This first look is based on the store listing, not a test of import accuracy or budget calculations.
The important distinction is between what the card account recorded and the portion you want to analyse. Those figures can differ for an entirely ordinary reason, such as a shared meal. The app provides a way to record that distinction, but it does not change the card balance, settle a reimbursement or move money.
Based on official store information. We have not tested this app hands-on.
What it does
The described workflow begins with a Chase credit-card CSV export. Purchases and credits can be reviewed, with exact amounts, spending shares and exclusions. That means the useful record is not merely the imported row: it is the row plus a deliberate decision about attribution. Do not infer support for unrelated banks or every CSV format from the general idea of file import.
Tags and memos can organise transactions and preserve context. Monthly and category views offer ways to inspect spending, while budgets and manually recorded money sources support planning. A memo can explain why a share differs from the full amount, which may be more useful later than a number that once seemed obvious.
The listing describes offline work with a local SQLite library and optional saved-data sync through a private iCloud database. No direct bank connection is involved. This makes file handling a central part of the routine: obtaining the export, deciding which records it covers and keeping an understandable local history. We have not tested the data model, duplicate detection, sync conflicts or the result of importing overlapping files.
Before you install
Begin with a short export whose transactions you can verify against the official account record. Compare a purchase, a credit and a shared item before importing a larger history. Preserve the original CSV unchanged so you can distinguish the bank's data from your later attribution decisions. A plausible chart is not proof that signs, dates and amounts were interpreted as intended.
Choose a consistent rule for shares and exclusions. Excluding a transaction from your spending analysis does not remove the obligation from the card account. Likewise, recording only your portion of a purchase does not establish that another person has repaid the remainder. Keep those questions separate so the app's personal total is not mistaken for a statement balance or a settlement record.
Credits need context too. A refund may relate to an earlier purchase, while another credit can have a different meaning. Review the actual account description and your own records instead of assuming every negative number should affect a category identically. We have not tested how SpendScope represents each of those cases, so inspect the specific examples important to you.
Overlapping export periods are a useful question to resolve early. Importing a month twice can create a very convincing but misleading trend if duplicates are not handled as expected. We have not established the app's behaviour in that case, so test a harmless copy and keep the original files clearly labelled privately.
A monthly budget should also use the same meaning of spending as the reports you compare it with. A target based on full household purchases is not directly comparable to a history showing only your allocated shares. Define that basis before interpreting whether you are over or under a plan.
Price and access
The official description says SpendScope is free, without in-app purchases or subscriptions. It does not connect to a bank or move money. Optional iCloud sync requires an Apple Account. Confirm the current store listing and compatible devices before installation rather than extending those access terms to unrelated services or account arrangements.
The main commitment is maintaining a careful import-and-review routine. A free tool still needs to fit the source format you have and the questions you want answered. If you need automatic bank feeds, money transfers or an institution-independent import system, those capabilities are not established by this description.
Our take
SpendScope's clearest contribution is a focused distinction: the full card transaction and your own spending share need not be the same number. Exact attribution, tags and memos can make that distinction visible without requiring a bank login. For the right Chase-export workflow, a narrow scope may be an advantage because the intended source and purpose are explicit.
We have not validated import handling, arithmetic, privacy or sync reliability. Our take is to begin with a small, reversible sample and compare the results with the source statement. Keep the official card record authoritative, explain attribution decisions and inspect credits carefully. Choose it when the resulting personal view answers a real question more clearly than a spreadsheet you already maintain.
Sources
App icon from the official store listing.
