Whether you modify the bank data file using a Python Script, or an Excel Lookup Table, or by some other means, is up to you. It's relatively easy to embed that information into the data file before importing it. Similarly, any transfer out of your bank account labelled "Netflix" will inevitably go against your GnuCash expense category Expenses:Utilities:Streaming Services. For example if your Account A data file contains the descriptor "A12345678" which reliably means "this is a transfer from Account B" then you can actually modify your data file so that "Account B" is identified as the transfer account. "Tidying-up" in Steps 3 and 6 is only necessary if GnuCash isn't provided with sufficient information in the data file it's importing. The GnuCash Import process has a Transaction Matching stage where it will effectively ask you "Is this $100 transfer out of Account B the same $100 transfer that I already have recorded for that date, or is it a new and separate transaction?" With one mouse-click, you can confirm that it is indeed the same transaction - and GnuCash won't create an unwanted new transaction. This is great preparation for importing your transactions for Account B. This should give you a better outcome because:īy the time you've completed Steps 2 and 3 (imported the first lot of data and tidied up), there is already a recognisable transaction in the GnuCash database showing a $100 transfer from Account B to Account A.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |