Banking
How to Match Bank Transactions to Business Receipts
Reconcile statement rows with recorded expenses without duplicating purchases, hiding exceptions or mixing one Business with another.

Matching a bank transaction to a receipt is a completeness check. It confirms that the payment activity and the Business record describe the same event. It should not create a second expense or hide a transaction that still needs investigation.
Start with the correct Business and account
Choose the statement account that belongs to the Business you are reviewing. Confirm the currency and statement period before importing or entering rows.
Personal accounts may contain Business purchases, but they should not be treated as Business-owned bank accounts. Record personally paid expenses through the appropriate owner-paid workflow.
Compare the strongest matching fields
Look at:
- amount and currency;
- transaction date and posting date;
- supplier or payment description;
- payment method;
- receipt date;
- Business purpose; and
- refunds or reversals.
Dates and names may not match perfectly. A card purchase can post later, and a payment processor may use a different descriptor. Use several facts together instead of relying on one field.
Match—do not duplicate
If the expense already exists, connect the statement row to that record. Do not create a new expense merely because the bank transaction was imported.
Before creating a record from an unmatched transaction, search for possible duplicates using amount, date, supplier and attachment details.
Keep exceptions visible
Common exceptions include:
- a transaction with no receipt;
- a receipt with no matching payment;
- a transfer mistaken for income or expense;
- a refund with no original purchase;
- a split purchase covering several categories;
- a personal purchase on a Business account; and
- a Business purchase paid personally.
Record the known facts and assign a next action. Do not force a match to improve a progress percentage.
Reconcile in small batches
A practical routine is:
1. Import or enter one statement period.
2. Match obvious one-to-one transactions.
3. Review likely duplicates.
4. Investigate unmatched rows.
5. Attach or request missing evidence.
6. Record owner-paid or repayment relationships separately.
7. Review the remaining exceptions before closing the period.
Progress indicators can help you see what remains, but “100% reviewed” should mean every row has a documented outcome—not that every row became an expense.
Protect original evidence
Keep the original statement and receipt files private. Use authorized, short-lived access when sharing attachments, and avoid emailing sensitive documents unnecessarily.
The CRA’s recordkeeping guidance identifies bank statements, cancelled cheques, invoices and receipts as records that can support Business transactions. Retain clear, readable records for the required period and ask a professional when the evidence is unclear.
SilaTrail’s reconciliation workspace helps owners review statement rows and connect them to existing records while keeping unresolved items visible. It does not access your bank directly or make accounting decisions automatically.
See the CRA’s Business records and Keeping Records guidance for authoritative information.
Continue the workflow
- See SilaTrail’s bank-statement matching.
- Review the receipt-capture workflow.
- Resolve open items through monthly review.
