Can Accounting Systems be TOO Integrated?

Systems like SAP, Oracle Financials and PeopleSoft attempt to integrate all aspects of a business, regardless of the number of countries, industries, product lines they operate in.  They address all areas of the business, from accounting, to manufacturing, to planning, to human resources, to management.  There is no question that large corporations have benefited from this integration, but is it possible that we’ve gone too far?

The larger the computer system, the higher the cost of change.  For example, one of my clients was an international oil company which wanted to experiment with a new subsidiary.  The company found it cost effective to do a whole installation of Microsoft Dynamics (and throw it away when the experiment proved to be a success) than to integrate the new subsidiary into their main system right away.

But, more importantly, large systems become increasingly complex, reducing their ability to adapt to change.  I don’t have an inside track, but I have noticed that my telephone company’s billing system seems to be unable to keep up with changes in cellphone services and fees.  In any competitive industry, even large companies need to be nimble and respond to changes in the marketplace quickly.

Finally, there is the “best of breed” problem.  You may have the biggest, most integrated system, but there are other systems that handle specific functions better.  You then are faced with the choice of the one-vendor-solution versus assembling a system from the best of breeds by several vendors.  So, you get your basic General Ledger, Accounts Payable, Banking and Accounts Receivable from one vendor, your Point-of-Sale system from another and your document imaging from a third.

A good example of this type of thinking was a client who wanted to connect his ordering system to his web site.  Both systems claimed to be able to handle the sales tax, but in testing, the engine in the accounting system proved to be more robust than the web site.  The client decided to process the order in the web site, but have it pass the information to the accounting engine to calculate the taxes and send the result back to the web site.  The result was a better system with no tax discrepancies.

Not JUST an Accounting System

Alice* shared one of her constant frustrations in a meeting about their accounting system.  She is an accounting supervisor in a medium sized company with offices across the country.  Her problem is the staff in other departments saying that the computer system belongs to the Finance department, so they don’t have to take responsibility for the quality of the information.  It’s not their responsibility if the information in the accounting system is wrong or out of date.

Accounting systems used to be confined to recording entries, producing invoices and making payments.  Current accounting systems integrate into other business software, so that the Sales, Purchasing, Manufacturing, Distribution and Human Resources systems are now part of the “Accounting System.”  More and more, other systems, such as Document Imaging and Customer Relationship Management, are integrating with the accounting system.

In a world where computer reporting is expected to be detailed and instantaneous, there is no room for error.  In short, EVERYONE owns the data.

By the same token, information needs to be shared.  There should be no arguments about who “owns” the data.  If it is needed in decision making, it needs to be made available to the decision makers, regardless of their department.

The more that operational data gets married to the financial data, the more focused the reports and the better the decision making.  The more integrated the systems, the easier it is to marry the data.  But can systems be too integrated?  Stay tuned for the next blog!  


* Not her real name.

Whose System is it, Anyway?

There are many stages a computer system goes through during an implementation.  At first, it is just an idea perhaps starting with frustration with the current system or a sudden new requirement that the current computer (if there is one) can’t handle.  At this point, all you know is that you need a new system.

The Hunt

Then you start looking.  Maybe you ask colleagues.  Maybe you initiate a Request For Proposals (RFP), asking a number of vendors a series of questions about what their system can do, and inviting them to bid on your business.  Maybe the system has already been chosen for you by a parent company.

Then come the demonstrations and the system becomes more real.  You compare different products.  You talk to consultants and the customers they offer as reference sites.  You do your homework and you make your decision about which system to buy, but it’s not your system yet.  Even though you may have signed a contract, taken delivery of the software and paid for it, your staff has not taken ownership of the system.

The Implementation

Next comes the detailed planning, the configuration, the set-up, the training and the conversion of the data from the previous system.  What can the new system really do?  What fits and what doesn’t?  You add additional software.  Maybe the new system doesn’t have Electronic Data Exchange (EDI) for orders and payments to large retail companies, so you add an EDI package.  Maybe you need workflow to handle your online orders or document imaging to get rid of the tedious searches through filing cabinets, so you turn to iDatix.

At this point, you examine your internal processes.  You look for formerly manual steps that the system can now do.  With the workflow system now reminding people to submit their expense forms, move the person who used to phone all the salespeople to a higher value task, such as following up on customer payments.

By this time, your staff should start to feel like they own the system, that it is their responsibility to make it their own and work with its strengths and weaknesses.  Unfortunately, after many years of implementations, my experience has been that they often don’t.  All of a sudden, the old system looks better.  The new one seems clunky.  There’s always something that worked better before.  The staff doesn’t remember the issues they had when the old system was new.  They don’t remember the workarounds they had to come up with.  They don’t have enough time or patience for the new system.

Naming the Beast

Accounting systems are complex.  In a medium sized implementation, there may be over 500 data files.  In a large one, there are literally thousands.  When you layer on tax requirements, Generally Accepted Accounting Principles, industry standards, vendor/customer complexities, etc. etc. even the best planned systems require extensive work to fit.  One simple thing you can do to help your staff take ownership and really commit to the new system is to name it.  It sounds like a small step, but it underlines the fact that it has been customized for your company.  The system is no longer SAP, Oracle, Microsoft, Sage or even Quickbooks, it is yours.  So, if you were the Leamington Manufacturing Corporation for example, you might call your system Lexie (Leamington’s EXtended Information Environment) and have one of the more artistic members of staff find a suitable image.  Give the system a good start by throwing a party, and when people complain, make sure to take their complaints seriously, but also ask them to have patience with Lexie.  After all, she is the newest member of the team.

Re-posted with the kind permission of iDatix:  http://www.idatix.com/insider-perspective-whose-system-is-it-anyway/

The Cost of Data Entry

 Ah, I remember those days well.  As a young auditor, looking a little uncomfortable wearing a suit every day, I was asked to audit the Accounts Payable department of a national retail chain.  The office was in a low rise building in the suburbs and the Accounts Payable department took up a whole floor.  That’s right, row after row of middle-aged women with comptometers, which were large, manual calculators.

Their job was to check all of the calculations on the invoices received from vendors and then batch the invoices for data entry.  The women (and they were all women in those days) down in data entry were not supposed to even think while they entered the invoices.  They were supposed to be like human computers and just key in the data, only looking at it if it didn’t agree to the comptometer total that came with the batch.

Funny story:  one of the older women in Accounts Payable liked me because I was careful about putting all of the invoices I selected for audit testing back into the right files.  She invited me out to lunch one Friday with “some friends from other departments.”  At the restaurant, she introduced me to the new credit manager, a woman about my age.  Then she looked at her watch and said that she had forgotten to do something important, and that we should go on without her.  Lunch turned out to be just the two of us.  The credit manager was deeply embarrassed and told me how the ladies in Accounts Payable thought she was much too pretty to be single, so they kept setting her up with eligible young men.  I’d love to be able to say that we were married the following year, but such was not to be.  The lunch ended quickly and we went our separate ways.

Data entry has changed a lot since those days too.  We expect the people who enter information to understand and correct the transactions, as well as flagging any that need further follow up.  Data entry is a more responsible position than it used to be.  Personally, I think that’s a good thing.  It’s a more rewarding experience to be involved in the business than to just sit there doing mindlessly repetitive tasks.
Data entry is also disappearing.  When we receive cheques, for example, they are entered via a scanner, which reads the bank’s magnetic encoding, as well as attempting to read the sender’s address information.  The data entry clerk reviews and corrects the information before posting the cash receipts, a much faster process.  Other companies, more advanced than ours, get rid of paper altogether by using Electronic Data Interchange (EDI) where all of the payment information is received from the vendor and the payment is wired into the bank account, freeing up staff to do more value added work, such as following up on outstanding payments.  So, instead of having a room full of data entry clerks, you have none.