Txs Verify lets you compare one account's transactions from two sources, side by side, for a date range you choose. One side shows the transactions read from the account's bank statements. The other side shows the transactions fetched from the bank connection. Each row shows whether the two sides match. It works for MasterCard, MX and Statements & Checks connections.
Who can use it
Firm users can open Txs Verify for the clients they have access to. If a client signs in and tries to open it, they are taken to their own client profile instead.
Where to find it
You can open it in either of these ways:
- From the Bank Connections menu, select Txs Verify.
- On the Bank Connections page, select the Txs Verify tab.
If you haven't selected a client, LedgerSync selects the first client for you.
How to run a check
- In the selector, choose an account. You can only choose accounts on this page: bank connections are greyed out and can't be selected. When the page opens, an account is already selected for you.
- Set the Transaction Date range. By default, it runs from the first day to the last day of the previous month. You can change the dates, but you can't clear the range.
- Wait for the check to finish. While it runs, the page shows "Checking reconciliation status...". When the check is ready, the grid appears.
The check runs again each time you change the account, the dates or the search text.
If some statements in the date range haven't been read and checked yet, LedgerSync prepares them first. While this happens, the page shows messages such as "Preparing data..." and "Still preparing...".
If the client has no account to select, the page shows "No Bank Connection or Account selected".
For MasterCard connections, the start date must be on or after December 1, 2025. For an earlier start date, the page shows "No data available for this period".
What the grid shows
Each row has:
- A match icon: a green check means the row is matched, and a red warning means it is not.
- Account Code: the number or code of the selected account, the same on every row.
- A Statement Transactions group with Date, Description and Amount.
- A Fetched Transactions group with Date, Description and Amount.
Rows are sorted by date, newest first, by default.
If both sides of a row have a value and the two values are different (ignoring upper and lower case), the cells are highlighted. The highlight is yellow on matched rows and red on unmatched rows.
To show only some rows, type in the Search... box next to the date range. Only rows where the statement description or the fetched description contains that text are shown. The search ignores upper and lower case.
How transactions are matched
A fetched transaction is matched to the first statement transaction found that hasn't already been matched, has exactly the same amount, and is dated no more than 4 days before or after it. Transactions without a date or an amount are never matched.
- A fetched transaction with no match appears on its own row, with only the fetched side filled in.
- A statement transaction with no match appears on its own row, with only the statement side filled in.
Which transactions are included
- Statement side: statements dated within the range, and the transactions on them that are dated within the range. Statement lines without a date are kept.
- Fetched side, MasterCard connections: active transactions posted within the selected date range.
- Fetched side, MX and Statements & Checks connections: the account's transactions dated within the selected date range.
When there are problems with statements
If any statement in the date range has a problem, the check can't go ahead and the grid is not shown. Instead, the page shows "Cannot proceed with reconciliation. Some statements have issues that need attention." and a Statement Issues: list. The list gives each affected statement's number, its date and the reason. Reasons include:
- "Statement balance doesn't match extracted transactions. Please review the statement or contact support."
- "Statement extraction or validation failed. Please retry extraction or contact support."
- "The stored statement PDF is corrupt or incomplete, so it cannot be extracted. Retrying will not help - the statement needs to be fetched again from the provider. Please contact support."
A statement that was skipped during validation is also listed, with the reason it was skipped. For example:
- "Statement is a brokerage/investment statement and cannot be reconciled using standard methods."
- "Document is not a bank statement (may be a check image, wire receipt, etc.)."
- "Statement is missing beginning balance information."
- "Statement is missing ending balance information."
- "No transactions were extracted from the statement."
- "An error occurred while calculating the statement balance."
- "Validation was skipped for this statement."