What hidden limitations should I watch out for when importing large historical transaction volumes from a legacy system into Wave Accounting
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What hidden limitations should I watch out for when importing large historical transaction volumes from a legacy system into Wave Accounting
1 real search · 1 real-search pass
Wave Accounting import transactions CSV limitations historical transactions bulk import limits journal entries bank transactions official helpGoogle ↗
OBSERVEDInstruction
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Wave Accounting import transactions CSV limitations historical transactions bulk import limits journal entries bank transactions official help Google ↗
- Automated bookkeeping with auto-updates · support.waveapps.com
- Categorize or recategorize transactions · support.waveapps.com
- Resolve duplicate transactions imported from your bank · support.waveapps.com
- Turn automatic transaction imports on or off for individual accounts · support.waveapps.com
- Switch to Wave from a spreadsheet · support.waveapps.com
- Move Your Data Between Wave Accounts · support.waveapps.com
- Resolve differences between your Wave balances and bank balances · support.waveapps.com
- Fix an unreconciled period · support.waveapps.com