dkb2homebank icon indicating copy to clipboard operation
dkb2homebank copied to clipboard

Wrong import column for incoming payments

Open mfernau opened this issue 1 year ago • 3 comments

Hello hamvocke,

I'm having trouble to explain this. Prior your change to the new format an incoming payment displayed the sender in the column 'payee' in HomeBank: Screenshot_20231029_110632

But now - after your change - the sender isn't displayed any more. Instead I see myself as the payee which isn't very informative for incoming payments as I can't see the real sender for this booking: Screenshot_20231029_111231

I hope you understand my problem...

Thanks for you efforts in this tool! I'm using it very often

mfernau avatar Oct 29 '23 10:10 mfernau

I understand that this is a change from what happened before, but I'd argue that what you're describing here is in fact the correct behavior.

Payee is the person who gets the money. If it's an incoming payment, that's you.

I know that the previous CSV formats treated this a little differently - but that's because of the way DKB generated the CSV files in the old banking portal, not due to the way this script is processing files.

Would it be useful to add the sender into the "Info" field instead?

hamvocke avatar Oct 30 '23 08:10 hamvocke

The 4th Column in the import CSV File is named "payee" as of the official CSV-Format http://homebank.free.fr/help/misc-csvformat.html This actually leads to the interpretation that the “recipient of money” should always be written there. However, this makes no sense for incoming cash because "the receiver" is already defined as of the CSV file itself which is then imported into a concrete account. To display my name in this field for incoming cash is totally worthless. If you have a look at an official screenshot of HomeBank: image2

For me this looks like that there is normally "the other party" in this field even if this field is named payee. "Amiga Tech" seems to be the employer in this example and these bookings are the salary. I think this is a problem with a single field for an ambiguous meaning: incoming vs outgoing cash. Error by design if you ask me.

To use the info field instead feels not good either because I sometimes use this field as an additional information why or for what a concrete booking was for.

I can understand that you argue that this field is named "payee" and that there is "no room for interpretation." Maybe you can add a switch to you tool so that one can decide to use this field more as an "the other involved party" oder a real "payee" field.

mfernau avatar Oct 30 '23 10:10 mfernau

The problem that @mfernau describes can be easily solved by checking whether the transaction is of type "Ausgang" or "Eingang". If it is the latter, then you should use the column "Zahlungspflichtiger" to set the payee. You change the line 208 in the script as follows: 'payee': (row["zahlungspflichtiger"], row["zahlungsempfänger*in"])[row["umsatztyp"] == "Ausgang"], By doing so, the script works like a charm. Many thanks, @hamvocke, for this nice script !

skalaid avatar Nov 28 '23 01:11 skalaid