FMSweb5 Welcome myacct


Untitled Document CLS Frequently Asked Questions

D. General

1. Importing CLS reports into Microsoft Word

  1. In CLS, select the report you want to bring into Word. Print it to a file and accept the default name provided by CLS (e.g., CLBSJCC.PRN). The file will be saved in the CLS program path, normally c:\newcls.
Note: Saving the file on a floppy disk will make it easier to find in Word.  To do this, insert A: before the file name (e.g., A:CLBSJCC.PRN).
  1. Start Word.  From the Word menu, select Tools, then options.  Select the tab marked General, and check Confirm Conversion at Open(This only has to be done once).
  1. In Word, select file, then open the report file in the CLS program path.
  1. When the Convert File window appears, choose Encoded Text, and select Other Encoding.
  1. For the conversion format, select OEM United States.
  1. Now choose File and Page Setup. Change the top and bottom margins to 0.5”.
  1. Remember that CLS uses fixed-space fonts. If you change the report font in Word to a proportional font, the amount columns will no longer line up.
  1. If you wish, save the imported file as a Word document (change the file type and the name).
  1. At this point, you may fax or e-mail the report or, if you have purchased Adobe Acrobat, print it to a pdf file.

Top of Page
Return to CLS FAQ's Home


2. Importing transactions from Peachtree Software
In CLS, AT 1 (3) lets you import transactions from most Windows versions Peachtree Software.  You can import all transactions, including payroll checks.

The Peachtree chart of accounts must be compatible with the CLS chart of accounts, and employees in Peachtree must be assigned CLS employee numbers.

When exporting transactions from Peachtree, you must separately export A/R (both invoices and cash receipts), A/P (both invoices and payments), Payroll, and General Ledger transactions.  CLS requires a specific record layout for each of these files, and each must be imported separately into CLS.

Please refer to Appendix C of the CLS Reference Guide for detailed instructions on setting up Peachtree for compatibility with CLS, and for creating the export files.

Top of Page
Return to CLS FAQ's Home


3. Importing transactions from QuickBooks
In CLS, AT 1 (6) lets you import transactions from all Windows versions of QuickBooks.  You can import all transactions, including payroll checks.

The QuickBooks chart of accounts must be compatible with the CLS chart of accounts, and employees in QuickBooks must be assigned CLS employee numbers.  Since QuickBooks does not use employee numbers, there is a trick to this part.  Also, QuickBooks doesn’t specifically allow transactions to be exported; however, printing the Journal to a file can create the export file  CLS needs.

Please refer to Appendix C of the CLS Reference Guide for detailed instructions on setting up QuickBooks for compatibility with CLS, and for creating the export file.

Top of Page
Return to CLS FAQ's Home


4. Net profit doesn’t print on the balance sheet
Either the current earnings account(s) are not set up correctly in LI 3 (3), or the accounts have not been added to the chart of accounts.

In LI, Menu Selection 3 (3), choose shareholder/partner number 1, and enter the correct account number.  If you have defined more than one shareholder, enter the correct account numbers for each shareholder; use different accounts for each shareholder.

Make sure that all of the accounts used in LI 3 (3) are present in the chart of accounts.

Top of Page
Return to CLS FAQ's Home


5. Transferring transactions from one ledger or generation to another
Transactions can easily be moved from one ledger or generation to another using the Accounting Transfer (AT) program:
a. Export the transactions from the incorrect ledger/generation:
  1. Use LS to select the ledger or generation where the transactions were entered incorrectly.

  2. Use AT 4 (4), (Export CLS Info, Current or YTD Transactions) to create an export file.  Block all the transactions that need to be moved.  Make a note of the export file name and the export path; you will need this information when importing the transactions (below).

b. Import them into the correct ledger/generation:

  1. If the transactions were entered in the wrong generation (not the wrong client), and you need a new generation to move the transactions into, close the current generation (EP) to roll forward to the next period.
  2. If you are not already in the correct ledger/generation, use LS to select the ledger generation where the transactions are to be imported.
  3. Use AT 3 (3,1) (Import CLS Info, Comma-delimited Transaction File, Standard CLS Field Sequence) to import the file created above.  Enter the path and file name from step a2.
  4. The transactions will be edited during the import process.  Print an edit listing (Exceptions Only is OK).  If any transactions fail, don’t import the valid ones.  Instead, correct the problems (add accounts, employees or vendors as needed) and then re-import.
  5. After importing the transactions, you can view or edit them using ET; you may need to correct the transaction month or year.
  6. Use PT to post the new transactions.
c. Now, delete the incorrectly entered transactions:
  1. Use LS to return to the ledger/generation where the transactions were entered in error.  Use PT to unpost the transactions, then ET to edit them.  Use F3 to block the transactions that have been transferred, and press D to delete them.
  2. Use PT to re-post the edited transactions.
  3. If the transactions were entered in the wrong generation (not the wrong client), re-close (EP) this generation, answering Y to Keep Existing Transactions, to bring the correct balances forward.

Top of Page
Return to CLS FAQ's Home


Contact Us |  Support |  Privacy Policy |  Site Map
Copyright 2017 - Financial MicroSystems, Inc. All rights reserved.