@AnBe, you have outlined a process in which the expense claim payer does not have authority to create a liability for the company. Yet an expense claim creates a liability. Therefore, the payer should not be allowed to enter the claim directly. It should only be entered after review and approval.
There is a difference between submitting an application for reimbursement of expenses and recording accounting transactions of a business. The latter should only be done by personnel authorized to do so and capable of determining whether the transactions are legitimate and have necessary approval. When approval authority is separated from those who take actions, such as employees incurring expenses they hope the business will reimburse, sometimes extra steps are necessary.
Manager does not have the ability to store pending transactions. Nor does it have any layered approval process. That has been suggested previously, and is in the ideas category. As you can see, I have moved your post and responses to it to the relevant topic.
Big Thread, and almost celebrating 3 years.
fully support this idea, feature and shall be implemented ASAP.
any transaction shall be approved by other user, specially for electronic documents which doesnât require signature & stamp
user with access to create, edit can change things, and if you cant trace on the log, at least if the log section associated with each transaction could be easier to view who create, when, who edit, what was the edit
as of now manager is big risk if multiuser on the business
Hello @Ayman
Do Not Be impatient About Implementation of this.
This is in ideas Category Because it is a great Idea And Improvement to Manager But Decision of Implementation is not yet Taken by @lubos ( The Developer ).
I am not a computer expert. I am a financial accounting expert. I have already seen this âauthorizationâ and âflow chartâ already being utilized in manager. A good example is for reccuring sales invoice (income cycle) and say reccuring payslips (expense cycle) where the system (I assume as a user) creates transactions and floats them somewhere waiting for approval and posting. The system then notifies you of pending source documents pending to be issued. You then have an option of creating the source documents or discarding them.
In my opinion, the only thing that programmers need to do is inject a code that says, for example in the sales/purchase quotation, the option of âsend to invoiceâ can be treated like the way reccuring invoice are treated. The quote creator is then notified that they donât have permission to create an invoice and that the same has been staged pending approval from someone with authority.
The process can be replicated where on the invoice view screen, the âreceived paymentâ can consider whether one has right to edit banks/cash transaction, and they can be notified that the payment has been staged pending approval/rejection from an authorized officer.
Maintaining physical control on cash and banks is not effective if the person who may misappropriate the resources already has authority to incur expenditure. The workflow ensures the AIE holder only receives/spends money that has already been approved by those charged with management.
That said, I know Manager is meant for small businesses, and small business have only one goal, to become big, and they often do so. I donât think you have envisioned a scenario where small companies that make it big by using Manager, can now start looking for ways to replace it. Most of many popular ERP Softwares have nothing on Manager.