@Fred1 the journal Entry only allows Supplier Party on the creditors account, I havent tested the effects of ignoring this but I thought it was a good idea and would like to look into it. Likely later as I cant test it right now.
Keep contributing!
I also like the idea of having some expenses recur automatically, like rent or server costs. I’ll look into subscriptions later (is it still called this?)
If you have a bit of time on your hands and can help with the testing or development, please join in on telegram. Otherwise please continue giving your ideas on this thread.
@adam26d well done.Since it is payment, accepting supplier as party under creditor should be the norm and it will be great if you test it and incorporate.Subscription is called now auto repeat.Including it sound good
I prefer to book the bills with invoices. Then pay them with invoice payment. @Monolithon also having a point about this:
And use auto-repeat to repeat them. No need to reinvent the wheel.
And use Expense doctype for the more-cash-basis transactions.
That’s why I prefer to have Expense doctype simple and not having too many fields to fill, let alone having to care line by line. Just do quick and simple.
In my view, this Expense doctype purpose is simply to be the frontend to JE. So non-accounting users don’t have to deal with JE.
Giving Error on install
Installing expense_request…
Updating DocTypes for expense_request: [============= Updating DocTypes for expense_request: [========================== Updating DocTypes for expense_request: [========================================]
bad json: /home/frappe/frappe-bench/apps/expense_request/expense_request/fixtures/notification.json
An error occurred while installing expense_request:
No JSON object could be decoded
Yes, actually Expense Entry is just a simpler form that creates a JE, you can do it directly. This is more for those who don’t understand debits and credits. Also approval convenience. And Yes cancelling should come eventually.