support for OFX

[mtotschnig]

with OFX it might be possible to implement payment types

[lauco74]

Yes !!!

[mtotschnig]

Having investigated the OFX specification and the way Grisbi handles OFX import , I learned that it is not possible to encode the category of a transaction into OFX. Hence, the rationale for supporting OFX is no longer valid.
Unfortunatly none of the current import formats supported by Grisbi (OFX,GIF,Gnucash,CSV), allows to transmit both category and payment method.

[thomascrisan]

Twelve years later from when this issue was closed, several of my financial institutions no longer export to QIF. The current choices are QFX (Quicken), QFO (Quickbooks), and OFX.(Open Financial eXchange).

Would you consider adding OFX now for current compatibility with various financial institutions that are no longer offering QIF export?

https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf

[mtotschnig]

@thomascrisan Thanks for bringing this topic to my attention again. I am definitely interested, particularly also because OFX seems also to allow to implement direct communication between the app and the bank. Unfortunately being Europe based, I do not have access to any bank that offers that type of access, but I will definitely look into the topic.

[mtotschnig]

@thomascrisan I am evaluating feasibility of OFX import for version 3.7.5. Do I understand you correctly that you are interested in OFX import? Can you imagine valid use cases for OFX export? Might it be possible for you to share any minimal example (potentially replacing real data with fake values) of the files made available by your banks here or with support@myepxenses.mobi ?