I just noticed that a bank account had some missing transactions and upon further inspection, it turned out that Manager wasn’t importing all the lines on the false assumption they were imported before.
I narrowed down the bank statement to just these rejected entries and tried again:
This is a feature, not a bug.
Banks do tend to change descriptions between bank exports.
So Manager will match dates/amounts only and uses description only if there are multiple transactions with the same date/amount.
This prevents importing duplicate when bank description changes between bank exports.
You must have already those two transactions imported with different description.
The thing is, these transactions are not duplicates.
Yes, they have same amounts and dates, but they are not the same.
We have some amounts that appear multiple times during the day – for example 5 BHD, 10 BHD, etc, and some times we need to do multiple imports per day.
This is an example of type II error → valid data not passing validation.
I think this has been a recent change since we have been getting duplicates when importing summarized bank transactions for a virtual bank where Description field is the identifier, previously Manager used to catch these and ignores them.
The way I see it that there was a problem with some banks – it wasn’t Manager’s fault.
However, trying to solve these problems for the banks ended up introducing a type II error in Manager, that is rejecting false
I think the previous method was objectively better since before there used to be error type I (accepting invalid data) which was the fault of the bank but now we have both type I & II errors which could have been prevented by Manager
That’s not a problem but when you are doing bank import, you need to include all the transactions for the day. Not just new additions. What is the source of the import file that it doesn’t include full day of transactions?
Not a recent change. It was actually discussed more than 10 years ago. Here is what I wrote back then:
That’s weird, I just started getting these duplicates/ommissions this past week.
It’s a virtual wallet for a delivery agent.
The reason it doesn’t include the full day of transactions is beyond me.
It groups transactions by sessions, the session number is the id field and it appears in the description.
The problem is that some of which are active and some are closed.
The closed sessions pose no problem, but active ones will also appear in the next import.
The problem is that their statement doesn’t show if a session is active or closed.
I accept this as a solution for the ommissions, but I don’t know what to do with the duplicates – but this isn’t Manager’s fault since the wallet doesn’t allow me to show only closed sessions.
Looks like that’s something that I need to figure out.
