Overview

After exporting transactions from the LedgerSync for Accounting CS App, you need to import the CSV file into Accounting CS. This article explains how to use the Spreadsheet Import Wizard to complete the import process.

Prerequisites

• CSV file - Exported from the LedgerSync for Accounting CS App
• Accounting CS - Installed and running with client file open
• Import permissions - User must have rights to import transactions

Step 1: Locate Your CSV File

1. Find the CSV file you exported from the ACS app
2. File name format: ClientName_BankName_StartDate_EndDate.csv
3. Note the location - you'll need it for the import wizard

Step 2: Open Accounting CS

1. Launch Accounting CS
2. Open the client file you want to import transactions into
3. Verify you're in the correct client before proceeding

Step 3: Access the Spreadsheet Import Wizard

1. Go to File menu
2. Select Import/Export
3. Click Spreadsheet Import Wizard
4. The wizard opens with a welcome screen
5. Click Next

Step 4: Select the CSV File

1. Click Browse button
2. Navigate to your CSV file location
3. Select the file
4. Click Open
5. File path appears in the text box
6. Click Next

Step 5: Map Columns

The import wizard shows column mapping screen.

Auto-Mapping

If you're using the standard LedgerSync export format, columns should auto-map:

• Date â†' Transaction Date
• Transaction ID â†' Reference
• Vendor Code â†' Vendor
• Description â†' Description/Memo
• Debit â†' Debit Amount
• Credit â†' Credit Amount
• GL Code â†' Account Number
• Reference â†' Check Number

Manual Mapping (if needed)

If columns don't auto-map:

1. Click dropdown next to each CSV column
2. Select the matching Accounting CS field
3. Ensure Date, Vendor, Amount, and GL Code are mapped
4. Optional fields (Department, Class) can be left unmapped

Click Next when mapping is complete.

Step 6: Review Import Settings

Settings screen appears with options:

Key Settings

• Import to - Verify correct journal (usually General Journal)
• Date format - Should match your CSV (MM/DD/YYYY)
• Duplicate handling - Choose "Skip duplicates" or "Create new"
• Validate vendor codes - Leave checked to verify vendors exist
• Validate GL codes - Leave checked to verify accounts exist

Recommended Settings:

• Import to: General Journal
• Skip duplicate entries: Checked
• Validate vendors: Checked
• Validate accounts: Checked

Click Next to continue.

Step 7: Preview Import

1. Preview screen shows first 10-20 transactions
2. Review data to ensure it looks correct
3. Check:
   • Dates are formatted correctly
   • Vendor codes match your vendor list
   • GL codes are valid
   • Debits and credits are in correct columns
4. If errors appear, click Back to adjust mapping
5. If preview looks good, click Import

Step 8: Execute Import

1. Import process begins
2. Progress bar shows completion status
3. For 100 transactions: typically 5-15 seconds
4. For 1000+ transactions: may take 1-2 minutes

Step 9: Review Import Results

When import completes, you'll see a summary:

• Total records processed - Number of transactions in CSV
• Successfully imported - Transactions added to Accounting CS
• Errors/Warnings - Transactions that couldn't be imported
• Skipped (duplicates) - Transactions already in the system

If Errors Occurred

1. Click View Error Log
2. Review which transactions failed and why
3. Common issues:
   • Invalid vendor code
   • Invalid GL code
   • Missing required field
   • Date format mismatch
4. Note the errors
5. Correct the CSV file or create missing vendors/GL codes
6. Re-import if needed

Step 10: Verify Imported Transactions

1. Navigate to the General Journal in Accounting CS
2. Filter by date range matching your import
3. Spot-check transactions:
   • Verify amounts are correct
   • Check vendor codes assigned properly
   • Confirm GL codes are accurate
   • Review debits vs credits
4. Run trial balance to ensure books still balance

Troubleshooting

Issue: "Invalid vendor code" errors

Solution:

1. Go to Accounting CS vendor setup
2. Add missing vendor codes
3. OR: Update CSV file to use existing vendor codes
4. Re-import the file

Issue: "Invalid account number" errors

Solution:

1. Verify GL codes in CSV match your chart of accounts
2. Add missing GL codes to chart of accounts
3. OR: Correct GL codes in the CSV file
4. Re-import

Issue: "Duplicate transaction" warnings

This is normal if:

• You're re-importing a file you already imported
• Transactions already exist from a different source

Duplicates are skipped automatically - no action needed.

Issue: Dates appear in wrong format

Solution:

1. Go back to column mapping step
2. Change date format setting to match your CSV
3. Common formats: MM/DD/YYYY, DD/MM/YYYY
4. Re-import

Best Practices

• Backup first - Always backup your Accounting CS client file before importing
• Test with small file - Import 10-20 transactions first to verify process
• Review before finalizing - Check imported transactions before closing the period
• Keep CSV files - Save copies of all CSV files imported for audit trail
• Document vendor mappings - Keep a reference list of vendor codes used

After Import: Month-End Close

1. Review all imported transactions
2. Make any necessary adjustments
3. Run financial reports
4. Complete your normal month-end close process

Need Help?

For assistance with the import process, contact support@ledgersync.com

Updated: March 19, 2026