A method and apparatus for generating a reply slip

Abstract

The application discloses a method and device for generating a return single, and relates to the technical field of big data processing. A specific embodiment of the method comprises the following steps: receiving detailed data transmitted by each upstream business system, integrating the detailed data transmitted by each upstream business system to form a detailed data table; traversing each piece of detailed data in the detailed data table, querying return single configuration information of the detailed data from a return single configuration table, and judging whether the detailed data needs to generate a return single; if not, marking the state of the detailed data as filtered, and writing the detailed data into an ignored information table; if yes, judging whether the state of the detailed data is not generated a return single; and if yes, generating a return single according to the detailed data. The embodiment can solve the technical problems that a return single cannot be generated in time, a compensation mechanism is lacked, and data cannot be flexibly re-run in batch processing.

Description

Technical Field

[0001] This invention relates to the field of big data processing technology, and in particular to a method and apparatus for generating receipts. Background Technology

[0002] Currently, the transaction statement service serves tens of millions of corporate clients across the bank, generating over 1 billion statements annually, with peak daily printing exceeding 17 million statements. The transaction details generated by branches in various regions are massive, and many product types require customized transaction statements. Processing such large volumes of data, along with the diverse types of customized statements, presents significant challenges. Ensuring the accuracy of the processed data is undoubtedly the most important and crucial aspect.

[0003] In the process of realizing this invention, the inventors discovered at least the following problems in the prior art:

[0004] There are frequent occurrences of missing detailed data and processing errors, resulting in the inability to generate receipts in a timely manner, causing inconvenience and trouble for users; the system cannot guarantee that the transaction details are processed completely and lacks a compensation mechanism; it cannot flexibly rerun batch processing of data, and there are no solutions for encountering processing omissions or errors. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method and apparatus for generating receipts to solve the technical problems of being unable to generate receipts in a timely manner, lacking a compensation mechanism, and being unable to flexibly reprocess batch data.

[0006] To achieve the above objectives, according to one aspect of the present invention, a method for generating a receipt is provided, comprising:

[0007] Receive detailed data from various upstream business systems, integrate the detailed data from various upstream business systems, and form a detailed data table;

[0008] The system iterates through each detailed data entry in the detailed data table and queries the return receipt configuration information of the detailed data from the return receipt configuration table to determine whether the detailed data needs to generate a return receipt. The return receipt configuration information includes whether a return receipt needs to be generated or not, and the return receipt configuration information is configured by the user.

[0009] If not, mark the status of the detailed data as filtered and write the detailed data into the ignore information table;

[0010] If so, determine whether the status of the detailed data is "no receipt generated"; if so, generate a receipt based on the detailed data.

[0011] Optionally, after generating the receipt based on the detailed data, the method further includes:

[0012] Determine whether the detailed data has successfully generated a receipt;

[0013] If so, mark the status of the detailed data as "receipt generated";

[0014] If not, the identifier of the detailed data is written into the error message table.

[0015] Optionally, before iterating through each detailed data entry in the detailed data table and querying the return receipt configuration information of the detailed data from the return receipt configuration table to determine whether the detailed data needs to generate a return receipt, the process further includes:

[0016] Delete the detailed data identifiers in the error message table.

[0017] Optionally, before iterating through each detailed data entry in the detailed data table and querying the return receipt configuration information of the detailed data from the return receipt configuration table to determine whether the detailed data needs to generate a return receipt, the process further includes:

[0018] Based on the return receipt result data table, find the detailed data of the returned receipts that have been generated in the detailed data table, and mark the detailed data as having generated a returned receipt.

[0019] Optionally, the detailed data of the generated receipts can be retrieved from the receipt result data table, including:

[0020] Based on account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction, find the detailed data in the detailed data table that is the same as the return receipt result data table.

[0021] Optionally, after generating the receipt based on the detailed data, the method further includes:

[0022] Receive a receipt supplementary entry instruction;

[0023] Locate the target receipt corresponding to the receipt supplementation instruction;

[0024] Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

[0025] Optionally, the receipt supplementation instruction carries account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction;

[0026] Locating the target receipt corresponding to the receipt supplementation instruction includes:

[0027] The target receipt is located based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction carried in the receipt supplementation instruction.

[0028] Optionally, after updating the target receipt with the supplementary information carried in the receipt supplementation instruction, the method further includes:

[0029] The status of the target receipt is marked as "recorded".

[0030] Additionally, according to another aspect of the present invention, an apparatus for generating a receipt is provided, comprising:

[0031] The receiving module is used to receive detailed data from various upstream business systems, integrate the detailed data from various upstream business systems, and form a detailed data table.

[0032] The traversal module is used to traverse each piece of detailed data in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and thus determine whether the detailed data needs to generate a return order; wherein, the return order configuration information includes whether a return order needs to be generated or not, and the return order configuration information is configured by the user;

[0033] The filtering module is used to mark the status of the detailed data as filtered if no, and to write the detailed data into the ignore information table;

[0034] The generation module is used to determine whether the status of the detailed data is "no receipt generated" if the status is "yes"; if so, it generates a receipt based on the detailed data.

[0035] Optionally, the generation module is further configured to:

[0036] After generating the receipt based on the detailed data, determine whether the receipt was successfully generated.

[0037] If so, mark the status of the detailed data as "receipt generated";

[0038] If not, the identifier of the detailed data is written into the error message table.

[0039] Optionally, the traversal module is further configured to:

[0040] Iterate through each detailed data entry in the detailed data table, retrieve the return order configuration information of the detailed data from the return order configuration table, and then delete the detailed data identifier in the error information table before determining whether the detailed data needs to generate a return order.

[0041] Optionally, the traversal module is further configured to:

[0042] Traverse each detailed data entry in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and determine whether the detailed data needs to generate a return order. Before that, find the detailed data in the detailed data table that has generated a return order based on the return order result data table, and mark the detailed data as having generated a return order.

[0043] Optionally, the traversal module is further configured to:

[0044] Based on account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction, find the detailed data in the detailed data table that is the same as the return receipt result data table.

[0045] Optionally, it also includes a supplementary recording module for:

[0046] After generating the receipt based on the detailed data, receive the receipt supplementation instruction;

[0047] Locate the target receipt corresponding to the receipt supplementation instruction;

[0048] Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

[0049] Optionally, the receipt supplementation instruction carries account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction;

[0050] The supplementary recording module is also used for:

[0051] The target receipt is located based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction carried in the receipt supplementation instruction.

[0052] Optionally, the supplementary recording module is further configured to:

[0053] After updating the target receipt with the supplementary information carried in the receipt supplementary instruction, the status of the target receipt is marked as supplemented.

[0054] According to another aspect of the present invention, an electronic device is also provided, comprising:

[0055] One or more processors;

[0056] Storage device for storing one or more programs.

[0057] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0058] According to another aspect of the present invention, a computer-readable medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the methods described in any of the above embodiments.

[0059] According to another aspect of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods described in any of the above embodiments.

[0060] One embodiment of the above invention has the following advantages or beneficial effects: Because it employs a technique that determines whether a receipt needs to be generated for detailed data, and if not, marks the status of the detailed data as filtered and writes the detailed data into an ignored information table; if yes, it determines whether the status of the detailed data is "not generated," and if not, generates a receipt based on the detailed data, it overcomes the technical problems of existing technologies such as the inability to generate receipts in a timely manner, the lack of a compensation mechanism, and the inability to flexibly rerun batch processing of data. This embodiment of the invention can generate receipts in a timely manner, improve system fault tolerance, and ensure the correctness of data processing; moreover, it can repeatedly rerun batch processing exceptions, improving the ability to handle exceptions or emergencies, and it does not generate duplicate data.

[0061] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0062] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Wherein:

[0063] Figure 1 This is a schematic diagram of the main flow of the method for generating receipts according to an embodiment of the present invention;

[0064] Figure 2 This is a schematic diagram of the main flow of a method for generating a receipt according to a possible embodiment of the present invention;

[0065] Figure 3 This is a schematic diagram of the main flow of a method for generating a receipt according to another applicable embodiment of the present invention;

[0066] Figure 4 This is a schematic diagram of the main flow of a method for generating a receipt according to another possible embodiment of the present invention;

[0067] Figure 5This is a schematic diagram of the main modules of the device for generating receipts according to an embodiment of the present invention;

[0068] Figure 6 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0069] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0070] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0071] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0072] Figure 1 This is a schematic diagram of the main flow of a method for generating receipts according to an embodiment of the present invention. As one embodiment of the present invention, such as... Figure 1 As shown, the method for generating receipts may include:

[0073] Step 101: Receive detailed data from each upstream business system, integrate the detailed data from each upstream business system, and form a detailed data table.

[0074] First, detailed data is received from various upstream business systems. Then, this detailed data is integrated to form a single detailed data table for unified processing in subsequent steps. Upstream business systems can include component-based receipt systems, list-based receipt systems, filtering task systems, internal ledger systems, voucher repository receipt systems, etc.

[0075] Step 102: Traverse each piece of detail data in the detail data table and determine whether the detail data needs to generate a receipt; if not, proceed to step 103; if not, proceed to step 104.

[0076] First, iterate through each record in the detailed data table. Each record records whether a receipt needs to be generated. If the user needs a receipt, mark the record as needing a receipt; otherwise, mark the record as not needing a receipt or leave it unmarked.

[0077] Optionally, the detailed data includes account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending / borrowing direction (debit account, debit account name, credit account, credit account name).

[0078] Step 103: Mark the status of the detailed data as filtered and write the detailed data into the ignore information table.

[0079] If the detailed data does not require the generation of receipts, then the status of the detailed data is marked as filtered, and the detailed data is written to the ignore information table.

[0080] Step 104: Determine whether the status of the detailed data is "no receipt generated"; if yes, proceed to step 105; otherwise, end.

[0081] If the detailed data requires the generation of a receipt, then continue to determine whether the status of the detailed data is "no receipt generated". The status of the detailed data includes "no receipt generated" and "received receipt generated".

[0082] Step 105: Generate a receipt based on the detailed data.

[0083] If the status of the detailed data is "no receipt generated", then a receipt is generated based on that detailed data. If the status of the detailed data is "receipt generated", then the process ends to prevent duplicate processing of the data.

[0084] This invention provides a backup data processing guarantee for the workflow of processing various upstream receipt information, and performs unified processing of standard receipts, interest lists, fee vouchers and other types in the backup process. The number of receipts generated by this workflow accounts for more than 50% of the total daily receipt volume.

[0085] This invention employs filtering techniques at the financial product component, institution, and account levels to prevent duplicate processing of transaction data. The filtered data is then processed by categorizing it into current account transaction details, periodic account transaction details, and treasury account details, generating corresponding transaction receipts. This invention is positioned at the end of the batch processing workflow as a safety net, performing backup data processing after other processing jobs are completed. This ensures no transaction data is lost, and if a preceding processing job encounters an error, the backup job can still generate a correct receipt.

[0086] Based on the various embodiments described above, it can be seen that the embodiments of the present invention solve the technical problems in the prior art of failing to generate timely receipts, lacking compensation mechanisms, and being unable to flexibly rerun batch processing of data by determining whether detailed data needs to generate receipts. If not, the status of the detailed data is marked as filtered and the detailed data is written to an ignored information table; if so, the status of the detailed data is determined as not having generated a receipt, and if not, a receipt is generated based on the detailed data. The embodiments of the present invention can generate receipts in a timely manner, improve system fault tolerance, and ensure the correctness of data processing; moreover, it can repeatedly rerun batch processing exceptions, improving the ability to handle exceptions or emergencies, and will not generate duplicate data.

[0087] Figure 2 This is a schematic diagram of the main flow of a method for generating a receipt according to a possible embodiment of the present invention. As another embodiment of the present invention, such as... Figure 2 As shown, the method for generating receipts may include:

[0088] Step 201: Receive detailed data from each upstream business system, integrate the detailed data from each upstream business system, and form a detailed data table.

[0089] Step 202: Traverse each piece of detailed data in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and thus determine whether the detailed data needs to generate a return order; if not, proceed to step 203; if not, proceed to step 204.

[0090] Step 203: Mark the status of the detailed data as filtered and write the detailed data into the ignore information table.

[0091] Step 204: Determine whether the status of the detailed data is "no receipt generated"; if yes, proceed to step 205; otherwise, end.

[0092] Step 205: Generate a receipt based on the detailed data.

[0093] Step 206: Determine whether the detailed data has successfully generated a receipt; if yes, proceed to step 207; if no, proceed to step 208.

[0094] Step 207: Mark the status of the detailed data as "receipt generated".

[0095] Step 208: Write the identifier of the detailed data into the error information table.

[0096] After generating a receipt based on the detailed data, in order to ensure that the receipt is generated correctly, it is necessary to determine whether the receipt was successfully generated for that detailed data. If it was, the status of the detailed data is marked as a receipt generated. If not, the identifier of the detailed data is written to the error information table so that the detailed data that failed to generate a receipt can be retrieved.

[0097] Furthermore, the specific implementation details of the method for generating receipts in one of the reference embodiments of the present invention have been described in detail in the above-described method for generating receipts, so the details will not be repeated here.

[0098] Figure 3 This is a schematic diagram of the main flow of a method for generating a receipt according to another possible embodiment of the present invention. As another embodiment of the present invention, such as... Figure 3 As shown, the method for generating receipts may include:

[0099] Step 301: Receive detailed data from each upstream business system, integrate the detailed data from each upstream business system, and form a detailed data table.

[0100] Step 302: Delete the detailed data identifier in the error message table.

[0101] First, the detailed data identifier in the error message table must be deleted. If the detailed data in the error message table successfully generates a receipt, it will not be written to the error message table again. If the detailed data in the error message table fails to generate a receipt, it will be written to the error message table again.

[0102] Step 303: Based on the return receipt result data table, find the detailed data of the generated return receipts in the detailed data table, and mark the detailed data as generated return receipts.

[0103] To prevent duplicate data processing, it is necessary to first locate the detailed data of the generated receipts in the detailed data table based on the receipt result data table, and mark the detailed data as having generated receipts. Then, in subsequent steps, these detailed data that have been marked as having generated receipts will not generate receipts again.

[0104] Optionally, the detailed data of the generated receipts in the detailed data table can be retrieved based on the receipt result data table. This includes: searching for detailed data in the detailed data table that is identical to the receipt result data table based on account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction. To accurately find the same detailed data in the detailed data table, the search is performed based on account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction to ensure the uniqueness of the detailed data and avoid errors.

[0105] It should be noted that step 302 can be executed first and then step 303, or step 303 can be executed first and then step 302, or steps 302 and 303 can be executed simultaneously.

[0106] Step 304: Traverse each piece of detailed data in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and thus determine whether the detailed data needs to generate a return order; if not, proceed to step 305; if not, proceed to step 306.

[0107] Step 305: Mark the status of the detailed data as filtered and write the detailed data into the ignore information table.

[0108] Step 306: Determine whether the status of the detailed data is "no receipt generated"; if yes, proceed to step 307; otherwise, end.

[0109] Step 307: Generate a receipt based on the detailed data.

[0110] Step 308: Determine whether the detailed data has successfully generated a receipt; if yes, proceed to step 309; if no, proceed to step 310.

[0111] Step 309: Mark the status of the detailed data as "receipt generated".

[0112] Step 310: Write the identifier of the detailed data into the error information table.

[0113] Furthermore, the specific implementation details of the method for generating receipts in one of the reference embodiments of the present invention have been described in detail in the above-described method for generating receipts, so the details will not be repeated here.

[0114] Figure 4 This is a schematic diagram of the main flow of a method for generating a receipt according to another possible embodiment of the present invention. As another embodiment of the present invention, such as... Figure 4 As shown, the method for generating receipts may include:

[0115] Step 401: Receive detailed data from each upstream business system, integrate the detailed data from each upstream business system, and form a detailed data table.

[0116] Step 402: Traverse each piece of detailed data in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and thus determine whether the detailed data needs to generate a return order; if not, proceed to step 403; if not, proceed to step 404.

[0117] Step 403: Mark the status of the detailed data as filtered and write the detailed data into the ignore information table.

[0118] Step 404: Determine whether the status of the detailed data is "no receipt generated"; if yes, proceed to step 405; otherwise, end.

[0119] Step 405: Generate a receipt based on the detailed data.

[0120] Step 406: Receive the instruction to supplement the receipt.

[0121] When an existing receipt needs to be supplemented, the user or business personnel can send a receipt supplementation instruction to the business system. The receipt supplementation instruction carries the account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction.

[0122] Step 407: Locate the target receipt corresponding to the receipt supplementation instruction.

[0123] After receiving a receipt supplement instruction, the business system retrieves the target receipt corresponding to the supplement instruction from the already generated receipts, which is the receipt that needs to be supplemented.

[0124] Optionally, step 407 may include: locating the target receipt based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction carried in the receipt supplementation instruction. To accurately locate the target receipt, the generated receipt can be found based on detailed data such as the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction carried in the receipt supplementation instruction, ensuring the uniqueness of the detailed data and avoiding errors.

[0125] Step 408: Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

[0126] After locating the target receipt, supplementary information is added to the target receipt. Specifically, the supplementary information carried in the receipt supplementary information instruction is updated to the target receipt. If the receipt already has supplementary information, the supplementary information carried in the receipt supplementary information instruction is used to replace the content in the receipt. If the receipt does not have supplementary information, the supplementary information carried in the receipt supplementary information instruction is added to the receipt.

[0127] Step 409: Mark the status of the target receipt as "recorded".

[0128] After completing the supplementary entry of the receipt, the status of the target receipt is marked as supplemented, thereby enabling users to process the supplementary entry information of the generated receipts in real time.

[0129] Furthermore, the specific implementation details of the method for generating receipts in one of the reference embodiments of the present invention have been described in detail in the above-described method for generating receipts, so the details will not be repeated here.

[0130] Figure 5 This is a schematic diagram of the main modules of the apparatus for generating receipts according to an embodiment of the present invention. Figure 5 As shown, the device 500 for generating receipts includes a receiving module 501, a traversal module 502, a filtering module 503, and a generation module 504. The receiving module 501 receives detailed data from various upstream business systems and integrates this data to form a detailed data table. The traversal module 502 traverses each piece of detailed data in the detailed data table, queries the receipt configuration information of the detailed data from the receipt configuration table, and determines whether the detailed data needs to generate a receipt. The filtering module 503, if the data is not filtered, marks it as filtered and writes it to an ignore information table. The generation module 504, if the data is not filtered, determines whether the data is in a state of "no receipt generated"; if so, it generates a receipt based on the detailed data.

[0131] Optionally, the generation module 504 is further configured to:

[0132] After generating the receipt based on the detailed data, determine whether the receipt was successfully generated.

[0133] If so, mark the status of the detailed data as "receipt generated";

[0134] If not, the identifier of the detailed data is written into the error message table.

[0135] Optionally, the traversal module 502 is further configured to:

[0136] Iterate through each detailed data entry in the detailed data table, retrieve the return order configuration information of the detailed data from the return order configuration table, and then delete the detailed data identifier in the error information table before determining whether the detailed data needs to generate a return order.

[0137] Optionally, the traversal module 502 is further configured to:

[0138] Traverse each detailed data entry in the detailed data table, query the return order configuration information of the detailed data from the return order configuration table, and determine whether the detailed data needs to generate a return order. Before that, find the detailed data in the detailed data table that has generated a return order based on the return order result data table, and mark the detailed data as having generated a return order.

[0139] Optionally, the traversal module 502 is further configured to:

[0140] Based on account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction, find the detailed data in the detailed data table that is the same as the return receipt result data table.

[0141] Optionally, it also includes a supplementary recording module for:

[0142] After generating the receipt based on the detailed data, receive the receipt supplementation instruction;

[0143] Locate the target receipt corresponding to the receipt supplementation instruction;

[0144] Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

[0145] Optionally, the receipt supplementation instruction carries account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction;

[0146] The supplementary recording module is also used for:

[0147] The target receipt is located based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction carried in the receipt supplementation instruction.

[0148] Optionally, the supplementary recording module is further configured to:

[0149] After updating the target receipt with the supplementary information carried in the receipt supplementary instruction, the status of the target receipt is marked as supplemented.

[0150] It should be noted that the specific implementation details of the device for generating receipts described in this invention have been described in detail in the method for generating receipts described above, so the details will not be repeated here.

[0151] Figure 6 An exemplary system architecture 600 is shown, in which the method or apparatus for generating receipts according to embodiments of the present invention can be applied.

[0152] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0153] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0154] Terminal devices 601, 602, and 603 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0155] Server 605 can be a server that provides various services, such as a backend management server that supports shopping websites browsed by users using terminal devices 601, 602, and 603 (this is just an example). The backend management server can analyze and process data such as received item information query requests, and then feed the processing results back to the terminal devices.

[0156] It should be noted that the method for generating receipts provided in this embodiment of the invention is generally executed by server 605, and correspondingly, the device for generating receipts is generally located in server 605.

[0157] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0158] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device of the present invention. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0159] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0160] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0161] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this invention.

[0162] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0163] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer programs according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0164] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a receiving module, a traversal module, a filtering module, and a generating module. The names of these modules do not necessarily limit the functionality of the module itself.

[0165] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the device, the device implements the following method: receiving detailed data from various upstream business systems; integrating the detailed data from the various upstream business systems to form a detailed data table; traversing each piece of detailed data in the detailed data table; querying the return receipt configuration information of the detailed data from the return receipt configuration table to determine whether the detailed data needs to generate a return receipt; wherein the return receipt configuration information includes whether a return receipt needs to be generated or not, and the return receipt configuration information is configured by the user; if not, marking the status of the detailed data as filtered and writing the detailed data into an ignore information table; if yes, determining whether the status of the detailed data is that a return receipt has not been generated; if yes, generating a return receipt based on the detailed data.

[0166] In another aspect, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the methods described in any of the above embodiments.

[0167] According to the technical solution of this invention, by determining whether a receipt needs to be generated for the detailed data, and if not, marking the status of the detailed data as filtered and writing the detailed data into an ignored information table; and if so, determining whether the status of the detailed data is that a receipt has not been generated, and if so, generating a receipt based on the detailed data, this invention overcomes the technical problems of existing technologies, such as the inability to generate receipts in a timely manner, the lack of a compensation mechanism, and the inability to flexibly rerun batch processing of data. This invention can generate receipts in a timely manner, improve system fault tolerance, and ensure the correctness of data processing; moreover, it can repeatedly rerun batch processing exceptions, improving the ability to handle exceptions or emergencies, and will not generate duplicate data.

[0168] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for generating a receipt, characterized in that, include: Receive detailed data from various upstream business systems, integrate the detailed data from various upstream business systems, and form a detailed data table; The process iterates through each record in the detailed data table and queries the return receipt configuration table to determine whether a return receipt needs to be generated for that record. The return receipt configuration information indicates whether a return receipt needs to be generated or not, and this information is configured by the user. If the user requires a return receipt to be generated, the record is marked as requiring a return receipt; otherwise, it is marked as not requiring a return receipt or left unmarked. If not, mark the status of the detailed data as filtered and write the detailed data into the ignore information table; If so, determine whether the status of the detailed data is "no receipt generated"; if so, generate a receipt based on the detailed data. After generating the receipt based on the detailed data, it also includes: Determine whether the detailed data has successfully generated a receipt; If so, mark the status of the detailed data as "receipt generated"; If not, the identifier of the detailed data is written into the error message table; Before iterating through each record in the detailed data table and querying the return receipt configuration information from the return receipt configuration table to determine whether a return receipt needs to be generated for that detailed data, the process also includes: Based on the account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction, the detailed data that is the same as the return receipt result data table is found in the detailed data table, and the detailed data is marked as having generated a return receipt.

2. The method according to claim 1, characterized in that, Before iterating through each record in the detailed data table and querying the return receipt configuration information from the return receipt configuration table to determine whether a return receipt needs to be generated for that detailed data, the process also includes: Delete the detailed data identifiers in the error message table.

3. The method according to claim 1, characterized in that, After generating the receipt based on the detailed data, it also includes: Receive a receipt supplementary entry instruction; Locate the target receipt corresponding to the receipt supplementation instruction; Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

4. The method according to claim 3, characterized in that, The receipt supplementation instruction carries the account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction; Locating the target receipt corresponding to the receipt supplementation instruction includes: The target receipt is located based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction carried in the receipt supplementation instruction.

5. The method according to claim 3, characterized in that, After updating the target receipt with the supplementary information carried in the receipt supplementary instruction, the process also includes: The status of the target receipt is marked as "recorded".

6. An apparatus for generating a receipt, characterized in that, include: The receiving module is used to receive detailed data from various upstream business systems, integrate the detailed data from various upstream business systems, and form a detailed data table. The traversal module is used to traverse each piece of detailed data in the detailed data table, query the return receipt configuration information of the detailed data from the return receipt configuration table, and thus determine whether the detailed data needs to generate a return receipt; wherein, the return receipt configuration information includes whether a return receipt needs to be generated or not, and the return receipt configuration information is configured by the user; if the user needs to generate a return receipt, the detailed data is marked as needing to generate a return receipt, and if the user does not need to generate a return receipt, the detailed data is marked as not needing to generate a return receipt or is not marked; The filtering module is used to mark the status of the detailed data as filtered if no, and to write the detailed data into the ignore information table; The generation module is used to determine whether the status of the detailed data is "no receipt generated" if the condition is met; if so, it generates a receipt based on the detailed data. The generation module is also used for: After generating the receipt based on the detailed data, determine whether the receipt was successfully generated. If so, mark the status of the detailed data as "receipt generated"; If not, the identifier of the detailed data is written into the error message table; The traversal module is also used for: Before determining whether a receipt needs to be generated for a detailed data entry, each detailed data entry in the detailed data table is traversed. The receipt configuration information of the detailed data is queried from the receipt configuration table. Based on the account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction, the detailed data that is the same as the receipt result data table is found in the detailed data table, and the detailed data is marked as having generated a receipt.

7. The apparatus according to claim 6, characterized in that, The traversal module is also used for: Iterate through each detailed data entry in the detailed data table, retrieve the return order configuration information of the detailed data from the return order configuration table, and then delete the detailed data identifier in the error information table before determining whether the detailed data needs to generate a return order.

8. The apparatus according to claim 6, characterized in that, It also includes a supplementary recording module, used for: After generating the receipt based on the detailed data, receive the receipt supplementation instruction; Locate the target receipt corresponding to the receipt supplementation instruction; Update the target receipt with the supplementary information carried in the receipt supplementary information instruction.

9. The apparatus according to claim 8, characterized in that, The receipt supplementation instruction carries the account identifier, transaction flow identifier, transaction tracking identifier, transaction time, transaction amount, and lending direction; The supplementary recording module is also used for: The target receipt is located based on the receipt identifier, account identifier, transaction flow identifier, transaction tracking identifier, transaction amount, and lending direction carried in the receipt supplementation instruction.

10. The apparatus according to claim 8, characterized in that, The supplementary recording module is also used for: After updating the target receipt with the supplementary information carried in the receipt supplementary instruction, the status of the target receipt is marked as supplemented.

11. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-5.

12. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-5.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

Images