ICAI RFP for Providing Practice Management Software for CA #1086
adarshmadrecha
announced in
Announcements
Replies: 1 comment
-
Here is an update as per ICAI Website (as on 20th August 2022) Comments / Observation:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
ICAI has yet again produced Request for Proposal (RFP) for providing Practice Management Solution for Chartered Accountants. This is the second time, ICAI is trying to "get a software built" for managing practice.
This post covers our public stand and some comments on the same. Consider this as an open letter to CA Community in general.
Ref: https://resource.cdn.icai.org/70398cmp-pms-160522.pdf or Alternative Download Link
Good Things 🤩
1. Intent
Words from RFP:
It's good that ICAI recognises the need for a "Cloud" based Practice Management Solution. We appreciate the efforts ICAI is putting into providing a Practice Management Solution for all practicing Chartered Accountants.
2. Mention of Industry leading cloud solution provider
Words from RFP:
Mentioning of AWS and Azure is a good step. This would ensure secured infrastructure is adopted.
Not sure why GCP (Google) is omitted.
3. Open-Source is promoted
Words from RFP:
This is a welcome move.
Critics 😖
1. Timeline
Words from RFP:
Practice management solution is very vast. Jamku (online version) started development in 2017. It's still under active development with many new modules releasing every couple of months. The expectation of the RFP is to complete full design and development in 60 days which is impractical.
2. No respect for Privacy or Client Confidentiality 🥶🙈
Words from RFP:
This means all the information entered by CA Firm will have to be shared with ICAI periodically. This is grave violation of client confidentiality.
Users of any Practice Management solution would expect that their data is never seen by any human, not even by Database Administrator. And the RFP expects all the "Intellectual information" should be shared with ICAI.
3. Small players are omitted due to some arbitrary clauses
Words from RFP:
These clauses would deter smaller players who genuinely have good products.
4. Enforcing outdated technology
Words from RFP:
Why restrict use of specific technology? There are newer technologies which would provide better user experience and performance than these older/outdated/propriety tech.
5. Requirement for providing Hard Copy (Printed Documents)
Words from RFP:
Why is there a need to provide "Hard Copy" of these documents? These documents would run into hundreds of pages (since it will contain screenshots). Hard copy concept is out-dated, un-economical and even harmful to the environment 😉
6. Vague wordings
Words from RFP:
7. SLA bar is set too high
Words from RFP:
2 Hours of "acknowledgement" time is too optimistic. It is not practically possible, after office hours for system at this scale.
Expectation of 2 hours during office hours would have been "fair" ask.
8. Ignorant to pricing model prevailing in the market
Words from RFP:
Cloud Software are sold on SAAS model. It would be rare to issue sales invoice of more than 10Lacs in "similar products".
Our suggestions 🙏🏻🙌🏻
1. Off the shelf rather than Build
Currently we have more than 10 solutions in Indian market. ICAI can evaluate and decide upon existing solution rather than building it from scratch.
2. Take feedback from members in practice
Take feedback from firms (both large and small) who are already using a practice management solution.
It's important to consider the needs of the firms from Trier I, II, III and IV cities.
3. Specify features in the RFP
Jot down the exact modules required in the software. Since the category "Practice Management" is relatively new (at least in India) the RFP should detail out what is the expectations. Current RFP is too vague on this.
Specifying list of features/modules will also enable members in practice set expectations and more importantly what they should not expect the software to perform.
Beta Was this translation helpful? Give feedback.
All reactions