Non-Check Matching

Bank Reconciliation > Matching > Types of Matches > Non-Check Matching

Non-Check Matching

Default: On

Possible Settings: On or Off

Attributes: Records are matched using using amount, site number, and that the records are within the data range

 
Transactions are grouped on the Bank and G/L by site. If site is not used, all sites are grouped into the default site group (0).

For each Bank record, the system looks for an equal amount on the G/L side. It then qualifies the record(s) by examining the business days (weekdays) between the two dates. See Adjusting the data range for information on modifying the range.
 
If multiple Bank transactions satisfy multiple general ledger transactions, both sides are matched sequentially in ascending date order.
 

Without matching on the group number, there is a possibility of a false positive match. For example, two deposits are made on the same day, one in the morning, one in the afternoon, each for $100. The bank clears one deposit (made in the morning) the next day, while the afternoon deposit clears two days later. Bank Reconciliation may cross match the deposits, as the general ledger deposit date was the same.
 
However, if the bank deposits were on sequential days the system would not cross match the records as the system would work with records in an ascending date order on both sets of data.

Exceptions Generated
 
Unmatched Bank records are marked either "Unrecorded bank deposits" (Exception #335) or "Unrecorded bank withdrawals" (Exception #340).
 
Unmatched general ledger records which decrease the account balance are marked as '"General ledger reduced, no bank entry" (Exception #230).

Unmatched general ledger records which increase the account balance are marked either "Deposits in Transit" (Exception #240) or "Missing Deposit" (Exception #220).  The exact exception generated depends on the date range.

Page url: http://www.treasurysoftware.com/TSHelp/index.html?br_matching_type_non_check_matching.htm