About Unmatched Transactions

Learn more

Transactions can be unmatched for any of the following reasons:

They are bank entries (such as fees, interest, NSF checks, or service charges) that you have not yet entered in Sage 300.
You have entered the transactions in Sage 300, but they have not yet cleared the bank. For example: A vendor has not yet cashed your check, so the payment is outstanding. Another example is the bank has not yet recorded a deposit to your account, so the deposit is considered outstanding.
There is a discrepancy between Sage 300 and your bank in the amount of the deposit or payment, or in the descriptive data used to identify the item. The discrepancy could be the result of a keying error (your error or the bank's error).
A discrepancy can also arise if you and the bank use different rates to convert foreign currency. This can result in an exchange rate spread larger than the difference permitted for the bank in Sage 300.
The bank used different descriptive information for a transaction than you used in your system.