The work of investment tracking often begins long before you look at a chart. Records arrive from different institutions, cash moves between accounts and a portfolio gradually spreads across several places. Bluwhale’s connected-finance approach starts with bringing that fragmented financial picture together.
A useful overview still depends on knowing what the underlying records mean. This article follows three practical tasks: bringing information into a review, reconciling overlapping records and keeping a usable history. Together, they explain why connected information can support better conversations about goals, WhaleScore and the agent workflows available through Bluwhale.
Choose an import method for each source
A supported account connection can reduce repeated entry, while a CSV import can bring in historical records or an unsupported account. Manual entries can cover a small number of holdings or corrections. The practical choice depends on the records available and how frequently they change.
Before importing a file, inspect its headings, date format, currency fields and transaction types. Preserve the original file. A date written as 03/04 can mean different days under different conventions, and a monetary amount without a currency label leaves an important assumption unresolved.
Keep account labels and instrument identifiers consistent. Two accounts can hold the same security, and two similarly named securities can be different instruments. Your data model should preserve both the account and the asset distinction.
Why connected information matters to Bluwhale
Bluwhale’s Individuals offering brings account visibility, WhaleScore and AI agents into one experience. For someone currently assembling spreadsheets from several accounts, its central proposition is a more connected starting point for understanding money and deciding what to do next.
That proposition is different from a promise about every data format. Account connections, CSV files and manual records are general ways tracking software can receive information; the examples here do not establish that Bluwhale supports a particular import or export feature. When exploring the platform, begin with your actual accounts and the workflow available for them. Use the record checks below to understand the resulting view.
Reconcile holdings, transactions and cash
Choose a cutoff date and compare the imported result with a source statement. Check quantities and cash first, then prices and currencies. Keep differences caused by the reporting time separate from differences caused by missing or duplicated entries.
Consider a fictional overlap: January's import contains a purchase of 10 shares, and a later January–February file contains the same purchase again. Importing both as new transactions could create a false 20-share record. A useful process identifies the repeated event or gives you a reliable way to review it.
Do not deduplicate solely by amount and date. Two legitimate purchases can have the same amount on the same day. Where available, use source transaction identifiers alongside account, instrument and event details, and retain enough evidence to reverse an incorrect merge.
Connected data can also change after an initial fetch. Plaid's Investments documentation describes updates to holdings and investment transactions, including canceled records. This provider example illustrates why a tracker needs a refresh process as well as an initial import.
Preserve corrections through the next refresh
Try a small supported correction and document it. For example, change a transfer label that was interpreted as an external deposit. Refresh the connection or reimport an overlapping file, then check whether the correction remains.
Different systems handle manual adjustments differently. Some preserve an override, some prioritize the source and others provide matching rules. What matters is knowing which behavior applies, so the same issue does not silently reappear during each review.
Keep a correction log with the original record, the reason for the change and its effect. Separate a presentation label from a change to quantity or value. A renamed transaction should not unexpectedly alter the economic record.
When a balance differs, investigate its components before entering an unexplained adjustment. Otherwise, a balancing entry can conceal a missing transaction and create another difference later.
A correction has more value when it improves the next financial conversation as well as today’s total. In the connected approach Bluwhale describes, the goal is to spend less of the review reconstructing the same account story and more of it considering what the money should do.
Check exports before committing to the workflow
Download a sample export and open it outside the software. Confirm that it preserves the fields needed for your next use: accounts, instrument identifiers, quantities, dates, currencies, transaction types and relevant corrections.
A holdings snapshot answers what was recorded at one point in time. A transaction history explains events over a period. A PDF chart may help communicate results but does not replace structured records for rebuilding a portfolio elsewhere.
- Check whether the export covers the full selected date range.
- Verify how decimal separators, timezones and currencies are represented.
- Confirm whether manual entries and corrections are included.
- Review access, retention and deletion controls for connected records.
Explore Bluwhale’s portfolio tracking overview and the case for bringing bank and crypto information together. Then take your account list and first financial goal into Bluwhale for Individuals.
Is CSV always better than an account connection?
No. CSV offers a portable snapshot, while supported connections can simplify updates. Compare the available history, maintenance and reconciliation needs.
Can I delete the source file after importing?
Keep an appropriate backup until you have verified the import and your recordkeeping needs. It provides a reference if a later correction is required.