Messages Reconciliation can show

That reconciliation is not in the books.

That account is not in this chart of accounts.

Account {code} is not an asset account. A reconciliation compares a bank or cash account against a statement, and there is no statement for anything else.

This statement would end on {end}, before it starts on {start}. Check the two dates.

Type the closing balance from the statement. It is not assumed to be zero, because zero is a real balance and the difference would then be measured against nothing.

Say what the statement line is. A line with no description cannot be checked back against the statement.

A statement line needs an amount and it cannot be zero. Use a negative amount for money leaving the account.

That entry is not on this reconciliation’s account, so this bank statement has nothing to say about it.

That entry is dated {date}, after this statement ends on {statementEnd}. The bank cannot have seen it yet.

That entry has already been ticked off, here or on an earlier reconciliation. An entry clears once — otherwise the same money counts as cleared in two months and both would appear to balance.

That entry is not ticked off on this reconciliation, so there is nothing to undo.

This reconciliation has been completed, so its ticks and statement lines can no longer be changed. Start a new one for the next statement.

There is nothing in that file. Export the statement again from your bank and upload it.

That file is larger than {megabytes} MB, which is more than a statement should be. Export a shorter period and upload it a period at a time.

This is not a bank statement this product can read. SISC reads MT940, camt.053, and a CSV export once you have told it how that bank lays its columns out. A PDF cannot be imported at all: there is nothing in one a program can check.

One line of that statement, {length} characters long, is not in a shape this product can read — so nothing at all was imported. Importing the rest would leave your sheet missing a movement with no way to see which one.

These books are kept in {expected} and that statement is in {found}. It was refused rather than converted: a rate nobody chose is not something to put into a reconciliation.

The statement states {amount}, which is finer than the {precision} decimal places your currency carries. It was refused rather than rounded — a rounded figure no longer agrees with the paper the bank sent you.

That statement does not add up: it opens at {opening}, its lines move {movement}, and it says it closes at {closing}. Nothing was imported. Either the file is incomplete or it is not the export your bank intended.

That file holds statements for more than one bank account, so it is not one statement. Export each account on its own.

Page {page} of that statement opens at {found} where the page before it closed at {expected}, so a page is missing between them. Nothing was imported: the pages you do have would leave a hole that ties against nothing.

Account {code} does not say which bank account it is, so a statement cannot be checked against it. Set its bank account number on the chart of accounts first. It is not guessed, even when there is only one bank account.

That statement is for a different bank account from the one account {code} names. Nothing was imported — importing another account's statement here would reconcile this account against a bank that never mentioned it.

This sheet says the bank closed at {sheet} and that statement closes at {file}. Nothing was imported. A statement that ends on this sheet's last day and closes at a different figure is a different statement, and importing it would reconcile the wrong month.

That statement reaches {date}, outside this sheet's period of {start} to {end}. Nothing was imported: a movement this sheet cannot tick off would sit in the difference for ever.

Account {code} has no CSV layout saved, so a spreadsheet statement cannot be read for it. Set the columns up once for this bank and they are remembered. The layout is never guessed: the same date can mean two different months, and only you know which one your bank means.

This layout needs the {field} column and it is not set. Without it every line of the statement would be read wrongly, so nothing was imported.

{value} is not something this product accepts for {field}. Choose one of the options offered — a layout it cannot read is a layout it reads wrongly.

This file is not a bank statement this product can read. SISC reads MT940, camt.053, and a CSV export whose columns you have set up. The kind of file is decided from what is inside it, never from its name.

That file holds no transactions. The usual reason is that the layout skips more header rows than the file actually has — check the number of header rows and upload it again.

Row {row} does not fit this layout: its {field} could not be read. Nothing at all was imported — importing the rest would leave your sheet missing a movement with no way to see which one.

This server cannot store the statement file securely, so nothing was imported. A bank statement is kept encrypted here like every other file, and this product will neither import one without keeping it nor keep one unencrypted. Ask your administrator to finish the security setup.

This server cannot read XML, so a camt.053 statement cannot be imported on it. Ask your administrator to enable the XML extension, or ask your bank for the MT940 export instead.

That XML file declares a document type or an entity, and was refused without being read. A bank statement has no reason to carry one, and a file that does is not treated as a statement.

That statement line is not on this reconciliation.

That statement line has already been matched to an entry. Undo the match first if it was the wrong one.

The bank says {statement} and that entry says {book}, a difference of {difference}. They are not the same movement, so they were not matched. If the gap is a bank charge, it is a separate line on the statement — explain that line and the entry for it is created.

That entry can no longer be matched here: it has been ticked off, it now answers another statement line, or it is not on this account. Reload the suggestions and choose again.

That statement line is not matched to anything, so there is nothing to undo.

Say which account this movement belongs to. It is never chosen for you: a bank charge posted to a holding account is a cost nobody finds again.

The other side of this entry cannot be account {code} — that is the bank account this reconciliation is about. An entry with both sides on one account moves nothing, and the difference you are chasing would not change.