Correcting the Year on Transactions
Bank statements often omit the year on transaction rows. Here's how DocuClipper infers the year and how to fix it when the inference is wrong.
Why the year can be wrong
Most bank statements print dates like 03/15 on each transaction row. The year only appears once, at the top of the statement or in the period range, and DocuClipper reads the period to determine the year for every transaction.
If the period isn't recognized (faded scan, unusual layout, missing cover page), DocuClipper falls back to the current year, which often isn't right, especially for statements from prior tax years.
Fixing it
You don't have to edit every transaction. Fix the statement's period once and the year propagates automatically.
- Open the converted job and look at the summary pane at the top of the transactions view.
- Find the Period or Date Range field; it shows the inferred start and end dates.
- Click the edit icon next to the period.
- Correct the year (and month/day if needed) and click Save.
Every transaction row updates to the correct year automatically.
Multiple statements in one job
If you converted statements across multiple accounts or periods in the same job:
- Use the Account / Period selector at the top of the grid to switch between them.
- Fix the period on each one independently.
Editing individual transactions
If only a handful of transactions have the wrong year (e.g. December transactions that belong to the previous year on a January statement), click the date cell on each row and edit the year directly. Changes save automatically.