Establishing Standards for the Paperless Office
A paperless accounting practice is in many regards very similar to one based on paper, although it will be much more efficient if good practices and standards are implemented during the transition to paperless. Many firms start the move to paperless by scanning documents and storing them on a hard drive in some sort of homegrown folder structure. This gets the process started, but standards are hard to enforce and implement. Problems with this approach include:
- No enforceable naming structure for client folders and documents
- Minimal and difficult to use security features
- Weak and frequently unusable workflow processes
- Lack of granular security control
- No efficient document capture methods
- No way to efficiently and securely share documents with clients
- Ability to remotely access documents
Most of these problems occur because there is no way to force a user to name a document or apply security in a standard way. If someone gets in a hurry or simply forgets, it is quite simple to name a file incorrectly, file it in the wrong folder, and/or apply security incorrectly. In addition, there is no way to workflow a document through a business process effectively. Typically, Adobe or some other package is used to scan documents one at a time, with no sort of batch input.
In order to overcome the shortfalls of using a Windows Explorer structure, it is best to start with an electronic document management system (EDMS) which has the feature set to overcome the issues raised above. In general, most mid- to high-end document management systems should allow you the ability to:
- Create document templates with default naming and security
- Effectively control document security and provide an audit log
- Effectively provide workflow (both rules-based and ad hoc)
- Provide granular security classes for both client folders and documents
- Provide multiple capture points for documents (either paper or electronic)
- Provide easy secure access for authorized personnel (both local and remote)
Document Templates
Document templates provide a standardized method of entering document descriptions and applying security/retention and other settings. Default values should automatically be added to the description and minimal data entry by the document creator should be required. Required data fields are a must so key information is not ignored or forgotten. The goal of a document template is to provide a fast, easy and intuitive method to file a document with the minimum number of steps.
They also insure documents are named correctly and consistently no matter who is filing the document, making it much easier to find the document later with minimum effort. Remember, a large part of filing documents correctly to begin with is to have the ability to retrieve them later as quickly as possible. Security settings allow documents to only be accessed by authorized personnel and retention policies protect a document from being edited or deleted in accordance to regulations or company policies.
Workflow
Virtually every business has documents that flow through some kind of work process. Expense reports, purchase orders, and travel requests are some common examples. As the document passes from one person or department to the next, someone acts on the information and files it or passes the document on for review or further action. The process of accurately tracking the document’s progress from its originator through to its final destination is known as document workflow management. Ideally, this process is started when the document is filed in the document management system. Once again we move to the document template. A good EDMS should provide a method to automatically workflow the document based on the document template selected. Document templates are capable of doing a number of things automatically without user intervention.
Tip: A good EDMS should apply naming conventions, security classes and any necessary workflow at the time the document is added to the system. This prevents a user from neglecting any of these items out of haste or ignorance (particularly if these items can be applied automatically without user input).
- « Previous Page
- 1
- 2
- Next Page »

