Re: [GNC] difficulties with managing accounts with lots of split transactions
On 12/28/2021 5:39 PM, Adrien Monteleone wrote: Personally I use #2 as Transaction Journal & Double Line mode 24/7. The always visible detail doesn't bother me and I generally like to have it instantly available without having to change modes, but I understand mileage varies. Regards, Adrien And of course those of us who learned bookkeeping in the old pen and ink on paper days find this perfectly familiar. We first entered a transaction in the "journal" and then later posted it to the affected "ledger" accounts. So if you use #2 you can think of gnucash as if it were old fashioned bookkeeping EXCEPT that posting is automatic and free from error (transcription errors during posting were the bane of every bookkeeper in those days). It is possible that those new to gnucash but familiar with the old "first enter into the journal" might actually have a shorter learning curve using #2. Michael D Novack ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] difficulties with managing accounts with lots of split transactions
Personally I use #2 as Transaction Journal & Double Line mode 24/7. The always visible detail doesn't bother me and I generally like to have it instantly available without having to change modes, but I understand mileage varies. Regards, Adrien On 11/7/21 6:08 AM, Platon Pronko wrote: Hi! I currently find it a bit difficult to handle multi-split transactions that include several "splits" going to the same account. For example, if I'm buying some computer hardware I want to record the prices of each part for later reference, but all those parts are recorded in "Hardware" account - thus several splits go into the same account. In default "Basic Ledger" view this is shown in a confusing way - each split gets its own row, but each row displays the same transaction description (not the name of the individual part). For the moment I explored several different solutions to this situation: 1. Record each item (hardware part in this example) as a separate transaction. This solves the issue with display since I can now put each item name into the description field. But now I have multiple transactions my credit card account, which would make reliable reconciliation almost impossible. 2. Use the "Transaction Journal" view. It handles this situation a bit better than "Basic Ledger" - the rows are not duplicated. But it show all the splits, even the ones not related to the currently viewed account, and the simple two-split transactions start taking 3 rows each, which is too verbose, especially since this is a global setting. 3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the code patch that does it, applies to version 4.8). This works quite nicely - simple transactions keep using one row, complex transactions display only the splits related to the current register and each split shows its memo right in the register. However this is a code customization, won't help anybody else with similar problems, and maintaining it is going to be more difficult than built-in solutions. Do you have any suggestions about a better way of handling this? ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] difficulties with managing accounts with lots of split transactions
Thanks for the tip about hotkeys, that's quite useful (I was longing for a way to toggle splits for a long time). Best regards, Platon Pronko On 2021-11-07 16:16, david whiting wrote: I've set up hotkeys for the different views that gnucash has and I find it helpful for this sort of thing. It allows me to quickly switch between different views. ctrl+1: basic view ctrl+2: auto-split view (all splits for current transaction) ctrl+3: transaction journal view (all splits for all transactions) ctrl+4: toggle double line view (to see transaction notes) Here's how to set it up: https://lists.gnucash.org/pipermail/gnucash-user/2020-August/092757.html David On Sun, 7 Nov 2021 at 12:09, Platon Pronko wrote: Hi! I currently find it a bit difficult to handle multi-split transactions that include several "splits" going to the same account. For example, if I'm buying some computer hardware I want to record the prices of each part for later reference, but all those parts are recorded in "Hardware" account - thus several splits go into the same account. In default "Basic Ledger" view this is shown in a confusing way - each split gets its own row, but each row displays the same transaction description (not the name of the individual part). For the moment I explored several different solutions to this situation: 1. Record each item (hardware part in this example) as a separate transaction. This solves the issue with display since I can now put each item name into the description field. But now I have multiple transactions my credit card account, which would make reliable reconciliation almost impossible. 2. Use the "Transaction Journal" view. It handles this situation a bit better than "Basic Ledger" - the rows are not duplicated. But it show all the splits, even the ones not related to the currently viewed account, and the simple two-split transactions start taking 3 rows each, which is too verbose, especially since this is a global setting. 3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the code patch that does it, applies to version 4.8). This works quite nicely - simple transactions keep using one row, complex transactions display only the splits related to the current register and each split shows its memo right in the register. However this is a code customization, won't help anybody else with similar problems, and maintaining it is going to be more difficult than built-in solutions. Do you have any suggestions about a better way of handling this? Best regards, Platon Pronko___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] difficulties with managing accounts with lots of split transactions
Storing the info simply in the notes (or in a scan) feels a bit unstructured - harder to analyze later. But I didn't know about ability to attach a link to the transaction, that might be handy later - thanks for the tip. Best regards, Platon Pronko On 2021-11-07 16:13, Derek Atkins wrote: Use a vendor invoice to record it.. Or scan the receipt and attach it.. Or put the info into the notes... Or.. Lots of options. -derek Sent using my mobile device. Please excuse any typos. On November 7, 2021 7:10:42 AM Platon Pronko wrote: Hi! I currently find it a bit difficult to handle multi-split transactions that include several "splits" going to the same account. For example, if I'm buying some computer hardware I want to record the prices of each part for later reference, but all those parts are recorded in "Hardware" account - thus several splits go into the same account. In default "Basic Ledger" view this is shown in a confusing way - each split gets its own row, but each row displays the same transaction description (not the name of the individual part). For the moment I explored several different solutions to this situation: 1. Record each item (hardware part in this example) as a separate transaction. This solves the issue with display since I can now put each item name into the description field. But now I have multiple transactions my credit card account, which would make reliable reconciliation almost impossible. 2. Use the "Transaction Journal" view. It handles this situation a bit better than "Basic Ledger" - the rows are not duplicated. But it show all the splits, even the ones not related to the currently viewed account, and the simple two-split transactions start taking 3 rows each, which is too verbose, especially since this is a global setting. 3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the code patch that does it, applies to version 4.8). This works quite nicely - simple transactions keep using one row, complex transactions display only the splits related to the current register and each split shows its memo right in the register. However this is a code customization, won't help anybody else with similar problems, and maintaining it is going to be more difficult than built-in solutions. Do you have any suggestions about a better way of handling this? Best regards, Platon Pronko -- ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] difficulties with managing accounts with lots of split transactions
I've set up hotkeys for the different views that gnucash has and I find it helpful for this sort of thing. It allows me to quickly switch between different views. ctrl+1: basic view ctrl+2: auto-split view (all splits for current transaction) ctrl+3: transaction journal view (all splits for all transactions) ctrl+4: toggle double line view (to see transaction notes) Here's how to set it up: https://lists.gnucash.org/pipermail/gnucash-user/2020-August/092757.html David On Sun, 7 Nov 2021 at 12:09, Platon Pronko wrote: > > Hi! > > I currently find it a bit difficult to handle multi-split transactions that > include several "splits" going to the same account. For example, if I'm > buying some computer hardware I want to record the prices of each part for > later reference, but all those parts are recorded in "Hardware" account - > thus several splits go into the same account. > > In default "Basic Ledger" view this is shown in a confusing way - each split > gets its own row, but each row displays the same transaction description (not > the name of the individual part). > > For the moment I explored several different solutions to this situation: > > 1. Record each item (hardware part in this example) as a separate > transaction. This solves the issue with display since I can now put each item > name into the description field. But now I have multiple transactions my > credit card account, which would make reliable reconciliation almost > impossible. > > 2. Use the "Transaction Journal" view. It handles this situation a bit better > than "Basic Ledger" - the rows are not duplicated. But it show all the > splits, even the ones not related to the currently viewed account, and the > simple two-split transactions start taking 3 rows each, which is too verbose, > especially since this is a global setting. > > 3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the > code patch that does it, applies to version 4.8). This works quite nicely - > simple transactions keep using one row, complex transactions display only the > splits related to the current register and each split shows its memo right in > the register. However this is a code customization, won't help anybody else > with similar problems, and maintaining it is going to be more difficult than > built-in solutions. > > Do you have any suggestions about a better way of handling this? > > Best regards, > Platon Pronko___ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > - > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. -- David Whiting ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
Re: [GNC] difficulties with managing accounts with lots of split transactions
Use a vendor invoice to record it.. Or scan the receipt and attach it.. Or put the info into the notes... Or.. Lots of options. -derek Sent using my mobile device. Please excuse any typos. On November 7, 2021 7:10:42 AM Platon Pronko wrote: Hi! I currently find it a bit difficult to handle multi-split transactions that include several "splits" going to the same account. For example, if I'm buying some computer hardware I want to record the prices of each part for later reference, but all those parts are recorded in "Hardware" account - thus several splits go into the same account. In default "Basic Ledger" view this is shown in a confusing way - each split gets its own row, but each row displays the same transaction description (not the name of the individual part). For the moment I explored several different solutions to this situation: 1. Record each item (hardware part in this example) as a separate transaction. This solves the issue with display since I can now put each item name into the description field. But now I have multiple transactions my credit card account, which would make reliable reconciliation almost impossible. 2. Use the "Transaction Journal" view. It handles this situation a bit better than "Basic Ledger" - the rows are not duplicated. But it show all the splits, even the ones not related to the currently viewed account, and the simple two-split transactions start taking 3 rows each, which is too verbose, especially since this is a global setting. 3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the code patch that does it, applies to version 4.8). This works quite nicely - simple transactions keep using one row, complex transactions display only the splits related to the current register and each split shows its memo right in the register. However this is a code customization, won't help anybody else with similar problems, and maintaining it is going to be more difficult than built-in solutions. Do you have any suggestions about a better way of handling this? Best regards, Platon Pronko -- ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. ___ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. - Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
[GNC] difficulties with managing accounts with lots of split transactions
Hi!
I currently find it a bit difficult to handle multi-split transactions that include several
"splits" going to the same account. For example, if I'm buying some computer hardware I
want to record the prices of each part for later reference, but all those parts are recorded in
"Hardware" account - thus several splits go into the same account.
In default "Basic Ledger" view this is shown in a confusing way - each split
gets its own row, but each row displays the same transaction description (not the name of
the individual part).
For the moment I explored several different solutions to this situation:
1. Record each item (hardware part in this example) as a separate transaction.
This solves the issue with display since I can now put each item name into the
description field. But now I have multiple transactions my credit card account,
which would make reliable reconciliation almost impossible.
2. Use the "Transaction Journal" view. It handles this situation a bit better than
"Basic Ledger" - the rows are not duplicated. But it show all the splits, even the ones
not related to the currently viewed account, and the simple two-split transactions start taking 3
rows each, which is too verbose, especially since this is a global setting.
3. Show "memo" as a separate column in "Basic Ledger" view (I've attached the
code patch that does it, applies to version 4.8). This works quite nicely - simple transactions
keep using one row, complex transactions display only the splits related to the current register
and each split shows its memo right in the register. However this is a code customization, won't
help anybody else with similar problems, and maintaining it is going to be more difficult than
built-in solutions.
Do you have any suggestions about a better way of handling this?
Best regards,
Platon PronkoAdd a memo column after description column.
diff --git a/gnucash/register/ledger-core/split-register-layout.c b/gnucash/register/ledger-core/split-register-layout.c
index 6f7f2bef9..6fbc14789 100644
--- a/gnucash/register/ledger-core/split-register-layout.c
+++ b/gnucash/register/ledger-core/split-register-layout.c
@@ -93,20 +93,21 @@ gnc_split_register_set_cells (SplitRegister* reg, TableLayout* layout)
gnc_table_layout_set_cell (layout, curs, DATE_CELL, 0, 0);
gnc_table_layout_set_cell (layout, curs, NUM_CELL, 0, 1);
gnc_table_layout_set_cell (layout, curs, DESC_CELL, 0, 2);
-gnc_table_layout_set_cell (layout, curs, MXFRM_CELL, 0, 3);
-gnc_table_layout_set_cell (layout, curs, RECN_CELL, 0, 4);
+gnc_table_layout_set_cell (layout, curs, MEMO_CELL, 0, 3);
+gnc_table_layout_set_cell (layout, curs, MXFRM_CELL, 0, 4);
+gnc_table_layout_set_cell (layout, curs, RECN_CELL, 0, 5);
if (reg->is_template)
{
-gnc_table_layout_set_cell (layout, curs, FDEBT_CELL, 0, 5);
-gnc_table_layout_set_cell (layout, curs, FCRED_CELL, 0, 6);
+gnc_table_layout_set_cell (layout, curs, FDEBT_CELL, 0, 6);
+gnc_table_layout_set_cell (layout, curs, FCRED_CELL, 0, 7);
}
else
{
-gnc_table_layout_set_cell (layout, curs, DEBT_CELL, 0, 5);
-gnc_table_layout_set_cell (layout, curs, CRED_CELL, 0, 6);
+gnc_table_layout_set_cell (layout, curs, DEBT_CELL, 0, 6);
+gnc_table_layout_set_cell (layout, curs, CRED_CELL, 0, 7);
}
-gnc_table_layout_set_cell (layout, curs, BALN_CELL, 0, 7);
-gnc_table_layout_set_cell (layout, curs, RATE_CELL, 0, 8);
+gnc_table_layout_set_cell (layout, curs, BALN_CELL, 0, 8);
+gnc_table_layout_set_cell (layout, curs, RATE_CELL, 0, 9);
curs_last = curs;
curs = gnc_table_layout_get_cursor (layout,
@@ -135,10 +136,10 @@ gnc_split_register_set_cells (SplitRegister* reg, TableLayout* layout)
gnc_table_layout_set_cell (layout, curs, DATE_CELL, 0, 0);
gnc_table_layout_set_cell (layout, curs, NUM_CELL, 0, 1);
gnc_table_layout_set_cell (layout, curs, DESC_CELL, 0, 2);
-gnc_table_layout_set_cell (layout, curs, TDEBT_CELL, 0, 5);
-gnc_table_layout_set_cell (layout, curs, TCRED_CELL, 0, 6);
-gnc_table_layout_set_cell (layout, curs, TBALN_CELL, 0, 7);
-gnc_table_layout_set_cell (layout, curs, RATE_CELL, 0, 8);
+gnc_table_layout_set_cell (layout, curs, TDEBT_CELL, 0, 6);
+gnc_table_layout_set_cell (layout, curs, TCRED_CELL, 0, 7);
+gnc_table_layout_set_cell (layout, curs, TBALN_CELL, 0, 8);
+gnc_table_layout_set_cell (layout, curs, RATE_CELL, 0, 9);
curs_last = curs;
curs = gnc_table_layout_get_cursor (layout,
@@ -165,19 +166,19 @@ gnc_split_register_set_cells (SplitRegister* reg, TableLayout* layout)
gnc_table_layout_set_cell (layout, curs, ACTN_CELL, 0, 1);
gnc_table_layout_set_cell (layout, curs, MEMO_CELL,
