The General Ledger (GL) module is included in the SrCoreSystem base system and provides for the maintenance of multiple charts of accounts, storage of information about counterparties, accounts, documents, account balances and turnovers, basic accounting settings and localization of bank accounting policy rules, various types of directories
GL maintains a single pool of accounting entries, which can be entered manually, formed by operations on contract subsystems, regulations, simple operations, or formed via API by external subsystems. In the general pool of transactions the detailed review is available in the context of sub-accounts, as well as parameters of ounce and quantitative accounting
All documents have their own configured route, with a corresponding set of statuses, check procedures, etc. The system controls all general ledger objects, primarily the main system objects with incomplete routes. Control is carried out both at the close of the day and beforehand at the end of the working day by a bank employee.
The document posting function includes the control of limits and arrests and can be configured for any transition of route statuses. All other mandatory validation procedures and bank's own validation procedures are also configured.
All documents have a unique Reference and operation code with which one document or a group of documents were generated.
When closing/opening a trading day, the system uses a customizable set of routine procedures that perform the necessary data validation and automatically carry out the necessary bulk operations. Revaluation procedures are also included in the trading day closing package and are performed fully automatically.
The general ledger has a single typified, expandable pool of data on the bank's counterparties. Types of counterparties can be configured by the bank independently. As for all objects of the system, for the module for working with counterparties, depending on the type, a route is configured that allows flexible counterparty data validation for various stages of the object life cycle. There is a mechanism for grouping counterparties by type of relationship.
The task of working with accounts and balances primarily offers viewing information on balances for a date or period, in the context of sub-accounts, analytical and balance accounts (with details by class, section and group), according to the specifics of the NBU Chart of Accounts.
It is possible to configure the segmentation of an analytical account for an arbitrary chart of accounts. For the convenience of presenting account numbers, as well as for encoding analytical parameters, you may specify a symbol in the account number for separating segments (usually a dot) and rules for automatically generating segments when performing an automatic account opening operation. The mechanism of analytical / sub-account segmentation provides for the mandatory indication of the account mask when opening it. In the future, the account number is formed in strict accordance with the selected mask. Automatic numbering rules and lookups are specified for segments, limiting the list of valid segment values.
The account can be multi-currency. As a rule, all general ledger accounts are opened automatically as part of their business processes. At the account level, setting limits is available. IBAN standard is supported as well.
Working with file cabinets of deferred payments/transactions (SEP retaliatory payments, FM stopped payments, documents on receivables for cash settlements, etc.) is also one of the convenient General Ledger functions. Working with file cabinets is the same unified mechanism as working with contract and transaction subsystems. The General Ledger functionality also includes the maintenance of all system directories divided into several large groups (system, mandatory directories of the NBU and other regulators, client, etc.)
There are more additional options for working with objects of the general ledger, from a list of operations that can be performed on one line or a group of lines (contractors, accounts, documents, etc.), i.e. BPM elements, to various service functions. These features are presented in the User's Guide and Administrator's Guide to the SrCoreSystem and CBS SRBank.