Most Common Fixes

• When Opening the Payment Reconciliation Journal, a Warning Appeared That Balances Do Not Match
• New Transactions Have Not Arrived/Transactions Are Missing
• Bank Statements Were Imported Incorrectly, Now There Are Duplicate Transactions in the System
• Transactions Are in the Payment Reconciliation Journal, but They Are Unapplied
• High Transactions Are in the Payment Reconciliation Journal, but Automatic Posting Is in Use

When Opening the Payment Reconciliation Journal, a Warning Appeared That Balances Do Not Match

The warning compares two values: the specific Bank Account’s “Balance in Bank” field and the ending balance in the last XML statement. The “Balance in Bank” field is a calculated field in Business Central that adds and subtracts transaction amounts as they are entered into the system. If a transaction has been skipped through the bank connection, this also means that this balance will be calculated incorrectly.

You need to identify from what date the transaction is missing. To do this, you must compare the internet bank and Business Central’s Bank Accounts list in parallel.

In the Bank Accounts list, open the Filter pane. Then “Filter totals by”, select “Date Filter” and set a date there. Open the same date in the internet bank and compare whether “Balance in Bank” and the internet bank’s ending balance match. This way you can identify the first day when the balances differed and find the missing transaction(s). Import the missing transaction(s) into the system again according to the following instructions.

New Transactions Have Not Arrived/Transactions Are Missing

• Check if all RTB Job Queue Entries are working. In order for automation to work in the future, job queues must be restored. In any case, let the consultant know if jobs have failed. Simply restarting the Job Queue Entry may not be enough for automation to start working again. You can also view the content of error messages under the Job Queue Log Entries.
  • If the bank-named job has stopped working
    • If the error code starts with 5 (500, 503, etc.), it means that the bank is not accepting requests. In most cases, this indicates either issues with their system or maintenance work.
    • It is also possible that the certificate has expired
  • If the “RTB - Process/Apply/Post” job has stopped working
    • The problem occurred after importing messages from the bank, either during processing, application, or posting. The consultant will help clarify the nature of the problem.
  • If job queues are working
    • Check on the Bank Account page transactions whether transactions are missing
    • The consultant will help clarify the nature of the problem.
• Are there new messages on the Incoming Bank Messages page?
  • If you go to the page and immediately see lines with date(s) that are missing from the system, it means that data has been received from the bank but has not been processed.
    • If they are red, there was an error processing the messages, error info is displayed in the info pane - contact the consultant if necessary
    • If the messages are in bold black text, they are unprocessed. For these, run the “Process” action and clear the filter field
  • If new messages from the respective dates are missing or you are not sure if something is missing…
• Load the missing transactions into the system. There are two options for this: the first is longer but works in any case. If you use the options below, no transactions will be loaded into the system twice, regardless of whether the transactions were already in the system before or not.
  • Manual payment file import
    • export the missing bank statements as XML in the internet bank
    • open the Incoming Bank Messages page in Business Central
    • “Import from File” action
    • add the XML statement
    • run the “Process” action
    • clear the filter field
    • OK
  • Payment file import via Swedbank bank connection
    • page Swedbank Gateway Setup
    • action “Request Account Statement”
    • select “Report Type” Previous Period
    • mark the period where transactions are (potentially) missing
      NB! if the current day i.e. today’s date falls within the period, a service fee of €0.50 applies
    • OK
    • action “Get New Bank Messages”
    • page Incoming Bank Messages
    • action “Process”
    • clear the filter field
    • OK
  • Payment file import via SEB bank connection (if missing transactions are within the last 21 days)
    • page SEB Baltic Gateway Setup
    • action “Get EOD Transactions”
    • mark the date with (potentially) missing transactions
      NB! must be done separately for each date
    • OK
    • page Incoming Bank Messages
    • action “Process”
    • clear the filter field
    • OK
• Now the transactions are in the Payment Reconciliation Journal and their “Match Confidence” is None

Bank Statements Were Imported Incorrectly, Now There Are Duplicate Transactions in the System

Incorrect import means directly into the Payment Reconciliation Journal - this must not be done.

If transactions were posted this way, now the same transactions have also come through Realtime Bank again into the Payment Reconciliation Journal - this means they can no longer be deleted. Definitely notify the consultant and assess the situation together.

One solution is to uninstall the app (while keeping the data), then delete the duplicate transactions from the Payment Reconciliation Journal, reinstall the app, and review user permissions.

Transactions Are in the Payment Reconciliation Journal, but They Are Unapplied

Therefore, an error occurred during automatic application of one or more transactions and the transactions were not applied.

• Filter for transactions whose “Match Confidence” is None.
• Select these lines
• Run the “Apply Selected…” action

High Transactions Are in the Payment Reconciliation Journal, but Automatic Posting Is in Use

Therefore, an error occurred during automatic posting of one or more transactions and the transactions were not posted. You need to find the transaction(s) that caused the problem, resolve them, and then post manually.