The Solution Bridge Blog
Sage Accounting Canada: check the covered dates before importing another statement
Compare the proposed statement period with existing imports and bank-feed activity before adding another transaction file.
Applies to: Sage Accounting cloud, Canada, browser workflow. Not Sage 50; account-type and currency limitations follow the Canadian product documentation.
Uploading another statement can feel like a quick way to fill a gap. It can also introduce overlapping transactions if part of that period already arrived through a file or a bank feed. Establish what is already present before importing again.
Sage Canada’s bank-import FAQ describes statement uploads and connected feeds, including matching imports to existing records. It identifies supported account types and says foreign-currency bank accounts cannot use this import. Match the guide to Sage Accounting Canada rather than Sage 50.
Keep a coverage log
- Identify the intended bank account and its currency.
- Record the proposed file’s start date, end date and source filename.
- List the dates already covered by completed imports and feed activity.
- Identify any partially processed batch before starting another one.
- Compare overlapping items using date, amount and reference.
- Record the accepted batch and any unresolved exceptions after review.
The log is a review aid, not a substitute for the account’s transaction history. A date range alone cannot prove that every item within it exists or that two similar payments are duplicates.
A simple overlap example
Suppose a completed import covers September 1–20 and a new export covers September 15–30. September 15–20 is an overlap to investigate; September 21–30 is the later period to compare with any feed activity. The reviewer checks the actual items before deciding which entries need to be matched or added.
Do not discard a transaction solely because its date falls in the overlap. Two legitimate payments can share a date and amount. Retain the reference and evidence supporting the decision.
Handle unfinished imports first
Sage’s Bank Feeds setup guidance says to finish a partially processed statement import before connecting feeds to avoid duplicates. Keep a record of where the existing batch stopped rather than beginning a replacement without checking it.
Our cloud accounting and bookkeeping service can help organize this import coverage and reconciliation review.
Import-overlap questions
Does the same date and amount prove a duplicate?
No. Compare references and the underlying transaction evidence.
Should I re-upload the whole month to fill one gap?
First identify the missing item and what is already processed.
Can these steps be assumed to apply to Sage 50?
No. Use the documentation for the actual product and country edition.
Prepared by The Solution Bridge. Sources checked 2026-10-09. Educational guidance; verify current product instructions and applicable requirements.
Useful answers
Sage One / Sage Accounting FAQs
Is Sage One the same name everywhere?
Sage has renamed Sage One in several markets. Check your regional product page and current subscription name before choosing instructions.
Can I use Sage 50 steps for Sage Accounting?
Only if the vendor explicitly says they apply. Different Sage products have different interfaces and troubleshooting procedures.
What should I include in a Sage enquiry?
Provide the product, country edition, affected task and exact message. Include where the workflow stopped, without credentials or customer data.
Talk to The Solution Bridge
Let’s make your next step clearer
Tell us what you need help with. For software enquiries, include the product, version and exact message. Please leave out passwords, tax identifiers and financial documents.