---
title: "Reconcile an Imported Bank Statement"
canonical: "https://kb.myframeworks.com.au/space/CO/30515312/Reconcile%20an%20Imported%20Bank%20Statement"
format: markdown
---
Reconcile an imported bank statement by working through automated suggestions, manual matching, and adjustments in a systematic sequence.

> 📝 ## Prerequisites
> 📝 
> 📝 - Bank statement has been imported using [Import a Bank Statement](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/30530970) procedure.
> 📝 - Bank Statement Reconciliation screen is open with imported statement transactions displayed.
> 📝 - Feature code **BNK** (Electronic Banking) is active.
> 📝 - GL period is open for the statement date.

## The Reconciliation Workflow

1. Navigate to **General Ledger > Transaction Processing > Bank Reconciliation**.
2. Enter search criteria to find the bank statement you want to reconcile.
3. Click **Find** to open the **Bank Statement Reconciliation** screen.
4. Review the **Ledger Date**, to determine which GL transactions for the period are available for matching.
  1. The ledger date automatically aligns with the latest imported statement date, which is suitable for matching transactions within the month.
  2. For final month-end bank reconciliations, click **Show Date Chooser** and set the ledger date to the last day of the month.
  3. Enable the **Include Future GL** checkbox to show all GL transactions for the period regardless of statement or ledger date.
5. Resolve any duplicate transactions (if prompted).
6. Review the automated suggestions (Customer Payments, Supplier Refunds, GL Journals and GL Matches).
7. Manually match remaining transactions.
8. Create adjustments for unmatched statement transactions (if required).
9. Review your reconciled transactions.
10. Finalise the reconciliation.

---

## Resolve Duplicate Transactions

If you see a **Resolve Duplicate Transactions** notification below the header details, resolve duplicates before proceeding with matching.

### Steps

1. Click the **Import** icon to open the **Resolve Duplicate Transactions** window.
2. Review the duplicate transactions listed.
3. Enable the **Sel** checkbox for transactions to keep or remove.
4. Click **Accept** to keep selected transactions or **Delete** to remove them.

> ✅ Refer to [Resolve Duplicate Statement Transactions](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402358293) for detailed guidance.

---

## Review Automated Suggestions

Frameworks provides four types of automated matching suggestions. Review and post suggestions in this order for best results.

### 1. Suggested Matches

Frameworks suggests matches to **find existing GL transactions** that match statement entries. This is useful when GL transactions have already been entered in Frameworks but need to be matched to the bank statement.

### Steps - Suggested Matches

1. Click **Suggest Matches** to display a list of **Bank Statement** **Suggested Matches **with GL transactions.
2. Frameworks suggests matches based on matching amounts between statement entries and existing GL transactions in the system.
3. Review the suggested matches. Click the **Delete** icon to remove any suggestion you want to handle differently.
4. Click **Post Matches** to process all remaining suggestions and move them to the **Reconciled** tab.

### 2. Suggested Customer Payments

Frameworks suggests customer payments to **create new customer payment GL transactions** from statement entries. This is useful when customer payments appear on the bank statement but haven't been entered in Frameworks yet.

### Steps - Suggested Customer Payments

1. Click **Suggest Customer Payments** to review recommended customer payment matches.
2. Frameworks identifies statement entries (with positive amounts) that contain customer numbers or off-system banking (OSB) references in the description or reference field, and matches them against customers with outstanding balances.
3. Enable the **Sel** checkbox for suggested payments you want to create (or enable **Select All**).
4. Click **Create Payments** to create new customer payment GL transactions and move the matched statement and GL transactions to the **Reconciled** tab.

> ⚠️ **Important:** The newly created customer payments still need to be allocated to customer invoices. Refer to [Process Customer Payments](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/30516976) for allocation instructions.

### 3. Suggested Supplier Refunds 

Frameworks suggests supplier refunds to **create new supplier refund GL transactions** from statement entries. This creates a negative payment on the supplier account to take up any credit balance the supplier may have. This is useful when supplier refunds appear on the bank statement but haven't been entered in Frameworks yet.

### Steps - Suggested Supplier Refunds 

1. Click **Suggest Supplier Refunds** to review recommended supplier refund matches.
2. Frameworks identifies statement entries that match supplier refund patterns.
3. Enable the **Sel** checkbox for refunds you want to create.
4. Click **Create Refunds** to create new supplier refund GL transactions and move the matched statement and GL transactions to the **Reconciled** tab.

> ⚠️ **Important: **Suggested supplier refunds require bank statements imported using the MT940 format. Supplier references must be configured in **Bank Reconciliation Entity Maintenance** before suggestions will appear.

### 4. Suggested GL Journals

Frameworks suggests GL journals to **create new journal entry GL transactions** from statement entries. This is useful when bank fees, interest, or other adjustments appear on the bank statement but haven't been entered in Frameworks yet.

### Steps - Suggested GL Journals

1. Click **Suggest GL Journals** to review recommended journal entry matches.
2. Frameworks identifies statement entries that match common journal entry patterns (such as bank fees or interest).
3. Enable the **Sel** checkbox for journal entries you want to create.
4. Click **Create Journals** to create new journal entry GL transactions and move the matched statement and GL transactions to the **Reconciled** tab.

---

## Manually Match Remaining Transactions

For statement transactions not matched by automated suggestions, manually match them with GL transactions.

### Steps

1. In the **Statement** section under the **Unreconciled** tab, enable the **Sel** checkbox for the statement transaction you want to match.
2. In the **General Ledger Transactions** section, enable the **Sel** checkbox for the matching GL transaction.
3. Verify the **Selected** totals at the bottom of each section match exactly.
4. Click **Match** to move the matched transactions to the **Reconciled** tab.

> ℹ️ ### Matching Rules
> ℹ️ 
> ℹ️ - You can match one statement transaction to multiple GL transactions.
> ℹ️ - You can match multiple statement transactions to multiple GL transactions.
> ℹ️ - The selected statement total and GL transaction total must be equal to match.
> ℹ️ - Zero-dollar GL transactions can be matched to move them to the Reconciled tab.

> ❌ An error message displays if the selected totals do not match.

---

## Create Adjustments for Unmatched Items

For statement transactions with no corresponding GL transaction in Frameworks, create journal entries or customer payments.

### Create Journal Entries from a Bank Statement

For bank fees, interest, errors or other GL adjustments:

1. Click the **Journal Entry** icon for the unmatched statement transaction.
2. The **Bank Statement Journal Entry** window opens showing the statement transaction details.
3. Create the required journal entry to balance against the statement transaction.
4. Click **Post** to create the journal entry and move the transactions to the **Reconciled** tab.

> ✅ Refer to [https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403996675](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403996675) or [https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402685980](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402685980) for detailed steps.

### Create Customer Payments from a Bank Statement

For customer payments not picked up by automated suggestions:

1. Click the **Customer Payment** icon for the unmatched statement transaction.
2. The **Bank Statement Payment Entry** window opens showing the statement transaction details.
3. Enter the customer and payment amount (or import BPay/FatZebra files).
4. Click **Post** to create the customer payment and move the transactions to the **Reconciled** tab.

> ✅ Refer to [https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402980894](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402980894) or [https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403144715](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403144715) for detailed steps.

### Alternative Adjustment Methods

You can also use the **New Journal** or **New Payment** buttons to open the standard screens:

- **New Journal** - Opens a **Journal Entry window**. Create the journal entry, then manually match the resulting GL transaction. Useful for accrual journals.
- **New Payment** - Opens the standard **Customer Payments screen**. Create and allocate the payment, then manually match the resulting GL transaction.

> ✅ Refer to [Create a Journal Entry for Bank Reconciliation](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/401801224) for details steps on this alternative method.

---

## Review Reconciled Transactions

Before finalising the reconciliation, review all matched transactions to verify accuracy.

### Steps

1. Click the **Reconciled** tab.
2. Click **Load Matched** to display all reconciled transactions.
3. Review the matched statement and GL transactions.
4. If you find an incorrect match, enable the **Sel** checkbox for that match and click **Un-Match** to return it to the **Unreconciled** tab.

> ✅ **Tip:** Sort the **Reconciled** tab by the **Match#** column to group matched statement and GL transactions together. You will need to add the **Match#** column first if it is not already visible.

---

## Finalise the Reconciliation

Once all statement transactions are matched, finalise the reconciliation.

### Steps

1. Verify the **Difference** field in the header details shows $0.00.
2. Click **Reconcile** to finalise the bank reconciliation.
3. Confirm the reconciliation when prompted.

> ⚠️ **Warning:** Marking a reconciliation as reconciled cannot be reversed. If the statement date is not the end of the month, you will be reminded of this before confirmation.

## Result

The bank statement reconciliation status changes to **Reconciled**. All matched transactions are locked and cannot be unmatched. Unmatched GL transactions remain available for the next period's reconciliation. The reconciliation appears on the [Bank Reconciliation Dashboard](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28380822) with a status of **Reconciled**.

> ✅ ## Related Tasks
> ✅ 
> ✅ **Before this procedure:**
> ✅ 
> ✅ - [Import a Bank Statement](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/30530970)
> ✅ - [Bank Reconciliation - Overview](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/30529362)
> ✅ 
> ✅ **During this procedure:**
> ✅ 
> ✅ - [Resolve Duplicate Statement Transactions](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402358293)
> ✅ - [Create a Journal Entry from Bank Statement](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403996675)
> ✅ - [Create an Inter-Company Journal Entry from Bank Statement](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402685980)
> ✅ - [Create Customer Payments from Bank Statement](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/402980894)
> ✅ - [Import Payment Gateway Statements for Bank Reconciliation](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/403144715)
> ✅ - [Create a Journal Entry for Bank Reconciliation](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/401801224) (alternative method)
> ✅ 
> ✅ **After this procedure:**
> ✅ 
> ✅ - [Process Customer Payments](https://sterlandsupport.atlassian.net/wiki/spaces/CO/pages/30510956) (to allocate payments to invoices)

> ✅ ## Related Information
> ✅ 
> ✅ - [Bank Reconciliation Dashboard](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28380822) - Field Definitions
> ✅ - [Bank Statement Reconciliation Screen](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28380810) - Field Definitions
> ✅ - [Electronic Bank Reconciliation - Setup and Configuration](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28408698)

---

> ⚠️ ## Additional Notes
> ⚠️ 
> ⚠️ **BPay and FatZebra imports:** When using the **Bank Statement Payment Entry** window (Customer Payment icon), you can import BPay (.brf) or FatZebra (.csv) files. BPay imports are available for ANZ and NAB .brf files. Commonwealth Bank BPay details must be imported using the Commonwealth Bank (CSV) file format when importing the bank statement.
> ⚠️ 
> ⚠️ **Print reconciliation:** Click **Print Reconciliation** at any time to output a document showing all unreconciled statement and GL transactions for review.