GLM is a standalone system with accounts and balances being mirrored from DDA\s. The actual accounts and balances are on DDA.
GLM will either pull the account turnover data from DDA and build the balance for the account or DDA will push the actual value dated balances to GLM tables based on which GLM will update the account balances and carry out its function of sweeping and pooling
8.1 Maintaining Balance Upload
Balance fetch parameter maintained at Branch Setup maintenance will govern the mode of balance update on GLM.GLM supports two modes of balance update, Online and Offline
In the online mode, the balances for the accounts in the branch will be fetched through a Web Service from the DDA. Basically it’s a pull by GLM from DDA. The balance build always happens before the sweep/pool execution hence the sweeps/pool will always be performed on the latest balances on the account.
GLM builds online balances in the following manner.
8.1.1.1 Value Date Build
In this scenario GLM will fetch balances from the DDA. The balance fetch includes previous day (T-1) closing value date account balance and the account turnover for the current book date (T) based on which the balance is built for the account, The account turnover considers transaction posted by the DDA and the transactions posted by GLM as well (which may be due to Intraday/time based sweeps)
As part of account turnover fetch GLM can receive the following:
● Only current value dated (T) turnover. In this situation the TO is clubbed with previous day’s value date balance to arrive at today’s value date balance
● Both current value dated (T) turnover and back dated turnover (T-X, where X is the number of days) or
● Only back dated turnover (T-X, where X is the number of days ).
8.1.1.2 DDA Turnover(BVT Turnover)
In this scenario GLM will only fetch the turnover for all the days in the BVT period without including the transactions that are posted by LM. This is used for BVT processing.
In offline mode, the balances for the accounts in the branch will be fetched from the backend tables of GLM. These balances are updated through a periodic file upload from DDA. Basically it’s a push from DDA to GLM. DDA will keep periodically pushing the balance files to GLM and the periodicity is governed by the DDA. GLM will refer to its backend tables before the start of sweep/pool.
In offline method GLM will build balances on actual value dated balances of the participant accounts (based on the last file upload from DDA)
Note
All transaction posted in DDA from GLM, will have a unique transaction code.