How to Reconcile Bank of New York Mellon Statements

Drag & drop statement PDFs hereor tap to choose files — multiple PDFs for batch mode

Privacy: uploaded files and generated exports are stored only briefly to complete your download and are automatically deleted within 15 minutes. Files are never used for any other purpose.

What you are checking against

Bank of New York Mellon statements typically separate activity into sections — deposits, withdrawals, fees — ahead of a daily balance summary on many account types. Headquartered in New York, New York, Bank of New York Mellon issues every account's statements through the same online banking platform.

Bookkeepers sometimes describe the statement as the referee, and the metaphor earns its keep: the bank's record is the one both the books and the conversion must satisfy. A converted file is therefore reconciled twice in a healthy workflow — once against the statement at conversion, and once inside the accounting software when the month is closed. Skipping the first reconciliation does not save the work; it moves the hunt for errors into the tool least able to localize them. The full method is documented on the methodology page.

The Bank of New York Mellon month-end reconciliation workflow

Anchor the month at both ends. Write down the statement's opening and closing balances before anything is imported. Those two numbers are the month's contract; everything else is fulfilment.
Convert and take the result at face value. A reconciled result means the file reproduces the statement. A flagged result names its rows. An unverified result means the statement offered no balances — in that case, total the file yourself before trusting it.
Clear flags while the PDF is open. Flagged rows are resolved against the statement image or text in front of you, in minutes, while context is fresh — not reconstructed weeks later.
Reconcile in the accounting software. Import the proven file and reconcile the account to the same closing balance and date. Any difference now lives in the books, and the short list of outstanding items should explain it.
Initial the chain. Note that this month's closing equals next month's opening. That single habit converts a year-end mystery into twelve small certainties.

These are the general steps most banks follow for statement downloads; exact menu labels vary by bank and change over time.

Reading one Bank of New York Mellon statement closely

Reconciliation goes faster when you know the document's habits. On a Bank of New York Mellon statement, check where fees and interest sit — inside the chronological flow or in a closing section of their own — because that is where unrecorded items hide. Confirm the statement's closing date matches the period you think you are closing; cycle dates drift from calendar months. And keep the source straight: reconcile against the statement filed under eStatements in the Bank of New York Mellon website and mobile app, the bank's own record of the month.

When a Bank of New York Mellon statement does not tie out

Two transactions with the same amount were collapsed or one was duplicated — compare the row count in the flagged region against the PDF.
A fee or interest line sits in its own section of the statement and was easy to overlook when eyeballing the total — it is a real row and belongs in the books.
The account had a mid-period product change or merger conversion, and the statement covers two layout eras. Convert it in two parts if the columns visibly change mid-document.
The statement period straddles a bank holiday weekend and the bank grouped several days of card activity under one posting date — the rows are all present, but their order differs from the software's expectation.

Reconciling when the books were kept by someone else

Inherited books deserve a colder eye: trust nothing that is not tied to a statement. Start at the most recent statement and work backwards only as far as the engagement requires, proving each month against its own document before accepting its closing balance as the next month's ground. Where a predecessor forced a reconciliation to agree, the plug usually sits in an adjustments or suspense entry — find those first, because every honest month built on a plugged balance inherits the error.

Questions and answers

The difference is exactly one transaction's amount. Where is it?

Either that transaction is missing from the file or it is in twice. Search the converted file for the amount: zero hits means a dropped row, two hits where the statement shows one means a duplicate.

Can I reconcile from a scan?

Yes — scanned statements convert through OCR and go through the identical checks. Because OCR can misread digits, treat flagged rows on scans with extra care and always resolve them against the image.

The difference is a few cents. Is that worth chasing?

Yes. Small differences are usually misread digits or rounding on a split transaction, and they compound silently if waved through. A reconciliation that tolerates cents teaches the whole file to drift.

Can I reconcile a quarter at once instead of monthly?

You can import in batches, but prove the months individually and in order. Three months reconciled as one blob hides which month owns a difference; the chain check needs each month's closing balance separately.

My software balance and the statement agree, but I never reconciled. Am I fine?

Not necessarily — two errors can cancel. Agreement of balances is a hint, not a proof; the proof is the transaction-level comparison a reconciliation performs. Convert and check the statements to be sure.