Why you can’t assess auditing software just the same way as accounting software.

Why you can’t assess auditing software just the same way as accounting software.

As a representative of a popular audit software product, I often get asked by audit practitioners whether I could avail them with a demo copy of the software so that we can ‘play around with it’.

Since financial audit and accounting are related, how different can the respective software be? The self-check procedures accountants use to decide whether an accounting system is working are quite simple and straightforward in their design: You put in a piece of data at one end and check to see if the information that has been crunched through the system and that comes out at the other end meets your expectations. A simple example of such a procedure would be taking a pocket calculator and adding up the column of numbers your assistant gave you to see if it agrees with the total at the bottom of his schedule.

However procedures like these only tell you whether the accounting softwareis able to properly process information that has been fed into it according to the rules that you specify. It’s the sort of procedure where because you know in advance, what the results should be, you can test it quite easily using that input vs. output model.

The real job of an accountant however, is not merely entering a transaction in the records but rather of knowing how to classify transactions. For example, which engineering items are repairs and which ones should be treated as new fixed assets instead? Is the value of the motor car as shown in the accounts still valid or does it need to be marked down – or even up? The accountant is also responsible for summarising the transactions in the way that most suits the people who need the information and presenting it in a way that makes sense. Seen in this light, it is not possible to create “accounting” software as these accounting judgement roles cannot be played by a computer program. What we refer to as accounting software should really be referred to as bookkeeping software.

Auditing, on the other hand, is the checking process. Confirming that data going in at one end of the system comes out the way it should at the other end, is just one audit objective and frankly, it isn’t even the most important one. The most important objectives of audit are to determine whether the financial statements (a) contain all the information they should contain, (b) contain only the information they should contain and (c) are reported in a way that conforms to a pre-agreed standard.

It does involve the arithmetical accuracy checking that most accountants do in the first place. However it also involves checking that the basis of classifying and summarising information was properly done – a test of judgement(because so-called accounting programs will execute incorrect instructionsto summarise or classify information just as faithfully as they will correct ones.)It also involves checking that there is no information missing  - another judgement test.It also involves checking that the information is not overstated – also a matter of judgement. That’s not all however. International Standards on Auditing now actually pay attention to the process that was used to evaluate the accountant and it requires certain mandatory steps to be taken and documented, no matter how certain the auditor may be of the correct situation.

This leads to an interesting question then; is it possible to create software that can meet all of these requirements of the audit? Data interrogation and sample selection software could go through the accounting information and try to extract information that makes sense but could it tell if the classification method used by the accountant was wrong? How would it decide if the evidence provided was acceptable? This is a trickier proposition and indeed, nobody has yet been able to design software that actually “audits”, much in the same way that nobody has been able to design software that does “accounting.”

What does this mean for a practitioner thinking about buying audit software? Audit software doesn’t have transactions that you can insert at one end and click to see if they have been properly classified at the other end. Instead it provides what amounts to very a long and sophisticated checklist (or series of checklists) of the all the procedures an auditor needs to carry out to determine the three objectives and comply with the mandatory procedures mentioned above. These are extensive and run, at present to nearly 800 separate mandatory procedures in the International Standards on Auditing. And that’s not counting the steps in the audit programmes in each section of the audit file. There is only one way to tell if this collection of checklistsworks properly; carry out an audit with it and submit the results of the audit to an independent quality reviewer to determine if the work was done properly.

People who aren’t skilled enough to know how to use the checklist will not be able to gauge whether they failed or passed the quality review due to an inadequacy of their checklist or due to their failure to use it properly.

Also, although the ISAs prescribe the approach to the audit to which all auditors should conform and in some instances even stipulate the exact tests to be carried out, they are not precise enough about how to do it. For example, there are more than a dozen ways to develop a sampling frame that produces a truly random sample. Which one is most appropriate? What’s a reasonable maximum or minimum sample size? If your sample contains an error, by how much should you extend your tests if at all? What’s the best way to calculate materiality? How many levels of review should there be in a particular assignment? The ISAs just don’t say.

Audit software helps by providing handy computation tools for sample design and selection and guidance on developing materiality. They even provide specific program steps for various areas of the audit. They also nudge you, (by blocking access to particular file areas and questionnaires), into using the work flow sequence that is most efficient or effective. These features, in the aggregate, comprise the methodology of particular audit software.

Without training by a person with proper experience on the specific methodology of a particular piece of audit software, it could be difficult to understand how all the questionnaires, computing tools and checklists work together to achieve efficient compliance with the ISAs.

For these reasons, taking a demo copy of audit software to try it out is unlikely to be helpful unless you are also willing to undergo not just “demo” training in the methodology but also a “demo” quality review – all lengthy and costly steps.

I would suggest that a more reassuring route would be to work through a presentation with an experienced user and ask to be shown all the features that you consider to be key in your existing methodology to ensure that they are present. Another, perhaps more important source of reassurance would be to look at the number of other practitioners relying on the same software to carry out their work successfully. The more there are, the more likely that it is the right product for you.

 Joe Gichuki

Joe, a member of ICPAU, is the CEO of Kawai Consulting, a firm that specialises in providing technical and capacity building services to financial auditors. Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Random news

ACCOUNTANCY PROFILE

“Anybody can succeed if they discover their talent and purpose for living, go ahead to develop it and take a step to deploy it. The 3 Ds (Discover, Develop and Deploy) have shaped my life and, it is a personal success model that can positively affect other people’s lives”. 

Who is Moses Kasakya?

Moses Kasakya was born in Budaka district in Eastern Uganda. It is also here in Budaka that he got his Primary and O-Level education. He later moved to Masaba senior secondary school for his A-level where he undertook Mathematics, Economics and Geography. From there, Moses went to Makerere University for a Bachelor of Commerce Degree where he graduated in January 1994. Moses is also a member of the Institute of Certified Public Accountants of Uganda. Moses has a Post Graduate Diploma in Financial Management and Post Graduate Diploma in Revenue & Tax Administration. Moses has over the years undertaken specialised trainings in Leadership, Fraud Risk Management, Corporate Integrity and Internal Audit. He is also a member of the Institute of Internal Auditors, USA.

With such education background (which he terms simple education), Moses is so much more than what the eyes see. Within him lays a wealth of knowledge and determination, within him a clear conscience exits, and when you chat with him, his words scintillate with a lot of remarkable brilliance.

Professional Journey

Moses’ professional journey has been a steady and progressive affair. In his own words, Moses says that “God has blessed him where he has been able to move from glory to glory as far as his professional career is concerned”.

Moses started working when he was still a student at Makerere University as a Research Assistant at Uganda Bus Company.  As a Research Assistant, his role was to collect relevant information that would enable the management of the bus company devise means of competing in the transport market. At that time tax commuter vans (matatu) were posing a direct competition especially for shorter around-town trips like Gayaza, Lugazi and Kayunga. Moses also taught Economics in Butebo S.S, Palisa District.

Immediately after completing his studies at Makerere University, Moses joined Kyagalanyi Coffee Limited as an Accounts Clerk. In 1996 he joined J. Lutta Coffee Limited (defunct) as an Accountant. In September 1997 he joined Uganda Revenue Authority (URA) where he began as Assistant Revenue Officer in Customs for 3 months. In 1998, Moses was posted to Jinja as Head of VAT Audit for two years. In 2000, he was posted to Tororo as the District Revenue Officer for two years. In 2002 he was posted back to Kampala to work in the Commissioner’s Office as a Tax Inspector where he was tasked with responsibility of advising the commissioner on Compliance matters at districts.

In 2004, he was appointed as Senior Revenue Officer, Internal Audit. Towards the end of 2004, URA commenced a restructuring program following results of the commission of inquiry. Following the restructuring exercise, Moses was appointed as a Supervisor, Tax Investigations in May 2005.

Towards the end of 2007, Moses took leave to go ponder and pray about his stay in URA as a “tax collector”. Being a Christian, the phrases like “tax collectors will not go to heaven” had started to affect him. During this break he learnt that tax collection is biblical and that those that won’t go to heaven are those that either cheat the taxpayers or cheat the government as advised by John the Baptist when tax collectors sought him out (Luke 3:12-13). Further appreciating that tax was to enable government administrators provide public services where individuals cannot afford on their own like construction of roads and other infrastructures; and that everybody must pay their debts including tax as biblically advised by Paul (Romans 13:5-7). Most satisfying was when he affirmed that even Jesus paid tax (Mathew 17:27). Moses’ conclusion was that if the process of tax collection that ends with tax payment was evil, Jesus would not have accepted to participate in it.

While still on leave where he had gone to ponder on his stay in URA, where he made interesting discoveries, Moses was recalled by his Commissioner and asked to manage a new project, the Compliance & Integrity Enhancement Project. As Manager, Compliance & Integrity Enhancement, Moses was to advise management on best practices in Compliance and Corporate Integrity and also coordinate implementation of Integrity Enhancement Initiatives.

The objective was to develop integrity driven workforce to enable the Authority accomplish majorly four outcomes i.e. Increased revenue yield, Reduction in costs of fraud, Improvement in Client satisfaction and attain Positive Reputation for the organisation and individual staff. To Moses, this was an exciting opportunity to positively impact the values of his fellow workmates. “This was and is an engagement I am so proud of” he said, with his eyes glowing with contentment. In light of the integrity enhancement program, and with support and involvement of the URA top management, the URA Integrity Perception index made a drastic gain from 51% at the time to about 80% in five years.

After 5 years in that position, Moses felt it was time for a move. He got an opportunity, Umeme Ltd as Integrity Manager responsible for forensic auditing, internal policy compliance, corporate integrity and physical security. This move to Umeme Ltd helped him to advance his exposure to a publicly listed organisation.

In November 2015, Moses got another opportunity with the Uganda National Roads Authority (UNRA) as the Director Internal Audit. He is part of the top management team tasked with the responsibility of transforming UNRA’s performance following the public scandals around its operations.

Also worthy noting is that in between all his assignments in the different organizations Moses continued teaching on professional accountancy courses, particularly Advanced Financial Accounting, Taxation and Audit. He believes teaching is one of his purposes for living. He contemplates progressing this calling through publishing articles or books that will be relevant even to people in places he can’t reach or long after he is gone.

On how he achieves objectives

As a Director, my role is to identify the “end in mind” in line with the company strategy. Then sell that “end in mind” to key stakeholders while accommodating prudent adjustments. In my case the key stakeholders are the Board Audit committee, Audit clients/ management and my staff.

With clear sight of the “end in mind”, I put my controls on majorly two things. One is the plan plus resources to achieve the “end in mind” and the other is to ensure quality of the final product of our services. In this case the quality of findings in the report and advise therein. I normally do not entertain results of “excited” auditors. I entertain results with sufficient evidence and those that address risks which make a boss lose sleep. In between the plan and final product I let employees deploy their creativity as this boosts their morale and interest in their work.

Both by law and company policy, UNRA employs CPAs i.e. Members of ICPAU across the various directorates and specifically in Finance and Audit. In internal audit department we also have other major professionals such as engineers and IT professionals.

On Staff training and knowledge enhancement

“The management team at UNRA led by Mrs. Allen C. Kagina believes that the foundation of success of any institution lies in the quality of the employees. At UNRA we assess quality of staff on four fronts; we review whichever staff are competent, productive, motivated and are of integrity” Explained Moses. To this end we dedicate sufficient resources to improving the quality of our staff including training.

On the role of ICPAU in promoting the accountancy profession in Uganda and beyond

I remember when ICPAU came in as the national accountancy body. It came in with a massive and aggressive program of encouraging people to study accountancy and it continues to do so. Secondly, it developed the curriculum to guide trainers of the profession. It also enforces the quality of the final products (we accountants) to be released to the public through administering examinations

The Institute enforces quality of the accountants through mandatory continuous development programs or else some would become stale and an embarrassment to the profession. It further maintains up-to-date articles via the website. It also registers and publishes a list of members on the website to make it easy for interested parties to confirm who is a CPA and who is not.

The lobbying for the Accountants Act, 2013 was a milestone for the accountancy profession as a whole. Unlike before, masquerading as an accountant has become a crime. The institute also lobbied government to sponsor candidates especially those working with government entities and this boosted the numbers of accountants in Uganda.

However, I believe that the Institute should do a little more on fighting fraud in the country. He therefore calls upon ICPAU to be more proactive take initiatives to investigate into media reports; The Institute will not only enforce its public interest but also save the country’s resources for the benefit of all of us and for generations to come.

OnRole of Government in promoting accountability

I believe Government always means well. It has put in place infrastructures that enable accountability and ensure standards are followed. Some of these include the enactment of the relevant laws like the Accountants Act, 2013, Public Finance Management Act, 2015, Leadership code administered by IGG, Anti-Corruption Act and setting up the Anti-corruption court.

The Government also put in place services of Auditor General to check and advise on compliance, effectiveness of controls and value for money. It also set up respective Committees of Parliament to review accountabilities of Government votes. The Government has also invested in automated information management system (IFMS) that boosts efficiency in accountability and continuously institutes commissions of inquiry where things go wrong.

To that end it is objective and fair to say that government means well on matters of accountability. However, it still comes back to us the professionals in our respective industries to ensure that we live up to our codes of conduct.

A word to Accountants

First and foremost, it’s a privilege to qualify and enroll as an accountant. It is only accountants that are most likely to be found in every entity including spiritual entities given that all entities have money matters.

Accountants should position themselves as strategic business advisors and not gain comfort in being book keepers or just producing financial reports. In addition to analyzing the financial data and hopefully its implications, the accountants should go ahead and advise on viable business opportunities or better still use the accounting knowledge and skill to start business ventures to boost the economy.

I also encourage accountants to explore the political platform in Uganda, specifically the Parliament of Uganda to help law makers on matters of finance.

I call upon all accountants to uphold integrity; acting with integrity minimizes some risks and illnesses associated with stress. People whose wealth is through fraudulent means never gain complete joy in life as the fraud element always comes back to haunt them, say when a child or friend inquires into how they made money even when the inquest is innocent. People would rather develop the potential of someone with integrity and let go of a competent product that is fraudulent.

BUSINESS PROCESS IMPROVEMENT: EMPHASIS ON CYCLE TIME

BUSINESS PROCESS IMPROVEMENT: EMPHASIS ON CYCLE TIME:

Cycle time refers to the period required to complete one cycle of an operation; or to complete a function, job, or task from start to finish. Cycle time is used in differentiating total duration of a process from its run time.

It is the average time between successive deliveries. In other words:
Cycle Time = Operating Hours per day / Quantity per day
For example, assume that the plant operates for 10 hours per day and need to produce 60 computers each day. The Cycle Time is 10 / 60 = 1/6th of an hour,which is 10 minutes. In other words, on average every 10 minutes a computer rolls off the assembly line.
“Quantity per day” is the same as Throughput for a day, in the example 60 computers per day.
As the old saying goes that time is money, critical business processes are subject to the rule of thumb that time is money. Such processes are usually carried out through resources that often result as bottlenecks. Unfortunately, the products derived from these processes are usually the ones that matter most to customers; therefore, the products need to be delivered as fast as possible. This cuts across both to the internal and external clients, manufacturing and service industries.



    Competitive Advantage:Business and service delivery has changed over recent years, and competitors threaten in almost every market. Reducing product cycle times increases the potential to develop and deliver innovative products and be first to market with them. This is especially true if you compete against multiple providers that offer similar products or close substitutes. Every day you reduce your cycle time is a day you gain in meeting or beating competitor product launch dates.
If company A cannot supply the desired product at the desired time, a competitor will.Inthisnew environment, cycle time reduction provides a key competitive advantage.

    Customer satisfaction: Reduced cycle time can translate into increased customer satisfaction. Quick response companies can launch new products earlier, penetrate
New markets faster, meet changing demand, and can deliver rapidly and on time. They can also offer their customers lower costs because quick response companies have streamlined processes with low inventory and less obsolete stock. According to empirical studies, halving the cycle time (and doubling the work-in-process inventory tums can increase productivity20% to 70%. Moreover, quartering the time for one step typically reduces costs by 20.05%.

    Improves quality: With reduced cycle times, quality improves too. Faster processes allow lower inventories which, in turn, expose weaknesses and increase the rate of improvement. After eliminating non-value added transactions (as opposed to value added transformations), there are fewer opportunities for defects. Fast cycle time organizations experience more rapid feedback throughout the supply chain as downstream customers receive goods closer and closer to the time they were manufactured.

    Cost savings: Cycle time reduction saves costs.

Typically, optimizing efficiency in production processes helps you cut down on cycle time, which saves you money. This often results from thorough analysis of every step of the development and production process, refinement of inefficient steps and removal of steps unnecessary to the process. Each hour or day cut from the product cycle time saves money spent on labor, equipment and utilities used in production.
For example, if manufacturing cannot respond quickly and if a high service level isdesired, then the organization must either keep high inventory or lengthen the promisedlead time. Also consider a service industry: Suppose the central store spends less time on internal clients, they will save on deterioration, pilferage and insurance if some of the inventory is insured. 

    Distribution Channel Benefits
Within a traditional distribution channel, manufacturers produce and then sell products to distributors or retailers, which eventually sell goods to consumers. Maintaining close relationships in your distribution channel is important to manufacturers, and reducing product cycle times helps you meet the needs and requirements of distribution channel partners. This strengthens your position and makes you more attractive for other resellers looking for efficient producers.
Cycle time reduction results in simplified processes with fewer steps. In most cases, a process that has fewer steps will yield fewer mistakes. Simpler processes produce fewer errors.

Common methods to reduce cycle time
There are several efforts suitable for reducing cycle times. Streamlining multiple efforts, however, can yield a much more efficient process resulting in cost and time savings and customer satisfaction. When reducing process cycle time, consider a combination of the following ideas.
Perform activities in parallel. Most of the steps in a business process are often performed in sequence. A serial approach results in the cycle time for the entire process being the sum of the individual steps, not to mention transport and waiting time between steps. When using a parallel approach, the cycle time can be reduced by as much as 80% and produces a better result.
A classic example is product development, where the current trend is toward concurrent engineering. Instead of forming a concept, making drawings, creating a bill of materials, and mapping processes, all activities take place in parallel by integrated teams. In doing so, the development time is reduced dramatically, and the needs of all those involved are addressed during the development process.
Change the sequence of activities. Documents and products are often transported back and forth between machines, departments, buildings, and so forth. For instance, a document might be transferred between two offices a number of times for inspection and signing. If the sequence of some of these activities can be altered, it may be possible to perform much of the document's processing when it comes to a building the first time.
Reduce interruptions. Any issue that causes long delays and increases the cycle time for a critical business process is an interruption. The production of an important order can, for example, be stopped by an order from a far less valuable customer request--one that must be rushed because it has been delayed. Similarly, anyone working amidst a critical business process can be interrupted by a phone call that could have been handled by someone else. The main principle is that everything should be done to allow uninterrupted operation of the critical business processes and let others handle interruptions.
Improve timing. Many processes are performed with relatively large time intervals between each activity. For example, a purchasing order may only be issued every other day. Individuals using such reports should be aware of deadlines to avoid missing them, as improved timing in these processes can save many days of cycle time.
A case study in streamlining
Consider an electronics manufacturer receiving customer complaints about long order processing times--a cycle time of 29 days. An assessment of the order processing system revealed 12 instances where managers had to approve employees' work.
It was determined that the first 10 approval instances did not yield detailed reviews because managers felt the activity was an interruption when there were other activities that needed to be addressed. Those initiating the orders, therefore, were given authority to approve their own work. This saved an average of seven to eight days in the order processing activity.
Many subsystems had interfered with the process--each performing the same or similar tasks. The logical step was to perform redundancy elimination, and a detailed flowchart of the process was created. At closer inspection, 16 steps proved very similar to one another. By changing the sequence of activities and creating one companywide order document, 13 of these steps were removed.
Over a period of four months, the order system was totally redesigned to allow information to be entered once and become available to the entire organization. Due to this adjustment, activities could be handled in a parallel manner. After a value-added analysis, the manufacturer was able to reduce cycle time from 29 days to 9 days, save cost and employee time per standard order, and increase customer satisfaction.
The good news is that almost every company is a good candidate for cycle time reduction.

CPA SSEMPIJJA WILBERFORCE

Why you can’t assess auditing software just the same way as accounting software.

Why you can’t assess auditing software just the same way as accounting software.

As a representative of a popular audit software product, I often get asked by audit practitioners whether I could avail them with a demo copy of the software so that we can ‘play around with it’.

Since financial audit and accounting are related, how different can the respective software be? The self-check procedures accountants use to decide whether an accounting system is working are quite simple and straightforward in their design: You put in a piece of data at one end and check to see if the information that has been crunched through the system and that comes out at the other end meets your expectations. A simple example of such a procedure would be taking a pocket calculator and adding up the column of numbers your assistant gave you to see if it agrees with the total at the bottom of his schedule.

However procedures like these only tell you whether the accounting softwareis able to properly process information that has been fed into it according to the rules that you specify. It’s the sort of procedure where because you know in advance, what the results should be, you can test it quite easily using that input vs. output model.

The real job of an accountant however, is not merely entering a transaction in the records but rather of knowing how to classify transactions. For example, which engineering items are repairs and which ones should be treated as new fixed assets instead? Is the value of the motor car as shown in the accounts still valid or does it need to be marked down – or even up? The accountant is also responsible for summarising the transactions in the way that most suits the people who need the information and presenting it in a way that makes sense. Seen in this light, it is not possible to create “accounting” software as these accounting judgement roles cannot be played by a computer program. What we refer to as accounting software should really be referred to as bookkeeping software.

Auditing, on the other hand, is the checking process. Confirming that data going in at one end of the system comes out the way it should at the other end, is just one audit objective and frankly, it isn’t even the most important one. The most important objectives of audit are to determine whether the financial statements (a) contain all the information they should contain, (b) contain only the information they should contain and (c) are reported in a way that conforms to a pre-agreed standard.

It does involve the arithmetical accuracy checking that most accountants do in the first place. However it also involves checking that the basis of classifying and summarising information was properly done – a test of judgement(because so-called accounting programs will execute incorrect instructionsto summarise or classify information just as faithfully as they will correct ones.)It also involves checking that there is no information missing  - another judgement test.It also involves checking that the information is not overstated – also a matter of judgement. That’s not all however. International Standards on Auditing now actually pay attention to the process that was used to evaluate the accountant and it requires certain mandatory steps to be taken and documented, no matter how certain the auditor may be of the correct situation.

This leads to an interesting question then; is it possible to create software that can meet all of these requirements of the audit? Data interrogation and sample selection software could go through the accounting information and try to extract information that makes sense but could it tell if the classification method used by the accountant was wrong? How would it decide if the evidence provided was acceptable? This is a trickier proposition and indeed, nobody has yet been able to design software that actually “audits”, much in the same way that nobody has been able to design software that does “accounting.”

What does this mean for a practitioner thinking about buying audit software? Audit software doesn’t have transactions that you can insert at one end and click to see if they have been properly classified at the other end. Instead it provides what amounts to very a long and sophisticated checklist (or series of checklists) of the all the procedures an auditor needs to carry out to determine the three objectives and comply with the mandatory procedures mentioned above. These are extensive and run, at present to nearly 800 separate mandatory procedures in the International Standards on Auditing. And that’s not counting the steps in the audit programmes in each section of the audit file. There is only one way to tell if this collection of checklistsworks properly; carry out an audit with it and submit the results of the audit to an independent quality reviewer to determine if the work was done properly.

People who aren’t skilled enough to know how to use the checklist will not be able to gauge whether they failed or passed the quality review due to an inadequacy of their checklist or due to their failure to use it properly.

Also, although the ISAs prescribe the approach to the audit to which all auditors should conform and in some instances even stipulate the exact tests to be carried out, they are not precise enough about how to do it. For example, there are more than a dozen ways to develop a sampling frame that produces a truly random sample. Which one is most appropriate? What’s a reasonable maximum or minimum sample size? If your sample contains an error, by how much should you extend your tests if at all? What’s the best way to calculate materiality? How many levels of review should there be in a particular assignment? The ISAs just don’t say.

Audit software helps by providing handy computation tools for sample design and selection and guidance on developing materiality. They even provide specific program steps for various areas of the audit. They also nudge you, (by blocking access to particular file areas and questionnaires), into using the work flow sequence that is most efficient or effective. These features, in the aggregate, comprise the methodology of particular audit software.

Without training by a person with proper experience on the specific methodology of a particular piece of audit software, it could be difficult to understand how all the questionnaires, computing tools and checklists work together to achieve efficient compliance with the ISAs.

For these reasons, taking a demo copy of audit software to try it out is unlikely to be helpful unless you are also willing to undergo not just “demo” training in the methodology but also a “demo” quality review – all lengthy and costly steps.

I would suggest that a more reassuring route would be to work through a presentation with an experienced user and ask to be shown all the features that you consider to be key in your existing methodology to ensure that they are present. Another, perhaps more important source of reassurance would be to look at the number of other practitioners relying on the same software to carry out their work successfully. The more there are, the more likely that it is the right product for you.

 Joe Gichuki

Joe, a member of ICPAU, is the CEO of Kawai Consulting, a firm that specialises in providing technical and capacity building services to financial auditors. Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Today's Accountant Magazines