An error file processing method and device, a storage medium and a program product

Abstract

Embodiments of the present specification provide an error file processing method and device, a storage medium and a program product, which can be applied to the field of big data technology. The method comprises: sending an error file to an audit terminal to enable the audit terminal to audit the error file; in the case of receiving audit pass information, matching a business attribution component corresponding to the error file; determining a target account based on the business attribution component corresponding to the error file; in the case that the error file meets the account adjustment condition, obtaining a declaration document corresponding to the error file; and processing the error file based on the target account and the declaration document. The above method guarantees the automatic processing process of the error file, can match the corresponding component based on the nature of the error file, thereby processing the error file based on the obtained information, reducing the workload of manually processing the error file, and being conducive to dealing with complex and variable error file processing situations.

Description

TECHNICAL FIELD

[0001] Embodiments of the present specification relate to the technical field of big data, and in particular, to an error file processing method and device, a storage medium and a program product. BACKGROUND

[0002] In the daily business processing flow of banks and third-party payment institutions, errors are inevitable. Especially when the business involves fund mobilization, if errors are found after verification, the errors must be cleared to remedy the loss of the accounts involved in the errors. When clearing errors, the specific business end generally generates corresponding error files based on error information, and then submits the error files to the corresponding processing agencies or data centers for processing of the error files.

[0003] In the past, when processing error files, since the number of error files was not large, the error files were generally directly assigned to corresponding processing personnel for manual processing. However, with the development of society and the increase of business volume, the number of errors occurring in the business processing process is increasing, and the types of error files are more complex. The previous manual processing method not only greatly increases the workload of the processing personnel, but also has higher requirements for the error file processing capacity of the processing personnel, making the manual processing method no longer suitable for the current error file processing situation. Therefore, there is an urgent need for a method that can conveniently and effectively process error files. SUMMARY

[0004] The purpose of the embodiments of the present specification is to provide an error file processing method, device, storage medium and program product to solve the problem of how to conveniently and effectively automatically process error files.

[0005] To solve the above technical problems, the embodiments of the present specification provide an error file processing method, comprising: sending an error file to an audit terminal to enable the audit terminal to audit the error file; in the case of receiving audit pass information, matching a business attribution component corresponding to the error file; determining a target account based on the business attribution component corresponding to the error file; in the case that the error file meets the account adjustment condition, obtaining a declaration document corresponding to the error file; and processing the error file based on the target account and the declaration document.

[0006] The error file processing apparatus provided by the embodiments of the present specification comprises: an error file sending module configured to send an error file to an auditing terminal, so that the auditing terminal audits the error file; a service attribution component matching module configured to match a service attribution component corresponding to the error file in a case where audit pass information is received; a target account determining module configured to determine a target account based on the service attribution component corresponding to the error file; a declaration document obtaining module configured to obtain a declaration document corresponding to the error file in a case where the error file meets a account adjustment condition; and an error file processing module configured to process the error file based on the target account and the declaration document.

[0007] The embodiments of the present specification also provide a computer readable storage medium having computer programs / instructions stored thereon, the computer programs / instructions, when executed by a processor, implement the error file processing method described above.

[0008] The embodiments of the present specification also provide a computer program product comprising computer programs / instructions, the computer programs / instructions, when executed by a processor, implement the error file processing method described above.

[0009] As can be seen from the technical solutions provided by the embodiments of the present specification, after receiving an error file, the embodiments of the present specification audit the error file by an auditing terminal, which preliminarily ensures the processability of the error file. After the audit passes, the service attribution component corresponding to the error file is matched, and then the corresponding target account is determined, and the declaration document of the error file is obtained, so that the error file can be processed directly based on the obtained target account and declaration document. The above process guarantees the automatic processing process of the error file, and the corresponding component can be matched based on the nature of the error file, so that the error file is processed based on the obtained information, which reduces the workload of manually processing the error file, and is conducive to dealing with complex and variable error file processing situations. BRIEF DESCRIPTION OF DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present specification, and other drawings can be obtained by those skilled in the art without creative labor.

[0011] Figure 1 A flowchart of an error file processing method according to an embodiment of the present specification;

[0012] Figure 2 A flowchart of an account adjustment process according to an embodiment of the present specification;

[0013] Figure 3 A flowchart of an error file processing method according to an embodiment of the present specification is shown in FIG. 1.

[0014] Figure 4 A module diagram of an error file processing device according to an embodiment of the present specification is shown in FIG. 2. DETAILED DESCRIPTION

[0015] The technical solutions in the embodiments of the present specification will be described clearly and completely below with reference to the drawings in the embodiments of the present specification. Obviously, the described embodiments are only part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by a person of ordinary skill in the art without creative work should fall within the protection scope of the present specification.

[0016] To solve the above technical problems, an error file processing method is provided in the embodiments of the present specification. The execution subject of the error file processing method is an error file processing device, which includes but is not limited to a server, a distributed processing system, an industrial computer, a PC, etc. As shown in FIG. 1, the error file processing method can include the following specific implementation steps. Figure 1

[0017] S110: sending the error file to an auditing terminal to make the auditing terminal audit the error file.

[0018] The error file is a file related to errors in the business processing process. When an error occurs, the error needs to be checked and modified to make up for the error in the business process and eliminate the loss of the institution and the user. Although errors generally occur in basic institutions such as banks and payment institutions, error files generally need to be sent to a data center for auditing and processing to ensure the authority of the processing results.

[0019] Since the processing of error files may involve changes in account funds, the error files generally need to be audited before being formally processed to ensure the validity and correctness of the data in the error files.

[0020] Specifically, in the embodiments of the present specification, the error file is sent to the auditing terminal for auditing. The auditing terminal is a terminal device corresponding to a business processor for preliminary auditing of the error file. The business processor can audit the error file based on the preset auditing standard based on the error file received by the auditing terminal. Specifically, it can include whether the error file lacks data to be supplemented, or whether the data in the error file is not in line with the standard. In specific implementation, the error file can also be directly audited by the auditing terminal based on the processing file of the audited error file to reduce the consumption of human resources.

[0021] ​In some embodiments, the auditing terminal includes an undertaking terminal and a reviewing terminal. The undertaking terminal and the reviewing terminal can audit different types of error files. Specifically, the error files can include adjustment files and detail files. The adjustment files can be files that provide an overview of the error information, mainly describing the overall nature of the error. The detail files can be files that describe the details of the error, such as specific account transaction information.

[0022] To ensure the effectiveness of each step, the adjustment file can be sent to the undertaking terminal first, and after the undertaking terminal audits and passes, the detail file can be sent to the reviewing terminal for further auditing.

[0023] Specifically, the undertaking terminal can query the corresponding snapshot information based on the batch information to audit the adjustment file. The batch information can include the clearing date, the channel, the batch number, etc., which is not limited in actual application.

[0024] If the audit result of the adjustment file based on the audit of the undertaking terminal is abnormal, the overall file of the error file has an error, such as a lack of a certain type of data in the error file or an error in the generation process of the error file, the audit abnormal information can be fed back to the error file processing device.

[0025] The error file processing device receives the audit abnormal information fed back by the undertaking terminal, indicating that the current error file has an error in the generation process, and the generation process of the error file can be re-executed. The generation process of the error file will be described in subsequent embodiments, and will not be described here.

[0026] In the case where the undertaking terminal audits and passes, the reviewing terminal also needs to audit the detail file in the error file. If the audit passes, the subsequent formal processing procedure can be executed; if the audit fails, it means that the data of the error file itself has a problem, and the error file may not be processed. In the case where the audit fails, the reviewing terminal can also feed back the corresponding audit abnormal information to the error file processing device.

[0027] The error file processing device receives the audit abnormal information sent by the reviewing terminal, and can terminate the current processing procedure of the error file. The reviewing terminal sends the audit abnormal information, indicating that the data of the error file itself has a problem, such as an irregular data format or an error in the data itself, and the error file cannot be processed, so the current processing procedure of the error file can be terminated. Correspondingly, the corresponding notification can be sent to the submitting agency of the error file.

[0028] After the terminal for auditing passes the error file, the terminal for auditing can feed back the passing information corresponding to the error file to inform that the error file passes the auditing, and the subsequent processing steps can be performed on the error file.

[0029] The process of auditing the error file by the terminal for auditing can be set based on the actual application requirements, and will not be described here.

[0030] In some embodiments, before the error file is sent to the terminal for auditing, the current device must involve the reception of the error file. The error file can be obtained by summarizing the initial clearing files sent by banks or payment institutions. The process of obtaining the error file based on the initial clearing file can be to parse the initial clearing file to obtain error file data under the condition that the initial clearing file meets the batch processing dependent condition; the batch processing dependent condition includes that the type of the initial clearing file meets the preset error file type requirement; and the error file is obtained by summarizing the error file data based on the preset data type.

[0031] Specifically, the error file processing device first receives the initial clearing files sent by different banks and payment institutions. The error file processing device first determines whether the initial clearing file meets the batch processing dependent condition based on the initial clearing file. The initial clearing file corresponds to different file types. Generally, all initial clearing files corresponding to a clearing process need to be obtained before the corresponding clearing process can be effectively performed.

[0032] The preset error file type requirement is that all file types that the initial clearing file needs to meet in order to effectively process the error file are preset. For example, three different types of initial clearing files correspond to the same error file, and the batch processing dependent condition can be that the same error file has three different types of initial clearing files. The specific preset error file type can be set based on the actual application requirements, and will not be described here.

[0033] The initial clearing file can have a corresponding identifier, and the initial clearing file corresponding to the same error file can be extracted from all initial clearing files by reading the identifier, so that the initial clearing file can be identified and summarized even if the initial clearing file is sent to the error file processing device in chronological order.

[0034] After the batch processing dependency condition is started, a parsing and warehousing process corresponding to the initial clearing file can be started. First, the initial clearing file needs to be parsed to obtain error file data. By parsing the initial clearing file, the data in the initial clearing file can be effectively sorted, and the uniformity of the format of the error file obtained by summarizing is ensured. Specifically, the error file data can be sorted based on batch information to obtain error file data; the batch information includes at least one of a clearing channel, a clearing date, and a batch number. Based on the clearing channel, the clearing date, and the batch number, the error file can be effectively sorted and classified to ensure the speed and effectiveness of error file processing.

[0035] After obtaining the error file data, the error file data can be summarized based on a preset data type to obtain a final error file. The error file can essentially be a data table. The error file is preconfigured with a corresponding data table format. Based on the data table format embodied by the error file, after the error file data is imported into the data table corresponding to the error file, the data summarization is completed, the error file is obtained, and subsequent processing of the error file can be implemented.

[0036] The preset data type can be a data type defined in the error file, and the data in the error file can be effectively sorted and divided. In some embodiments, the preset data type includes at least one of an error total amount, a total amount to be received, a total amount to be paid, a total number of amounts to be received, a total number of amounts to be paid, a total number of errors, and snapshot information. In actual application, the preset data type can be modified according to the specific type of error file data, and is not limited to the above examples, which will not be described here.

[0037] In some embodiments, the error file involves a change in funds. In order to effectively mobilize funds in subsequent steps, the error fund amount corresponding to the error file can be determined first, and the error fund amount can be booked to an error clearing account based on the error fund amount. The error fund booked in the error clearing account is a temporary fund, and does not involve interaction with the actual personal account until the error file processing is completed.

[0038] S120: In the case where the audit pass information is received, the business attribution component corresponding to the error file is matched.

[0039] If the audit pass information sent by the audit terminal is received, it indicates that there is no major problem with the error file itself, and the error file can be directly processed.

[0040] The business attribution component can be a processing module preset for different business types, and corresponding business processing logic is set based on different business characteristics, so as to realize automatic processing of error files.

[0041] Specifically, the business attribution component can include, for example, a payment settlement component, a credit card component, a collection component, and an electronic banking component, and can perform corresponding processing operations for payment business, credit card business, collection business, and electronic banking business, respectively.

[0042] In some embodiments, the process of matching the business attribution component corresponding to the error file can be to first determine the corresponding business scenario type based on the business data in the error file, and then determine the business attribution component corresponding to the business scenario type.

[0043] The business scenario type is used to describe the actual application scenario of the business corresponding to the error file. Since the error file is generated in the process of business processing for the error generated, there is a corresponding relationship between the error file and the actual business scenario. Since there is a corresponding relationship between the business scenario type and the business attribution component, based on the foregoing exemplary description of the business attribution component, the business scenario type can also include a payment settlement scenario, a credit scenario, a collection scenario, and an electronic banking scenario, etc. Additional business scenario types and business attribution components can be set based on demand in actual application, and are not limited to the foregoing examples, which are not limited.

[0044] Determining the business scenario type can be based on the business data in the error file. The business data can include at least one of an institution number, a batch number, a transaction type, an error type, a card number, a merchant number, and a terminal number. In different business scenarios, the business data generated when the business is executed often has different rules corresponding to the business scenario, so the business data corresponding business scenario can be determined by analyzing the business data. The error file generally also contains business data, and the corresponding business scenario type can also be determined based on the business data in the error file, and then the business attribution component is determined.

[0045] In the specific execution process, in order to facilitate subsequent processing, the number corresponding to the determined business attribution component can be recorded in a data table, so as to effectively call the business component in the case of a large number of error files.

[0046] In some special execution processes, the error file may not be directly found based on the existing matching logic when matching the business scenario type, and the error file can be added to the waiting queue after the business scenario type is determined based on the above process. The waiting queue is a queue for storing error files waiting to be manually determined for the business scenario type. Specifically, the operator of the handling terminal can view the waiting queue and extract the error file from the waiting queue. The operator can determine the business scenario type and / or the business attribution component of the error file based on actual processing experience, and then feed back to the error file processing device to ensure the effective execution of the subsequent process.

[0047] S130: determining a target account based on the business attribution component corresponding to the error file.

[0048] After obtaining the business attribution component, the target account can be determined according to the business component. The target account can be a target internal account corresponding to the internal account. Since different error files involve internal accounting processes, the error needs to be processed based on the internal account.

[0049] The target account and the business attribution component can be pre-set to correspond to each other, so as to determine the corresponding target account according to the business attribution component. Preferably, when determining the target account, the business component, the agency number and the transaction currency information can be combined to determine the target account. The agency number and the transaction currency information can be obtained from the error file.

[0050] In practical applications, the target account can also be determined based on the business attribution component in combination with other types of information, and is not limited to the above examples, which will not be described here.

[0051] S140: obtaining a declaration document corresponding to the error file if the error file meets the account adjustment condition.

[0052] Since the error file generally involves the movement of funds in the actual account, when processing the error file, it is also necessary to determine whether the error file meets the account adjustment condition. The account adjustment condition is used to determine whether the error file can be automatically processed based on the current error file processing logic.

[0053] Specifically, after determining the business belonging component, information of the error file can be written into the to-be-processed document first, for recording key information corresponding to the error file. In this step, it can be determined according to the key information contained in the to-be-processed document whether the error file meets the reconciliation condition. The key information may, for example, include at least one of a card number, a reconciliation type, a reconciliation amount, a business component number, a target internal account number, a merchant number, and a terminal number. Requirements and restrictions corresponding to the reconciliation condition can be set in advance for the key information, for example, part of the content of the card number is subject to format restrictions, the reconciliation type has preset type restrictions, and the like. The setting of the reconciliation condition can be based on actual processing capacity, which will not be described here.

[0054] After determining that the error file meets the reconciliation condition, the to-be-processed document can be marked, and a corresponding document is matched as a declaration document corresponding to the error file from a data table corresponding to the error file according to information such as the reconciliation type, the clearing date, the reconciliation amount, the card number, and the system tracking number.

[0055] If the error file does not meet the reconciliation condition based on the judgment, that is, the error file cannot be automatically processed, the error file can be submitted to a corresponding manual processing terminal for manual processing by a corresponding operator.

[0056] S150: processing the error file based on the target account and the declaration document.

[0057] After determining the target account and the declaration document, the final processing of the error file can be completed, that is, in the case of fund change involved in the error file, the error fund is deducted from the account; in the case of data error involved in the error file, the data of the error file is corrected.

[0058] Since the corresponding processing logic is set in the system, the automatic processing of the error file can be completed according to the processing logic in combination with the target account and the declaration document.

[0059] In some embodiments, the process of processing the error file can be to deduct the account resource corresponding to the error file to the target account based on the declaration document first; the target account includes a business component to-be-cleared account. In the foregoing processing process, the account resource corresponding to the error file can be registered in the target internal account in advance, and therefore the account resource in the target internal account can be deducted to the business component to-be-cleared account in this step. Since the declaration document can embody specific deduction amount and specific type of the account resource and the like, the foregoing step can be automatically completed.

[0060] Subsequently, based on the account relationship corresponding to the error file, the account resources in the target account can be transferred to at least one corresponding personal account. After the account resources are transferred to the personal account, the conversion of account resources from internal accounts to external accounts is realized, thereby completing the processing of the error file.

[0061] In some implementations, the transfer of account resources from the target account to at least one corresponding individual account may fail. In this case, the information on the declaration form may be incorrect. The account resources from the target account can be transferred to the branch's pending settlement account first, allowing branch staff to supplement the error document information. After the branch staff supplements the corresponding error document information based on the problems, the aforementioned steps are repeated based on the supplemented information, and finally, the account resources from the branch's pending settlement account are transferred to the at least one corresponding individual account.

[0062] Based on the above implementation method, situations may arise where supplementation fails. For example, the error file itself may be faulty, or the branch operator may not be able to directly determine the required supplementary error file information based on the current error file and the problem. In such cases, the branch operator can report the corresponding supplementation failure information. Upon receiving the supplementation failure information, if the error file processing device cannot automatically complete the processing of the error file, it can forward the error file to the handling terminal so that the operator can process the error file.

[0063] To illustrate the above adjustment process, let's take a specific example, such as... Figure 2 The diagram illustrates a process for adjusting accounts. First, step 151 is executed, transferring account resources from the primary bank's error-pending account to the corresponding primary bank business component's pending account. Then, step 152 completes the transfer of account resources (principal and fees) from the primary bank business component's pending account to the customer's personal account and corresponding fee account. If successful, step 153 determines that the account has been successfully posted, thus completing the automatic processing of the error file. If the posting fails, step 154 ​​is executed, transferring account resources from the primary bank's error-pending account to the branch service component's pending account, followed by step 155, where the branch staff supplements the valid deposit card number, merchant number, terminal number, and other information. Generally, after step 155, step 156 is executed directly, transferring account resources (principal and fees) from the branch service component's pending account to the customer's personal account and corresponding fee account. In specific situations, such as when there is no valid deposit card number, step 159 is executed, switching to manual processing to complete the process. After executing step 156, execute judgment step 157 to determine whether the account has been successfully posted. If the account was successfully posted, the process is completed; if the account was not posted, proceed to step 158 for manual processing and completion of the process.

[0064] Based on the above introduction, combined with Figure 3 , a specific error file comprehensive processing flowchart is further described. First, steps 310 to 350 are executed to complete the generation of the error file. Specifically, in step 310, after the file dependency is met, the batch processing flow is triggered directly, and step 320 is executed to clean up the data according to the channel, clearing date, and file batch number. Then, based on different error clearing file data A 331, error clearing file data B 332, etc., step 340 is executed to perform batch processing clearing data processing, and the data is uniformly processed to an error account adjustment temporary table. In step 350, the total amount of errors, the total amount of receivables, the total amount of payables, the total number of receivables, the total number of payables, and the total number of errors are summarized according to the first-line agency dimension, thereby realizing the generation of the error file.

[0065] Then, based on the obtained error file, step 360 is executed, the first-line clearing agent selects the clearing date and batch number for auditing, and step 370 is executed to judge the batch processing state, the total amount, the receivable amount, the payable amount, the detail strategy, and whether it is abnormal. If there is an exception, return to step 310 to complete the generation of the error file again. If there is no exception, if the audit is passed, execute step 380, the first-line clearing review post selects the clearing date and batch number for review. If the review is passed, execute step 390, based on the key information matching the business scenario to associate the components, and retrieve the target internal account number. If it does not pass, terminate the current batch processing directly. For step 390, if the association is successful, execute step 3100 to judge whether the automatic accounting condition is met. If the association fails, execute step 3110, the error clearing agent queries and fills in the key information manually to select the associated business component. Correspondingly, after step 3110 is executed, if the accounting condition is met, execute step 3130 directly, the error account adjustment temporary table is processed to the error account adjustment table, and the local error account report document is matched based on the key information of the error account adjustment, and waits for automatic entry. If it is not met, it is also executed to step 3110. After step 3110 is executed, execute step 3120, the error clearing review post judges whether the relevant information is met. If it is met, return to step 390 to execute according to the process. If it is not met, return to step 3110 to supplement the information until the automatic entry is completed in step 3130.

[0066] Based on the introduction of the above embodiments and specific examples, the above error file processing method can preliminarily ensure the processability of the error file after receiving the error file, and the audit terminal audits the error file. After the audit is passed, the business attribution component corresponding to the error file is matched, and the corresponding target account is determined, and the declaration document of the error file is obtained, so that the error file can be processed directly based on the obtained target account and declaration document. The above process guarantees the automatic processing process of the error file, and can match the corresponding component based on the nature of the error file, so as to process the error file based on the obtained information, reduce the workload of manual processing of the error file, and be conducive to coping with complex and variable error file processing conditions.

[0067] Based on Figure 1 The corresponding error file processing method, the error file processing device is introduced. The error file processing device can be arranged on the error file processing equipment. As shown in Figure 4 The error file processing device includes the following modules.

[0068] The error file sending module 410 is configured to send the error file to the audit terminal, so that the audit terminal audits the error file.

[0069] The business attribution component matching module 420 is configured to match the business attribution component corresponding to the error file when the audit pass information is received.

[0070] The target account determination module 430 is configured to determine the target account based on the business attribution component corresponding to the error file.

[0071] The declaration document acquisition module 440 is configured to acquire the declaration document corresponding to the error file when the error file meets the account adjustment condition.

[0072] The error file processing module 450 is configured to process the error file based on the target account and the declaration document.

[0073] In some embodiments, the audit terminal includes an agent terminal and a review terminal; the error file includes an account adjustment file and a detailed file; the agent terminal is configured to audit the batch information of the account adjustment file; the review terminal is configured to audit the batch information of the detailed file; and the batch information includes at least one of a clearing channel, a clearing date, and a batch number.

[0074] Based on the foregoing embodiment, the device further comprises: an initial clearing file obtaining module, configured to obtain an initial clearing file corresponding to the error file in a case where the review exception information fed back by the handling terminal is received; a secondary error file generating module, configured to generate a secondary error file based on the initial clearing file; a secondary error file sending module, configured to send the secondary error file to the review terminal, so that the review terminal reviews the secondary error file; a secondary error file matching module, configured to match a business attribution component corresponding to the secondary error file in a case where the review pass information is received; a target account determining module, configured to determine a target account based on the business attribution component corresponding to the secondary error file; a declaration document obtaining module, configured to obtain a declaration document corresponding to the secondary error file in a case where the secondary error file meets the account adjustment condition; and a secondary error file processing module, configured to process the secondary error file based on the target account and the declaration document.

[0075] Based on the foregoing embodiment, the device further comprises: a processing flow termination module, configured to terminate the processing flow of the error file in a case where the review exception information fed back by the review terminal is received.

[0076] In some embodiments, the business attribution component matching module comprises: a business scenario type determining unit, configured to determine a corresponding business scenario type based on business data in the matching error file; the business data comprises at least one of an institution number, a batch number, a transaction type, an error type, a card number, a merchant number and a terminal number; and a business attribution component determining unit, configured to determine a business attribution component corresponding to the business scenario type; the business attribution component comprises at least one of a payment settlement component, a credit card component, a collection component and an electronic banking component.

[0077] Based on the foregoing embodiment, the business attribution component matching module further comprises: a waiting queue adding unit, configured to add the matching error file to a waiting queue, so that a user extracts the error file from the waiting queue based on the handling terminal for processing.

[0078] In some embodiments, the device further comprises: an initial clearing file parsing module, configured to parse the initial clearing file to obtain error file data in a case where the initial clearing file meets a batch processing dependent condition; the batch processing dependent condition comprises that a type of the initial clearing file meets a preset error file type requirement; and an error file data summarizing module, configured to summarize the error file data based on a preset data type to obtain the error file.

[0079] Based on the foregoing embodiment, the initial clearing file parsing module comprises an initial clearing file collating unit configured to collate the initial clearing file based on batch information to obtain error file data; the batch information comprises at least one of a clearing channel, a clearing date, and a batch number.

[0080] Based on the foregoing embodiment, the preset data type comprises at least one of an error total amount, a total amount of receivables, a total amount of payables, a total number of receivables, a total number of payables, a total number of errors, and snapshot information.

[0081] In some embodiments, the error file processing module comprises: a business component to-be-cleared account deduction unit configured to deduct account resources corresponding to the error file to a business component to-be-cleared account based on the declaration document; and a first personal account deduction unit configured to deduct account resources in the business component to-be-cleared account to at least one corresponding personal account based on an account relationship corresponding to the error file.

[0082] Based on the foregoing embodiment, the error file processing module further comprises: a branch to-be-cleared account deduction unit configured to, in a case where deduction to the personal account fails, deduct account resources in the business component to-be-cleared account to a branch to-be-cleared account, so that branch operating personnel supplement error file information for the error file; and a second personal account deduction unit configured to, based on the supplemented error file information, deduct account resources in the branch to-be-cleared account to at least one corresponding personal account.

[0083] Based on the foregoing embodiment, the error file processing module further comprises: an error file forwarding unit configured to, in a case where supplement failure information is obtained, forward the error file to an agency terminal so that operating personnel process the error file.

[0084] The embodiment of the present specification provides a computer readable storage medium having computer programs / instructions stored thereon. The computer readable storage medium can be read by a processor based on the internal bus of the device, and then the program instructions in the computer readable storage medium are implemented by the processor.

[0085] In the present embodiment, the computer readable storage medium can be implemented in any appropriate manner. The computer readable storage medium includes but is not limited to random access memory (RAM), read-only memory (ROM), cache, hard disk drive (HDD), memory card, etc. The computer storage medium stores computer program instructions. When the computer program instructions are executed, the embodiment of the present specification is implemented. Figure 1Program instructions or modules of the corresponding embodiments.

[0086] In the present embodiment, the processor can be implemented in any suitable manner. For example, the processor can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (e.g. software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, etc.

[0087] In particular, the processor, when disposed on a computer device, can implement the processes described in the present specification Figure 1 The program instructions of the corresponding embodiments are used to implement the following steps: sending an error file to an audit terminal, so that the audit terminal audits the error file; in the case where audit pass information is received, matching a service attribution component corresponding to the error file; determining a target account based on the service attribution component corresponding to the error file; in the case where the error file meets a reconciliation condition, obtaining a declaration document corresponding to the error file; and processing the error file based on the target account and the declaration document.

[0088] The embodiments of the present specification also provide a computer program product comprising computer programs / instructions. The computer program product can be a program written in a corresponding computer program language and stored in a corresponding storage device in a program manner, and can be transmitted through a computer network. The computer program product can be executed by a processor. In the embodiments of the present specification, the computer program product, when executed, implements the processes described in the present specification Figure 1 Program instructions or modules of the error file processing method of the corresponding embodiments.

[0089] It should be noted that the error file processing method, device, storage medium and program product described above can be applied to the field of big data technology, and can also be applied to other technical fields other than the field of big data technology, and no limitation is made to this.

[0090] In addition, it should be noted that the reading, processing, storage and use of data in the error file processing method, device, storage medium and program product described above all comply with the relevant provisions of national laws and regulations.

[0091] Although the process flow described above includes a plurality of operations appearing in a specific order, it should be clearly understood that the processes can include more or fewer operations, which can be executed sequentially or in parallel (for example, using a parallel processor or a multi-threaded environment).

[0092] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0093] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0094] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. ​ one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0095] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0096] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory. The memory is an example of computer-readable media.

[0097] Computer-readable media includes permanent and non-permanent, moveable and non- moveable media that can be implemented by any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile discs (DVDs) or other optical storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. According to the definitions herein, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

[0098] Those skilled in the art will appreciate that embodiments of the present specification can be provided as methods, systems or computer program products. Accordingly, embodiments of the present specification can be embodied in the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present specification can be embodied in the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROMs, optical memory, etc.) having computer usable program code embodied thereon.

[0099] Embodiments of the present specification can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0100] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the system embodiments are described simply because they are substantially similar to the method embodiments. The relevant parts can be referred to the description of the method embodiments. In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the embodiments of the present specification. The illustrative description of the above terms in the present specification does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples. Furthermore, the person skilled in the art can combine and integrate the different embodiments or examples described in the present specification and the features of the different embodiments or examples without contradiction.

[0101] The above only describes the embodiments of the present application and is not intended to limit the present application. The present application can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of claims of the present application.

Claims

1. A method for processing error files, characterized in that, include: Send the error file to the auditing terminal so that the auditing terminal can audit the error file; Upon receiving the approval information, the corresponding business scenario type is determined based on the business data in the error file, and then the business component to which the business scenario type belongs is determined. The target account is determined by combining the institution number, transaction currency information, and the business attribution component corresponding to the error file obtained from the error file; the business attribution component includes at least one of the payment settlement component, credit card component, acquiring component, and electronic banking component; the target account corresponds to an account in the target internal ledger; If the error file meets the adjustment conditions, the corresponding document is matched from the data table corresponding to the error file based on the adjustment type, settlement date, adjustment amount, card number, and system tracking number, and used as the corresponding declaration document for the error file; the adjustment conditions are used to determine whether the error file can be automatically processed based on the current error file processing logic; The error files are processed based on the target account and the declaration documents. The processing of the error file includes: based on the declaration form, transferring the account resources corresponding to the error file to the target account; the target account includes the business component pending settlement account; based on the account relationship corresponding to the error file, transferring the account resources in the target account to at least one corresponding personal account, so as to realize the conversion of account resources from internal accounts to external accounts.

2. The method as described in claim 1, characterized in that, The audit terminal includes a processing terminal and a review terminal; the error file includes an adjustment file and a detailed file; the processing terminal is used to audit the batch information of the adjustment file; the review terminal is used to audit the batch information of the detailed file; the batch information includes at least one of the following: clearing channel, clearing date, and batch number.

3. The method as described in claim 2, characterized in that, After sending the error file to the auditing terminal, the process also includes: Upon receiving audit anomaly information from the handling terminal, obtain the initial settlement file corresponding to the error file; A secondary error file is generated based on the initial liquidation file; The secondary error file is sent to the auditing terminal so that the auditing terminal can audit the secondary error file; Upon receiving approval information, match the business component to which the secondary error file belongs; The target account is determined based on the business-related component corresponding to the secondary error file; If the secondary error document meets the adjustment conditions, obtain the corresponding declaration form for the secondary error document; The secondary error files are processed based on the target account and the declaration documents.

4. The method as described in claim 2, characterized in that, After sending the error file to the auditing terminal, the process also includes: Upon receiving feedback of audit anomaly information from the review terminal, the processing flow for the erroneous file is terminated.

5. The method as described in claim 1, characterized in that, The business data includes at least one of the following: institution number, batch number, transaction type, error type, card number, merchant number, and terminal number.

6. The method as described in claim 5, characterized in that, After determining the corresponding business scenario type based on the business data in the error file, the process further includes: If the business scenario type cannot be determined, the error file is added to the waiting queue so that the operator can retrieve the error file from the waiting queue based on the handling terminal and determine the business scenario type and / or business belonging component of the error file.

7. The method as described in claim 1, characterized in that, Before sending the error file to the auditing terminal, the process also includes: If the initial liquidation file meets the batch processing dependency conditions, the initial liquidation file is parsed to obtain error file data; the batch processing dependency conditions include that the type of the initial liquidation file meets the preset error file type requirements. The error file is obtained by summarizing the error file data based on a preset data type.

8. The method as described in claim 7, characterized in that, The process of parsing the initial liquidation file to obtain error file data includes: Error file data is obtained by organizing the initial liquidation documents based on batch information; the batch information includes at least one of liquidation channel, liquidation date, and batch number.

9. The method as described in claim 7, characterized in that, The preset data types include at least one of the following: total error amount, total receivable amount, total payable amount, total number of receivables, total number of payables, total number of error entries, and snapshot information.

10. The method as described in claim 1, characterized in that, After transferring the account resources from the target account to at least one corresponding personal account, the process further includes: In the event that the transfer to the personal account fails, the account resources in the target account will be transferred to the branch's pending settlement account so that the branch operators can supplement the error file information accordingly. Based on the supplementary error document information, the account resources in the branch's pending settlement account will be deducted to at least one corresponding personal account.

11. The method as described in claim 10, characterized in that, After transferring the account resources from the target account to the branch's pending settlement account, the process also includes: Upon receiving supplementary failure information, the error file is forwarded to the handling terminal so that the operator can process the error file.

12. An error document processing device, characterized in that, include: The error file sending module is used to send error files to the auditing terminal so that the auditing terminal can audit the error files; The business attribution component matching module is used to determine the corresponding business scenario type based on the business data in the error file when the approval information is received, and then determine the business attribution component corresponding to the business scenario type. The target account determination module is used to determine the target account by combining the institution number, transaction currency information obtained from the error file, and the business attribution component corresponding to the error file; the business attribution component includes at least one of the payment settlement component, credit card component, acquiring component, and electronic banking component; the target account corresponds to the account of the target internal account; The application document acquisition module is used to match the corresponding documents from the data table corresponding to the error document, based on the adjustment type, settlement date, adjustment amount, card number, and system tracking number, when the error document meets the adjustment conditions, and use them as the application documents corresponding to the error document; the adjustment conditions are used to determine whether the error document can be automatically processed based on the current error document processing logic; The error file processing module is used to process error files based on the target account and the declaration form. The error file processing includes: transferring the account resources corresponding to the error file to the target account based on the declaration form; the target account includes a business component pending settlement account; and transferring the account resources in the target account to at least one corresponding personal account based on the account relationship corresponding to the error file, so as to realize the conversion of account resources from internal accounts to external accounts.

13. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by a processor, they implement the steps of the method as described in any one of claims 1-11.

14. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, they implement the steps of the method as described in any one of claims 1-11.

Images