Refactor "movement" object

While the `parser.js` implementation is great, there's too much risk on having to manually select "date", "description" "currency", "amount", and "movements". This is prone to having issues down the line. Can't we find a way to either have these be their own properties of a class, or that these strings would be more easily accesible through constants or an enumeration to avoid human error?