Bill image file processing method, client, management end and system

Abstract

The embodiment of the invention provides a bill image file processing method, a client, a management end and a system, and relates to the field of financial science and technology or other related fields. The method comprises the following steps: a client responds to a plurality of processing requests, packs the processing requests to obtain an instruction packet, associates a bill image file corresponding to each processing request to the instruction packet based on an association identifier, and sends the instruction packet to a management end, so that when the management end executes billing processing based on the processing request in the instruction packet, the bill image file corresponding to each processing request is sent to the client; and hanging the bill image file corresponding to the processing request to an invoicing protocol corresponding to the processing request based on the association identifier to complete processing. According to the scheme of the invention, the plurality of processing requests are packaged in batches and are associated with the corresponding bill image files, and the processing requests are linked to the storage addresses of the bill image files based on the association identifiers, so that the bill image files can still be directly hung and reused after an invoicing protocol is deleted, and the processing efficiency of the bill image files is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology or other related fields, in particular to a bill image file processing method, a client, a management end and a system. BACKGROUND

[0002] With the continuous development of financial electronicization, banks or other financial enterprises need to perform receiving, collection, redemption and archiving operation processes on various bills (such as checks, drafts and bills) to verify the authenticity and legality of the bills. In the processing of the bills, related electronic image files need to be processed at the same time.

[0003] In related bill processing schemes, when a staff member accepts a draft, multiple different types of image data need to be uploaded in the business system. Among them, a set of image files needs to be uploaded separately for each newly added draft processing instruction, and manual uploading is time-consuming and laborious. In addition, when the business information is deleted, the uploaded images are also synchronized to be cleared, and when re-entering, all need to be re-uploaded and connected, further increasing the work burden and time cost. Therefore, the current problem to be solved is how to improve the efficiency of bill image file processing. SUMMARY

[0004] The present application provides a bill image file processing method, a client, a management end and a system to improve the efficiency of bill image file processing.

[0005] In a first aspect, the present application provides a bill image file processing method applied to a client, the method comprising: in response to multiple processing requests, obtaining bill image files corresponding to the multiple processing requests; packaging the multiple processing requests to obtain an instruction package, and associating the bill image file corresponding to each processing request to the instruction package based on an association identifier; wherein the association identifier is used to obtain a storage address of the bill image file to locate the bill image file; and sending the instruction package to a management end, so that when the management end performs bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is connected to the bill processing protocol corresponding to the processing request based on the association identifier, to complete the processing.

[0006] In a second aspect, the present application provides a bill image file processing method applied to a management end, the method comprising: receiving an instruction package sent by a user end; the instruction package is obtained by the user end after responding to multiple processing requests and obtaining bill image files corresponding to the multiple processing requests; wherein the instruction package is associated to the bill image file corresponding to each processing request based on an association identifier, and the association identifier is used to obtain a storage address of the bill image file to locate the bill image file; in response to performing bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is connected to the bill processing protocol corresponding to the processing request based on the association identifier, to complete the processing.

[0007] In a third aspect, the application provides a client, configured to: in response to a plurality of processing requests, acquire a plurality of bill image files corresponding to the plurality of processing requests; package the plurality of processing requests to obtain an instruction package, and associate each bill image file corresponding to a processing request to the instruction package based on an association identifier; wherein the association identifier is used to acquire a storage address of the bill image file to locate the bill image file; and send the instruction package to a management end, so that, when the management end performs an invoice processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is attached to an invoice protocol corresponding to the processing request based on the association identifier, to complete the processing.

[0008] In a fourth aspect, the application provides a management end, configured to: receive an instruction package sent by a user end; the instruction package is obtained by the user end after acquiring a plurality of bill image files corresponding to a plurality of processing requests in response to the plurality of processing requests; wherein the instruction package is associated to each bill image file corresponding to a processing request based on an association identifier, and the association identifier is used to acquire a storage address of the bill image file to locate the bill image file; in response to performing an invoice processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is attached to an invoice protocol corresponding to the processing request based on the association identifier, to complete the processing.

[0009] In a fifth aspect, a bill image file processing system is provided, comprising the client and the management end as described above.

[0010] The bill image file processing method, the client, the management end and the system provided by the application, the method comprising: the client, in response to a plurality of processing requests, packages the plurality of processing requests to obtain an instruction package, associates each bill image file corresponding to a processing request to the instruction package based on an association identifier, and sends the instruction package to a management end, so that, when the management end performs an invoice processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is attached to an invoice protocol corresponding to the processing request based on the association identifier, to complete the processing. The scheme of the application, by packaging a plurality of processing requests in batches and associating them with corresponding bill image files, linking to the storage address of the bill image file based on the association identifier, the bill image file can still be directly attached and reused after the deletion of the invoice protocol, improving the efficiency of bill image file processing. BRIEF DESCRIPTION OF DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0012] Figure 1 A flowchart of a bill image file processing method provided by an embodiment of the application;

[0013] Figure 2A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1.

[0014] Figure 3 A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1.

[0015] Figure 4 A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1.

[0016] Figure 5 A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1.

[0017] Figure 6 A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1.

[0018] Figure 7 A structure diagram of a bill image file processing system provided by an embodiment of the present application is shown in FIG. 1.

[0019] The specific embodiments of the present application have been shown in the above-described drawings, and will be described in more detail hereinafter. These drawings and the written description are not intended to restrict 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

[0020] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The same reference numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0021] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary security measures are taken, public order and good customs are not violated, and appropriate operation portals are provided for the user to choose authorization or refusal.

[0022] And the present application relates to the user information for big data analysis (including but not limited to personal biological characteristics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and adopts artificial intelligence technology to make automatic decision, makes the technical scheme based on automatic decision result to have the important influence decision to personal rights and interests, provides the corresponding operation entrance for user, for user to choose to agree or refuse automatic decision result;If user chooses to refuse, then enter expert decision process.

[0023] It should be noted that the bill image file processing method, client, management end and system provided by the present application can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The application field of the bill image file processing method, client, management end and system in the present application is not limited.

[0024] With the continuous development of financial electronic process, bill business processing has become a key link in the daily operation of banks and other financial institutions. In the receiving, collection, redemption and archiving of bills and a series of operations, not only the entity bill needs to be audited and transferred, but also the corresponding electronic image file needs to be collected, stored and associated. These image data, as an important carrier of bill electronic identity, are directly related to the legality verification, risk control and audit traceability of bill business, and thus play an irreplaceable role in modern financial business processes.

[0025] However, the related image file processing mechanism still has many significant defects: the staff must manually upload multiple types of images one by one for each business instruction, which is repetitive and time-consuming; once the business changes or needs to be re-entered, all the transmitted images are cleared and must be collected and connected again from the beginning, which not only greatly increases the burden of manual operation, but also is more prone to human errors such as omission and wrong transmission caused by repeated processing. The overall process relies on manual intervention and lacks the support of automation and integration, ultimately leading to low efficiency of business processing.

[0026] The technical content provided in the present application aims to solve the above technical problems in the prior art. In the bill image file processing method, the client, the management end and the system provided in the present application, the method comprises: the client responds to a plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, associates the bill image file corresponding to each processing request to the instruction package based on an association identifier, and sends the instruction package to the management end, so that when the management end executes the billing processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to the billing protocol corresponding to the processing request based on the association identifier to complete the processing. The scheme of the present application packs a plurality of processing requests in batches and associates the corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly hung and reused after the billing protocol is deleted, thereby improving the efficiency of bill image file processing.

[0027] The technical scheme of the present application and how the technical scheme of the present application solves the above technical problems will be 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 can not be described again in some embodiments. The embodiments of the present application will be described below with reference to the drawings.

[0028] Figure 1 The flowchart of the bill image file processing method provided in the embodiments of the present application is shown in FIG. 1. Figure 1 As shown in the figure, the method is applied to a client, and the method comprises:

[0029] S101, responding to a plurality of processing requests, obtaining a plurality of bill image files corresponding to the processing requests;

[0030] S102, packing the plurality of processing requests to obtain an instruction package, and associating the bill image file corresponding to each processing request to the instruction package based on an association identifier; wherein the association identifier is used to obtain the storage address of the bill image file to locate the bill image file;

[0031] S103, sending the instruction package to the management end, so that when the management end executes the billing processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to the billing protocol corresponding to the processing request based on the association identifier to complete the processing.

[0032] In actual application, the form of the client for executing the bill image file processing method can be various, such as an online bank end. Alternatively, the client can also be a mobile bank application, an enterprise financial software end or a special bill processing platform end. In actual application, these clients are usually integrated in the digital services of financial institutions or enterprises to provide convenient bill processing functions for users.

[0033] In some embodiments, the processing requests are usually initiated by users through the client, involving relevant operations of bills of exchange or checks, such as acceptance requests of bills of exchange, cashing applications of checks, discount processing of bills, or endorsement transfer, etc., which are intended to complete the financial transactions or management processes of bills.

[0034] For example, the occurrence of multiple processing requests can be due to the user submitting multiple bill processing tasks in batches within a certain time, such as uploading multiple bill image files for processing in one session, or the bill image files corresponding to these requests have the same business background, such as multiple bills belonging to the same transaction or the same customer. In this example, this batch processing method can improve efficiency and reduce repetitive operations. Further, the client software can be used to implement the packaging of multiple processing requests to obtain an instruction package. Specifically, message queues or batch processing techniques can be used to aggregate the requests into a data package, which contains the metadata and associated information of all processing requests, to optimize network transmission, reduce the number of interactions with the management end, and improve processing efficiency, especially in high-concurrency scenarios, which can significantly reduce system load.

[0035] It should be understood that the above example does not limit the scope of the bill image file, which is not limited to the image of the bill of exchange or check itself, but includes all auxiliary proofs and contractual documents necessary to complete the bill processing request. For example, the bill image file can also include legal identification documents representing the identity and qualifications of enterprises or individuals, trade contracts closely related to the bill transaction background, cargo transport documents, invoice copies, and agreement documents proving the relationship between debt and credit. In practical applications, in order to meet the risk control requirements of specific businesses, the electronic images of the qualification proofs provided by the client and the written materials required by the bank can also be considered as important components of the bill image file. Therefore, the above-mentioned files collectively constitute the basis system for the management end to execute bill processing, conduct audits, and archive.

[0036] In some embodiments, the association of the bill image file corresponding to each processing request to the instruction package based on the association identifier is achieved by generating a unique identifier (such as a hash value) on the client side. The association identifier is bound to the storage address of the bill image file, such as the path of the file in the server or cloud storage. Specifically, the association identifier is used to quickly locate and retrieve the file in subsequent processing, ensuring that the management end can accurately access the required image.

[0037] In some optional embodiments, the storage address of the bill image file is usually located in the management end or a shared storage system, rather than locally on the client side, because the management end needs to centrally manage and securely store these files, but the client side can temporarily cache the file address information to assist with the association.

[0038] The management end is usually a back-end server system. In actual applications, the management end can be connected to a bank's credit service system or other financial processing platforms, and is responsible for coordinating the bill processing flow. Specifically, the management end executes the bill processing based on the processing request in the instruction package, which can be triggered by an automated program, for example, based on a rule engine or a workflow system to automatically analyze the request and perform corresponding operations, or can be started manually by bank staff through a management interface when manual intervention is required.

[0039] In this example, the management end links the bill image file corresponding to the processing request to the bill processing agreement corresponding to the processing request based on the association identifier. This means that when processing a request, the management end uses the association identifier to obtain the bill image file from storage and dynamically associates it with the relevant bill processing agreement (such as an electronic agreement or transaction record), thereby ensuring the integrity and traceability of the bill information and ultimately completing the processing flow.

[0040] The bill image file processing method provided by the present application includes: a client responds to a plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, associates a bill image file corresponding to each processing request to the instruction package based on an association identifier, and sends the instruction package to a management end, so that when the management end executes bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is linked to the bill processing agreement corresponding to the processing request based on the association identifier to complete the processing. The scheme of the present application packs a plurality of processing requests in batches and associates them with corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly linked and reused after the bill processing agreement is deleted, thereby improving the efficiency of bill image file processing.

[0041] Figure 2 A flowchart of the bill image file processing method provided by the embodiment of the present application is shown in FIG. Figure 2 As shown in the figure, the method further includes:

[0042] S201, in response to a supplement request, obtaining a supplement image file; wherein the supplement request includes the identifier of the first processing request in the instruction package;

[0043] S202, determining the instruction package according to the identifier of the first processing request, and positioning the first bill image file according to the association identifier; the first bill image file is the bill image file corresponding to the first processing request;

[0044] S203, updating the supplement image file to the first bill image file.

[0045] In actual application, the supplement request can be initiated by the user or sent by the management end. For example, when the management end is processing a certain specific processing request (i.e., the first processing request) in the instruction package, it finds that the original bill image file is incomplete or lacks necessary auxiliary proofs, and then initiates the request to the client, requiring the user to supplement and provide relevant image materials. After the client responds to the supplement request, the user is prompted to submit the required supplement image file through uploading or rescan.

[0046] In some embodiments, determining the instruction package according to the identification of the first processing request means finding the corresponding instruction package in the multiple sent instruction packages by using the identification of the first processing request, so as to confirm the context of the request. Then, the associated identification preset for the request in the instruction package is used to accurately locate the stored first bill image file. It should be noted that the "first bill image file" here refers to the original bill image file set initially associated with the processing request.

[0047] For example, the supplement image file is updated to the first bill image file, which is usually an operation of appending or replacing in actual implementation. Taking the appending operation as an example, the supplement image file is added as a new file item, and the original first bill image file is merged into a more complete file set, which collectively represents the complete image evidence of the processing request to meet the audit requirements of the management end.

[0048] For example, according to the scheme of the present example, the user initially submits a draft acceptance request and corresponding draft image files, and the management end finds that a necessary trade contract is missing as background proof after auditing, and then sends a supplement request to the client. The client locates the original instruction package and the stored draft image according to the identification of the request, and the user then uploads the contract document. The system associates the contract supplement image file with the original draft image file and updates it to the complete bill image file set of the request.

[0049] The scheme of the present example accurately locates the original instruction package and the associated bill image file based on the unique identification, improves the strong consistency between the supplement process and the initial request, and improves the fault tolerance of the bill image file processing through the supplement image file.

[0050] Figure 3 The flowchart of the bill image file processing method provided by the embodiments of the present application is shown in FIG. 1. Figure 3 As shown in FIG. 1, the method further includes:

[0051] S301, in response to the supplement request, acquiring the supplement image file; wherein the supplement request includes the identification of the instruction package;

[0052] S302, locate the second bill image file according to the association identifier, the second bill image file is the bill image file corresponding to each processing request in the instruction package;

[0053] S303, update the supplementary image file to the second bill image file.

[0054] For example, the supplementary request is usually sent by the management end. When the management end audits a certain received instruction package, it finds that all processing requests in the instruction package generally lack a certain type of necessary proof file (for example, a total contract involved in all transactions), and initiates the supplementary request to require the user to provide the file at one time. In practical application, the client responds to this request and guides the user to upload one or more supplementary image files through the client interface.

[0055] In some embodiments, locating the second bill image file according to the association identifier means that the system finds the corresponding entire instruction package according to the identifier of the instruction package, and then locates all original bill image files corresponding to each processing request in the instruction package through the pre-stored association identifier set in the package.

[0056] In some optional embodiments, the second bill image file is a collective concept, which specifically refers to the collective name of the original bill image files corresponding to all processing requests in the instruction package, representing the initial file set of the entire batch.

[0057] Further, updating the supplementary image file to the second bill image file is usually a batch addition operation, not a replacement. Specifically, the newly obtained supplementary image file is added to the file set associated with each processing request in the instruction package at the same time, becoming shared background information owned by each request, thereby avoiding the operation redundancy of supplementing each request individually.

[0058] For example, according to the scheme of the present example, an enterprise submits an instruction package containing five bill acceptance requests and uploads the image file of each bill. After auditing, the management end finds that the five transactions are based on the same framework agreement, but the agreement image is not provided. Therefore, the management end sends a supplementary request to the client for the entire instruction package. The client locates all original bill images (i.e. the second bill image file) of the five requests according to the instruction package identifier, and the user subsequently uploads the framework agreement. The system adds the framework agreement as a supplementary image file to the bill image file set associated with each request in the five requests, so that the files of each request become complete.

[0059] The scheme of the example realizes batch synchronization supplement of the bill image file at the instruction package level, improves the efficiency and consistency of the supplement operation, and avoids resource consumption for multiple separate treatments of a large number of repeated missing files in the package.

[0060] As another example, on the basis of any of the examples, the method further includes receiving a supplement instruction sent by the management end, the supplement instruction including a type identifier of the bill image file to be supplemented.

[0061] In some embodiments, when the management end initiates a supplement request, the supplement instruction sent by the management end not only includes a request or instruction package identifier of a file to be supplemented, but also further explicitly indicates the specific type of the missing file, such as requiring supplement of a “copy of a business license” or a “trade contract text”, and the like. The type identifier provides clear supplement submission guidance for the user, thereby avoiding multiple back-and-forth interactions due to inaccurate supplement files.

[0062] The scheme of the example precisely guides the user to submit correct supplement image files through the type identifier, thereby improving the efficiency and success rate of the supplement process.

[0063] The bill image file processing method provided in the application includes: a client responding to a plurality of processing requests, packaging the plurality of processing requests to obtain an instruction package, associating a bill image file corresponding to each processing request to the instruction package based on an association identifier, and sending the instruction package to a management end, so that when the management end performs invoice processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to the invoice protocol corresponding to the processing request based on the association identifier to complete the processing. The scheme of the application packages a plurality of processing requests in batches and associates the corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly hung and reused after the invoice protocol is deleted, thereby improving the efficiency of bill image file processing.

[0064] Figure 4 A flowchart of a bill image file processing method provided for an embodiment of the application is shown in FIG. 1. Figure 4 As shown in FIG. 1, the method is applied to a management end, and the method includes:

[0065] S401, receiving an instruction package sent by a user end; the instruction package is obtained by the user end in response to a plurality of processing requests and by packaging the plurality of processing requests corresponding to the bill image files; wherein the instruction package is associated to the bill image file corresponding to each processing request based on an association identifier, and the association identifier is used to obtain a storage address of the bill image file to locate the bill image file;

[0066] S402, in response to the processing request based on the instruction package, the bill image file corresponding to the processing request is hung to the bill issuing protocol corresponding to the processing request based on the association identifier, so as to complete the processing.

[0067] In practical application, the form of the client for executing the bill image file processing method can be various, such as an online bank terminal. Alternatively, the client can also be a mobile bank application, an enterprise financial software terminal or a special bill processing platform terminal. In practical application, these clients are usually integrated in the digital services of financial institutions or enterprises to provide users with convenient bill processing functions.

[0068] In some embodiments, the processing request is usually initiated by the user through the client, involving relevant operations of the draft or check, such as the acceptance request of the draft, the cashing application of the check, the discount processing of the bill or the endorsement transfer, etc. These requests aim to complete the financial transaction or management process of the bill.

[0069] For example, the occurrence of multiple processing requests can be due to the user submitting multiple bill processing tasks in batches within a certain period of time, such as uploading multiple bill image files for processing in one session, or the bill image files corresponding to these requests have the same business background, such as multiple bills belonging to the same transaction or the same customer. In this example, this batch processing method can improve efficiency and reduce repetitive operations. Further, the client software logic module can be used to package multiple processing requests to obtain an instruction package. Specifically, message queue or batch processing technology can be used to aggregate the requests into a data package, which contains the metadata and association information of all processing requests, to optimize network transmission, reduce the number of interactions with the management end, and improve processing efficiency, especially in high concurrency scenarios, which can significantly reduce system load.

[0070] It should be understood that the above examples do not limit the scope of the bill image file, which is not limited to the image of the draft or check itself, but includes all auxiliary proofs and contract documents necessary to complete the bill processing request. For example, the bill image file can also include legal identification documents representing the identity and qualifications of enterprises or individuals, trade contracts closely related to the bill transaction background, cargo transport documents, invoice copies and agreement documents proving the relationship between debt and credit. In practical application, in order to meet the risk control requirements of specific businesses, the electronic image of the qualification certificate provided by the client and the written materials required by the bank can also be regarded as an important part of the bill image file. Therefore, the above documents collectively constitute the basis system for the management end to execute the bill issuing processing, conduct audit and archive.

[0071] In some embodiments, the association of the bill image file corresponding to each processing request to the instruction package based on the association identifier is achieved by generating a unique identifier (such as a hash value) on the client side, which is bound to the storage address of the bill image file, such as the path of the file in the server or cloud storage. Specifically, the association identifier is used to quickly locate and retrieve the file in subsequent processing, ensuring that the management end can accurately access the required image.

[0072] In some optional embodiments, the storage address of the bill image file is usually located in the management end or a shared storage system, rather than locally on the client side, because the management end needs to centrally manage and securely store these files, but the client side can temporarily cache the file address information to assist in association.

[0073] For example, the management end is usually a back-end server system, and in actual application, the management end can be connected to a bank's credit service system or other financial processing platform, responsible for coordinating the bill processing flow. Specifically, the management end performs bill processing based on the processing request in the instruction package, which can be triggered by an automated program, such as automatically parsing the request and performing corresponding operations based on a rule engine or workflow system, or manually confirmed by bank staff through a management interface and then started when human intervention is required.

[0074] In this example, the management end associates the bill image file corresponding to the processing request to the bill opening agreement corresponding to the processing request based on the association identifier, which means that the management end uses the association identifier to obtain the bill image file from the storage when processing the request, and dynamically associates it with the relevant bill opening agreement (such as an electronic agreement or transaction record), thereby ensuring the integrity and traceability of the bill information, and ultimately completing the processing flow.

[0075] The bill image file processing method provided by the present application includes: the client responds to a plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, associates the bill image file corresponding to each processing request to the instruction package based on an association identifier, and sends the instruction package to the management end, so that when the management end performs bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is associated to the bill opening agreement corresponding to the processing request based on the association identifier, to complete the processing. The scheme of the present application packs a plurality of processing requests in batches and associates them with corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly attached and reused after the bill opening agreement is deleted, thereby improving the efficiency of bill image file processing.

[0076] Figure 5 The flowchart of the bill image file processing method provided by the present application embodiment is shown in FIG. Figure 5 As shown, the method further includes:

[0077] S501, in response to the selection instruction, a plurality of second processing requests are executed to perform billing processing, based on the association identifier, the corresponding bill image file of each second processing request is located, and the type of the bill image file corresponding to each second processing request is determined;

[0078] S502, based on the type of the bill image file corresponding to each second processing request, the billing agreement of the second processing request is connected.

[0079] In some embodiments, the selection instruction is used to select a plurality of second processing requests under the instruction package to perform billing processing, and the corresponding execution subject is usually executed by the operator of the management end or the automatic audit program. For example, the operator can select a plurality of requests to be processed from a received instruction package by checking on the system interface of the management end; the automatic program can automatically generate the selection instruction based on the preset rule (such as all the requests with the status of "audit passed"); and the management end will capture this selection action and convert it into an explicit selection instruction.

[0080] For example, based on the association identifier, the corresponding bill image file of each second processing request is located, that is, the management end retrieves all bill image files bound to each request based on the unique association identifier of each request from the file storage system. Then, by analyzing the metadata or content characteristics of these files, the specific type of each file is determined, such as identifying which file is an identity card and which file is a trade contract.

[0081] Further, based on the type of the bill image file corresponding to each second processing request, the billing agreement of the second processing request is connected, that is, the management end will classify and associate the files according to the type when generating or updating the electronic billing agreement. For example, the qualification certificate file is connected to the customer information section of the agreement, and the trade contract is connected to the business background clause of the agreement, so as to build a clear structure and complete evidence of digital protocol archive.

[0082] For example, the management end operator selects three acceptance requests from an instruction package to perform batch billing processing. The management end first locates the corresponding bill image file set of each request according to the association identifier of each request, and identifies different types of files including business license, identity card and purchase and sale contract. Then, the system generates an electronic billing agreement for each of the three requests, and connects the business license as a qualification certificate, the identity card as an identity verification file, and the purchase and sale contract as a transaction background certificate, thereby completing the entire batch of agreement making.

[0083] The scheme of the example realizes the classification and connection of batch processing requests and their bill image files, and improves the generation efficiency and structural level of the billing agreement.

[0084] Figure 6 A flowchart of a bill image file processing method provided by an embodiment of the present application is shown in FIG. 1. As shown in FIG. 1, the method further includes the following steps. Figure 6

[0085] S601, receiving a verification result of a bill image file under a bill issuance agreement;

[0086] S602, when the verification result is not passed, taking the bill image file that does not pass as a bill image file to be supplemented, and sending a supplement instruction to the client; wherein the supplement instruction includes a type identifier of the bill image file to be supplemented.

[0087] In some embodiments, the determination of the verification result can be completed by combining the automatic technology and manual review. For example, the management end can be built-in with image processing and content recognition functions, and automatically perform preliminary verification on the bill image file, such as checking the clarity, integrity, and format of the file to see if they meet the requirements, or checking whether the key information is clear and readable and whether there is a contradiction by using optical character recognition technology. Optionally, for complex situations that cannot be completely judged by the automatic tool, such as the compliance of the contract terms and the authenticity of the seal, the staff of the management end still needs to perform the final manual review on the review interface, and manually submit the verification result by clicking the “verification not passed” button on the interface or the like.

[0088] For example, when the verification result is not passed, the system will mark the specific bill image file that fails the review as a bill image file to be supplemented, and automatically generate a supplement instruction sent to the client.

[0089] In some optional embodiments, the instruction not only indicates which file under which processing request needs to be resubmitted, but also includes an explicit type identifier, such as “the business license image is blurred, please upload a clear version” or “the legal representative signature page is missing”, so as to accurately inform the user of the specific type of the file to be supplemented and the supplement requirements, and guide the user to submit the correct file that meets the standards.

[0090] The scheme of the present example can construct a feedback closed loop based on the precise type identifier through the verification of the bill image file, and improve the efficiency and accuracy of the bill image file review and supplement process.

[0091] ​The bill image file processing method provided in the application comprises: a client responds to a plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, associates a bill image file corresponding to each processing request to the instruction package based on an association identifier, and sends the instruction package to a management end, so that when the management end performs bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to a bill processing protocol corresponding to the processing request based on the association identifier to complete the processing. The scheme of the application packs a plurality of processing requests in batches and associates the corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly hung and reused after the bill processing protocol is deleted, thereby improving the efficiency of bill image file processing.

[0092] The application further provides a client for:

[0093] The client responds to a plurality of processing requests, obtains bill image files corresponding to the plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, and associates a bill image file corresponding to each processing request to the instruction package based on an association identifier. The association identifier is used to obtain a storage address of the bill image file to locate the bill image file. The instruction package is sent to a management end, so that when the management end performs bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to a bill processing protocol corresponding to the processing request based on the association identifier to complete the processing.

[0094] In actual application, the client for executing the bill image file processing method can have various forms, such as an online bank end. Alternatively, the client can also be a mobile bank application, an enterprise financial software end, or a special bill processing platform end. In actual application, these clients are usually integrated in digital services of financial institutions or enterprises to provide users with convenient bill processing functions.

[0095] In some embodiments, the processing request is usually initiated by a user through the client, involves related operations of a draft or a check, such as a draft acceptance request, a check cashing application, a bill discount processing, or a endorsement transfer, and the like, and these requests aim to complete financial transactions or management processes of bills.

[0096] For example, the occurrence of multiple processing requests can be due to a user submitting a plurality of bill processing tasks in batches within a certain time, such as uploading multiple bill image files for processing in one session, or the bill image files corresponding to the requests have the same business background, such as multiple bills belonging to the same transaction or the same customer. In this example, this batch processing method can improve efficiency and reduce repetitive operations. Further, the packaging of multiple processing requests to obtain an instruction package can be implemented by a logical module of the client software. Specifically, message queues or batch processing techniques can be used to aggregate the requests into one data package, which contains the metadata and associated information of all processing requests, to optimize network transmission, reduce the number of interactions with the management end, and improve processing efficiency, especially in high-concurrency scenarios, which can significantly reduce system load.

[0097] It should be understood that the examples do not limit the scope of the bill image file to the image of the bill itself, but include all auxiliary proofs and contractual documents necessary to complete the bill processing request. For example, the bill image file can also include legal identification documents representing the identity and qualifications of an enterprise or an individual, trade contracts closely related to the bill transaction background, cargo transport documents, invoice copies, and agreement documents proving the relationship between debt and credit. In practical applications, in order to meet the risk control requirements of specific businesses, the electronic images of the qualifications provided by the client and the written materials required by the bank can also be considered as important components of the bill image file. Therefore, the above-mentioned files collectively constitute the basis system for the management end to perform bill processing, auditing, and archiving.

[0098] In some embodiments, associating the bill image file corresponding to each processing request to the instruction package based on the association identifier is achieved by generating a unique identifier (such as a hash value) on the client side. The association identifier is bound to the storage address of the bill image file, such as the path of the file in the server or cloud storage. Specifically, the association identifier is used to quickly locate and retrieve the file in subsequent processing, ensuring that the management end can accurately access the required image.

[0099] In some optional embodiments, the storage address of the bill image file is usually located in the management end or a shared storage system, rather than locally on the client side, because the management end needs to centrally manage and securely store these files, but the client side can temporarily cache the file address information to assist in association.

[0100] The management end is typically a back-end server system. In actual applications, the management end can be connected to a bank's credit service system or other financial processing platform, and is responsible for coordinating the bill processing flow. Specifically, the management end executes the bill processing based on the processing request in the instruction package, which can be triggered by an automated program, for example, based on a rule engine or a workflow system to automatically analyze the request and perform corresponding operations, or can be started manually by bank staff through a management interface when human intervention is required.

[0101] In this example, the management end links the bill image file corresponding to the processing request to the bill processing agreement corresponding to the processing request based on the association identifier. This means that when processing a request, the management end uses the association identifier to obtain the bill image file from storage and dynamically associates it with the relevant bill processing agreement (such as an electronic agreement or transaction record), thereby ensuring the integrity and traceability of the bill information and ultimately completing the processing flow.

[0102] The client provided by the present application responds to multiple processing requests, packages the multiple processing requests to obtain an instruction package, associates the bill image file corresponding to each processing request to the instruction package based on the association identifier, and sends the instruction package to the management end. When the management end executes the bill processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is linked to the bill processing agreement corresponding to the processing request based on the association identifier to complete the processing. The scheme of the present application packages multiple processing requests in batches and associates them with corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly linked and reused after the bill processing agreement is deleted, thereby improving the efficiency of bill image file processing.

[0103] In some examples, the client is further configured to:

[0104] In response to the supplement request, the supplement image file is obtained; wherein the supplement request includes the identifier of the first processing request in the instruction package; the instruction package is determined according to the identifier of the first processing request, and the first bill image file is located according to the association identifier; the first bill image file is the bill image file corresponding to the first processing request; and the supplement image file is updated to the first bill image file.

[0105] In some examples, the client is further configured to:

[0106] In response to the supplement request, the supplement image file is obtained; wherein the supplement request includes the identifier of the first processing request in the instruction package; the instruction package is determined according to the identifier of the first processing request, and the first bill image file is located according to the association identifier; the first bill image file is the bill image file corresponding to the first processing request; and the supplement image file is updated to the first bill image file.

[0107] In some examples, the client is further configured to: receive a supplement instruction sent by the management terminal, the supplement instruction comprising a type identifier of the bill image file to be supplemented.

[0108] The embodiment of the present application further provides a management terminal, which is used for:

[0109] receiving an instruction package sent by the user terminal, the instruction package being obtained by the user terminal by packing a plurality of processing requests after responding to the plurality of processing requests and obtaining bill image files corresponding to the plurality of processing requests; wherein the instruction package is associated to the bill image file corresponding to each processing request based on an association identifier, the association identifier being used to obtain a storage address of the bill image file to locate the bill image file; and the processing request is executed to perform the billing processing based on the instruction package, and the bill image file corresponding to the processing request is hung to the billing protocol corresponding to the processing request based on the association identifier to complete the processing.

[0110] In some examples, the management terminal is further configured to:

[0111] in response to the selection instruction package and the plurality of second processing requests, locate the bill image file corresponding to each second processing request based on the association identifier, and determine the type of the bill image file corresponding to each second processing request; and based on the type of the bill image file corresponding to each second processing request, the billing protocol corresponding to the second processing request is hung.

[0112] In some examples, the management terminal is further configured to:

[0113] receiving a verification result of the bill image file under the billing protocol;

[0114] when the verification result is not passed, the bill image file that is not passed is taken as the bill image file to be supplemented, and a supplement instruction is sent to the client; wherein the supplement instruction comprises a type identifier of the bill image file to be supplemented.

[0115] The management terminal and the client provided by the present application interact to realize bill image file processing, wherein the client responds to a plurality of processing requests, packs the plurality of processing requests to obtain an instruction package, associates the bill image file corresponding to each processing request to the instruction package based on an association identifier, and sends the instruction package to the management terminal, so that when the management terminal executes the billing processing based on the processing request in the instruction package, the bill image file corresponding to the processing request is hung to the billing protocol corresponding to the processing request based on the association identifier to complete the processing. The scheme of the present application packs a plurality of processing requests in batches and associates the corresponding bill image files, links to the storage address of the bill image file based on the association identifier, and the bill image file can still be directly hung and reused after the billing protocol is deleted, thereby improving the efficiency of bill image file processing.

[0116] Figure 7A structural schematic diagram of a bill image file processing system provided by an embodiment of the present application is shown in the figure, wherein the system comprises the client 71 of any of the above embodiments and the management end 72 of any of the above embodiments.

[0117] It should be noted that, for the above-mentioned method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the action sequence described, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.

[0118] It should be further noted that, although each step in the flowchart is shown in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise stated in this article, the execution of these steps has no strict sequence limitation, and these steps can be executed in other sequences. Moreover, at least part of the steps in the flowchart can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence of these sub-steps or stages is not necessarily sequential, but can be executed with at least part of other steps or sub-steps or stages of other steps in rotation or alternation.

[0119] It should be understood that the above-mentioned device embodiments are only schematic, and the device of the present application can also be realized by other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical functional division, and actual implementation can have another division way. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0120] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application can be integrated in one unit / module, or each unit / module can exist physically, or two or more units / modules can be integrated together. The above-mentioned integrated unit / module can be realized in the form of hardware or in the form of software program module.

[0121] If the integrated units / modules are implemented in the form of software program modules and sold or used as independent products, they can be stored in a computer readable memory. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a memory and includes a number of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the embodiments of the method of the present application. The aforementioned memory includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

[0122] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described, however, as long as the combinations of the technical features do not exist contradictory, they should be considered as the scope of the present application.

[0123] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The application is intended to cover any variations, uses or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the application pertains or can relate. The specification and examples are to be regarded as exemplary only, and the true scope and spirit of the application are indicated by the following claims.

[0124] It should be understood that the application is not limited to the precise construction that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is limited only by the appended claims.

Claims

1. A method for processing invoice image files, characterized in that, Applied to a client, the method includes: Responding to multiple processing requests, obtain the ticket image files corresponding to the multiple processing requests; The multiple processing requests are packaged into an instruction package, and the ticket image file corresponding to each processing request is associated with the instruction package based on the association identifier; wherein, the association identifier is used to obtain the storage address of the ticket image file to locate the ticket image file; The instruction packet is sent to the management terminal so that when the management terminal performs invoicing processing based on the processing request in the instruction packet, it attaches the invoice image file corresponding to the processing request to the invoicing protocol corresponding to the processing request based on the association identifier to complete the processing.

2. The method according to claim 1, characterized in that, The method further includes: In response to a supplementary request, supplementary image files are obtained; wherein, the supplementary request includes an identifier of the first processing request in the instruction packet; The instruction packet is determined based on the identifier of the first processing request, and the first invoice image file is located based on the association identifier; the first invoice image file is the invoice image file corresponding to the first processing request. Update the supplementary image file to the first ticket image file.

3. The method according to claim 1, characterized in that, The method further includes: In response to a supplementary request, supplementary image files are obtained; wherein, the supplementary request includes the identifier of the instruction packet; The second ticket image file is located based on the associated identifier, and the second ticket image file is the ticket image file corresponding to each processing request in the instruction packet; Update the supplementary image file to the second ticket image file.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The system receives a supplementary instruction from the management terminal, which includes the type identifier of the ticket image file to be supplemented.

5. A method for processing invoice image files, characterized in that, Applied to the management end, the method includes: The system receives instruction packets sent by the user terminal. The instruction packet is obtained by the user terminal after responding to multiple processing requests and obtaining the ticket image files corresponding to the multiple processing requests, and then packaging the multiple processing requests together. The instruction packet is associated with the ticket image file corresponding to each processing request based on an association identifier, and the association identifier is used to obtain the storage address of the ticket image file to locate the ticket image file. The invoicing process is executed in response to the processing request in the instruction packet. The invoice image file corresponding to the processing request is attached to the invoicing protocol corresponding to the processing request based on the association identifier to complete the processing.

6. The method according to claim 5, characterized in that, The method specifically includes: In response to multiple second processing requests under the selection instruction package, invoicing processing is performed, the invoice image file corresponding to each second processing request is located based on the association identifier, and the type of the invoice image file corresponding to each second processing request is determined; Based on the type of the invoice image file corresponding to each second processing request, the invoicing protocol is attached to that second processing request.

7. The method according to claim 6, characterized in that, The method further includes: Receive the verification result of the invoice image file under the invoicing agreement; When the verification result is unsuccessful, the unsuccessful ticket image file is used as a ticket image file to be supplemented, and a supplementation instruction is sent to the client; wherein, the supplementation instruction includes the type identifier of the ticket image file to be supplemented.

8. A client application, characterized in that, Used for: Responding to multiple processing requests, obtain the ticket image files corresponding to the multiple processing requests; The multiple processing requests are packaged into an instruction package, and the ticket image file corresponding to each processing request is associated with the instruction package based on the association identifier; wherein, the association identifier is used to obtain the storage address of the ticket image file to locate the ticket image file; The instruction packet is sent to the management terminal so that when the management terminal performs invoicing processing based on the processing request in the instruction packet, it attaches the invoice image file corresponding to the processing request to the invoicing protocol corresponding to the processing request based on the association identifier to complete the processing.

9. A management terminal, characterized in that, Used for: The system receives instruction packets sent by the user terminal. The instruction packet is obtained by the user terminal after responding to multiple processing requests and obtaining the ticket image files corresponding to the multiple processing requests, and then packaging the multiple processing requests together. The instruction packet is associated with the ticket image file corresponding to each processing request based on an association identifier, and the association identifier is used to obtain the storage address of the ticket image file to locate the ticket image file. The invoicing process is executed in response to the processing request in the instruction packet. The invoice image file corresponding to the processing request is attached to the invoicing protocol corresponding to the processing request based on the association identifier to complete the processing.

10. A ticket image file processing system, characterized in that, The system includes the client as described in claim 8 and the management terminal as described in claim 9.

Images