Is bank access required?
Ask: Can the application be used without linking a financial institution?
Verify: Look for an explicit manual or file-based alternative.
Record: Optional, central, or required for a specific feature.
A pre-subscription review should identify what current documentation confirms and what routine the user would need to maintain.
Ask: Can the application be used without linking a financial institution?
Verify: Look for an explicit manual or file-based alternative.
Record: Optional, central, or required for a specific feature.
Ask: Can transactions, categories, scheduled entries, and corrections be maintained directly?
Verify: Check device availability and feature dependencies.
Record: List work that remains manual even with import enabled.
Ask: Which tasks occur as activity happens, weekly, and at a period boundary?
Verify: Look for reconciliation, duplicates, category adjustments, and recovery.
Record: Describe the sequence without inventing minutes.
Ask: What data can leave, and in which format?
Verify: Check transactions, categories, notes, attachments, and scheduled items.
Record: Separate an available export from a complete migration.
Ask: When does access change?
Verify: Use current subscription, cancellation, and retention documents.
Record: Date the finding; cancellation and deletion may differ.
Ask: Can category names, records, and history move elsewhere?
Verify: Determine whether a destination interprets the export.
Record: Identify what needs manual reconstruction.
Ask: Are data use, maintenance, exports, cancellation, and deletion explained?
Verify: Prefer dated first-party sources.
Record: Mark gaps “Documentation Check Needed.”