How to Reconcile SECU Statements

What you are checking against

A SECU statement typically opens with a per-account summary, then lists each account's transactions in date order with its own balances — members with only a share savings account may be statemented quarterly. The institution is based in Linthicum, Maryland; its statement archive is organized per account, newest period first.

Reconciliation fails in instructive ways, which is why it is worth doing before import rather than after. A difference the size of one transaction means a row is missing or doubled; twice a transaction means a sign flipped; a few cents means a digit was misread somewhere. The check on this page reports which pattern a statement fell into by naming the rows where the running balance breaks, so the hunt starts at the right row instead of the first page. The methodology page explains the arithmetic in full.

The SECU month-end reconciliation workflow

Prove the opening first. Before touching the month, confirm its opening balance equals last month's proven closing balance. If it does not, the problem is behind you, not in this month.
Convert with the check on. Run the month's PDF through the converter and take the reconciliation result seriously: reconciled, flagged or unverified are three different instructions.
Fix flagged rows at the source. Correct flagged rows against the statement PDF itself. Never adjust the books to match an unproven file.
Reconcile the software to the statement. Import the verified file and run the software's own reconciliation against the same closing balance and closing date.
Lock the month. Once both checks agree, the month is solid ground. Record it, and let next month build on it.

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

Reading one SECU statement closely

Reconciliation goes faster when you know the document's habits. On a SECU 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 Statements and Documents in SECU online banking (website and app), the bank's own record of the month.

When a SECU statement does not tie out

A page-header or section-total line was read as a transaction — the converter guards against this, and any survivor shows up as a row whose own balance breaks the walk.
The PDF is a scan and OCR misread a digit. The flagged rows name the expected and printed balances; correct those rows against the image.
An interest credit or cashback posting lands on the closing date, after the last transaction row in some layouts — present on the statement, easy to miss in a manual total.
Two accounts' statements were converted into one file — the numbers for the second account read as unexplained differences in the first. Separate the documents and check each against its own balances.

What to hand over at year end

A clean year-end handoff is boring in the best way: the twelve statement PDFs, the twelve converted files with their reconciliation results, and a short list of the items still outstanding at the final closing date. With that package an accountant or a successor bookkeeper can re-perform any month in minutes. The habit that creates it costs nothing — save the conversion result with the statement, every month, while the work is fresh.

Questions and answers

Which balances does a SECU statement print?

Deposit statements print an opening and closing balance, and most print a running balance per transaction. Card statements print Previous and New Balances instead. The reconciliation check uses whichever the statement provides; a statement with no balances at all is reported as unverified.

Does reconciling in QuickBooks or Xero replace the conversion check?

They check different things. The conversion check proves the file matches the statement; the software reconciliation proves the books match the file. Doing both, in that order, is what makes a month solid.

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.

The difference is double a transaction's amount. What does that tell me?

A sign error: the transaction was read as money in when it was money out, or the reverse. The totals move by twice the amount because the correction has to both remove the wrong entry and add the right one.

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.