DocuClipper logo
Docs
Bank Statements

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.

Last updated

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 it from there to date every transaction.

When the statement period isn't printed in a form DocuClipper recognizes (faded scan, unusual layout, missing cover page), it takes the year from the next best place on the document, in this order:

  1. the statement date or closing date,
  2. a year printed elsewhere on the statement, outside the transaction table,
  3. the file name, for example Statement - July 2024.pdf.

A statement never ends after the day you uploaded it, so a year that would put it in the future is not used.

"Year not printed on this statement - check the dates"

Some statements, often card statements and phone photos of a single page, show only the day and month and carry no year anywhere. DocuClipper then uses the most recent year that keeps the statement out of the future, and shows this note above the balances:

The yellow note "Year not printed on this statement - check the dates" directly above the From and To dates of the summary strip

Check the dates against the statement. If the year is wrong, fix it as described below. The note goes away once you set the period's Start Date or End Date.

Fixing it

You don't have to edit every transaction. Correct the statement's Start Date and End Date once and the year propagates to every transaction row automatically.

  1. Open the converted job. Above the transactions table is a summary strip showing Start Date, Start Balance, End Date, and End Balance for the selected account and period. A wrong year is often flagged with a red Bad year warning.
  2. Click the Start Date value to edit it inline. Enter the correct date in YYYY-MM-DD format and press Enter.
  3. Do the same for the End Date.
  4. DocuClipper re-derives the year for every transaction in that period and refreshes the table.

The Start Date must be on or before the End Date. A date that would make the period end before it starts is not saved, and DocuClipper tells you why. When you move a period into a different year, change the date that keeps the period in order first: the Start Date when moving it earlier, the End Date when moving it later.

The summary strip with editable From (Start Date) and To (End Date) fields

Multiple statements in one job

If you converted statements across multiple accounts or periods in the same job:

  • Use the Account and Period dropdowns above the table to switch between them.
  • Fix the Start Date and End Date on each account and period 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.