How to Reconcile First National Bank of Pennsylvania Statements

What you are checking against

First National Bank of Pennsylvania statements typically list transactions chronologically with a running balance on deposit accounts, and print opening and closing balances for the period. First National Bank of Pennsylvania (Hermitage, Pennsylvania) files its statements in the documents area of online banking, organized by account and closing date.

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 First National Bank of Pennsylvania 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 First National Bank of Pennsylvania statement closely

Start a First National Bank of Pennsylvania reconciliation by reading the statement's summary block — most layouts print one. It states the opening balance, totals for each activity type, and the closing balance, which gives you four numbers to aim at before any row is touched. If the converted file reproduces the summary totals, remaining differences are categorization questions, not reading errors. The document itself comes from eStatements in First National Bank of Pennsylvania online banking (website and app); reconcile only against that issued original, never against a re-export or a screenshot.

When a First National Bank of Pennsylvania statement does not tie out

A pending card transaction appears on one statement and posts on the next, so both statements are right and the import order is what needs care.
A transfer between two of the customer's own accounts was imported on one side only. Each account reconciles against its own statement; the pair of differences, equal and opposite, is the fingerprint.
A cheque image or money order fee was deducted inside the cheque's own line rather than as a separate row — the transaction count is right and the total is short by exactly that fee.
A mobile deposit was recorded in the books on the day it was made and posted by the bank two days later, landing in the next statement period — an honest timing difference that clears next month.

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

Can I reconcile several First National Bank of Pennsylvania accounts together?

Convert and check each account's statements separately — balances are per account — then reconcile each account in your software. Combined Excel exports keep one sheet per statement so accounts never blur.

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.

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.

What if two statements overlap or leave a gap at a product change?

When an account changes product, banks sometimes issue a short final statement for the old product and a first statement for the new one. Convert and prove both; the old one's closing balance should equal the new one's opening balance, and that handover is the seam to verify before anything else.

My First National Bank of Pennsylvania statement shows a running balance but my software disagrees mid-month while agreeing at the end. Problem?

Usually not an error: running balances depend on the order transactions are walked, and the software may order same-day items differently from the bank. Agreement at the closing balance with every transaction present is the substance; mid-month ordering differences on the same posting date are cosmetic.