Troubleshooting
Guide 41: Troubleshooting
Solutions to common issues
Application Issues
OtterLedger won't start
- Restart your computer
- Check if another instance is running
- Verify .NET 8 runtime is installed
- Try running as administrator
- Reinstall OtterLedger
Application is slow
- Close other applications
- Check file size (large files take longer)
- Rebuild database indexes (Settings → Advanced → Rebuild)
- Check for pending updates
Crashes on startup
- Delete settings database (will reset preferences)
- Windows:
%AppData%\OtterLedger\settings.db - Mac:
~/Library/Application Support/OpenLedger/settings.db
- Windows:
- Restore from backup if file is corrupted
Data Issues
Transactions not saving
- Check if file is read-only
- Verify disk space available
- Close and reopen file
- Check file permissions
Balance doesn't match bank
- Run reconciliation
- Check for pending transactions
- Look for duplicates
- Verify cleared status
Missing transactions after import
- Check import date range
- Look in correct account
- Review duplicate detection settings
- Check import log for errors
Bank Connection Issues
SimpleFin not syncing
- Check internet connection
- Verify SimpleFin credentials
- Refresh bank connection
- Some banks have delays (wait 24 hours)
Bank login fails
- Update bank credentials
- Check for bank website changes
- Clear connection and re-add
- Contact bank for API access
Duplicate transactions from sync
- Adjust duplicate detection settings
- Review and merge duplicates
- Adjust sync date range
Import Issues
QFX/OFX file not importing
- Verify file isn't corrupted
- Check file encoding
- Open in text editor to verify format
- Try exporting from bank again
CSV import problems
- Verify column mapping
- Check date format matches
- Remove special characters from amounts
- Ensure UTF-8 encoding
Wrong amounts after import
- Check decimal separator settings
- Verify amount column mapping
- Look for currency conversion issues
PDF Import Issues
PDF file not parsing correctly
- Verify the PDF is a text-based statement (not a scanned image)
- Try the "Flip Signs" button if amounts seem inverted
- Check if NegateStatementAmounts is toggled correctly for credit card statements
- Some bank PDF formats are not yet supported — try importing as CSV instead
PDF balance doesn't match
- Verify the correct statement period was extracted
- Check if multi-section statements have all sections included
- Use the "Flip Signs" button for liability accounts
Reconciliation Issues
Can't find matching transaction
- Widen date range
- Search by amount only
- Check for splits
- Verify transaction wasn't deleted
Statement doesn't balance
- Verify beginning balance
- Check for missing transactions
- Review cleared transactions
- Look for duplicate entries
AI Issues
AI not categorizing
- Check AI settings enabled
- Verify API key (for cloud)
- Check local LLM is running
- Review error logs
Wrong categories from AI
- Create rules for common payees
- Adjust confidence threshold
- Review and correct to train the system
- Check category mappings
XGBoost model not working
- Verify you have enough categorized transactions (minimum ~50) to train the model
- Go to Settings → AI → XGBoost and click "Train Model"
- Check that the model status shows "Trained"
- If accuracy is low, categorize more transactions and retrain
Web search enrichment errors
- Google Search may be rate-limited (HTTP 429) — DuckDuckGo will be used as fallback
- Check Settings → AI → Web Search to verify enrichment is enabled
- Some cryptic payees may not return useful results from web search
Performance Issues
Reports are slow
- Narrow date range
- Filter to specific accounts
- Check for large transaction count
- Export and view externally
Search is slow
- Rebuild search index
- Use more specific terms
- Filter by date range first
Getting Help
Log Files
Location: %AppData%\OtterLedger\logs\
- Include logs when reporting issues
- Logs contain no personal financial data
Support Resources
- Check this troubleshooting guide
- Search community forums
- Review release notes for known issues
- Report bugs on GitHub
See also: Guide 42: FAQ