Bill account checking method and device and electronic equipment

Abstract

The invention discloses a bill account checking method and device and electronic equipment. The method comprises the following steps: acquiring bill ledger data reported by a sub-department, the bill ledger data comprising a department code of the sub-department, and the sub-department comprising any one department belonging to an institution; target bill data corresponding to the department code is determined from a bill business data set, and the bill data in the bill business data set comprises bill data of all departments; and comparing the bill machine account data with the target bill data to obtain difference bill data, the difference bill data being used for representing an account checking result obtained after account checking is performed on the bill machine account data of the sub-departments. According to the invention, the technical problems of low efficiency and large error due to the fact that the rationality of bill ledger data reported by subordinate member units needs to be manually judged by institution business departments in related technologies are solved.

Description

Technical Field

[0001] The present application relates to the field of bill management, and in particular, to a method, device and electronic equipment for bill reconciliation. Background Art

[0002] Bill reconciliation is an important part of bill business management, which requires timely and accurate bill inventory and reconciliation to achieve a closed loop of bill management. At present, the business departments of institutions manually count and reconcile the bills of subordinate member units. Due to the limitations of manual operations, the accuracy, completeness and timeliness of the reconciliation results are difficult to guarantee. The reconciliation process is inefficient and requires a lot of manpower and time.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method, device and electronic device for bill reconciliation, so as to at least solve the technical problems that the relevant technologies require the business departments of institutions to manually judge the rationality of the bill ledger data reported by subordinate member units, which is inefficient and has large errors.

[0005] According to one aspect of an embodiment of the present application, a method for bill reconciliation is provided, including: obtaining bill ledger data reported by a sub-department, wherein the bill ledger data includes a department code of the sub-department, and the sub-department includes any department affiliated to an organization; determining target bill data corresponding to the department code from a bill business data set, wherein the bill data in the bill business data set includes bill data of all departments; comparing the bill ledger data with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

[0006] In some embodiments of the present application, target bill data corresponding to the department code is determined from a bill business data set, including: obtaining a unified social credit code corresponding to the department code from a mapping table, wherein the mapping table is at least used to reflect the correspondence between the department code of each sub-department and the unified social credit code; and filtering the bill data corresponding to the unified social credit code from the bill business data set to obtain the target bill data.

[0007] In some embodiments of the present application, the bill business data in the bill business data set is obtained in the following manner: collecting bill data, wherein the bill data includes the bill number and the business type of the bill; determining the target record corresponding to the bill number in the basic information record table, wherein a record in the basic information record table is used to represent the life cycle information of a bill, and the life cycle information includes multiple business type information; generating business disposal information corresponding to the business type of the target record, wherein the business disposal information is used to record the business type change information of the bill; determining the bill status corresponding to the business disposal information, and obtaining the bill business data.

[0008] In some embodiments of the present application, the method also includes: obtaining the first bill that is on the bill expiration date and the bill status of the first bill in the basic information record table; when the bill status of the first bill is the target status, generating first business disposal information corresponding to the bill status of the first bill; and updating the bill status of the first bill to the status corresponding to the first business disposal information.

[0009] In some embodiments of the present application, the method also includes: obtaining a first sub-ticket interval of the ticket data, and obtaining a second sub-ticket interval of the target record, wherein the first sub-ticket interval is a sub-ticket interval obtained by splitting the ticket data according to the ticket number, and the second sub-ticket interval is a sub-ticket interval obtained by splitting the target record according to the ticket number; when the second sub-ticket starting number of the second sub-ticket interval is equal to the first sub-ticket starting number of the first sub-ticket interval, and the second sub-ticket ending number of the second sub-ticket interval is greater than the first sub-ticket ending number of the first sub-ticket interval, the second sub-ticket interval of the target record is updated to a third sub-ticket interval, wherein the third sub-ticket interval is the remaining interval in the second sub-ticket interval after excluding the first sub-ticket interval.

[0010] In some embodiments of the present application, the bill ledger data is compared with the target bill data to obtain difference bill data, including: obtaining a selection instruction for the target object, wherein the selection instruction includes a target business type for reconciliation and a target time period for reconciliation; respectively obtaining first business information and second business information corresponding to the target business type from the bill ledger data and the target bill data; and comparing the bill data of the first business information with the bill data of the second business information to obtain difference bill data.

[0011] In some embodiments of the present application, collecting invoice data includes: collecting invoice data of different business types of all departments in sequence according to a preset order; storing the invoice data collected within a first preset time period in a collection table, and storing the invoice data collected within a second preset time period in an archive table, wherein the end time of the first preset time period is before the start time of the second preset time period.

[0012] According to another aspect of the embodiment of the present application, a device for bill reconciliation is also provided, including: an acquisition module, used to acquire bill ledger data reported by a sub-department, wherein the bill ledger data includes the department code of the sub-department, and the sub-department includes any department affiliated to the organization; a determination module, used to determine the target bill data corresponding to the department code from the bill business data set, wherein the bill data in the bill business data set includes the bill data of all departments; a comparison module, used to compare the bill ledger data with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

[0013] According to another aspect of the embodiment of the present application, there is also provided an electronic device, including: a memory and a processor, the memory being used to store program instructions; the processor being connected to the memory and being used to execute the above-mentioned method of bill reconciliation.

[0014] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned bill reconciliation method by running the computer program.

[0015] According to another aspect of the embodiments of the present application, a computer program product is also provided, including computer instructions, which implement the above-mentioned bill reconciliation method when executed by a processor.

[0016] In the embodiment of the present application, an automated reconciliation method is adopted to obtain a reconciliation result by comparing the bill ledger data reported by the sub-department with the corresponding bill data in the institution's bill business data set, thereby achieving the purpose of accurate reconciliation, thereby realizing efficient and accurate processing of the reconciliation process, avoiding the cumbersome and erroneous technical effects of traditional manual reconciliation, and further solving the technical problems that the relevant technology requires the business department of the institution to manually judge the rationality of the bill ledger data reported by the subordinate member units, which is inefficient and has large errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal for a bill reconciliation method according to an embodiment of the present application;

[0019] Figure 2 is a flow chart of a method for bill reconciliation according to an embodiment of the present application;

[0020] Figure 3 It is a structural schematic diagram of a bill reconciliation device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0024] Unified Social Credit Code (USCC): A unique, lifelong legal identification code for legal persons and other organizations. It consists of 18 digits or letters and is used to uniquely identify and query the information of enterprises or organizations among commercial, financial and other institutions to ensure the uniformity and authority of corporate information.

[0025] Ticket Life Cycle (TLC): The entire process of a ticket from its issuance, circulation to final redemption or cancellation. This cycle includes the following key stages:

[0026] (1) Issuance: The stage when a bill is first created or issued by the drawee or acceptor. At this point, the bill has clear basic information such as amount, term, and issue date.

[0027] (2) Acceptance: The stage at which the drawee or acceptor promises to pay the face amount of the bill on the maturity date, thus making the bill valuable for circulation.

[0028] (3) Endorsement: The process by which a bill holder transfers the bill to another party. By signing the bill and identifying the endorsee, the original holder transfers the ownership of the bill and the right to receive payment to the endorsee.

[0029] (4) Discount: The process in which the holder transfers the bill to a bank or financial company in exchange for cash before the bill matures. The discounter needs to pay a certain discount interest.

[0030] (5) Holding: The stage when an entity legally holds the bill and enjoys the right to receive payment represented by the bill.

[0031] (6) Collection at maturity: The process by which the bill holder submits the bill to the acceptor or payee on the maturity date and requests payment of the face amount.

[0032] (7) Redemption: The stage at which the acceptor or payee pays the face amount of the bill at maturity or within a specified time after maturity, marking the end of the bill life cycle.

[0033] Ticket Splitting (TS) is an operation in the financial field that aims to split a large bill into multiple small bills to improve the liquidity and flexibility of the bill. The split bills have independent bill numbers and sub-ticket ranges, but remain consistent with the original bills in key business attributes, ensuring the business continuity and legal validity of the bills.

[0034] At present, there are many subordinate units in the same institution, and there are differences in the bill management mode and business processing methods of each member unit. For example, there are multiple modes such as centralized processing mode, surrender and allocation mode, and self-management. In each management mode, some member units have realized the online processing of commercial banks' electronic bill business through direct bank-enterprise connection, and some units still use online banking to operate electronic bill business and then enter the bill information into the treasury system. The institutional level mainly analyzes and controls by summarizing the bill business data of subordinate units, and has high requirements for the bill business standards and timeliness of processing of each member unit. It is difficult to fully and accurately grasp the basic bill information and business application of each unit. Since the relevant regulations have high requirements for the accuracy and completeness of bill information, if the institution cannot fully control and flexibly extract the bill business information of subordinate member units, it will not be able to meet the requirements of the regulations.

[0035] After the enterprise connected to the bill information service platform, it realized the collection of full bill information at the institutional level. However, there were several problems in the actual application process: (1) All collected information was identified by the unified social credit code, which was not convenient for statistics and analysis according to the organizational structure level of the institution; (2) The bill information service platform only provided five parts of information, including bill receivable balance details, endorsement transaction information, discount transaction information, bill payable balance details and commercial acceptance bill balance details. It lacked bill collection transaction information, bill due collection transaction information, bill issuance transaction information, bill redemption information, etc., and the information provided was not complete. Providing the balance and transaction data of a certain trading day on a daily basis cannot realize the statistical analysis of the occurrence of all business types during a certain business period; (3) According to the amount of data collected by medium-sized institutions, if only the data at historical points in time are counted through the collected information, it is necessary to frequently access data volumes exceeding tens of millions or even hundreds of millions, which has a significant impact on system performance and stability, and is likely to cause system freezes or crashes, inducing system security risks; (4) There is a lack of effective processing mechanisms or methods for the management and control of the bill business of member units, and the rationality of the bill ledger information reported by the member units is manually judged. The full bill collection service provided by the bill information service platform has not been reasonably and fully utilized.

[0036] In order to solve the above technical problems, the embodiments of the present application provide corresponding solutions, which are described in detail below.

[0037] The method embodiment of bill reconciliation provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing a method for bill reconciliation is shown. Figure 1 As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0038] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0039] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the method of bill reconciliation in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizing the above-mentioned method of bill reconciliation. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0040] The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0041] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0042] It should be noted that, in some optional embodiments, the above Figure 1 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0043] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of a method for reconciling bills. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0044] Figure 2 is a flow chart of a method for bill reconciliation according to an embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0045] Step S202, obtaining the bill ledger data reported by the sub-department, wherein the bill ledger data includes the department code of the sub-department, and the sub-department includes any department affiliated to the organization.

[0046] In the above step S202, the bill ledger data refers to all business information and transaction records related to bills recorded and maintained by each sub-department (or member unit) within the enterprise, including but not limited to detailed data of the entire process of bill issuance, endorsement, discounting, maturity collection, and payment. The bill ledger data may include basic information of the bill (such as bill number, face value, issue date, etc.), business processing information (such as endorsement date, endorser, endorsee, discount bank, discount rate, etc.) and the department code of the sub-department, which is used to identify the source and ownership of the bill.

[0047] In some embodiments of the present application, the sub-department collects data on internal bill business, for example, bill information obtained from banks, finance companies or other financial institutions, and records bill transaction details through an internal system or manually; in an optional embodiment, the collected bill information can be standardized in the format specified by the organization, and the standardized bill ledger data must include key fields, such as bill number, face value, transaction date, transaction type (such as endorsement, discount, etc.) and department code of the sub-department; the bill ledger data is uploaded to the bill management system of the organization (i.e., the corporate headquarters) through the internal network of the enterprise or a dedicated data transmission platform.

[0048] Step S204, determining target bill data corresponding to the department code from the bill business data set, wherein the bill data in the bill business data set includes bill data of all departments.

[0049] In the above step S204, the bill business data set refers to the set of bill business data collected by the institution from official channels (such as banks) that summarizes all departments. The bill data in the bill business data set includes basic information of the bill, such as bill number, face value, issue date, maturity date, etc., and business processing information in the life cycle of the bill, such as endorsement, discount, acceptance, maturity collection and payment. The bill business data set is directly provided by official channels and is a real, accurate and comprehensive bill business data source.

[0050] In order to improve the level of refinement of bill management and reduce the amount of data access, the bill business data in the bill business data set can be constructed by recording the life cycle information of the bill, specifically: collecting bill data, wherein the bill data includes the bill number and the business type of the bill; determining the target record corresponding to the bill number in the basic information record table, wherein a record in the basic information record table is used to represent the life cycle information of a bill, and the life cycle information includes multiple business type information; generating business disposal information corresponding to the business type of the target record, wherein the business disposal information is used to record the business type change information of the bill; determining the bill status corresponding to the business disposal information, and obtaining the bill business data.

[0051] Bill data refers to the original data from the official bill information collection platform, including basic information such as bill number and business type. The bill number refers to the unique serial number of the bill, which is used to identify each bill. The business type can include various links in the bill life cycle, such as opening, acceptance, endorsement, and discount.

[0052] By storing the collected bill data in different tables in chronological order, the efficiency of data storage and management can be improved. Specifically: the bill data of different business types of all departments are collected in sequence according to the preset order; the bill data collected within the first preset time period is stored in the collection table, and the bill data collected within the second preset time period is stored in the archive table, wherein the end time of the first preset time period is before the start time of the second preset time period.

[0053] The preset time period (the first preset time period and the second preset time period) refers to the time window set by the system to distinguish the data storage location, such as one year, one quarter, etc., to determine whether the bill data should be stored in the collection table or the archive table. The collection table refers to the database table used to store recent bill data. It can be used to save bill information in the current year or a certain time range for daily query, analysis and business operations. The archive table refers to the table used to save historical bill data for a long time. It can be used to save bill information for more than one year or a specified time range for future historical analysis, audit or compliance inspection.

[0054] In some embodiments of the present application, the system can automatically pull the latest bill data from the bill information service platform in the order of "bill holding information", "endorsement information", "discount information", "issue information" and "acceptance information" within a preset time period to ensure the timeliness and completeness of the data.

[0055] The basic information record table refers to a database table used to store the basic information of each bill from its issuance to its final disposal, including the basic elements of the bill (such as bill number, issue date, maturity date, face value, etc.) and business disposal information (such as endorsement date, discount date, etc.), and each record corresponds to the life cycle information of a bill. The life cycle information includes all business type information from the generation to the final disposal of the bill, such as issue, receipt, endorsement, discount, maturity collection, payment, etc., which is used to reflect the real-time status and historical trajectory of the bill. In some embodiments of the present application, when new bill data is received, the system can query the basic information record table to determine the record that is exactly the same as the bill number in the new bill data to determine the target record.

[0056] Business disposal information refers to the specific information that records the change of business type of the bill in the whole life cycle, that is, the trace information of each business link. Business disposal information corresponds to the business type and is used to analyze the liquidity and business activities of the bill. For example, when the financial system of the subordinate unit A of the organization finds that the bill with bill number "222222222" changes from "received" to "endorsed", the system will generate a business disposal information, which records the endorsement date, endorsement unit, endorsement receiving unit, etc. in detail.

[0057] The bill status refers to the real-time status of the bill under different business disposals, such as issued (i.e. the bill already exists), received (i.e. the recipient has confirmed acceptance), endorsed (i.e. the bill has been transferred by the holder to another unit or individual), discounted (i.e. the bill holder has exchanged a certain amount of cash from a bank or discount company before the bill expires), collected (i.e. the bill holder has requested the acceptor to pay the face value of the bill when or after the bill expires), and redeemed (i.e. the final state of the bill life cycle, indicating that the acceptor has paid the face value of the bill to the holder), etc., which is used to update the current business type of the bill in the basic information record table. For example, after receiving the information that "Bill number 123456789 was endorsed by unit X to unit Y on March 1, 2023", the system updates the bill status of the bill to "endorsed", and further updates the business disposal information of the bill in the bill business data set to reflect the latest circulation of the bill.

[0058] In order to ensure the real-time update and accuracy of the bill status, the key information of the current business processing link of the target record in the basic information record table can be automatically updated or supplemented through the following steps: obtain the first bill on the bill expiration date and the bill status of the first bill in the basic information record table; when the bill status of the first bill is the target status, generate the first business disposal information corresponding to the bill status of the first bill; update the bill status of the first bill to the status corresponding to the first business disposal information.

[0059] The bill maturity date refers to the date on which the face amount of the bill should be paid according to its issue date and term. The first bill refers to the bill that is at the bill maturity date when the system performs bill analysis. The target state can be a preset bill state, such as entrusted (i.e.). The first business disposal information refers to the information generated in accordance with the preset business rules corresponding to the bill maturity date, and is used to record the processing information when the bill matures, such as detailed records of collection.

[0060] For example, the system can check the expiration dates of all bills in the bill pool every day. For the first bill with bill number "123456" due on March 10, 2023, the system queries that its current bill status is "entrusted"; on March 10, 2023, the system generates the first business disposal information corresponding to this status, namely, the due collection information, including the collection date and the collection unit; after generating the first business disposal information of due collection, the system updates the bill status of the bill to "collected", reflecting that the bill has entered the due collection processing stage.

[0061] In the case where bill splitting and merging are required, in order to improve the accuracy of the basic information record table, the following steps can also be performed when the bill data is collected: obtain the first sub-bill interval of the bill data, and obtain the second sub-bill interval of the target record, wherein the first sub-bill interval is the sub-interval obtained after the bill data is split according to the bill number, and the second sub-bill interval is the sub-interval obtained after the target record is split according to the bill number; when the second sub-bill starting number in the second sub-bill interval is equal to the first sub-bill starting number in the first sub-bill interval, and the second sub-bill ending number in the second sub-bill interval is greater than the first sub-bill ending number in the first sub-bill interval, the second sub-bill interval of the target record is updated to the third sub-bill interval, wherein the third sub-bill interval is the remaining interval in the second sub-bill interval after excluding the first sub-bill interval.

[0062] The sub-bill interval refers to the number range of each sub-bill after the original bill is split into multiple sub-bills during the split operation. For example, after a commercial acceptance bill with numbers from 1000 to 2000 is split, the number range from 1000 to 1500 can be regarded as a sub-bill interval. The first sub-bill interval refers to the sub-bill interval corresponding to the collected bill data, and the second sub-bill interval refers to the sub-bill interval contained in the basic information record.

[0063] For example, when the system collects the split information of bill numbers 10001 to 10050 (i.e., the first sub-bill interval) on March 10, 2023, it checks the corresponding bill record (i.e., the target record) in the basic information record table; the bill number range of the target record is 10001 to 10100 (i.e., the second sub-bill interval), which matches the starting number of the collected split bills, but contains a wider range, that is, the target record originally contains all bills from 10001 to 10100; the system confirms the starting number of the first sub-bill interval It is equal to the starting number of the target record, and the ending number of the target record is greater than the ending number of the first sub-ticket interval, which meets the splitting condition; the system then updates the sub-ticket interval of the target record to the third sub-ticket interval, that is, from 10051 to 10100, removes the split bill number range of 10001 to 10050, and recommends a new record in the basic information record table for bills with bill numbers from 10001 to 10050 to store their bill information, ensuring the real-time accuracy and completeness of the bill pool information in the system.

[0064] In some embodiments of the present application, when the collected bill data is used to construct a bill business data set, different processing can be performed for the collected data of different business types, specifically:

[0065] (1) Collecting bill collection (i.e., receiving) business data: When collecting bill holding information (i.e., when bills flow from the issuer to the recipient, the recipient needs to record the relevant information of the bill), you can exclude records with bill status of "received for acceptance" and "received for acceptance to be signed" to ensure that only bill data for which bills have been actually collected is processed. The system matches the bill holding table records (the table used to record bill holding information) with the basic information record table based on "bill number + sub-bill interval" to support data generation for the following three subdivided scenarios:

[0066] a) New record collection: If there is no record in the basic information record table that matches the record in the ticket table, the system will judge it as a newly collected incremental ticket. The system can directly write a new record in the basic information record table based on the record information in the ticket table and generate a custody track. The business date is taken from the receipt date in the ticket table to ensure that the newly collected tickets are recorded in a timely manner.

[0067] b) Repeated collection: If one or more records matching the ticket table records already exist in the basic information record table, and the ticket status of at least one of the records is "entrusted", the system will determine that the ticket is a repeated collection of existing tickets. At this time, the system will not perform any processing to avoid data redundancy.

[0068] c) Processing of return tickets: If there are one or more records in the basic information record table that match the records in the ticket holder table, and the bill status of all matching records is "endorsement transfer", the system will determine it as a return ticket (that is, the bill was endorsed and transferred and then returned to the original unit). In this case, the system can write a record in the basic information record table based on the information in the ticket holder table record, set the bill status to "entrusted", and generate an entrustment track. The business date is taken from the receipt date in the ticket holder table to ensure accurate recording and management of return tickets.

[0069] (2) Collected bill endorsement business data: The system matches the endorsement table records (a table used to record endorsement information) with the basic information record table records based on the "bill number + sub-bill interval" to support data generation for the following four subdivision scenarios:

[0070] a) Same-day endorsement on the day of receipt: If there is no record in the basic information record table that matches the bill number and sub-bill interval in the endorsement table record, the system can determine that the bill is endorsed on the day of receipt. The system can create a record in the basic information record table based on the endorsement table record information, set the bill status to "endorsement transfer", and generate a custody track and an endorsement track. The business date of the two tracks is the endorsement date in the endorsement table to ensure that the bill information collected and endorsed on the same day is accurately recorded.

[0071] b) Endorsement of existing bills: If there is a record in the basic information record table that matches the bill number and sub-bill interval in the endorsement table, and the bill status of the record with the latest receipt date in the matching record is "entrusted", the system determines that the bill is an endorsement of the existing bill. The system can update the bill status of the corresponding record in the basic information record table to "endorsement transfer" and generate an endorsement track. The business date of the track is the endorsement date in the endorsement table to ensure that the endorsement information of the existing bill is updated.

[0072] c) Repeated collection of endorsed data: If there are records in the basic information record table whose endorsement date is equal to the collection date, the system will determine that it is endorsed data that has been collected repeatedly. At this time, no processing will be performed to avoid duplicate data writing.

[0073] d) Sub-package endorsement collection: If the starting sub-ticket interval of the bill package in this endorsement record is the same as the starting sub-ticket interval of the basic record, but the ending sub-ticket interval is smaller than the ending sub-ticket interval of the basic record, this indicates that the endorsement transaction information collected this time is a sub-package endorsement record of the original bill package. The system can update the sub-ticket interval of the original bill package to the remaining available interval, and generate a new bill package record with the sub-ticket interval information of this endorsement transaction, and set the bill status to "endorsement transfer" to ensure that the information after the bill sub-package endorsement is accurately updated and recorded.

[0074] (3) Collected bill discount business data: The system matches the discount table records (the table used to record discount information) with the basic table records based on the "bill number + sub-bill interval" to handle the following four sub-scenarios:

[0075] a) Discount on the same day of collection: If there is no record in the basic table that matches the bill number and sub-bill interval in the discount table record, the system determines that the bill is discounted on the same day of collection. The system can generate a record in the basic table based on the discount table record information, and generate a custody track and a discount track. The business date of the two tracks is the discount date in the discount table to ensure that the bill information collected and discounted on the same day is accurately recorded.

[0076] b) Discount of existing bills: If there is a record in the basic table that matches the bill number and sub-bill interval in the discount table record, and the bill status of the record with the latest bill collection date in the matching record is "entrusted", the system determines that the bill is a discount of existing bills. The system can update the bill status of the corresponding record in the basic table to "discounted" and generate a discount track. The business date of the track is the discount date in the discount table to ensure that the discount information of the existing bills is updated.

[0077] c) Duplicate collection of discounted data: If there are records in the basic table whose discount date is equal to the collection date, the system will judge it as duplicated discounted data and will not process it to avoid data duplication.

[0078] d) Sub-package discount collection: If the starting sub-bill interval of the bill package in this discount record is the same as the starting sub-bill interval of the basic record, but the ending sub-bill interval is smaller than the ending sub-bill interval of the basic record, this indicates that the discount transaction information collected this time is a sub-package discount record of the original bill package. The system can update the sub-bill interval of the original bill package to the remaining available interval, and generate a new bill package record with the sub-bill interval information of this discount transaction, and set the bill status to "discounted" to ensure that the sub-package discount information is accurately recorded and processed.

[0079] (4) Collected bill issuance business data: The system matches the bill issuance table records with the basic table records based on the bill number to support data writing in the following two business scenarios:

[0080] a) New bill issuance: If there is no record in the basic table that matches the bill number in the billing table, the system can accumulate the amount of all records of this bill number collected on the day and generate a bill information in the basic table. The bill status is set to "Open" to ensure accurate recording of new bill issuance information.

[0081] b) Duplicate opening data processing: If there is already a record in the basic table that matches the ticket number in the ticket issuance table, the system can perform a duplication check. If there is a duplication, no new data will be written. If there is no duplication, a new record will be inserted into the basic table to avoid duplicate writing of data and maintain the uniqueness and accuracy of the data.

[0082] (5) Bill collection business data processing: The system adds a new scheduling task. For bills with a bill status of "entrusted" in the basic table, a collection track is automatically generated on the due date. The business date of the track is the bill due date, and the bill status in the basic table is updated to "collected" to ensure the automated processing and status update of due bill collection.

[0083] (6) Payment business data processing: The system adds a new scheduling task. For bills with a bill status of "issued but not paid" in the basic table, a payment track is automatically generated on the due date. The business date of the track is the due date of the bill, and the bill status in the basic table is updated to "paid" to ensure the automatic processing and status update of the due payment of bills.

[0084] Based on the bill business data generated above, you can perform operations such as bill overview indicator analysis, bill total amount trend analysis, and display of the maturity distribution of existing bills. It also supports joint query of bill detail records, realizes multi-dimensional statistical analysis of bill business data, and meets the institution's overall control and lean management requirements for bill business. For example, the bill maturity distribution can take the bill detail information corresponding to the end-of-period balance of the current system month, and calculate and display it according to the number of days due, including the maturity distribution of bills receivable and the maturity distribution of bills payable.

[0085] Target bill data refers to bill information related to a specific sub-department that is filtered out from the bill business data set by department code. Target bill data is collected through official channels. Unlike the reported bill ledger data, it provides a basis for observing the department's bill business from an external perspective, which helps institutions conduct data analysis, risk monitoring and business decision-making.

[0086] In order to ensure the consistency and reliability of reconciliation data and avoid reconciliation errors caused by mismatch between department code and unified social credit code, the target bill data can be filtered through the following steps: obtain the unified social credit code corresponding to the department code from the mapping table, where the mapping table is at least used to reflect the correspondence between the department code and the unified social credit code of each sub-department; filter the bill data corresponding to the unified social credit code from the bill business data set to obtain the target bill data.

[0087] The mapping table is a key data structure in the bill management information system of an enterprise or institution, which is used to record the correspondence between the department code of each sub-department and the unified social credit code to ensure that the bill data obtained from official channels can be accurately matched with the department information within the enterprise. In some embodiments of the present application, the mapping table can be constructed in the following way: collect all sub-department information within the institution (i.e., the corporate headquarters), including the department name, department code, and the unified social credit code of the department; create a unit code-social credit code mapping table, define the fields in the table, including the unit name, unit code, and unified social credit code; enter the collected sub-department information into the mapping table, and each record should contain at least one sub-department unit code and the corresponding unified social credit code.

[0088] In order to ensure that the bill information can be classified and counted according to the organizational hierarchy of the institution, a superior unit code field can also be added to the mapping table to reflect the hierarchical structure between the sub-departments in the institution. For the processing of the hierarchical structure, a recursive query method can be used to trace the superior unit of each sub-department from bottom to top through the superior unit code field until it is traced back to the corporate headquarters. In some embodiments of the present application, in the process of constructing a bill business data set, when receiving bill information, the system can automatically query the hierarchical structure mapping table, find the corresponding department code and superior unit code through the unified social credit code, and classify the bill information into the correct sub-department or institution. At the same time, the hierarchical structure information is used to summarize the data to display the bill business profile of each sub-department and its superior department.

[0089] In some embodiments of the present application, a unified social credit code setting function interface is constructed, and a new company basic organization and unified social credit code corresponding setting function is added in the first-level treasury system, and the organization can set the corresponding relationship between the basic organization of each subordinate unit (including the hierarchical relationship between the superior and subordinate units) and the unified social credit code. After obtaining the bill information, the system matches the basic organization and the unified social credit code correspondence table through the unified social credit code in the bill information, and then takes out the secondary unit to which the bill information belongs through the subordinate relationship between the bottom unit and the secondary unit, and can display the bill balance information and transaction information of each secondary unit according to the basic organizational structure of the organization.

[0090] Step S206, comparing the bill ledger data with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

[0091] In the above step S206, the difference bill data refers to the result data generated by the system after comparing and analyzing the bill ledger data with the target bill data, which is used to indicate the difference between the two. The difference bill data may include bill information that is not correctly recorded or omitted in the bill ledger data of the sub-department, and bill business operation records that appear in the target bill data but not in the bill ledger data of the sub-department.

[0092] In order to improve the flexibility and specificity of reconciliation, reconciliation can be performed by users defining target business types and time intervals for reconciliation. Specifically: obtain a selection instruction for the target object, wherein the selection instruction includes the target business type for reconciliation and the target time interval for reconciliation; obtain first business information and second business information corresponding to the target business type from the bill ledger data and the target bill data, respectively; compare the bill data of the first business information with the bill data of the second business information to obtain difference bill data.

[0093] The selection instruction refers to the reconciliation instruction issued by the target object (such as the staff of the bill management department) through the operation interface. The instruction specifies the specific business type to be reconciled (such as bill collection, bill endorsement, bill discount, etc.) and the time range for reconciliation (such as "the second quarter of 2023" or "January 1, 2023 to March 31, 2023").

[0094] The first business information refers to the bill information of all relevant businesses extracted by the system from the bill ledger data based on the business type and time interval selected by the target object. The second business information refers to the bill information of all relevant businesses extracted by the system from the target bill data based on the business type and time interval selected by the target object.

[0095] The target user-defined business type and time interval can help the system accurately locate the reconciliation scope, improve the efficiency and pertinence of the reconciliation, and ensure the completeness and accuracy of the bill pool information. In some embodiments of the present application, the target object can select menu items including: bill collection reconciliation, bill endorsement reconciliation, bill collection reconciliation, bill discount reconciliation, bill issuance reconciliation, and bill payment reconciliation to realize the verification of the treasury bill ledger information and the bill pool information and the display of difference results.

[0096] (1) Bill collection reconciliation: used to check the consistency of bill collection information between the bill ledger data and the target bill data for a certain month.

[0097] (2) Bill endorsement reconciliation: used to check the consistency of bill endorsement information between the bill ledger data of a certain month and the target bill data.

[0098] (3) Bill collection reconciliation: used to check the consistency of bill collection information between the bill ledger data and the target bill data in a certain month.

[0099] (4) Bill Discount Reconciliation: used to check the consistency of bill discount information between the bill ledger data of a certain month and the target bill data.

[0100] (5) Bill issuance reconciliation: used to check the consistency of bill issuance information between the bill ledger data of a certain month and the target bill data.

[0101] (6) Bill payment reconciliation: used to check the consistency of bill payment information between the bill ledger data and the target bill data for a certain month.

[0102] Through the above steps S202 to S206, an automated reconciliation method is adopted to obtain a reconciliation result by comparing the bill ledger data reported by the sub-department with the corresponding bill data in the institution's bill business data set, thereby achieving the purpose of accurate reconciliation, thereby realizing efficient and accurate processing of the reconciliation process, avoiding the cumbersome and erroneous technical effects of traditional manual reconciliation, and further solving the technical problems that the relevant technology requires the business department of the institution to manually judge the rationality of the bill ledger data reported by the subordinate member units, which is inefficient and has large errors.

[0103] Figure 3 is a structural diagram of a bill reconciliation device according to an embodiment of the present application, such as Figure 3 As shown, the device comprises:

[0104] The acquisition module 302 is used to acquire the bill ledger data reported by the sub-department, wherein the bill ledger data includes the department code of the sub-department, and the sub-department includes any department affiliated to the organization;

[0105] A determination module 304 is used to determine target bill data corresponding to the department code from the bill business data set, wherein the bill data in the bill business data set includes bill data of all departments;

[0106] The comparison module 306 is used to compare the bill ledger data with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

[0107] In the above-mentioned bill reconciliation device, the determination module is also used to obtain the unified social credit code corresponding to the department code from the mapping table, wherein the mapping table is at least used to reflect the correspondence between the department code of each sub-department and the unified social credit code; and to filter the bill data corresponding to the unified social credit code from the bill business data set to obtain the target bill data.

[0108] In the above-mentioned bill reconciliation device, the determination module is also used to collect bill data, wherein the bill data includes the bill number and the business type of the bill; determine the target record corresponding to the bill number in the basic information record table, wherein a record in the basic information record table is used to represent the life cycle information of a bill, and the life cycle information includes multiple business type information; generate business disposal information corresponding to the business type of the target record, wherein the business disposal information is used to record the business type change information of the bill; determine the bill status corresponding to the business disposal information, and obtain the bill business data.

[0109] In the above-mentioned bill reconciliation device, the determination module is also used to obtain the first bill on the bill expiration date and the bill status of the first bill in the basic information record table; when the bill status of the first bill is the target status, generate first business disposal information corresponding to the bill status of the first bill; update the bill status of the first bill to the status corresponding to the first business disposal information.

[0110] In the above-mentioned bill reconciliation device, the acquisition module is also used to obtain the first sub-bill interval of the bill data and the second sub-bill interval of the target record, wherein the first sub-bill interval is the sub-bill interval obtained after the bill data is split according to the bill number, and the second sub-bill interval is the sub-bill interval obtained after the target record is split according to the bill number; when the second sub-bill starting number of the second sub-bill interval is equal to the first sub-bill starting number of the first sub-bill interval, and the second sub-bill ending number of the second sub-bill interval is greater than the first sub-bill ending number of the first sub-bill interval, the second sub-bill interval of the target record is updated to the third sub-bill interval, wherein the third sub-bill interval is the remaining interval in the second sub-bill interval after excluding the first sub-bill interval.

[0111] In the above-mentioned bill reconciliation device, the comparison module is also used to obtain a selection instruction for the target object, wherein the selection instruction includes a target business type for reconciliation and a target time period for reconciliation; obtain first business information and second business information corresponding to the target business type from the bill ledger data and the target bill data, respectively; compare the bill data of the first business information with the bill data of the second business information to obtain difference bill data.

[0112] The above-mentioned bill reconciliation device also includes a collection module 308, which is used to collect bill data of different business types of all departments in sequence according to a preset order; the bill data collected within the first preset time period is stored in a collection table, and the bill data collected within the second preset time period is stored in an archiving table, wherein the end time of the first preset time period is before the start time of the second preset time period.

[0113] It should be noted that Figure 3 The device for bill reconciliation shown is used to perform Figure 2 The method of reconciliation of bills shown, therefore Figure 2 The relevant explanations in the method of reconciliation of bills in the Figure 3 The device for reconciling bills shown will not be described in detail here.

[0114] An embodiment of the present application also provides an electronic device, which includes a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the steps of the method for bill reconciliation in each embodiment of the present application.

[0115] For example, the processor performs the following functions by executing program instructions stored in the memory:

[0116] Obtain the bill ledger data reported by the sub-department, wherein the bill ledger data includes the department code of the sub-department, and the sub-department includes any department affiliated to the organization; determine the target bill data corresponding to the department code from the bill business data set, wherein the bill data in the bill business data set includes the bill data of all departments; compare the bill ledger data with the target bill data to obtain the difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

[0117] An embodiment of the present application also provides a non-volatile storage medium, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the steps of the bill reconciliation method in each embodiment of the present application by running the computer program.

[0118] An embodiment of the present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the method for bill reconciliation in each embodiment of the present application.

[0119] An embodiment of the present application also provides a computer program, which, when executed by a processor, implements the steps of the method for bill reconciliation in each embodiment of the present application.

[0120] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0121] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0122] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0123] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0124] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0125] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0126] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for bill reconciliation, characterized in that: include: Obtaining bill ledger data reported by a sub-department, wherein the bill ledger data includes a department code of the sub-department, and the sub-department includes any department affiliated to an organization; Determining target bill data corresponding to the department code from a bill service data set, wherein the bill data in the bill service data set includes bill data of all departments; The bill ledger data is compared with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

2. The method according to claim 1, characterized in that Determining target bill data corresponding to the department code from the bill business data set includes: Obtaining the unified social credit code corresponding to the department code from a mapping table, wherein the mapping table is at least used to reflect the correspondence between the department code of each sub-department and the unified social credit code; The bill data corresponding to the unified social credit code is screened from the bill business data set to obtain the target bill data.

3. The method according to claim 1, characterized in that The bill service data in the bill service data set is obtained in the following manner: Collecting bill data, wherein the bill data includes the bill number and the business type of the bill; Determine a target record corresponding to the ticket number in a basic information record table, wherein a record in the basic information record table is used to represent life cycle information of a ticket, and the life cycle information includes multiple business type information; Generate business disposal information corresponding to the business type of the target record, wherein the business disposal information is used to record the business type change information of the bill; Determine the bill status corresponding to the business disposal information and obtain the bill business data.

4. The method according to claim 3, characterized in that The method further comprises: Acquire the first bill in the basic information record table that is on the bill expiration date and the bill status of the first bill; When the bill status of the first bill is the target status, generating first business disposal information corresponding to the bill status of the first bill; The bill status of the first bill is updated to a status corresponding to the first business disposal information.

5. The method according to claim 3, characterized in that: The method further comprises: Obtaining a first sub-ticket interval of the ticket data and a second sub-ticket interval of the target record, wherein the first sub-ticket interval is a sub-ticket interval obtained by splitting the ticket data according to the ticket number, and the second sub-ticket interval is a sub-ticket interval obtained by splitting the target record according to the ticket number; When the second sub-ticket starting number of the second sub-ticket interval is equal to the first sub-ticket starting number of the first sub-ticket interval, and the second sub-ticket ending number of the second sub-ticket interval is greater than the first sub-ticket ending number of the first sub-ticket interval, the second sub-ticket interval of the target record is updated to the third sub-ticket interval, wherein the third sub-ticket interval is the remaining interval in the second sub-ticket interval after excluding the first sub-ticket interval.

6. The method according to claim 1, characterized in that When the bill account data is compared with the target bill data, difference bill data is obtained, including: Obtaining a selection instruction for a target object, wherein the selection instruction includes a target business type for reconciliation and a target time interval for reconciliation; Acquire first business information and second business information corresponding to the target business type from the bill ledger data and the target bill data respectively; The bill data of the first business information and the bill data of the second business information are compared to obtain the difference bill data.

7. The method according to claim 3, characterized in that Collect bill data, including: Collect bill data of different business types from all departments in a preset order; The bill data collected within a first preset time period is stored in a collection table, and the bill data collected within a second preset time period is stored in an archive table, wherein the end time of the first preset time period is before the start time of the second preset time period.

8. A device for bill reconciliation, characterized in that: include: An acquisition module, used to acquire bill ledger data reported by a sub-department, wherein the bill ledger data includes a department code of the sub-department, and the sub-department includes any department affiliated to an institution; A determination module, used to determine the target bill data corresponding to the department code from the bill business data set, wherein the bill data in the bill business data set includes bill data of all departments; The comparison module is used to compare the bill ledger data with the target bill data to obtain difference bill data, wherein the difference bill data is used to represent the reconciliation result obtained after reconciling the bill ledger data of the sub-department.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute the method for bill reconciliation as described in any one of claims 1 to 7.

10. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the method for bill reconciliation described in any one of claims 1 to 7 is implemented.

Images