It would be a nice addition to Manager, if authorizations for entiries is implemented. It is useful feature when a user enter a voucher, then a manager approve as some type pf entries require authorization before it can affect financially. A tab could be added to notify the top level user of transactions that require approval.

In our organization we have our sales guys have access to sales quotes, sales orders and purchase orders on occasion. Once approved, we convert to sales invoice and send the document to the customer and copy the rep on the sale.

[image] Tut: purchase vouche Purchase Voucher = Purchase Invoice.

Then all the questions I listed earlier apply, and probably others I didn’t think of yet.

Approval in accounting systems is not new. Many accounting systems have it.

Authorization comes together with audit trail and user permission level I Imagined. As long lubos yet to made later both flexible and reliable. Authorization have to wait. This is complex feature.

Hi, Looking at the communication on the topic, what Tut says is right in view of program integration. But surely this requirement is a thing which every company having a hierarchy will want for. To simplify this idea to work, lets look at this way: why we need levels of authorization is to maintain a work flow and to avoid duplicates, errors and doubtful transaction and also the fact that to excercise the authority by the senior officer in the line. So, lets solve this all, by introducing a work flow in Manager : System should allow in setting to create a workflow from quotation to invoice.( quote - sales order - PO - PI - GR - SI -DO ) each company can set its own way, → So,this will avoid duplication, errors and confusion. the server and cloud system allows muti user, and allows to assigning Tab (function) to user. So System only need to print automatically the user name. → So, this solves the problem to show the ownership of document/transaction. i think its worth realizing that the Manager or its use is been put to much advanced now than merely being an accounting software. i believe the developers and most active members in this forum can realize that. so these requirements are no surprise and it only shows the growth of satisfied customers.

This features requires some other functionalities to be added and it will make manager more close to ERP. I worked with Oracle E-Business Suite and provided consultancy as well. It has such a big engine for this purpose you can’t take complete hold of it. For this function you requires an automation process most likely workflow, notifications, hierarchy on each process in company and authorization control. Complete user features which are defined with employees and software users together. Forms status and auto status change upon approval or rejection and you can’t delete any record after it has been sent to approval engine. Thus it will just increase your database size and load to your software. I am not against this functionality but @Tut has asked questions, are first to consider before asking such features. BTW manager is for small business. Consider your business scale before over loading your employees with such huge responsibilities.

In some smaller accounting systems, the posting (or as you call it authorization) is made with below reasons: To have the accounting head some control on what is entered or not in financial reports. To restrict modification of entries after posting without knowledge of the accounting head. Normally, posting is just a way of controlling. No changes should be made on logic and rules, especially on costing, etc. No matter how many levels of authorization will there be, the final step is posting, and that is where the accounting entry is made in the ledgers. Generating of financial reports should have the ability to incude unposted transactions or not.

@jeffbangquil Transaction authorisation will be a very cool feature to have. But the user permission system in Manager is currently not ready for this feature . There is a lot of work to be done to improve the user permission before further advancements (including authorisation) could be made. See this thread for example [image] Suggestion for improving user permissions Hello Guys I just realised this and have to draw your attention to it. The current user permission is seriously flawed. I tested with a procurement officer user who is supposed to have access only to create Suppliers and purchase orders and noticed the flaw. [0] The procurement officer is able to generate a spend money transaction even though he has no bank or cash access by duplicating the spend money transaction he is allowed to view. He is also able to edit and update records Purchase … I have been waiting since 2014 to have the system’s user permission workflow improved so that I could go commercial with it here in my country (issue proposals to get organisations to buy and and I get something from installing and setup) but I have waited in vain, price, user permission and occasionally authorisation is what they all ask about first. No organisation will deploy the system in their server here in my country currently with the nature of user permission workflow Manager currently has, the risk is too high (my only disappointment with manager.io) Authorisation to post and strong user permission is very much a very basic requirement in accounting software these days but to my surprise it totally ignored here. Looks like the Manager.io team is focused on perfecting the desktop version for now and maybe in the future they may consider enhancing user permission and perhaps include authorisation to post. You gonna have to wait for long.

[image] Abeiku: Looks like the Manager.io team is focused on perfecting the desktop version for now I would be very surprised if supporting a particular deployment platform was a major focus of Managers feature release plans (particularly the one which produces no financial return). Looking a what software development is actually achieving, the reverse appears to be the case, ie supporting a broad range of deployment platforms. [image] Abeiku: Authorisation to post and strong user permission is very much a very basic requirement in accounting software … maybe in the future they may consider enhancing user permission and perhaps include authorisation to post. I do however agree any product can not be everything to everyone. It is sensible to for Manager to be optimised for a particular market segment. Both in terms of: Product function:- Accounting program, Material management system, Budget forecasting, Personnel management, etc). As well as Business size:- personal records, sole trader, small business, Large business / corporation. What is a “basic requirement” is very dependant on what market segment the software targets. As the target business size increases, authorisation requirements become more complex. However so does program complexity and cost to support the program. Hence product focus is important. Clearly I have zero input in any of this other than to observe specifying a “basic requirement” really does depend on what each user perceives Managers main market to be.

Multi Level Authorization

ideas

Topic		Replies	Views
A Practical Approval System for Manager Using Forms (Draft Entry) and Copy-To ideas	4	317	June 27, 2026
Authorization of Transactions Uncategorized	3	298	June 4, 2024
Suggestion for improving user permissions Uncategorized	72	5477	November 12, 2022
Approval process in system Uncategorized	7	746	May 31, 2026
One issue preventing manager from becoming a market leader ERP Uncategorized	23	2442	October 28, 2021

Multi Level Authorization

Related topics