What Is the Verified Running Balance Report?

The Verified Running Balance report is LedgerSync's solution for customers who cannot access a traditional bank statement — whether because the bank does not support statement downloads, the connection does not support PDF retrieval, or statements are simply unavailable for a given account or time period.

Instead of relying on a bank statement, this report reconstructs your account history using two independent bank data feeds — Finicity (Mastercard) and MX — and cross-validates the results to produce a running balance that is as accurate and trustworthy as possible.

Think of it as a bank-grade transaction ledger that LedgerSync builds for you, showing every debit, credit, and running balance in chronological order — exactly the way your bank's website displays your account activity.

When Should I Use This Report?

Use the Verified Running Balance report in any of the following situations:

• Your bank does not support PDF statement downloads through LedgerSync
• Statement fetching has failed and no statement is available for the date range you need
• You need transaction history for a period that predates your statement connection
• You want an independently verified transaction ledger to supplement or replace a bank statement for reconciliation purposes

This report is the recommended alternative whenever a bank statement cannot be retrieved. It is not a replacement for a bank statement in all contexts, but it provides a high level of confidence when statement access is unavailable.

How Does It Work?

LedgerSync connects to your bank through two separate data networks simultaneously:

• Finicity (Mastercard) — LedgerSync's existing primary bank data connection
• MX — A second, fully independent bank data network added specifically to verify the Finicity feed

Both networks retrieve your transactions independently. LedgerSync then compares what each network reports. When both networks agree on a transaction, it is marked as verified and included in the running balance with full confidence. When only one network reports a transaction, it is flagged for review so you can investigate before including it.

Throughout the day, LedgerSync also takes balance snapshots directly from your bank. These snapshots serve as checkpoints — if your calculated running balance drifts significantly from the bank's reported balance over several days, that is a signal that transactions may be missing.

Understanding the Confidence Grade

Every Verified Running Balance report is assigned a confidence grade from A to F, displayed prominently at the top of the report.

• Grade A — Dual Verified: Both Finicity and MX agree on all transactions. The running balance is confirmed accurate and ready for reconciliation.
• Grade B — Mostly Verified: One or two transactions are not yet confirmed by the second network, likely due to a timing delay. The balance is reliable with minor caveats.
• Grade C — Partially Verified: Only one data source is connected, or the match rate between the two feeds is below 80%. Use with caution.
• Grade D — Low Confidence: Significant gaps exist in the transaction feed. Several days of balance history are missing or unverified.
• Grade F — Unverified: The bank connection is broken. Do not use this report for reconciliation until the connection is restored.

The grade updates automatically as new transactions arrive and are verified. A report that starts at Grade B can improve to Grade A without any action on your part once the second feed catches up.

What Does the Report Show?

The report has three tabs:

• Running Balance — The main ledger. Every transaction in date order with its debit or credit amount, running balance after each transaction, data source badge, and verification status. This is the tab to use for reconciliation.
• Feed Comparison — A side-by-side view of the Finicity and MX transaction lists. Use this tab to investigate any transactions that only appeared in one feed.
• Snapshots — A table of all balance snapshots taken during the selected period, showing the variance between the snapshot balance and the calculated running balance at each point in time.

What Happens When Transactions Do Not Match?

When a transaction appears in only one feed, LedgerSync surfaces it clearly with a warning icon and an estimated balance. You can resolve unmatched transactions with one of three options:

• Hold for 48 hours — The transaction is pending or delayed. LedgerSync will automatically re-check once the holding period has passed.
• Accept as single-source — You have independent confirmation the charge is real. Include it in the balance. The report grade will adjust to reflect the single-source status.
• Discard — The transaction is a data artifact from one aggregator. Remove it from the balance and log it as a false positive. The grade remains unaffected.

What Happens When the Bank Connection Was Offline?

If the bank connection was broken for a period of time, the report shows a clearly labeled gap row for those dates with an estimated balance. The last confirmed balance before the gap is preserved as an anchor. When the connection is restored, the report automatically rebuilds forward from that anchor using recovered transactions.

Gaps are never hidden. You will always know exactly which date ranges have incomplete data and what the last confirmed balance was before the gap.

Requirements

To generate a Grade A Verified Running Balance report, your account must be connected through both Finicity and MX. If only one aggregator is connected, the report will still generate at a lower confidence grade with a prompt to connect the second data source.

If you need help connecting your bank through both data sources, please contact LedgerSync support at support@ledgersync.com.