Different files can contain the same bank movements. A monthly PDF may have a different name from Friday's CSV, yet both include the deposit received on the eighth. Recording them as separate events can overstate the book balance even when each individual import looks tidy. Prevention starts by establishing the period covered by each file and how it will be used.
Identical files, overlapping periods, and duplicate movements are different
An identical file retains its content even after being renamed. An overlapping period shares dates with another download but may contain additional activity. A duplicate movement represents one actual bank event twice. Distinguishing those situations helps you avoid deleting valid information because names look alike or assuming that a file detector has already checked every individual movement.
Check the account and currency too. Statements from an operating account and a reserve account can both cover August without duplicating each other. Two statements for the same account and currency deserve comparison when dates overlap. Maintain a simple file register recording the account, starting date, ending date, download date, and review status.
Hypothetical example: the monthly statement arrives later
A company imported a CSV for its colón account covering August 1 through 15 and recorded a CRC 120,000 customer receipt dated August 8. It later downloads a PDF covering August 1 through 31. The PDF contains that receipt as well as activity from August 16 onward. Uploading it does not establish that everything is new: the first half already has evidence in the system.
Recording the August 8 receipt again would show CRC 240,000 of receipts for a real CRC 120,000 deposit. The difference is not additional revenue or extra money sent by the customer. It comes from representing the evidence twice. This illustration assumes that references and the receipt advice confirm that both lines describe the same deposit.
The second half of the PDF still matters. Identify which lines are already represented and which are missing. If the bank offers a download for August 16 through 31, a nonoverlapping file may simplify review. Otherwise, retain the complete original and document your comparison. Do not silently edit the statement to remove activity without preserving an explanation someone else can verify.
Compare more than dates and amounts
Two CRC 25,000 purchases on the same day are not necessarily duplicates. Compare bank references, descriptions, movement direction, accounts, and receipts. A deposit and withdrawal of the same amount are not the same line either. If the bank supplies no useful reference, consult operational evidence and record why you retained or excluded a possible duplicate.
- Find the original file and its import before uploading again.
- Identify the dates shared with the new download.
- Compare references and movements rather than filenames alone.
- Check which lines already have postings or linked payments.
- Retain new activity and document each confirmed duplicate.
Xero's documentation explains that duplicate statement lines can cause the imported statement balance to differ from the actual bank balance. It treats matching dates and amounts as potential duplicates to investigate. That supports checking evidence, not automatically deleting every match. Xero's reports and screens should not be mistaken for Tario's interface.
Tario's checks do not replace movement review
Tario identifies identical files by checking their content. It also checks overlapping periods among open imports for the same account. Those controls address different issues: converting a PDF to CSV produces a different file, and a finalized import is no longer open. The absence of an upload block does not guarantee that every movement in the file is new.
When a duplicate warning appears, open the import it identifies. Check whether it was read, remains pending, or was posted. Resolve a correct open import before starting again. Renaming a file to get around a warning does not fix the underlying issue. For an overlap warning, inspect the detected dates and assigned account before deciding which file should retain the pending work.
Deleting an incorrect unposted import and reversing activity already recorded are not equivalent actions. Identify dependent records before either operation. Tario's bank flow supports leaving a movement out with a reason, including duplicate, without creating a new posting. Base that decision on the record representing the real event, rather than using it to clear an inconvenient pending line.
Verify the balance without concealing the error
Creating a CRC 120,000 expense to offset the example's second receipt could hide the symptom while distorting the history. Find the duplicated action and review its correction with the accounting owner. The appropriate procedure depends on whether the duplication is only an imported line, a newly created payment, or a link to an existing transaction.
File balance validation and bank reconciliation answer different questions. A PDF can be read correctly and still overlap a previous CSV. Compare the account balance at the same cutoff, retained movements, and explained outstanding items. Do not accept a difference merely because it matches a suspected duplicate amount. Locate the repeated evidence before deciding what needs correction.
Prepare the next download
Assign responsibility for each account's import calendar. Weekly statements may support monitoring while a monthly statement supports verification, but distinguish which file feeds new records and which provides supporting evidence. A list of reviewed periods helps a colleague avoid posting a download that another person processed during an absence. Keep that list accessible to the people handling the account.
At the end of the example, the August 8 deposit should appear once in recorded cash and once in its payment application. New activity from August 16 through 31 should remain supported. Record which file contained repeated evidence and how it was handled. The explanation should remain understandable later without relying on someone's memory of which download arrived first.