Com - Chapter - 2.2 2005 - 2
Com - Chapter - 2.2 2005 - 2
Com - Chapter - 2.2 2005 - 2
Highlights
35
Introduction
2.2.1
The Company was incorporated in June 1974 with the objective of
procurement and distribution of food grains and other essential commodities
so as to ensure their easy availability to the public at reasonable prices.
The Company was also engaged in distribution of petroleum products, tea,
medicine, sugar, etc., as well as public distribution of rice, levy sugar and
wheat, distribution of rice and pulses to schools under the Mid Day Meal
Scheme.
The Company with its headquarters at Ernakulam has five Regional Offices,
supported by 1,050 outlets (August 2005). There is a separate EDP section.
Computerisation
2.2.2
The Company in 1987 started computerisation of its applications
and initiated in-house development of software for Payroll, Financial
Accounting, Sales Accounting, Sugar Transportation Accounting and
Purchase Accounting. Development of software for Depot Management, Super
Market Billing and Stock Accounting was outsourced. While the in-house
applications were developed using Oracle and Developer 2000, others were
developed using FoxPro. The Company had so far spent Rs.2.65 crore (2004)
towards computerisation.
Objective of computerisation
2.2.3
To increase efficiency in :
sales accounting/analysis of outlets by producing accurate and
timely reports on sale and stock ;
evaluation of stock by determining its age ; and
installing a perfect Management Information System (MIS).
Scope of audit
2.2.4
The audit conducted during February-July 2004 covered the
functioning of the Financial Accounting System (FAS) and Sales Accounting
System (SAS) at Head Office and two* Regional Offices, Depot Management
System in three depots**and Supermarket Billing System in six Super
Markets/Labham Markets.
Audit objectives
2.2.5
Information Technology (IT) Audit was taken up to ascertain
whether the system was designed to ensure data integrity, reliability of inputs
and outputs, IT security and adequacy of controls.
* Ernakulam and Thiruvananthapuram
** Thrippunithura, Valiathura and Beypore
Supermarkets at Sadanam Road, Panampally Nagar, East Fort, and Kozhikode
Labham Markets at Peroorkada and Thrippunithura
36
Audit methodology
2.2.6
Data available in Head Office, Regional Offices, Depots, and
Supermarkets were analysed using CAAT@ namely IDEA (Interactive Data
Extraction and Analysis).
Audit findings
Audit findings are discussed in the succeeding paragraphs.
General IT Controls
2.2.7
A review of the general IT controls revealed that controls were
weak in respect of IT access, software acquisition, development and
maintenance. As can be seen from succeeding paragraphs, many controls were
either inadequate or non- existent.
Non-achievement of intended IT benefits due to partial computerisation
2.2.8
2.2.9
Despite having an in-house software development team, all modules
of FAS and SAS were yet to be developed. Thus, MIS reports on age-wise
analysis of stock of commodities, sales analysis of retail outlets and
commodity-wise analysis could not be generated as planned, and hence could
@ Computer Assisted Audit Technique
37
not facilitate the decision making process. As the Company failed to set up a
proper network, the transfer of data from retail outlets to Regional Offices and
Head Office needed for timely generation of reports, was affected. A proposal
(January 2004) to develop a network through CUSAT* also did not yield
results and hence was dropped.
Network connections
essential for timely
transfer of data to be set
up.
The Management stated (April 2005) that steps have been taken to develop
software, for web enabled data transfer and that more technical persons would
be recruited as System Support officers. The Government also stated
(August 2005) that computers had been provided in all 56 depots and the
software for inventory maintenance was being implemented and the depots
were using the internet facility.
Lack of systems development methodology
2.2.10
Organisations implementing IT Projects should decide upon a
standard methodology to design and develop a system. There should be proper
documentation on various processes involved in systems development,
indicating, inter alia, personnel authorised and responsible to manage
application development and its implementation. Audit scrutiny revealed that
no such documentation existed in the Company. Further, documents such as
User Requirement Specification, System Requirement Specification, User
Manual and logs of tests made and acceptance of software relating to the FAS
and SAS developed in-house were not available with the Company.
In the absence of the above, Management could not ensure that all
requirements have been incorporated in the system developed in-house.
Government stated (August 2005) that these would be taken care of in the
software being developed and implemented in depots and in the future
software developments.
Instances of deficient system development process reflected in the functioning
of the software noticed in audit are discussed in paragraphs 2.2.11 and 2.2.12
infra.
Improper design of retail outlets/depots codes.
2.2.11
The Company assigned 4-digit codes for outlets/depots, the first
digit indicating the region, the second digit indicating the district and the next
two digits identifying the outlets under a district. No uniform and scientific
system of coding was, however, followed and there was a mix up of numerical
codes and alphanumerical codes.
The system at Tea division, however, accepted the first four alphabets of the
depot names as depot codes, which were entirely different from the codes
adopted for the sales accounting system.
38
The Government stated (August 2005) that the 7-digit outlet code had been
introduced in 56 depots and would be incorporated in other outlets, after
re-designing/developing the software.
Absence of uniform commodity codes
2.2.12
The commodities dealt with by the Companys outlets are broadly
classified as Maveli items* and Non-Maveli items**. The non-Maveli items
are procured centrally, regionally or locally. They may include consignment
items, which are not taken to stock, but sales are billed.
As per the system of coding for commodities, Manager of an outlet could allot
any code number below 9999 to any item including the consignment items.
Common commodity
codes were not designed. Thus, there was a mismatch of codes given by various outlets. While the
Commodity code for a
Supermarket at Sadanam Road, Ernakulam classified the commodities into
particular item varied
five categories of 65 groups, the Supermarket at Panampally Nagar,
from outlet to outlet.
Ernakulam had 10 categories of 47 groups. The categorisation and grouping
had no basis and there were cases of overlapping/ duplication. The depots and
supermarket godowns followed their own system of coding for the
commodities.
Commodity-wise
consolidation of sales
and stock not possible
2.2.13
In any major IT system, the duties of various IT staff are required to
be properly defined and segregated, with clear responsibilities. Audit analysis,
however, revealed (June 2004) that the IT staff in the Company did not have
Essential commodities and their product derivatives most of which are procured centrally
and marketed in the companys brand.
** All other items such as provisions, stationeries, bakery items, meat product, vegetables,
etc
39
Moreover, in order to control authorised access to data and systems, the duties
and responsibility of the users of the system need to be decided by the
management, based on which the required modules are provided to the
individual users/sections. It was noticed in audit that though user level
passwords were provided but these were common for the same group. Thus,
the passwords were not unique and were shared by the staff. For example, to
access the Financial Accounting module, user name and the password were
common for the Finance clerk and the Managers. In effect, the sharing of login
ids and passwords defeat the very purpose of control as accountability,
confidentiality and integrity of data and programs would be affected.
Maintenance of a unique user id and password is required for the purpose of
fixing responsibility for unauthorised access to data.
Government stated (August 2005) that once MIS division was adequately
strengthened, there would be clear definition of works handled by each staff.
It further said that proper password maintenance and back up procedure had to
be implemented by unit managers. Frequent changes of staff in each level was
a bottleneck in this respect, which would be solved when system support
officers were appointed. The reply clearly shows that the Government has not
yet grasped the importance of segregation of duties and access controls in an
automated system controlling a turnover of more than Rs. 400 crore per year.
It is important for the Government to realise that in a computerised system
segregation of duties is as important as defining duties and responsibilities in
conventional system. As in a manual system it is inconceivable that a clerk
will have the same financial powers and responsibilities as a manager,
similarly in a computerised system appropriate differentiation has to be
enforced albeit by technology enabled methods such as assigning privileges
according to the user profile and access controls by passwords, etc.
Absence of Business Continuity Plan
No documented back up
procedure
2.2.14
The Company did not have documented procedures, operating
manuals and a disaster recovery plan. Though daily backups were reportedly
taken, absence of a disaster recovery plan had the risk of potential data loss,
with consequent disruption of business, in case of any disaster.
Application controls
2.2.15
Application controls are included in the IT Systems to provide
assurance that all transactions are valid, authorised, complete, accurate and
properly recorded. Shortcomings in application control noticed during audit
are discussed in the succeeding paragraphs.
Deficiencies in Sales Accounting System (SAS)
2.2.16
The system was installed in Regional offices for consolidation of
monthly sales at retail outlets, wherein credit sales to schools for noon feeding
40
2.2.18
According to the instructions for stores verification, unit managers
should declare items as per book stock as on 31 March. The Stock verification
There is no provision for
accounting of shortage in officer would verify whether the declared stock and actual stock are the same.
Items verified as good stock will be carried over as opening stock as on
stock
1st April. If there is any difference between declared and verified stock,
disciplinary action will be taken against the unit manager. There is, however,
41
2.2.20
A test check of the computerised physical verification reports of the
super markets at Sadanam Road, Ernakulam; Panampally Nagar, Ernakulam
and Indira Gandhi Road, Kozhikode (as on 31 March 2003) revealed that the
stock declared by units based on the database was less than the physical stock
in 26 per cent cases and was more than the physical stock in 39 per cent cases.
Thus the system did not ensure complete accuracy in inventory management.
Government stated (August 2005) that steps would be taken to address the
deficiencies pointed out.
Display of minus balance in stock
No provision to prevent
billing when stock is nil
2.2.21
As per the existing billing system, bills are made, without reference
to availability of stock notwithstanding any wrong product code, thus resulting
in negative stock values. All the items declared as negative stock are treated as
excess stock under the presumption that each accumulated negative stock is
due to a billing error and compensating excess stock will be available
somewhere in the shop. This indicates deficient software development
whereby validation checks were not incorporated into the system.
Thus, the computerised system introduced to ensure accuracy in stores
management ended up posing a risk to the operations and was unable to
prevent possible covering up of theft, pilferage, inaccuracy and inefficiency,
as no steps had been taken to prevent the printing of bills when the quantity as
per stock becomes zero. Proper inbuilt controls are needed to prevent
generation of bills for an item whose stock is nil.
Government stated (August 2005) that steps would be taken to address these
problems.
42
Government stated (August 2005) that the new software being developed
would take care of these problems.
Conclusion
The Company started computerisation in 1987 in order to increasing
efficiency in sales accounting/analysis of outlets by processing
accurate/timely reports on sale and stock, evaluation of stock by
determining its age and installing a perfect MIS, but failed to fully
achieve its objectives. Despite incurring substantial expenditure, it could
computerise only 162 out of 1110 outlets/depots till January 2004. The
present system has poor access controls and the database is plagued with
inaccuracies. This leaves the system at a risk of being manipulated to
cover up theft, pilferage and embezzlement.
In order to monitor speedy movement of commodities in the outlets and to
evaluate the age of stock, it is essential to capture commodity-wise stock
position in Outlets/Depots and plan procurement and distribution
accordingly, but the Company could not ensure development of all
modules of the software, networking of the outlets and installation of MIS
to facilitate decision making, on the basis of sales analysis and market
trends. As a result of non-uniformity in the coding of commodities
generation of meaningful MIS reports, even if desired, is not feasible.
43
Recommendations
44