GNUCASH OPENING BALANCE VERIFICATION
GNUCASH OPENING BALANCE CODE

QSF is part of the Gnome2 port of GnuCash. So that a complete bank contact would read: Ī lot of this can be achieved in GnuCash/QsfXml - this provides a generic export and import function in plain XML for selected entities from GnuCash (and other applications).

GNUCASH OPENING BALANCE CODE

PS: To support international transfers it be allowed to append the Bank Identification Code (BIC ) to the IBAN.

GNUCASH OPENING BALANCE VERIFICATION

The generic-exporter could also display the transactions for verification before handing them over to the interface specific exporter, maybe in the (printable) International Payment Instruction (IPI) standard form.

Otherwise the whole rest (not in brackets) of the description is used as info field for the online order. Here 'customer #999' is explicitly specified in quotes for the info field of the online order, so that the rest of gnucash's info field does not get exported and remains as a private note. ) a 8 digit bank code and a 10 digit account number follow. The first two letters from the IBAN specify the country, next is a two digit checksum, and for German IBANs (DExx. The left part is the name and the right part is the IBAN. The bank-contact data is written in brackets. Here is an example string of a description field: The new International Bank Account Number Standard (IBAN) is suggested to be used. Therefore 'bank contact' data is stored in the description fields in a unique way. The account number, the bank, and the name of the receiver for example. One problem is that bank interfaces need datafields that are not explicitly necessary in gnucash. 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).

Gnucash opening balance