Thanks for feedback. I think it will be sensible to modify the current GST-report to
1. instead of combined Sales/Purchases Accounts, request them separately. 2. add a tab "Format" -- this will be new new home for toggling sales/purchase/tax summaries or individual accounts 3. within "Format" tab, add multichoice option to specify 'default' or 'uk-vat' which converts report output to the HMRC box 1-9 columns. As this requires a change in saved-report options, will be best in the 4.x series. While this is in development, UK-VAT-report.scm will still work unchanged. This means we won't need to add a new report altogether, and other countries could tack their formats at the end of income-gst-statement.scm. See example at https://github.com/Gnucash/gnucash/pull/500 On Wed, 24 Jul 2019 at 11:34, Maf. King <m...@chilwell.net> wrote: > Hi, > > yes, changing the preference from Locale to UK results in a YYYY in the > export. > > thanks. > Maf. > > > > On Wednesday, 24 July 2019 12:13:30 BST you wrote: > > Hi Maf, you're welcome; thanks for letting me know. > > > > The dates are printed via gnucash's date-printer and will probably obey > > the locale or general preferences setting. Try Preferences/Date&Time. > > > > I'm still considering how to incorporate the UK rules into the current > > merged report; I now know the sales/purchases accounts selection via > > Income/Expense account-type is a design mishap; perhaps the next 4.x > series > > will request the sales/purchase acocunts separately. This means the > UK-VAT > > report (including the EC rules and the EC account tagging hacks) could > then > > be an optional switch in the GST Report. > > > > On Wed, 24 Jul 2019 at 10:39, Maf. King <m...@chilwell.net> wrote: > > > Hi Christopher, > > > > > > I've just submitted the first MTD VAT return using GC and the report > you > > > very > > > kindly wrote. > > > > > > The only glitch discovered in actual production use is that the dates > > > exported > > > by the report in to the CSV file and hence read by the bridging > > > spreadsheet > > > need to have a 4-digit year, the export is presently only 2 digits. > > > > > > I had no EU transactions this quarter > > > > > > but otherwise, no problems, the numbers all matched up to my old custom > > > reports. > > > > > > so thank you very much for the time to make this work. > > > > > > best regards, > > > Maf. > > > > > > On Wednesday, 12 June 2019 15:30:15 BST Christopher Lam wrote: > > > > Hi > > > > > > > > I think it'll be reasonable for now to merge some infrastructure > work in > > > > the transaction-report engine to allow CSV export. > > > > > > > > uk-vat-report.scm would be a custom-report, added onto > standard-reports > > > > > > or > > > > > > > possibly config-user.scm on request, with caveat that the > > > > accounts-selection is not yet set in stone. > > > > > > > > Ultimately it may be an idea to add onto the Tax-Info dialog to tag > > > > accounts, but I don't know how to do that. > > > > > > > > C > > > > > > > > On Wed, 12 Jun 2019 at 11:07, Maf. King <m...@chilwell.net> wrote: > > > > > Hi Christopher, > > > > > > > > > > thanks for the gentle prod. I've been very busy for the last > couple > > > > > of > > > > > weeks, > > > > > and I apologise for not getting back to you sooner. > > > > > > > > > > so far, the VAT report seems to work for me, I haven't spotted any > > > > > > glaring > > > > > > > > problems, although I appreciate the limitations on the account > > > > > > selections > > > > > > > > that > > > > > you mention, and I haven't explored deeply with anything other > than my > > > > > normal > > > > > files. > > > > > > > > > > it seems that MTD hasn't gone away (unfortunately) and would be a > > > > > > shame to > > > > > > > > miss the release bundle, although I accept that this is still code > > > > > > which > > > > > > > > is > > > > > beta-ish in nature, and I don't know the GC policy on including > code > > > > > > which > > > > > > > > may > > > > > still need some polish in a finished release. However, I would > also > > > > > counter > > > > > that the first real complete test of the workflow has to wait for > July > > > > > > and > > > > > > > > the > > > > > first return being prepared. > > > > > > > > > > best regards, > > > > > Maf. > > > > > > > > > > On Sunday, 9 June 2019 15:53:26 BST Christopher Lam wrote: > > > > > > Any final views on enabling CSV export of subtotals and VAT > report? > > > > > > 3.6 > > > > > > > > > will be in preparation soon... > > > > > > > > > > > > The VAT report is rather UK-specific regarding EC sales and I > don't > > > > > > know > > > > > > > > > rules for other EC countries. It'll be a shame to limit it to UK > > > > > > only, > > > > > > > > > which means any other EC VAT report will need to duplicate and > amend > > > > > > the > > > > > > > > > report. > > > > > > > > > > > > And while the selection of Sales/Purchases/VAT accounts is IMHO > > > > > > satisfactory, the tagging of EC accounts via account-description > is > > > > > > > > > > rather > > > > > > > > > > > hackish, but possibly the easiest one available so far, unless we > > > > > > reuse > > > > > > > > the > > > > > > > > > > > Tax-Info dialog. > > > > > > > > > > > > Unless the above questions are not finalised I wouldn't think > it's > > > > > > appropriate to merge VAT-report. > > > > > > > > > > -- > > > > > Maf. King > > > > > PGP Key fingerprint = 8D68 A91F 733B 2C1F 43B7 2B7C E591 E8E1 0DE7 > > > > > > C542 > > > > > > > > > -- > > > Maf. King > > > PGP Key fingerprint = 8D68 A91F 733B 2C1F 43B7 2B7C E591 E8E1 0DE7 > C542 > > > -- > Maf. King > PGP Key fingerprint = 8D68 A91F 733B 2C1F 43B7 2B7C E591 E8E1 0DE7 C542 > > > > > > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
