FDE Statement Extraction — How It Works & Custom Date Range

FDE Statement Extraction — How It Works & Custom Date Range

Notes
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 connection. This article explains how FDE works and how to use the custom date range feature.

What Is FDE?

FDE is a statement and transaction extraction method that LedgerSync uses when a standard Mastercard or MX API connection is not available for a bank. Instead of pulling data through an open banking API, FDE extracts data from financial documents (statements) through a secure extraction pipeline.

FDE is distinct from uploading a PDF manually — it is an automated document extraction connection that can refresh periodically, while PDF upload is a one-time manual action.

Adding an FDE Connection

  1. Click Add Bank Connection for the client
  2. Look for the FDE option (may be labeled as "Statement Extraction" or appear for specific banks)
  3. Follow the connection prompts
  4. LedgerSync will begin extracting statements and transactions for that account

Custom Date Range for FDE

When refreshing an existing FDE connection or adding a new one, you can now specify a custom date range for the extraction instead of relying on the default lookback period.

How to use:
  1. Open the FDE connection for the client
  2. Click Refresh (or Add Connection for a new one)
  3. Select the From and To dates for the range you want to pull
  4. Click Run

Limits and validation:
  • Maximum range: 6 months back from today
  • The From date cannot be after the To date
  • Future dates are not permitted
  • Ranges exceeding 6 months return a clear error message

Handling MFA / Bank Tokens for FDE Connections

Some FDE banks require a one-time security code (MFA token) to complete or refresh the extraction. When a token is required, LedgerSync can text the token request directly to the client — the same streamlined flow used for Mastercard and MX connections.
  • The client receives a secure text prompting them for the bank’s one-time code
  • They enter the code on their own device — you don’t need to be on a call with them
  • Once submitted, the FDE extraction continues automatically
This means FDE connections that require periodic re-verification can be resolved without the accountant handling the client’s security code manually.

Extraction Summary Popup

After FDE finishes processing a bank connection, LedgerSync displays a summary popup showing:
  • Number of statements extracted
  • Number of transactions extracted
  • Any errors or exceptions that occurred during extraction
This lets you immediately confirm how much data was pulled in without navigating away from the page.

FDE Connections in the Communication Center

FDE bank connections are now included in the Communication Center’s broken-connection tracking. If an FDE connection breaks:
  • It is counted in the broken connections report alongside Mastercard and MX connections
  • You can send a fix or reconnect notification to the client directly from the Communication Center, the same way you would for a Mastercard or MX connection

FDE via the LedgerSync API

FDE-sourced statements and transactions are available through the LedgerSync API alongside Mastercard and MX data, so firms building custom integrations can retrieve FDE data programmatically. Contact support for API access and details.

Need Help?

Contact LedgerSync Support at support@ledgersync.com

Related Articles:

    • Related Articles

    • Bank Connection Notes — How to Add Shared Notes to a Bank Connection

      Overview The Notes feature lets you attach persistent, shared notes to any bank connection in LedgerSync — whether it is connected via Mastercard, MX, or FDE (document-based extraction). Notes are visible to all users in your firm and are a great way ...

    • 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 ...

    • 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 ...

    • LedgerSync Close — Overview and How It Works

      Overview LedgerSync Close is a month-end reconciliation tool that compares your bank statements directly against the transactions recorded in QuickBooks Online (QBO). It automatically identifies missing transactions, duplicate entries, and category ...