Re: [GNC] Forward payments
You can edit the transfer into the expense account and change the recipient to be the asset acct. You will get a warning that you are changing a reconciled transaction but it will not affect the reconcile (just make sure you don't change the amount transferred). Colin On 29 June 2018 at 04:34, Tony Vanson wrote: > My thanks to all respondents. It is finally making sense to my befuddled > brain. > However I have one more spanner in the works. I had already transferred > funds from my Current Assets:Bank account to Expenses:Staff. > My Bank account has been reconciled. > What, if any, process is available to transfer the forward payment funds > from Expenses:Staff to the newly created Current Assets:Forward Payment > Credit account without messing things up, or would I need to delete the > original transfer and re-enter it to reflect the new process? > Thanks again for all your patience. > Cheers > > > On Fri, Jun 29, 2018 at 12:13 AM, Stephen M. Butler wrote: > >> On 06/28/2018 12:25 AM, Tony Vanson wrote: >> > Thank you for your quick response. My Staff account is set up as an >> Expense >> > not as an Asset. In this particular case would I need to set up a new >> > account Current Assets:Staff - as a child account under Current Assets? >> > Cheers >> >> I would set it up as an asset. Even if you physically handed them the >> cash and they physically put it into their wallet for future >> disbursement as needed, it is still your asset. If anything is left >> over when you return it would come back to you for put back into the bank. >> >> I presume you will get periodic statements about how that asset is being >> disbursed so you can make the appropriate entries to transfer funds to >> the appropriate expense accounts (just like you do now, except the asset >> side is not the bank but the "staff accountant"). >> >> That way you could notice if the funds were running short and do online >> banking to send more funds to that person. >> > On Thu, Jun 28, 2018 at 2:08 PM, Maf. King wrote: >> > >> >> On Thursday, 28 June 2018 07:53:02 BST Tony Vanson wrote: >> >>> Hi all, >> >>> Hopefully someone can advise me how to treat the following problem >> which >> >>> stumps me. >> >>> I am using GNUcash 2.6.18 on Windows 10. >> >>> I shall be away for several months and have transferred credit from my >> >>> Savings account to my Staff account with a lump sum amount for her to >> pay >> >>> her Salary, Electricity, Pool chemicals, Internet access etc, on the >> due >> >>> date. All these are set up as expense accounts. >> >>> All accounts, apart from her Salary and Internet access, are variable >> in >> >>> amount and payment date. >> >>> I assume that I have to split the lump sum to the various accounts as >> >> they >> >>> are paid or is there some other method? >> >>> I also need to take into account that the payment I've made to the >> Staff >> >>> account may be too small or too large. >> >>> Any enlightenment to a personally perplexing problem would be greatly >> >>> appreciated. >> >>> P.S. I only use GNUcash for my personal information and does not have >> any >> >>> taxation or other legal requirement. >> >>> Cheers >> >> Hi Tony. >> >> >> >> Do you have accounts in GC that represent your Savings account & Staff >> >> accounts? >> >> >> >> To me it seems that you should let GC reflect reality - you've got a >> >> transaction from Assets:Savings to Assets:StaffAccount. as the payments >> >> are >> >> made, you have transactions between Assets:StaffAccount & expense >> accounts >> >> as >> >> appropriate. (presumably, you could be emailed details of payments made >> to >> >> keep your GC up to date?) >> >> >> >> If, on your return, you have balance left in Assets:StaffAccount, just >> >> record >> >> a transaction putting it back into savings. >> >> >> >> HTH, >> >> Maf. >> >> >> >> >> >> >> >> >> >> >> > >> >> ___ >> 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. >> > > > > -- > *Tony Vanson* > > *The older I get,* > *the better I was* > ___ > 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 sub
Re: [GNC] GnuCash 3.2 Released
Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: > Further research: > > It appears that net-charts.scm is a replacement for two other files in > standard-reports: net-linecharts.scm and net-barcharts.scm > > I renamed those two to have a .old extension on them and GnuCash now > starts up without complaining about duplicate report IDs. > Ah indeed. As you indicated you didn't uninstall first, the old files remained in the installation directory causing the conflict. The formal way to uninstall is a bit picky. You should run "make uninstall" in your build directory *before* changing the source directory to a newer version (be it a new git checkout or pull, or installing a new release tar ball). If you installed gnucash in it's own prefix (by adding -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy as deleting this prefix. But in this case manually removing/renaming the offending files works as well. I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/ scm/ccache/ directory as well though. Geert > > Stephen M Butler, PMP, PSM > stephen.m.butle...@gmail.com > kg...@arrl.net > 253-350-0166 > --- > GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8 > > On 06/25/2018 10:20 AM, Stephen M. Butler wrote: > > Compiled and installed on Ubuntu 18.04. > > > > When starting up it reports several duplicate report IDs. Should I have > > uninstalled 3.1 first? I did these commands (with an empty mybuild): > > > > cd mybuild > > > > cmake ../gnucash-3.2 > > > > make > > > > sudo make install > > > > > > Stephen M Butler, PMP, PSM > > stephen.m.butle...@gmail.com > > kg...@arrl.net > > 253-350-0166 > > --- > > GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8 > > > > On 06/24/2018 08:40 PM, John Ralls wrote: > >> The GnuCash development team announces GnuCash 3.2, the second release of > >> the 3.x stable release series. > >> > >> Changes > >> > >> Between 3.0 and 3.2, the following bugfixes were accomplished: > >>• Bug 787401 - Test Report System - Report Definition. > >>• Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to > >>scm-gnome-utils. > >>• Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers the > >>check boxes. • Bug 795247 - datepicker broken in Persian. GnuCash > >>passes dates as integer y/m/d without using locale-specific formats, so > >>we need to strip out 'E' and 'O' from the format when scanning dates or > >>determining separators in gnc-date. None of '-', 'E', or 'O' are > >>supported by boost (and '-' causes errors), so strip them out from > >>formatters in gnc-datetime as well. • Bug 795253 - Have problems input > >>Chinese. > >>• Bug 795272 - QIF importer causes application crash if action is > >>invalid. > >>• Bug 795276 - Invalid date on price stops file from being parsed. > >>• Bug 795362 - Special variable "i" not parsed in function calls. Due to > >>balance tests with insane random values. • Bug 795471 - Impossible to > >>Edit Budget Unless Maximized. > >>• Bug 795519 - Credit card payment after reconciliation. > >>• Bug 795666 - Backslash '\' in Description field spoils CSV Import > >>without helpful error message. • Bug 795831 - When read only threshold > >>set, dates are silently changed. Display a message box informing the > >>user of the change. • Bug 795944 - Cannot store change to Business > >>Suppliers data. > >>• Bug 796079 - Repeatable Crash in Tax Report Options. > >>• Bug 796081 - Tax Schedule Report - An error occurred while running the > >>report. • Bug 796083 - Reconcile Selection Doesn't Work Anymore. > >>• Bug 796117 - Connecting 3.1 to an existing mysql db drops all data. > >>Provide a backup recovery function that instead of dropping primaries > >>and restoring backups merges the primaries and backups. This should > >>handle a worst-case safe-save failure where the backup tables don't > >>have a complete set of rows for some reason. • Bug 796256 - Main Window > >>stays hidden when starting after closing main window while minimized. • > >>Bug 796369 - Notes lost or perhaps just not displaying when using > >>SQLite backend. This bug caused data loss if you saved your SQLite3 > >>database to a different file or database. The problem is that in > >>SQLite3 (though not in MySQL or PgSQL) the subquery ((SELECT DISTINCT > >>guid FROM transactions)) (note the double parentheses) returns only the > >>first guid in the subquery's results. Some transactions are loaded by > >>special queries and those queries are also used to retrieve the > >>transaction's slots so they weren't affected. • Bug 796398 - Restrict > >>accelerator keys to valid date range. > >>• Bug 796409 - Incorrect Curre
Re: [GNC] GnuCash 3.2 Released
Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West: > I'm sure you like to get feedback from someone with absolutely no > problems at all. > > I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my > standby testbed (both on Win 10.1803). I finally decided to take the > plunge and upgraded my primary computer form 2.6.21 to 3.2. The > experience was flawless and now my testbed pc is eagerly awaiting vs 4.0. > > Dennis Dennis, That's nice to hear :) Geert ___ 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] was: Rethinking the placeholder account concept Re: Fwd: The two modules
Op donderdag 28 juni 2018 22:48:16 CEST schreef D: > On June 28, 2018, at 1:12 PM, Geert Janssens wrote: > >Op donderdag 28 juni 2018 18:47:18 CEST schreef Stephen M. Butler: > [Snip] > > >> Maybe the financial folks can band together to get the developers to > >> enforce no-transactions to a parent account. > > > >I think we should modify the concepts. "Placeholder" is ambiguous and for > >the lack of a better solution is has been abused to make existing accounts > >read- only.I > > I am under the impression that the placeholder setting is only meant to make > an account read-only, so saying that users have "abused" this seems > incorrect. We've used the tool we've been given. "Abused" was probably a poor choice of words. I meant no offense. I merely wanted to clarify the "placeholder" feature is IMO used in ways it was not initially intended. If it was only meant be make an account read-only, it would have been named "read only" :) It was named "placeholder" though and IMO it was originally intended to be used for hierarchical organization of accounts. I even guess it was a design oversight that an account with transactions could be made a placeholder. This oversight made it a convenient proxy for marking an account a placeholder account. And it looks like it's even the more common and promoted use case right now. I'm completely fine with that in itself. On the other hand the double use of this option is causing unnecessary confusion which is why I am proposing to clear this out somewhere in the future. > >Perhaps it's time to introduce a "View" type account which is only used to > >structure the account tree (and as aggregate account in reports) and next > >to that introduce a read-only attribute to normal accounts. Placeholder > >could then be phased out in favor of these two. We could even try to > >automate this using some heuristics: > >- if a placeholder account has no transactions, convert it into a view > >account - if a placeholder account does have transactions, make it > >read-only instead. Add in an informational message to the user about what > >was done so the user can make corrections if needed (like adding view > >accounts if an account was being used for both functions). > >Geert > > You might even call a View account "Closed," or are there other reasons an > account might behave this way? > That's not what I meant with "View". The way I intend this is it's not even really an account. It's merely an element that helps organize the account hierarchy. Closed to me suggests it can also be "open" under other conditions. It can't. It's permanently empty and won't ever take any splits. The only property it has is it's balance which is the sum of all its children's balances. Internally this is a calculated value though, not stored. But that's a technical detail. > I'd also add that eliminating these accounts from drop down controls should > go along with the changes, but assume that would be implied from the fact > that Placeholder accounts don't appear there currently. Agreed. A structural "view" account would only serve in the global account hierarchy and on reports. As one can't use them to store splits, they never make sense in dropdowns. Geert ___ 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] Fwd: The two modules
Hi David It'd seem the Frozen status relates to transaction status (Unreconciled/Cleared/Reconciled/Void/Frozen) only, and is so far unused. I'm going to amend the balsheet-pnl to the desired format. This means the accounts are shown sequentially, and *every* account will also include children amounts, no exceptions. This means Expense:Household will always reflect total household spending. If an account has sub-accounts, then the account's own amount will be shown first, if it exists, followed by the children amounts. If any child account has amount & child accounts, the child total amount shown first, then the child own amount (if any), followed by the grandchildren amounts. This seems to be desired approach. The separate-row multilevel subtotals will be completely disabled & removed. On 29/06/18 02:34, David Carlson wrote: Is the 'frozen' status which is already in place but seemingly unused supposed to be for this purpose? David C On Thu, Jun 28, 2018, 12:31 PM John Ralls wrote: On Jun 28, 2018, at 10:10 AM, Geert Janssens wrote: Op donderdag 28 juni 2018 18:47:18 CEST schreef Stephen M. Butler: On 06/27/2018 04:41 PM, DaveC49 wrote: An active non-placeholder account should not have child/subaccounts, although I don't think GnuCash actually prevents this. In this case, the parent account total is the sum of the child subaccount totals plus the sum of any transactions into the parent account itself. This will make a report look to be incorrect as the sum of transactions into the parent account is not presented separately and its total will not be the sum of the child account totals. I can't think of a use case where this would be desirable, but some people may be happy with that behavior. I don't think this behavior has changed since I first checked it out in an earlier version (around 2.2 I think). This is a problem. In a good report the parent with transactions should show a line for the parent so that the column total for that parent (on the balance sheet) is correct. This seems to make most sense to me: If a parent has transactions put it twice: Once as aggregate account and once as an account on it's own. That would meet both needs. The aggregate will total it's own transactions with those of its child accounts. Or put differently the aggregate account would treat itself as a child account. +1 At least, as a former IT software development manager, I would insist that a column total show all of it's inputs. Maybe the financial folks can band together to get the developers to enforce no-transactions to a parent account. I think we should modify the concepts. "Placeholder" is ambiguous and for the lack of a better solution is has been abused to make existing accounts read- only. Perhaps it's time to introduce a "View" type account which is only used to structure the account tree (and as aggregate account in reports) and next to that introduce a read-only attribute to normal accounts. Placeholder could then be phased out in favor of these two. We could even try to automate this using some heuristics: - if a placeholder account has no transactions, convert it into a view account - if a placeholder account does have transactions, make it read-only instead. Add in an informational message to the user about what was done so the user can make corrections if needed (like adding view accounts if an account was being used for both functions). I propose that we combine “placeholder” and “hidden” to “inactive” which removes an account from the picker list and from the Accounts page unless “show inactive accounts” is selected from the filter. While marking an account “placeholder” prevents adding transactions to it, there’s no requirement in GnuCash that an account with children have the placeholder flag set. To strictly follow David Cousen’s advice we’d have to impose that restriction, but some users might find that a bit drastic. Perhaps we could make it a book option? Regards, John Ralls ___ 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. ___ gnucash-user mailing list gnucash-user
[GNC] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
Op donderdag 28 juni 2018 19:27:47 CEST schreef John Ralls: > > On Jun 28, 2018, at 10:10 AM, Geert Janssens > > wrote:> > > Op donderdag 28 juni 2018 18:47:18 CEST schreef Stephen M. Butler: > >> On 06/27/2018 04:41 PM, DaveC49 wrote: > >>> An active non-placeholder account should not have child/subaccounts, > >>> although I don't think GnuCash actually prevents this. In this case, the > >>> parent account total is the sum of the child subaccount totals plus the > >>> sum > >>> of any transactions into the parent account itself. This will make a > >>> report > >>> look to be incorrect as the sum of transactions into the parent account > >>> is > >>> not presented separately and its total will not be the sum of the child > >>> account totals. I can't think of a use case where this would be > >>> desirable, > >>> but some people may be happy with that behavior. I don't think this > >>> behavior has changed since I first checked it out in an earlier version > >>> (around 2.2 I think). > >> > >> This is a problem. In a good report the parent with transactions should > >> show a line for the parent so that the column total for that parent (on > >> the balance sheet) is correct. > > > > This seems to make most sense to me: > > If a parent has transactions put it twice: > > Once as aggregate account and once as an account on it's own. That would > > meet both needs. The aggregate will total it's own transactions with > > those of its child accounts. Or put differently the aggregate account > > would treat itself as a child account. > > +1 > > >> At least, as a former IT software development manager, I would insist > >> that a column total show all of it's inputs. > >> > >> Maybe the financial folks can band together to get the developers to > >> enforce no-transactions to a parent account. > > > > I think we should modify the concepts. "Placeholder" is ambiguous and for > > the lack of a better solution is has been abused to make existing > > accounts read- only. > > > > Perhaps it's time to introduce a "View" type account which is only used to > > structure the account tree (and as aggregate account in reports) and next > > to that introduce a read-only attribute to normal accounts. Placeholder > > could then be phased out in favor of these two. We could even try to > > automate this using some heuristics: > > - if a placeholder account has no transactions, convert it into a view > > account - if a placeholder account does have transactions, make it > > read-only instead. Add in an informational message to the user about what > > was done so the user can make corrections if needed (like adding view > > accounts if an account was being used for both functions). > > I propose that we combine “placeholder” and “hidden” to “inactive” which > removes an account from the picker list and from the Accounts page unless > “show inactive accounts” is selected from the filter. > Something to think about as well. So that would define "inactive" as "read- only" (placeholder) and "hidden". I think that aligns well with other uses of "Active", like for customers and vendors. I wonder whether there are use cases for a read-only flag or hidden flag other than marking an account as inactive. I'm trying to gauge the proper granularity here. Would one want to make an account just read-only so it appears in reports but can't be modified where an inactive account won't appear by default ? For "hidden" I think hiding can imply setting it read-only. So I don't think we need separation between "hidden" and "inactive". > While marking an account “placeholder” prevents adding transactions to it, > there’s no requirement in GnuCash that an account with children have the > placeholder flag set. To strictly follow David Cousen’s advice we’d have to > impose that restriction, but some users might find that a bit drastic. To clarify I am thinking of introducing an extra account type rather than continuing to use the placeholder flag. Although I'm proposing it in this context I have a wider scope in mind. It would also allow more freedom in restructuring account hierarchies. For example the European model of structuring a chart of accounts with Active vs Passive (where Passive is the subdivided in Liabilities and Equity) would become possible. And I don't know if we currently can enforce this. Isn't there something with stock accounts requiring a parent in the proper currency ? I'm not tracking stock so I don't know the details there. So at this point I would encourage where it makes sense. And set an example in our account hierarchy templates. Yet using ordinary accounts as parents would still be allowed. With or without the option to make them read-only. > Perhaps we could make it a book option? I like the idea of a book option. For existing books it would not be set. For new books it would be set by default. If a user sets it for an existing book gnucash can check if the account hierarchy is conform with th
Re: [GNC] Fwd: The two modules
Op donderdag 28 juni 2018 20:34:45 CEST schreef David Carlson: > Is the 'frozen' status which is already in place but seemingly unused > supposed to be for this purpose? > > David C I have no idea what the intent of that status is. Looks like yet another variant of this though. Geert ___ 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] How to regularly use two currencies
How to regularly use two currencies I would very much appreciate if somebody could help me to solve a problem. In GnuCash 2.6.19,on a Windows 10 computer, I made the following arrangements – but maybe my assumptions were wrong, as I cannot see the results I had hope for. I do not have much experience, so I dare to ask for advice and help. I live in Cambodia, where it is usual all over the country to use two currencies regularly: the Cambodian Riel, and the US$ (at normally 4000 Riel per Dollar). (In Tools, Price Editor, I have set Khmer Riels as the second currency in addition to US$.) I live on a farm, where, among other things, we produce, sell, and buy vegetables. Under Income, I created an account FARM, and under FARM an account SHOP, and under shop a Placeholder account VEGETABLES (currency USD). Under VEGETABLES I created a VEG$ sub-account for business in US dollars, and another sub-account VEGR for business in Riels. Now I enter all business actions into VEG$ or VEGR, either as Income or Charge, according to the currency used. After some entries, I can see the calculated result (gain or loss) in US$ in the Placeholder account VEGETABLES. I had hoped that the entries in VEGR would be transferred into US$ and also be part of the reported results in the placeholder account VEGETABLES – but this is not the case. Now my kind request: 1) please tell me if there is a way to get also the Riel values reflected in the Placeholder account above the VEGR; I had assumed that this should be possible with Placeholder accounts which are “intended to be used for hierarchical organization of accounts” - but maybe not when different currencies are involved? 2) please give me advice if all this is wrong – how could I handle our situation? Every purchase and sale has to be recorded in one of the two currencies. My hope was to get the overall results in US dollars in this way – and the goal remains the same: at the end of he day/week/month, I want to know how we did manage – all calculated in US$. Thanks for any help. Norbert KLEIN ___ 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] How to regularly use two currencies
Hi Norbert, I don't know the accounting customs of your country, so first a question: Is it common in Cambodia to *account* in two currencies as well or only to *pay* in two currencies ? Or put differently - do you want to track your income in the two currencies or just in one (hence the placeholder account) ? But you do want to be able to accept/make payments in the two currencies ? If you only want to accept/make payments in two currencies but just track it in one, the account structure would be slightly different. If you want to track your income in multiple currencies as you have set up, you'll need to make sure you have entries in your price database for conversion rates between USD and Cambodia Riel. Or more generally between your book's currency and the foreign currencies you trade in. Regards, Geert Op vrijdag 29 juni 2018 12:28:00 CEST schreef Norbert Klein: > How to regularly use two currencies > > I would very much appreciate if somebody could help me to solve a problem. > > In GnuCash 2.6.19,on a Windows 10 computer, I made the following > arrangements – but maybe my assumptions were wrong, as I cannot see the > results I had hope for. I do not have much experience, so I dare to ask > for advice and help. > > I live in Cambodia, where it is usual all over the country to use two > currencies regularly: the Cambodian Riel, and the US$ (at normally 4000 > Riel per Dollar). > > (In Tools, Price Editor, I have set Khmer Riels as the second currency > in addition to US$.) > > I live on a farm, where, among other things, we produce, sell, and buy > vegetables. > > Under Income, I created an account FARM, and under FARM an account SHOP, > and under shop a Placeholder account VEGETABLES (currency USD). Under > VEGETABLES I created a VEG$ sub-account for business in US dollars, and > another sub-account VEGR for business in Riels. > > Now I enter all business actions into VEG$ or VEGR, either as Income or > Charge, according to the currency used. > > After some entries, I can see the calculated result (gain or loss) in > US$ in the Placeholder account VEGETABLES. > > I had hoped that the entries in VEGR would be transferred into US$ and > also be part of the reported results in the placeholder account > VEGETABLES – but this is not the case. > > Now my kind request: > > 1) please tell me if there is a way to get also the Riel values > reflected in the Placeholder account above the VEGR; I had assumed that > this should be possible with Placeholder accounts which are “intended to > be used for hierarchical organization of accounts” - but maybe not when > different currencies are involved? > > 2) please give me advice if all this is wrong – how could I handle our > situation? Every purchase and sale has to be recorded in one of the two > currencies. > > My hope was to get the overall results in US dollars in this way – and > the goal remains the same: at the end of he day/week/month, I want to > know how we did manage – all calculated in US$. > > Thanks for any help. > > Norbert KLEIN > > ___ > 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] Forward payments
Thanks Colin That's done the trick. Cheers On Fri, Jun 29, 2018 at 2:15 PM, Colin Law wrote: > You can edit the transfer into the expense account and change the > recipient to be the asset acct. You will get a warning that you are > changing a reconciled transaction but it will not affect the reconcile > (just make sure you don't change the amount transferred). > > Colin > > On 29 June 2018 at 04:34, Tony Vanson wrote: > > My thanks to all respondents. It is finally making sense to my befuddled > > brain. > > However I have one more spanner in the works. I had already transferred > > funds from my Current Assets:Bank account to Expenses:Staff. > > My Bank account has been reconciled. > > What, if any, process is available to transfer the forward payment funds > > from Expenses:Staff to the newly created Current Assets:Forward Payment > > Credit account without messing things up, or would I need to delete the > > original transfer and re-enter it to reflect the new process? > > Thanks again for all your patience. > > Cheers > > > > > > On Fri, Jun 29, 2018 at 12:13 AM, Stephen M. Butler > wrote: > > > >> On 06/28/2018 12:25 AM, Tony Vanson wrote: > >> > Thank you for your quick response. My Staff account is set up as an > >> Expense > >> > not as an Asset. In this particular case would I need to set up a new > >> > account Current Assets:Staff - as a child account under Current > Assets? > >> > Cheers > >> > >> I would set it up as an asset. Even if you physically handed them the > >> cash and they physically put it into their wallet for future > >> disbursement as needed, it is still your asset. If anything is left > >> over when you return it would come back to you for put back into the > bank. > >> > >> I presume you will get periodic statements about how that asset is being > >> disbursed so you can make the appropriate entries to transfer funds to > >> the appropriate expense accounts (just like you do now, except the asset > >> side is not the bank but the "staff accountant"). > >> > >> That way you could notice if the funds were running short and do online > >> banking to send more funds to that person. > >> > On Thu, Jun 28, 2018 at 2:08 PM, Maf. King wrote: > >> > > >> >> On Thursday, 28 June 2018 07:53:02 BST Tony Vanson wrote: > >> >>> Hi all, > >> >>> Hopefully someone can advise me how to treat the following problem > >> which > >> >>> stumps me. > >> >>> I am using GNUcash 2.6.18 on Windows 10. > >> >>> I shall be away for several months and have transferred credit from > my > >> >>> Savings account to my Staff account with a lump sum amount for her > to > >> pay > >> >>> her Salary, Electricity, Pool chemicals, Internet access etc, on the > >> due > >> >>> date. All these are set up as expense accounts. > >> >>> All accounts, apart from her Salary and Internet access, are > variable > >> in > >> >>> amount and payment date. > >> >>> I assume that I have to split the lump sum to the various accounts > as > >> >> they > >> >>> are paid or is there some other method? > >> >>> I also need to take into account that the payment I've made to the > >> Staff > >> >>> account may be too small or too large. > >> >>> Any enlightenment to a personally perplexing problem would be > greatly > >> >>> appreciated. > >> >>> P.S. I only use GNUcash for my personal information and does not > have > >> any > >> >>> taxation or other legal requirement. > >> >>> Cheers > >> >> Hi Tony. > >> >> > >> >> Do you have accounts in GC that represent your Savings account & > Staff > >> >> accounts? > >> >> > >> >> To me it seems that you should let GC reflect reality - you've got a > >> >> transaction from Assets:Savings to Assets:StaffAccount. as the > payments > >> >> are > >> >> made, you have transactions between Assets:StaffAccount & expense > >> accounts > >> >> as > >> >> appropriate. (presumably, you could be emailed details of payments > made > >> to > >> >> keep your GC up to date?) > >> >> > >> >> If, on your return, you have balance left in Assets:StaffAccount, > just > >> >> record > >> >> a transaction putting it back into savings. > >> >> > >> >> HTH, > >> >> Maf. > >> >> > >> >> > >> >> > >> >> > >> >> > >> > > >> > >> ___ > >> 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. > >> > > > > > > > > -- > > *Tony Vanson* > > > > *The older I get,* > > *the better I was* > > ___ > > gnucash-user mailing list > > gnucash-user@gnucash.org > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinf
Re: [GNC] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
> On Jun 29, 2018, at 2:24 AM, Geert Janssens > wrote: > > Op donderdag 28 juni 2018 19:27:47 CEST schreef John Ralls: >>> On Jun 28, 2018, at 10:10 AM, Geert Janssens >>> wrote:> >>> Op donderdag 28 juni 2018 18:47:18 CEST schreef Stephen M. Butler: On 06/27/2018 04:41 PM, DaveC49 wrote: > An active non-placeholder account should not have child/subaccounts, > although I don't think GnuCash actually prevents this. In this case, the > parent account total is the sum of the child subaccount totals plus the > sum > of any transactions into the parent account itself. This will make a > report > look to be incorrect as the sum of transactions into the parent account > is > not presented separately and its total will not be the sum of the child > account totals. I can't think of a use case where this would be > desirable, > but some people may be happy with that behavior. I don't think this > behavior has changed since I first checked it out in an earlier version > (around 2.2 I think). This is a problem. In a good report the parent with transactions should show a line for the parent so that the column total for that parent (on the balance sheet) is correct. >>> >>> This seems to make most sense to me: >>> If a parent has transactions put it twice: >>> Once as aggregate account and once as an account on it's own. That would >>> meet both needs. The aggregate will total it's own transactions with >>> those of its child accounts. Or put differently the aggregate account >>> would treat itself as a child account. >> >> +1 >> At least, as a former IT software development manager, I would insist that a column total show all of it's inputs. Maybe the financial folks can band together to get the developers to enforce no-transactions to a parent account. >>> >>> I think we should modify the concepts. "Placeholder" is ambiguous and for >>> the lack of a better solution is has been abused to make existing >>> accounts read- only. >>> >>> Perhaps it's time to introduce a "View" type account which is only used to >>> structure the account tree (and as aggregate account in reports) and next >>> to that introduce a read-only attribute to normal accounts. Placeholder >>> could then be phased out in favor of these two. We could even try to >>> automate this using some heuristics: >>> - if a placeholder account has no transactions, convert it into a view >>> account - if a placeholder account does have transactions, make it >>> read-only instead. Add in an informational message to the user about what >>> was done so the user can make corrections if needed (like adding view >>> accounts if an account was being used for both functions). >> >> I propose that we combine “placeholder” and “hidden” to “inactive” which >> removes an account from the picker list and from the Accounts page unless >> “show inactive accounts” is selected from the filter. >> > Something to think about as well. So that would define "inactive" as "read- > only" (placeholder) and "hidden". I think that aligns well with other uses of > "Active", like for customers and vendors. > > I wonder whether there are use cases for a read-only flag or hidden flag > other > than marking an account as inactive. I'm trying to gauge the proper > granularity here. > Would one want to make an account just read-only so it appears in reports but > can't be modified where an inactive account won't appear by default ? > For "hidden" I think hiding can imply setting it read-only. So I don't think > we need separation between “hidden" and "inactive". > >> While marking an account “placeholder” prevents adding transactions to it, >> there’s no requirement in GnuCash that an account with children have the >> placeholder flag set. To strictly follow David Cousen’s advice we’d have to >> impose that restriction, but some users might find that a bit drastic. > > To clarify I am thinking of introducing an extra account type rather than > continuing to use the placeholder flag. Although I'm proposing it in this > context I have a wider scope in mind. It would also allow more freedom in > restructuring account hierarchies. For example the European model of > structuring a chart of accounts with Active vs Passive (where Passive is the > subdivided in Liabilities and Equity) would become possible. > > And I don't know if we currently can enforce this. Isn't there something with > stock accounts requiring a parent in the proper currency ? I'm not tracking > stock so I don't know the details there. > > So at this point I would encourage where it makes sense. And set an example > in > our account hierarchy templates. Yet using ordinary accounts as parents would > still be allowed. With or without the option to make them read-only. Stock accounts need to have a parent denominated the currency in which the stock trades in order for the asset roll-up to w
Re: [GNC] was: Rethinking the placeholder account concept Re: Fwd: The two modules
> On Jun 29, 2018, at 1:31 AM, Geert Janssens > wrote: > Agreed. A structural "view" account would only serve in the global account > hierarchy and on reports. As one can't use them to store splits, they never > make sense in dropdowns. Well, they never appear as terminal elements in the dropdown, but they’ll be part of a selectable account’s hierarchy, right? e.g. Assets:Current Assets:Bank of America:Savings, where only Savings is an actual account and the other three are “Views”. Regards, John Ralls ___ 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] GnuCash 3.2 Released
> On Jun 29, 2018, at 12:42 AM, Geert Janssens > wrote: > > Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: >> Further research: >> >> It appears that net-charts.scm is a replacement for two other files in >> standard-reports: net-linecharts.scm and net-barcharts.scm >> >> I renamed those two to have a .old extension on them and GnuCash now >> starts up without complaining about duplicate report IDs. >> > > Ah indeed. As you indicated you didn't uninstall first, the old files > remained > in the installation directory causing the conflict. > > The formal way to uninstall is a bit picky. You should run "make uninstall" > in > your build directory *before* changing the source directory to a newer > version > (be it a new git checkout or pull, or installing a new release tar ball). > > If you installed gnucash in it's own prefix (by adding > -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy > as deleting this prefix. > > But in this case manually removing/renaming the offending files works as > well. > I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/ > scm/ccache/ directory as well though. CMake doesn’t create an uninstall target. To uninstall, use `xargs rm < install_manifest.txt` from the build directory. (In Windows CMake writes install_manifest.txt with windows paths so you have to use a Powershell window and do `get-contents install_manifest.txt | remove-item`). On a related note, CMake’s clean target seems broken for makefiles but works fine for ninja. Regards, John Ralls ___ 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] was: Rethinking the placeholder account concept Re: Fwd: The two modules
Op vrijdag 29 juni 2018 17:05:41 CEST schreef John Ralls: > > On Jun 29, 2018, at 1:31 AM, Geert Janssens > > wrote: Agreed. A structural "view" account would only serve in the global > > account hierarchy and on reports. As one can't use them to store splits, > > they never make sense in dropdowns. > > Well, they never appear as terminal elements in the dropdown, but they’ll be > part of a selectable account’s hierarchy, right? > > e.g. Assets:Current Assets:Bank of America:Savings, where only Savings is an > actual account and the other three are “Views”. > > Regards, > John Ralls Yes. Geert ___ 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] Fwd: Acounts not available in budget
Hi, I have now downloaded version 3.2 and it the budget function is not working as it not showing any accounts when setting up a new budget. Does anyone else has the same problem or knows how to fix this? Kind regards, Robert -- Forwarded message -- Hi, I have recently downloaded and installed gnucash 3.1 for windows (10). When I set up a new company and select the Action new budget, there are no accounts available in the budget. I have noticed that there is no default budget accounts available in the New book options tab, which may be the reason that there are no budget accounts available. Do you know how to show accounts in the budget tab or maybe how to create a default budget account list? Kind regards, Robert ___ 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] GnuCash 3.2 Released
Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler: > On 06/29/2018 12:42 AM, Geert Janssens wrote: > > Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: > >> Further research: > >> > >> It appears that net-charts.scm is a replacement for two other files in > >> standard-reports: net-linecharts.scm and net-barcharts.scm > >> > >> I renamed those two to have a .old extension on them and GnuCash now > >> starts up without complaining about duplicate report IDs. > > > > Ah indeed. As you indicated you didn't uninstall first, the old files > > remained in the installation directory causing the conflict. > > Hopefully I remember for the next upgrade. > > > The formal way to uninstall is a bit picky. You should run "make > > uninstall" in your build directory *before* changing the source directory > > to a newer version (be it a new git checkout or pull, or installing a new > > release tar ball). > > > > If you installed gnucash in it's own prefix (by adding > > -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as > > easy as deleting this prefix. > > > > But in this case manually removing/renaming the offending files works as > > well. I would remove/rename the corresponding .go files in gnucash' > > lib64/gnucash/ scm/ccache/ directory as well though. > > Hmm. Can't find that path. Here is what is in /lib64 on my Ubuntu > 18.04 box: Oh, right. I believe debian and derivates use a different scheme for 64-bit applications Do you have /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ? Geert ___ 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] GnuCash 3.2 Released
On 06/29/2018 12:42 AM, Geert Janssens wrote: > Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: >> Further research: >> >> It appears that net-charts.scm is a replacement for two other files in >> standard-reports: net-linecharts.scm and net-barcharts.scm >> >> I renamed those two to have a .old extension on them and GnuCash now >> starts up without complaining about duplicate report IDs. >> > Ah indeed. As you indicated you didn't uninstall first, the old files > remained > in the installation directory causing the conflict. Hopefully I remember for the next upgrade. > The formal way to uninstall is a bit picky. You should run "make uninstall" > in > your build directory *before* changing the source directory to a newer > version > (be it a new git checkout or pull, or installing a new release tar ball). > > If you installed gnucash in it's own prefix (by adding > -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy > as deleting this prefix. > > But in this case manually removing/renaming the offending files works as > well. > I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/ > scm/ccache/ directory as well though. Hmm. Can't find that path. Here is what is in /lib64 on my Ubuntu 18.04 box: drwxr-xr-x 2 root root 4096 May 6 20:28 ./ drwxr-xr-x 26 root root 4096 Jun 12 10:04 ../ lrwxrwxrwx 1 root root 32 Apr 16 13:14 ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.27.so* lrwxrwxrwx 1 root root 20 May 6 20:28 ld-lsb-x86-64.so.2 -> ld-linux-x86-64.so.2* lrwxrwxrwx 1 root root 20 May 6 20:28 ld-lsb-x86-64.so.3 -> ld-linux-x86-64.so.2* And here is the location of all lib64 directories (via sudo find / -name lib64 /usr/src/linux-headers-3.19.0-28/arch/sh/lib64 /usr/src/linux-headers-3.19.0-26/arch/sh/lib64 /usr/src/linux-headers-3.19.0-25/arch/sh/lib64 /usr/src/linux-headers-4.15.0-23/arch/sh/lib64 /usr/src/linux-headers-3.19.0-29/arch/sh/lib64 /usr/src/linux-headers-4.15.0-22/arch/sh/lib64 /usr/src/linux-headers-3.19.0-27/arch/sh/lib64 /usr/src/linux-headers-3.19.0-23/arch/sh/lib64 /usr/src/linux-headers-3.19.0-24/arch/sh/lib64 /usr/src/linux-headers-3.16.0-32/arch/sh/lib64 /lib64 /var/tmp/mkinitramfs_pYKPbh/lib64 /var/tmp/mkinitramfs_edihqS/lib64 /var/tmp/mkinitramfs_JevWJj/lib64 /var/tmp/mkinitramfs_dZ5Hy3/lib64 /var/tmp/mkinitramfs_2s7hMA/lib64 /var/tmp/mkinitramfs_ncQdoR/lib64 /var/tmp/mkinitramfs_fF6uQ0/lib64 /var/tmp/mkinitramfs_pWngoT/lib64 /var/tmp/mkinitramfs_gE5Jr7/lib64 /var/tmp/mkinitramfs_9spxCx/lib64 /var/tmp/mkinitramfs_Qr12to/lib64 /var/tmp/mkinitramfs_FJaQ9o/lib64 /snap/core/4830/lib64 /snap/core/4571/lib64 /snap/core/4650/lib64 /opt/wine-devel/lib64 /opt/sophos-av/lib64 /opt/sophos-av/update/cache/Primary/sav-linux/x86/64/lib64 /opt/epson-inkjet-printer-201208w/lib64 > Geert > > Thanks, -- Steve ___ 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] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
> On Jun 29, 2018, at 9:52 AM, Geert Janssens
> wrote:
>
> Op vrijdag 29 juni 2018 16:59:07 CEST schreef John Ralls:
>> Stock accounts need to have a parent denominated the currency in which the
>> stock trades in order for the asset roll-up to work correctly on the
>> Accounts page. Three-commodity transactions are possible using trading
>> accounts, but I haven’t dealt with that stuff in a while and the details
>> have gone fuzzy on me.
>>
>> Stock accounts aside, let’s not conflate different purposes. We *should*
>> have an account type to accommodate the European Passive account with
>> Liability and Equity children, so let’s create that. We’ll need to tweak
>> some of the reports a bit to accommodate it, but otherwise it won’t have
>> much impact. It should, of course, be what we now call a placeholder and it
>> should be able to have only Root as a parent and only one each Liability
>> and Equity placeholder children.
>>
> I was in fact deliberately trying to come up with a solution that's more
> flexible than fitting the currently known use cases. The European Passive
> account was just one example.
>
> However we may be spending more time on it than necessary. I checked in the
> current version of the commercial accounting package* I also have to deal
> with
> and it doesn't define a Passive type at all. "Passive" it doesn't even appear
> on its default balance sheet. That is a bit uncommon though as the reports I
> get from my accountant do have a passive section. However just like gnucash
> this package is targeting a worldwide audience (though with country specific
> extensions). That may explain why they didn't bother adding the Passive
> section.
>
> Let me add that contrary to other accounting packages I have played with in
> gnucash the chart of accounts takes a very central place. So whether or not
> we
> want our own Passive type to group liabilities and equity hierarchically on
> the chart of accounts as well is up for debate.
>
>> I don’t think that creating a generic placeholder type account that can have
>> children of any type is a good idea,
>
> Here's another example: a household that wants to track its finances, but
> would want to keep separate account hierarchies per family member. Standard
> response: create two files. However they would benefit from common reporting
> which is cumbersome with two separate files. So what if we would allow to
> create two independent account hierarchies in one file. With a view type
> account one could create two top-levels ("Husband" and "Wife") and create a
> independent hierarchy for each. While this could also be solved if we would
> allow multiple root accounts and make that root visible I'm using it here to
> illustrate there are use cases we are not covering well.
>
> I borrowed the idea of a view type account from an old version of the
> commercial package* we have to use. Looking more closely it turns out the
> current version has dropped view accounts and instead is organizing charts/
> reports using a combination of account type (roughly like we do) and
> hierarchical account numbers. So I must admit perhaps the idea was not so
> bright after all :)
>
> The package also doesn't have a hierarchical account tree. It's flat and
> hierarchy is only added in reports as explained above. So there is no such
> thing as a parent account in that package and hence no restriction on which
> account type a certain account can be.
>
> Again in gnucash the chart of accounts is very central and visible so we
> probably shouldn't drop its hierarchical structure just yet.
>
> The downside of this hierarchical structure is then of course we have to
> think
> about issues like whether or not we should allow accounts to have any type
> of
> child or not. I believe parts of gnucash rely on this (I seem to remember a
> relatively recent issue in the export code that it didn't find all liability
> accounts if they had a non-liability parent or such).
>
>> and I think that we already have too
>> many overlapping account types with subtle behavior differences that are
>> neither documented nor easily discoverable in code.
>>
> I'm all for clearing this up. If we can reduce the number of account types
> that would be great.
> For reference this is the list of 17 account types supported by the
> commercial
> package*:
> Receivable, payable, bank and cash (one type), current assets, non-current
> assets, prepayments, fixed assets, current liabilities, non-current-
> liabilities, equity, current year earnings, other income, income,
> depreciation, expenses, cost of revenue, credit card.
>
> Gnucash currently has 15 of which a few are internal only:
> Bank, cash, credit, asset, liability, stock, mutual, currency, income,
> expense, equity, receivable, payable, root and trading.
>
>
>
> The leftovers from this long discussion for immediate use may be summarized
> as:
> - on reports display placeholder
Re: [GNC] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
On 06/29/2018 09:52 AM, Geert Janssens wrote:
> Op vrijdag 29 juni 2018 16:59:07 CEST schreef John Ralls:
>> Stock accounts need to have a parent denominated the currency in which the
>> stock trades in order for the asset roll-up to work correctly on the
>> Accounts page. Three-commodity transactions are possible using trading
>> accounts, but I haven’t dealt with that stuff in a while and the details
>> have gone fuzzy on me.
I have been reading up on trading accounts and the similarity between
currencies and stock. Essentially stock is just a different currency
with an exchange rate that changes much to fast!
>>
>> Stock accounts aside, let’s not conflate different purposes. We *should*
>> have an account type to accommodate the European Passive account with
>> Liability and Equity children, so let’s create that. We’ll need to tweak
>> some of the reports a bit to accommodate it, but otherwise it won’t have
>> much impact. It should, of course, be what we now call a placeholder and it
>> should be able to have only Root as a parent and only one each Liability
>> and Equity placeholder children.
To my way of thinking, if you want total flexibility, you should be able
to define your top level accounts and name them according to your
language and custom.
Hence, for me:
Assets
Liabilities
Equity
Income
Expense
For friends across the big ocean:
Activa
Assets
Expense
Passiva
Libilities
Equity
Income
(At least I think that is how they organize them.)
Each top level would need an indicator whether it is normally a Debit or
Credit account.
<>
> Here's another example: a household that wants to track its finances, but
> would want to keep separate account hierarchies per family member. Standard
> response: create two files. However they would benefit from common reporting
> which is cumbersome with two separate files. So what if we would allow to
> create two independent account hierarchies in one file. With a view type
> account one could create two top-levels ("Husband" and "Wife") and create a
> independent hierarchy for each. While this could also be solved if we would
> allow multiple root accounts and make that root visible I'm using it here to
> illustrate there are use cases we are not covering well.
Not sure how:
WIFE
HUSBAND
would fit in as top level accounts though. I would think, at a minimum,
they would be sub-accounts with the top level -- else how could you
combine all the assets together for a total?
Then again, with total flexibility, how do you define the generally
accepted accounting formulas?
<>
> The package also doesn't have a hierarchical account tree. It's flat and
> hierarchy is only added in reports as explained above. So there is no such
> thing as a parent account in that package and hence no restriction on which
> account type a certain account can be.
>
> Again in gnucash the chart of accounts is very central and visible so we
> probably shouldn't drop its hierarchical structure just yet.
>
> The downside of this hierarchical structure is then of course we have to
> think
> about issues like whether or not we should allow accounts to have any type
> of
> child or not. I believe parts of gnucash rely on this (I seem to remember a
> relatively recent issue in the export code that it didn't find all liability
> accounts if they had a non-liability parent or such).
>
>> and I think that we already have too
>> many overlapping account types with subtle behavior differences that are
>> neither documented nor easily discoverable in code.
>>
> I'm all for clearing this up. If we can reduce the number of account types
> that would be great.
> For reference this is the list of 17 account types supported by the
> commercial
> package*:
> Receivable, payable, bank and cash (one type), current assets, non-current
> assets, prepayments, fixed assets, current liabilities, non-current-
> liabilities, equity, current year earnings, other income, income,
> depreciation, expenses, cost of revenue, credit card.
>
> Gnucash currently has 15 of which a few are internal only:
> Bank, cash, credit, asset, liability, stock, mutual, currency, income,
> expense, equity, receivable, payable, root and trading.
And figuring out when to use which is hard enough without adding more.
Maybe some of these should become indicators rather than account types
and revert back to just the 5 basic?
> The leftovers from this long discussion for immediate use may be summarized
> as:
> - on reports display placeholder accounts once as aggregate account and once
> as its own account if it has splits.
> - work to be more pedantic about the meaning of "placeholder". It should
> become an empty account used for structuring the account hierarchy and for
> collecting (sub)totals.
> - introduce a read-only status for accounts one doesn't want to accidentally
> modify, but that should still appear in the chart of accounts
Re: [GNC] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
Op vrijdag 29 juni 2018 16:59:07 CEST schreef John Ralls:
> Stock accounts need to have a parent denominated the currency in which the
> stock trades in order for the asset roll-up to work correctly on the
> Accounts page. Three-commodity transactions are possible using trading
> accounts, but I haven’t dealt with that stuff in a while and the details
> have gone fuzzy on me.
>
> Stock accounts aside, let’s not conflate different purposes. We *should*
> have an account type to accommodate the European Passive account with
> Liability and Equity children, so let’s create that. We’ll need to tweak
> some of the reports a bit to accommodate it, but otherwise it won’t have
> much impact. It should, of course, be what we now call a placeholder and it
> should be able to have only Root as a parent and only one each Liability
> and Equity placeholder children.
>
I was in fact deliberately trying to come up with a solution that's more
flexible than fitting the currently known use cases. The European Passive
account was just one example.
However we may be spending more time on it than necessary. I checked in the
current version of the commercial accounting package* I also have to deal with
and it doesn't define a Passive type at all. "Passive" it doesn't even appear
on its default balance sheet. That is a bit uncommon though as the reports I
get from my accountant do have a passive section. However just like gnucash
this package is targeting a worldwide audience (though with country specific
extensions). That may explain why they didn't bother adding the Passive
section.
Let me add that contrary to other accounting packages I have played with in
gnucash the chart of accounts takes a very central place. So whether or not we
want our own Passive type to group liabilities and equity hierarchically on
the chart of accounts as well is up for debate.
> I don’t think that creating a generic placeholder type account that can have
> children of any type is a good idea,
Here's another example: a household that wants to track its finances, but
would want to keep separate account hierarchies per family member. Standard
response: create two files. However they would benefit from common reporting
which is cumbersome with two separate files. So what if we would allow to
create two independent account hierarchies in one file. With a view type
account one could create two top-levels ("Husband" and "Wife") and create a
independent hierarchy for each. While this could also be solved if we would
allow multiple root accounts and make that root visible I'm using it here to
illustrate there are use cases we are not covering well.
I borrowed the idea of a view type account from an old version of the
commercial package* we have to use. Looking more closely it turns out the
current version has dropped view accounts and instead is organizing charts/
reports using a combination of account type (roughly like we do) and
hierarchical account numbers. So I must admit perhaps the idea was not so
bright after all :)
The package also doesn't have a hierarchical account tree. It's flat and
hierarchy is only added in reports as explained above. So there is no such
thing as a parent account in that package and hence no restriction on which
account type a certain account can be.
Again in gnucash the chart of accounts is very central and visible so we
probably shouldn't drop its hierarchical structure just yet.
The downside of this hierarchical structure is then of course we have to think
about issues like whether or not we should allow accounts to have any type of
child or not. I believe parts of gnucash rely on this (I seem to remember a
relatively recent issue in the export code that it didn't find all liability
accounts if they had a non-liability parent or such).
> and I think that we already have too
> many overlapping account types with subtle behavior differences that are
> neither documented nor easily discoverable in code.
>
I'm all for clearing this up. If we can reduce the number of account types
that would be great.
For reference this is the list of 17 account types supported by the commercial
package*:
Receivable, payable, bank and cash (one type), current assets, non-current
assets, prepayments, fixed assets, current liabilities, non-current-
liabilities, equity, current year earnings, other income, income,
depreciation, expenses, cost of revenue, credit card.
Gnucash currently has 15 of which a few are internal only:
Bank, cash, credit, asset, liability, stock, mutual, currency, income,
expense, equity, receivable, payable, root and trading.
The leftovers from this long discussion for immediate use may be summarized
as:
- on reports display placeholder accounts once as aggregate account and once
as its own account if it has splits.
- work to be more pedantic about the meaning of "placeholder". It should
become an empty account used for structuring the account hierarchy and for
co
[GNC] Upgrading GC under Ubuntu
It seems that GC is a very popular accounting program, and Ubuntu/Linux is a very popular Operating System, yet when there is an upgrade in GC, I cannot find a straightforward method of updating GC under Ubuntu/Linux. I understand that there is a delay before the new version of GC is in the Ubuntu Software download system. That is internal to Ubuntu. But there are alternatives, such as an alternative repository and self compiling. Oh yes, what about pre-compiled binaries like Windows and Mac? Each could have clear concise instructions on how to perform the task. One could direct the user with specific commands to go th the repository that gets the upgrade first. A script could be written and published with copious comments, testing for dependencies, loading them, doing a security check of the downloaded files, compiling and testing. Google has not turned out to be my friend, otherwise I would not be writing this. There are articles years old, no install scripts, no suggestions of repositories with instructions. Feel free to prove me wrong, I have spent a couple of hours searching with many selected key words, John ___ 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] GnuCash 3.2 Released
On 06/29/2018 11:02 AM, Geert Janssens wrote: > Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler: >> On 06/29/2018 12:42 AM, Geert Janssens wrote: >>> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: Further research: It appears that net-charts.scm is a replacement for two other files in standard-reports: net-linecharts.scm and net-barcharts.scm I renamed those two to have a .old extension on them and GnuCash now starts up without complaining about duplicate report IDs. >>> Ah indeed. As you indicated you didn't uninstall first, the old files >>> remained in the installation directory causing the conflict. >> Hopefully I remember for the next upgrade. >> >>> The formal way to uninstall is a bit picky. You should run "make >>> uninstall" in your build directory *before* changing the source directory >>> to a newer version (be it a new git checkout or pull, or installing a new >>> release tar ball). >>> >>> If you installed gnucash in it's own prefix (by adding >>> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as >>> easy as deleting this prefix. >>> >>> But in this case manually removing/renaming the offending files works as >>> well. I would remove/rename the corresponding .go files in gnucash' >>> lib64/gnucash/ scm/ccache/ directory as well though. >> Hmm. Can't find that path. Here is what is in /lib64 on my Ubuntu >> 18.04 box: > Oh, right. I believe debian and derivates use a different scheme for 64-bit > applications > > Do you have > /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ? > > Geert > > Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the odd member here? I did find them here though: /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports Occasionally find can be useful! sudo find / -name net-barchart.go /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-barchart.go I removed both. ___ 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] Upgrading GC under Ubuntu
On 06/29/2018 11:45 AM, John R. Sowden wrote: > It seems that GC is a very popular accounting program, and > Ubuntu/Linux is a very popular Operating System, yet when there is an > upgrade in GC, I cannot find a straightforward method of updating GC > under Ubuntu/Linux. > > I understand that there is a delay before the new version of GC is in > the Ubuntu Software download system. That is internal to Ubuntu. But > there are alternatives, such as an alternative repository and self > compiling. Oh yes, what about pre-compiled binaries like Windows and > Mac? > > Each could have clear concise instructions on how to perform the task. > > One could direct the user with specific commands to go th the > repository that gets the upgrade first. > > A script could be written and published with copious comments, testing > for dependencies, loading them, doing a security check of the > downloaded files, compiling and testing. > > Google has not turned out to be my friend, otherwise I would not be > writing this. There are articles years old, no install scripts, no > suggestions of repositories with instructions. > > Feel free to prove me wrong, I have spent a couple of hours searching > with many selected key words, > > John > Having just done a download and compile to my Ubuntu 18.04, let me share with you what I did. Sometimes reading the web sites leaves one (at least me) scratching their head vigorously -- in my case not a good idea with the hair I have left! 1. Read this page: https://wiki.gnucash.org/wiki/BuildUbuntu16.04 It works for 18.04 also. You didn't say which version of Ubuntu so I am presuming either 16.04 or 18.04 You may need to install a bunch of libraries. I found that a couple or more were already on my box. My box had some old libraries hanging around that I had to manually remove in /usr/src: sudo rm -rf /usr/src/gtest /usr/src/gmock See this note: https://larry-price.com/blog/2013/10/13/installing-gtest-and-gmock-libs-in-ubuntu-13-dot-04/ But don't worry. Just remove the above two entries (if they exist) and the install of googletest and googlemock will work. I ended up uninstalling the two packages on my way to figuring out what had happened. sudo apt-get install build-essential sudo apt-get install cmake sudo apt-get install libtool libltdl-dev sudo apt-get install libglib2.0 libglib2.0-dev #glib2 > v2.40.0 sudo apt-get install icu-devtools libicu-dev sudo apt-get install libboost-all-dev# boost > 1.50.0 - requires locale and regex built with ICU support sudo apt-get install guile-2.0 guile-2.0-dev # guile >=2.0.0 sudo apt-get install swig3.0 # swig >2.0.10 *(swig3.0 on Ubuntu18.04)* not required if building from tarball, sudo apt-get install googletest sudo apt-get install googlemock sudo apt-get install libgtest-dev # but from any version control system sudo apt-get install libxml2 libxml++2.6-dev sudo apt-get install libxslt1.1 libxslt1-dev sudo apt-get install xsltproc sudo apt-get install texinfo # required for makeinfo sudo apt-get install gtk+3.0 sudo apt-get install libgtk-3-dev sudo apt-get install libwebkit2gtk-4.0-37# > webkit2gtk-3.0 sudo apt-get install libwebkit2gtk-4.0-dev sudo apt-get install libdbi1 libdbi-dev # > v0.8.3 # one of the following three if you want a database backend option: sudo apt-get install libdbd-pgsql# PostgreSQL database sudo apt-get install libdbd-mysql# MySQL database sudo apt-get install libdbd-sqlite3 # Sqlite database sudo apt-get install libofx-dev sudo apt-get install aqbanking-tools libaqbanking-dev # > v4.0.0 sudo apt-get install gwenhywfar-tools libgwenhywfar60 libgwenhywfar60-dev sudo apt-get install ktoblzcheck libktoblzcheck1-dev sudo apt-get install python3-pytest As noted above, my box had many of these already so apt-get skipped the install for them and told me I already had the latest. 2. Download this source code from: https://sourceforge.net/projects/gnucash/files/gnucash%20%28stable%29/3.2/gnucash-3.2.tar.gz/download 3. Move the file to where you want to house your source: I made mine $HOME/Projects/GnuCash. mkdir -p $HOME/Projects/GnuCash cd Downloads mv gnucash* $HOME/Projects/GnuCash 4. Go there and build your source and build folders cd ../Projects/GnuCash gunzip gnucash* tar -xf gnucash* mkdir mybuild cd mybuild 5. Compile and install cmake ../gnucash* make sudo make install I'll admit that I made several mis-steps along the way and needed help from the great folks here. Hopefully this will get you going. Oh, uninstall gnucash first if you already have a version. I failed to do that and had to remove some outdated files. Stephen M Butler, PMP, PSM stephen.m.butle...@gmail.com kg...@arrl.net 253-350-0166 ---
Re: [GNC] Upgrading GC under Ubuntu
Before 'rolling your own' GnuCash, check out Getdeb.net. They may not have 3 series yet, but they are up to 2.6.17 at least, if not later. David C On Fri, Jun 29, 2018 at 2:50 PM, Stephen M. Butler wrote: > On 06/29/2018 11:45 AM, John R. Sowden wrote: > > It seems that GC is a very popular accounting program, and > > Ubuntu/Linux is a very popular Operating System, yet when there is an > > upgrade in GC, I cannot find a straightforward method of updating GC > > under Ubuntu/Linux. > > > > I understand that there is a delay before the new version of GC is in > > the Ubuntu Software download system. That is internal to Ubuntu. But > > there are alternatives, such as an alternative repository and self > > compiling. Oh yes, what about pre-compiled binaries like Windows and > > Mac? > > > > Each could have clear concise instructions on how to perform the task. > > > > One could direct the user with specific commands to go th the > > repository that gets the upgrade first. > > > > A script could be written and published with copious comments, testing > > for dependencies, loading them, doing a security check of the > > downloaded files, compiling and testing. > > > > Google has not turned out to be my friend, otherwise I would not be > > writing this. There are articles years old, no install scripts, no > > suggestions of repositories with instructions. > > > > Feel free to prove me wrong, I have spent a couple of hours searching > > with many selected key words, > > > > John > > > Having just done a download and compile to my Ubuntu 18.04, let me share > with you what I did. Sometimes reading the web sites leaves one (at > least me) scratching their head vigorously -- in my case not a good idea > with the hair I have left! > > 1. Read this page: https://wiki.gnucash.org/wiki/BuildUbuntu16.04 > It works for 18.04 also. > > You didn't say which version of Ubuntu so I am presuming either > 16.04 or 18.04 > You may need to install a bunch of libraries. I found that a couple > or more were already on my box. > > My box had some old libraries hanging around that I had to manually > remove in /usr/src: > sudo rm -rf /usr/src/gtest /usr/src/gmock > > See this note: > https://larry-price.com/blog/2013/10/13/installing-gtest- > and-gmock-libs-in-ubuntu-13-dot-04/ > But don't worry. Just remove the above two entries (if they exist) > and the install of googletest and googlemock will work. > I ended up uninstalling the two packages on my way to figuring out > what had happened. sudo apt-get install build-essential > > sudo apt-get install cmake > sudo apt-get install libtool libltdl-dev > sudo apt-get install libglib2.0 libglib2.0-dev #glib2 > v2.40.0 > sudo apt-get install icu-devtools libicu-dev > sudo apt-get install libboost-all-dev# boost > 1.50.0 - > requires locale and regex built with ICU support > sudo apt-get install guile-2.0 guile-2.0-dev # guile >=2.0.0 > sudo apt-get install swig3.0 # swig >2.0.10 *(swig3.0 > on Ubuntu18.04)* not required if building from > tarball, > > sudo apt-get install googletest > sudo apt-get install googlemock > sudo apt-get install libgtest-dev > # but from any version > control system > sudo apt-get install libxml2 libxml++2.6-dev > sudo apt-get install libxslt1.1 libxslt1-dev > sudo apt-get install xsltproc > sudo apt-get install texinfo # required for makeinfo > > > sudo apt-get install gtk+3.0 > sudo apt-get install libgtk-3-dev > sudo apt-get install libwebkit2gtk-4.0-37# > webkit2gtk-3.0 > sudo apt-get install libwebkit2gtk-4.0-dev > > sudo apt-get install libdbi1 libdbi-dev # > v0.8.3 > > # one of the following three if you want a database backend option: > sudo apt-get install libdbd-pgsql# PostgreSQL database > sudo apt-get install libdbd-mysql# MySQL database > sudo apt-get install libdbd-sqlite3 # Sqlite database > > sudo apt-get install libofx-dev > > sudo apt-get install aqbanking-tools libaqbanking-dev # > v4.0.0 > sudo apt-get install gwenhywfar-tools libgwenhywfar60 libgwenhywfar60-dev > sudo apt-get install ktoblzcheck libktoblzcheck1-dev > > sudo apt-get install python3-pytest > > As noted above, my box had many of these already so apt-get skipped the > install for them and told me I already had the latest. > > > 2. Download this source code from: > https://sourceforge.net/projects/gnucash/files/gnucash%20%28stable%29/3.2/ > gnucash-3.2.tar.gz/download > > 3. Move the file to where you want to house your source: I made mine > $HOME/Projects/GnuCash. > mkdir -p $HOME/Projects/GnuCash > cd Downloads > mv gnucash* $HOME/Projects/GnuCash > > 4. Go there and build your source and build folders > cd ../Projects/GnuCash > gunzip gnucash* > tar -xf gnucash* > mkdir mybuild > cd mybuild > > 5. Compile and install > cmak
Re: [GNC] GnuCash 3.2 Released
Op vrijdag 29 juni 2018 21:04:31 CEST schreef Stephen M. Butler: > On 06/29/2018 11:02 AM, Geert Janssens wrote: > > Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler: > >> On 06/29/2018 12:42 AM, Geert Janssens wrote: > >>> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: > Further research: > > It appears that net-charts.scm is a replacement for two other files in > standard-reports: net-linecharts.scm and net-barcharts.scm > > I renamed those two to have a .old extension on them and GnuCash now > starts up without complaining about duplicate report IDs. > >>> > >>> Ah indeed. As you indicated you didn't uninstall first, the old files > >>> remained in the installation directory causing the conflict. > >> > >> Hopefully I remember for the next upgrade. > >> > >>> The formal way to uninstall is a bit picky. You should run "make > >>> uninstall" in your build directory *before* changing the source > >>> directory > >>> to a newer version (be it a new git checkout or pull, or installing a > >>> new > >>> release tar ball). > >>> > >>> If you installed gnucash in it's own prefix (by adding > >>> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as > >>> easy as deleting this prefix. > >>> > >>> But in this case manually removing/renaming the offending files works as > >>> well. I would remove/rename the corresponding .go files in gnucash' > >>> lib64/gnucash/ scm/ccache/ directory as well though. > >> > >> Hmm. Can't find that path. Here is what is in /lib64 on my Ubuntu > > > >> 18.04 box: > > Oh, right. I believe debian and derivates use a different scheme for > > 64-bit > > applications > > > > Do you have > > /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ? > > > > Geert > > Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the > odd member here? > > I did find them here though: > /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports > Occasionally find can be useful! > > sudo find / -name net-barchart.go > /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-ba > rchart.go > > I removed both. Ah, indeed. If you don't specify a prefix, cmake will use /usr/local. Sorry for sending you around on different wrong paths. Geert ___ 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] Bugs.gnucash.org Up and Running
We've completed the migration of Bugzilla to https://bugs.gnucash.org and we're ready to resume normal bug ops there. The updates on bugzilla.gnome.org are still running (after 2 hours not quite halfway done), but that doesn't affect using https://bugs.gnucash.org. There's one change since yesterday's announcement: We've shortened the pseudo-addresses for bugmail: Group Elements c...@gnucash.bugs Backend-SQL, Backend-XML, Budgets, Build System, Business, Currency and Commodity, Engine, Python Bindings, Scheduled Transactions documentat...@gnucash.bugsDocumentation, Translations, Website gene...@gnucash.bugs General imp...@gnome.bugs Import-AqBanking, Import-CSV, Import-OFX, Import- Other, Import-QIF, Import-QSF, TXF Export ma...@gnucash.bugsMacOS repo...@gnucash.bugs Check Printing, Reports u...@gnucash.bugs Register, Regist-2, User Interface General wind...@gnucash.bugs Windows all-b...@gnucash.bugs Everything For now we've adopted the Gnome skin for familiarity, but we'd love to have someone who's artistically inclined to design us a GnuCash-specific one! Regards, John Ralls ___ 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] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
Hi,
Am 29.06.2018 um 19:26 schrieb John Ralls:
>
>
>> On Jun 29, 2018, at 9:52 AM, Geert Janssens
>> wrote:
>>
>> Op vrijdag 29 juni 2018 16:59:07 CEST schreef John Ralls:
>>> Stock accounts need to have a parent denominated the currency in which the
>>> stock trades in order for the asset roll-up to work correctly on the
>>> Accounts page. Three-commodity transactions are possible using trading
>>> accounts, but I haven’t dealt with that stuff in a while and the details
>>> have gone fuzzy on me.
>>>
>>> Stock accounts aside, let’s not conflate different purposes. We *should*
>>> have an account type to accommodate the European Passive account with
>>> Liability and Equity children, so let’s create that. We’ll need to tweak
>>> some of the reports a bit to accommodate it, but otherwise it won’t have
>>> much impact. It should, of course, be what we now call a placeholder and it
>>> should be able to have only Root as a parent and only one each Liability
>>> and Equity placeholder children.
>>>
>> I was in fact deliberately trying to come up with a solution that's more
>> flexible than fitting the currently known use cases. The European Passive
>> account was just one example.
>>
>> However we may be spending more time on it than necessary. I checked in the
>> current version of the commercial accounting package* I also have to deal
>> with
>> and it doesn't define a Passive type at all. "Passive" it doesn't even
>> appear
>> on its default balance sheet. That is a bit uncommon though as the reports I
>> get from my accountant do have a passive section. However just like gnucash
>> this package is targeting a worldwide audience (though with country specific
>> extensions). That may explain why they didn't bother adding the Passive
>> section.
>>
>> Let me add that contrary to other accounting packages I have played with in
>> gnucash the chart of accounts takes a very central place. So whether or not
>> we
>> want our own Passive type to group liabilities and equity hierarchically on
>> the chart of accounts as well is up for debate.
>>
>>> I don’t think that creating a generic placeholder type account that can have
>>> children of any type is a good idea,
>>
>> Here's another example: a household that wants to track its finances, but
>> would want to keep separate account hierarchies per family member. Standard
>> response: create two files. However they would benefit from common reporting
>> which is cumbersome with two separate files. So what if we would allow to
>> create two independent account hierarchies in one file. With a view type
>> account one could create two top-levels ("Husband" and "Wife") and create a
>> independent hierarchy for each. While this could also be solved if we would
>> allow multiple root accounts and make that root visible I'm using it here to
>> illustrate there are use cases we are not covering well.
>>
>> I borrowed the idea of a view type account from an old version of the
>> commercial package* we have to use. Looking more closely it turns out the
>> current version has dropped view accounts and instead is organizing charts/
>> reports using a combination of account type (roughly like we do) and
>> hierarchical account numbers. So I must admit perhaps the idea was not so
>> bright after all :)
>>
>> The package also doesn't have a hierarchical account tree. It's flat and
>> hierarchy is only added in reports as explained above. So there is no such
>> thing as a parent account in that package and hence no restriction on which
>> account type a certain account can be.
>>
>> Again in gnucash the chart of accounts is very central and visible so we
>> probably shouldn't drop its hierarchical structure just yet.
>>
>> The downside of this hierarchical structure is then of course we have to
>> think
>> about issues like whether or not we should allow accounts to have any type
>> of
>> child or not. I believe parts of gnucash rely on this (I seem to remember a
>> relatively recent issue in the export code that it didn't find all liability
>> accounts if they had a non-liability parent or such).
>>
>>> and I think that we already have too
>>> many overlapping account types with subtle behavior differences that are
>>> neither documented nor easily discoverable in code.
>>>
>> I'm all for clearing this up. If we can reduce the number of account types
>> that would be great.
>> For reference this is the list of 17 account types supported by the
>> commercial
>> package*:
>> Receivable, payable, bank and cash (one type), current assets, non-current
>> assets, prepayments, fixed assets, current liabilities, non-current-
>> liabilities, equity, current year earnings, other income, income,
>> depreciation, expenses, cost of revenue, credit card.
>>
>> Gnucash currently has 15 of which a few are internal only:
>> Bank, cash, credit, asset, liability, stock, mutual, currency, income,
>> expense, equity, receivable, payable, root and trad
Re: [GNC] GnuCash 3.2 Released
On 06/29/2018 02:17 PM, Geert Janssens wrote: > Op vrijdag 29 juni 2018 21:04:31 CEST schreef Stephen M. Butler: >> On 06/29/2018 11:02 AM, Geert Janssens wrote: >>> Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler: On 06/29/2018 12:42 AM, Geert Janssens wrote: > Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler: >> Further research: >> >> It appears that net-charts.scm is a replacement for two other files in >> standard-reports: net-linecharts.scm and net-barcharts.scm >> >> I renamed those two to have a .old extension on them and GnuCash now >> starts up without complaining about duplicate report IDs. > Ah indeed. As you indicated you didn't uninstall first, the old files > remained in the installation directory causing the conflict. Hopefully I remember for the next upgrade. > The formal way to uninstall is a bit picky. You should run "make > uninstall" in your build directory *before* changing the source > directory > to a newer version (be it a new git checkout or pull, or installing a > new > release tar ball). > > If you installed gnucash in it's own prefix (by adding > -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as > easy as deleting this prefix. > > But in this case manually removing/renaming the offending files works as > well. I would remove/rename the corresponding .go files in gnucash' > lib64/gnucash/ scm/ccache/ directory as well though. Hmm. Can't find that path. Here is what is in /lib64 on my Ubuntu 18.04 box: >>> Oh, right. I believe debian and derivates use a different scheme for >>> 64-bit >>> applications >>> >>> Do you have >>> /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ? >>> >>> Geert >> Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the >> odd member here? >> >> I did find them here though: >> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports >> Occasionally find can be useful! >> >> sudo find / -name net-barchart.go >> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-ba >> rchart.go >> >> I removed both. > Ah, indeed. If you don't specify a prefix, cmake will use /usr/local. Sorry > for sending you around on different wrong paths. > > Geert > > > > No problem. Forces me to figure out what _is_ happening. At least you told me about the .go files. ___ 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] Rethinking the placeholder account concept (was: Re: Fwd: The two modules)
> On Jun 29, 2018, at 3:26 PM, Christian Kluge wrote:
>
> Hi,
>
> Am 29.06.2018 um 19:26 schrieb John Ralls:
>>
>>
>>> On Jun 29, 2018, at 9:52 AM, Geert Janssens
>>> wrote:
>>>
>>> Op vrijdag 29 juni 2018 16:59:07 CEST schreef John Ralls:
Stock accounts need to have a parent denominated the currency in which the
stock trades in order for the asset roll-up to work correctly on the
Accounts page. Three-commodity transactions are possible using trading
accounts, but I haven’t dealt with that stuff in a while and the details
have gone fuzzy on me.
Stock accounts aside, let’s not conflate different purposes. We *should*
have an account type to accommodate the European Passive account with
Liability and Equity children, so let’s create that. We’ll need to tweak
some of the reports a bit to accommodate it, but otherwise it won’t have
much impact. It should, of course, be what we now call a placeholder and it
should be able to have only Root as a parent and only one each Liability
and Equity placeholder children.
>>> I was in fact deliberately trying to come up with a solution that's more
>>> flexible than fitting the currently known use cases. The European Passive
>>> account was just one example.
>>>
>>> However we may be spending more time on it than necessary. I checked in the
>>> current version of the commercial accounting package* I also have to deal
>>> with
>>> and it doesn't define a Passive type at all. "Passive" it doesn't even
>>> appear
>>> on its default balance sheet. That is a bit uncommon though as the reports
>>> I
>>> get from my accountant do have a passive section. However just like gnucash
>>> this package is targeting a worldwide audience (though with country
>>> specific
>>> extensions). That may explain why they didn't bother adding the Passive
>>> section.
>>>
>>> Let me add that contrary to other accounting packages I have played with in
>>> gnucash the chart of accounts takes a very central place. So whether or not
>>> we
>>> want our own Passive type to group liabilities and equity hierarchically on
>>> the chart of accounts as well is up for debate.
>>>
I don’t think that creating a generic placeholder type account that can
have
children of any type is a good idea,
>>>
>>> Here's another example: a household that wants to track its finances, but
>>> would want to keep separate account hierarchies per family member. Standard
>>> response: create two files. However they would benefit from common
>>> reporting
>>> which is cumbersome with two separate files. So what if we would allow to
>>> create two independent account hierarchies in one file. With a view type
>>> account one could create two top-levels ("Husband" and "Wife") and create a
>>> independent hierarchy for each. While this could also be solved if we would
>>> allow multiple root accounts and make that root visible I'm using it here
>>> to
>>> illustrate there are use cases we are not covering well.
>>>
>>> I borrowed the idea of a view type account from an old version of the
>>> commercial package* we have to use. Looking more closely it turns out the
>>> current version has dropped view accounts and instead is organizing charts/
>>> reports using a combination of account type (roughly like we do) and
>>> hierarchical account numbers. So I must admit perhaps the idea was not so
>>> bright after all :)
>>>
>>> The package also doesn't have a hierarchical account tree. It's flat and
>>> hierarchy is only added in reports as explained above. So there is no such
>>> thing as a parent account in that package and hence no restriction on which
>>> account type a certain account can be.
>>>
>>> Again in gnucash the chart of accounts is very central and visible so we
>>> probably shouldn't drop its hierarchical structure just yet.
>>>
>>> The downside of this hierarchical structure is then of course we have to
>>> think
>>> about issues like whether or not we should allow accounts to have any type
>>> of
>>> child or not. I believe parts of gnucash rely on this (I seem to remember a
>>> relatively recent issue in the export code that it didn't find all
>>> liability
>>> accounts if they had a non-liability parent or such).
>>>
and I think that we already have too
many overlapping account types with subtle behavior differences that are
neither documented nor easily discoverable in code.
>>> I'm all for clearing this up. If we can reduce the number of account types
>>> that would be great.
>>> For reference this is the list of 17 account types supported by the
>>> commercial
>>> package*:
>>> Receivable, payable, bank and cash (one type), current assets, non-current
>>> assets, prepayments, fixed assets, current liabilities, non-current-
>>> liabilities, equity, current year earnings, other income, income,
>>> depreciation, expenses, cost of revenue, credit
