Guides & Resources
College Month-End Bank Reconciliation Checklist
College Month-End Bank Reconciliation Checklist
A college bank reconciliation should do more than confirm that two balances can be made to agree.
The process should establish that the complete population of transactions has been reviewed, differences have been explained, adjustments have been recorded, and unresolved items have been assigned for follow-up.
A standard checklist helps finance teams complete this work consistently across periods, accounts, and employees.
The following checklist can be adapted to the institution’s ERP, bank accounts, staffing structure, and close timetable.
1. Confirm the reconciliation scope
Before collecting any files, define exactly what is being reconciled.
- Confirm the legal entity or institution
- Confirm the bank account
- Confirm the general ledger account
- Confirm the reconciliation start date
- Confirm the reconciliation end date
- Confirm the opening book balance
- Confirm the opening bank balance
- Identify the preparer
- Identify the reviewer
- Confirm the expected completion date
The same scope should be used consistently across the ERP export, bank statement, and supporting records.
2. Obtain the source files
Collect the files required to support the complete reconciliation.
- ERP or general ledger transaction export
- Bank statement
- Bank transaction export
- Check register
- Deposit register
- Prior-period outstanding-check list
- Prior-period deposit-in-transit list
- Payment processor settlement files, where applicable
- Records of transfers between bank accounts
- Supporting schedules for expected adjustments
- Prior-period approved reconciliation
Retain the original source files separately from any cleaned or reformatted versions.
3. Validate the completeness of the data
Before matching individual transactions, confirm that the datasets are complete.
ERP data
- Confirm that the export covers the correct account
- Confirm that the export covers the complete period
- Confirm that opening and closing parameters are correct
- Confirm that no required transaction types were excluded
- Confirm that the total agrees with the relevant ERP report
- Record the date and time the export was generated
Bank data
- Confirm that the statement belongs to the correct account
- Confirm that the opening balance agrees with the prior statement
- Confirm that the closing balance agrees with the official statement
- Confirm that all statement pages are present
- Confirm that the transaction export covers the full statement period
- Confirm that pending transactions are treated consistently
- Record the date the bank file was downloaded
A reconciliation performed on an incomplete population may appear balanced while still omitting relevant transactions.
4. Standardize the transaction data
The ERP and bank may represent the same transaction differently.
Complete the required preparation before applying matching rules.
- Convert dates into a consistent format
- Standardize debit and credit signs
- Separate debit and credit values where necessary
- Remove unnecessary spaces
- Standardize check numbers
- Resolve leading-zero differences
- Standardize reference-number formatting
- Confirm that amount columns are numeric
- Identify blank or invalid values
- Retain the original source-row reference
- Preserve the original transaction description
- Identify duplicate source records
Do not overwrite the original source values. Any cleaned field should remain traceable to the source record.
5. Load prior-period outstanding items
Unresolved items from the previous period should be included in the current reconciliation.
- Load prior-period outstanding checks
- Load prior-period deposits in transit
- Load unresolved bank adjustments
- Retain the original transaction date
- Retain the original amount
- Retain prior comments and supporting references
- Confirm whether each item cleared during the current period
- Calculate the age of each remaining item
- Escalate items exceeding the institution’s review threshold
Older outstanding items should not be carried forward automatically without review.
6. Perform high-confidence matching
Begin with rules that produce clear and reliable matches.
- Match by check number and amount
- Match by transaction reference and amount
- Match by document number and amount
- Match by exact amount and date
- Match known transfers between accounts
- Match recurring bank transactions
- Confirm that the same transaction was not used in more than one match
Record the rule responsible for each match.
This makes it easier for the preparer and reviewer to understand how the matched population was generated.
7. Perform tolerance-based matching
Some valid transactions may contain processing-date differences.
- Define the approved date tolerance
- Identify transactions with equal amounts within the tolerance
- Review duplicate amounts before confirming a match
- Consider transaction type and description
- Record the reason for accepting the match
- Avoid using broad tolerances that create ambiguous results
An amount match alone may not be sufficient where several transactions carry the same value.
8. Review grouped transactions
Colleges may record transactions individually while the bank reports a consolidated deposit or settlement.
- Identify deposits containing multiple receipts
- Group records by batch, settlement, date, or payment channel
- Compare the grouped total with the bank transaction
- Confirm that all group components belong to the same settlement
- Identify fees deducted from net settlements
- Retain visibility into every transaction included in the group
- Confirm that group members were not matched elsewhere
The completed reconciliation should show both the combined result and the individual transactions that produced it.
9. Classify unmatched bank transactions
Review transactions appearing in the bank file without a corresponding ERP record.
Possible classifications include:
- Bank service charge
- Interest income
- Wire fee
- Returned payment
- Direct debit
- Automatic payment
- Unrecorded deposit
- Transfer
- Duplicate bank entry
- Transaction belonging to another account
- Transaction requiring investigation
For each item:
- Assign an owner
- Record the required action
- Attach or reference supporting evidence
- Determine whether an accounting entry is needed
- Establish a target resolution date
10. Classify unmatched ERP transactions
Review transactions recorded in the ERP but absent from the current bank file.
Possible classifications include:
- Outstanding check
- Deposit in transit
- Future-dated payment
- Voided transaction
- Reversed transaction
- Duplicate ERP posting
- Incorrect bank account
- Incorrect transaction date
- Incorrect amount
- Transaction requiring investigation
Confirm whether the item cleared immediately after period-end before finalizing its classification.
11. Review outstanding checks
Outstanding checks require additional attention because some will remain unresolved across several periods.
- Confirm the check was validly issued
- Confirm the payee
- Confirm the issue date
- Confirm the amount
- Confirm that the check has not cleared
- Check whether the payment was voided
- Check whether a replacement was issued
- Check for duplicate recording
- Determine whether follow-up with the payee is required
- Escalate stale checks according to institutional policy
- Retain the item for the next period only when appropriate
Do not remove an old check merely to simplify the reconciliation.
Its resolution should be supported and documented.
12. Record accounting adjustments
Identify all items requiring entries in the institution’s financial system.
- Bank fees
- Interest income
- Returned payments
- Recording errors
- Duplicate entries
- Incorrect amounts
- Incorrect accounts
- Missing deposits
- Transfer corrections
- Other bank-originated activity
For every adjustment:
- Record the proposed entry
- Obtain the required approval
- Post the entry
- Record the journal or document number
- Confirm that the adjustment appears in the ERP
- Retain supporting documentation
13. Confirm the reconciliation totals
Calculate and verify the adjusted balances.
Bank side
- Begin with the bank statement closing balance
- Add deposits in transit
- Subtract outstanding checks
- Include other supported reconciling items
- Calculate the adjusted bank balance
Book side
-
Begin with the ERP or general ledger closing balance
-
Add unrecorded bank credits
-
Subtract unrecorded bank debits
-
Include posted corrections
-
Calculate the adjusted book balance
-
Confirm that the adjusted bank and book balances agree
-
Investigate any remaining difference
-
Do not use unsupported balancing entries
14. Prepare the reconciliation package
The completed package should allow another person to understand the process without reconstructing it from scratch.
Include:
- Reconciliation summary
- Bank statement
- ERP report
- Detailed matched transactions
- Outstanding checks
- Deposits in transit
- Unmatched bank transactions
- Unmatched ERP transactions
- Adjustment details
- Journal-entry references
- Supporting documentation
- Preparatory notes
- Evidence of completion
15. Complete the reviewer checklist
The reviewer should independently evaluate the reconciliation.
- Confirm that the correct account and period were used
- Confirm the completeness of the source files
- Review the matching methodology
- Review material or unusual transactions
- Review manual matches
- Review grouped matches
- Review outstanding checks
- Review older unresolved items
- Review all proposed adjustments
- Confirm that required entries were posted
- Confirm that adjusted balances agree
- Confirm that supporting evidence is available
- Record review comments
- Sign and date the completed reconciliation
Preparation and review should remain distinguishable even when the institution uses reconciliation software.
16. Archive and prepare for the next period
After approval:
- Store the final reconciliation in the designated location
- Restrict or control later edits
- Retain the source files
- Retain the approved report
- Carry forward valid outstanding items
- Preserve comments and original dates
- Track open actions separately
- Record recurring issues for process improvement
- Confirm the next reconciliation deadline
Automating the checklist with Cointab
Cointab helps colleges convert recurring reconciliation steps into a structured, reusable process.
The finance team can use Cointab to:
- Upload ERP and bank files
- Validate and prepare transaction data
- Apply multiple matching rules
- Reconcile checks and deposits
- Process grouped transactions
- Retain prior-period outstanding items
- Review unmatched records
- Use AI-assisted matching for complex exceptions
- Download detailed reconciliation reports
This allows employees to spend less time searching through spreadsheets and more time reviewing unresolved transactions and strengthening financial controls.
Contact Cointab to discuss automating a college bank reconciliation workflow.
