Cash Book for Bank Reconcilliation

Looking for information on using the CB suite of apps to reconcile bank statements, particularly for stale dated checks and escheatment.

We currently reconcile our checks in a MS Access Database which is proving to be a bit less reliable as we go through the MS Office 2016 migration.

Was reading through the CB User Guide and it seems quite the complicated process.

So, what do you use for bank reconciliation?

Infor Nexus Managed Services Offerings (1).pdf

Find more posts tagged with

Infor Lawson Financials Group - Discussion

Comments

unknown

We don't use CB for the "full" bank reconciliation, but we definitely mark the checks cleared and obtain our outstanding check list via CB. This is useful for users outside of GL as well, as they can easily see via drill-around when an invoice was paid and whether or not the check cleared the bank. I have a test script that I can share (just need to remove at least one screen print because of the names included). Additionally, I think I have the documentation that we utilized when we first set this up, which was a long time ago. The test script follows our current process, while the other documentation hits on a few useful reports and such that the test script does not.

unknown

Here's a good overview, actually - note that we now use CB25.1 (upload) in conjunction with CB185 to mark checks are cleared.

Cash Ledger – Check Reconciliation

The following is a high level overview of the check reconciliation process in Lawson Cash Ledger (CB)

When AP issues checks, records are written to the CB module – CBCHECK and CBTRANS are the two tables that we commonly query for check data.

CB80 is utilized for bank adjustments – most notably the option to void/stop-pay a check or reconcile a check. When a check is reconciled, AP has easy access to see that a check cleared the bank (typically they utilize drill-around.) This allows them to respond to vendor inquiries more efficiently. Additionally, this data indicates that a check can not be voided and reissued.

CB80 requires the user to input the cash code and transaction code in order to inquire on data and then void or reconcile. The majority of checks processed by Accounts Payable are for cash code 2100 – the operating account. However, several of the PC’s have their own accounts and therefore 8100, 8200, etc also exist.

CB80 reconciliation data can be updated via an upload process, which is done at least monthly (may be done more frequently depending upon finance’s needs and processing). If the activity is minimal, this can be done manually. Simply enter an ‘R’ on the line, enter a valid reconciliation date, then click ‘change.’

The transaction numbers in CB80 can skip as this screen shows only records that are available for adjustment. CB90.4 will show all records, regardless of status. In the past, the 2100 cash code was ‘closed’ after bank reconciliations were completed (CB190). This updates a field on the record to indicate that it can no longer be adjusted. Transactions for periods that have been closed can be inquired on in CB90.4

Reconciling items in CB80 (or via upload) will prevent users from inadvertently voiding a record that should not be voided. Note that a record marked as reconciled can be re-set to open simply by entering an ‘O’ (open) on the line, removing the reconciliation date in CB80, and clicking ‘change.’ By closing periods (CB190) once an account has been fully reconciled to the bank statements (outside of Lawson) a reconciled transaction can no longer be re-set to open.

While preparing bank reconciliations, a listing of outstanding checks can be accomplished with a simply query against CBCHECK, or by running a CB221 – Bank Transaction Listing report with the appropriate parameters selected.

Copyright © 2025 Infor. All rights reserved.