Accounting CS (ACS) Integration — 2026 Updates & Important Changes

Accounting CS (ACS) Integration — 2026 Updates & Important Changes

Notes
Overview
LedgerSync's Accounting CS (ACS) integration has received significant improvements in 2026. This article summarizes the key changes that affect how ACS users work with GL codes, exports, and the Rules Engine. If you previously used the ACS integration, please review this article in full — some behaviors have changed.

Summary of Changes

What ChangedBeforeNow
GL Code display formatAccount name only (e.g., "Cash - Checking")GL Code + name combined (e.g., "1000 - Cash - Checking")
ACS export file formatCSV (.csv)Excel (.xlsx) — plus OFX available
GL Code column in exported fileNot includedIncluded as a dedicated column
Deleting client-created categories/vendorsNot possibleCan be deleted individually
ACS app platformLegacy platformMigrated to LedgerSync's Java-based platform (faster, more stable)
Uploading ACS chart of accounts (wrong option)Silently imported with incorrect formatRejects with a clear error and directs you to the correct upload option

Change 1 — GL Code Now Shown with Account Name

Previously, the Rules Engine, Manual Categories edit page, and Transactions/Categorized page displayed only the account name (e.g., "Cash - Checking") without the GL Code number. This made it difficult to identify the correct account when multiple accounts had similar names.

What it looks like now: All account references in the ACS integration now display the GL Code and the account name together — for example, "1000 - Cash - Checking." This applies everywhere the account is referenced: the category dropdown, the Transactions page, the Categorized page, and the Manual Categories edit screen.

What you need to do: Nothing — this is automatic. The format updated across all screens. If you notice an account that isn't showing a GL Code prefix, contact support.

Change 2 — ACS Export Now Produces XLSX (and OFX Is Available)

The export file format for Accounting CS transactions has changed from CSV to XLSX (Excel). Accounting CS only accepts XLS or XLSX files for import — the previous CSV format could not be imported directly, requiring manual conversion. The XLSX format eliminates that extra step.

In addition, an OFX download is now available for Accounting CS customers who import statement data via OFX, alongside the existing CSV and XLS options.

What it looks like now: When you click the export button for ACS, the downloaded file is named with a .xlsx extension and opens directly in Excel. You can import it into Accounting CS without any conversion. OFX is offered where your workflow requires it.

What you need to do: Update any internal workflows that expected a CSV file. The data and column structure are the same — only the file format changed.

Change 3 — GL Code Column Added to ACS Excel Export

The GL Code (account number) is now included as a dedicated column in the ACS Excel export file. Previously, the export contained the account name but not the GL Code number, which was required for the import to process correctly in Accounting CS.

What it looks like now: The exported XLSX file includes the following columns:
  • Client Name
  • Bank Name
  • Bank Account
  • Transaction Date
  • Description
  • Amount
  • GL Code (the account number from your chart of accounts)
  • Category / Account Name
What you need to do: If you have any Excel macros, import templates, or scripts that process the ACS export file by column index, update them to account for the GL Code and leading Client/Bank/Account columns.

Change 4 — Delete Client-Created Categories & Vendors

You can now delete categories and vendors that were created within ACS — including test or duplicate entries added by mistake. Previously there was no way to remove them.
What you need to do: Open the category or vendor and use the delete action to remove individual client-created entries.

Change 5 — ACS Platform Migration to Java

The Accounting CS integration app has been migrated to LedgerSync's core Java-based platform. This is an infrastructure change and is transparent to most users — the workflows and screens look the same. The migration brings:
  • Improved stability and speed for vendor matching and GL code matching
  • Better integration with the main LedgerSync Rules Engine — AI vendor/GL matching now behaves the same as the main Rules Engine (including auto-creating a Vendor/GL rule from your edited selection), and bulk actions and the audit log work consistently for ACS clients
  • The standard LedgerSync OCR pipeline is now used for bank statement extraction within ACS, replacing the previous custom OCR
What you need to do: Nothing — the migration is complete and transparent. If you notice any difference in behavior, contact support.

Change 6 — Uploading ACS Chart of Accounts via the Wrong Option

Previously, if you accidentally uploaded an Accounting CS chart-of-accounts spreadsheet through the generic "Categories" upload option (rather than the dedicated Accounting CS option), LedgerSync would silently import it in the wrong format, showing bare GL codes without the account names.

What it looks like now: LedgerSync detects when an Accounting CS file is submitted through the wrong upload option and rejects it with a clear error message, telling you to re-upload using the correct Accounting CS option. Nothing is imported incorrectly.

What you need to do: Always use the Accounting CS upload option (not the generic "Categories" option) when uploading your ACS chart of accounts. If you receive this error, re-upload using the correct option.

Uploading Your ACS Chart of Accounts — Correct Process

  1. In LedgerSync, navigate to the client's ACS configuration
  2. Click Upload GL Codes (or Upload Accounting CS Chart of Accounts — use the option labeled for Accounting CS specifically)
  3. Select your ACS export file
  4. Click Upload
  5. Confirm the import looks correct before saving

AlertNote on re-uploading GL Codes: When you upload a new set of GL codes, the setup page no longer pre-loads the old data from a previous import. The Review button stays disabled until a new file has been uploaded. This prevents confusion between stale and freshly imported data. Always upload a fresh file before reviewing.

Exporting Transactions for Multiple Clients

When you apply a bank account filter before exporting to Accounting CS, the XLSX file now generates correctly (a previous bug caused the file to download as empty/zero bytes when a filter was applied).

Note that transactions from two different clients cannot be combined into a single exported spreadsheet. If you need to export for multiple clients, export each client's transactions separately.

Need Help?

Contact LedgerSync Support at support@ledgersync.com

Related Articles: