cch prosystem fx import guide

CCH ProSystem fx ImportGuideCaseWare Working Papersv1.0

CaseWare International Inc.1 Toronto St. Suite 1400, Toronto, ON M5C 2V6 CanadaTel:416-867-9504 | Fax:416-867-1906 | www.caseware.com

Copyright. 2020 CaseWare International Inc. ("CWI"). All Rights Reserved. Use, duplication, or disclosure by the United StatesGovernment is subject to the restrictions set forth in DFARS 252.227-7013 © (1) (ii) and FAR 52.227-19. Notice to U.S. GovernmentEnd Users. This publication and the related computer software was developed exclusively at private expense and for the purposes ofU.S. acquisition regulations the related computer software is "commercial computer software" subject to limited utilization ("RestrictedRights").

This publication may only be copied and otherwise used as permitted in the applicable license agreement and, subject to the expressterms of such license, use of this publication is subject to the following terms and conditions:

All copyright and other proprietary notices must be retained on every copy made.

CWI has not conferred by implication, estoppel or otherwise any license or right under any patent, trademark or copyright of CWI or ofany third party.

This publication is provided "as is" without warranty or condition of any kind, either expressed or implied, including, but not limited to,the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

This and related publications may include technical inaccuracies or typographical errors. Changes are periodically made to CWIpublications and may be incorporated in new editions.

CWI may improve or change its products described in any publication at any time without notice. CWI assumes no responsibility forand disclaims all liability for any errors or omissions in this publication or in other documents, which are referred to within or linked tothis publication. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you.

Should you or any viewer of this publication respond with information, feedback, data, questions, comments, suggestions or the likeregarding the content of any CWI publication, any such response shall be deemed not to be confidential and CWI shall be free toreproduce, use, disclose and distribute the response to others without limitation. You agree that CWI shall be free to use any ideas,concepts or techniques contained in your response for any purpose whatsoever including, but not limited to, developing,manufacturing and marketing products incorporating such ideas, concepts or techniques.

This publication is distributed internationally and may contain references to CWI products, programs and services that have not beenannounced in your country. These references do not imply that CWI intends to announce such products, programs or services in yourcountry.

Product names, logos, designs, titles, words or phrases within this publication may be trademarks, service marks, or trade names ofCWI or other entities and may be registered in certain jurisdictions.

Chromium Embedded Framework - Copyright (c) 2008-2013 Marshall A. Greenblatt. Portions Copyright (c) 2006-2013 Google Inc. Allrights reserved.

Copyright

Overview 1

Install and configure SQL Server 1

Synchronize binders 2

Create initialization files (advanced imports) 2

Basic import 4

Advanced import 5

Convert third-party links 7

Table of Contents

OverviewYou can import client information, Trial Balance data, and associated documents from ProSystem fxEngagement to your Working Papers file. For a list of supported ProSystem fx Engagement versions,see the Software import index.

Before you can proceed, you must complete the following prerequisites:

l Install and configure a SQL Server instance on your workstation to facilitate the conversion.l Ensure you have a local installation of ProSystem fx Engagement on your workstation.l Synchronize your ProSystem fx Engagement binders.l For advanced imports, create a bulk autofill initialization file to help generate the Excelconfiguration file, and a mapping/grouping initialization file to automatically fill out map andgroup numbers.

After completing these prerequisites, you can proceed with a basic (single) or advanced (multiple)import. If applicable, when the import is complete, we suggest that you convert ProSystem fxEngagement links in Word or Excel documents to CaseWare Connector links.

Install and configure SQL ServerIf you want to import data from certain accounting software, but you do not have the software installedor you can't access its database, you can perform the import by installing a local SQL Server instanceon your workstation.

The SQL Server version must meet or exceed the version that was used to create the import files.

l To download the latest version of SQL Server, see Microsoft Download Center.l For installation instructions, see Install SQL Server from the Installation Wizard.

After installing SQL Server, you'll need to install the Backward Compatibility Components in thesame bitness as your version of SQL Server (64-bit for x64 servers).

To install SQL Server Backward Compatibility Components:

CCH ProSystem fx Import Guide

v1.0 | Copyright 2020 © CaseWare International Inc.1

https://www.microsoft.com/downloads/

https://docs.microsoft.com/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup

1. Download the Microsoft SQL Server 2008 Server Pack 2 Feature Pack.2. Expand the Install Instructions menu.3. Navigate to Microsoft SQL Server 2005 Backward Compatibility Components.4. Click the linked package in the same bitness as your SQL Server.5. Download the file, then run it on your workstation.

The necessary components are installed.

Note: Since ProSystem fx Engagement databases use the SQL data engine, it requires its owninstance of the SQL server. To prevent modifications to the SQL Server instance and the functionalityof the program itself, we recommend installing an independent SQL Server instance on your machineprior to importing into Working Papers.

Synchronize bindersPrior to the import, you must move the ProSystem fx Engagement binder to the Local File Room (LFR)and perform a synchronization to ensure that all files are up-to-date. Out-of-date files will cause theimport to fail.

Note: Files from the Central File Room (CFR) are not supported.

To synchronize binders:

1. In ProSystem fx Engagement, select the binder, then click Tools | Synchronize Binder....2. Complete the Synchronize Binder Wizard as required.

The binders are synchronized and ready for import.

Create initialization files (advanced imports)Before you can perform an advanced import from ProSystem fx Engagement to Working Papers, youmust create two initialization files:

l Bulk Autofill file (CCHBulkAutofill.ini)l Mapping/Grouping file (cchmapping-grouping.ini)



https://documentation.caseware.com/downloads/SQLServer2005_BC.msi

These files contain parameters for the templates, destination Working Papers file, and anymapping/grouping relationships.

To create a Bulk Autofill file:

1. In Windows, open a new Notepad text file.

2. Enter the following information:

[Template]default=<file path>Financial Institution=<file path>[Grouping]Financial Statements=1Consolidation=1

Where <file path> represents the path to the destination Working Papers file. For example,C:\Program Files (x86)\CaseWare\Data\Samp01\Samp01. Note that the file extension (.ac)does not need to be included in the file path, only the file name.

3. Save the file with the file name CCHBulkAutofill.ini.

The Bulk Autofill initialization file is ready for use during the ProSystem fx Engagement import.

To create a Mapping/Grouping file:



1. In Windows, open a new Notepad text file.

2. Enter your intended mapping structure. For example, if your ProSystem Fx Engagement file hasthe group number 1100.1100.10, and you want it to correspond to the map number 11.210 inyour template, the syntax will be:

[MappingCWGroup1]1100.1100.10=11.210

If your ProSystem Fx Engagement file has the group number 1100.1100.10, and you want it toimport it to CaseWare Group 1 within group B, then the syntax will be:

[GroupingCWGroup1]1100.1100.10=B

You can also specify multiple sections by incrementing the group number up to[MappingCWGroup10]. For example:

[MappingCWGroup1]1100.1100.10=11.210[MappingCWGroup2]1100.1100.20=11.220

3. Save the file as cchmapping-grouping.ini.

The Mapping/Grouping initialization file is ready for use during the ProSystem fx Engagement import.

Basic importPerform a Basic import if you are importing a single file.

To import data from ProSystem fx Engagement (Basic):

1. Ensure you have completed all the necessary import prerequisites before you proceed.2. Open Working Papers with administrator privileges by right-clicking the application icon and

clicking Run as administrator.



3. On the ribbon, click Engagement | Import | ProSystem fx Engagement Import Wizard. TheProSystem fx Engagement Import Wizard displays.

4. On the Welcome screen, click Basic Conversion.5. On the Import Settings screen:

l In the Version drop-down menu, select the version of your ProSystem fx Engagementinstallation. In the Program Folder field, browse for the location where ProSystem fxEngagement is installed.

l In the Import Workspace group, select the option that best describes where you want toimport data. Select Use previously copied ProSystem fx Engagement files in thefollowing folder when performing subsequent imports.

l In the SQL Server group, enter your SQL Server instance name and login information.Select Automatically Stop and Start ProSystem SQL Server Instance if you have notmanually stopped the instance prior to starting the import.

Click Next.

6. On the Import Options screen, select the client data that you want to import. Click Next.7. On the Client Selection screen, select the client files that you want to import. Use CTRL + click to

select multiple client files. Click Next.8. A summary of the import displays. Click Convert to proceed.

The data is imported to your Working Papers file.

Advanced importPerform an Advanced import if you are importing files that are based on more than one template, orcontain multiple top level consolidations.

To import data from ProSystem fx Engagement:

1. Ensure you have completed all the necessary import prerequisites before you proceed.2. Open Working Papers with administrator privileges by right-clicking the application icon and

clicking Run as administrator.



3. On the ribbon, click Engagement | Import | ProSystem fx Engagement Import Wizard. TheProSystem fx Engagement Import Wizard displays.

4. On the Welcome screen, click Advanced Conversion.5. On the Import Settings screen:

l In the Version drop-down menu, select the version of your ProSystem fx Engagementinstallation. In the Program Folder field, browse for the location where ProSystem fxEngagement is installed.

l In the Import Workspace group, select the option that best describes where you want toimport data. Select Use previously copied ProSystem fx Engagement files in thefollowing folder when performing subsequent imports.

l In the SQL Server group, enter your SQL Server instance name and login information.Select Automatically Stop and Start ProSystem SQL Server Instance if you have notmanually stopped the instance prior to starting the import.

Click Next.

6. On the Import Options screen, select the client data that you want to import. Click Next.7. On the Client Selection screen, select the client files that you want to import. Use CTRL + click to

select multiple client files. Click Next.8. On the Bulk Conversion Options screen, select Create an Excel configuration file to store your

client and binder information. In the Auto-populate file field, browse for your CCHBulkAutofill.inifile. Click Create.

9. The Excel configuration file opens for your review. If the data is correct, close the Excel file.

10. A summary of the import displays.

l Excel configuration file: The path of the configuration file created in the previous step.l Folder for newWP files: Browse for a folder to store the new Working Papers files.l Mapping/Grouping config file: Browse for your cchmapping-grouping.ini file toautomatically fill out map and group numbers in the Working Papers file.

Click Convert to proceed.

The data is imported to your Working Papers file.



Convert third-party linksYou can convert links from third-party applications to Connector links. Converting a third-party linkreplaces the existing link formula with the Connector equivalent. Only Connector formulas canestablish a connection to a Working Papers database.

Notes:

l Links must be converted manually if they contain errors in the original formula, have noequivalent Connector function, or include ranges (e.g. J.J10:L.L90).

l After conversion, links that referenced the third-party entity are changed to reference the defaultWorking Papers entity.

l See the ProSystem fx Engagement conversion for a list of ProSystem fx functions that can beconverted.

To convert third-party links to Connector links:

1. Open the document containing the third-party links in Word or Excel.

2. On the ribbon, click the Add-ins tab. In the Connector group, click Tools | Convert | Third PartyFormulas....

3. The Convert dialog is displayed. In the Convert From: drop-down menu, select the relevant third-party application. In the Convert To: drop-down menu, select the function type. Click OK to beginthe conversion.



4. When a third-party link is identified, the Convert dialog displays.

Field Description

Old Formula Displays the existing link formula (third-party).

New FormulaDisplays the new link formula after conversion to DDE/UDF functions.You can manually modify this field if required.

New Formula ResultDisplays the value that the new formula retrieves from the activeWorking Papers database. If the new formula is manually modified,click Recalculate to refresh the result.

5. To proceed, choose from the following options:

l Find Next: Skip conversion for the current link.

l Replace: Accept conversion for the current link.

l Replace All: Accept conversion for all links in the document.

l Recalculate: Recalculate the formula result based on manual modifications.

l Close: Cancel the conversion.



6. Repeat for each link until they have all been converted or skipped.

The third-party links in the document are converted to Connector links. Review the document toensure all links return the appropriate values, then save the changes.

ProSystem fx Engagement conversion

When converting ProSystem fx Engagement links to Connector links, you will receive an error if any ofthe following issues occur:

l There is an error in the original ProSystem fx Engagement formulal The original formula is longer than 1024 charactersl There is no equivalent function in Working Papersl The original formula contains a range

To determine which functions you can convert, refer to the following tables.

Calculation functions

Function Supported

ADDIFF Yes

AORAND No

APDIFF Yes

DDIFF Yes

PDIFF Yes

XFOOT No

Client information functions

Function Supported

CLIENTNAME Yes



CLIENTNAME2 No

CLIENTID Yes

CLIENTADDRESS1 Yes

CLIENTADDRESS2 Yes

CLIENTCITY Yes

CLIENTSTATE Yes

CLIENTZIP Yes

CLIENTCOUNTRY Yes

CLIENTPHONE Yes

CLIENTFAX Yes

CLIENTURL Yes

PRIMARYEMAIL Yes

SECONDARYEMAIL Yes

CLIENTTYPE No

CLIENTINDUSTRY No

CLIENTFEIN No

CLIENTSTATEID No

FIRM(YYY) No

Date functions

Function Supported



CY Yes

PY Yes

CYBDATE Yes

CYEDATE Yes

CPBDATE Yes

CPEDATE Yes

PYEDATE Yes

PPBDATE No

PPEDATE No

PERIODSQ Yes

Name functions

Function Supported

PJNAME No

BINDER(YYY) No

WPNAME Yes

WPINDEX No

Trial balance functions

Function Supported

TBLINK Yes



cch prosystem fx import guide

Documents