Bank inconsistenties in general (Beta)

Modified on Fri, 6 Nov at 11:38 AM

Disclaimer

All screenshots in the article were taken in the Dutch version of Nmbrs Accounting.


In the bank account overview, the Consistency check column uses an icon to indicate whether there is a discrepancy (bank inconsistency) between the bank files and the accounting records.


TIP!

Always have Nmbrs Accounting recalculate the inconsistency before you start searching. To do this, click on the red triangle with the exclamation point in the upper-left corner of the screen.



What is a bank inconsistency?

Nmbrs Accounting detects an inconsistency by comparing the balances from the most recently imported bank file with the balance in the corresponding GL account. If these do not match, a warning icon appears.


The software distinguishes between two types of inconsistencies:

  • Balance not verified: The bank does not include a beginning or ending balance in the file (often the case with certain CSV formats).

    Action
    Check the balance periodically using official (paper or PDF) daily statements. Contact your accountant if any transactions are missing.

  • Balance is incorrect: Nmbrs Accounting detects a gap in the numbering or dates; the calculated balance differs from the actual bank balance.

    Action
    Check which days are missing transactions and download or export this period again via online banking.



Access to Bank inconsistencies

To access:

  • click on the Bank icon in the navigation bar
  • click on Bank accounts
  • in the now-opened screen, click on the name of the relevant bank account
  • then open the Statements view.



Statements view




Meaning of colors

  • White: The opening and closing balances calculated by Nmbrs Accounting match exactly the balances provided by the bank.
  • Red: There is a reconciliation discrepancy:
    • The calculated opening balance does not match the closing balance of the preceding statement line,
    • OR
    • The calculated closing balance does not match the opening balance of the subsequent statement line.


ATTENTION!

Even if lines appear in red, there is no actual bank inconsistency as long as the final bank balance equals the Nmbrs Accounting closing balance. The point where the balances first diverge indicates the cause.


The columns Check opening balance from Nmbrs Accounting and Check closing balance from Nmbrs Accounting are visible only to users with the 'Back office' role.



Common causes of bank inconsistencies

A discrepancy in the bank balance is usually caused by:



How does Nmbrs Accounting identify bank inconsistencies?

Nmbrs Accounting compares the opening balance of a newly imported file with the closing balance of the previous file (and with the balance in the corresponding GL account):


If a file is missing (for example, from a specific week or day):

  • The opening balance of the newest file does not match the balance in the administration.
  • The transactions from the missing period are omitted, causing the calculated control ending balance to immediately deviate from the actual bank balance.
  • The lines in the 'Statements' view are marked in red starting from the missing date.


Important rules regarding import:

  • Statement lines that have already been imported are automatically ignored during a repeat import.
  • Nmbrs Accounting skips transactions from a date if transactions from that date have already been imported.
  • An opening and closing balance are shown for each day if transactions occurred on that day.
  • The date in the statement overview shows the date of the last closing balance in the imported bank file; the corresponding opening balance may be further back in time.
  • At the top of the screen, under 'Check closing balance from Nmbrs Accounting', you will always see the cumulative closing balance calculated by Nmbrs Accounting across all years, not just the balance for the selected display period.


MT940 files and balance verification

Nmbrs Accounting can only automatically validate balances if the bank files contain opening and closing balances (as in MT940 format).


Important record types in an MT940 file:

  • :25:12345789 (Bank account)
  • :28:10601/1 (Statement number, less important)
  • :60F:D250415EUR9272.67 (Opening balance as of April 15, 2025)
  • :61:2504160416D30,N192NONREF (Transaction line on April 16, 2025)
  • :62F:D250416EUR9621.23 (Ending balance on April 16, 2025).


ING and Triodos MT940 files

Typically contain one opening and one closing balance per file/period (regardless of the number of days for which entries were made).


Rabobank MT940 file (.swi)

Contains an opening and closing balance for each individual calendar day, even if there were no transactions on that day.



Identify discrepancies and duplicate lines (entries)

When the trial balance differs from the bank balance:

  1. Calculate the exact difference:
    Calculate the difference between the most recent bank closing balance and the most recent trial balance from Nmbrs Accounting.
  2. Search for the discrepancy:
    Use the search bar within the accounting system to immediately check whether there is an line with this specific amount.
  3. Check for rejected/duplicate lines:
    Click on the Bank icon in the navigation bar and then click on Electronic statements. In the now-opened screen, click on the Duplicate lines button.
    Check whether the missing transaction has been flagged as a duplicate here and restore it if necessary.


Quick verification procedure after each correction

After resolving an issue, always perform this standard routine:

  • Click on the red triangle with the exclamation mark in the upper-left corner of the screen to immediately recalculate the balance series.
  • In the Statements view, check whether the most recent line is highlighted in white.
  • Verify that the Check closing balance from Nmbrs Accounting matches the actual balance in the bank account.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article