Check a blocked bank statement
When you import a bank statement, Profit compares the balance of the imported bank statement with the balance of the bank's ledger account. If the balances deviate, the following message appears: 'The opening balance in the file does not match the balance in the journal'. The bank statement is blocked. In the case of blocked bank statements, you can check the transaction file and the administration in order to determine why the bank balance differs. You then resolve the cause of the blocked bank statement, depending on the situation that is applicable.
After you have resolved the problem and the balance is correct, the message does not disappear, because it is only determined once. You can delete the bank statement and import it again if it is still available or wait for the next statement to see if the message has not come back.
Contents |
Check the balance
You check whether the balance of the bank statement differs from the balance of the bank journal.
To check the balance:
- Go to: Financial / Ledger / Journal.
- Open the properties of the bank journal.
- Go to the tab: General.
The Contra account field shows the ledger account of the bank journal.
- Go to the tab: Balances.
Check the closing balance of the last processed bank statement. If this balance does not match, then there have been some incorrect entries. Also check the balances of previous periods.
Manual entries
You check whether there are any manual entries that were not created by importing the transaction files.
Check for manual entries
- Go to: Financial / Ledger / Journal.
- Open the properties of the bank journal.
- Go to the tab: General.
The Contra account field shows the ledger account of the bank journal.
- Go to the tab: Entries.
Add a new view with the Source journal entry field.
The manual entries have the FIentry value. Check that the value of these entries matches the balance difference between the transaction file and the bank journal.
- Click on: OK.
Double import
You check whether a transaction file has been imported previously.
To check for a duplicate import:
- Go to: Financial / Enter / Bank statement
- Check whether the transaction file has been imported multiple times.
You may be importing a transaction file, whereas a colleague has already entered the statement manually.
- Delete the manual entries.
You can only delete bank statements that have the Blocked, Processed or Loaded status.
Note:
Deleting a bank statement does not delete all entries. Thus you have to delete the entries as well to avoid duplication.
Not processed
You check if there are any transaction files that have not yet been processed.
To check for files that have not been processed:
- Go to: Financial / Enter / Bank statement.
- Check whether there are any (interim) transaction files that have not been processed.
Previously imported transaction files may still have the Loaded or Current status. You must first process these transaction files.
- Process these files using one of the following methods:
- Click on the action: Process if you want to process the files.
- Click on the action: Set status to 'processed' if you no longer want to process these files.
Bank statement ID
You use the Bank statement ID field to check if the bank statements have been imported in the correct order.
To check the import sequence using Bank statement ID:
- Go to: Financial / Enter / Bank statement.
- Add a new view with the Bank statement ID field.
- In the view, use the Bank statement ID field to check if the bank statement files have been imported in the correct order.