Account write-off management method, system, device, equipment and medium

Abstract

The present disclosure provides a write-off management method, which can be applied to the financial field. The method includes: obtaining at least one write-off file, each of which includes a record of a clearing transaction and N first transactions that constitute a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; matching the identification information of the N first transactions in each of the write-off files with the identification information of all second transactions currently waiting for write-off; wherein the identification information used to identify the same transaction is the same and unique; and writing off the second transaction that has been successfully matched. The present disclosure also provides a write-off management system, device, equipment, storage medium and program product.

Description

Technical Field

[0001] The present disclosure relates to the field of information processing technology and can be used in the financial field. More specifically, it relates to an account write-off management method, system, device, equipment, medium and program product. Background Art

[0002] In the daily operations of enterprises and other organizations, there are often situations where the flow of funds such as receivables or payables is not synchronized with actual transactions. If receivables or payables are not settled in a timely manner, or if the status of various receivables or payables cannot be timely grasped, it will be inconvenient for account verification and risk management.

[0003] For example, in the agency financial payment business, there will be a large number of accounts receivable or accounts payable. Specifically, the agency financial payment business can include four links: advance payment, advance settlement, refund and return settlement. Among them, the advance payment link refers to the agency financial payment business (for example, a bank) receiving the payment instruction from the financial unit, which can first advance the internal account's own funds to the zero balance account and pay the actual payee. The advance settlement link refers to the bank recovering the advance payment through fund settlement with the clearing party, where the clearing party is generally a designated unit. Refund refers to the bank's failure to pay the actual payee or the payee's active refund, resulting in the return of the funds to the zero balance account. However, before this, the funds have been cleared by advance settlement. At this time, the funds need to be temporarily returned to the bank's internal advance account and wait for return settlement. Return settlement refers to the process of returning the funds temporarily returned to the bank in the refund link to the clearing party. It can be seen that advance payment constitutes the bank's accounts receivable to the clearing party, and refund constitutes the bank's accounts payable to the clearing party. Since transactions in agency financial payment business are often very frequent and the transaction volume is relatively large, the timely settlement of advance funds or refund funds is very critical to the orderly and efficient operation of agency financial business. Summary of the invention

[0004] In view of the above problems, the embodiments of the present disclosure provide a write-off management method, system, device, equipment, medium and program product for improving the efficiency of account reconciliation and risk management.

[0005] In a first aspect of the embodiments of the present disclosure, a method for account cancellation management is provided. The method comprises: obtaining at least one account cancellation file, each of which comprises a record of a clearing transaction and N first transactions constituting a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; matching the identification information of the N first transactions in each of the account cancellation files with the identification information of all second transactions currently waiting for account cancellation; wherein the identification information used to identify the same transaction is the same and unique; and performing account cancellation processing on the second transactions that have been successfully matched.

[0006] According to an embodiment of the present disclosure, the method further includes calculating the aging of the second transaction. For the second transaction that is successfully matched, the aging of the aging = the cancellation date - the aging start date, and for the second transaction that is not successfully matched, the aging of the aging = the current date - the aging start date.

[0007] According to an embodiment of the present disclosure, the method further includes issuing an early warning prompt for the second transaction whose pending account age exceeds a predetermined allowed pending account time.

[0008] According to an embodiment of the present disclosure, the obtaining of at least one write-off file includes: generating the write-off file based on a preset template file for generating the write-off file, and business background information of the clearing transaction and N first transactions constituting the package grouping relationship. The template file is provided with a plurality of first fields for recording the business background information of the clearing transaction in the package grouping relationship, and a plurality of second fields for recording the business background information of each first transaction in the package grouping relationship.

[0009] According to an embodiment of the present disclosure, before matching the identification information of the N first transactions in each of the write-off files with the identification information of all second transactions currently waiting for write-off, the method further includes: verifying the write-off file according to a preset rule.

[0010] According to an embodiment of the present disclosure, verifying the write-off file according to preset rules includes at least one of the following: verifying whether the data format in the write-off file meets predetermined requirements; verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct; or verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file meets the requirements of the information closed loop.

[0011] According to an embodiment of the present disclosure, the method is applied to the agency financial payment business, wherein a payment advance settlement and the corresponding N payment advances constitute the package relationship, or a return settlement and the corresponding N refunds constitute the package relationship.

[0012] According to a second aspect of the embodiments of the present disclosure, there is provided a method for account cancellation management, which is applied to a main system of an account cancellation management system, wherein the account cancellation management system is composed of the main system and M branch systems respectively communicating and connecting, and M is an integer greater than or equal to 1. The method comprises: obtaining at least one account cancellation file uploaded by the M branch systems, wherein each of the account cancellation files comprises a record of a clearing transaction and N first transactions constituting a package relationship; wherein in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; matching the identification information of the N first transactions in each of the account cancellation files with the identification information of all second transactions waiting for account cancellation in the main system; wherein the identification information used to identify the same transaction in the account cancellation management system is the same and unique; and performing account cancellation processing on the second transactions that have been successfully matched.

[0013] According to an embodiment of the present disclosure, the method further includes: calculating the pending account age of the second transaction; wherein, for the second transaction that is successfully matched, the pending account age = the account cancellation date - the initial date of the pending account; and for the second transaction that is not successfully matched, the pending account age = the system date of the overall system - the initial date of the pending account.

[0014] According to an embodiment of the present disclosure, the method further includes: issuing an early warning prompt for the second transaction whose pending account age exceeds a predetermined allowed pending account time.

[0015] According to an embodiment of the present disclosure, the obtaining of at least one write-off file uploaded by the M branch systems includes: obtaining at least one write-off file uploaded by the M branch systems on the previous working day.

[0016] According to an embodiment of the present disclosure, the method is applied to an agency financial payment business, wherein a payment advance settlement and its corresponding N payment advances constitute the package relationship, or a return settlement and its corresponding N refunds constitute the package relationship.

[0017] According to a third aspect of the embodiments of the present disclosure, there is provided a method for account cancellation management, which is applied to a branch system of an account cancellation management system, wherein the account cancellation management system is composed of a main system and M branch systems that are respectively connected in communication, and M is an integer greater than or equal to 1. The method comprises: generating at least one account cancellation file, wherein the account cancellation file comprises a record of a clearing transaction and N first transactions that constitute a package relationship; wherein in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; and uploading at least one of the account cancellation files to the main system, so that the main system performs account cancellation processing on the second transactions that have been successfully matched based on the matching of the identification information of the N first transactions in each of the account cancellation files with the identification information of all the second transactions waiting for account cancellation in the main system, wherein the identification information used to identify the same transaction in the account cancellation management system is the same and unique.

[0018] According to an embodiment of the present disclosure, generating at least one write-off file includes generating the write-off file based on a preset template file for generating the write-off file and business background information of the clearing transaction and N first transactions constituting the package group relationship. The template file is provided with a plurality of first fields for recording the business background information of the clearing transaction in the package group relationship, and a plurality of second fields for recording the business background information of each first transaction in the package group relationship.

[0019] According to an embodiment of the present disclosure, the method is applied to the agency financial payment business, wherein a payment advance settlement and the corresponding N payment advances constitute the package relationship, or a return settlement and the corresponding N refunds constitute the package relationship.

[0020] According to an embodiment of the present disclosure, generating the write-off file includes: obtaining an advance payment settlement voucher or a return payment settlement voucher from a financial system using a process automation RPA system; and filling in the multiple first fields in the template file based on the advance payment settlement voucher or the return payment settlement voucher.

[0021] According to an embodiment of the present disclosure, before uploading at least one of the write-off files to the overall system, the method further includes verifying each of the write-off files according to preset rules.

[0022] According to an embodiment of the present disclosure, verifying each of the write-off files according to preset rules includes at least one of the following: verifying whether the data format in the write-off file meets predetermined requirements; verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct; or verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file meets the requirements of the information closed loop.

[0023] According to a fourth aspect of the embodiments of the present disclosure, there is provided an account closing management system. The system comprises a main system and M branch systems, wherein the main system and the M branch systems are respectively connected in communication, and M is an integer greater than or equal to 1. The main system is used to execute the method provided in the second aspect, and the branch system is used to execute the method provided in the third aspect.

[0024] In a fifth aspect of the embodiments of the present disclosure, a write-off management device is provided. The device includes an acquisition module, a matching module, and a write-off module. The acquisition module is used to acquire at least one write-off file, each of which includes a record of a clearing transaction and N first transactions that constitute a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1. The matching module is used to match the identification information of the N first transactions in each of the write-off files with the identification information of all second transactions currently waiting for write-off; wherein, the identification information used to identify the same transaction is the same and unique. The write-off module is used to write off the second transaction that has been successfully matched.

[0025] According to an embodiment of the present disclosure, the device further includes an aging monitoring module. The aging monitoring module is used to calculate the pending account aging of the second transaction, wherein, for the second transaction that is successfully matched, the pending account aging = the account cancellation date - the pending account start date, and for the second transaction that is not successfully matched, the pending account aging = the current date - the pending account start date.

[0026] According to an embodiment of the present disclosure, the aging monitoring module is further used to issue an early warning prompt for the second transaction whose aging exceeds a predetermined allowable aging period.

[0027] According to an embodiment of the present disclosure, the device further includes a verification module. The verification module is used to verify the write-off file according to a preset rule before matching the identification information of the N first transactions in each write-off file with the identification information of all second transactions currently waiting for write-off.

[0028] According to an embodiment of the present disclosure, the verification module is used to perform at least one of the following: verifying whether the data format in the write-off file meets predetermined requirements; verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct; or verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file meets the requirements of the information closed loop.

[0029] In a sixth aspect of the embodiments of the present disclosure, an electronic device is provided. The electronic device includes one or more processors and one or more memories. The processor is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the write-off management method provided in the above aspects.

[0030] The seventh aspect of the embodiments of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the write-off management methods provided in the above-mentioned aspects.

[0031] The fifth aspect of the embodiments of the present disclosure also provides a computer program product, including a computer program, which, when executed by a processor, implements the write-off management method provided in the above-mentioned various aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The above contents and other purposes, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0033] Figure 1 A schematic diagram showing an application scenario of a write-off management method, apparatus, device, medium, and program product according to an embodiment of the present disclosure;

[0034] Figure 2 A flowchart of a method for managing account cancellations according to an embodiment of the present disclosure is schematically shown;

[0035] Figure 3 A flowchart of a method for managing account cancellation according to another embodiment of the present disclosure is schematically shown;

[0036] Figure 4 A flowchart of a method for managing account cancellation according to another embodiment of the present disclosure is schematically shown;

[0037] Figure 5 The following schematically shows an application scenario diagram of an agent financial payment service applicable according to an embodiment of the present disclosure;

[0038] Figure 6 The information interaction scenario between the banking system and the financial system in the agent financial payment business according to the embodiment of the present disclosure is schematically shown;

[0039] Figure 7 The application scenario diagram of the account cancellation management system according to the embodiment of the present disclosure is schematically shown;

[0040] Figure 8 A flowchart of a write-off management method executed in a write-off management system according to an embodiment of the present disclosure is schematically shown;

[0041] Fig. 9 A block diagram schematically shows a device for managing account closing according to an embodiment of the present disclosure; and

[0042] Fig.10 The block diagram schematically shows an electronic device suitable for implementing the write-off management method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0043] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0044] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0045] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0046] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0047] It should be understood herein that any number of elements in the specification and drawings is for illustration rather than limitation, and any naming (eg, first, second) is only for distinction but not for limitation.

[0048] The disclosed embodiments provide a write-off management method, system, device, equipment, medium and program. The method includes first obtaining at least one write-off file, each write-off file including a record of a clearing transaction and N first transactions constituting a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions, wherein N is an integer greater than or equal to 1. Then, the identification information of the N first transactions in each write-off file is matched with the identification information of all second transactions currently waiting for write-off; wherein, the identification information used to identify the same transaction is the same and unique. Finally, the second transaction that has been successfully matched is written off. In this way, the efficiency of account reconciliation is improved.

[0049] According to an embodiment of the present disclosure, a package relationship refers to a total-to-score correspondence between a clearing transaction and an account receivable / payable transaction. For example, in an agency financial payment business, an advance payment clearing can be used to clear one or more advance payment payments, and a return clearing can be used to clear one or more refunds. Thus, there is a total-to-score correspondence between advance payment clearing and advance payment, and return clearing and refund. Thus, a package relationship can be formed between advance payment clearing and the corresponding advance payment, and return clearing and the corresponding refund.

[0050] According to the embodiments of the present disclosure, the write-off file may be a file that records the package relationship, which is a concrete embodiment of the package relationship. For example, in the agency financial payment business, a write-off file may be used to record the information of one advance payment settlement and N corresponding advance payment, etc. Or a write-off file may be used to record the information of one return settlement and N corresponding refunds.

[0051] It should be noted that the write-off management method, system, device, equipment, medium and program determined in the embodiments of the present disclosure can be used in the financial field (for example, agency financial payment business, or other businesses with receivables and payables), and can also be used in any field other than the financial field (for example, corporate financial management, etc.). The present disclosure does not limit the application field.

[0052] Figure 1 The following schematically illustrates an application scenario diagram of a write-off management method, apparatus, device, medium, and program product according to an embodiment of the present disclosure. It should be noted that: Figure 1 The illustrated example is merely an example of a system architecture to which the embodiments of the present disclosure may be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure may not be used in other devices, systems, environments or scenarios.

[0053] like Figure 1As shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0054] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as bank management systems, government applications, monitoring applications, web browser applications, search applications, office applications, instant messaging tools, email clients, social platform software and other applications (only as examples).

[0055] The server 105 may be a server that provides various services, such as a background management server that provides support for websites browsed or applications used by users using the terminal devices 101 , 102 , 103 (only as an example).

[0056] For example, the user can operate the terminal devices 101, 102, 103 and interact with the server 105 to realize transactions such as credit purchase, payment, loan, repayment, and installment payment, thereby generating transactions receivable or payable (for example, prepayment of deposits in business activities, or payment after delivery, or payment before delivery, etc.). At the same time, according to the embodiment of the present disclosure, when performing background account processing, the server 105 can execute the write-off management method of the embodiment of the present disclosure, and perform centralized write-off management of the generated receivables / payables, etc., so as to improve the efficiency of financial verification and effectively control risks.

[0057] It should be noted that the write-off management method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the write-off management apparatus, device, medium and program provided in the embodiment of the present disclosure can generally be set in the server 105. The write-off management method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the write-off management apparatus, device, medium and program provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0058] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0059] The following will be based on Figure 1 The scene described by Figure 2 to Figure 4 The account cancellation management method according to the embodiment of the present disclosure is described in detail.

[0060] Figure 2 The flowchart of the write-off management method according to an embodiment of the present disclosure is schematically shown.

[0061] like Figure 2 As shown, the write-off management method may include operations S210 to S230.

[0062] In operation S210, at least one write-off file is obtained, each write-off file including a record of a clearing transaction and N first transactions constituting a package relationship. In the package relationship, the clearing transaction is used to clear the N first transactions, where N is an integer greater than or equal to 1.

[0063] Table 1 exemplarily lists a write-off file, in which the clearing transactions and N first transactions with a package relationship can be recorded. It should be noted that the contents of the record fields of the clearing transactions and first transactions in Table 1 are only illustrative. In actual applications, the contents of the fields are set or selected according to the business background information of the transaction (i.e., the time, location, participants, cause, voucher, result, etc. of the transaction).

[0064] Table 1

[0065] Clearing transactions Identification Information Amount Information Liquidation Time Clearing Certificate ... 1 ... ... ... ... ... First Transaction Identification Information Amount Information Trading Hours Trading instruction information ... 1 ... ... ... ... ... 2 ... ... ... ... ... ... ... ... ... ... ... N ... ... ... ... ...

[0066] In one embodiment, in operation S210, the prepared write-off file may be searched from a network or a database, or a write-off file sent by other users may be received.

[0067] In another embodiment, in operation S210, an accounting file may also be generated according to the accounting details. For example, a template file (e.g., Table 1) for generating an account write-off file may be pre-set, wherein a plurality of first fields (e.g., the fields in the first row of Table 1) for recording the business background information of the clearing transaction in the package group relationship, and a plurality of second fields (e.g., the fields in the third row of Table 1) for recording the business background information of each first transaction in the package group relationship may be set in the template file. Then, the business background information of each of the clearing transaction and the N first transactions constituting the package group relationship may be obtained, and then, based on the preset template file for generating the account write-off file, the corresponding data is extracted from the business background information of each transaction, and filled in the fields in the template file, thereby generating the account write-off file.

[0068] In operation S220, the identification information of the N first transactions in each write-off file is matched with the identification information of all second transactions currently waiting to be written off, wherein the identification information used to identify the same transaction is the same and unique.

[0069] In the present disclosure, the first transaction refers to the transaction object processed in the business settlement process. The second transaction is the transaction object processed in the account summary and verification stage. Among them, the account summary and verification are statistics of the results of business activities. Therefore, for an organization, the data set formed by the second transaction includes N first transactions.

[0070] In the financial system of an organization, for the same transaction, identification information is used as the identity authentication information of the transaction. For example, in a complex system, there may be a main system and branch systems. The branch system handles complex and specific business processes, and the main system is responsible for account aggregation. In this case, the same transaction can be uniquely identified in the main system and the branch system through identification information (for example, event number).

[0071] Operation S230: canceling the successfully matched second transaction.

[0072] When the match is successful, it means that the second transaction has been cleared in the business settlement process, so the second transaction can be written off. In this way, the automatic write-off of accounts can be realized, the efficiency of account verification can be improved, and the ability to control financial risks can be enhanced.

[0073] Figure 3 The flowchart of the write-off management method according to another embodiment of the present disclosure is schematically shown.

[0074] like Figure 3 As shown, the write-off management method according to this embodiment may further include operation S340 after operation S210 to operation S230. In some embodiments, operation S340 may further include operation S350.

[0075] In operation S340, the account aging of the second transaction is calculated.

[0076] For the successfully matched second transaction, the pending account age = the cancellation date - the pending account start date. The successfully matched second transaction was cancelled, so the pending account age does not change after being calculated based on the cancellation date.

[0077] For the second transaction that is not successfully matched, the pending account age = current date - initial date of the pending account. The pending account age is recalculated based on the current date each time the second transaction that is not successfully matched is used.

[0078] Then, in operation S350, an early warning can be issued for the second transaction whose pending account age exceeds the predetermined allowed pending account time. The allowed pending account time (e.g., 3 days) can be pre-parameterized and defined according to actual needs. The transaction details whose pending account time exceeds the allowed pending account time are monitored in a timely manner (e.g., by marking with different colors), so as to facilitate monitoring and timely processing of the account at the granularity of the transaction details.

[0079] Figure 4 The flowchart of the write-off management method according to another embodiment of the present disclosure is schematically shown.

[0080] like Figure 4 As shown, according to the write-off management method of this embodiment, in addition to operations S210 to S230, operation S420 may also be included. Operation S420 is performed before operation S220.

[0081] According to an embodiment of the present disclosure, after the write-off file is obtained, the write-off file is first verified according to a preset rule in operation S420. After the verification is passed, the file is matched according to the identification information in operation S220, and the write-off process is performed in operation S230.

[0082] The content of the preset rules can be set arbitrarily according to actual needs. For example, the data format requirements of each field in the write-off file are set through parameterized definition to verify the data standardization in the write-off file. For another example, by comparing the key field in the write-off file with the corresponding field or content at the source of the field, it is determined whether the value of the field is correct. For another example, the clearing transaction and the first transaction in the write-off file are checked from the aspects of the total amount or the number of transactions to see whether the information in the package relationship corresponds.

[0083] According to an embodiment of the present disclosure, verifying the write-off file according to preset rules includes at least one of the following: verifying whether the data format in the write-off file meets the predetermined requirements; verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct; or verifying whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file meets the requirements of the information closed loop. The information closed loop means that the information of the clearing transaction and the first transaction with the package relationship in terms of the total amount, the number of transactions, the time regulations of the transaction, the geographical location regulations of the transaction, etc. needs to meet the corresponding relationship (for example, equal, or contain, or other mapping relationships). For example, if a clearing transaction is a clearing of N first transactions, then the number of first transactions in the write-off file must be equal to N, and the clearing amount must be equal to the sum of the amounts of the N first transactions. For another example, if the clearing transaction is a clearing of the first transaction in a certain area, then the regional information of the first transaction in the package relationship must be within the regional range included in the clearing transaction.

[0084] According to the embodiments of the present disclosure, the write-off management method can be applied to the agency financial payment business. Among them, a payment settlement and the corresponding N payment settlements form a package relationship. A return settlement and the corresponding N refunds form a package relationship.

[0085] Figure 5 The following schematically shows an application scenario diagram of the agent financial payment service applicable according to the embodiment of the present disclosure. Figure 5 The specific process of accounting processing involved in the agency financial payment business is described in detail to help those skilled in the art to more clearly understand the above-mentioned package relationship in the agency financial payment business.

[0086] like Figure 5 As shown, in application scenario 500, the counterparties of the agency financial payment business involve finance, commercial banks, clearing parties and actual payees.

[0087] In application scenario 500, the entire life cycle of the agency financial payment business includes the capital flow in four stages: advance payment, advance settlement, refund, and return settlement. The accounting process of each stage is briefly described as follows.

[0088] In the advance payment link, after receiving a payment instruction from a financial unit to pay the actual payee, the commercial bank will review the payment instruction and, after the review is passed, use its own funds to advance the money to the financial zero balance account or the budget unit zero balance account (hereinafter referred to as the zero balance account) in strict accordance with the instruction, and then pay the actual payee's account from the zero balance account, thereby realizing the financial payment to the actual payee. Among them, in the accounting processing of the advance payment link, the accounting entries of the commercial bank are:

[0089] Debit: Commercial bank's internal account for advances

[0090] Credit: Financial zero balance account or budget unit zero balance account

[0091] Debit: Financial zero balance account or budget unit zero balance account

[0092] Credit: Actual beneficiary account

[0093] Among them, the commercial bank's internal account for advances is used to record the details of the commercial bank's advances in the advance payment link. The zero balance account is a bank settlement account opened by the financial department or budget unit with the approval of the financial department at the bank that acts as the agent for financial payment, and is used to handle the centralized treasury payment business. Due to the nature of the business, the financial unit generally does not store any amount in the account in advance. Therefore, according to the above accounting entries, it can be seen that under normal circumstances, the balance of funds in the zero balance account should be zero. According to the accounting entries of the advance payment link, it can be seen that the advance payment link actually involves two steps: advance transaction and payment transaction, that is, it involves two debit and two credit operations.

[0094] In the advance payment settlement phase, commercial banks can recover the advance payment through fund settlement with the clearing party. In the account processing of advance payment settlement phase, the accounting entries of commercial banks are:

[0095] Debit: Clearing Party Account

[0096] Credit: Commercial bank's internal account for advances

[0097] Among them, the clearing party account is an account opened by the clearing party for agency financial payment and clearing, including but not limited to the treasury deposit account opened by the finance department in the treasury department of the central bank (referred to as the "treasury single account"), the extra-budgetary financial account opened by the finance department in the agent bank (referred to as the "extra-budgetary financial account"), etc. After passing a series of quota approval procedures of the finance department and the bank, the funds in this account can be used to repay the financial funds advanced by the bank.

[0098] It can be seen that the advance payment settlement link is the settlement of the funds advanced by the bank in the advance payment link. The bank can settle multiple advance payments at one time through an advance payment settlement. For example, the bank can settle all the advance payment details formed on the day at a fixed time point on each working day, or the bank can settle all the advance payment details formed on the previous day on each working day. Therefore, a package relationship is formed between an advance payment settlement and the corresponding multiple advance payments.

[0099] In the refund process, the refunded funds of failed interbank payments to the actual beneficiary by the commercial bank, or the funds that are actively returned after consultation with the finance and treasury, etc., should be returned to the zero balance account first. However, if the funds have been cleared through advance payment, the funds will be refunded in the agency finance payment business, temporarily returned to the commercial bank and wait for the return to the treasury for clearing. Among them, in the accounting processing of the refund process, the accounting entries of the commercial bank are:

[0100] Debit: Financial zero balance account or budget unit zero balance account

[0101] Credit: Commercial bank's internal account for advances

[0102] In the return settlement phase, the commercial bank returns one or more refunds generated in the refund phase to the clearing party. Among them, in the accounting processing of the return settlement phase, the accounting entries of the commercial bank are:

[0103] Debit: Commercial bank's internal account for advances

[0104] Credit: Account of the clearing party.

[0105] It can be seen that the return settlement link is the settlement of the funds that the bank should return to the clearing party in the refund link. The bank can settle multiple refunds at one time through a return settlement. For example, the bank can settle all refund details that occurred on the same day at a fixed time point on each working day, or the bank can settle all refund details formed on the previous day on each working day. Therefore, a return settlement and the corresponding multiple refunds form a package relationship.

[0106] Therefore, in the agency financial payment business, a package relationship is formed between an advance settlement and the corresponding N advance payments, and a package relationship is formed between a return settlement and the corresponding N refunds.

[0107] Figure 6 The information interaction scenario between the banking system and the financial system in the agent financial payment business according to the embodiment of the present disclosure is schematically shown.

[0108] like Figure 6 As shown, according to an embodiment of the present disclosure, the information interaction scenario 600 can be divided into two operating modes: a non-electronic mode and an electronic mode.

[0109] In the non-electronic mode, the information interaction scene 600 may include the banking system 610 and the financial system 620, but does not include the electronic voucher library 630. In the non-electronic mode, the financial system 620 is not connected to the banking system 610. The electronic vouchers issued by the financial system 620 rely on a single line transmission such as an independent dedicated line deployed on the Internet or in the banking system 610, and the financial unit delivers paper vouchers to the bank. After the bank receives the paper vouchers, the staff logs on to the website of the financial system to check the electronic vouchers, and conducts business transactions based on the voucher information after the verification is correct.

[0110] In the electronic mode, the information interaction scenario 600 may include a banking system 610, a financial system 620, and an electronic voucher library 630. The banking system 610 and the financial system 620 may exchange electronic vouchers through the electronic voucher library 630. Thus, the banking system 610 may execute the business transaction indicated by the information of the electronic voucher after obtaining the electronic voucher and passing the verification.

[0111] At present, the financial system and banking system in some regions have realized the electronic mode, while the financial system and banking system in some regions are still using the non-electronic mode.

[0112] When the bank system 610 executes the write-off management method according to the embodiment of the present disclosure, the implementation logic of the bank system 610 in the electronic mode and the non-electronic mode is the same, with the difference that: in the electronic mode, the bank system 610 can rely on the electronic voucher library to generate an advance settlement voucher or a return settlement voucher by the bank system 610, and the package relationship between advance settlement and advance payment, return settlement and refund can be stored in the underlying logic of the bank system 610, which can support the bank system 610 to automatically process and obtain package relationships one by one according to a fixed process; in the non-electronic mode, the advance settlement voucher and the return settlement voucher are generated by the financial system 620, and it is necessary to obtain the information of the advance settlement voucher and the return settlement voucher from the financial system 620 manually or through the process automation RPA system, and then enter the package relationships formed between the advance settlement and advance payment, return settlement and refund into the bank system 610 through manual intervention.

[0113] Figure 7 The application scenario diagram of the account cancellation management system according to an embodiment of the present disclosure is schematically shown.

[0114] like Figure 7 As shown, the application scenario 700 includes an account write-off management system 710 and multiple financial systems 720. The multiple financial systems 720 may be financial systems of financial units deployed in different regions.

[0115] The account closing management system 710 according to the embodiment of the present disclosure may include a main system 711 and multiple branch systems 712. The account closing management system 710 may be part of a bank system. The branch systems 712 may be deployed in various branches of a bank to perform specific business processing. The main system 711 may be deployed in an account summary agency of a bank to summarize the results of business activities.

[0116] Each branch system 712 can be connected to a financial system 720. For example, each branch system 712 can be connected to the financial system of the region corresponding to the branch where it is located. The connection mode between each branch system 712 and the financial system 720 can be: Figure 6 The electronic mode or non-electronic mode between the banking system 610 and the financial system 620.

[0117] It should be noted that in Figure 7The connection between a branch system 712 and a financial system 720 is only exemplary. In real life, a branch system 712 can often be connected to multiple financial systems 720. For example, a branch can provide agency financial payment services to multiple financial units within its area.

[0118] The branch system 712 can generate a write-off file containing a package relationship based on the account information in the financial payment business it represents, and upload the write-off file to the main system 711, and then the main system 711 performs write-off management based on the matching of the write-off file and the second transaction waiting for write-off in the main system 711. In one embodiment, due to the frequent transactions in the financial payment business, the concept of "asynchronous write-off register" can be used to perform operations and processing between the branch system 712 and the main system 711 respectively: that is, the branch system 712 writes the write-off file on day T, and the main system 711 performs unified write-off processing on day T+1 based on the write-off file uploaded by the branch system on day T.

[0119] The following is based on Figure 6 Information interaction scenarios and Figure 7 Application scenarios, through Figure 8 An exemplary description is given of the process of account write-off management by a bank's account write-off management system in agency financial payment business.

[0120] Figure 8 The flowchart of the write-off management method executed in the write-off management system according to an embodiment of the present disclosure is schematically shown.

[0121] like Figure 8 As shown, the flowchart may include operations S11 to S15 and operations S21 to S25.

[0122] The operation process executed by the branch system 712 includes operations S11 to S15.

[0123] In operation S11, an advance payment settlement voucher or a return payment settlement voucher is obtained, wherein the information on the advance payment settlement voucher or the return payment settlement voucher records the business background information of the advance payment settlement or the return payment settlement.

[0124] In the non-electronic mode interaction scenario, the branch system 712 can use the process automation RPA system to obtain the information of the advance payment settlement voucher or the return payment settlement voucher from the financial system 720. In the electronic mode interaction scenario, the branch system 712 can obtain the advance payment settlement voucher or the return payment settlement voucher from the electronic voucher library.

[0125] In operation S12, business background information of advance payment or refund is obtained. The advance payment and refund business is processed by the branch system 712, and the corresponding business background information can be directly obtained from the database of the branch system 712.

[0126] In operation S13, a write-off file is generated. Specifically, the write-off file can be generated based on a preset template file for generating a write-off file, and the business background information of the clearing transaction and the N first transactions constituting the package group relationship. The template file is provided with a plurality of first fields for recording the business background information of the clearing transaction in the package group relationship, and a plurality of second fields for recording the business background information of each first transaction in the package group relationship.

[0127] In the electronic mode interaction scenario, the write-off file can be generated by the branch system 712 according to fixed logic. One write-off file corresponds to only one settlement voucher, including "jurisdiction area information", "budget year", "clearing voucher type", "clearing voucher number", "clearing voucher generation date", "clearing amount (cents)", "number of transactions", "other bank logo", "clearing (advance) internal account", "clearing (advance) internal account name", "payer account number", "payer full name", "fund nature code", "instruction channel source" and other non-empty field information. At the same time, one write-off file can support the filling of multiple advance payment (or refund) information, and can automatically generate registration details according to the screening conditions of the handling personnel, which can include "payment date", "payment event number", "jurisdiction area information", "budget year", "voucher type", "voucher number", "amount (cents)", "event number", "instruction channel source" and other fields.

[0128] In the non-electronic mode interaction scenario, the preparation process of the write-off file is as follows: obtain the advance payment voucher or refund voucher from the branch system 712, wherein the complete business information stored in the branch system 712 includes "payment date", "payment voucher code", "jurisdiction area information", "voucher type", etc., and when the payment is successful or the refund is made, the system automatically generates an "event number" (i.e., identification information) as an index keyword and is unique. The historical and current advance payment or refund vouchers support the generation of detailed lists and the export of write-off files based on screening conditions such as voucher status (unpaid, successful, failed, in process), voucher type (direct payment, authorized payment, direct payment refund, authorized payment refund), or nature of funds (within budget, outside budget, etc.). At the same time, the information of each field of the clearing transaction in the write-off file can be filled in manually according to the relevant information in the advance settlement voucher or return voucher generated by the financial system 720, and then the preparation of the write-off file can be completed.

[0129] In operation S14, each write-off file is checked according to a preset rule.

[0130] For example, you can check whether the write-off file format is correct and whether the required fields are filled in completely.

[0131] Verify whether the "liquidation amount" and "number of transactions" in the write-off file are consistent with the summary amount and number of advance payment or refund, and whether they form an information closed loop. Verify whether the "jurisdiction area information" and "year" of the advance settlement voucher or return voucher are consistent with the advance payment voucher or refund voucher, and whether each parameter is within the preset value range of the branch system 712.

[0132] Check the amount actually cleared and credited to the internal account of the advance payment in the check receipt query, and check whether the account name of the other bank is consistent with the "bank identification information", "payee's bank account opening bank" and "payee's full name" registered in the account cancellation file, and whether it is consistent with the preset information of the clearing bank parameters under the region and fund nature of the financial system 720 connected to the branch system 712.

[0133] According to the "jurisdictional area information" + "clearing voucher type" + "nature of funds" of the clearing voucher in the write-off file, check whether the "internal account for advance payment" and "account name" involved in the clearing are consistent with the preset parameter information such as the region, clearing voucher type, and nature of funds of the financial system 720 connected to the branch system 712.

[0134] Then in operation S15, after verification, the write-off file is uploaded to the general system 711. The write-off file can be added as an attachment to the clearing voucher record and uploaded to the general system 711 together. The analysis system can be automatically triggered or manually triggered in the form of a button to upload the write-off file. The advance clearing voucher or return voucher and the write-off file are associated with the advance internal account single entry details, and the package relationship is assigned to the advance clearing link, involving the credit funds transferred to the advance internal account through other banks through the modern payment system.

[0135] The operation flow executed by the overall system 711 includes operations S21 to S25.

[0136] In operation S21, the uploaded write-off file is obtained. In one embodiment, at least one write-off file uploaded by the M branch systems 712 on the previous working day is obtained. This is because the bank's business volume is relatively large, so the write-off processing of the branch offices can be asynchronously and uniformly performed.

[0137] In operation S22, the transactions in the write-off file are matched with all transactions currently waiting for write-off. Specifically, the identification information (e.g., a unique event number) of the N first transactions in each write-off file is matched with the event numbers of all second transactions waiting for write-off in the overall system 711.

[0138] In operation S23, the second transaction that has been successfully matched is processed for account cancellation. The matching is realized by hanging and canceling matching, which can be automatic or manual. The matching element is the debit and credit amount of the internal account of the advance payment. When the message status of the advance payment settlement voucher or the return settlement voucher is received by the clearing party and the account arrival query is completed (funds have been received, etc.), the general system 711 associates the actual account according to the debit and credit event number in the account cancellation file, and realizes the automatic matching closed loop of the debit and credit accounts of the same package relationship associated with the account cancellation file.

[0139] If the write-off file does not match the actual accounts due to missing fields in the write-off file preparation, errors in the preparation logic, or failure to upload the write-off file in time, the abnormal status of the details can be manually registered and supplemented by manual checking.

[0140] After that, in operation S24, the aging of the second transaction can be calculated. For the second transaction that is successfully matched, the aging of the aging = the cancellation date - the initial date of the aging. For the second transaction that is not successfully matched, the aging of the aging = the system date of the general system 711 - the initial date of the aging.

[0141] Then, in operation S25, a warning is issued for the second transaction whose pending account age exceeds the predetermined allowed pending account time.

[0142] In the embodiment of the present disclosure, the general system 711 can calculate the age of accounts and monitor pending accounts. The general system 711 can calculate the age of accounts by checking the details of the debit and credit accounts of the pending accounts on a daily basis. When the pending accounts are not closed-loop, the age of the pending accounts = system date - pending account date; when the accounts have been closed and checked, the age of the pending accounts is recalculated, and the age of the pending accounts = cancellation date - pending account date.

[0143] In accordance with actual management requirements, business personnel are supported to parameterize the definition of the number of days allowed for advance payment internal accounts. The general system 711 identifies overdue accounts and the number of overdue days based on the aging calculation results, making it easier to intuitively locate long-term advance payment vouchers or long-term unreturned refund vouchers.

[0144] Therefore, bank staff can query the details of uncleared advance payments and unrefundable funds under the internal advance account based on account reconciliation status (unreconciled, partially reconciled), transaction code, account age and other dimensions. They can also locate abnormal accounts based on account age, urge bank branches to clear internal account advances in a timely manner, and improve the bank's internal control level.

[0145] At the same time, it can also make the advance funds account more intuitive and transparent. The operation department can timely grasp the overdue data and feedback to the business supervisory department one by one. The business supervisor will communicate and report with the finance or liquidation party in a timely manner, request payment and liquidation in time, and maintain the orderly and smooth progress of financial payments, ensuring that the accounting risks can be seen clearly, understood thoroughly, and controlled.

[0146] According to the method of the embodiment of the present disclosure, it is possible to overcome the difficulties in account settlement in the agency financial payment business, such as large transaction volume, many-to-one relationship between pending and cancellation, and difficulty in tracing the age of the balance of the internal account of the advance payment. Relying on the concept of "asynchronous account settlement register", the branch system 712 sends a settlement file containing the package relationship on day T, and matches the transaction identification information (for example, event number) with the event number in the host accounting details uploaded on day T+1 in the main system 711. While giving the business background to the account details uploaded by the branch system 712, a logical relationship of cross-checking between pending and cancellation accounts is achieved, and the account age of the business advance payment, the account instructions and the account details are intuitively provided. The account verification results of the actual situation are realized, and the large-scale and frequent account cross-checking relationships of the internal accounts of the non-cancelled advance payment can be sorted out, registered and traced back afterwards.

[0147] The disclosed embodiments can involve the four business accounting links of advance payment, advance settlement, refund, and return settlement in agency financial payment, as well as the four-in-one account management mechanism of "account suspension, account cancellation, account reconciliation, and account age" of internal bank accounts through account cancellation control. It can construct a scenario-driven control and four-in-one accounting management mode for the internal account suspension of agency financial payment business, solve the manual account processing such as manual entry or modification of account number and amount in the accounting process in related technologies, as well as unclear account cancellation rules, inability to obtain account age information, and untimely account suspension processing. To a certain extent, it achieves the effect of having standards for accounting, basis for purchase and sale, control of the system, monitoring of account age, and early warning of overdue accounts.

[0148] Understandably, Figure 8 The process shown is exemplary and non-limiting. In some embodiments, the branch system 712 may first upload the debit file, and then verify it before matching the identification information in the main system 711. In other embodiments, a special system for processing the agent financial payment business may be developed, and the system may store various vouchers for the agent financial payment business, verify the debit file, and then upload it to the main system 711 after the verification is passed.

[0149] Fig. 9 The block diagram of the account closing management device 900 according to an embodiment of the present disclosure is schematically shown.

[0150] like Fig. 9 As shown, according to an embodiment of the present disclosure, the write-off management device 900 may include an acquisition module 910, a matching module 920, and a write-off module 930. According to other embodiments of the present disclosure, the device 900 may further include an aging monitoring module 940 and / or a verification module 950. The device 900 may be used to perform a reference Figure 2 to Figure 4 ,as well as Figure 8 Described method of charge-off management.

[0151] The acquisition module 910 can, for example, perform operation S210 to acquire at least one write-off file, each write-off file including records of a clearing transaction and N first transactions constituting a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1.

[0152] The matching module 920 may, for example, perform operation S220 to match the identification information of the N first transactions in each write-off file with the identification information of all second transactions currently waiting for write-off; wherein the identification information used to identify the same transaction is the same and unique.

[0153] The write-off module 930 may, for example, execute operation S230 to write-off the successfully matched second transaction.

[0154] The aging monitoring module 940 may, for example, perform operation S340 to calculate the aging of the second transaction, wherein, for a successfully matched second transaction, the aging of the second transaction = the cancellation date - the aging start date, and for an unsuccessfully matched second transaction, the aging of the second transaction = the current date - the aging start date. According to some embodiments of the present disclosure, the aging monitoring module 940 may, for example, further perform operation S350 to issue an early warning prompt for a second transaction whose aging exceeds a predetermined allowable aging time.

[0155] The verification module 950 may, for example, perform operation S420 to verify the write-off file according to a preset rule before matching the identification information of the N first transactions in each write-off file with the identification information of all second transactions currently waiting to be written off.

[0156] According to an embodiment of the present disclosure, the verification module 950 is specifically used to perform at least one of the following: verifying whether the data format in the write-off file meets the predetermined requirements; verifying whether the information of the clearing transaction and the N first transactions that constitute the package relationship in the write-off file is correct; or verifying whether the information of the clearing transaction and the N first transactions that constitute the package relationship in the write-off file meets the requirements of the information closed loop.

[0157] According to an embodiment of the present disclosure, any multiple modules of the acquisition module 910, the matching module 920, the write-off module 930, the aging monitoring module 940 or the verification module 950 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the acquisition module 910, the matching module 920, the write-off module 930, the aging monitoring module 940 or the verification module 950 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the acquisition module 910, the matching module 920, the write-off module 930, the aging monitoring module 940 or the verification module 950 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0158] Fig.10 The block diagram of an electronic device 1000 suitable for implementing the write-off management method according to an embodiment of the present disclosure is schematically shown.

[0159] like Fig.10 As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0160] In RAM 1003, various programs and data required for the operation of electronic device 1000 are stored. Processor 1001, ROM 1002 and RAM 1003 are connected to each other via bus 1004. Processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0161] According to an embodiment of the present disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device 1000 may further include one or more of the following components connected to the I / O interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0162] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiment; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the write-off management method according to the embodiment of the present disclosure is implemented.

[0163] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0164] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the write-off management method provided by the embodiment of the present disclosure.

[0165] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1001. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0166] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0167] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0168] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

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

[0170] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0171] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A method for account cancellation management, applied to agency financial payment business, wherein: The method comprises: Acquire at least one write-off file, each of which includes a record of a clearing transaction and N first transactions that constitute a package relationship; wherein, in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; Verifying the write-off file according to preset rules, including verifying whether the information of the clearing transaction and the N first transactions in the write-off file meets the requirements of an information closed loop; wherein, the information closed loop means that the clearing transaction and the N first transactions having a package relationship meet a corresponding relationship in terms of the total number of financial items, the number of transactions, the transaction time, and the transaction geographical location; Matching the identification information of the N first transactions in each verified cancellation file with the identification information of all second transactions currently waiting for cancellation; wherein the identification information used to identify the same transaction is the same and unique; and canceling the second transaction that is successfully matched; The package relationship includes a package relationship between advance payment settlement and advance payment transactions, and / or a package relationship between return settlement and refund transactions; Among them, in the package relationship between the advance clearing and advance payment transactions, the clearing transaction is an advance clearing transaction, and the first transaction is an advance payment transaction; wherein each advance clearing transaction involves the transfer of funds from the clearing party account to the advance internal account of the commercial bank; and each advance payment transaction involves firstly advancing funds from the advance internal account of the commercial bank to the fiscal zero balance account or the budget unit zero balance account, and then paying from the fiscal zero balance account or the budget unit zero balance account to the actual beneficiary account; Wherein, in the package relationship between the return clearing and refund transactions, the clearing transaction is a return clearing transaction, and the first transaction is a refund transaction; wherein each return clearing transaction involves the transfer of funds from the commercial bank's internal advance account to the clearing party's account; and each refund transaction involves the transfer of funds from the fiscal zero balance account or the budget unit zero balance account to the commercial bank's internal advance account; Wherein, the second transaction is a detail formed by an advance payment transaction or a refund transaction under the advance internal account of the commercial bank; Wherein, obtaining at least one write-off file includes: The business background information of the clearing transaction is obtained by obtaining an advance clearing voucher or a return clearing voucher, wherein the information on the advance clearing voucher or the return clearing voucher records the business background information of the advance clearing or the return clearing; Obtaining the business background information of each first transaction by reading the business background information of the advance payment transaction or refund transaction from the database of the branch system; Based on a preset template file for generating a write-off file, corresponding data is extracted from the business background information of the clearing transaction and the N first transactions constituting the package relationship, and filled into each field in the template file to generate the write-off file.

2. The method according to claim 1, wherein: The method further comprises: Calculating the pending account age of the second transaction; in, For the second transaction that is successfully matched, the pending account age = the account cancellation date - the pending account start date; and For the second transaction that is not successfully matched, the pending account age = current date - initial date of pending account.

3. The method according to claim 2, wherein: The method further comprises: For the second transaction whose pending account age exceeds the preset allowed pending account time, an early warning prompt is issued.

4. The method according to claim 1, wherein: The template file is provided with a plurality of first fields for recording business background information of the clearing transaction in the package grouping relationship, and a plurality of second fields for recording business background information of each first transaction in the package grouping relationship.

5. The method according to claim 1, wherein: The checking of the write-off file according to the preset rules also includes at least one of the following: Verify whether the data format in the write-off file meets the predetermined requirements; or Verify whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct.

6. A method for account cancellation management, applied to the overall system of the account cancellation management system, wherein: The account cancellation management system is composed of the main system and M branch systems respectively connected in communication, where M is an integer greater than or equal to 1, wherein the method is applied to the agency financial payment business, including: Acquire at least one write-off file uploaded by the M branch systems, wherein each write-off file includes a record of a clearing transaction and N first transactions constituting a package relationship; wherein in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; Verifying the write-off file according to preset rules, including verifying whether the information of the clearing transaction and the N first transactions in the write-off file meets the requirements of an information closed loop; wherein, the information closed loop means that the clearing transaction and the N first transactions having a package relationship meet a corresponding relationship in terms of the total number of financial items, the number of transactions, the transaction time, and the transaction geographical location; Matching the identification information of the N first transactions in each verified write-off file with the identification information of all second transactions waiting for write-off in the overall system; wherein the identification information used to identify the same transaction in the write-off management system is the same and unique; and canceling the second transaction that is successfully matched; The package relationship includes a package relationship between advance payment settlement and advance payment transactions, and / or a package relationship between return settlement and refund transactions; Among them, in the package relationship between the advance clearing and advance payment transactions, the clearing transaction is an advance clearing transaction, and the first transaction is an advance payment transaction; wherein each advance clearing transaction involves the transfer of funds from the clearing party account to the advance internal account of the commercial bank; and each advance payment transaction involves firstly advancing funds from the advance internal account of the commercial bank to the fiscal zero balance account or the budget unit zero balance account, and then paying from the fiscal zero balance account or the budget unit zero balance account to the actual beneficiary account; Wherein, in the package relationship between the return clearing and refund transactions, the clearing transaction is a return clearing transaction, and the first transaction is a refund transaction; wherein each return clearing transaction involves the transfer of funds from the commercial bank's internal advance account to the clearing party's account, and each refund transaction involves the transfer of funds from the fiscal zero balance account or the budget unit zero balance account to the commercial bank's internal advance account; Wherein, the second transaction is a detail formed by an advance payment transaction or a refund transaction under the advance internal account of the commercial bank; Wherein, obtaining at least one write-off file includes: The business background information of the clearing transaction is obtained by obtaining an advance clearing voucher or a return clearing voucher, wherein the information on the advance clearing voucher or the return clearing voucher records the business background information of the advance clearing or the return clearing; Obtaining the business background information of each first transaction by reading the business background information of the advance payment transaction or refund transaction from the database of the branch system; Based on a preset template file for generating a write-off file, corresponding data is extracted from the business background information of the clearing transaction and the N first transactions constituting the package relationship, and filled into each field in the template file to generate the write-off file.

7. The method according to claim 6, wherein: The method further comprises: Calculating the pending account age of the second transaction; in, For the second transaction that is successfully matched, the pending account age = the account cancellation date - the initial date of the pending account; and For the second transaction that is not successfully matched, the pending account age = the system date of the overall system - the initial date of the pending account.

8. The method according to claim 7, wherein: The method further comprises: For the second transaction whose pending account age exceeds the preset allowed pending account time, an early warning prompt is issued.

9. The method according to claim 6, wherein: The obtaining of at least one write-off file uploaded by the M branch systems comprises: Obtain at least one of the write-off files uploaded by the M branch systems on the previous working day.

10. A method for account cancellation management, applied to a branch system of an account cancellation management system, wherein: The account closing management system is composed of a main system and M branch systems respectively connected in communication, where M is an integer greater than or equal to 1; wherein the method is applied to the agency financial payment business, including: Generate at least one write-off file, wherein the write-off file includes a record of a clearing transaction and N first transactions constituting a package relationship; wherein in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; Verifying the write-off file according to preset rules, including verifying whether the information of the clearing transaction and the N first transactions in the write-off file meets the requirements of an information closed loop; wherein, the information closed loop means that the clearing transaction and the N first transactions having a package relationship meet a corresponding relationship in terms of the total number of financial items, the number of transactions, the transaction time, and the transaction geographical location; and Uploading at least one of the verification-passed write-off files to the general system, so that the general system performs write-off processing on the second transactions that successfully match based on the matching of the identification information of the N first transactions in each of the write-off files with the identification information of all the second transactions waiting for write-off in the general system, wherein the identification information used to identify the same transaction in the write-off management system is the same and unique; The package relationship includes a package relationship between advance payment settlement and advance payment transactions, and / or a package relationship between return settlement and refund transactions; Among them, in the package relationship between the advance clearing and advance payment transactions, the clearing transaction is an advance clearing transaction, and the first transaction is an advance payment transaction; wherein each advance clearing transaction involves the transfer of funds from the clearing party account to the advance internal account of the commercial bank; and each advance payment transaction involves firstly advancing funds from the advance internal account of the commercial bank to the fiscal zero balance account or the budget unit zero balance account, and then paying from the fiscal zero balance account or the budget unit zero balance account to the actual beneficiary account; Wherein, in the package relationship between the return clearing and refund transactions, the clearing transaction is a return clearing transaction, and the first transaction is a refund transaction; wherein each return clearing transaction involves the transfer of funds from the commercial bank's internal advance account to the clearing party's account, and each refund transaction involves the transfer of funds from the fiscal zero balance account or the budget unit zero balance account to the commercial bank's internal advance account; Wherein, the second transaction is a detail formed by an advance payment transaction or a refund transaction under the advance internal account of the commercial bank; The step of generating at least one write-off file includes: The business background information of the clearing transaction is obtained by obtaining an advance clearing voucher or a return clearing voucher, wherein the information on the advance clearing voucher or the return clearing voucher records the business background information of the advance clearing or the return clearing; Obtaining the business background information of each first transaction by reading the business background information of the advance payment transaction or the refund transaction from the database of the branch system; Based on a preset template file for generating a write-off file, corresponding data is extracted from the business background information of the clearing transaction and the N first transactions constituting the package relationship, and filled into each field in the template file to generate the write-off file.

11. The method according to claim 10, wherein: The template file is provided with a plurality of first fields for recording business background information of the clearing transaction in the package grouping relationship, and a plurality of second fields for recording business background information of each first transaction in the package grouping relationship.

12. The method according to claim 11, wherein: The generating of the write-off file comprises: Use the process automation RPA system to obtain advance payment settlement vouchers or return payment settlement vouchers from the financial system; and Based on the advance payment settlement voucher or the warehouse return settlement voucher, the multiple first fields in the template file are filled in.

13. The method according to claim 10, wherein: The checking of each of the write-off files according to the preset rules also includes at least one of the following: Verify whether the data format in the write-off file meets the predetermined requirements; or Verify whether the information of the clearing transaction and the N first transactions constituting the package relationship in the write-off file is correct.

14. A write-off management system, comprising: A main system and M branch systems, wherein the main system and the M branch systems are respectively connected in communication, and M is an integer greater than or equal to 1; in, The overall system is used to perform the method according to any one of claims 6 to 9; The branch system is used to execute the method according to any one of claims 10 to 13.

15. A write-off management device, comprising: an acquisition module, configured to acquire at least one write-off file, each of the write-off files including a record of a clearing transaction and N first transactions constituting a package relationship; wherein in the package relationship, the clearing transaction is used to clear the N first transactions; wherein N is an integer greater than or equal to 1; A verification module is used to verify the write-off file according to preset rules, including verifying whether the information of the clearing transaction and the N first transactions in the write-off file meets the requirements of the information closed loop; wherein, the information closed loop means that the clearing transaction and the N first transactions with a package relationship meet the corresponding relationship in terms of the total number of financial items, the number of transactions, the transaction time and the transaction geographical location; a matching module, configured to match the identification information of each of the N first transactions in the verification-passed account cancellation file with the identification information of all second transactions currently waiting for account cancellation; wherein the identification information used to identify the same transaction is the same and unique; and A write-off module, used for writing off the successfully matched second transaction; The package relationship includes a package relationship between advance payment settlement and advance payment transactions, and / or a package relationship between return settlement and refund transactions; Among them, in the package relationship between the advance clearing and advance payment transactions, the clearing transaction is an advance clearing transaction, and the first transaction is an advance payment transaction; wherein each advance clearing transaction involves the transfer of funds from the clearing party account to the advance internal account of the commercial bank; and each advance payment transaction involves firstly advancing funds from the advance internal account of the commercial bank to the fiscal zero balance account or the budget unit zero balance account, and then paying from the fiscal zero balance account or the budget unit zero balance account to the actual beneficiary account; Wherein, in the package relationship between the return clearing and refund transactions, the clearing transaction is a return clearing transaction, and the first transaction is a refund transaction; wherein each return clearing transaction involves the transfer of funds from the commercial bank's internal advance account to the clearing party's account; and each refund transaction involves the transfer of funds from the fiscal zero balance account or the budget unit zero balance account to the commercial bank's internal advance account; Wherein, the second transaction is a detail formed by an advance payment transaction or a refund transaction under the advance internal account of the commercial bank; Wherein, the acquisition module is specifically used for: The business background information of the clearing transaction is obtained by obtaining an advance clearing voucher or a return clearing voucher, wherein the information on the advance clearing voucher or the return clearing voucher records the business background information of the advance clearing or the return clearing; Obtaining the business background information of each first transaction by reading the business background information of the advance payment transaction or refund transaction from the database of the branch system; Based on a preset template file for generating a write-off file, corresponding data is extracted from the business background information of the clearing transaction and the N first transactions constituting the package relationship, and filled into each field in the template file to generate the write-off file.

16. An electronic device, comprising: one or more processors; one or more memories for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 13.

17. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 13.

Images