Why are the bank transactions truncated at times?

Why are the bank transactions truncated at times?

Overview

Bank transactions imported via the Mastercard API are sometimes truncated to 32 characters in the description field. This is not a LedgerSync limitation — it comes from the bank itself, which sends data in the legacy Quicken format capped at 32 characters.

Why This Happens

When banks transmit transaction data to Mastercard's aggregation network, some use the old Quicken data format, which limits transaction descriptions to 32 characters. LedgerSync receives exactly what the bank sends and cannot extend truncated descriptions.

The Solution: Use the PDF Statement Instead

PDF bank statements always contain the full transaction description. LedgerSync can convert any bank PDF statement into Excel, CSV, QBO, or OFX format — giving you complete transaction details.

How to Convert a Bank Statement PDF

  1. Click Tools in the top navigation bar.
  2. Select PDF Converter.
  3. Drag and drop your bank statement PDF into the converter.
  4. Choose your export format: Excel, CSV, QBO, or OFX.
  5. Download the converted file.
Warning
The PDF converter cannot process image-only (scanned) PDFs or password-protected PDFs. To test if your PDF will work, try highlighting and copying text from it — if you can, the converter should be able to read it.

Need Help?

Contact us at support@ledgersync.com.

    • Related Articles

    • How to Upload a Bank Statement PDF as a Transaction Source in LedgerSync

      Overview LedgerSync supports uploading bank statement PDFs directly as a live transaction source — alongside your Mastercard and MX bank connections. This is ideal for clients whose banks cannot be connected electronically, or where only a PDF ...

    • MX Statement Aggregation — Which Banks Support Statement Downloads via MX?

      Overview LedgerSync supports bank statement aggregation through two aggregators: Mastercard Open Finance and MX. Not every bank that supports transaction aggregation via MX also supports statement aggregation. This article explains how MX statement ...

    • MX Bank Connection — Overview, Setup, and FAQ

      Overview MX is LedgerSync's second full bank data aggregator, available alongside the Mastercard API. MX is fully deployed and actively used across the platform — it is not a beta feature. If your bank is not supported by the Mastercard API, or if ...

    • FDE Statement Extraction — How It Works & Custom Date Range

      Overview FDE (Financial Document Extraction) is LedgerSync’s document-based statement extraction pipeline. It is used for banks and financial institutions that require statement retrieval through document extraction rather than a direct API ...

    • How to Convert Bank PDF Statements to Excel, QBO, or CSV

      Overview The LedgerSync PDF Converter extracts transactions from bank statement PDFs and converts them into Excel, CSV, QBO, or OFX format — without any manual data entry. This is especially useful when a client can only provide PDF statements and ...