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.
So it’s not recommended to use this yet? I just need something simple to record utility expenses since my current bookkeeping team isn’t experienced with making JE.
It worked flawlessly on V12. I’ve used it a bit in V13 and haven’t noticed any problems so far. Don’t hold me to it, but I think it’s okay to implement.