Tail box data processing method and device, equipment and medium
By decoupled the data update function in the bank trading system, determine and update the target tailbox data according to the transaction information, solve the problem of high -end box data update and the transaction system coupling Independent development and maintenance of management and update functions.
Patent Information
- Application Number
- CN202411587606.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-08
- Publication Date
- 2025-01-28
AI Technical Summary
In the prior art, the bank teller's trunk data update function has a high coupling with each transaction system, which makes it impossible to develop and maintain individually, and the accounting information related to the trunk cannot be managed uniformly.
After receiving the transaction information sent by the transaction system, determine the target tail box from multiple tail boxes from multiple tail boxes according to the transaction information, and update the data in the target tail box. Management and update function decoupling.
The uniform management of account information related to the tail box is realized, and at the same time, it allows separate development and maintenance of the tail box update function module to improve the flexibility and maintenance efficiency of the system.
Smart Images
Figure CN119379442A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of distributed systems, and in particular to a method, device, equipment and medium for processing tail box data. Background Art
[0002] Many transaction systems of banks may handle cash business, such as deposit system, cash withdrawal system, etc. When these transaction systems handle cash business, they all involve the data update of bank teller's tail box.
[0003] In the prior art, when a cash transaction occurs in each transaction system, the transaction systems corresponding to different transaction types update the tail box respectively, and the tail box update function has a high coupling with different transaction systems.
[0004] However, this is not conducive to the development and maintenance of the trunk update function module, and it is impossible to uniformly manage the accounting information related to the trunk. Summary of the invention
[0005] The embodiments of the present application provide a method, device, equipment and medium for processing tail box data, so as to achieve the technical effect of realizing unified management of tail box related accounting information while also being able to independently develop and maintain the tail box update function module.
[0006] In a first aspect, an embodiment of the present application provides a method for processing tail box data, which is applied to a device for processing tail box data, and the device for processing tail box data establishes data connections with multiple transaction systems and multiple tail boxes respectively; the method includes:
[0007] After receiving the transaction information sent by any transaction system, a target tail box to be updated is determined from multiple tail boxes according to the transaction information;
[0008] Update the data in the target tail box according to the transaction information.
[0009] In one possible implementation, the transaction information includes a teller identification and a currency type;
[0010] Accordingly, a target tail box to be updated is determined from multiple tail boxes according to the transaction information, including:
[0011] According to the teller ID and the currency type, as well as the pre-stored mapping relationship between the teller and the tail box, the target tail box corresponding to the teller ID is determined.
[0012] In a possible implementation, the transaction information also includes the trunk update direction and the transaction amount;
[0013] Correspondingly, the transaction information updates the data in the target tail box, including:
[0014] If the tail box update direction is tail box increase, determine whether the transaction amount meets the preset minimum ticket constraint condition;
[0015] If the transaction amount meets the minimum face value constraint, the target tail box is updated based on the transaction information;
[0016] If the transaction amount does not meet the minimum face value constraint, an error message will be returned to the transaction system.
[0017] In a possible implementation, it further includes:
[0018] If the tail box update direction is tail box reduction, determine whether the currency type is foreign currency;
[0019] If the currency type is foreign currency, determine whether there is an amount that needs to be returned based on the minimum face value constraint;
[0020] If there is no amount to be returned, the target tail box is updated by reducing the tail box according to the transaction information;
[0021] If there is an amount that needs to be returned, the tail box reduction update operation is performed on the target tail box according to the amount that needs to be returned and the transaction information.
[0022] In a possible implementation, the method further includes:
[0023] After the target tail box is updated, the transaction information and the account information involved in updating the target tail box are stored.
[0024] In a possible implementation, the method further includes:
[0025] After the target tail box is updated, the tail box update result information is returned to the transaction system.
[0026] In a possible implementation manner, the transaction information further includes:
[0027] Institution identification, transaction type and counterparty account;
[0028] Among them, transaction types include normal transactions and reversal transactions.
[0029] In one possible implementation,
[0030] In a second aspect, an embodiment of the present application provides a device for processing tail box data, wherein the device for processing tail box data establishes data connections with multiple transaction systems and multiple tail boxes respectively; the device comprises:
[0031] A first processing module is used to determine a target tail box to be updated from multiple tail boxes according to the transaction information after receiving the transaction information sent by any transaction system;
[0032] The second processing module is used to update the data in the target tail box according to the transaction information.
[0033] In a possible implementation manner, the first processing module is specifically configured to determine the target tail box corresponding to the teller identification according to the teller identification and a pre-stored mapping relationship between the teller and the tail box.
[0034] In a possible implementation manner, the second processing module is specifically configured to:
[0035] If the tail box update direction is tail box increase, determine whether the transaction amount meets the preset minimum ticket constraint condition;
[0036] If the transaction amount meets the minimum face value constraint, the target tail box is updated based on the transaction information;
[0037] If the transaction amount does not meet the minimum face value constraint, an error message will be returned to the transaction system.
[0038] In a possible implementation manner, the second processing module is specifically configured to:
[0039] If the tail box update direction is tail box reduction, determine whether the currency type is foreign currency;
[0040] If the currency type is foreign currency, determine whether there is an amount that needs to be returned based on the minimum face value constraint;
[0041] If there is no amount to be returned, the target tail box is updated by reducing the tail box according to the transaction information;
[0042] If there is an amount that needs to be returned, the target trunk is updated to reduce the amount according to the amount to be returned and the transaction information.
[0043] In a possible implementation manner, the device for processing the trunk data further includes:
[0044] Storage module: used to store transaction information and account information involved in updating the target tail box after the target tail box is updated.
[0045] Return module: used to return the tail box update result information to the trading system after completing the update of the target tail box.
[0046] In a third aspect, an embodiment of the present application provides a device for processing trunk data, including: a memory, a processor;
[0047] The memory stores computer-executable instructions;
[0048] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.
[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.
[0050] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.
[0051] The method, device, equipment and medium for processing tail box data provided in the embodiments of the present application, after receiving transaction information sent by any transaction system, determine the target tail box to be updated from multiple tail boxes according to the transaction information, and update the data in the target tail box according to the transaction information, so as to achieve the technical effect of realizing unified management of the account information related to the tail box while independently developing and maintaining the tail box update function module. BRIEF DESCRIPTION OF THE DRAWINGS
[0052] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0053] Figure 1 A schematic diagram of a scenario of a method for processing trunk data provided in this application;
[0054] Figure 2 A flowchart of a first embodiment of a method for processing trunk data provided by the present application;
[0055] Figure 3 A flowchart of a second embodiment of the method for processing tail box data provided by the present application;
[0056] Figure 4 A flowchart of a specific embodiment of the method for processing tail box data provided by the present application;
[0057] Figure 5 A schematic diagram of the structure of a first embodiment of a device for processing trunk data provided by the present application;
[0058] Figure 6 A schematic diagram of the structure of a second embodiment of a device for processing trunk data provided by the present application;
[0059] Figure 7 A schematic diagram of the structure of the trunk data processing device provided in this application.
[0060] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0061] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0062] First, the terms involved in this application are explained:
[0063] Tail box data: Tail box refers to the personal virtual vault corresponding to the cash banknotes in the name of the bank teller on the bank system, or a virtual small warehouse used to count the specific transaction operations of the teller. Tail box data includes the cash data records kept by each teller and the transaction records of the teller when handling cash business. Generally, in order to facilitate statistics, the bank stores the tail box data of each teller in a centralized manner.
[0064] Face value: Face value refers to the physical face value of each currency type corresponding to the cash. For example, the face value of RMB is 1 yuan, 5 yuan, 10 yuan, 100 yuan, etc.
[0065] Change: When a customer withdraws foreign currency cash, if there is a small amount in the amount that cannot be paid in full foreign currency units, the bank will usually choose to convert the small amount into RMB and pay the customer. This is a common operation method for foreign currency change business.
[0066] Reversal transaction: In the banking system, reversal operations are often used to correct incorrect transfer records. When a customer finds that the transfer amount is incorrect or the receiving account information is incorrect, he or she can request the bank to perform a reversal operation to transfer the incorrect funds back to the original account.
[0067] In order to clearly understand the technical solution of the present application, the solution of the prior art is introduced in detail below.
[0068] With the continuous development of information technology, the business functions of banks are becoming more and more complex, and more and more transaction systems are involved. These transaction systems may all involve the same type of business, such as cash business. When these transaction systems are to process cash transactions, they all need to perform tail box data processing operations. In the prior art, the update operation of cash tail box data is coupled to these transaction systems and is part of the functional logic when the transaction system processes cash business. The tail box data update function module is highly coupled with each transaction system and cannot be functionally used, so it is impossible to develop and maintain this function module separately. In addition, for the business department responsible for managing the tail box data, the existing tail box update method cannot uniformly manage and calculate the account information related to the tail box, causing inconvenience to the business analysis link of the bank.
[0069] In addition, in order to facilitate centralized management, banks generally store teller trunk data in a centralized manner. Therefore, the processing mechanism of trunk data involving multiple systems is an issue that needs to be considered.
[0070] Figure 1 A schematic diagram of a scenario of a method for processing trunk data provided in this application, such as Figure 1 As shown, the network architecture of the application scenario of the method for processing tail box data provided by the embodiment of the present invention includes: transaction system 101 and transaction system 102, a processing device 103 for tail box data, and tail boxes 104, 105, and 106. When a bank has cash business, the teller enters information such as the transaction amount and currency type in the transaction system 101 or the transaction system 102; after the function call of the transaction system, the transaction system 101 or the transaction system 202 sends various transaction information to the processing device for tail box data through the data connection; after receiving the transaction information sent by the cash withdrawal transaction system 1 or the transaction system 103, the processing device for tail box data determines the target tail box to be updated from the tail box 104 / tail box 105 / tail box 106 according to the transaction information, and updates the tail box data corresponding to the target tail box. Among them, the target tail box is the tail box corresponding to the teller being operated.
[0071] In combination with the above scenarios, it can be seen that the method for processing tail box data provided by the present application is applied to a tail box data processing device that establishes data connections with multiple transaction systems and multiple tail boxes. After a function call is made to the tail box data processing device in any transaction system and transaction information is sent, the tail box data processing device receives the transaction information, determines the target tail box to be updated from multiple tail boxes according to the transaction information, and updates the data in the target tail box. This solves the technical problem that the existing technology cannot independently develop and maintain the function module for updating tail box data, and the relevant business departments cannot uniformly manage the accounting information related to the tail boxes.
[0072] It should be noted that the method, device, equipment and medium for processing tail box data of the present application can be used in the distributed field, and can also be used in any field other than the distributed field, such as the financial field. The application field of the method, device, equipment and medium for processing tail box data of the present application is not limited.
[0073] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0074] Figure 2 This is a flow chart of the first embodiment of the method for processing tail box data provided by the present application. The method is applied to a device for processing tail box data. The device for processing tail box data establishes data connections with multiple transaction systems and multiple tail boxes respectively. Figure 2 As shown, the method includes:
[0075] S201, after receiving transaction information sent by any transaction system, determining a target tail box to be updated from the multiple tail boxes according to the transaction information;
[0076] In this solution, the method for processing tail box data provided by this solution is applied to a tail box data processing device. When a customer performs various cash transactions such as account withdrawals and bill transactions at a bank, the teller will determine the corresponding transaction system to be operated according to the type of transaction. For any transaction system that processes cash transactions, the transaction system sends the relevant transaction information generated by the cash transaction to the tail box data processing device through function calls; the tail box data processing device determines the tail box to be updated based on the received transaction information, and updates the data of the tail box.
[0077] In this step, the transaction system may be a transaction system that can perform cash business, such as a cash withdrawal transaction system, a deposit transaction system, a bill transaction system, etc. The content of the transaction information is determined according to the actual business situation. For example, the transaction information may include the teller identification, the tail box update direction, the transaction amount, the currency type, etc. The tail box data processing device analyzes the received transaction information and determines the target tail box to be updated according to the identification information in the transaction information that has a corresponding relationship with the tail box.
[0078] In one possible implementation, the transaction information includes a teller ID and a currency type. Accordingly, a target tail box to be updated is determined from multiple tail boxes based on the transaction information. The target tail box corresponding to the teller ID can be determined based on the teller ID and the currency type, as well as a pre-stored mapping relationship between the teller and the tail box.
[0079] The teller ID is used to indicate the teller who operates the transaction system, and one teller corresponds to one teller ID. Generally, one teller ID can determine one or more corresponding tail boxes, and the number of tail boxes corresponding to one teller ID is determined according to the number of currency types that the teller is responsible for managing. The mapping relationship between the teller and the tail box is pre-stored in the database. For a teller, the mapping relationship between the teller and the tail box is used to indicate one or more tail boxes corresponding to the teller. It should be noted that the multiple tail boxes corresponding to the teller are only managed by the teller.
[0080] Specifically, it should be understood that in a bank, a teller may be responsible for managing multiple currency types. Accordingly, when a teller is responsible for handling cash business of multiple currency types, the teller ID of the teller corresponds to multiple tail boxes. Therefore, after determining the multiple tail boxes corresponding to the teller according to the teller ID and the pre-stored mapping relationship between the teller and the tail box, it is also necessary to determine the target tail box to be updated from the multiple tail boxes corresponding to the teller according to the currency type in the transaction information.
[0081] For example, the teller ID of a certain teller is 047, and the teller is responsible for RMB business and USD business. Therefore, when the teller handles RMB business, it is necessary to determine the target tail box corresponding to "Teller ID-047" as the RMB tail box corresponding to the teller from the RMB tail box and USD tail box corresponding to the teller based on "Teller ID-047" and "Currency Type-RMB", as well as the mapping relationship between the teller and the tail box.
[0082] S202: Update the data in the target trunk according to the transaction information
[0083] In this step, after the tail box to be updated is determined according to the teller identification and currency type in the transaction information, how to update the target tail box is determined according to other information in the transaction information.
[0084] The method for processing tail box data provided in this embodiment is applied to a tail box data processing device that establishes data connection with multiple transaction systems and multiple tail boxes. After receiving transaction information sent by any transaction system, the target tail box to be updated is determined from the multiple tail boxes according to the transaction information, and the data in the target tail box is updated according to the transaction information. In this embodiment, the function module of tail box data update is decoupled from each transaction system, which is convenient for subsequent independent development and maintenance of the function module. In addition, since this solution separates the tail box data processing device from other transaction systems, the relevant account information of the tail box update (such as the increase or decrease of the cash amount in the tail box) and other account information (such as the deposit and withdrawal of the amount in the customer account) are separated, which facilitates the statistical processing of the relevant business departments.
[0085] Figure 3 A flowchart of a second embodiment of the method for processing tail box data provided by the present application is shown in FIG. Figure 3 As shown, in a specific implementation, the transaction information also includes the tail box update direction and the transaction amount. Accordingly, the data in the target tail box is updated according to the transaction information, including:
[0086] S301. Determine a trunk update method according to a trunk update direction.
[0087] S302: If the tail box update direction is tail box increase, determine whether the transaction amount meets the preset minimum ticket face constraint condition.
[0088] S303: If the transaction amount meets the minimum bill constraint, the target tail box is updated based on the transaction information.
[0089] S304: If the transaction amount does not satisfy the minimum face value constraint, an error message is returned to the transaction system.
[0090] In the above steps, the transaction information also includes the tail box update direction and the transaction amount. The tail box update direction is used to indicate the increase or decrease of the tail box. When money is deposited into the tail box, the tail box update direction corresponds to the increase of the tail box; correspondingly, when money is taken out of the tail box, the tail box update direction corresponds to the decrease of the tail box. The transaction amount corresponds to the amount of the tail box increase or the amount of the tail box decrease.
[0091] It should be understood that before the tail box is updated according to the transaction information, the minimum face value constraint condition needs to be pre-set. The minimum face value constraint condition limits the face value information of the transaction. Among them, the minimum face value constraint condition is determined by the pre-set parameter information such as the minimum face value of each currency type. It should be understood that the parameter information only needs to be pre-set once. Generally, the minimum face value of each currency type corresponds to the minimum denomination of the cash of the corresponding currency type that the bank can provide. For example, the minimum face value of RMB is set to 10 cents; the minimum face value of US dollars is set to 1 US dollar.
[0092] Specifically, when the tail box is increased, that is, when external cash needs to be deposited into the tail box, it is necessary to check whether the transaction amount submitted meets the minimum face value conditions supported by the bank's business. If the transaction amount submitted meets the minimum face value conditions supported by the bank's business, the data of the determined target tail box will be added; if the transaction amount submitted does not meet the minimum face value conditions supported by the bank's business, an error prompt message will be returned to the transaction system, and the target tail box will not be updated.
[0093] For example, when a customer deposits money into a bank, if the deposited amount contains denominations that are not supported by the bank's business, such as depositing $5.3 into the bank, of which $0.3 is a denomination that is not supported by the bank's business, an error message is returned to the transaction system and the target tail box is not updated.
[0094] In a specific implementation, updating the data in the target tail box according to the transaction information also includes:
[0095] S305: If the tail box update direction is tail box reduction, determine whether the currency type is foreign currency.
[0096] S306: If the currency type is not a foreign currency, a tail box reduction and update operation is performed on the target tail box according to the transaction information.
[0097] S307. If the currency type is foreign currency, determine whether there is an amount that needs to be returned based on the minimum face value constraint.
[0098] S308: If there is no amount to be returned, a tail box reduction and update operation is performed on the target tail box according to the transaction information;
[0099] S309: If there is an amount that needs to be returned, a tail box reduction and update operation is performed on the target tail box according to the amount that needs to be returned and the transaction information.
[0100] In the above steps, when the tail box is reduced, the currency type of the transaction needs to be judged. If the currency type of the transaction is RMB, the tail box is directly reduced and updated. When the currency type of the transaction is foreign currency (currencies other than RMB are all foreign currencies), it is necessary to determine whether the bank needs to make change based on the minimum face value constraint corresponding to the currency type of the transaction, that is, to determine whether there is an amount that needs to be returned:
[0101] If there is no amount to be returned, the target tail box will be directly reduced and updated according to the transaction amount in the transaction information; if there is an amount to be returned, the target tail box will be updated according to the returned amount and the transaction amount in the transaction information. Since the bank needs to make change in this case, the foreign currency tail box and RMB tail box corresponding to the teller need to be reduced and updated at the same time.
[0102] Exemplarily, when a customer withdraws foreign currency cash, if there is a fraction that cannot be paid in full foreign currency units in the withdrawn amount, then change is required at this time. Further, it is necessary to calculate the RMB amount corresponding to the foreign currency fraction based on the customer's transaction amount and foreign currency fraction. After paying the corresponding amount of foreign currency and RMB to the customer, the RMB tail box and foreign currency tail box corresponding to the teller are reduced and updated. For example, if a customer withdraws $5.28 from the bank, the teller will pay the customer $5 and RMB 2, and the teller's corresponding US dollar tail box data and RMB tail box data will both be reduced.
[0103] The method for processing tail box data provided in this embodiment proposes a specific tail box update strategy for transactions with increased or decreased tail boxes according to the tail box update direction, transaction amount, and currency type in the transaction information. The method provided in this embodiment provides a specific implementation method for determining the tail box update method based on transaction information, fully considering factors such as foreign currency transactions and ticket information in the transaction process, and improving the tail box update service mechanism of this solution. The application of this method enables other transaction systems to provide more comprehensive tail box update strategies to other transaction systems when they make function calls to the tail box data processing device, thereby improving the independence, flexibility, and comprehensiveness of the tail box data processing device.
[0104] On the basis of the above embodiments, the method for processing trunk data provided by the present application also includes the following contents:
[0105] In a specific implementation, the transaction information also includes: institution identification, transaction type and counterparty account; wherein the transaction type includes normal transaction and reversal transaction.
[0106] It should be understood that in one embodiment, the target tail box to be updated can be determined based on the institution identification, teller identification and currency type. This embodiment adds the transaction information of the institution identification, improves the execution effect of the tail box data update, reduces the difficulty of the teller identification design, and further facilitates the unified management of the account information of the tail box update design.
[0107] In addition, transaction types are divided into normal transactions and reversal transactions, wherein a reversal transaction is a reverse operation on an erroneous or non-compliant transaction that has already occurred, in order to correct the error and restore the correct account record. Therefore, in one embodiment, if the transaction type in the transaction information is a reversal transaction, the impact of the original transaction on the tail box data needs to be revoked. For example, if a customer has reversed a previous withdrawal transaction, it is necessary to cancel the impact of the previous withdrawal transaction on the tail box data, that is, this transaction needs to increase the corresponding amount of the tail box that has been reduced and updated by the previous transaction. This embodiment introduces the transaction type as transaction information, takes into account the reversal transaction situation that exists in the transaction process, and further improves and enriches the tail box update mechanism provided by this application.
[0108] In one implementation, the counterparty account may be a customer's bank account, which is used to assist in recording account information.
[0109] In a specific implementation, after the target tail box is updated, the transaction information and the account information involved in updating the target tail box are stored.
[0110] The transaction information and the account information involved in updating the target trunk are stored in the following form:
[0111] If cash is deposited into the tail box, that is, when the tail box data increases, the account information is recorded as "debit: cash account, credit: counterparty account" and stored in the database; if cash is taken out of the target tail box, that is, when the target tail box data decreases, the account information corresponding to the target tail box is recorded as "debit: counterparty account, credit: cash account" and stored in the database; the cash amount is not necessarily the transaction amount, but the actual increase or decrease amount corresponding to the target tail box. This implementation method is used to store the account information involved in updating the target tail box, which is convenient for the subsequent related business parts to process the related accounts, and the record of the account information is clearer and more explicit.
[0112] In a specific implementation, after the target tail box is updated, the tail box update result information is returned to the transaction system.
[0113] Specifically, the tail box update result information may include: unsuccessful update / failed tail box update, and the corresponding target tail box update amount when the tail box update is successful. For example, when a customer withdraws $5.27, if the tail box update is successful, the returned tail box update result information includes: "tail box update successful" and "RMB tail box deducted 2 yuan, USD tail box deducted 5 dollars".
[0114] Figure 4The flowchart of a specific embodiment of the method for processing tail box data provided by the present application is a schematic diagram of a method for processing tail box data in a specific embodiment of the present application, wherein the method is applied to a device for processing tail box data that establishes data connections with multiple transaction systems and multiple tail boxes, such as Figure 4 As shown, the method includes:
[0115] S401. Set the minimum denomination and other information of different currencies.
[0116] S402, message processing. Receive the tail box update service message and analyze the tail box update service message, wherein the tail box update service message format is "institution number|teller number|currency|update direction|transaction type|amount|counterparty account". Specifically, the update direction includes tail box increase and tail box decrease; the transaction type includes normal transaction and reversal transaction.
[0117] S403: Transaction processing.
[0118] According to the "institution", "teller number" and "currency" information in the message, the tail box data to be changed is determined, that is, the target tail box is determined;
[0119] According to the "update direction" and "transaction type" information in the message, determine the tail box update processing flow. Specifically, when adding a tail box, check whether the amount sent meets the minimum denomination supported by the bank's business. If not, report an error and reject; if it meets, perform the tail box increase and update operation. When reducing the tail box, determine whether the transaction type is foreign currency. If not, directly perform the tail box reduction and update operation on the tail box; if it is foreign currency, perform change calculation processing. If the foreign currency change amount is not 0 (there is an amount that needs to be returned), the foreign currency change amount needs to be converted into RMB, and the tail box reduction and update operation is performed on the RMB tail box and foreign currency tail box corresponding to the teller at the same time.
[0120] S404: Return a service result message.
[0121] S405, transaction account processing. Based on the transaction data obtained in S403, such as the amount of increase or decrease in the tail box, process and record the account information involved in the tail box update service. Specifically, one party of the cash transaction account is the cash account, and the other party is specified by the counterparty account in the transaction data. Among them, when cash is deposited, it is recorded as "debit: cash account, credit: counterparty account" and when cash is withdrawn, it is recorded as "debit: counterparty account, credit: cash account".
[0122] The method for processing tail box data provided in this embodiment receives and analyzes the message information sent by the transaction system, determines the tail box to be updated according to the message information, and updates the tail box data. The tail box data update function module is decoupled from each transaction system, which facilitates the subsequent independent development and maintenance of the function module. In addition, since the solution separates the relevant account information of the tail box data processing from other account information, such as customer account deposit and withdrawal information, it facilitates the statistical processing of the relevant business departments.
[0123] Figure 5 This is a structural diagram of a first embodiment of a device for processing trunk data provided by the present application, as shown in FIG. Figure 5 As shown, the tail box data processing device 50 provided in this embodiment includes:
[0124] The first processing module 501 is used to determine a target tail box to be updated from multiple tail boxes according to the transaction information after receiving the transaction information sent by any transaction system;
[0125] The second processing module 502 is used to update the data in the target tail box according to the transaction information.
[0126] The device 50 for processing trunk data provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, which will not be described in detail in this embodiment.
[0127] In a possible implementation, the first processing module 501 is specifically configured to determine the target tail box corresponding to the teller identification according to the teller identification and a pre-stored mapping relationship between the teller and the tail box.
[0128] In a possible implementation manner, the second processing module 502 is specifically configured to:
[0129] If the tail box update direction is tail box increase, determine whether the transaction amount meets the preset minimum ticket constraint condition;
[0130] If the transaction amount meets the minimum face value constraint, the target tail box is updated based on the transaction information;
[0131] If the transaction amount does not meet the minimum face value constraint, an error message will be returned to the transaction system.
[0132] In a possible implementation manner, the second processing module 502 is specifically configured to:
[0133] If the tail box update direction is tail box reduction, determine whether the currency type is foreign currency;
[0134] If the currency type is foreign currency, determine whether there is an amount that needs to be returned based on the minimum face value constraint;
[0135] If there is no amount to be returned, the target tail box is updated by reducing the tail box according to the transaction information;
[0136] If there is an amount that needs to be returned, the target trunk is updated to reduce the amount according to the amount to be returned and the transaction information.
[0137] Figure 6 This is a schematic diagram of the structure of the second embodiment of the processing device for the trunk data provided by the present application. Based on the above embodiment, Figure 6 As shown, the trunk data processing device 50 provided in the present application further includes:
[0138] Storage module 503: used to store the transaction information and the account information involved in updating the target tail box after the target tail box is updated.
[0139] Return module 504: is used to return the tail box update result information to the transaction system after completing the update of the target tail box.
[0140] The device 50 for processing trunk data provided in this embodiment can execute the method provided in the above method embodiment, and its implementation principle and technical effect are similar, which will not be described in detail in this embodiment.
[0141] Figure 7 This is a schematic diagram of the structure of the tail box data processing device provided by this application. Figure 7 As shown, the trunk data processing device 60 provided in this embodiment includes: at least one processor 601 and a memory 602. Optionally, the device 60 also includes a communication component 603. The processor 601, the memory 602 and the communication component 603 are connected via a bus 604.
[0142] In a specific implementation process, at least one processor 601 executes the computer execution instructions stored in the memory 602, so that at least one processor 601 executes the above method.
[0143] The specific implementation process of the processor 601 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.
[0144] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
[0145] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk storage.
[0146] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.
[0147] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.
[0148] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.
[0149] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.
[0150] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.
[0151] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.
[0152] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0153] 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.
[0154] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory ROM, random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0155] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.
[0156] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.
Claims
1. A method for processing tail box data, characterized in that: A processing device for tail box data is applied, and the processing device for tail box data establishes data connections with multiple transaction systems and multiple tail boxes respectively; the method includes: After receiving the transaction information sent by any transaction system, determining a target tail box to be updated from the multiple tail boxes according to the transaction information; The data in the target tail box is updated according to the transaction information.
2. The method according to claim 1, characterized in that The transaction information includes teller identification and currency type; Correspondingly, determining a target tail box to be updated from the plurality of tail boxes according to the transaction information includes: The target tail box corresponding to the teller identification is determined according to the teller identification and the currency type, and a pre-stored mapping relationship between tellers and tail boxes.
3. The method according to claim 2, characterized in that The transaction information also includes the trunk update direction and the transaction amount; Correspondingly, updating the data in the target tail box according to the transaction information includes: If the tail box update direction is tail box increase, determine whether the transaction amount meets the preset minimum ticket constraint condition; If the transaction amount meets the minimum bill constraint, then the target tail box is updated according to the transaction information; If the transaction amount does not satisfy the minimum face value constraint, an error prompt message is returned to the transaction system.
4. The method according to claim 3, characterized in that The method further comprises: If the tail box update direction is tail box reduction, determining whether the currency type is a foreign currency; If the currency type is a foreign currency, determine whether there is an amount that needs to be returned based on the minimum face value constraint; If there is no amount to be returned, performing a tail box reduction and update operation on the target tail box according to the transaction information; If there is an amount that needs to be returned, the tail box reduction update operation is performed on the target tail box according to the amount that needs to be returned and the transaction information.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: After the target tail box is updated, the transaction information and the account information involved in updating the target tail box are stored.
6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: After the target tail box is updated, the tail box update result information is returned to the transaction system.
7. The method according to any one of claims 1 to 4, characterized in that: The transaction information also includes: Institution identification, transaction type and counterparty account; The transaction types include normal transactions and reversal transactions.
8. A device for processing tail box data, characterized in that: The tail box data processing device establishes data connections with multiple transaction systems and multiple tail boxes respectively; including: A first processing module, configured to determine a target tail box to be updated from the plurality of tail boxes according to the transaction information after receiving the transaction information sent by any transaction system; The second processing module is used to update the data in the target tail box according to the transaction information.
9. A device for processing tail box data, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.