Closed michielbdejong closed 3 years ago
The MCC codes should also help for BEA transactions
The shops should be uniquely identified, so I guess it makes sense to have a special Shops addressbook for parsing BEA transactions. The full name could be the trimmed part before the >
. for instance for this transaction description:
'Gumus Market >UTRECHT 11.10.2020 14U35 KV008 8KG2YV MCC:5499 Contactloze betaling NLNEDERLAND'
The following contact could be automatically added to the user's 'Shops' address book:
What I would need from solid-logic is methods to:
I think there should be one history per shop (purchase + settlement pairs, so the balance there stays at zero), plus on for the bank account whose transaction history was imported (settlement only so balance there goes down) (settlement transaction only)
If you'd be open to sharing some of your decision-making process regarding which ontology to use, please do so! I'd be very interested (in contributing later on)!
@MikiDi Good to hear! We can discuss in the weekly Solid OS meeting https://solidos.solidcommunity.net/Team/2020/schedule/solidos-schedule.html
The current code is a very bare skeleton that imports statements from a csv download from your bank.
I haven't written the code yet to store it as RDF since I'm still finding out which ontology / predicates to use.
But one thing I want to do next is to create one contact per shop (transaction counterparty) that appears on the bank statement.
For insight in personal finance it would then suffice to group these contacts into themes ("Groceries", "Utilities" etc).