Coder Social home page Coder Social logo

Comments (3)

hamvocke avatar hamvocke commented on September 28, 2024

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?

from dkb2homebank.

mfernau avatar mfernau commented on September 28, 2024

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.

from dkb2homebank.

skalaid avatar skalaid commented on September 28, 2024

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["zahlungspflichtige
r"], row["zahlungsempfänger*in"])[row["umsatztyp"] == "Ausgang"],
By doing so, the script works like a charm.
Many thanks, @hamvocke, for this nice script !

from dkb2homebank.

Related Issues (9)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.