Archive previous balance repair for older app versions
Older-version guidance for a resolved Archive previous-balance issue. Current users should start with balance troubleshooting instead.
Archived older-version guidance
This article is kept for older Foreseenly CashFlow versions. The Archive previous-balance issue described here relates to transactions deleted before version 1.10.5. If you are using the current app, start with Manual: Troubleshooting or How to update an account balance.
In older builds, deleting a transaction directly from Archive could cause the previous balance shown in history to differ by the amount of deleted transactions. Later app versions changed this behavior.
If you are on the current app
- Update Foreseenly™ CashFlow from the App Store first.
- Check the account's Forecast and Past/History for the transaction that likely caused the difference.
- If needed, use the account +/- balance update to enter the current real-world balance.
- Contact support if the same pattern repeats after updating.
Older workaround
The original workaround involved recreating a temporary transaction, saving it without updating the balance, restoring it from Archive with balance update enabled, then deleting the temporary forecast item. This is preserved here only for users following an older support thread.
Need more help? Search this product's help articles, or send a ticket if you still need help.
Was this article helpful?
Your vote helps QApps find articles that need clearer steps or better screenshots.
What was missing?