![]() ![]() The "action" field is set to something the exporter recognizes like "wire transfer" and the status is set to a yet to define new status like "s" for "send it". Pending "online actions" would be characterized be two things. The concept involves defining a format for "bank contact" data that is stored within the description fields of regular gnucash transactions which should not be a problem for any other feature to handle (passively).ġ) look for transactions that are pending "online actions",Ģ) read the "bank contact" and info data,ģ) hand those transactions to specific hbci-, ofx-, web-, print- interface-exporter etc.Ĥ) and change the status of transactions accordingly Without a exporter concept the same would be true with any other interface implementation. Such nice features as scheduled transactions can't be used because they are not hbci-aware. Right now generation of hbci online transactions can only be done in a stand alone hbci-gui-module. On the gnucash-de mailing list the idea of a generic-exporter has developed to improve integration of the HBCI-protocol features and facilitate many other features.Ī generic-exporter framework will also be good for other online protocols, file formats, check printing, data syncing etc. Conceptual Issues regarding an implementation.Data splitting function (from existing beta 2).Implement accounting periods ("periods").Simple "Close Accounting Period" help druid.Why is Book Closing/Accounting Periods Still Unfinished?.Distinguishing Accounting Periods and Data splitting.(A) description of "book closing" (aka Plan A from /src/doc/books.txt). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |