Automatically Generate and Save Reports #7

Closed
GoogleCodeExporter opened this Issue Aug 27, 2015 · 14 comments

Comments

Projects
None yet
1 participant
Contributor

GoogleCodeExporter commented Aug 27, 2015

Most users and professionals utilize a book keeping system to keep track of 
financial records. One way to do this is by utilizing various tools to produce 
reports on financial activity. 

As it stands, Bkper can produce charts and graphs to show financial activity 
based on a specific query, however it does not provide the ability to 
automatically generate and save reports. 

The idea behind this is that at a user specified time (say for instance at the 
end of the week or month) the Bkper system will automatically generator a 
predefined report (defined by the user) and save the report into the Bkper 
system. Not only will these reports be saved so the user can review them later 
they should also be manageable in that I can search out a report for a specific 
time. 

This functionality would be highly useful for users who are trying to view 
their financial history. Instead of having to manually enter hundreds of 
queries to compare activity over a year, it would be nice to compare a few 
monthly reports to get the same effect. 

Original issue reported on code.google.com by jmgil...@google.com on 12 Sep 2014 at 6:14

Contributor

GoogleCodeExporter commented Aug 27, 2015

There are some questions that would help us:


1) What do you think about the produced reports being saved to Google Drive?


2) What do you think about scheduling the generation of reports, say, monthly 
or weekly, and being sent to a list of predefined emails?


Would you mind help us with this questions, so we can move forward?

Thanks

Original comment by m...@nimbustecnologia.com.br on 13 Sep 2014 at 12:00

  • Changed state: Accepted
Contributor

GoogleCodeExporter commented Aug 27, 2015

Original comment by m...@nimbustecnologia.com.br on 13 Sep 2014 at 12:01

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect
Contributor

GoogleCodeExporter commented Aug 27, 2015

1) Saving it to Drive would be ideal. This way they are ensured to be backed up 
somewhere safe.

2) This is what I imagined would happen. Have a setup screen to select what 
accounts or groups are to be included in the report, how frequent it should be 
generated, and who it should be sent to.

Original comment by jmgil...@google.com on 13 Sep 2014 at 2:50

Contributor

GoogleCodeExporter commented Aug 27, 2015

Also, these reports should include more than just graphs or charts. Ideally the 
report should show the balance of each account at the beginning of the report 
period, all the transactions that happened during the report period for each 
account, and the final ending balance of each account at the end of the report 
period. 

This way we can have a good idea of how money was moved around during that time 
period. 

Original comment by jmgil...@google.com on 13 Sep 2014 at 2:53

Contributor

GoogleCodeExporter commented Aug 27, 2015

Issue 4 has been merged into this issue.

Original comment by m...@nimbustecnologia.com.br on 16 Sep 2014 at 2:39

Contributor

GoogleCodeExporter commented Aug 27, 2015

Original comment by m...@nimbustecnologia.com.br on 26 Sep 2014 at 12:38

  • Added labels: Priority-High
  • Removed labels: Priority-Medium
Contributor

GoogleCodeExporter commented Aug 27, 2015

Original comment by m...@nimbustecnologia.com.br on 26 Sep 2014 at 12:44

Contributor

GoogleCodeExporter commented Aug 27, 2015

We are developing an integration with Ultradox. A first example is already 
woking. 

You can go to http://www.ultradox.com and look for bkper tag to copy the 
example.
After copy you should click at the script "reload" button to authorize (Better 
guide comming soon).

The next examples will come with balances and charts.

Any feedback is welcome!

Original comment by kris...@nimbustecnologia.com.br on 26 Sep 2014 at 2:48

  • Changed state: Started
Contributor

GoogleCodeExporter commented Aug 27, 2015

[deleted comment]
Contributor

GoogleCodeExporter commented Aug 27, 2015

The better guide: http://about.bkper.com/articles_ultradox.html

Original comment by kris...@nimbustecnologia.com.br on 27 Sep 2014 at 12:07

Contributor

GoogleCodeExporter commented Aug 27, 2015

Despite of the inicial version of Ultradox integration provided, that can work 
for almost all cases, we will leave this Issue opened since we still 
researching a simpler way, probably less powerful and flexible than Ultradox, 
but can fit well simpler cases for the average non technical users.

Original comment by m...@nimbustecnologia.com.br on 8 Oct 2014 at 6:13

Contributor

GoogleCodeExporter commented Aug 27, 2015

Just added "Update" Feature to Google Docs Add-on. 

Now the inserted statements (charts and tables) are connected to bkper, so you 
can update all at a time later.
This feature is very powerful if used with query variables ($d, $m, $y), so you 
always get your report updated over time.

We will still let this Issue open until next steps:
- Autosend periodically (Each number of days or Months)
- Add ability to also insert transactions list, the same way it works on Sheets 
Add-on

Feedbacks welcome!



Original comment by m...@nimbustecnologia.com.br on 31 Oct 2014 at 12:45

Contributor

GoogleCodeExporter commented Aug 27, 2015

Released an Autosend feature on Google Docs Add-on to periodically update, 
generate pdf report and send by email.

Original comment by m...@nimbustecnologia.com.br on 7 Nov 2014 at 6:45

Contributor

GoogleCodeExporter commented Aug 27, 2015

Released Transactions Tab to  Docs Add-on. Now users can also insert 
transactions on document.

If the que query filters by one a permanent account, an additional column with 
balances of that account will be added.

The basic feature is working. From now on the issues should be filled separated 
so we will iterating over each one and releasing improvements.

Feedbacks are welcome so we can continue evolving the Add-on.

Original comment by m...@nimbustecnologia.com.br on 19 Nov 2014 at 6:46

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment