SavePoint Troubleshooting
Even great software hits the occasional snag, and most fixes are quicker than you would expect. This guide gathers the most common SavePoint issues alongside clear solutions, plus performance tips to keep the app running smoothly as your data grows. If you are still stuck, we show you the fastest ways to reach a real person who can help. Think of it as the page that gets you unstuck and back to managing your money.
Common solutions to frequently encountered issues, performance optimization tips, and maintenance procedures to ensure SavePoint operates smoothly and efficiently for your financial management needs.
Quick solutions to the most frequently reported issues, organized by feature area for fast problem resolution.
💻 Installation & Startup Issues
- Microsoft Edge Blocks Download: If you are using Microsoft Edge, you may see a warning that says "SavePoint isn't commonly downloaded." The downloaded file may appear grayed out or unclickable. In the Edge Downloads panel (top right of the browser), click the three-dot menu (...) next to the download, click "Keep", then click "Keep anyway" on the confirmation prompt. If this does not work, you can temporarily disable SmartScreen for Edge in Windows Security under App & browser control. Remember to turn it back on after installing
- Windows Defender SmartScreen Blocks Installer: If you see a blue "Windows protected your PC" message when running the installer, click "More info" then click "Run anyway" to proceed. This is standard behavior for desktop applications distributed outside of the Microsoft Store. The application is safe to install and run
- Antivirus Blocks or Quarantines SavePoint: Some antivirus programs (Norton, McAfee, Bitdefender, Avast, etc.) may flag SavePoint during or after installation. This is common for desktop applications distributed outside of platform app stores. Check your antivirus notifications or quarantine section, restore the file if it was quarantined, and add SavePoint's installation folder to your antivirus exclusion/whitelist. The typical Windows path is
C:\Users\[YourUsername]\AppData\Local\Programs\SavePoint\. On macOS, add/Applications/SavePoint.app. SavePoint runs entirely offline and does not execute external code, so whitelisting it poses minimal security risk - macOS Won't Open SavePoint ("App is damaged" or "Cannot be opened"): macOS Gatekeeper may block applications downloaded outside the Mac App Store. Open Terminal (Finder → Applications → Utilities → Terminal), paste the command
xattr -cr /Applications/SavePoint.appand press Enter. Close Terminal and try opening SavePoint again. This only needs to be done once. See the macOS Installation section for full details - SavePoint Crashes on First Launch: If SavePoint crashes immediately after installation, try running the application as administrator (Windows: right-click → Run as Administrator). If the problem persists, check that your antivirus is not interfering in real-time by temporarily disabling it and trying again. Ensure your system meets the minimum requirements and that the installation completed fully without errors
🔄 Data & Import Issues
- CSV Import Failures: When CSV imports fail, first verify the file is valid by opening it in Excel or Google Sheets. If it won't open there, SavePoint can't import it either. Next, check that your column mapping is correct during the import wizard. The Date column in your CSV should map to SavePoint's Date field, Amount to Amount, Description to Description, etc. If dates aren't importing correctly, verify your date format in Settings (Settings → Preferences → Date Format) matches your CSV dates. Banks use different formats like MM/DD/YYYY (US), DD/MM/YYYY (UK/EU), or YYYY-MM-DD (ISO). SavePoint expects exactly one header row followed by data rows, so remove any extra header rows your bank may have added. Finally, ensure amounts in your CSV are numeric only (123.45) without currency symbols ($123.45) or text. SavePoint may have issues parsing amounts with symbols in some cases.
- Missing Transactions: If transactions seem to have disappeared, the most common cause is active filters on the Transactions page. Check if your date range filter is set to a specific month like "January 2025". You won't see February transactions until you clear or expand the date range. Verify the Account filter dropdown isn't set to a specific account when you're trying to view transactions from all accounts. Similarly, if the Category filter is set to "Groceries", you'll only see grocery transactions. To reset and see all transactions, set Account filter to "All Accounts", Category filter to "All Categories", and clear any custom date range. Filter persistence means these settings remain active even after closing and reopening SavePoint, which often causes confusion.
- Duplicate Transactions: To find and remove duplicate transactions, use the Transactions page filters to narrow your search. Filter by the date range and amount range where you suspect duplicates exist, then manually review the filtered results. When you identify duplicates, enable the checkboxes in the leftmost column, select the duplicate transactions you want to remove, and click the "Delete Selected" button that appears. Always create a backup before bulk deleting (Settings → Data Management → Create Backup). If you accidentally delete legitimate transactions, you can restore from backup. To prevent duplicates, avoid importing the same CSV file twice, as SavePoint doesn't track which files have been previously imported. The duplicate detection during import helps but isn't foolproof, especially for identical transactions on the same day.
- Incorrect Categorization: When transactions are categorized incorrectly, first review your merchant mapping patterns at Settings → Merchant Mapping Tab to see if an overly broad pattern is causing the issue. For example, if your pattern "store" matches both "GROCERY STORE" and "DEPARTMENT STORE" incorrectly, make it more specific like "grocery store" instead. Check your categorization priority setting (Settings → Merchant Mapping → Priority). If set to Pattern-First, patterns override your manual categorization. If set to Historical Override (default), your manual changes should stick. Also verify that you haven't manually categorized that specific merchant incorrectly in the past, as Historical Override mode remembers those choices. For immediate fixes, enable Edit Mode on the Transactions page, change the category dropdown for affected transactions, and save your changes.
📊 Reports & Charts Issues
- Charts Not Loading or Show "No Data": When Dashboard charts display "No Data" or fail to load, first verify you have transactions in the selected date range. The Dashboard defaults to "This Month", so if you haven't entered any transactions yet this month, charts will be empty. Try changing the Dashboard date range dropdown to "Last 12 Months" or "All Time" to see if data appears. For category-specific charts (like Spending by Category), ensure your transactions have categories assigned. Uncategorized transactions don't appear in category charts. If one specific chart fails while others load successfully, the issue may be specific to that chart type. Try refreshing the page or restarting SavePoint. Charts requiring multiple accounts or specific data types may not render until you have sufficient data configured.
- CSV Export Failures: Export failures typically occur due to insufficient disk space, permission issues, or file locks. Check your available disk space before exporting. Exports need free space to write CSV files, especially for large transaction sets. Try exporting to a different location like your Desktop instead of Documents folder to rule out permission issues. If you previously opened an exported CSV file in Excel, close Excel before exporting again. Windows can't overwrite files that are currently open. For persistent permission errors, try running SavePoint as administrator (right-click SavePoint → Run as Administrator) to ensure write permissions. Very large exports (10,000+ transactions) may timeout on slower computers. Consider exporting smaller date ranges in multiple segments.
- Missing Data in Reports: When expected data doesn't appear in reports, first check transaction dates carefully. A transaction dated December 31 won't appear in a January report. Verify your transactions have correct categories assigned, as "Uncategorized" transactions are excluded from category-based reports and analyses. Some reports apply automatic account filters. For example, investment reports may only show Investment account types while excluding Checking and Savings. Check if accounts are archived or closed, as some reports exclude inactive accounts by default. Finally, verify the report's date range matches your expectations. Reports showing "This Month" won't include last month's transactions even if you just entered them.
- Theme/Display Issues: If you encounter visual problems with a specific theme, switch to a different theme temporarily via Settings → Preferences → Theme and select an alternative. This helps determine if the issue is theme-specific or affects the entire application. If a particular theme is broken or displaying incorrectly, continue using a working theme and report the bug to support with details about which theme caused issues. After changing themes, restart SavePoint if the display doesn't immediately update. Theme changes sometimes require a restart to fully apply. Check whether the issue affects only specific charts/pages or the entire application, as this information helps troubleshoot whether it's a theme problem or a broader display issue.
Security & Access Issues
- Forgot Master Password: If you've forgotten your master password, click "Forgot Password?" on the login screen and answer the security questions you configured during password setup. Security questions are the ONLY way to recover access if you forget your password. There is no backdoor or master key. If you didn't configure security questions or you've forgotten the answers to your security questions, your data is permanently inaccessible with absolutely no recovery option. This is by design for security. The cryptographic hashing means even the SavePoint team cannot recover your password. To prevent this situation, document your password and security question answers in a secure location like a password manager or physical safe stored off-site. Consider this documentation as important as the data itself, because without it, your financial data could be permanently lost.
- Auto-Lock Not Working: Auto-lock requires master password protection to be enabled, so first verify you have a master password set (Settings → Security → Master Password). Check that auto-lock is actually enabled and has a timeout configured by going to Settings → Security → Auto-Lock and ensuring the toggle is on and you've selected a timeout period (5, 10, 15, or 30 minutes). Test the feature by waiting for the timeout period. Note that mouse movement or keyboard input resets the timer, so if your 5-minute timeout hasn't triggered, try moving your mouse at the 4-minute mark to verify the timer is working. Be aware that computer sleep may bypass auto-lock depending on your operating system settings. Configure your computer to require password on wake for additional security. Auto-lock only works when SavePoint is running and visible, not when minimized or if your computer goes to sleep.
- Database Encryption Issues: If you're having trouble accessing an encrypted database, first verify you're entering the encryption key correctly. Encryption keys are case-sensitive, so "MyKey" and "mykey" are different keys. If you've lost your encryption key, understand that there is no recovery option. Encrypted databases are permanently inaccessible without the correct key, even if you have the database file. When initially encrypting an existing database, if the encryption process fails, create a backup of your unencrypted database first before retrying, so you can restore from backup if the encryption fails again. Remember that backup files of encrypted databases require the same encryption key as the original database. You can't decrypt backup files without the key, so document your encryption key in a secure location separate from your database and backups.
- Multi-Database Management: SavePoint allows multiple database files, but each database is completely separate with no shared data between files. Transactions, accounts, and settings in one database don't appear in another. To open a specific database, use File → Open Database and browse to your .db file. If you open the wrong database accidentally, simply close SavePoint and open the correct file. To avoid confusion between databases, name your database files clearly with descriptive names like "JohnSmith-Personal.db" for personal finances and "JohnSmith-Business.db" for business finances. Some users maintain separate databases for different purposes (personal vs. business, or one per family member), and clear naming prevents opening the wrong database and entering transactions in the incorrect file. Note only one database can be used at a time.
🔑 License & Authentication Issues
- Program Won't Launch - Not Activated: If SavePoint won't start or displays an activation message, you need to activate your license. Open SavePoint and locate your unique Hardware ID (displayed in the licensor notification window in the top right part of the screen). Visit savepointfinance.com and navigate to the license redemption page. Enter your Hardware ID to generate your unique activation key. Copy the activation key and paste it into SavePoint to complete activation. The full process is also demonstrated in our video tutorial
- License Invalid After Hardware Change: If you've upgraded your computer (new motherboard, CPU, or built a new PC) and your license no longer works, this is expected behavior as licenses are tied to your hardware configuration. Each user is entitled to one hardware replacement every two years to account for computer upgrades or new systems. Contact support through the website with your original purchase email and new Hardware ID, and our team will issue a replacement license key
- Multiple Computers: Each SavePoint purchase includes two licenses, allowing you to use the software on multiple computers (such as home and work, or desktop and laptop). If you need additional licenses beyond the two included, contact SavePoint support to discuss licensing options and volume pricing if needed
- Hardware ID Not Displaying: If you can't locate your Hardware ID, ensure you're running the latest version of SavePoint. The Hardware ID appears in the licensor notification window in the top right part of the screen, or in the activation prompt on first launch. If still not visible, try running SavePoint as administrator or contact support for assistance
- Activation Key Not Working: Verify you've copied the complete activation key without extra spaces. Ensure the key was generated for the correct Hardware ID shown in your SavePoint installation. Keys are case-sensitive and must match exactly. If problems persist, generate a fresh key from the website or contact support
⚡ Performance Issues
- Transactions Page Loading Slowly (5+ seconds): If the Transactions page takes 5 or more seconds to load, you likely have over 1,000 transactions and should enable pagination. Go to Settings → Preferences → Transaction Pagination, enable the feature, and set page size to 100 transactions per page. This immediately improves load time by 50-90% because the page only renders 100 transactions instead of loading all 5,000+ at once. If the page is still slow after enabling pagination, try reducing the page size to 50 transactions per page. This provides even faster loading at the expense of more frequent page navigation. Pagination becomes essential once you exceed 5,000 transactions, as the page may freeze or crash without it on some computers.
- Dashboard Slow or Freezing: Dashboard performance degrades when too many charts are enabled or when displaying data across very long time periods. Access Dashboard settings by clicking the gear icon and uncheck any charts you don't regularly review. Displaying 8 charts loads significantly faster than rendering 15 charts. Change the Dashboard date range from "All Time" to "Last 12 Months" or "Last 6 Months" to reduce the amount of data each chart must process. If the Dashboard remains sluggish after viewing multiple charts or changing date ranges frequently, close and reopen SavePoint to clear accumulated chart memory cache. Some users find that disabling 5-7 unused charts and limiting the date range to 6 months makes the Dashboard responsive even with 10+ years of financial data.
- Application Using Too Much Memory: High memory usage typically results from prolonged sessions with extensive chart viewing or large transaction datasets. The simplest solution is restarting SavePoint, which clears accumulated memory from charts and database operations. Close other resource-intensive applications like web browsers with dozens of tabs to free system memory for SavePoint. If you have 10,000+ transactions and haven't enabled pagination, do so immediately as described above. Pagination significantly reduces memory usage on the Transactions page. Check memory usage in Windows Task Manager (Ctrl+Shift+Esc → Processes tab → find SavePoint). If SavePoint is using over 1GB of RAM, a restart is recommended. Memory usage over 1.5GB suggests pagination isn't enabled or you have an unusual number of charts/operations running simultaneously.
- CSV Export Taking Long Time or Failing: Large CSV exports naturally require processing time. Exporting 5,000+ transactions typically takes 10-30 seconds, while 20,000+ transactions may take 45-60 seconds on slower computers. This is normal and unavoidable for large datasets. Close other applications to free system resources and ensure adequate disk space is available. You need free space at least equal to the export file size. Don't click the export button multiple times if the export seems slow. Multiple clicks trigger multiple concurrent exports which compete for resources and slow everything down further. Wait for the first export to complete, as indicated by a success message or the export file appearing in your chosen location. If exports consistently fail, try exporting to a different location like your Desktop to rule out permission issues with your Documents folder.
- FIRE Planning Calculations Slow: Monte Carlo simulations generating 10,000 scenarios typically take 5-15 seconds to calculate. This is completely normal given the computational complexity of running thousands of lifetime financial projections. If simulations take longer than 20 seconds and you find this disruptive, reduce the scenario count by going to FIRE Planning → Settings → Scenario Count and selecting 5,000 or 1,000 scenarios instead. Fewer scenarios calculate faster but may provide less statistical confidence in the results. 1,000 scenarios is usually sufficient for most users. Avoid running multiple simulations simultaneously. If you click "Run Simulation" on one FIRE plan while another is still calculating, both will run slowly as they compete for CPU resources. Wait for the first simulation to complete before running another, or close SavePoint and restart to cancel a stuck simulation.
Regular maintenance procedures to keep SavePoint running optimally and prevent common issues before they impact your financial management workflow.
-
Verify Automated Backups
Check backup success logs, verify backup file integrity, and test restore process quarterly.
-
Performance Review
- Monitor application startup times and responsiveness
- Check memory usage during heavy operations
- Review export performance and adjust settings if needed
- Update automation rules based on transaction patterns
-
Data Quality Check
- Review uncategorized transactions and apply categories
- Verify account balances match external statements
- Check for and resolve duplicate transactions
- Update merchant mapping rules for improved automation
Enable automated backups from day one, regularly review and update categorization rules, monitor performance with large datasets, and keep security settings current. Set quarterly reminders for backup restore testing to ensure data integrity.
Practical performance strategies for keeping SavePoint responsive as your financial data grows over months and years. Most users won't need these optimizations initially, but they become increasingly important as you accumulate thousands of transactions, manage dozens of accounts, or use resource-intensive features like Monte Carlo simulations for FIRE planning.
⚡ Transaction Management Performance
As your transaction history grows, the Transactions page can slow down when loading and displaying thousands of records. The primary solution is enabling pagination, which dramatically improves responsiveness by loading only a subset of transactions at a time instead of all records simultaneously.
Enable Pagination: Go to Settings → Preferences → Transaction Pagination and enable the feature. Start with 100 transactions per page. This provides good balance between seeing enough data and maintaining fast load times. For databases with 1,000+ transactions, pagination typically improves page load time by 50-90%. If you have 5,000+ transactions, pagination becomes essential as the page may freeze or crash without it.
Filter Before Bulk Operations: When you need to bulk delete transactions, always filter to a specific date range or category first. For example, if you're removing duplicate transactions from January, filter to January first, then select and delete. Operating on 100 filtered transactions is significantly faster than trying to select from 5,000 unfiltered records. Additionally, "Select All" only works on the current page when pagination is enabled, so filtering makes bulk operations more manageable.
Batch Your Data Entry: If manually entering transactions in Edit Mode, work in batches of 10-20 transactions. Add your batch, press Ctrl+S to save, then add the next batch. This approach prevents data loss if SavePoint crashes during entry. You'll only lose the current unsaved batch rather than an hour's worth of work. Batching also reduces memory pressure from having too many unsaved changes in memory.
Import Regularly: Import bank statements weekly or monthly instead of once a year. Importing 100 transactions 12 times per year is much easier to review and categorize than importing 1,200 transactions all at once. Smaller, frequent imports also make it easier to spot errors or duplicates before they accumulate. The import process itself runs faster with smaller files, and you're less likely to encounter timeout issues.
📊 Dashboard & Charts Performance
Dashboard charts consume significant memory and processing power, especially when displaying data across multiple years or generating complex visualizations. Optimizing chart display improves both load times and overall application responsiveness.
Disable Unused Charts: Access Dashboard settings via the gear icon and uncheck any charts you don't regularly review. Each active chart requires memory and processing to render. Displaying 8 charts loads noticeably faster than 15 charts. If you only check certain charts quarterly, disable them and re-enable when needed rather than keeping them active constantly.
Use Shorter Date Ranges: The Dashboard defaults to showing data for your selected time period. If you're viewing "All Time" with 5 years of data, every chart must process 5 years of transactions. Switching to "Last 12 Months" or "Last 6 Months" dramatically reduces the data each chart must process, resulting in faster rendering. You can always expand the date range when you need historical perspective.
Restart After Heavy Chart Use: If you've spent an extended session reviewing different charts across multiple tabs (Dashboard, Budget, Cashflow, FIRE Planning), the application may feel sluggish as chart memory accumulates. Simply restarting SavePoint clears the chart cache and restores snappy performance. Consider restarting if you notice charts loading slowly or if memory usage seems high.
FIRE Planning Memory Management: Monte Carlo simulations generate thousands of scenario calculations and use substantial memory to render projection charts. After reviewing your FIRE projections, switch to a different tab to free up these resources. If you're actively working with FIRE planning, close other resource-intensive tabs temporarily to ensure smooth simulation performance.
💱 Multi-Currency Performance
If you use SavePoint's multi-currency features, the frequency and volume of exchange rate uploads directly impacts both database size and currency conversion performance. Finding the right balance between accuracy and efficiency depends on your specific use case.
Upload Only What You Need: SavePoint supports 150+ currencies, but you should only upload exchange rates for currencies you actually use. If you only have USD and EUR accounts, don't upload rates for JPY, GBP, CAD, and dozens of other currencies. Each unnecessary currency pair adds database records that slow conversions without providing value.
Choose Appropriate Frequency: Monthly uploads (rates on the 1st of each month) are sufficient for most users tracking investments or savings in foreign currencies. This frequency provides adequate accuracy for investment performance tracking and foreign account balance snapshots while keeping database records minimal. Weekly uploads (every Monday) work well for users with frequent foreign currency activity. You capture most rate movement without overwhelming the database. Daily uploads should only be used if you require precise daily conversion accuracy, such as for active forex trading or businesses with daily foreign currency transactions.
Understand the Impact: Consider the long-term storage implications of your upload frequency. If you track 2 currency pairs with monthly rates for 5 years, you'll have 120 exchange rate records. Switch to daily rates and you'll have 3,650 records. A 30x increase. With 10 currency pairs and daily rates, that's 36,500 records over 5 years. More records mean slightly slower currency conversions and a larger database file, though the performance impact is only noticeable once you exceed 1,000+ exchange rate records.
🗄️ Database Size Management
Your SavePoint database grows over time with transactions, exchange rates, daily balance snapshots, and historical data. Monitoring and managing database size helps maintain optimal performance, especially as you approach years of financial history.
Monitor Your Database: Check Settings → Profile Tab to see your current database size. Database size varies significantly based on transaction volume, multi-currency usage (exchange rates consume space), and frequency of daily balance snapshots. If your database exceeds 100MB and you're experiencing performance issues, consider optimization strategies. Database size over 200MB warrants attention unless you have extensive multi-year transaction history with frequent currency conversions.
Archive Old Data: For transactions older than 5 years that you rarely reference, consider archiving: Export the old transactions to CSV (Settings → Data Management → Export Transactions), verify the CSV file opens correctly and contains your data, then delete those old transactions from SavePoint. Keep the CSV files for permanent records and tax purposes. This reduces your active database size while preserving historical data in a portable format.
Manage Backups: SavePoint's automatic backup system keeps your 10 most recent backups and permanently deletes older ones. However, if you've created numerous manual backups, these accumulate separately. Periodically review your backup folder and delete manual backups older than 6-12 months. While old backups don't affect SavePoint performance directly, they consume disk space which can slow system-wide operations when your drive fills up.
Ensure Adequate Disk Space: SavePoint operations can slow or fail when disk space runs low. Keep at least 1GB of free space on the drive where SavePoint stores your database. If your disk is 90%+ full, you may experience slow saves, failed backups, or export errors.
💻 System-Level Optimizations
Beyond SavePoint-specific settings, system-level optimizations can significantly impact performance, especially for users with large datasets or resource-constrained computers.
Close Other Applications: SavePoint with 10,000+ transactions typically uses 500MB-1GB of RAM during normal operation. If you're simultaneously running a web browser with 20+ tabs, email client, and other applications, your system may run low on available memory. Close unnecessary applications to free resources, particularly when importing large CSV files or running FIRE planning simulations.
Restart Regularly: If you keep SavePoint running continuously for days or weeks, memory usage gradually increases as chart caches and operation history accumulate. Restarting SavePoint every few days clears this accumulated memory and restores optimal performance. Think of it like restarting your web browser when it starts feeling sluggish after days of use with hundreds of tabs opened and closed.
Use SSD Instead of HDD: If your SavePoint database is stored on a traditional hard drive (HDD), moving it to a solid-state drive (SSD) provides dramatic performance improvements. Database operations are disk-intensive. SSDs can load and save the database 3-5x faster than HDDs. If you're experiencing slow startup times (10+ seconds), slow transaction saves, or sluggish page transitions, check if your database is on an HDD and consider moving it to an SSD.
Antivirus Considerations: Real-time antivirus scanning can slow database operations as the antivirus checks the database file every time SavePoint reads or writes to it. Consider adding your SavePoint folder to your antivirus's exclusion list. Since SavePoint doesn't download files from the internet or execute suspicious code, the security risk is minimal, while the performance benefit can be significant for users with large databases.
Months 1-6 (Under 1,000 transactions): No optimization needed. Use SavePoint normally without worrying about performance settings. Most users experience excellent performance during this phase.
Months 7-12 (1,000-2,000 transactions): Enable transaction pagination at 100 per page when the Transactions page starts taking more than 2-3 seconds to load. Disable any Dashboard charts you never use. Performance should remain excellent with these simple optimizations.
Year 2+ (5,000+ transactions): Pagination is essential at this scale. Consider using date range filters regularly on the Transactions page instead of viewing all transactions. Disable unused Dashboard charts. Restart SavePoint weekly if you use it daily. If your database exceeds 100MB, consider archiving transactions older than 3 years.
Multi-Currency Users: Start with monthly exchange rate uploads. If you need more precision, try weekly uploads for one month and see if the extra accuracy matters for your use case. Review and delete old exchange rate records annually. You probably don't need EUR/USD rates from 5 years ago at daily granularity.
SavePoint includes help resources and support channels to assist with any questions, issues, or feature requests you may encounter during your financial management journey.
📚 Built-in Help System
SavePoint includes comprehensive contextual help accessible from every major page via the Help button (? icon). This built-in documentation provides immediate guidance without requiring internet access or external documentation searches.
How to Access: Click the Help button (usually located in the top-right corner of each page) to open a modal window with tabbed help content specific to that page's features. Help modals typically contain 3-5 tabs organized by topic - Overview, Getting Started, feature-specific tabs, and Tips/Best Practices.
Content Coverage: Built-in help covers all major features with step-by-step instructions, practical examples, and troubleshooting guidance. Complex features like FIRE Planning and Monte Carlo simulations include detailed workflows walking you through each step of setup and usage. Help content updates with each SavePoint version, ensuring documentation always matches your installed features.
When to Use Built-in Help vs. This Web Documentation: Use built-in help for quick task-specific guidance while working in SavePoint - "How do I create a budget?" or "How do I import transactions?" Use this web documentation for comprehensive feature understanding, comparing features before purchase, or troubleshooting complex issues requiring detailed explanations.
🆘 Support Channels
- Video Tutorials: Visit our YouTube channel to access comprehensive video guides covering setup, features, and workflows. Our video library includes step-by-step tutorials for getting started, budget creation, transaction management, and advanced features like FIRE planning and multi-currency support
- Email Support: Contact our support team directly at support@savepointfinance.com or through the contact form on our website. Our team responds to technical questions, feature requests, bug reports, and general inquiries. Please include relevant details such as your operating system, SavePoint version, and steps to reproduce any issues
- Discord Community: Join our Discord server for real-time community support, tips and tricks from other users, feature discussions, and direct access to the SavePoint team. Our Discord community is active with users sharing workflows, templates, and best practices for financial management
- Website Resources: Visit savepointfinance.com for the latest updates, release notes, feature announcements, and downloadable resources including user guides and quick reference sheets
Contact technical support for: persistent database errors, encryption key issues, multi-user access problems, backup/restore failures, or any security-related concerns. Always backup your data before attempting major troubleshooting steps or software updates.