![]() ![]() WHne you have a correct import then import your full file. If those transactions are incorrect on import, delete them, swap the headers and reimport the test file. Again if uncertain import an edited data file with 1-2 records and assign both headers. You may also encounter import files with two columns of unsigned amount data. WHen you have a successful header assignment, import the full file. If this does not give the correct transactions on import, delete the imported records from that file and try the other header. The best procedure is to import a small file of one or two records (edited form your main import file using one of the column header Deposit/withdrawal. ![]() This has not been fully tested in GnuCash for the above assumptions at this stage. The assignment of column headers is indicative only. Table of equivalence between informal and formal accounting register labels in GnuCash and label usage in imported records This description is of common usage by organisations like banks however there is no guarantee that their exported data will necessarily conform. The following table is intended to give new users of the CSV importer some assistance when trying to match the importer's column headers to match the data labels in the imported data and sign conventions where debit/credit amounts are represented by signed integers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |