Relocation to other account is booked twice

[Talkabout]

Hi,

I am facing a weird issue with my Firefly III instance where I am not sure if it can be even solved. I have 2 accounts configured that are synched on a daily basis. Everything works fine execpt one case once a month. We are relocating some amount of money from one bank account to the other. The description of this transfer is "Eigeneinzahlung". The problem seems to be that on one account this is correctly booked as "Eigeneinzahlung" whereas on the second account (where the money goes to), for whatever reason, it is booked as "EIGENEINZAHLUNG". This seems to cause Firefly to assume that these are different transactions and thus it is booked twice. I have not found any way to reconfigure or disable this function so that the double booking does not take place. When looking into the transaction list of both the bank accounts in their web frontend I can also see that difference. I can easily solve this by removing the "wrong" transaction from the second account in Firefly, the balance is immediately corrected. But I would like to avoid this manual step.
Can I solve this somehow by configuration? Anybody faced such a problem?

Thanks!

[JC5]

There is no real solution for this, I suffer from the same issue. My bank has different transaction IDs too, so the transaction A > B is different in the system from B < A. Very annoying, and I fear I have nothing yet.

[Talkabout]

Thanks for your feedback @JC5
Maybe something like "transaction rules" would be possible? For specific transactions (identified by the same rules currently available) one could define what kind of comparison to use to determine equality of transactions. For my case something like "strtolower"on the description field would be sufficient. Your solution would be to not include the transaction id but only check the other fields... Yeah, not that easy to solve... Are you also simply deleting the duplicated transaction manually?

[JC5]

Right now, it doesn't happen too often so I delete them manually indeed.

[ch-iwi]

Hi there,

I have spent some time setting this up for my six accounts and have really been enjoying using it so far. Fantasic application by the way!

I use the ISO file import and have noticed there is the notion of a booking account. Could we not use this to block one of the transfer transactions?

That way instead of trying to use a rule with source and destination accounts, which just ends up removing both transactions. We could ignore transactions from just one of the booking accounts, while allowing the other?

Cheers