Suggestion: Transaction Statistics Report

Hello @lubos
I was looking for a quick way to get the total number of transactions entered in a given period but couldn’t. I was wondering if we could have a statistics section in reports for statistics like:

  • Transaction count by transaction type

  • Transaction count transactions by user

  • 0 value transaction count by transaction type

  • 0 value transaction count by user

  • Unassigned special accounts

  • Unclassified accounts and control accounts

  • Number of inactive accounts, special accounts, groups, transaction types, users … etc.

  • Duplicate transaction numbers

  • Transactions without numbers

Alternatively, we can have reports for masters a tab view for all transactions showing:

  • Transaction
  • Number
  • Value
  • Date created
  • Date modified
  • Created by
  • Modified by
  • Description / summary
  • Total tax value


1 Like

It isn’t clear how or why you would use some of this information. Can you provide use cases? Also, some of it is already available:

This would essentially be the entire database, plus some of its history. What is the use case? What useful information would you get from such a report that you don’t already have from the General Ledger Transactions and Tax Transactions reports?

Then I proposed alternative for all transaction statistics :point_down::point_down::point_down:

This should solve all the needs for transactions statistics and then I would need this:

  • Number of unused accounts, groups, control accounts, special accounts

So you suggest a new tab in the program, but are not willing to explain your use case(s). And when it is pointed out where some information is already available, you either add to your requirements or withdraw the request. Then you throw in transactions in Suspense to justify having statistics on groups and other accounts. And apparently, you don’t want to address why existing reports that seem to give the information you ask for are not adequate.

You have been a forum member for most of a year, long enough to have noticed that the developer is often accommodating when new feature requests are thoughtfully justified. If you want your ideas to be considered and supported, you need to explain their benefits for users.

Why are you so tense? I know @lubos is a very busy man and I appreciate the work he does greatly. I don’t know what you understood from it all but look at the title: Just a suggestion. If you do not want suggestions then please say so.

Back to your comment, yes I withdrew some SUGGESTIONS because based on your initial comments I saw that they were unnecessary … So, what did I do wrong here?

Second, also yes, you were clearly playing on words when you say:

That is a clear evasion of my point, tell me how “special accounts” is a proper classification, any accounts that remain there are effectively unclassified. I am not going to discuss the definition of the words “Classified” or “Assigned.”

What I SUGGESTED was either giving us a statistics section in the reports OR giving us a tab we can use to make our own statistics to give red flags on:

  • Completeness of records (e.g. if there was a period without any invoices, receipts entered: say the staff is taking customer collections without issuing invoice and/or receipt. There is no other way to find this not even the bank reconciliation)
  • Integrity of data (i.e. proper unique numbering of transactions, this will certainly help when auditing, reconciling and just referencing transactions for retrieval)
  • Who to followup with (i.e. created by and modified by and when)

If you want better explanations, please ask valid questions.

Solved here