Re: Digest for microsoft-money@googlegroups.com - 4 updates in 2 topics

[rusty fender]

I had a statement discrepancy with Money on time, and I fixed my problem by exporting all accounts, and importing them into a new file. My discrepancy was only 0.20, but importing the data into a new file fixed the issue.

On Wed, Jul 1, 2026, 11:56 PM <microso...@googlegroups.com> wrote:

microso...@googlegroups.com

Google Groups

Topic digest
View all topics

• Account Balancing Offset - 3 Updates
• F2O note, and upcoming F2O minor tweaks - 1 Update

Account Balancing Offset

J Hoban <jho...@umich.edu>: Jul 01 03:31AM -0700 The starting balance in Money reconcile is the sum of all reconciled transactions. For your starting balance to be off from your bank, a transaction was marked as reconciled when it shouldn't have been, or vice versa. I'd be looking at your January bank statement against your reconciled transactions to see if there isn't something mismarked.   Then again, you could just go through a reconcile and see if the problem solves itself.   My way of operating is to sort of doing a reconcile each time I read an ofx file. Unless I had manually entered transactions, the "Bank Balance" in the upper right above the headers should match the Money account balance. If I have manually entered transactions I temporarily play with dates of the non-E transactions to get a line that compares. Its easier to fix balance errors early.       On Tuesday, June 30, 2026 at 5:04:55 PM UTC-4 Ameridan (microsoftmoneyoffline.wordpress.com) wrote:

Jeff Feit <jeff...@gmail.com>: Jul 01 09:48AM -0400 The problem was that the starting balance WAS NOT the sum of all reconciled transactions. In my example below, the sum of all reconciled transactions was $16,908.78. When I went to balance it, Money showed the starting balance as $14,908.78. I've been using Money for 28 years (and this account dates back to 2006) so I'm pretty familiar with how it is supposed to work, and it was not working correctly.   Whatever the issue was, it resolved itself. After going through and balancing it for the rest of the statements I had-- each time it telling me I was off by $2000, and each time ignoring it and not allowing it to adjust my starting balance-- it now matches. If I hit "Balance this account" it shows the correct sum of all reconciled transactions.   On 7/1/2026 6:31 AM, J Hoban wrote:

J Hoban <jho...@umich.edu>: Jul 01 01:22PM -0700 Sorry Jeff, I wasn't very clear.   My going in assumption from years of messing up my own account balances is that Money is correct, the starting balance is the sum of all reconciled transactions. For you to see a transaction marked R having a balance that matched your bank statement and then have the balancing tool show a starting balance $2,000 less, there must be something like an earlier unreconciled deposit that you are not seeing, or a later reconciled withdrawal. You might not see the transaction because you have filtered it out, date filter or reconcile filter. Once you get into the balancing tool it shows you all the unreconciled transactions for all dates. If there was an earlier unreconciled deposit, it would have shown at the top of in your list, hard to miss. So, that leaves a mistakenly reconciled future withdrawal. If you filter out reconciled transactions, you would never it. Eventually, you reconciled the statement that contained that transaction and then everything balances out. That sounds kind of odd also, how could a future transaction get marked as reconciled, but it fits the description.

Back to top

F2O note, and upcoming F2O minor tweaks

Cal Learner <msm.cal...@gmail.com>: Jul 01 08:04AM -0700 F2O_beta20.zip uploaded to https://drive.google.com/drive/folders/1-4fBbRxaPhNYZK0gNHuZ3n-Bdoncy2aR   If you use F2O and new transactions are not coming in, a change in the Fidelity Accounts_History*.csv files for *some* users has been discovered. Such changes may be phased in to the rest of us at some point.   Date format in the CSV has been mm/dd/yyyy format, but for some has changed to mm-dd-yyyy format. This caused the transactions to be ignored during processing. A change to be tolerant of either is being tested. Beta20 accepts either date format.   If/when that change happens to your CSV, since the CSV lines changed, and the FITID is a hash based on the CSV line, there will be a different FITID for existing transactions. Therefore in your F2O_cfg.py, add/change IGNORE_BEFORE_YYYYMMDD="20260618", but use whatever date comes after your latest existing successful downloads. Alternatively, accept the duplicates and void one of each duplication, or just click No, and that gives a voided transaction.   See the bottom of recent_note.txt for recent changes. On Tuesday, June 30, 2026 at 1:54:41 PM UTC-5 Cal Learner wrote:

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to microsoft-mon...@googlegroups.com.