Overview

After exporting transactions from the LedgerSync for Accounting CS application, you'll have an 11-column CSV file formatted specifically for the Accounting CS Spreadsheet Import Wizard. This article explains how to import that CSV file into your Accounting CS software.

Prerequisites

Before importing:

• You've exported transactions from the LedgerSync Accounting CS app
• The CSV file is saved on your computer (typically in Downloads folder)
• You're logged into Accounting CS
• The client exists in Accounting CS
• GL codes in the CSV match your Accounting CS chart of accounts

Step-by-Step Import Process

Step 1: Open Accounting CS

1. Launch Thomson Reuters Accounting CS
2. Open the client's company file you want to import transactions for

Step 2: Access the Spreadsheet Import Wizard

1. In Accounting CS, go to Tools
2. Select Spreadsheet Import Wizard
3. The Import Wizard window opens

Step 3: Select the CSV File

1. Click "Browse" or "Select File"
2. Navigate to your Downloads folder (or wherever you saved the export)
3. Select the LedgerSync CSV file (filename typically includes client name and date range)
4. Click "Open"

Step 4: Confirm Column Mapping

The Spreadsheet Import Wizard will display the CSV columns. Verify the mapping:

Column Mappings (11 columns):

Note: The LedgerSync CSV is pre-formatted for Accounting CS, so column mapping should be automatic. If any columns are unmapped, use the dropdown menus to assign them correctly.

Step 5: Review Import Settings

Check the following settings:

• Import Type: Select "General Ledger Transactions" or "Cash Receipts/Disbursements" (depending on your workflow)
• Date Format: Should be MM/DD/YYYY (matches LedgerSync export format)
• Skip Header Row: Ensure this is checked (CSV has column headers in first row)

Step 6: Import the Data

1. Review the preview of transactions to be imported
2. Verify transaction count matches your LedgerSync export
3. Click "Import" or "Next"
4. Wait for the import process to complete
5. Accounting CS will display a completion message showing:
   • Number of transactions imported
   • Any errors or warnings

Step 7: Verify in Accounting CS

After import completes:

1. Go to the client's General Ledger
2. Check that imported transactions appear correctly
3. Verify:
   • Transaction dates are correct
   • Amounts match your LedgerSync export
   • GL codes are assigned correctly
   • Vendor names appear properly

Common Import Issues and Solutions

Issue: "Column Mismatch" Error

Solution:

• Manually map columns using the dropdown menus in the Import Wizard
• Ensure all 11 columns are mapped to the correct ACS fields
• Double-check that you selected the correct CSV file

Issue: "Duplicate Transactions" Warning

Solution:

• Check if these transactions were already imported previously
• Review your export history in LedgerSync to avoid re-importing same date range
• If truly duplicates, skip import or manually delete duplicates after import

Issue: "Invalid GL Code" Error

Solution:

• Verify the GL codes in the CSV match your Accounting CS chart of accounts
• GL codes must exist in ACS before import
• Add missing GL codes to your chart of accounts, then retry import
• Check for typos in GL codes (e.g., "610O" vs "6100")

Issue: "Date Format Error"

Solution:

• LedgerSync exports use MM/DD/YYYY format
• Ensure Accounting CS Import Wizard is set to MM/DD/YYYY format
• If error persists, check that dates in CSV are valid (e.g., no Feb 30th)

Issue: "Vendor Not Found" Warning

Solution:

• Accounting CS may create new vendors automatically during import
• Alternatively, pre-create vendors in ACS before importing
• Ensure vendor names match your ACS vendor list (if you want to use existing vendors)

Issue: Transaction Count Doesn't Match

Solution:

• Count transactions in the CSV file (excluding header row)
• Compare to the count shown in LedgerSync export confirmation
• Check for any rows with errors that were skipped during import
• Review the import log for details on skipped transactions

Best Practices

Review Before Importing:

• Open the CSV file in Excel before importing to verify data looks correct
• Check for any obvious errors or missing data
• Verify transaction count matches what you expect

Import Regularly:

• Import transactions weekly or monthly (depending on your workflow)
• Smaller, regular imports are easier to verify than large bulk imports
• Keep track of what date ranges you've already imported

Backup First:

• Create a backup of your ACS company file before importing large batches
• This allows you to rollback if import has unexpected issues

Document Your Process:

• Keep notes on which date ranges have been imported for each client
• Use LedgerSync's export history feature to track what's been downloaded

Alternative Import Methods

If the Spreadsheet Import Wizard doesn't work for your workflow, consider:

• Manual Entry: For small transaction volumes, manual entry may be simpler
• Third-Party Tools: Some accounting firms use data import tools that work with ACS
• Custom Scripts: For advanced users, custom import scripts can be developed

Need Help?

If you're experiencing import issues:

• LedgerSync Support: support@ledgersync.com (for CSV format questions)
• Thomson Reuters Support: Contact TR support for Accounting CS Import Wizard issues

Related Articles:

• Article 76: What is LedgerSync for Accounting CS?
• Article 78: How to Get Started with LedgerSync for Accounting CS
• Article 81: Understanding the Review & Export Workflow
• Article 83: Creating and Managing Vendor Rules
• Article 84: Creating and Managing GL Code Rules