RU2723452C2 - Computer-implemented method and system for centralized control of financial-credit organization day of operation - Google Patents

Abstract

FIELD: data processing; control systems.SUBSTANCE: invention relates to a method for centralized management of a financial-credit institution operating day. Method, in which forming group of operational day status, group of procedures of operational day; at the beginning of the operational day T + 1, the previous calendar day T is transferred to the processed status; in the processed status performing the operations, which are actually performed in the calendar day T + 1, but must be reflected in the bottom T; status of operational day T into routine status for performing mass operations; translating operational day T into a locked status, where a prohibition on performing all operations with reflection in the operating day T; routine and control procedures are performed during the action of the blocked status of the operational day, upon successful execution of the control procedures, the status of the operation day T is changed to the closed status; if unsuccessful, the status of operational day T is changed to a restricted status to perform correction operations.EFFECT: technical result consists in improvement of level of controllability and control of performance of intraday procedures of operational day and reduction of number of errors in formation of accounting operations.9 cl, 4 dwg

Description

FIELD OF TECHNOLOGY

[001] This technical solution, in General, relates to the field of computer technology, and in particular to methods and systems for centralized management of the operational day of a financial institution.

BACKGROUND

[002] Currently, documents received by the financial and credit institution during the business day from customers are accepted for execution on the same day, and those received after the end of the business day on the next business day. Depending on the specifics of payments and customer transactions, financial institutions may establish an extended business day. An operational day is a part of a bank’s working day, during which documents for transfer and documents for withdrawing funds are received from customers and, if technically possible, they can be processed, transferred and executed.

[003] Existing business day management mechanisms do not provide the capabilities necessary to ensure centralized management of the business day and to meet the requirements of the regulator. The problem with similar solutions is that, in particular, it is necessary to have a technological break to complete the closing day procedures, it is impossible to keep records of transactions on different days, there is no mechanism for centralized control of the sequence of closing days. Also, quite often there is no mechanism for managing permissions for processing business services the day after the operational day at the user or role or unit level.

[004] JP 9293104 A, “ATM systems for bank transaction transmits transaction date and transaction day from on-line system of unit bank to online system of customer bank through relay center, for transaction transmitting unit," patent holder: HITACHI, is known from the prior art. LTD, published: 1997-11-11.

[005] This solution solves the problem of synchronizing transaction dates between different banks. The system performs a transaction between various customer banks and several banks through a single center. Each online bank system transmits the transaction date and transaction day through the center to the online bank system of various customers from the transaction transfer unit. The comparative transaction evaluation unit compares the transaction day of the online banking system and the transaction day of the online banking client system. If the day of the transaction matches, the transaction process is executed on the same day of the transaction. If the transaction day is different, the transaction is executed the next day. The process notification transmission unit transmits daily transactions between the party processed by the bank and various customer banks based on the transaction judgment block.

SUMMARY OF THE INVENTION

[006] This technical solution is aimed at eliminating the disadvantages inherent in existing solutions known in the art.

[007] The technical problem (or technical problem) in this technical solution is to provide the ability to reflect operations in the operational day (T-1) even when the calendar day T occurs, as well as to organize the technical ability to configure and perform intraday procedures and closing procedures of the operating day.

[008] The technical result achieved in solving this problem is to increase the level of controllability and control over the implementation of intraday operating day procedures and reduce the number of errors in the formation of accounting transactions.

[009] The specified technical result is achieved through the implementation of a method for centralized management of the operational day of a financial institution in which a group of operating day statuses is formed, within which current operational activities are carried out to conduct and support banking operations, and the group includes current, processed, regulated, blocked, limited, and closed status of the trading day; then form a group of operating day procedures, the implementation of which is necessary to ensure the correct implementation of the life cycle of the operating day; then, upon the occurrence of the current operational day T + 1, the previous calendar day T is transferred to the processed status to complete banking operations that started on calendar day T and did not complete when it was switched from the current to the processed status; then after the completion of the processed status of the day T, the status of the operational day T is transferred to the regulatory status to perform bulk operations from the above-mentioned group of procedures of the operational day; after the completion of all the regulatory procedures performed in the previous step, of the operational day T, the operational day T is transferred to the blocked status, according to which a ban is established on all operations with reflection in the operational day T; perform routine and control procedures in the general ledger during the validity of the blocked status of the trading day, and in case of successful completion of control procedures in the general ledger, the status of operating day T is automatically transferred to the closed status; in case of unsuccessful execution of control procedures in the general ledger, the status of the trading day T is automatically transferred to a limited status for performing adjustment operations.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The features and advantages of the present invention will become apparent from the following detailed description of the invention and the accompanying drawings, in which:

[0011] In FIG. 1 shows an example implementation of a method for centralized management of an operating day of a financial institution, shown in the form of a flowchart.

[0012] In FIG. Figure 2 shows an example of the implementation of a centralized management system for the operational day of a financial institution.

[0013] In FIG. Figure 3 shows an implementation option in which the database in which entities are stored (for example, the trading day, its status, etc.) is located on several server nodes of the cluster (intended for data storage).

[0014] FIG. Figure 4 shows an embodiment of a centralized management system for the operational day of a financial institution with external modules.

DETAILED DESCRIPTION OF THE INVENTION

[0015] This technical solution can be implemented on a computer, in the form of an automated information system (AIS) or a machine-readable medium containing instructions for performing the above method.

[0016] The technical solution may be implemented as a distributed computer system.

[0017] In this decision, a system means a computer system, a computer (electronic computer), CNC (numerical control), PLC (programmable logic controller), computerized control systems, and any other devices capable of performing a given, well-defined sequence of computing operations (actions, instructions).

[0018] An instruction processing device is understood to mean an electronic unit or an integrated circuit (microprocessor) executing machine instructions (programs).

[0019] An instruction processing device reads and executes machine instructions (programs) from one or more data storage devices. Storage devices may include, but are not limited to, hard disks (HDDs), flash memory, ROM (read only memory), solid state drives (SSDs), and optical drives.

[0020] A program is a sequence of instructions for execution by a computer control device or an instruction processing device.

[0021] The terms and concepts necessary for the implementation of this technical solution will be described below.

[0022] Data is a formally interpreted representation of information suitable for communication, interpretation or processing (ISO / IEC 2382: 2015, 2121272 “data”);

[0023] A data element is a unit of data that is considered indivisible in the context (“unit of data that is considered in context to be indivisible”) (ISO / IEC 2382: 2015, 2121599 “data element”);

[0024] A database (DB) is a collection of data organized in accordance with a conceptual structure describing the characteristics of these data and the relationships between them, and such a collection of data that supports one or more applications (ISO / IEC 2382: 2015, 2121413 " database ");

[0025] Metadata - data about data or data elements, possibly including a description of the data, and data on data ownership, access paths, access rights, and data volatility (ISO / IEC 2382: 2015, 2121505 “metadata”);

[0026] Server - a functional unit in a computer network that provides services for workstations, personal computers or other functional units (ISO / IEC 2382: 2015, 2120558 "server"); a function block that provides common services for workstations or other function blocks over a data network (ISO / IEC 2382: 2015, 2124462 “server”);

[0027] An entity is any concrete or abstract thing that exists, existed or could exist, including a combination of such things (ISO / IEC 2382: 2015, 2121433 "entity");

[0028] Attribute - a named property of an entity (ISO / IEC 2382: 2015, 2121440 “attribute”);

[0029] An entity class is a set of entities with a common attribute composition (ISO / IEC 2382: 2015, 2121438 "entity class");

[0030] An instance of an entity (an instance of an entity class) is a specific instance of an entity class (ISO / IEC 2382: 2015, 2121439 "entity occurence");

[0031] Attribute value - the specific attribute value (ISO / IEC 2382: 2015, 2121441 "attribute value");

[0032] An operation is an action or a set of actions on data and / or metadata in which at least one data or metadata element is changed or at least one data or metadata element is created or deleted or at least one resulting value is generated.

[0033] The general ledger is a consolidated document that presents the totals of the financial statements and accounts. The main ledger is maintained on the basis of ledgers and contains all the information about the financial position of the company.

[0034] A method for centrally managing a business day of a financial institution shown in FIG. 1 in a block diagram includes the following steps.

[0035] Step 110: form a group of operating day statuses within which current operational activities for conducting and supporting banking operations are carried out, the group including the current, processed, scheduled, blocked, limited, and closed status of the operating day.

[0036] A business day is a period of time in which a financial institution accepts, processes, deletes documents related to one calendar date.

[0037] In a particular embodiment, a business day can be implemented as an entity in a database that is stored on a storage device 202 of the system 200, which is shown in FIG. 2, and the essence has the following structure.

[0038] It will be apparent to those skilled in the art that any type of database known in the art can be used as a database. For example, hierarchical, network, relational, and object-oriented databases.

[0039] A business day may include attributes such as a unique identifier for a business day, a unit (a unique identifier for a department for which a business day is valid), a date for a business day, and the status of a business day, not limited to.

[0040] The status of a trading day can also be represented as an entity in a database that contains attributes such as identifier, status name, status code, which is used as an application identifier.

[0041] A group of valid transaction day statuses that may be assigned to a transaction day depending on its condition is implemented in some embodiments of the invention in the form of a directory or list with a limited set of items. In some embodiments, the database in which the entities are stored (for example, the trading day, its status, etc.) is located on one server node or on several server nodes of the cluster (intended for data storage), as shown in FIG. 3. On which server nodes the data is stored depends on the topology of the cluster and on the type of entity. The directory is read-only and does not allow changing its contents after the system 200 starts working. The contents of the directory contain the status of the trading day and the status code in symbolic form, for example,

• Open. Current (OPEN_CURRENT);

• Open. Processed (OPEN_PROCESSING);

• Open. Regulatory (OPEN_REGLAMENT);

• Open. Blocked (OPEN_BLOCKED);

• Open. Limited (OPEN_LIM_ACCESS);

• Closed (CLOSED).

[0042] In the status of the trading day “Open. Current ”is allowed to create and process all operations of the current trading day.

[0043] In the status of the trading day “Open. Processed ”it is allowed to create and process all operations after changing the date of the trading day, except for operations created in the front-end system (cash services, personal account of a mobile application, etc.).

[0044] In the status of the trading day “Open. Regulatory ”allowed the implementation of regulatory (batch) procedures. In this status, the creation and processing of operations by regulatory procedures is allowed. Upon successful completion of all regulatory procedures, the trading day automatically changes the status of “Regulatory” to “Blocked”.

[0045] In the status of the trading day “Open. Blocked "complete processing operations. Upon the successful completion of processing, the closing of the trading day in the general ledger is automatically performed (launch of the routine and control procedures of the general ledger), blocking the creation and processing of all operations.

[0046] In the status of the trading day “Open. Limited ”it is allowed to create and process operations for which there is a corresponding permission for a particular user / unit on a given date to eliminate identified discrepancies in the balance sheet, which is configured by the system administrator 200 depending on the type of operations. It is allowed to repeat control procedures and regulatory procedures of the general ledger.

[0047] In the status of the trading day “Closed”, all operations are prohibited.

[0048] Step 120: form a group of operating day procedures, the implementation of which is necessary to ensure the correct implementation of the life cycle of the operating day.

[0049] A list of such procedures is maintained in a separate directory, which is also stored on the storage device 202, in which, along with the data necessary for users to set the schedule and to monitor the execution of the operational day tracking procedures (hereinafter referred to as “PSOD”) in the schedule (procedure name, code, validity period, expected execution time) sets the data used when starting the procedure. Such data in particular is the name of the java class for the implementation of the procedure, the identifier of the application module, the parameters for starting the procedure, etc.

[0050] If some external module 209 is in the system 200, as shown in FIG. 4, develops a batch procedure and wants to include it in the business day management system 200, then the java class implementing this procedure must implement the interface and implement all its methods. After that, this procedure can be added to the list of operating day support procedures — procedures that can be started according to the schedule of the operating day management system 200. In some implementations, new procedures are added manually by the user of the system 200. In other implementations, a list of procedures (already verified) is added automatically when the system 200 starts up.

[0051] The structure of the directory as an entity can be implemented in the form of a table in a database located on the storage device 202, or in the storage in random access memory in the form of a "key-value". The entity itself contains the following set of attributes: a unique procedure identifier, procedure code, procedure name, procedure type (scheduled or control), completion wait time, procedure validity period, name of the applied external module 209 (from which the procedure is executed), etc., not limited to.

[0052] The procedure code is required to identify the procedure by users of the system 200. This is a short unique code that is intended to be used in the schedule approval documents instead of the name (names can be long and similar for different procedures: for example, “capitalization” is in deposits and deposits )

[0053] The regulatory procedure is a procedure, the result of which is a change in grocery and (or) accounting. For example, "extension of contracts."

[0054] A control procedure is a procedure that results in information on whether the verification of certain conditions has been successfully or unsuccessfully (without changing credentials). For example, "accounts with a red balance are found or missing."

[0055] The wait time for completion during which the procedure is to be completed can be determined in seconds and represents the number of check cycles for certain conditions. After starting the procedure, a cycle for checking completion status is launched for it with a verification period equal to the waiting time for completion. If the procedure is not completed after the specified time, then it is considered “hung up” and its control is transferred to the user of the system 200 for manual analysis. The waiting time can be determined in advance based on measurements of load testing and forecast of the volume of operations, where an expert assessment of the planned time of the procedure and the number verification cycles. Since the closing of the trading day and the handing over of the balance to the Central Bank are regulated by the regulatory documents of the Central Bank, there is a need to limit the time it takes to follow the business day and it must be controlled. Thus, if the planned time for executing the procedure is exceeded, there is a risk of violation of the deadlines for the balance to be submitted to the Central Bank and escalation is needed.

[0056] For example, the “capitalization of deposits” procedure is configured for 1 hour of execution and 2 verification cycles. In this case, the completion of capitalization within two hours will be a normal course of events. And if the execution time is exceeded by more than two hours, the system sets the procedure status to "failure to complete." If there is a notification setting for the “capitalization of deposits” procedure, the user is sent an SMS and an email to the phone and address specified in the setting. Then, an analysis of the reasons for the slowdown or freezing of the procedure is carried out, after which decisions are made on further actions.

[0057] The validity period of a procedure determines how long it will not start, which ensures historicity. For example, before August 1 and after August 1, it is necessary to calculate interest on the deposit with different algorithms, in connection with which two procedures are implemented. One must be launched before August 1, and the other from August 1 and later. By indicating the validity period in the card, this approach can be implemented. In addition, specifying a period ensures that an “outdated” algorithm cannot be included in new schedules.

[0058] The name of the applied external module 209 (or adjacent external computing system) indicates where a particular procedure has been developed. For example, it can be deposits and accounts of individuals, deposits, loans, accounting for reserves, etc. Also, the applied external module 209 contains a unique identifier that is used to send an external AS when routing a request to start a procedure.

[0059] Step 130: form a list of procedures for tracking the trading day with an indication of the startup sequence.

[0060] This sequence is implemented using a schedule and a list of scheduled procedures for this schedule.

[0061] The schedule is implemented as an entity in the database and has the following attributes: unique identifier, schedule name, validity period, identifier of the user responsible for the schedule. In some implementations of schedules in system 200, there may be several. Schedules can have statuses (for example, draft, on approval, approved, current, archived). Only one schedule can be valid at a time. A schedule is a task template for launching a trading day without specifying specific dates (the relative date in the T and (T + 1) format is indicated in the launch date settings, where T is the date of the trading day).

[0062] For each schedule, a list of scheduled procedures, the launch of which is scheduled in accordance with this schedule, is indicated. Planned procedures are implemented as a database entity. Each scheduled procedure represents a separate object with its own properties in the storage device 202 (in the case of using a database, each entity is represented as a table row, properties are fields). For each scheduled procedure, the following properties are indicated: a unique identifier for the planned procedure, a transaction day tracking procedure (a unique identifier for the transaction day tracking procedure, which determines the data used when launching and monitoring the completion of the PSOD ”), a schedule identifier (to which the planned procedure refers), level of organizational structure (Company Code / Terbank / Bank) and a list of departments (for which the procedure should be started), conditions for starting the procedure (By date and time, by changing the status of the OD, by fulfilling the dependencies, etc.), dependencies (identifiers other planned procedures of the same schedule - along with the launch conditions determine the launch sequence of the PSOD in the schedule), not limited to.

The connection of the schedule with the planned PSOD is implemented as follows: The schedule of the list of scheduled procedures is not stored in the schedule, but for each object of the "Scheduled procedure", the link to the schedule to which it refers is stored in the "Schedule identifier" attribute.

[0063] The launch is performed not on these entities, but on the essence of “Task for starting procedures”. The planned procedures for maintaining the operational day of one schedule are a “template” that should be applicable for operational days, the dates of which are included in the validity period of this schedule. According to this template, a list and sequence of launching tasks for launching procedures for a specific operational day is compiled. This is as follows. Every day at the time set in the settings according to the prepared schedule (meaning the schedule in the “Effective” status, that is, approved and during the validity of which the date of the transaction day in question falls), tasks are formed to start the procedures for tomorrow. This is carried out according to all planned procedures of the schedule valid for tomorrow.

[0064] When the execution manager located on the multimedia component 203 is automatically populated, for all procedures, the type of launch of which assumes an automatic start in time, the task scheduler, which can start the procedures / processes in time, adds start tasks on the specified date and start time in the settings of the planned PSOD. The rest of the launch conditions: to change the status of the trading day and to fulfill the dependencies are achieved as follows:

1. Each time when the status of the trading day changes to a different status, all launch tasks that should start are carried out;

2. Each time upon completion of the launch task, they search for other tasks in the status “Waiting for dependencies to complete”, which depend on the completed one.

[0065] For each task to start the procedure during its formation, the following properties are indicated (most of these properties are determined from the scheduled procedure by which the start task is generated):

• Unique identifier of the task to start the procedure, the planned procedure - a unique identifier of the planned procedure, which determines the relationship with the schedule, according to which the tasks for the launch are generated, and the data used to start and monitor the implementation of the PSOD ”- you can“ go up by the link to the planned procedure »To the OD maintenance procedure, by which to determine data for displaying information about the procedure and data for its launch);

• Date of the operational day for which the launch task is being generated;

• The unit for which the procedure is to be started. For each unit from the list of units of the planned procedure, a separate task is generated to start the procedure. T.O. one launch task is performed in one unit;

• Conditions for starting the procedure - include the type of launch (Manual, By date and time, by changing the status of the OD, by changing the start of the previous OD, by executing dependencies, etc.), the planned date and time of the launch (indicated for the types of launch, time-based - for example: Manually, By date and time) and the dependent status of the OD (indicated for launch types based on a change in the status of the OD - for example: By changing the status of the OD, By changing the status of the previous OD). When creating a launch task, launch conditions are determined from the corresponding properties of the scheduled procedure. In this case, the launch date and time are determined based on the time zone of the unit for which the launch task is generated. For example, if the planned procedure indicates: List TE Unit 1 (UTC + 3), Unit 2 (UTC + 4); Startup Type = By date and time; Launch date = T, Launch time = 10:00 Moscow time; That is, when launching tasks are generated for OD date 08/01/2018 according to this planned procedure, two launch tasks will be generated: (1) For the department “Unit 1” with the launch type “By date and time” and the planned launch date / time = 01.08. 2018 10:00; (2) For the unit “Unit with the launch type“ By date and time ”and the planned start date / time = 08/01/2018 09:00 Moscow time (the launch will be performed at 10:00 according to the unit’s time zone);

• Dependencies indicating the level of dependence (the description of the levels is presented below) - identifiers of other tasks for launching. Determine the launch sequence of the PSOD in the schedule) .;

• Status of the procedure

[0066] Further actions to start the procedures and to monitor the result of their execution are carried out in the execution manager. The dispatcher can be implemented in the form of a graphical user interface located on the multimedia component 203, which displays all the tasks for launching the support procedures for the operating day and the result of their execution. Tasks can be filtered, and monitoring can be done automatically or by a user of the 200 system. In the dispatcher, you can select tasks and change the start parameters for them and (or) start manually. Manual control of the launch and change of parameters is carried out by users (employees responsible for managing the operational day). In the main screen of the execution manager, the parameters and status of the execution are displayed, and you can also call up a window with detailed information on the execution of each task. The details reflect when the launch took place, the results of dependency checking, the results of a survey of the status of the procedure, the detailed information that the procedure returns when it is completed.

[0067] For each procedure, the schedule can specify the start mode (manually / automatically), as well as events of the system 200 (for example, the start date / time, change in the status of the trading day, completion of another procedure), upon occurrence of which the procedure starts . The system 200 has the following options for starting procedures:

• Manually - manual start by the user of the system. Automatic start is not performed;

• By date and time - automatic start when the time comes;

• By changing the status of the OD - automatic start when the status of the OD is changed (the necessary status is specified in the "Dependent Status of OD" parameter);

• By changing the status of the previous OD - automatic start when the status of the previous OD is changed (the necessary status is specified in the "Dependent OD status" parameter);

• By executing dependencies, but not later - automatic start when dependencies are completed or by time (whichever comes first).

[0068] The sequence of starting procedures is determined by building dependencies between schedule procedures. In this case, two levels of dependence are permissible.

[0069] The first level of dependence is hard dependence. It is indicated if it is necessary to start the procedure provided that the dependency is successfully completed. For example, if PSOD1 (the procedure for tracking an operating day, as indicated above) depends on PSOD2 with the level of “Hard dependence”, then PSOD1 will only start if PSOD2 is successfully completed. For example, the “revaluation” procedure is launched only if the procedure “reconciliation of balances and revolutions of grocery and accounting” has been successfully completed. [0070] The second level of dependence is soft dependence. It is indicated if it is necessary to start the procedure, provided that the dependency is completed, regardless of the result: successful or unsuccessful. For example, if PSOD1 depends on PSOD2 with the “Soft Dependency” level, then PSOD1 will start if PSOD2 is successfully or unsuccessfully (PSOD1 will not be launched until PSOD2 is completed).

[0071] Step 140: upon the onset of the current transaction day T + 1, the previous calendar day T is transferred to the processed status to complete banking operations that began on calendar day T and did not complete when it switched from the current to the processed status.

[0072] Automatic creation of a new “Operational Day” object with the status “Open. Current ”and a change in its status is implemented as operating day procedures, which should be added to the operating day schedule indicating launch conditions and a list of dependencies. Moreover, in the algorithm of the procedure for creating an operating day, the translation of the previous operational day (if it exists) is configured to the status “Open. Processed ”to exclude work in two or more“ Current ”days.

[0073] The announcement of the procedure for creating a new trading day and its translation immediately into the current status occurs automatically with the following attributes and their values:

[0074] Scheduled procedure settings in the schedule:

[0075] The announcement of the procedure for transferring the previous business day to the “Processed” status occurs automatically with the following attributes and their values:

[0076] Scheduled procedure settings in the schedule:

[0077] Step 150: after completion of the processed status of the day T, the status of the operational day T is transferred to the regulatory status to perform bulk operations from the above-mentioned group of operating day procedures.

[0078] As mass operations (or in other words batch), for example, commissions based on the results of the transfers made per day and the amounts, foreign exchange payments, capitalization on all deposits, etc. can be used.

[0079] Changing the status of the trading day to “Open. Regulatory ”is implemented in the form of a trading day procedure, which should be added to the trading day schedule with an indication of the launch conditions and the level of dependencies. Creating a trading day and changing the status of a trading day are implemented in the form of procedures that are entered in the schedule. Thus, to start them, you can use various settings (timers, depending on the parameters or actions in system 200).

[0080] The announcement of the procedure for transferring a trading day to the “Regulatory” status occurs automatically with the following attributes and their values:

[0081] Scheduled procedure settings in the schedule:

[0082] Batch procedures, the launch of which must be performed in the regulatory status, are configured in the schedule with the corresponding launch condition (Launch Type = "By changing the status of the OD" with the dependent status of the OD = "Open. Regulatory").

[0083] Step 160: after completing all the routine procedures performed in the previous step, the operational day T is transferred to the operational day T in a blocked status, according to which a ban is placed on all operations with reflection in the operational day T.

[0084] Changing the status of the trading day to “Open. Blocked ”is implemented in the form of a trading day procedure, which should be added to the trading day schedule with an indication of the launch condition and the level of dependencies.

[0085] Procedure declaration:

[0086] Scheduled procedure settings in the schedule may be as follows:

[0087] A ban on performing all operations with reflection in the blocked operating day T is implemented at the start of operations level: At startup, the status of the OD is checked and fails if it = “Open. Blocked".

[0088] At the time the system starts a certain operation (for example: opening a deposit on 08/19), the system requests the status of the trading day equal to 08/19. If the status is Blocked, then the operation should be denied.

[0089] If the status has changed after the initialization of the system, but before the formation of the accounting entry, then the service execution error will be fixed at the time of checking the status of the trading day during the formation of transactions.

[0090] Step 170: perform routine and control procedures in the general ledger for the duration of the blocked status of the trading day, moreover

в случае успешного выполнения контрольных процедур в главной бухгалтерской книге, автоматически переводят статус операционного дня Т в закрытый статус;

in case of successful completion of control procedures in the general ledger, the status of the trading day T is automatically transferred to the closed status;

в случае неуспешного выполнения контрольных процедур в главной бухгалтерской книге, автоматически переводят статус операционного дня Т в ограниченный статус для выполнения корректировочных операций.

in case of unsuccessful execution of control procedures in the general ledger, the status of the trading day T is automatically transferred to a limited status for performing adjustment operations.

[0091] The regulatory procedure for the general ledger can be: revaluation, closing of accounts, and control: red balance, balances on closed accounts, etc.

[0092] Accounting is maintained in the general ledger (opening / closing accounts, generating accounting entries, etc.).

[0093] In the blocked status, the scheduled and control accounting procedures are automatically performed in accordance with the schedule. If all of them have been completed successfully, the closing procedure of the trading day is automatically started (transferring the status of the trading day to the “Closed” status).

[0094] The routine and control procedures of the general ledger, the launch of which should be performed in the blocked status, are configured in the schedule with the corresponding launch condition (Startup type = by changing the status of the trading day with the dependent status OD = Open. Blocked). At the same time, all procedures whose execution should be completed in a blocked status are indicated depending on the procedure for transferring a trading day to Limited or Closed status so that there is no premature change in the status of a trading day. In an exemplary embodiment, under the conditions for starting the closing procedure of the trading day, the “red balance" procedure is indicated in a "tight" relationship. This means that the closing procedure of the trading day will not start until the check implemented in the “red balance” procedure has been successfully completed. For the procedure for transferring the trading day to Limited or Closed status, the launch condition is set to “On dependency execution, but no later”. Thus, an automatic transition to a restricted or closed status will be performed only after all the necessary conditions have been met: have all the critical procedures for limiting / closing been completed (all dependencies have been completed). The target status of the trading day (the status that will be selected depending on the following conditions - "Closed" or "Limited") at the end of the procedure is determined depending on the status of completion of the dependencies:

• If dependencies are completed successfully, then the trading day is automatically transferred to the Closed status;

• If some of the dependencies are unsuccessful, then the OD is automatically transferred to the “Open. Limited ”(in which corrective operations are performed).

[0095] By completing dependencies is meant setting one of the final statuses for the procedure (Completed successfully, Completed unsuccessfully, Execution failed, Stopped, Disabled).

[0096] In the database, the procedure entity contains the following set of attributes: name (for example, Transaction of the trading day to the Closed status), procedure code (for example, OD_TO_CLOSE), type of procedure, waiting time for completion, number of verification cycles, start and end date actions etc.

[0097] When scheduling the selective procedures for tracking the trading day, you can specify control points in the format:

• End date = T + N. Defines a key date for completion relative to the date of the OD. For example, the target completion date T + 2 for the procedure performed for the date OD = 01/01/2018 is 03/01/2018;

• Reference completion time.

[0098] These control points are taken into account when constructing the operational information panel.

[0099] A list of events by which an alert can be made is implemented as a directory. The directory is available only in viewing mode and cannot be changed in the system.

[00100] The directory structure includes a unique event type identifier, an event type class (defines an event type group — the entity by which the event occurred), an event type name, and a notification template (text of the notification being sent).

[00101] The recipient list is also organized as a directory. The directory is editable and can have the following attributes: unique identifier of the mailing recipient, domain name of the mailing recipient, full name of the mailing recipient, phone, email address, etc.

[00102] The relationship between the events specified in the directory and the recipients of alerts is configured in a separate view. In accordance with the settings specified in this submission, notifications are sent to the specified addresses / numbers of recipients.

[00103] The system implements the “Operational Dashboard” view, designed to display operational information about the results of the operations of the trading day. The operational information panel displays: The color indicator of the closing day of the trading day, as well as the total number of procedures for tracking the trading day in the context of territorial units and completion statuses. The operational information panel is built on the control points specified during the schedule setting and, depending on the status of the operational day procedures, can display the following color indicators of the closing day of the operating day:

• Red: if at the time of formation of the information panel, among the procedures that have a control completion time (control point) earlier than the time of formation of the information panel, there is at least one unsuccessfully completed (or incomplete) procedure,

• Yellow: if at the time of formation of the information panel all the procedures were completed that have a control completion time (control point) earlier than the moment of forming the information panel, but among the procedures of the monitored trading day that are not control points, there are unsuccessful procedures. Those. the schedule for control points is not broken, but there is a risk of a violation in the future.

• Green: if at the time of formation of the information panel all the procedures have been completed that have a control completion time (control point) before the formation of the information panel, and among the procedures of the monitored trading day that are not control points, there are no unsuccessful procedures. Those. the schedule is not broken, the execution is according to the schedule

[00104] FIG. 2 refers to a block diagram of a centralized management system 200 of a business day of a financial institution, in an exemplary embodiment. For example, terminal equipment 200 such as a user’s mobile communication device, tablet computer, smart TV, etc., can serve as system 200.

[00105] As shown in FIG. 2, system 200 may include one or more of the following components:

[00106] a data processing component 201,

[00107] a storage device 202,

[00108] a multimedia component 203,

[00109] the audio component 204,

[00110] an input / output interface 205,

[00111] the sensor component 206 and

[00112] the communication component 207.

[00113] The data processing component 201 typically controls all operations of the system 200, for example, operations related to displaying information, making phone calls, transmitting data, operating the camera, and recording and processing information. The data processing component 201 may include one or more processors 201.1 for executing instructions in order to carry out all or part of the steps in the methods described above. In addition, the data processing component 201 may include one or more modules that facilitate the interaction between the data processing component 201 and other components. For example, the data processing component 201 may include a multimedia component 203 to facilitate interaction between the multimedia component 203 and the data processing component 201.

[00114] A storage device 202 is configured to store various types of data to support the operation of the system 200. Examples of such data include instructions for any applications or methods operating on the system 200, contact details, phone book data, messages, photographs, videos, etc. d. The storage device 202 can be performed using any type of volatile or non-volatile storage devices, or combinations thereof, such as static random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (ROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk, cloud data storage, etc.

[00115] The multimedia component 203 includes a screen providing an output interface between the system 200 and the user. In some embodiments, the implementation of the screen may include a liquid crystal display (LCD) and a touch panel (SP). If the screen includes a touch panel, the screen can be made in the form of a touch screen for receiving input control signals from the user, and the signals may be user actions. The touch panel includes one or more touch sensors for making tactile touches, swiping the screen with the finger, and moving the cursor on the touch panel. Touch sensors can not only determine the boundaries of the action of touching or holding on the screen with a finger, but also determine a specific period of time and pressure associated with touching or holding on the screen with a finger. In some embodiments of the present invention, the multimedia component 203 includes a front camera and / or a rear camera. The front camera and the rear camera have the ability to receive external multimedia data, while the system 200 is in operation mode, for example, in the schedule mode of the operating day. Each front camera and rear view camera can be a fixed system of optical lenses or have focus and the ability to optical zoom.

[00116] The audio component 204 is configured to receive / transmit output and / or input audio signals. For example, the audio component 204 includes a microphone (MICRO) configured to receive an external audio signal when the system 200 is in an operating mode, for example, a voice recognition mode. The resulting audio signal is further stored in the storage device 202, or transmitted through the communication component 207. In some embodiments of the present invention, the audio component 204 further includes a speaker for outputting audio signals.

[00117] The I / O interface 205 provides an interface between the data processing component 201 and the peripheral device interface modules, such as a keyboard, control wheel, button, and the like.

[00118] The sensor component 206 includes one or more sensors to provide status assessments of various aspects of the system 200. For example, the sensor component 206 can detect the open / closed status of the system 200 relative to the location of components, for example, the display and keyboard of the system 200, changes the position of one of the components of the system 200, the presence or absence of user contact with the system 200, the orientation or acceleration / deceleration of the components of the system 200, as well as the change in the operating temperature in the system 200. The sensor component 206 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 206 may also include a light sensor, such as a CMOS or CCD image sensor, used in image processing applications. In some embodiments, the implementation of the sensor component 206 may also include a hydraulic sensor, gyroscope, magnetic sensor, pressure sensor or temperature sensor.

[00119] The communication component 207 is configured to facilitate communication over a wired and wireless network between the system 200 and other devices. System 200 can access a wireless network based on communication standards such as Wi-Fi, 2G, or 3G, or a combination thereof. In one exemplary embodiment, the communication component 207 receives a warning or broadcast signal of related information from an external control system via a broadcast channel. In one exemplary embodiment, the communication component 207 further includes a near field communication module (CBF) to facilitate short-range communication. For example, the KBP module can be implemented on the basis of RFID (Radio Frequency Identification) technology, IrDA (InfraRed Data Association), ultra-wideband technology (UWB), Bluetooth technology (BT) and other technologies.

[00120] In exemplary embodiments, system 200 may be configured with one or more custom tailored integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLCs), user-programmable gate arrays (PPMLE), controllers, microcontrollers, microprocessors or other electronic components, to perform the above methods.

[00121] In exemplary embodiments, non-volatile computer readable media are also provided for storing information, including instructions, such as those included in a memory 202 executed by a processor 201.1 in the system 200, for performing the methods described above. For example, non-volatile computer-readable media for storing information may be ROM, RAM, ROM on a CD, magnetic tape, floppy disk, optical data storage device, and the like.

[00122] There is a non-volatile computer-readable medium for storing information, and when the instructions on the data medium are executed by the processor 201.1 of the system 200, and the system 200 is able to perform the information processing method described above.

[00123] It should be appreciated that the present invention is not limited to the precise construction or implementation that has been described above and illustrated in the accompanying drawings, and various modifications and changes can be made without departing from its scope. It is intended that the scope of the present invention be limited only by the appended claims.

Claims (18)

1. A computer-implemented method for centralized management of the operational day of a financial and credit organization, including the following steps: - form in the database using a data processing component containing one or more processors, a group of operating day statuses, within which current operational activities are carried out to conduct and support banking operations, and the group includes current, processed, scheduled, blocked, limited and closed trading day status; - form in the database using a data processing component containing one or more processors, a group of operating day procedures, the implementation of which is necessary to ensure the correct implementation of the operational day life cycle; - upon the occurrence of the current operational day, T + 1 is transferred to the database using the data processing component containing one or several processors, the previous calendar day T to the processed status to complete banking operations that began on calendar day T and did not end when it is switched from the current in processed status; while in the processed status in the database using the data processing component containing one or more processors, perform operations that are actually performed in the calendar day T + 1, but should be reflected in the day T - after completion of the processed status of the day T is transferred to the database using the data processing component containing one or more processors, the status of the operational day T is in the regulatory status to perform bulk operations from the above-mentioned group of procedures for the operational day; - after completing all the regulatory procedures performed in the previous step, the operational day T is transferred to the database using the data processing component containing one or more processors, the operational day T is in the blocked status, according to which a ban is placed on all operations with reflection in the operating bottom T; - perform in the database using the data processing component containing one or more processors, the routine and control procedures in the general ledger during the validity of the blocked status of the trading day, and in case of successful completion of control procedures in the general ledger, the status of the trading day T is automatically transferred to the closed status; in case of unsuccessful execution of control procedures in the general ledger, the status of the trading day T is automatically transferred to a limited status for performing adjustment operations. 2. The method according to p. 1, characterized in that for the generated list of procedures for the trading day, dependencies, the order and conditions of the launch are determined. 3. The method according to p. 1, characterized in that the processed status of the day T ends on the basis of a predetermined time. 4. The method according to p. 1, characterized in that the status of the working day changes on the basis of a pre-prepared schedule. 5. The method according to p. 1, characterized in that it additionally indicate the territorial units for which an agreed schedule of operating day procedures should be followed. 6. The method according to p. 1, characterized in that they indicate the control points of the procedures of the trading day. 7. The method according to p. 1, characterized in that they receive alerts when specified events occur. 8. The method according to p. 1, characterized in that they control the execution of the procedures of the business day using the dispatcher of the procedures of the business day with the ability to control a separate procedure. 9. The method according to p. 1, characterized in that they monitor the execution of the schedule of the operating day as a whole using the control panel.

Images