CCH Audit Automation SQL Release Notes

Size: px

Start display at page:

Download "CCH Audit Automation SQL Release Notes"

Myrtle Lewis
5 years ago
Views:

1 CCH Audit Automation SQL Release Notes

2 Disclaimer CCH Software has made every effort to ensure the accuracy and completeness of these release notes. However, CCH Software, its staff and agents will not be liable for any errors or omissions and use of the software is subject to the customer s licence with CCH Software. These release notes should not be relied upon as a detailed specification of the system or the software. CCH Software may make changes to these release notes from time to time. Copyright 2017 Wolters Kluwer (UK) Limited These release notes may not be copied, altered, edited, disposed of or distributed without the prior consent of CCH Software. The content is confidential Trademark Rights Microsoft, Windows, Windows NT, Windows for Workgroups, Windows 98, 2000, XP, MS-DOS, Windows Vista, Windows 7, Windows Server, Microsoft SQL Server, and Microsoft Office, are either registered trademarks or trademarks of Microsoft Corporation. Novell and NetWare are trademarks of Novell Inc. Citrix MetaFrame is a registered trademark or trademarks of Citrix Systems, Inc., All rights reserved. CCH Software 145 London Road, Kingston upon Thames, Surrey KT2 6SR UNITED KINGDOM II

3 Contents Disclaimer ii Contents iii Overview 1 Prerequisites 1 User management 2 Creating a new client 6 System Options 7 Converting client data 8 Client list and client control data 16 Document management 19 Current audit file 22 Standard audit programmes 24 Annual checklists 24 Installing the master packs 25 Mercia Company Master Packs 26 Converting a Master Pack 26 Merging Master Packs 31 Editing the Master Pack 32 Setting the Default Chart of Account. 33 Travelling Clients 34 Cancelling a travelled client state 42 Network at client 43 Known Issues 44 CCH AUDIT AUTOMATION SQL RELEASE RELEASE NOTES OCTOBER 2017

4 Overview The SQL version of AA uses the same user interface for the maintenance of master packs and completion of audits, however certain changes in the UI and underlying concepts have been made as a consequence of the way the data is now stored. The main changes are as follows: 1. Documents are no longer stored in client folders in the audit data area. They are held in the SQL database using the CCH Document Management store. This means that documents need to be checked out and held locally before they can be edited and they need to be checked in on completion of the changes. 2. A new concept of master pack inheritance has been introduced. This is a significant enhancement which enables you to make practice level changes to master packs and retain these changes when new versions are released. 3. As the data is no longer stored in client folders, the single SQL database holds multiple periods. This means that the prior periods data is accessible when you are working on a client. You can directly load a specified period, or switch to a different period when the client s data is loaded. This means that it will no longer be necessary to restore prior periods from the archive folder prior to travelling when taking data out of the office. 4. The AA database is designed to reside within the Central database. This means that, for those practices that wish to run a single database, client and employee data will be shared by AA and the other Central applications. 5. The AA software is now installed via the CSI (Central Suite Installer). 6. The office, partner and manager details of the client can now be filtered from the client list screen, this information can now be added in the client control data. Prerequisites To be able to use the client and master pack conversion utilities as detailed later in this document you need to have the following: - The machine that the conversion take place on must have the Borland Database Engine installed (BDE) - If the client data that is to be converted contains MS Excel files, MS excel must be installed on the machine that the conversion is carried out on. CCH AUDIT AUTOMATION SQL RELEASE NOTES

User management On installation, the system will be set up with a single user: Code: Password: MNGR Password When you convert a client, using the routine described below, the procedure will also

5 User management On installation, the system will be set up with a single user: Code: Password: MNGR Password When you convert a client, using the routine described below, the procedure will also convert your user file. This will update the MNGR user to the same password used in the dbase version and append any additional users not currently present in the user file in SQL. Existing Central Users For existing central users where the employee records already exist in the SQL user file it is necessary to update the central employee records with the audit user name. Failure to do this before client conversion may result in duplicate employee records if the audit user name does not match that of the user name in central. Following the installation of the SQL version of audit a new field will be available on the employee record screen: Audit U/Name. The update of this field with the audit user name should be carried before performing a client conversion. 2 CCH AUDIT AUTOMATION SQL RELEASE NOTES

When running the client conversion process the routine will show the following message if it matches an employee Central User Name to the user initials in the dbase version, and the Audit user name

In this scenario the audit user should be created in central and the audit user name field should be populated with the user initials that have been used in the dbase version of the software.

6 When running the client conversion process the routine will show the following message if it matches an employee Central User Name to the user initials in the dbase version, and the Audit user name field in central has not been populated. This is to cater for firms that have different employee s using central and audit but have matching employee codes in both systems. In this scenario the audit user should be created in central and the audit user name field should be populated with the user initials that have been used in the dbase version of the software. The conversion routine can then be restarted Security Groups The security groups for Audit SQL will also be available following the installation of audit. The security group can be selected and applied from the security groups tab in the employee record. Employees will not be able to log into the audit software until they have been allocated a Audit Automation Security group. CCH AUDIT AUTOMATION SQL RELEASE NOTES

7 The Security groups follows the same levels that are used in the dbase version of the software: Security Group Old Group New Group 0 Audit Automation System Manager 1 Audit Automation Partner 2 Audit Automation Manager 3 Audit Automation Senior 4 Audit Automation Junior 5 Audit Automation Read Only This is a new group and will allow users to be included in the staff details and budget sections but will not give them access to the software Audit Automation Staff Only 4 CCH AUDIT AUTOMATION SQL RELEASE NOTES

To change the password for the user, click on the Change password button and enter the details of the new password in the dialog that appears: 2.

8 User Management You can manage users using the AA Edit password and user details routines, however there are a couple of minor changes: 1. Changing a password When you display the details of an existing user, the password fields will be disabled. To change the password for the user, click on the Change password button and enter the details of the new password in the dialog that appears: 2. Deleting users SQL is a relational database and you are not able to remove records that are referenced by other records in the database. Hence, it will not be possible to delete a user who has entered completion details as their record will be referred to from elsewhere. If you try and delete such a user, the system will display an error message indicating that this is not possible. An option will be provided in the release version of the software to inactivate users who should no longer have access to the software. CCH AUDIT AUTOMATION SQL RELEASE NOTES

Each master pack is now identified by its code which does not include the version and the version is shown in a separate field.

9 Creating a new client The release version has been installed with the standard master packs that you subscribe to ready for you to create new clients in the software. As indicated, the system uses an inheritance model for the master packs and this means that the way that the master packs are referenced has changed. Each master pack is now identified by its code which does not include the version and the version is shown in a separate field. To create a new client, follow the same procedure that you would have followed in the dbase version. The dialog has been updated to reflect the separate fields: Enter the master pack code, e.g. IFULL, and press Tab. The system will automatically select the latest version of the pack, V7 in this case. Alternatively, select the pack from the pick list: If you do not select the current version of the pack then you will be warned that you have not selected the latest version. In all other respects creating a client is the same as in the dbase version. As the audit software is now sharing the central database, for clients that have other CCH products they use the Pick button to show a list the central clients that currently exist. 6 CCH AUDIT AUTOMATION SQL RELEASE NOTES

10 No need to initialise programmes and checklists When you first open a new client, the system will automatically initialise the checklist and programmes and checklists are also automatically initialised on a balance forward. Hence the option to initialise these items have been removed from the planning menu. System Options An Import system path location has been added to the Data Paths tab. This allows the default location to be set so that users can have access rights to be able to work with the system definition and mapping files. CCH AUDIT AUTOMATION SQL RELEASE NOTES

11 Converting client data A client data conversion routine is provided to enable you to convert data from your current dbase AA data. This routine will make a copy of the client data in the SQL database and will leave the dbase version unchanged, however we recommend that you make a copy of your live Audit Automation master and client data and convert from this to ensure no conflicts arise during the conversion process. Note: Conversion of system settings The conversion routine will also seek to convert your system settings as this data is required to convert your client data. To enable it to do this it requires access to the following files which are located in your existing Audit Automation program folder: ProAudit.ass PROaudit.ini Audit.ini ADDRESS.ini To enable the conversion utility to operate you will need to copy the above files into the Data path which is selected in the second step described below. To use the conversion routine, open Windows explorer, select the AA deploy folder and double click on ClientPackDataConverter: The converter is a 2 step wizard. Note: Close Audit Application before conversion The conversion routine requires use of the Borland database engine and therefore you must close the software that is using the BDE including the audit software and portfolio manager before conversion. 8 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Select items to convert Enter the following information: Program path (dbase) System data path Master data path Enter the path where the dbase Audit Automation program data is stored using the Browse

12 Select items to convert Enter the following information: Program path (dbase) System data path Master data path Enter the path where the dbase Audit Automation program data is stored using the Browse button to the right of the field. Enter the path where the dbase Audit Automation client data is stored using the Browse button to the right of the field. The system will check that the path contains audit data and extract and display the client list. Enter the path where the dbase Audit Automation master pack data is stored using the Browse button. As indicated, once a valid data path has been entered the system will display the client list: CCH AUDIT AUTOMATION SQL RELEASE NOTES

Note: Any clients which have already been converted will be shown in red in this list. You can convert clients individually or select multiple clients to convert in the run.

The code column defaults to the code used to identify the client in the dbase data, which is also displayed as the Old code to the right of the name.

13 Note: Any clients which have already been converted will be shown in red in this list. You can convert clients individually or select multiple clients to convert in the run. To select a client tick the checkbox to the left of the client. The code column defaults to the code used to identify the client in the dbase data, which is also displayed as the Old code to the right of the name. If you wish to allocate a difference code to the client in the SQL data, select the client and click Edit, or double click on the client. Within this dialog you can edit the code and name that will be used for the client in the SQL database. Note: Central Users For existing central users if the client already exists in central, the client code used on conversion should match that of the client code in central. If this is the case the audit data will be added to the existing central client record, if the client codes do no match a new client will be created 10 CCH AUDIT AUTOMATION SQL RELEASE NOTES

14 Converting a single year for a client If you just wish to convert a single year for a client, or clients, tick the checkbox by the clients and click Next. Conversion progress The conversion progress tab will be selected and the progress reported as the conversion proceeds. On completion of the conversion the progress bars will be replaced with a report detailing the results of the conversion. CCH AUDIT AUTOMATION SQL RELEASE NOTES

15 Conversion status It is possible that there are some historical issues with the dbase data which have accumulated over the years but have not caused a problem or been visible in the current version of the software. If any such issues have been found during conversion, they will be reported in the Conversion status column. In the above case some issues were found with the User created documents, Standard programme results and working paper review. In most cases these will be redundant records in the files which have simply not been converted and can be ignored. If you see any such issues reported then please review these areas in the converted data to make sure that the client data appears as expected. A full log of the issues will have been created and stored, so if you think that the data has not been converted correctly please contact us and we will review the log to see what errors occurred. If the system finds any files in the client data folder that are not recognised, and hence not converted, it will list these in the Conversion status report. In the above example 2 such files were found, Answers and RegIndex, and these can be ignored. Converting multiple periods for a client The SQL database can hold multiple periods records for each client and, if you have multiple periods present in your dbase data, you can link them so that they are recognised as data that should be stored under one client record. 12 CCH AUDIT AUTOMATION SQL RELEASE NOTES

To do this, highlight the multiple entries in the client list that correspond to the current and prior periods data for the client: Note: LR1 & LR2 are shown in red as they have already been

16 To do this, highlight the multiple entries in the client list that correspond to the current and prior periods data for the client: Note: LR1 & LR2 are shown in red as they have already been converted. Point to one of the entries and hold down the Ctrl key to highlight multiple entries, click the right mouse button, a popup menu will appear: Select Link clients and the client information dialog will appear populated with the code and name from the first record select: Edit the code and name as required to that which you wish to use in the SQL database and click OK. The system will represent the list with the periods linked as a single entry: CCH AUDIT AUTOMATION SQL RELEASE NOTES

17 This example shows linking 2 periods, however you may link any number of periods to convert. To convert the data tick the checkbox to the left of the entry and click Next. Conversion progress The conversion progress tab will be selected and the progress reported as the conversion proceeds. 14 CCH AUDIT AUTOMATION SQL RELEASE NOTES

18 On completion of the conversion the progress bars will be replaced with a report detailing the results of the conversion. Please see the comments above relating to converting a single client detailing how to interpret this report. As indicated, when you convert multiple years for a client using this process, they will appear as a single client entry in the list in Audit Automation. When you load the client the latest year will be displayed and the date shown in a new Processing period end drop down list in the main tool bar. To switch to a previous period, select the period end from the drop down list. CCH AUDIT AUTOMATION SQL RELEASE NOTES

19 Client list and client control data The client record has been extended to include details of the Office, Partner and Manager associated with the client. You can alter the width of each column shown in the list by dragging the area to the left of the column name in the heading. You can also filter the contents of the list by selecting an office, partner or manager from the drop down lists. The Search by name and Jump to code fields operate as they do in the dbase version. Loading the latest period for a client You can load the latest period for the client by double clicking on the row containing the client in the list, or by selecting the client and clicking on Load. Loading a prior period You can load a prior period by selecting the client and clicking on Load selected period. A dialog will appear listing the periods recorded for the client: 16 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Double click on a period to load it, or select the period and click on OK. If you have selected the wrong client, you can also switch to another client using the drop down or pick list.

20 Double click on a period to load it, or select the period and click on OK. If you have selected the wrong client, you can also switch to another client using the drop down or pick list. Switching to a different year for an open client When a client is open the period end date that you are working on is displayed in the Processing period end drop down list in the main tool bar. To switch to another period, select the period end from the drop down list. Note: It is still possible to have multiple instances of Audit Automation running if you wish to have both the current and previous period visible at the same time, or would like to have more than one client s data open at the same time. CCH AUDIT AUTOMATION SQL RELEASE NOTES

21 Client control dialog 3 new fields have been added to the client control dialog to allow you to set the engagement Office, Partner and Manager. You can populate these fields by selecting entries form the drop down lists. A further change to this dialog relates to the Master Pack code and version which is explained earlier in this document. 18 CCH AUDIT AUTOMATION SQL RELEASE NOTES

22 Document management The system no longer stores the documents in folders but holds them in a file store controlled through the SQL database. This means that documents must now be checked out to be edited and checked in when editing is complete. Permanent file Three new buttons have been added to the Permanent file window relating to document management: Check out Undo check out Check in Checks the selected document out and stores and editable copy in a local document store on your hard drive. Remove the record of you having checked out the document but does not check in any local changes. Hence if you have made changes and then undo your checkout any changes made since you checked the document out will be lost. The system does make a backup of your document in the local document store so if you do this by accident it will be possible to retrieve your work provided the backup has not been deleted during housekeeping. This option copies your local copy of the document back to the SQL database thereby saving any local edits you have carried out. These same 3 options have been added to the popup menu that appears when you click the right mouse button. Status icons When a document is checked out, the system displays the following icon to the left of the name of the document: CCH AUDIT AUTOMATION SQL RELEASE NOTES

Indicates document checked out When a checked out document is highlighted, the system also indicates the local path where the document is stored together with the name of the document in the button

23 Indicates document checked out When a checked out document is highlighted, the system also indicates the local path where the document is stored together with the name of the document in the button bar: There are a number of standard document which are defined in the system such as the points forward and general planning memorandums. If these have not yet been created, this is indicated by the following icon: Indicates document not yet created Once one of these documents has been created, by opening it, the icon will change to the icon which indicated that a new document created but not yet checked in: Indicates document created but not yet checked in. This icon will also appear by documents that have been created using Add until such time as they are checked in. User created documents The same 3 buttons and popup menu options have been added to the Window showing the list of user created documents. As can be seen the same icons are used to identify the filing status of documents. In addition, you can switch the display to list view which contains more information: 20 CCH AUDIT AUTOMATION SQL RELEASE NOTES

In this view, the status icons are presented in the second column and the name of the user who has the document checked out is displayed in the last column.

24 In this view, the status icons are presented in the second column and the name of the user who has the document checked out is displayed in the last column. You can only checkout 1 document at a time, however in this view you can check in multiple documents by ticking their checkboxes in the first column and selecting the check in, or undo check out, options. CCH AUDIT AUTOMATION SQL RELEASE NOTES

In the case of the current audit file, the status icon for new and checkout documents replaces the file type icon: View only mode and auto

25 Current audit file In the current audit file, you can check out a document by selecting it and then selecting Check out from the popup menu: The Check in and Undo check out options are also on this menu. In the case of the current audit file, the status icon for new and checkout documents replaces the file type icon: View only mode and auto checkout of documents If you open a document that has not been checked out, for example by double clicking on it, you will be asked if you wish to check it out for editing: 22 CCH AUDIT AUTOMATION SQL RELEASE NOTES

If you answer Yes, the document will be checked out and opened for edit. If you answer No it will not be checked out and will be opened in read only mode.

26 If you answer Yes, the document will be checked out and opened for edit. If you answer No it will not be checked out and will be opened in read only mode. In read only mode the document will either not be editable, or in the case of Word will accept your edits but it will not allow you to save the changes. Checking our reviewed documents The same rules are applied to checking out reviewed documents as were applied to the audit release of documents in the dbase version, i.e. 1. If a document has been reviewed by a higher level than the user, they will not be able to check out the document. They will need to release the document for editing before checking it out. 2. If a document has been reviewed by someone of the same level or lower, you will be able to check out the document for edit so you can add your comments and changes. The document will remain marked as reviewed, however an entry will be added to the audit trail showing that you checked out the document following review. CCH AUDIT AUTOMATION SQL RELEASE NOTES

27 Closing a client with documents checked out When you close a client the system checks to see if you have any documents checked out and if you do it will show you a list and give you the opportunity to check them in. This will happen if you close the client and return to the client list, or if you close the program while a client is open. All checked out documents will be ticked and clicking on Yes will result in them all being checked in. No will leave the documents checked out. You can check in some of the documents while leaving others checked out by removing the tick by the ones you do not wish to check in. Warning: If you leave any documents checked out then any changes that you have made to these documents will only be recorded in your local document store and will not be included in any backups created. Standard audit programmes The concept of standard audit programmes has been removed from the system and all standard programmes converted to Mandatory Procedures. This means that all audit tests, including those that formed the standard programmes, are now included in the pool of tests. It also results in there being a single combined audit programme shown in completion mode, rather than the standard programme and the combined programme of tests form the pool. The way that you customise the mandatory procedures has not changed, with the ability to add or remove test at a client level. We have also enhanced the process to allow you to force activation and inactivate mandatory test, in the same way that they were activated and inactivated in the standard programmes. Annual checklists The concept of annual checklists has also been removed from the program and all annual checklists have been converted to perennial checklists with only the current period s answer shown. 24 CCH AUDIT AUTOMATION SQL RELEASE NOTES

You will see a list of master packs that will correspond to the methodology you selected during the software installation.

28 Installing the master packs To install the master packs you need to run the routine that will add them to your database. Select Master Packs Install master packs. You will see a list of master packs that will correspond to the methodology you selected during the software installation. Tick all the packs you wish to install and then click Install. You will see progress messages as the packs are inserted into your database. When the pack have been installed click Close to close the Install packages dialog. CCH AUDIT AUTOMATION SQL RELEASE NOTES

29 Mercia Company Master Packs When converting the Mercia company master pack and group pack the please note that the master pack code has been changed for the latest Mercia master pack release this is to accommodate the new coding structure implemented in the SQL Version. Please see the table below to see the changes: Existing Code New Code IMER10A IMER 11 IMERG10A IMERG 11 MEREX10A MEREX 11 Converting a Master Pack A master pack data conversion routine is provided to enable you to convert data from your current dbase AA data. This routine is for practises that have created their own bespoke master packs. Uses that have not tailored the master packs should use the install routine as detailed earlier in this document. If only minor changes have been made to a standard master pack it is possible during the conversion to base the pack to be converted on an existing master pack. This process will incorporate the practise level changes that have been made and you will be able create a practise version of the master pack by changing the version number. You will need to have the standard master pack that you are basing the practice level pack in the dbase master pack directory. To use the conversion routine, open Windows explorer, select the AA deploy folder and double click on ClientPackDataConverter: The converter is a 2 step wizard. 26 CCH AUDIT AUTOMATION SQL RELEASE NOTES

30 Enter the following information: Program path (dbase) System data path Master data path Enter the path where the dbase Audit Automation program data is stored using the Browse button to the right of the field. Enter the path where the dbase Audit Automation client data is stored using the Browse button to the right of the field. The system will check that the path contains audit data and extract and display the client list. Enter the path where the dbase Audit Automation master pack data is stored using the Browse button. Once the valid data paths have been entered select the Add button and a list of master packs to convert been be shown, items shown in red have already been converted: CCH AUDIT AUTOMATION SQL RELEASE NOTES

31 28 CCH AUDIT AUTOMATION SQL RELEASE NOTES

32 Select the pack you with to convert and click OK The master pack will be added to the list of master packs to be converted. CCH AUDIT AUTOMATION SQL RELEASE NOTES

33 Client Next and the conversion progress tab will be selected and the progress reported as the conversion proceeds. A conversion report will be generated giving details of any areas that failed to convert correctly. 30 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Merging Master Packs In the SQL version of AA we have implement the facility to merge master packs. This option is available from the Master pack menu when logged in as the system administrator.

34 Merging Master Packs In the SQL version of AA we have implement the facility to merge master packs. This option is available from the Master pack menu when logged in as the system administrator. This routine is for clients who have made practice level changes to the standard master packs. When a new master pack update is release you will be able to compare the changes you have made against the updates in the new master pack. Select the master pack you wish to merge along with the current version. The software will identify the Source and target version and select Run Wizard. CCH AUDIT AUTOMATION SQL RELEASE NOTES

35 The system will show the master pack areas and will identify any differences between the practice and new master pack. When the system find a conflict you will have the option to either keep the local change or keep the update. Editing the Master Pack It is no longer possible to edit a default master pack. The following message is displayed if a default master pack is selected for editing: When editing the master pack there is a new Master Pack Chart option. This can only be used when no windows are open in the work area: This option will change the master chart that is used in the master pack and will change the chart of account, lead schedules, variables, equations and sub areas that become editable. 32 CCH AUDIT AUTOMATION SQL RELEASE NOTES

to set the default choice when creating a new client.

36 Setting the Default Chart of Account. As the SQL version of AA has the option to use different chart of accounts when creating a client it is possible to set the default choice when creating a new client. To do this select the Set default charts option from the master pack menu. Select the master pack to edit and click OK. When a new client is created the correct chart of account will be selected by default. CCH AUDIT AUTOMATION SQL RELEASE NOTES

Travelling Clients Travelling to offline database from Audit The computer that you are travelling the client pack onto needs to have a work station install of the CCH Audit automation software.

37 Travelling Clients Travelling to offline database from Audit The computer that you are travelling the client pack onto needs to have a work station install of the CCH Audit automation software. This should be installed using the Central Suite Installer and selecting the workstation install. The offline database and connection string for the local computer will be set up on the workstation the first time that traveling is performed. Whilst connected to the office network open the audit software and log into network at office. From the client maintenance screen select Transfer pack to or from office. Use the Pick button to select the client to be taken offline and the click OK. The Client will be exported from the Office database and then imported into the Offline database 34 CCH AUDIT AUTOMATION SQL RELEASE NOTES

38 The client name will be prefixed with the initials of the user that performed the travel. NOTE: If the client being travelled is using a master pack that is being used on the local machine for the first time then the travelling process will also take a copy of this master pack. This will result in all versions of the master pack being copied to the local database and therefore the process will take longer when new master packs are travelled to the local machine Travelling to office database from Audit Log in to the software using the Local Computer option, the client list will show the clients that have been travelled out from the office. Select Transfer pack to or from office and use the Pick button to select the client to be travelled back to the office database. The client will be removed from the offline database and the status of the client on the office database will be updated to current data and the initials of the user that travelled the client from the office will be removed from the client name. CCH AUDIT AUTOMATION SQL RELEASE NOTES

39 Travelling back to office database from Audit Log into the offline database and from the client maintenance screen select Transfer pack to or from office. Select the client to be travelled back to the office: 36 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Travelling to offline database from Central Configuration Settings The current method for travelling accounts production and corporation tax data was to travel each data set into a separate database,

40 Travelling to offline database from Central Configuration Settings The current method for travelling accounts production and corporation tax data was to travel each data set into a separate database, however with the addition of audit this is no longer possible as audit make use of the new travel function whereby the data is travelled into a single database. Warning: Before updating this setting any Accounts production or corporation tax data that is currently travelled out should be travelled back to the server. In the deploy folder open the ClientFrameWork.exe.config file in notepad and change the offline mode from zero to 1. This will travel all data into a single offline database. The CCH_Travelling_Mode configuration key will also need to be updated to 1. Open Central and browse to Maintenance > User Defined > Configuration and update the key value from 0 to 1. Travelling If a client is travelled from Audit and the client also has data for Accounts Production and / or Corporation Tax the following dialogue will appear: CCH AUDIT AUTOMATION SQL RELEASE NOTES

If only the audit data it to be travelled then select Yes, alternatively if the data for the other products is also to be travelled, select no and travel the client from central.

41 If only the audit data it to be travelled then select Yes, alternatively if the data for the other products is also to be travelled, select no and travel the client from central. Warning: If you leave any documents checked out then any changes that you have made to these documents will only be recorded in your local document store and will not be included in any backups created. From the client search window mark the client to be travelled using the check box and from the Actions drop down select Travel client: The following dialogue will be displayed and the client data that is available to be taken off line will be listed. Select the data to be travelled and select OK: 38 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Following the successful travel of a client when logging into central a

42 Following the successful travel of a client when logging into central a new line will appear on the central log in screen called CCH Offline (Offline database).this is the offline database that has been created and contains the travelled data. This option should be selected when using the accounts production or corporation tax data that has been travelled along with the audit data. CCH AUDIT AUTOMATION SQL RELEASE NOTES

43 Travelling back to office database from Central To travel the client back to the office log into the office database select the client from the client search window and from the actions dropdown select synchronise: The System will display the user who travelled the client and the date the client was travelled out of the office. Select yes and the data will be travelled back to the office database. CCH AUDIT AUTOMATION SQL RELEASE NOTES

Cancelling a travelled client state The status of a travelled client can be reversed if it is not possible to reverse the travelled client by transferring the pack back to the office.

44 Cancelling a travelled client state The status of a travelled client can be reversed if it is not possible to reverse the travelled client by transferring the pack back to the office. This routine should only be used if the computer with the travelled data is not available to transfer the pack back to the office. Select Undo transfer pack from the system maintenance window and use the Pick button to select the client reverse the travelled status on. The travelled status of the client will be reset and the conformation message below will appear. NOTE: Undo transfer pack will revert the client back to the position it was in when it was travelled out of the system. Therefore it will result in the loss of any work performed on the travelled client pack. Also the status of the pack on of the travelled client will not be updated and will still show are current data. This process can only be performed by a System manager. 42 CCH AUDIT AUTOMATION SQL RELEASE NOTES

The following Screen will appear and the user will need to select the name of the machine that

45 Network at client To enable multiple users to connect to the same offline database whilst on site the network at client log in can be used. The following Screen will appear and the user will need to select the name of the machine that they are trying to connect to. The user will only be shown available servers on their current network. CCH AUDIT AUTOMATION SQL RELEASE NOTES

Known Issues 1. Area Travel is currently disabled and will be enabled for a future release. 2. Screen refresh Some screens require a refresh before the change

46 Known Issues 1. Area Travel is currently disabled and will be enabled for a future release. 2. Screen refresh Some screens require a refresh before the change is correctly updated on the screen. E.g. Background information areas are not updated from red to blue when they become active, and forcing an audit area to become active from Risk assessment and audit program review does not change from grey to blue. When the screen is loaded following the change they items will be displayed correctly. 3. Standard documents General planning memo, Point forward memo, Opinion Summary, Management schedule. These documents are not created automatically as they were in the dbase version. Before they can be used, e.g. for recording users comments from checklists and audit tests they must first be created in the client. This can be achieve by selecting the document to use. 4. TB Import It has been reported by some users that it can take several minutes to import the TB data, in this scenario the import routine appears to hang and the screen shows a not responding message, however the routine is working and the system will become active upon completion. 5. Window focus In some scenario s the focus screen is active behind the main application. E.G. for TB import the import conformation screen can appear behind the main application window, minimising the application will show the hidden screen. 6. Screen not responding - It has been reported that some routines cause the application to show a not responding message, however the application has not crashed and simply waiting for the routine to finish will solve the issue. 7. If the option to change the working paper folder and reference is performed on a document in general documents the remaining documents are also move into new folder called Unknown area. 8. Some users have reported the following error message appearing when opening word documents. 44 CCH AUDIT AUTOMATION SQL RELEASE NOTES

Center tab from the options menu and open the Trust Center

47 The issue is caused by the trust settings in MS word and can be fixed as follows: Open Word and browse to the Trust Center tab from the options menu and open the Trust Center Settings. CCH AUDIT AUTOMATION SQL RELEASE NOTES

check the option for Subfolders of this location are also

48 Open the Trusted locations tab and click Add new location. Add the location of where the documents are downloaded to and check the option for Subfolders of this location are also trusted and select Ok 46 CCH AUDIT AUTOMATION SQL RELEASE NOTES

CCH Audit Automation Master Pack. PCAS Audit Pack version 12. Installation Guide

CCH Audit Automation Master Pack PCAS Audit Pack version 12 Installation Guide Legal Notice Disclaimer Wolters Kluwer (UK) Limited has made every effort to ensure the accuracy and completeness of these