Reconcile bank exports with your ledger, timing differences included.
Use structured CSV or XLSX exports with a shared transaction reference. MatchDock can compare amount and allow an explicit number of days between bank and ledger dates, while keeping unmatched transactions visible for review.
Key-based, one-row-to-one-row matching. Files stay in your browser.
Source A · bank export
bank-transactions.csv
| Reference | Value Date | Amount |
|---|---|---|
| TX-71 | 2026-08-12 | 150.00 |
| TX-72 | 2026-08-14 | -5.00 |
Source B · ledger export
ledger-postings.xlsx
| Reference | Posting Date | Amount |
|---|---|---|
| TX-71 | 2026-08-13 | 150.00 |
| TX-73 | 2026-08-15 | -70.00 |
Rule: Key: Reference + Date · Date difference: up to 1 day · Compare Amount
- TX-71
- Matched within date tolerance
- TX-72
- Only A · review bank item
- TX-73
- Only B · review ledger item
Check the input fit before you start.
MatchDock reads exported CSV/XLSX tables, not PDF statements. It needs a usable key such as a shared reference; there is no fuzzy payee matching, so it does not guess that “Acme Corp” and “Acme Corp Inc” are the same payee. It matches one row to one row, so grouped settlements or a payment split across ledger rows must be prepared outside MatchDock. It does not categorize transactions or create journal entries.
One bank export, one ledger export, a reviewable result.
Bank statement export → MatchDock ← Ledger / accounting export
1. Prepare comparable exports
Use CSV or XLSX tables for the same account, currency and review period. Check the date and amount basis. For one signed amount column, explicitly choose Keep sign or Negate sign per source in Rules. Prepare separate debit/credit columns outside MatchDock.
2. Choose identity and comparison rules
Use a shared reference or an explicit composite key. Select the amount and date fields you need to compare; apply text normalization, absolute or percentage amount tolerance, and date tolerance only when your process permits them. Amount comparisons use exact decimals.
3. Check both directions
Use the bank export as Source A and the ledger as Source B. Review both bank-only and ledger-only transactions, along with differences, duplicates and invalid keys. A match in one direction does not establish that the other file is complete.
Value date and posting date can differ.
A transaction may appear on the bank export a day before it posts to the ledger. Map the two date columns, add Date to a key with the transaction reference, and set a one-day tolerance if that fits your process. MatchDock only pairs a unique candidate within the configured window; ambiguous candidates remain exceptions.
A date difference or an unmatched row can prompt a timing review. MatchDock does not determine whether it is an outstanding check, a deposit in transit or an accounting adjustment; you investigate the records and decide the treatment.
Prepare comparable amounts
Check whether credits and debits use the same sign convention in both exports. A NUMBER compare field can explicitly keep or negate each source sign before comparison and tolerances; raw values stay unchanged. MatchDock does not silently reverse signs or infer a debit/credit mapping from payee text.
A bank-only item or amount difference may warrant checking a fee or another adjustment. MatchDock detects presence and configured field differences; it does not detect or classify bank fees automatically, or generate the accounting entry.
Keep the remaining items for human review.
These are ways to review MatchDock's existing outcomes, not automatic accounting classifications. Timing, missing entries and possible fees are investigation questions, not new product labels.
Matched or within tolerance
The unique pair passes your configured comparisons, exactly or within an explicit tolerance. Review the rule and any accepted difference; this does not certify an accounting balance.
Amount or date differences
An identified pair fails a configured comparison. Review the raw values, normalized values and difference. When a date used in the key has no candidate within its window, the rows remain unmatched instead.
Only in bank export
Could be a fee, timing item, or missing ledger entry. The result reports presence; you decide the accounting treatment.
Only in ledger export
Could be an outstanding item or an export-scope difference. Investigate before clearing it.
Duplicate or ambiguous keys
Review repeated references and multiple possible candidates. MatchDock keeps them unresolved rather than picking the first transaction or pairing them by amount.
Invalid keys
A required key is empty or cannot be parsed under your selected rules. Correct the input or configuration and rerun; an invalid key is not proof that a transaction is missing.
Repeat the check daily, weekly or monthly.
For a recurring reconciliation, keep the source scope, key and comparison rules explicit. With Pro, save a workflow and use Run Again with fresh bank and ledger files. Review changed headers and mapping suggestions before confirming the configuration.
The Bank reconciliation template provides a starting point for shared transaction references and exact amount, date and currency comparisons. Confirm the mappings and prepare compatible sign conventions yourself, or explicitly choose per-source polarity in Rules for a signed NUMBER compare column. The template keeps signs unchanged by default. Saved workflows do not connect to a bank, fetch files, run on a schedule or reconcile in the background.
Check opening and closing balances separately.
Use your own bank statement and ledger control totals to check opening balance, period movements and closing balance outside MatchDock. Confirm the period, currency, signs and export completeness. Equal totals alone can hide missing or offsetting transactions.
MatchDock's row comparison does not calculate an opening-to-closing balance reconciliation or certify that the accounts balance. Its optional Client-ready financial summary reports selected eligible transaction amounts; duplicate and invalid-key rows are excluded, and the report discloses that scope. It is not an automatic balance control.
Keep the evidence for the next review.
Detailed local evidence
Download the detailed XLSX or Evidence Package from Results to retain the run's outcomes, original rows and effective rules. Free includes these local exports within its input limits; export format and browser-resource limits still apply.
Pro reports for a colleague or client
Professional reporting adds a summary XLSX and printable HTML. Client-ready mode adds a locally generated PDF, Report ID, optional financial summary and count charts. Reports summarize the whole run; bounded examples do not replace full evidence or an accounting review.
Local report profiles reuse presentation choices in this browser. They do not store transaction results or automate the next reconciliation. PDF report output does not mean MatchDock can read PDF bank statements.
Your spreadsheet contents stay in your browser.
MatchDock parses and reconciles your files locally. Spreadsheet contents are not uploaded to MatchDock servers, and Excel exports are generated in your browser.
Ready to review the exceptions?
Start with two Excel or CSV exports. Choose the records that should match, apply explicit rules, and keep uncertain outcomes visible.