Contents
The aim of the Bank Reconciliation process is to reconcile all the incoming transactions from the bank to the IP1 GL transactions and verify the opening and closing balances. The central Bank Reconciliation file (GLBNK00P) holds the Bank and GL entries; with the bank entries from the bank upload and the GL entries that are transferred as part of GL end of day.
Each of these entries is assigned to a particular Bank Rec Group and Bank Key on this file and these two fields are used to match off the Bank vs GL entries.
This document describes the Automatic Bank Reconciliation process where there is no manual entries of the bank statement.
Process Overview
- Bank statements are uploaded into interim bank interface file (GLBNI000P)
- GL Bank Statement Print is run to review the interim file.
- GL Bank Statement is reviewed to check if its correctly mapped for bank reconciliation. (If the mapping is incorrect then control settings (TMSBK/XXX-TRC*) can be reviewed and the upload rerun).
- If bank rec mapping is correct then Bank statement can be transferred to Bank Rec file (GLBNK00P).
- AP/AR/GL transactions are updated to Bank Rec file as part of normal GLEOD.
- For the actual reconciliation process you can
- run the Bank Reconciliation report (GLR340) to review any mismatched entries
- run Bank Statements Re-print (GLR345) to check opening/closing match and list of transactions on Bank side entry
- Bank File Inquiry (GLI320) can be used to review transactions in Bank Rec file
- Use Work with Bank Rec to link/allocate Bank side entries to GL side and create/link any GL journals for missing GL transactions.
Business rules
The following business rules have to be setup to handle GL Bank Reconciliation. These business rules must be setup with support from Iptor IP1 consultants. It is critical to understand the setting of control files and how it works. Control files must be setup correctly for the system to operate as intended. Any changes to the control files setup should be addressed cautiously and in consultation with Iptor IP1 consultants.
| Note | This document does not cover customised setup tasks of specific companies. Deviations from this setup should be covered by setup tasks written by individual companies. |
| Control files | Setup |
| TMSGL/BNK-UPDT Bank file active | Bank reconciliation must be activated in this control file to allow update of the bank file. |
| TMSBK/***-BKAC Bank details | Each branch number and bank account must be listed on this control file with corresponding GL account code and a bank code which links to TMSBK/***-TRCD. |
| TMSBK/***-BKKY Bank key source exception |
This can be used to create special codes for TRCD bank key source This might be required where the bank key is not at start of the bank ref or cust ref field For example, if bank statement shows AP cheque numbers in the Bank Ref field with 10 characters, but only the last 8 characters match our IP1 cheque number (AP Doc#, GL Jnl#, Bank Key). Can use this control file to create a ‘source code’ that picks up from pos 3 of the Bank Ref field.. |
| TMSBK/***-COMM Commission code |
If the Bank upload procedure is to calculate any commissions then the commission codes must be defined in this control file and specified in TMSBK/***-TRCD. The G/L Account defined in this control will be used to automatically post G/L Journal for the commission. |
| TMSBK/***-PCDC PC document name | Defines the folder and document name to retrieve the bank statement data from. |
| TMSBK/***-TRCD Transaction codes | This control file is used to map bank transactions into appropriate bank rec group, bank key. |
| TMSBK/***-TRCX Transaction extended definitions | This defines extensions that are specified on TMSBK/***-TRCD column ‘Extension’. This will allow the bank file upload procedure to further identify transactions in the statement file apart from just the transaction code. |
| TMSAP/BNKA Valid bank accounts by company |
Identifies which GL accounts are ‘bank accounts’ (for GLO065 EOD interface to bank rec) |
| TMSGL/BNK-BKGR Bank reconciliation group code definitions | Holds the Bank reconciliation groups; defines the types of transactions on the Bank statement. |
| TMSGL/BNK-MTCH Bank reconciliation match group headings | Holds Bank Rec Group match group headings for GLR340 report (eg. Unpresented AP Cheques, etc. |
| TMSGL/BNK-GLMJ Default G/L accounts for bank statement entry |
For each bank rec group, can optionally nominate default bank key, GL account. MUST setup Journal Rule which identifies if GL account is mandatory, etc. |
| TMSGL/BNK-RPTC Banking report codes |
Only used in GLR040 interim report. Transactions that are given a Report Print Code will print on the |
| TMSGL/JNLT Journal types | Links GL Journal Types to bank rec groups. |
| TMSAP/BNK-PMTH Bank payment methods |
Dictates the GL Bank Account used for different payment methods It also has an “Auto Gen” column which dictates how Bank Rec Key will be assigned to these payments
|
| TMSAR/JNLI Banking journal interface definition |
This control file defines for each AR pay type
|
Procedure
It is your responsibility to ensure that you understand this procedure before performing the following tasks.
| Note |
Deviations from this procedure should be covered by procedures written by your company. Before performing any tasks please ensure all the business rules are set-up accordingly. |
Bank entries on Bank rec
This section describes how the “Bank” side of data is captured into the Bank rec file (GLBNK00P). The Bank transactions are transferred into the GLBNK00P file with G8SRC=B.
| Process | Steps |
|
Upload bank statement |
Various programs exist to accommodate upload of various bank statement formats, e.g. GLO100, GLO105 etc. The BAI or BAI2 format is becoming a global standard (program GLO121). The upload statement program will clear and replace the bank interface file GLBNI00P. Therefore if previous upload has not yet been ‘transferred’ to the Bank rec file, then that will be lost. See Bank statement upload programs in Auto Bank Reconciliation document for the details of the various upload programs.
|
|
Check/review interface file (GLBNI00P) |
Note: During the implementation/setup phase, you can keep repeating the bank statement upload after making TMSBK/xxx-TRC* changes until satisfied with mapping, before transferring to the final Bank Rec file. |
| Transfer to Bank Rec file (GLO030) |
Once the errors are checked and rectified and you are satisfied with the mapping, you can run the option to transfer to the Bank Rec file (GLBNK00P). Menu option: Base Modules> General Ledger> Bank reconciliation> Auto Bank Reconciliation> Bank Statement Transfer to GL. This program (GLO030) performs the following.
If there are no errors then GLO030P2 report has the BANK STATEMENT UPLOAD LIST. This shows more details of what has been uploaded, including GL bank acct, dates, group, bank key, amount, narrative. Also shows the GL Account and journal number for auto postings. After the transfer to GL, the interim GLBNI00P file is cleared. |
GL entries on Bank rec
This section describes how the “GL” side of data is captured into the Bank rec file (GLBNK00P).
GL transactions against ‘bank’ GL accounts (TMSAP/BNKA) are transferred as part of GL EOD process (see details below) into the GLBNK00P file with G8SRC=G. The GL Journal Number becomes the Bank Key G8BKKY for matching off purposes. The Bank Reconciliation Group is determined based on GL Journal Type (TMSGL/JNLT setup).
| AR to GL |
|
Typically, the AR transactions will be interfaced through to GL and bank rec files during the EOD process.
|
| AP to GL |
|
AP transactions may be interfaced to GL transaction by the AP background job, but payments will not show in the G side of bank reconciliation till a GL EOD is run (typically automated into distribution EOD also)
|
| GL End of Day Processing |
|
Any GL transactions against GL bank accounts (TMSAP/BNKA) that were not created from GLO030 (Bank Statement Transfer to GL) or from GLE030 (Bank Statement Entry) will be processed into the GLBNK00P file as part of GL EOD.
|
Bank reconciliation process
This section describes the actual Bank reconciliation process of matching off Bank vs GL entries.
| Process | Steps |
| Bank reconciliation report |
|
| Bank statement reprint |
Bank Statements Reprint (GLR345) may optionally be used to check opening/closing match and list of transactions on Bank side only. This is similar to GLR040P1, except this can be used after transferring GLBNI00P into GLBNK00P. Menu option: Base Modules> General Ledger> Bank reconciliation> Manual Bank Reconciliation> GL Bank Statement Reprint. See Bank Statement Reprint for details. |
| Bank file inquiry |
Bank File Inquiry can optionally be used to review transactions in Bank Rec file. It has option to start at specific bank group/key, but can scroll through and see all entries shows both B and G sides. Menu option: Base Modules> General Ledger> Bank reconciliation> Manual Bank Reconciliation> GL Bank File Inquiry. See Bank File Inquiry for details. |
| Work with Bank Rec |
With Work with Bank Rec functionality allows you to link/allocate existing Bank side entries with GL side entries in the Bank Rec file. You can also create and link new GL journals on the fly if required. This is particularly useful for cases where the GL entry does not exist yet for a bank transaction. Menu option: Base Modules > General Ledger > Other > Bank Reconciliation > Manual Bank Reconciliation > GL Work with Bank Rec. See Work with Bank Rec for details. |
