You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+37-27Lines changed: 37 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,14 @@ One area _Move2GnuCash_ will attempt to diverge from `csv2cash` is that the exis
13
13
- PieCash
14
14
- Pandas
15
15
16
+
## Limitations
17
+
18
+
Due to Quicken's manner of exporting data, account balances and categories need to be in place in the GnuCash book prior to the import of transactions. While this can be done manually (you still need to make them match what is coming out of Quicken!), _Move2GnuCash_ has options for importing these through two processes described below.
19
+
20
+
The challenges are exacerbated by limitations with Quicken's export of _All Transactions_ because we cannot group all non-investment accounts together into one export file. It becomes easier to export all transactions as one file and then let _Move2GnuCash_ divide the data into investment and non-investment transactions for processing.
21
+
22
+
_Move2GnuCash_ assumes all investment transaction history (in support of cost basis tracking) is present in the file even if non-investment transactions are limited to recent history (i.e., the chosen date for account balances described below). The implication is that non-investment transactions prior to th opening balances date will be filtered out while investment transactions will be retained.
23
+
16
24
## Exports from Quicken
17
25
18
26
_Move2GnuCash_ requires a minimum of two files from Quicken for each import process. Because exported CSV files from Quicken contain a varying number of extraneous lines and comments, these will have to be edited to get to final form.
@@ -27,32 +35,34 @@ With non-investment accounts, I chose 1 January 2017 as the start date, and so I
27
35
28
36
~~I then removed the top header lines (except the date), moved the labels from the first column to the second column, and removed the the other unnecessary formatting lines. In the end, the format of your file should look like this sample:~~
29
37
30
-
| ~~ | Accounts | 12/31/2016 |
38
+
~~
39
+
|| Accounts | 12/31/2016 |
31
40
| ------------------- | -------- | ---------- |
32
-
| Assets ||
33
-
| Cash ||
34
-
| - Cash | 77.12 |
35
-
| - Checking One | 440.84 |
36
-
| - Checking Two | 235.38 |
37
-
| - Total Cash | 753.34 |
38
-
| Savings ||
39
-
| - Spouse Savings | 987.12 |
40
-
| - Family Savings | 3250 |
41
-
| - Total Savings | 4237.12 |
42
-
| Property ||
43
-
| - 2012 Silverado | 30975 |
44
-
| - 2012 Camper | 0 |
45
-
| - Total Property | 39975 |
46
-
| Total Assets | 44965.46 |
47
-
| Liabilities ||
48
-
| Credit Card ||
49
-
| - Apple Card | 0 |
50
-
| - Credit Card | -973.4 |
51
-
| - Total Credit Card | -973.4 |
52
-
| Loan ||
53
-
| - Student Loan | -10500 |
54
-
| - Total Loan | -10650 |
55
-
| Total Liabilities | -11623 | ~~ |
41
+
| Assets ||
42
+
| Cash ||
43
+
| - Cash | 77.12 |
44
+
| - Checking One | 440.84 |
45
+
| - Checking Two | 235.38 |
46
+
| - Total Cash | 753.34 |
47
+
| Savings ||
48
+
| - Spouse Savings | 987.12 |
49
+
| - Family Savings | 3250 |
50
+
| - Total Savings | 4237.12 |
51
+
| Property ||
52
+
| - 2012 Silverado | 30975 |
53
+
| - 2012 Camper | 0 |
54
+
| - Total Property | 39975 |
55
+
| Total Assets | 44965.46 |
56
+
| Liabilities ||
57
+
| Credit Card ||
58
+
| - Apple Card | 0 |
59
+
| - Credit Card | -973.4 |
60
+
| - Total Credit Card | -973.4 |
61
+
| Loan ||
62
+
| - Student Loan | -10500 |
63
+
| - Total Loan | -10650 |
64
+
| Total Liabilities | -11623 ||
65
+
~~
56
66
57
67
_Move2GnuCash_ function `opening_book` retrieves the date (balances as of close of business) from the first line. The second line, because it has no associated figure in the second column, will be created as a [placeholder account](https://www.gnucash.org/docs/v4/C/gnucash-help/acct-create.html#accts-placeholder) and will be the parent of the next account created, and so on, until the accounts containing transactions are created (the hyphens will be removed).
58
68
@@ -97,7 +107,7 @@ TODO: Finish this documenting.
97
107
98
108
GnuCash uses [double entry accounting](https://www.investopedia.com/terms/d/double-entry.asp). PieCash uses the term splits to refer to these particulars in a [transaction](https://piecash.readthedocs.io/en/master/tutorial/index_new.html#creating-a-new-transaction), which can be confusing for those used to Quicken, and perhaps Mint.
99
109
100
-
Move-to-GnuCash will map CSV entries and account for splits by creating multi-split transactions for GnuCash.
110
+
_Move2GnuCash_ will map CSV entries to account for splits by creating multi-split transactions for GnuCash.
101
111
102
112
For example, consider this csv file which would reflect an expense in Quicken where \$11.50 is charged to the Dining category and \$0.95 reflects the sales tax charged by the state:
103
113
@@ -106,7 +116,7 @@ For example, consider this csv file which would reflect an expense in Quicken wh
106
116
| S | 01/22/2023 | Payment/Deposit | Breakfast Place | Dining | -10.55 | My Credit Card |
107
117
| S | 01/22/2023 | Payment/Deposit | Breakfast Place | Sales Tax | -0.95 | My Credit Card |
108
118
109
-
GnuCash treats categories as just another account. When the transaction is created by PieCash, it will include three splits in order to capture the changes to all three accounts. Extending the idea presented in the PieCash tutorial examples, it might look like this:
119
+
GnuCash treats categories as just another account. When the transaction is created by _Move2GnuCash_/PieCash, it will include three splits in order to capture the changes to all three accounts. Extending the idea presented in the PieCash tutorial examples, it might look like this:
0 commit comments