Bank account system 7*24 operation method and system

Abstract

The invention discloses a 7 * 24 operation method of a bank account system, and belongs to the technical field of data processing. The method comprises the following steps: acquiring business data; performing service scene distinguishing according to the service data to obtain a service scene distinguishing result; and updating the balance according to the service scene distinguishing result. Through the processing of the invention, 7 * 24 parallel online transaction and batch processing is thoroughly realized, through correct processing of single-form double balances, the problems of wrong downstream access, uneven total score check and the like caused by recovery or account balance data errors during batch processing period which are not supported by some banks are solved, the check completeness is improved, and the efficiency is improved. Banks are helped to improve technical innovation ability and good experience of customers.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method and system for operating a bank account system 24 / 7. Background Art

[0002] At present, after the day-end batch processing of the core banking system, the account amount data will be calculated and refreshed at the beginning of the day, such as: updating the overdue balance of the account, updating the previous day's balance of the account, accruing interest, issuing orders, etc. Generally, bank branches will complete the branch closing work before the core day-end batch processing. During the day-end batch processing, no teller will handle business, that is, no online request will be initiated from the counter, and the day-end batch processing will not be affected; some banks also perform verification control of online transactions during the day-end batch processing stage. Before the batch processing is executed, the verification that does not allow the initiation of online transactions is turned on, and after the batch processing is completed, the verification is turned off.

[0003] With the continuous development of banking business and the continuous advancement of financial technology, banks have gradually opened up a variety of electronic channels such as 24-hour self-service equipment, online banking, and mobile banking. At the same time, they have also connected to third-party channels such as payment and UnionPay. Since online requests can be initiated by users from online banking, 24-hour self-service equipment, mobile phones and other clients, the initiation time of online requests is different from that of branch tellers, and the request is very likely to occur during the core end-of-day batch processing. When online requests and batch processing read the same data before and after in the same time period and perform related calculations and update operations, the different calculation logics of online and batch processing will eventually lead to data update errors.

[0004] Based on the above situation, how to design a method and device for a bank account system to run 7×24 to support the storage and use of account balances in online transactions at the end-of-day batch stage, improve customer experience, improve the bank's control and accuracy of accounting data, and reduce the resource investment of the technology department has become a major pain point for the current bank accounting department. Summary of the invention

[0005] The purpose of the present invention is to provide a new method for operating a bank account system 24 / 7, improve the support for online transactions during batch processing, improve the completeness of accounting and the accuracy of data, enhance the bank's technological innovation capabilities, and reduce the impact and coupling of online transactions on batch transactions.

[0006] In order to solve the above technical problems, the present invention provides a method for operating a bank account system 24 / 7, comprising the following steps:

[0007] Get business data;

[0008] Differentiate business scenarios based on business data to obtain business scenario differentiation results;

[0009] Differentiate results based on business scenarios and update the previous day's balance.

[0010] Preferably, the business data includes a balance sheet;

[0011] The balance table includes the current balance, the previous day's balance, the transaction amount, the previous day's field update date, the current date and the balance type;

[0012] The balance types include recovered balance and overdue balance.

[0013] Preferably, business scenarios are distinguished according to business data to obtain business scenario distinction results, and the previous day's balance is updated according to the business scenario distinction results. Specifically, the following steps are included:

[0014] Determine the size of the last date field update date and the current date;

[0015] When the updated date of the previous day field is less than the current date, the previous day's balance is updated according to the balance type;

[0016] When the updated date of the previous day field is greater than the current date, the new previous day balance is calculated based on the previous day balance and transaction amount.

[0017] Preferably, updating the previous day's balance according to the balance type specifically includes the following steps:

[0018] When the balance type is overdue balance, the current balance will be calculated based on the current balance and transaction amount in the business data, and the current balance will be used as the new previous day balance;

[0019] When the balance type is recovery balance, the current balance will be used as the new previous day balance.

[0020] Preferably, after obtaining the business data, the following steps are also included:

[0021] Lock the balance table for query.

[0022] Preferably, the business data also includes a repayment plan table, a loan note table, a penalty interest accrual table and a compound interest accrual table.

[0023] Preferably, the method further comprises the following steps:

[0024] Perform end-of-day processing of repayment schedules, IOUs, and penalty interest accrual tables.

[0025] Preferably, the business data is processed at the end of the day, specifically including the following steps:

[0026] If the update date in the Last Date field is not empty and equal to the current date, or the due date or grace date in the repayment schedule is equal to the previous date and the document balance is greater than 0, there is no need to perform the overdue balance update; otherwise, perform the overdue balance update;

[0027] Automatically change the status of the household;

[0028] When the update date of the previous date field in the IOU table is not equal to the current date, update the previous date's IOU status and amount;

[0029] accrue interest;

[0030] When the principal repayment plan with the due date of the previous day in the repayment schedule has not been issued, issue the principal repayment order;

[0031] When the due date of the repayment schedule is the interest repayment schedule of the previous day, issue an interest bill;

[0032] If the penalty interest data with the previous interest settlement date in the penalty interest accrual table being the current time is not equal to 0 and no bill has been issued in the document table on the same day, a penalty interest bill will be issued;

[0033] When the compound interest data with the previous interest settlement date of the compound interest accrual table being the current time is not equal to 0 and no order has been issued in the document table of the day, compound interest order is issued;

[0034] When the update date of the Last Date field in the contract table is not equal to the current date, update the contract status of the last date.

[0035] The present invention also provides a method for operating a bank account system 24 / 7, including:

[0036] Acquisition module, used to acquire business data;

[0037] A business scenario identification module is used to distinguish business scenarios based on business data and obtain business scenario distinction results;

[0038] The update module is used to differentiate results according to business scenarios and update balances.

[0039] Compared with the prior art, the present invention has the following beneficial effects:

[0040] The present invention can improve the support level for online transactions during batch processing, improve the perfection of accounting and the accuracy of data, enhance the technical innovation capability of banks, and reduce the impact and coupling of online transactions on batch transactions.

[0041] The present invention can improve the perfection of the accounting system, reduce the impact of online transactions on data, and reduce the possibility of data errors caused by dirty reading of batch data. By replacing the idea of ​​batch processing of account end-of-day data and single-table double balances with online, the original fixed method of updating account balances in each stage is changed to a method of dynamically updating account balances according to account stages.

[0042] The processing of the present invention thoroughly realizes the 7×24 parallel operation of online transactions and batch processing. By correctly processing the double balances in a single table, it solves the pain points of downstream data retrieval errors and unequal total and sub-checking caused by some banks not supporting recovery during batch processing or errors in account balance data, improves the completeness of accounting, and helps banks enhance their technological innovation capabilities and customer experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The specific implementation modes of the present invention are further described in detail below with reference to the accompanying drawings.

[0044] Figure 1 It is a flowchart of online request and batch processing of accounts;

[0045] Figure 2 It is a flowchart of the method of operating the bank account system 7×24. DETAILED DESCRIPTION

[0046] Many specific details are set forth in the following description to facilitate a full understanding of the present invention. However, the present invention can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present invention, so the present invention is not limited to the specific implementation disclosed below.

[0047] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0048] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0049] The present invention is further described in detail below in conjunction with the accompanying drawings:

[0050] The present invention provides a method for operating a bank account system 24 / 7:

[0051] In the online recovery transactions initiated during the batch execution phase, it is necessary to provide account and balance locks, and update the previous day's balance according to different scenarios to ensure the accuracy of the data. For the verification of inconsistent transaction dates, according to the account end-of-day execution phase, online instead of batch execution of account end-of-day processing is performed, and then the subsequent business functions are executed.

[0052] According to the analysis of the initiation time and execution time of online transactions, the technical solution is mainly divided into the following three points:

[0053] Table 1

[0054]

[0055] Note: The time before the loan date is called T day, and the time after the loan date is called T+1 day.

[0056] During online recovery, when obtaining account information, the retrieved data is locked at the row level. The purpose is to ensure that when an online transaction is initiated, batch reading and modification of the account data is not allowed, and the normal execution of batch operations of other accounts must be guaranteed during the execution process.

[0057] like Figure 1 As shown, online recovery and overdue balance update share the AcctTransactionUnit component, and the balance table is locked when updating it, and an action to update the previous day's balance is added to the AcctTransactionUnit component to ensure the accuracy of the balance data before and after recovery.

[0058] Regarding how to trigger the balance update component to perform the balance rollover process, it is necessary to obtain the balance table information, add a row lock, and distinguish by obtaining the previous day's field update date prevDayUpdDate and the current transaction system date runDate on the balance table; based on the relationship between prevDayUpdDate (previous day's field update date) and runDate (current date) in the balance table, perform the balance rollover before and after the transaction.

[0059] Set flags: isUpdPrevBalAfterTran (whether to roll over the balance after the transaction), hasUpdPrevBal (whether the balance has been rolled over). When isUpdPrevBalAfterTran is true, it is an overdue balance update scenario. Calculate the current balance based on the current balance and the transaction amount, and use this current balance as the previous day's balance. When hasUpdPrevBal is true, that is, when prevDayUpdDate > runDate, calculate the new previous day's balance based on the previous day's balance and the transaction amount. When prevDayUpdDate < runDate, update the previous day's balance with the retrieved balance data before the transaction.

[0060] Regarding the date inconsistency problem caused by the journal engine callback for the recovery initiated on T day for T+1 day, it is provided by the transaction business pre-check (CheckSysDate). When the system header time is inconsistent with the current system time, an error of inconsistent transaction date is thrown.

[0061] For the recovery on T+1 day, when the batch process happens to reach the account end-of-day stage, the online recovery transaction needs to judge the account end-of-day status flag and execute the account end-of-day processing device to perform the online replacement of the batch processing end-of-day actions. The provided account end-of-day device includes the following:

[0062] a. Overdue balance update;

[0063] b. Automatic change processing of the sub-account status;

[0064] c. Update the previous day's note status and amount;

[0065] d. Interest accrual;

[0066] e. Principal bill issuance;

[0067] f. Interest bill issuance;

[0068] g. Penalty interest bill issuance;

[0069] h. Compound interest bill issuance;

[0070] i. Update the previous day's contract status;

[0071] The account end-of-day device can identify the remaining end-of-day stages that need to be executed, and after verification and inspection, it replaces the batch execution of subsequent end-of-day processing, that is, the batch business processing is completed, ensuring the accuracy of the data. When the subsequent account end-of-day batch processing is executed to the account, it can be directly skipped according to the verification and inspection. For an account, whether the account end-of-day processing is triggered online or batch on an accounting day, although the account end-of-day component will be repeatedly entered, the actual business execution logic is only once. That is, online batch parallelism 7*24 is realized.

[0072] In order to make the purpose, technical solution and advantages of the embodiments of the present invention more clear and understandable, the embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the invention, but are not intended to limit the present invention.

[0073] In view of the problem of inaccurate processing of account balance sheets when online transactions update balances during batch processing in the prior art, the present invention changes the original [fixed] method of updating account balances at each stage to a [dynamic] method of updating account balances at the end-of-day stage of the account, thereby improving the accuracy of balance calculation in financial business scenarios and expanding the processing of the end-of-day stage of the account, including but not limited to overdue balance update, principal bill issuance, interest bill issuance, penalty interest bill issuance, compound interest bill issuance and other stages.

[0074] In order to better illustrate the technical effect of the present invention, the present invention provides the following specific embodiments to illustrate the above technical process:

[0075] Embodiment 1, as Figure 2 As shown, the method for operating the bank account system 7×24 in an embodiment of the present invention may include the following steps:

[0076] Step S110: Obtaining business data online

[0077] Before the online transaction initiates the recovery, the recovery document query is called, in which the recovery information such as account and document is obtained, and the account day-end stage is judged. If it is matched, the account day-end device is called here, and the online instead of batch execution day-end processing is performed, and the latest document is returned for recovery.

[0078] Step S120: Account end-of-day device

[0079] The device consists of 9 nodes for account day-end processing. The nodes are executed according to the order of the account day-end stages. Before executing each node, it will check whether the account needs to execute the node. The check rules for all stages are shown in Table 2:

[0080] Table 2

[0081]

[0082]

[0083] The above-mentioned balance table, repayment plan table, penalty interest accrual table, compound interest accrual table, contract table, etc. are all included in the business data.

[0084] Step S130: Balance flipping scenario distinction

[0085] Before updating the balance, first lock the query, and then compare the update date with the current date based on the previous day field in the balance table:

[0086] If the update date of the previous day field in the balance table is less than the current date, it means that the system has been cut off and the account has not been batch processed. Since the accounting component is a common component for recovery and overdue balance update, it is necessary to distinguish the calling scenarios at this time. If it is an overdue balance update, the isUpdPrevBalAfterTran (whether to turn over the balance after the transaction) flag will be assigned a value of true, and the current balance will be calculated based on the current balance and transaction amount in the business data, and the current balance will be used as the previous day's balance; if it is a recovery balance update, the isUpdPrevBalAfterTran (whether to turn over the balance after the transaction) flag is not true, and the current balance in the business data will be used as the previous day's balance;

[0087] If the update date of the previous day field in the balance table is greater than the current date, it means that the transaction was initiated on day T, but the system has switched to day T+1, and the account has been reversed. The isUpdPrevBalAfterTran (whether to reverse the balance after the transaction) flag is assigned a value of true, and the new previous day balance is calculated based on the previous day balance and the transaction amount.

[0088] If they are equal, the previous day's balance will not be processed.

[0089] Step S140: balance calculation update;

[0090] The balance information of the corresponding amount type in the account balance table is updated based on the result of step S130.

[0091] According to whether the balance flag is turned over after the transaction, the balance of the current amount type is updated to the balance of the previous day; according to whether the balance flag has been turned over, the incremental amount of the amount type is updated to the balance of the previous day;

[0092] The business data is obtained online through step S110. Before initiating online recovery, the latest document that may be processed after the account end of day is obtained through recovery document query to ensure the consistency of the queried and recovered documents.

[0093] Through step S120, the account day-end device triggers online processing instead of batch processing of account day-end data, thereby preventing dirty reading of batch data or data errors caused by overwriting online transaction results, and reducing repeated execution and calculation of batch data on single account day-end data.

[0094] The balance reversal scenarios are distinguished through step S130, the date of the previous day field is updated, and the flag of whether to reverse the balance after the transaction is used to distinguish the currently called business scenario, and calculate different flags of the calculation logic for updating the previous day field. In step S140, the current balance and the previous day balance are correctly updated to ensure the accuracy of the data, laying the foundation for the subsequent total score verification.

[0095] The present invention aims to provide a new method for 7×24 operation of a bank account system, improve the perfection of the accounting system, reduce the impact of online transactions on data, and reduce the possibility of data errors caused by dirty reading of batch data. By replacing the idea of ​​batch processing of account end-of-day data and single-table double balances with online, the original fixed method of updating account balances in each stage is changed to a method of dynamically updating account balances according to account stages.

[0096] Account end-of-day device: Establish a complete component for account end-of-day processing, provide methods such as whether to execute verification and execution logic, provide it for online and batch use, ensure the consistency of processing logic, and participate in the account end-of-day data processing and update.

[0097] Differentiate between balance reversal scenarios: Calculate whether the balance has been reversed by comparing the previous day's field update date with the current date, and whether the overdue balance is updated and marked to reverse the balance after the transaction, and distinguish the calculation logic of the current balance and previous day's balance fields of the amount type to ensure the accuracy of the balance.

[0098] In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules, modules or units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units, modules or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0099] The units may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0100] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0101] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part, and / or installed from a removable medium. When the computer program is executed by the central processing unit (CPU), the above-mentioned functions defined in the method of the present invention are executed. It should be noted that the above-mentioned computer-readable medium of the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, a system, device or device of an electrical, magnetic, optical, electromagnetic, infrared segment, or semiconductor, or any combination of the above.

[0102] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0103] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for operating a bank account system 24 / 7, characterized in that: The following steps are involved: Get business data; Differentiate business scenarios based on business data to obtain business scenario differentiation results; Differentiate results based on business scenarios and update the previous day's balance.

2. The method for operating a bank account system 24 / 7 according to claim 1, characterized in that: The business data includes a balance sheet; The balance table includes the current balance, the previous day's balance, the transaction amount, the previous day's field update date, the current date and the balance type; The balance types include recovered balance and overdue balance.

3. The method for operating a bank account system 24 / 7 according to claim 2, characterized in that: Differentiate business scenarios based on business data, obtain business scenario differentiation results, and update the previous day's balance based on the business scenario differentiation results; The specific steps include: Determine the size of the last date field update date and the current date; When the updated date of the previous day field is less than the current date, the previous day's balance is updated according to the balance type; When the updated date of the previous day field is greater than the current date, the new previous day balance is calculated based on the previous day balance and transaction amount.

4. The method for operating a bank account system 7×24 according to claim 3, characterized in that: Update the previous day's balance according to the balance type, including the following steps: When the balance type is overdue balance, the current balance will be calculated based on the current balance and transaction amount in the business data, and the current balance will be used as the new previous day balance; When the balance type is recovery balance, the current balance will be used as the new previous day balance.

5. The method for operating a bank account system 7×24 according to claim 4, characterized in that: After obtaining the business data, the following steps are also included: Lock the balance table for query.

6. The method for operating a bank account system 24 / 7 according to claim 5, characterized in that: The business data also includes a repayment plan table, a loan note table, a penalty interest accrual table and a compound interest accrual table.

7. The method for 7×24 operation of a bank account system according to claim 6, characterized in that: The following steps are also included: Perform end-of-day processing of repayment schedules, IOUs, and penalty interest accrual tables.

8. The method for 7×24 operation of a bank account system according to claim 7, characterized in that: The end-of-day processing of business data includes the following steps: If the update date in the Last Date field is not empty and equal to the current date, or the due date or grace date in the repayment schedule is equal to the previous date and the document balance is greater than 0, there is no need to perform the overdue balance update; otherwise, perform the overdue balance update; Automatically change the status of the household; When the update date of the previous date field in the IOU table is not equal to the current date, update the previous date's IOU status and amount; accrue interest; When the principal repayment plan with the due date of the previous day in the repayment schedule has not been issued, issue the principal repayment order; When the due date of the repayment schedule is the interest repayment schedule of the previous day, issue an interest bill; If the penalty interest data with the previous interest settlement date in the penalty interest accrual table being the current time is not equal to 0 and no bill has been issued in the document table on the same day, a penalty interest bill will be issued; When the compound interest data with the previous interest settlement date of the compound interest accrual table being the current time is not equal to 0 and no order has been issued in the document table of the day, compound interest order is issued; When the update date of the Last Date field in the contract table is not equal to the current date, update the contract status of the last date.

9. A method for operating a bank account system 24 / 7, used to implement the system for operating a bank account system 24 / 7 as claimed in any one of claims 1 to 8, characterized in that: include: Acquisition module, used to acquire business data; A business scenario identification module is used to distinguish business scenarios based on business data and obtain business scenario distinction results; The update module is used to differentiate results according to business scenarios and update balances.

Images