So now I'm confused again. You are saying the dates could be correct when on
daylight savings, but a day early when on standard time? If strictly a
midnight GMT issue (again, my bank stamps the transaction as 000000[0:GMT]),
then whether daylight savings or not, the date should be early when
converted to EDT(-4) or EST(-5), right?

And now that I look more closely, I see some dates ok, some a day early (as
compared to the *rs.txt file and my expectation). And that happens with
transactions downloaded before and after daylight savings. If I go to
transactions before I upgraded from M04 to M06, I see the same mix of some
good, some a day early entries. But I cannot tell if that actually happened
in M04 & I never noticed it (but I've been using Money for years and have
not noticed), or if it was on converting to M06.

Something very odd is going on. I'm no longer even sure what to request from
my FI w.r.t. time zone stamp.

Thanks again for your help, tho!!

-Tony

"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:qp89o19j85h3juuu30man0orhgrpvlr7u7[at]4ax.com...
- quote -

In microsoft.public.money, t s wrote:

- quote -

Consider that when you were using Money 2004, it may have been
before the time change to standard time. Money 2004, as did/do Money
2003 and Money 2000, did/does indeed work the same way.

I went thru this for at least a couple winters before my FI
corrected it.

- quote -

I expect you will see something like "[-5:EST]" in the OFX file.

Thanks, Cal! Your time zone clue was valuable. Did some additional
searching, and found MS KB 840181. Using that, I found in the resulting log
file that my bank is using a time stamp of midnight GMT (000000[0:GMT]). M04
didn't seem to care (or didn't handle it "correctly"). In talking with my
bank, they too see that this "day early" issue affects M05 & M06. Makes
sense that if a transaction posts at midnight GMT, then it will look like a
day early EST, for example.

Of course, Microsoft says there's nothing they can do (and I have no way to
override time zone correction). And my bank says that they have changed
nothing, it works in M04 but not M05/M06, so it must be a Microsoft issue.


If I understand this correctly, it looks like my bank is using an incorrect
time stamp ('cause the transactions post midnight Eastern, not midnight
GMT). But I'd also like to see something in Money that would let me just use
the date and ignore the time stamp. Oh well, at least I see what's happening
now. But I'm still going to get on my bank. And I did log a case with
Microsoft.

-Tony

"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:3eg6o11c23r9gu54b1817s4psd9iiqn2cm[at]4ax.com...
- quote -

In microsoft.public.money, t s wrote:

- quote -

I suspect your bank is headquartered in a time zone to the east of
you, that you do OFX download from your bank, and the bank time
stamps each transaction at midnight ("0000"). But midnight one zone
east of you is 2300 the previous day.

Here is the start of a discussion of time zone issues in the OFX
spec:
================================================== ====================
3.2.8.4 Time Zone Issues

Several issues arise when a customer and FI are not in the same
time zone, or when a customer moves a computer into new time zones.
In addition, it is generally unsafe to assume that computer users
have correctly set their time or time zone. Although most
transactions are not sensitive to the exact time, they often are
sensitive to the date. In some cases, time zone errors lead to
actions occurring on a different date than intended by the
customer. For this reason, servers should always use a complete
local time plus GMT offset in any datetime values in a response.
================================================== =======================

The solution is that the bank either use the actual time or to
select a generic timestamp to use that corresponds to noon GMT. Then
no customer would have a date change. ares enough.

Your workaround is to change your time zone to either that of your
bank or GMT before processing the download. Then *try* to remember
to change it back afterwards.

Under some circumstance, the problem only occurs when there is not
daylight saving time in effect. That would occur if that bank was
one time zone east of you, and it always used standard time in the
OFX. In the summer, the standard time there and daylight saving time
in your zone are the same.

Hello,

Using M06 with direct connect & bill pay to my bank, the downloaded
transaction dates entered are a day early in Money. If I view my account
through my bank's web interface, the date would show as I'd expect (e.g.
11/21) for a given transaction. But when viewing my account in M06 (again
directly connected/downloaded from bank), that same transaction has a date
of 11/20. All transactions from this bank seem to "post" a day early in
Money.

I do let Money change the transaction date from what I entered to what the
bank says (that's the way I want it). I also manually downloaded a statement
as a csv from my bank and the dates are correct there (e.g. 11/21). So far
as I can tell, I only have this problem with this bank. I direct download my
credit card, investment stuff, etc, without apparent date problems (but I
need to check more closely). Interestingly, I did NOT see this problem with
this bank when running M04 (I upgraded to M06 two months ago).

For the short term, I know I can manually change dates, except for my
Epays!! I'm stuck with them showing in my M06 register as a day early.

Does this seem like a bank issue? An M06 issue -- not that there's any
issues with M06, right?
Any ideas on what I could look at to see what's going on?

Thanks! -Tony