Config option to filter out future dates

[hoejmann]

Not sure where to post ideas, but here I go :)

Some banks, in this case Nordea DK seems to occasionally have a 'bookingDate' and 'valueDate' set in the future, which returns in an error when sending the request to the YNAB API:

"bookingDate": "2024-04-22",
"valueDate": "2024-04-22",

{"error":{"id":"400","name":"bad_request","detail":"date must not be in the future or over 5 years ago (index: 0), date must not be in the future or over 5 years ago (index: 1)"}}

Idea: A new config option to automatically filter out dates in the future

[hpernu]

Interesting. Can you clarify what kind of transactions these are?
Is it consistently returning future dates for same exact transactions(until the date has passed, of course)?

If these stay the same, I would guess, these might be:

• something paid with credit/debit card which has not yet been fully finalized(i.e. in pending state)
• payments you have set to be made on a future date
• payments and/or transactions made during the weekend which will only settle the next monday

If these, however, are transient(i.e. they might disappear between calls), then it is in an error in Nordea and/or gocardless and should really be reported to them.

EIther way, we can still remove these(of course), in a manner you suggest(for example). Realistically, though, we cannot possibly work around every misbehavior of thousands of banks. So, if this really looks like changing between calls to Gocardless/Nordigen, it should be fixed in there.

[hpernu]

Come to think of it, I really see no benefit in ever importing transactions with dates in the future. There is the issue of possible difference in dates depending on timezones, or even the system running ynabber having an out-of sync clock(or wrong timezone). But I assume these would be eventually be imported anyway so it is not a big loss. The out-of-sync clock, if by huge margin, might be a problem but really ought to be fixed anyway.

[hoejmann]

The transactions did indeed appear to be in some sort of pending state, and had their dates updated at some point during the weekend to "not be in the future", which caused the following import to go through successfully.

It was the first time I observed this - bit unsure what exactly caused these particular transactions to have future date.

[martinohansen]

Thank you for bringing this up, I appreciate it. I made an issue from this discussion with a fix: #73

Instead of making it a config option, we filter out anything that's in the future or older than 5 years. I hope that works for you.