Re: [GNC-dev] New balsheet (and P report), API considerations, and (slow?) KVP in Account.cpp
Hi Adrien, Am 31.07.2018 um 02:27 schrieb Adrien Monteleone: > Frank, > > I’ve been following this for a while, and perhaps I’m not understanding, but > are the groupings just presentational? Usually the sums of this groups are economic indicators, e.g. if current assets < current liabilities there is a liquidity problem. > If that’s the case, I would think the place to address this is in the report > options, not the account structure. (you could use any structure you need, > and easily re-group based on the rule you decide or need to follow.) The tables in https://de.wikipedia.org/wiki/Gewinn-_und_Verlustrechnung#Gliederung show the grouping for the 3 regions AT (UGB), DE (HGB) and intl (IFRS). The latter can be adapted for the less formal US (GAAP). They are shown for 2 different methods: Period costing Method (Gesamtkostenverfahren) and Cost of Sales Method (Umsatzkostenverfahren) I have currently no idea, how to get this different forms from the report by options. > Regards, > Adrien Regards Frank P.S. I found a translation of my preferred account template at https://www.datev.de/web/de/datev-shop/material/skr-04-englisch/ pEpkey.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] New balsheet (and P report), API considerations, and (slow?) KVP in Account.cpp
> On Aug 7, 2018, at 5:00 PM, Frank H. Ellenberger > wrote: > > > > No, the grouping should be part of the account template - at least in > the current state. At some point in the future one could think about > additional account attributes to improve reporting... > I think this is only a limitation of the current report. If it’s being re-written anyway, I’d suggest: Default sections for the report, each section having it’s own account selection option(s). (not one all-encompassing set of accounts for the entire report) In the long term, default sections could be labeled based on a preference setting for the book/entity. But short term, There could be multiple balance sheet ‘reports’ each with the appropriate sections for entity types and/or jurisdictions. Or, simply have a set number of sections and you get to name each one whatever you want and select its own accounts to include. This way the user can specify which accounts are ‘current vs. fixed’ or ’short term vs. long’, which accounts constitute ‘cash’ and so on. (or whatever the sections may be) Of course, it’s just a suggestion. I can’t say how much extra work that would be, but that approach might cover many use cases. > > BTW has somebody a better expression here? For "source" I would expect a > selection from transaction, price database and online quotes. > ’Source’ with those options seems pretty reasonable as to what is being asked for. (though maybe preface ’transaction’ with ‘previous’ or something similar) > > From > https://screenshotscdn.firefoxusercontent.com/images/556716da-ba2e-4bed-9bd7-c7232542ab6f.png > I am confused. I would have expected: > Liability and Equity (header) > Equity (group) > Liability (group) > Liability and Equity (footer) I agree, they should appear once, combined is fine as that’s pretty standard, but they should only appear once. Regards, Adrien ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] New balsheet (and P report), API considerations, and (slow?) KVP in Account.cpp
Am 06.08.2018 um 14:40 schrieb Christopher Lam: > > (*: we all know Gnucash has evolved through generations rather than a > grand design ) ... because there is no all-purpose, all-country grand design. > 1) Frank et al requests some analysis of accounts for grouping into > Short/Long, etc. I disagree. The current balance-sheet does not make any > judgements into the types of monies held in various asset/liability > accounts, and I do not particularly think it is universally agreed which > assets should be long/short-term, which ones are fixed etc. The current > balance-sheet will just take a nested list of asset/liability accounts, > and simply list them sequentially, up to depth-limit. The ways that an > account can be tagged fixed, long or depreciation, contra, etc is not > something the current balance-sheet can understand, nor am I willing to > impose my judgement to report. The Tutorial and Concepts Guide does > encourage that Fixed Assets are held in account structure > Assets:Fixed:Asset1 and its depreciation amounts are recorded in > Assets:Fixed:Asset1:Depreciation, and I see no problem in that, and > balsheet (old or new) will diligently report all amounts. > > However I do understand there may be a wish for a customized balsheet to > apply heuristics/rules for depreciation/current/fixed etc assets but > this requires expert accounting knowledge. No, the grouping should be part of the account template - at least in the current state. At some point in the future one could think about additional account attributes to improve reporting... : > 3) In the screenshot, EUR Amounts not converted to USD is not confusing > at all. In the test book there are USD/GBP prices but no USD/EUR prices. > The old balance-sheet would convert any EUR amount to 0 USD and display > an incorrect total.4) The amounts being links are a new feature - the > new income-statement links to a transaction report detailing the > amounts, and the new balance-sheet links to the register entry which > documents the exact balance-sheet figure. At least for official reports, I assume, all assets are expected to be appraised in local currency. But because the rules differ between governments and over time, GnuCash can not do it automagical. Perhaps we should explain in the documentation, that the user should see this as their input error. They should have at least one price per commodity. And if they have multiple they should select the "price source". BTW has somebody a better expression here? For "source" I would expect a selection from transaction, price database and online quotes. : > 7) The sections are copied from balance-sheet and they need > experimentation... I'd be grateful if anyone can review the section > amounts are selecting the correct amounts. I don't think I've got it > 100% correct and need feedback. From https://screenshotscdn.firefoxusercontent.com/images/556716da-ba2e-4bed-9bd7-c7232542ab6f.png I am confused. I would have expected: Liability and Equity (header) Equity (group) Liability (group) Liability and Equity (footer) BTW an option, which to show first (equity or liability) would be fine here bacause country specific rules differ here. Compare the position of "Eigenkapital" in the german and swiss subsections of https://de.wikipedia.org/wiki/Bilanz#Aufbau_der_Bilanz Frank > C pEpkey.asc Description: application/pgp-keys ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] gnucash maint: Fix gncInvoice test failure.
Op maandag 6 augustus 2018 23:49:17 CEST schreef John Ralls: > Updatedvia https://github.com/Gnucash/gnucash/commit/78ab26cc > (commit) > from https://github.com/Gnucash/gnucash/commit/d87fa3a5 (commit) > > > > commit 78ab26cc2ba78a8e41ad725ae0fd64bc186c92d4 > Author: John Ralls > Date: Mon Aug 6 14:49:07 2018 -0700 > > Fix gncInvoice test failure. > > test_suite_gncInvoice sets up the test suite. It's not part of the test > runtime, so stack variables in it have gone out of scope by the time the > tests are actually run. Making invoiceData static makes it permanent so it > exists at runtime. > Thanks! I would have searched for this a long time. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
