Bank statement evidence, kept traceable
Banktrail turns statement exports into a transaction ledger with links back to source evidence. Named accounting ledgers keep your own entries alongside the bank record, with the same tags, comments, supporting images and search. It is built for people who need to review statement coverage and explain what a check found and what still needs an answer.
What Banktrail checks
- Statement rows are normalized into a ledger and retain references to their source files.
- Unread rows and statement arithmetic exceptions remain visible for review.
- Consecutive statement balances are compared to identify breaks in the available record.
- Notes, tags, and attached supporting evidence can be kept with a hosted ledger or in a local installation.
These checks organize evidence for a human reviewer. They do not determine why a difference occurred or replace review of the account, reporting period, and supporting documents.
Accounting entries linked to bank transactions
Create a named ledger and add entries manually or import CSV. Search within one ledger or across your accounting ledgers, then confirm links to bank transactions using the amount, currency, date and reference. Open each match from either side to review the connected record and its evidence.
Several accounting entries can link to one bank transaction, and one entry can link to several bank transactions. Each match records its reviewer, method and optional note and confidence. A reviewer can withdraw their own claim. See the supplier invoice example or read about the ledger workflow.
Hosted or local
The hosted workspace is available after sign-in. The new desktop preview for Mac and Windows opens local ledgers without a terminal or separate server. Public installers are not available yet. Command-line and self-hosted tools also let an organization choose where its ledger and attachments are stored. See the supported file formats and the synthetic review examples for more detail.