@Trudy wrote:
The statement will not be cut on the 27th nor balance report until the "not seen" actual new statement/close date. So although on one of my accounts it shows my next payment is due 9/4, it is technically 8/4 (extended beyond 7/24 shown) and close/report date will be 8/7 per what I was told on the call, even though the site still shows 7/24. So it will not report to the CB's until after 8/7. The "not seen" new close date is actually effective now. Other than possibly the notices they sent, you can't see that 7/24 is not actually your due date this month as this change occurred after the 6/27 statement that generated the now "fake" 7/24 due date.
9/4 is actually the following months due date with a close/report date of 9/7.
I have a reoccurring charge that hits on the 30th or 31st of the month. It would normally not be reported for this billing cycle due to the normal report date of the 27th. But with this mid cycle change it will appear on my new 8/7 statement and if I don't pay this charge by the actual due date of 8/4 it will be reported to the CB's.
The CSR stated they have received several calls from people who obviously monitor their credit regularly or who expected to receive their statement on-line on the 28th but waited until the 29th to call in case it was pushed out due to the weekend.
I called and was given the exact opposite of this information. I will have to call again today because my CSR was just reading what was on the screen and doesn’t really know the context of why I’m asking.
But anyway this is what he said. The due dates and cycle close dates that are now is a September are actually the next ones. There are no due dates or cycle close dates in August. I said are you sure? He said “that what the system says”. Sounds like a HUCA situation.
Though as odd as that may be it does match the email I received from Cap1.
