Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handling reoccurring transactions #2

Closed
GoogleCodeExporter opened this issue Aug 27, 2015 · 11 comments
Closed

Handling reoccurring transactions #2

GoogleCodeExporter opened this issue Aug 27, 2015 · 11 comments
Labels
auto-migrated Priority-High Type-Enhancement

Comments

@GoogleCodeExporter
Copy link
Contributor 

At the current time a user must manually add transactions (unless using a 
third-party script) each month, even if a specific transaction occurs on a 
monthly basis. This is problematic for businesses who have multiple reoccurring 
transactions and do not wish to have to keep up with posting them every month.

A proposed solution is to implement a feature to allow a user to add 
reoccurring transactions into the systems. These transactions would have a 
clear path of cash flow (credit/debit), an amount, and a reoccurring date (I.E 
every 15th of the month, or twice a week on Friday's). 

An enhancement to the above suggestion would be for Bkper to automatically 
suggest reoccurring transactions based on the user's recorded habits. However, 
this SHOULD NOT be the only means to add a reoccurring transaction and the 
system should only suggest the transaction and not force it.

An easy to user interface should be provided to manage these transactions so a 
user can edit and/or remove them on the fly.

Original issue reported on code.google.com by jmgil...@google.com on 2 Sep 2014 at 12:39
@GoogleCodeExporter
Copy link
Contributor Author 

In this sense it would (also) be good to have the possibility to copy & paste a 
transaction that I repeat frequently but not regularly.

Original comment by jacob...@lagaroo.com.br on 3 Oct 2014 at 1:31

@GoogleCodeExporter
Copy link
Contributor Author 

There is a way (not to obvious) to copy a transaction: With the "advanced mode" 
opened you can select a transaction and its data will be copied to the form. 
Maybe we can extend this to the single line recording mode.
Anyway, this should go to a separated issue.

Original comment by kris...@nimbustecnologia.com.br on 3 Oct 2014 at 1:42

@GoogleCodeExporter
Copy link
Contributor Author

Original comment by m...@nimbustecnologia.com.br on 20 Oct 2014 at 8:31

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

@GoogleCodeExporter
Copy link
Contributor Author

Original comment by kris...@nimbustecnologia.com.br on 22 Oct 2014 at 11:18

  • Changed state: Started

@GoogleCodeExporter
Copy link
Contributor Author 

A recurring transaction can be created on the record of a transaction by, for 
example:

#homerent 2000 every month
#extra 500 every 2 weeks

The frequency can be: day,week,month and year.

Original comment by kris...@nimbustecnologia.com.br on 29 Oct 2014 at 8:28

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Contributor Author 

[deleted comment]

@GoogleCodeExporter
Copy link
Contributor Author 

This does not seem to appear anywhere in the current documentation. Also, is 
there a way to manage reoccurring transactions (edit/delete)?

Original comment by jmgil...@google.com on 24 Mar 2015 at 6:25

@GoogleCodeExporter
Copy link
Contributor Author 

For now, you can delete on the webapp (Look at the delete link - red X - on the 
recurring transactions list - left down panel). Not through the API. Do you 
need API exclusion?

Original comment by kris...@nimbustecnologia.com.br on 29 Mar 2015 at 6:15

@GoogleCodeExporter
Copy link
Contributor Author 

Sorry, I'm not seeing where the recurring transaction list. Do you mean it's 
supposed to be under the account list by the saved queries? I'm not seeing 
anything on my account.

Original comment by jmgil...@google.com on 29 Mar 2015 at 11:51

@maelcaldas
Copy link
Member

After some time testing and evaluating the recurring transaction feature, we decided to shutdown this feature in favor of other alternatives. Some reasons for that:

  • Its not being actively used.
  • There are many more alternatives to solve this need using Integrations with Zapier and Apps Script.
  • It's not part of our core features, in which we can keep our focus on.

As an alternative, we suggest using Zapier integration:

https://zapier.com/zapbook/schedule/bkper/

To have many drafts recorded in one Zap, just add \n to break lines and save in batch.

@maelcaldas
Copy link
Member

I forgot to mention. New recurring transactions is not be saved anymore. The already running recurring transactions will work until Jun 9, 2016.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-High Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maelcaldas @GoogleCodeExporter