Account records
Starting information and relevant balances form the account layer.
This profile examines information, decisions, recurring maintenance, export limits, and exit questions associated with the documented workflow. It does not evaluate personal financial results and does not provide product-account assistance.
Product facts and editorial workload assessments are labeled separately.
Not every field is mandatory in every situation.
Starting information and relevant balances form the account layer.
Dates, amounts, payees, categories, inflow or outflow status, and optional memos.
Assigned and Available category amounts, plus scheduled activity the user chooses to create.
When a user chooses Direct Import, additional financial-account information is processed as described in the current Privacy Policy, including relevant balances and transaction data.
The workflow can be maintained through manual transaction entry. Direct Import is optional, and public documentation also describes scheduled transactions and file-based import.
Imported activity can reduce typing, but it still requires review for timing, matching, categories, omissions, and duplicates.
Initial use involves creating or identifying account records, entering starting information, establishing categories, and making first assignments. Connected use adds a separate data-connection decision.
Moderate editorial assessment
Current public guidance recommends reconciling cash and credit accounts at least once a week. Reconciliation compares the application record with corresponding real-world account information.
This is a maintenance recommendation, not a statement that daily use is mandatory.
Current public documentation describes web-based plan/category and transaction-history export to CSV or TSV.
Plan/category data and transaction history have a documented web export path.
Targets and category notes are excluded, and transaction photos cannot be exported in bulk.
Before relying on an export, confirm included fields, category readability outside the application, omitted notes or planning rules, and whether the destination interprets the files.
Current documentation says access continues through the paid period and plan access ends after expiration. Resubscribing may restore access while data remains retained.
The current Privacy Policy describes retention of most account data for up to 24 months after a trial or subscription expires, subject to its stated legal, security, deletion, and anonymized-data exceptions.
| Question | YNAB category workflow | Spreadsheet workflow |
|---|---|---|
| Structure | Purpose-built accounts, categories, and planning terms | User-defined rows, columns, formulas, and labels |
| Entry | Manual, imported, scheduled, or file-based approaches documented | Manual entry or user-managed import |
| Decisions | Category assignments and adjustments remain user decisions | Planning logic and sheet structure remain user decisions |
| Accuracy work | Review and reconciliation | Rows, formulas, omissions, and duplicates need checking |
| Portability | CSV/TSV export with excluded data types | Broad file portability; formulas may not transfer cleanly |
| Subscription | Depends on current subscription terms | Depends on software and storage provider |
This comparison describes responsibility for maintaining the workflow. It does not identify a winner or predict a financial result.
Labels are editorial workload descriptions, not scores, endorsements, or predictions of financial results.
Last reviewed: October 27, 2026
Product facts were reviewed against public first-party documentation on October 27, 2026 and may change. Confirm time-sensitive behavior with the product owner.