Variances occur when there is a discrepancy between the bank balance in the ledger and the balance on the bank statement.
Note: Bank Balance on the Smart Matching screen
Please note that the SF360 Bank Balance shown on the Smart Matching screen includes all transactions related to that bank account regardless of date. This includes transactions in a future financial year.
To review this balance, click the icon to generate a bank statement including transactions up to today's date.
If the balance still doesn't reconcile, review if there are any transactions posted after today's date.
If you are experiencing a variance in the bank balance, please first review the below questions:
Are you missing any transactions?
If a data feed is in use, you can attempt a re-request for the period where transactions may be missing. This can solve the Bank Balance variance:
Some banks do not support historical data. Please see Supported Banks for more information.
Have you entered "Do not import data before/after" dates?
Entering these dates into the data feed options will prevent data from feeding through, potentially leading to a gap in transaction data:
Have you created entries?
Data will not import for a period when entries have been created, potentially causing missing transactions leading to bank balance variance.
Should the balance variance persist, please see the guide below for troubleshooting purposes.
Skip to the next question in order if the answer is No:
- Has the ESI previously expired? If so, Request new ESI credentials to reactivate the feed.
- With an active ESI, re-requesting the transactions from the missing period should bring through any missing transactions (and resolve the variance). Please allow up to 24 hours for data to come through.
- Data will only feed into accounts with the correct BSB and account number. As a result, you will need to update the account details on the affected account(s) and contact the Data Services Team (email@example.com) to have the status updated in order for the feed to start again.
The Bank Statement Report should assist in locating when the variance began to occur. Once you have identified this, you will be able to troubleshoot further.
Similarly, a General Ledger Report (particularly audit view) may assist in identifying the source of any transaction that may be causing the error.
Determine if all transactions have been received during the period where the variance occurs. If there are transactions missing for a period where data should be available, please identify this missing period.
Duplicate transactions may cause a variance in the balance. With the assistance of the above reports, ensure that there are no duplicate transactions within the account that may be causing this error.
Please be sure to remove all duplicate transactions.
Please get in touch by Logging a Support Call, and include as much information as you can regarding the variance. A consultant will be in contact with you shortly.