Method and device for analyzing balance of to-be-settled money of ticket

Abstract

The invention discloses a ticket to-be-settled balance analysis method and device, and the method comprises the steps: obtaining full-amount ticket record data, and forming a ticket detail data-recorded balance statistics base table and a balance statistics table which comprises a plurality of ticket records; each ticket record comprises a plurality of pieces of balance information of each ticket in the process from air ticket sales to settlement; screening the balance statistical table to obtain a ticket record of which the balance is not zero, the obtained fare sharing information and the tax splitting information; determining a balance type for the ticket record matched with the transition user analysis method according to a mapping relationship between the balance type and a second condition met by the ticket record; the balance type represents a reason that the ticket balance is not zero; and for the ticket record matched with the ticket payment tax balance analysis method, determining the balance type according to the ticket payment allocation information, the tax splitting information and the balance statistics base table. According to the invention, balance analysis and monitoring of the to-be-settled money in detail of the ticket granularity can be realized.

Description

Technical Field

[0001] The present invention relates to the technical field of civil aviation passenger transportation settlement, and in particular to a method and device for analyzing the balance of unsettled funds on a ticket. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. No statement herein is admitted to be prior art by virtue of its inclusion in this section.

[0003] The air transport industry is characterized by sales first, followed by transportation. Due to the complexity of ticket returns, exchanges, and interline operations, airlines often use "ticket outstanding balances" (i.e., ticket settlement accounts) as a transitional account for accounting purposes. Ticket outstanding balances bridge the gap between airlines' sales and transportation businesses. Poor management of ticket outstanding balances can directly lead to a decline in transportation business or increased losses. Therefore, airlines need to track, control, and analyze ticket settlement accounts.

[0004] However, due to the complex scenarios and numerous steps involved in ticket outstanding balances, there is currently a lack of effective methods for calculating and analyzing outstanding balances, and even fewer automated system tools to support this. Existing technology often results in significant annual balances in airline ticket settlement accounts, making balance composition analysis difficult, and balance clearing often performed across the board. This makes the management of outstanding ticket balances a challenging and pressing issue for airline revenue management.

[0005] Currently, airlines generally use the general functions of their financial systems to perform statistical analysis of the amounts and balances of ticket settlement accounts. However, due to the accounting function and data space limitations of financial systems, the underlying data of this technical solution is aggregated voucher-level data. This crude data granularity cannot guarantee the accuracy of ticket settlement account amounts and cannot meet the airlines' refined management requirements. Furthermore, the voucher data in the financial system carries limited business information, consisting only of basic accounting information. Therefore, this technical solution can only present amount and balance data summarized by account segment values, which cannot meet the airlines' statistical requirements for integrated business and financial operations, further reducing the accuracy of ticket settlement balance composition analysis. Summary of the Invention

[0006] An embodiment of the present invention provides a method for analyzing the balance of bills to be settled, which is used to analyze and monitor the balance of bills to be settled at the bill granularity level, thereby improving the efficiency and accuracy of analyzing the balance of bill settlement. The method includes:

[0007] Obtain all ticket record data to form a balance statistics base table and a balance statistics table; the balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records, each of which includes multiple balance information for each ticket from ticket sales to settlement;

[0008] Filtering ticket records with non-zero balances from the balance statistics table, and obtaining ticket price allocation information and tax splitting information for the tickets with non-zero balances; the ticket price allocation information includes information on how the ticket price is allocated to each ticket coupon, and the tax splitting information includes information on how the ticket tax is split to each ticket coupon, where the ticket has one or more ticket coupons;

[0009] Matching each ticket record with a non-zero balance with a preset analysis configuration table to determine a balance analysis method; the balance analysis method includes a transition account analysis method and a ticket payment and tax balance analysis method; the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record;

[0010] For a ticket record matching the transition account analysis method, determining the balance type based on a mapping relationship between the balance type and the second condition satisfied by the ticket record; the balance type indicates the reason why the ticket balance is not zero;

[0011] For ticket records matching the ticket price and tax balance analysis method, the balance type is determined based on the ticket price allocation information, tax split information, and the balance statistics base table.

[0012] An embodiment of the present invention further provides a device for analyzing the balance of bills to be settled, which is used to analyze and monitor the balance of bills to be settled at the bill level, thereby improving the efficiency and accuracy of analyzing the balance of bill settlement. The device includes:

[0013] The ticket data collection module is used to obtain all ticket record data and form a balance statistics base table and a balance statistics table; the balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records, each of which includes multiple balance information for each ticket from ticket sales to settlement;

[0014] A tax and fee apportionment data acquisition module is configured to filter out ticket records with non-zero balances from the balance statistics table and obtain ticket price apportionment information and tax and fee splitting information for the tickets with non-zero balances; the ticket price apportionment information includes information on the apportionment of the ticket price to each ticket coupon, and the tax and fee splitting information includes information on the splitting of the ticket tax and fee to each ticket coupon, where the ticket has one or more ticket coupons;

[0015] The balance composition analysis module is used to match each ticket record with a non-zero balance with a preset analysis configuration table to determine the balance analysis method; the balance analysis method includes a transition account analysis method and a ticket payment and tax balance analysis method, and the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record; for ticket records matching the transition account analysis method, the balance type is determined based on the mapping relationship between the balance type and the second condition satisfied by the ticket record; for ticket records matching the ticket payment and tax balance analysis method, the balance type is determined based on the ticket payment allocation information, the tax splitting information and the balance statistics base table; the balance type indicates the reason why the ticket balance is non-zero.

[0016] An embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the above-mentioned method for analyzing the balance of the bill to be settled is implemented.

[0017] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned method for analyzing the balance of bills to be settled when executed by a processor.

[0018] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the above-mentioned method for analyzing the balance of the bill to be settled.

[0019] In the embodiment of the present invention, by collecting all ticket record data to form a balance statistics base table and a balance statistics table, the balance of the amount to be settled is monitored at the ticket granularity. For tickets with non-zero balances, the transition account analysis method and the ticket tax and fee balance analysis method can be used to perform balance analysis, supporting the refined management and analysis of the account of the ticket to be settled. The mapping relationship between the balance type and the second condition satisfied by the ticket record, as well as the comparative analysis of the balance statistics base table with the ticket amount allocation information and the tax and fee splitting information, can achieve an in-depth analysis of the composition of the ticket balance, help users identify the real cause of the ticket balance, and improve the efficiency and accuracy of the analysis of the amount and balance of ticket settlement. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0021] Figure 1Schematic diagram of the flow of a method for analyzing the balance of bills to be settled according to an embodiment of the present invention;

[0022] Figure 2 Schematic diagram of a balance statistics table and a balance statistics base table in an embodiment of the present invention;

[0023] Figure 3 A schematic diagram of the process of forming a balance statistics base table and a balance statistics table in an embodiment of the present invention;

[0024] Figure 4 Schematic diagram of the process of analyzing the ticket price and tax balance in an embodiment of the present invention;

[0025] Figure 5 Schematic diagram of a device for analyzing the balance of bills to be settled according to an embodiment of the present invention;

[0026] Figure 6 Schematic diagram of a computer device in an embodiment of the present invention. DETAILED DESCRIPTION

[0027] To make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0028] In order to clearly describe the technical solutions of the embodiments of the present invention, in the embodiments of the present invention, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order.

[0029] The acquisition, transmission, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

[0030] In the prior art, bill settlement amounts are usually processed using the general functions of the financial system. Although this system provides certain statistical functions for the amount of bills settled, it has the following drawbacks:

[0031] 1. Coarse data granularity: Due to the accounting function positioning of the financial system and the limitations of data storage space, the system can only store highly aggregated data and cannot trace back to business details. This leads to a lack of sufficient detailed data support when conducting balance composition analysis.

[0032] 2. Incomplete business information: The vouchers in the financial system only contain basic accounting information and lack detailed ticket business data. This makes it difficult for the system to provide sufficient business support data and accurately analyze balance structure.

[0033] 3. Functional limitations: The existing system can only perform simple statistics and aggregated displays of amounts and balances, and lacks methods for in-depth analysis of balances, resulting in low efficiency and accuracy in balance management.

[0034] In the existing technology, manual verification is also adopted. Users obtain business data such as sold but not shipped reports, allocated balance reports, and tax split balance reports from the income settlement system, and then piece together the reports and manually verify them.

[0035] However, there are the following limitations:

[0036] 1. Data inconsistency: Business reports and accounting data are inconsistent. Furthermore, balance data assembled from business reports is unlikely to be fully consistent with data in the financial system. Using such data for subsequent overdue carry-forward work creates the risk of undermining bill settlement accounts.

[0037] 2. Incomplete balance analysis logic: The balance analysis logic is incomplete and cannot connect the entire settlement business chain. Only partial data can be pieced together, making it difficult to accurately reflect the true balance structure.

[0038] 3. It takes a long time and requires a lot of manual work; the process of checking and piecing together consumes a lot of manpower and time.

[0039] In order to solve the technical defects existing in the existing technology, the embodiments of the present invention provide a method and device for analyzing the balance of bills to be settled, which can provide statistics and monitoring of the amount and balance of the bills to be settled, and provide the function of tracing back to business details, thereby improving the accuracy of the amount and balance, supporting the refined business and financial integrated balance statistics function, and from the perspective of the entire business chain, according to the set balance composition rules and business support data, realizing the analysis of the balance composition of the bill settlement account, thereby verifying the rationality of the balance and providing effective information for the subsequent balance carry-forward.

[0040] Figure 1 FIG. 1 is a flow chart of a method for analyzing the balance of bills to be settled according to an embodiment of the present invention. Figure 1 As shown, the method includes:

[0041] Step 101: Obtain all ticket record data to form a balance statistics base table and a balance statistics table; the balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records, each of which includes multiple balance information for each ticket from ticket sales to settlement;

[0042] Step 102: Filter the balance statistics table to obtain ticket records with non-zero balances, and obtain the ticket price allocation information and tax splitting information for the tickets with non-zero balances; the ticket price allocation information includes information on the ticket price allocation for each ticket coupon, and the tax splitting information includes information on the tax splitting for each ticket coupon. The ticket may have one or more ticket coupons.

[0043] Step 103: Match each ticket record with a non-zero balance with a preset analysis configuration table to determine a balance analysis method; the balance analysis method includes a transition account analysis method and a ticket fee and tax balance analysis method; the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record;

[0044] Step 104: For the ticket record matching the transition account analysis method, determine the balance type based on the mapping relationship between the balance type and the second condition satisfied by the ticket record; the balance type indicates the reason why the ticket balance is not zero;

[0045] Step 105: For the ticket record matching the ticket price and tax balance analysis method, determine the balance type based on the ticket price allocation information, tax split information, and the balance statistics base table.

[0046] It can be seen that the method of the embodiment of the present invention mainly includes three parts: collection of amount / balance details data, acquisition of ticket payment allocation and tax splitting data, and balance composition analysis.

[0047] In step 101, all ticket record data is obtained to form a balance statistics base table and a balance statistics table.

[0048] During implementation, you can set a periodic implementation cycle for this method and execute it regularly, for example, starting the data collection process after the monthly close.

[0049] In order to obtain the full amount of ticket record data, it is necessary to obtain ticket amount related data from multiple business systems of the airline company.

[0050] In one embodiment, obtaining full ticket record data includes: obtaining ticket record data from different data processing modules to form full ticket record data; the data processing modules include multiple business modules with different data processing functions in the process from ticket sales to settlement.

[0051] For example, ticket record data can be obtained from the five major business modules of sales, transportation, internal billing, external billing, and ticket refund and exchange in the airline's revenue settlement system.

[0052] The balance statistics base table records the detailed ticket data of each data processing module. Each ticket record in the balance statistics table includes the dynamic balance information of each ticket flowing through each data processing module.

[0053] Figure 2 This is a schematic diagram of the balance statistics table and the balance statistics base table in the embodiment of the present invention, with reference to Figure 2 The balance statistics base table is unmerged and granular. It contains transaction data from ticket coupons and various data processing modules, including but not limited to detailed data such as ticket company, ticket number, issue date, ticket coupon number, sales type, and transaction amount. It should be noted that the balance statistics base table only contains transaction amounts. The balance statistics table is a consolidated data table based on different scenarios. The granularity is ticket-based, meaning one record per ticket. This record contains fields for the beginning balance, transaction amount, and ending balance for the sales, return and exchange, transportation, internal billing, and external billing data processing modules.

[0054] refer to Figure 2 The balance statistics base table includes a record for each ticket number or ticket serial number, and the record includes the balance statistics table ID. That is, for a ticket, the balance statistics base table and the balance statistics table can be associated to achieve the tracing of ticket details or balance data.

[0055] Figure 3 Schematic diagram of the process of forming a balance statistical base table and a balance statistical table in an embodiment of the present invention. Figure 3 As shown, all ticket record data is obtained to form a balance statistics base table and a balance statistics table, which may include:

[0056] Step 301: When acquiring ticket record data from different data processing modules, monitor the account transfer status of each data processing module; the account transfer status includes whether the account transfer is completed;

[0057] Step 302: When the account guide status is "account guide completed," obtain the account guide table of each data processing module; the account guide table includes the ticket record data of the data processing module;

[0058] Step 303: Carry forward the ending balances of the balance statistics base table and balance statistics table of the previous statistical period to the beginning balances of the current statistical period, thereby obtaining the balance statistics base table and balance statistics table for which data is to be imported for the current statistical period.

[0059] Step 304: Merge the ticket record data for the current statistical period in the account guide tables of each data processing module one by one according to the preset aggregation column. Write the balance information of each ticket flowing through each data processing module in the merged data into the balance statistics table for the current statistical period. Write the ticket details in the merged data into the balance statistics base table for the current statistical period. This obtains the balance statistics base table for the current statistical period.

[0060] Step 305: Merge the coupon data in the balance statistics base table and the balance statistics table for the current statistical period; the coupon data includes the data of each coupon of the same ticket; the merging process means merging the data of multiple coupons of the same ticket into the first ticket.

[0061] In one embodiment, after merging the joint ticket data in the balance statistics base table and the balance statistics table of the current statistical period, the method may further include: transferring the ticket record data with a zero balance at the end of the period in the balance statistics base table and the balance statistics table of the current statistical period to a zero table; the zero table records the ticket record data with a zero balance at the end of multiple historical statistical periods.

[0062] The following describes the process of collecting detailed amount and balance data by obtaining data from the five data processing modules: sales, transportation, internal billing, external billing, and ticket returns. It also describes how to integrate and collect the data into a single record based on the specific conditions of ticket merging.

[0063] For example, after the five data processing modules of sales, transportation, internal billing, external billing, and ticket refunds process the data and import it into the airline's financial system, data collection operations begin.

[0064] 1) Data Integrity Verification: Data from the five data processing modules is transferred to the financial system. The detailed data in the five data processing modules is granular down to the ticket level, while the data in the financial system is aggregated at the voucher level. This makes it impossible to compare the two item by item. When the aggregate amounts are completely consistent, it is determined that no data has been lost. Specifically, the process first checks whether the transfer process for the five data processing modules has been completed. If completed, the detailed data's "Account Transfer Status" will be marked as "Account Transfer Completed." The amounts of the detailed data with this "Account Transfer Completed" status will be aggregated and compared with the aggregate amounts in the financial system data. If the aggregate amounts match, the transfer process is confirmed to be complete, and the next step is advanced. If the aggregate amounts do not match, the transfer process is incomplete, the collection process is terminated, and feedback is sent upstream. Collection will be restarted after the upstream feedback has been processed. The aggregate amounts refer to the current period's incurred amounts. The current period's invoice payments and tax payments are aggregated separately. These amounts are then compared with the aggregate amounts of invoice payments and tax fees in the financial system.

[0065] 2) Preliminary processing of data: If the statistical data for the current month has been generated, clear the current month's data in the balance statistics table, balance statistics base table, and zero table.

[0066] 3) Carry forward beginning-of-period data: Carry forward the ending amounts of each statistical dimension of the previous month to the beginning amounts of this month.

[0067] 4) Accounting Month Acquisition: From each data processing module's accounting table, obtain the processing month list for the current accounting month. (Accounting month and processing month are two different concepts. Processing month: Detailed data is divided based on the ticketing date and shipping date, with data for different processing months stored in different tables. Accounting month: The month actually imported into the financial system, which corresponds to the financial system's accounting month.) Typically, each data processing module imports data into the financial system during the current processing month, meaning the data's accounting month equals the processing month. However, sales data may be imported from previous processing months, meaning the current accounting month may contain data from multiple processing months. For subsequent data processing, obtaining a list of accounting months is necessary. Specifically, the accounting tables of each data processing module filter ticket records for the current statistical period and aggregate the data by accounting month. If the accounting month is empty, aggregate the data after it has been imported into the financial system (i.e., the accounting month has been assigned a value). The accounting month field is only assigned a value upon importing data into the financial system. By filtering and acquiring data based on the accounting month (i.e., the current statistical period), duplicate data is avoided and data processing efficiency is effectively improved.

[0068] 5) Data merging and processing of each data processing module.

[0069] 5.1) Taking the sales module data as an example, sales data is divided into normal ticket aggregation and ADM (Agency Debit Memo, adjustment notice) aggregation. Normal ticket aggregation is based on the aggregation columns of each scenario in the preset balance aggregation configuration table (such as ticket number, sales date, preset subject, etc.), and merges data one by one according to the scenario. ADM aggregation requires replacing the ticket number, issue date, settlement period, and transaction number of the detailed tickets involved with the ADM order number, issue date, settlement period, and transaction number, and then aggregating them one by one. The aggregated balance data is written into the balance statistics table for the current month, and the detailed data is written into the balance statistics base table. Among them, the user can provide a preset balance aggregation configuration table, which is used to configure the aggregation column identifier for merging data.

[0070] The data processing of other data processing modules is basically the same as that of the sales module. The data is merged according to the preset aggregation columns in the preset balance aggregation configuration table. They are not listed here one by one.

[0071] 5.2) Data integrity check: By comparing the summary amount of the five major data processing modules with the summary amount of the balance statistics base table (the summary amount refers to the current amount, which is the sum of the current amounts of ticket fees and taxes), check whether the statistical data has been fully entered into the monthly balance statistics table and the balance statistics base table. If the amounts are consistent, it is considered that all statistics are completed, and the next step is continued; if the amounts are inconsistent, it is considered incomplete, and the statistics have failed. The reason must be found out and the statistics must be re-calculated. For example, if the summary amount of the five major modules is 1002w, and the summary amount of the balance statistics base table is 1000w, the statistics are not completed and the statistics have failed. It is necessary to ensure that the five major modules are consistent with the balance statistics base table.

[0072] 6) Coupon Data Merger: Tickets include both regular (non-coupon) and coupons. A coupon refers to multiple tickets issued to a single person at once, typically for flights exceeding four sectors. A single ticket can only carry four coupons. For passenger journeys exceeding four sectors, a coupon is required—multiple tickets linked by the lead ticket number. Typically, the ticket with the smallest ticket number is the lead ticket, and the total amount for the entire coupon is recorded on the lead ticket.

[0073] In judging the combination ticket: if the combination ticket identifier and the combination ticket head ticket number are empty, the ticket is confirmed to be a normal ticket; if the combination ticket identifier is not empty and the combination ticket head ticket number has a value, the ticket is confirmed to be a combination ticket;

[0074] For standard invoices, balance analysis is performed on each individual invoice. For combined invoices, the combined invoice set is used as the unit of balance analysis. Therefore, all amounts from the subsidiary invoices of the combined invoice set must be consolidated into the primary invoice. First, retrieve the associated relationships between the combined invoices from the sales module. Next, obtain the data to be merged, generate new merged data based on the associated relationships, and establish a relationship between the merged data and the pre-merged data.

[0075] 7) Annual table data generation: After the statistical results are verified, the data is merged and the annual table data is generated based on the account segment value, auxiliary accounting item, preset account, sales month, and tax code. Figure 2 , showing a schematic diagram of the balance statistics year table, including fields such as account segment value, beginning of the whole year sales period, whole year sales occurrence, and beginning of the whole year return and exchange period.

[0076] 8) Zero table data transfer: In order to improve space utilization, the data with a closing balance of 0 is transferred to the zero table.

[0077] 9) End of process: Complete the collection of amount and balance details.

[0078] In summary, when collecting detailed amount and balance data, the data collection process begins after the monthly close. Both the included and non-included amounts from the five data processing modules in the revenue settlement system—sales, transportation, internal billing, external billing, and ticket returns—are recorded in the monthly balance statistics table, the balance statistics base table, and the zero table. The beginning and ending balances are also calculated. To ensure data accuracy and completeness, a rigorous verification process is implemented. Once verification passes, the data is further aggregated to generate a complete annual table. Furthermore, data with zero ending balances is transferred to improve space utilization.

[0079] In step 102, ticket records with non-zero balances are screened from the balance statistics table, and the ticket amount allocation information and tax splitting information of the tickets with non-zero balances are obtained; the ticket amount allocation information includes information on the ticket amount allocated to each ticket coupon, and the tax splitting information is information on the ticket tax splitting to each ticket coupon, and the ticket has one or more ticket coupons.

[0080] During implementation, the ticket price allocation information and tax split information for tickets with non-zero balances are obtained, which may include:

[0081] Obtaining ticket price allocation information from an allocation system and writing the ticket price allocation information into a ticket price allocation result information table; the allocation system is used to allocate the ticket price to each ticket coupon according to a first preset rule;

[0082] obtaining tax splitting information from a tax calculation system and writing the tax splitting information into a tax splitting result information table; the tax calculation system is used to allocate the ticket tax to each ticket coupon according to a second preset rule;

[0083] Furthermore, for ticket records matching the ticket price and tax balance analysis method, the ticket price allocation information, tax split information, and the balance statistics base table are compared and analyzed, and the balance type is output, which can include:

[0084] For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation result information table, tax and fee splitting result information table, and balance statistics base table, and output the balance type.

[0085] For example, to obtain bill payment allocation information, first filter out records with non-zero ending balances from the monthly balance statistics table. Then, extract information such as the bill number, company code, and bill type one by one. Based on this information, the bill payment allocation results for the corresponding bill number, company code, and bill type are retrieved from the allocation system and stored in the bill payment allocation result information table for subsequent analysis. For example, a bill is uniquely identified using the company code, bill type, and bill number fields. These three fields act as bill IDs and are used to match allocation information, tax splitting information, and balance analysis.

[0086] For example, a passenger may purchase multiple flights when purchasing a ticket, but only pay the fare once for one ticket (a coupon). For ticket number 999-233-1923831:

[0087] Ticket coupon 1: Beijing-Tokyo;

[0088] Ticket Coupon 2: Tokyo-Sydney;

[0089] Coupon 3: Sydney-Los Angeles;

[0090] The payment information is the ticket amount of 10,000 yuan.

[0091] When obtaining a ticket, the embodiment of the present invention cannot determine the amount of each coupon. However, each coupon must be individually confirmed for transportation or transport. Therefore, the allocation system will use a series of rules to allocate 10,000 yuan to coupons 1, 2, and 3. The final allocation result is, for example:

[0092] Ticket coupon 1: 1000 yuan;

[0093] Ticket coupon 2: 5,000 yuan;

[0094] Ticket coupon 3: 4,000 yuan.

[0095] This is the ticket allocation information obtained from the allocation system, which may include domestic identification, ticket number, company code, ticket type, ticket coupon number and allocation amount.

[0096] Similarly, to obtain tax split information, first filter out records with non-zero ending balances from the monthly balance statistics table. Then, extract information such as the domestic ID, invoice number, company code, and invoice type. Based on this information, obtain the tax split results from the tax calculation system and store them in the tax split result information table for subsequent analysis. Taxes are collected uniformly on a single invoice and need to be split across each invoice coupon. The tax calculation system will split the overall tax into each invoice coupon according to specific rules. Tax split information can include the domestic ID, invoice number, company code, invoice type, coupon number, and split amount.

[0097] It should be noted that ticket price allocation and tax calculation are very complex processes. Therefore, it is necessary to obtain the calculation results from the corresponding system.

[0098] Balance composition analysis is performed in steps 103 to 105. This balance composition analysis can be divided into three steps: clearing existing analysis results for this month, data preprocessing, and balance analysis. As the core of the analysis process, the embodiment of the present invention conducts a detailed analysis of the non-zero balance results for each ticket based on a preset analysis configuration table. By comprehensively considering multiple factors, such as amount, number of items, and sales type, the root cause of these non-zero balances can be accurately identified. This step is precisely the core goal of the embodiment of the present invention, namely, to provide a clear explanation and basis for the non-zero balance of each ticket. The data preprocessing primarily involves verifying whether each ticket record with a non-zero balance meets the conditions for balance analysis.

[0099] In one embodiment, before matching each ticket record with a non-zero balance with a preset analysis configuration table and determining a balance analysis method, the method of the embodiment of the present invention may further include:

[0100] Verify whether each ticket record with a non-zero balance meets the balance analysis conditions, and obtain the ticket records with non-zero balances that meet the balance analysis conditions. The balance analysis conditions include correct data consolidation, non-unilateral accounts, and non-voided tickets.

[0101] Match each ticket record with a non-zero balance with the preset analysis configuration table to determine the balance analysis method, including:

[0102] Match ticket records with non-zero balances that meet the balance analysis criteria with the preset analysis configuration table to determine the balance analysis method.

[0103] The following is a detailed description of the balance composition analysis process.

[0104] 1) Clear existing analysis results for this month: If analysis data for the current month has already been generated, before starting the data analysis for the current month, the first step is to check and delete the existing analysis results for the current month to ensure that the analysis results are up-to-date and accurate.

[0105] 2) Data preprocessing: First, verify whether the data meets the conditions for balance analysis. In this embodiment of the present invention, balance analysis is performed only on data that meets the conditions. The conditions are that the data is correctly merged and there are no unilateral accounts or voided invoices.

[0106] First, check whether the account segment values ​​for data with the same ticket number, preset account, and issue date are consistent. For example, if multiple records with the same ticket number, preset account, and issue date but inconsistent account segment values ​​appear, it can be assumed that the data collected from different data processing modules has a segment value conflict. The user will be prompted with incorrect data and no further analysis will be performed. If consistent, the data merge was correct. If inconsistent, the merge was incorrect or the account mapping was incorrect, and the user will be prompted with the incorrect data. This data will not be analyzed further. The focus is on investigating whether any records within the same merge dimension were not correctly merged into a single record to avoid unexpected analysis results.

[0107] Secondly, special data identification, such as unilateral account data and voided invoice data, is performed based on preset unilateral account and voided invoice number lists. If a ticket number in a non-zero balance record matches the preset unilateral account or voided invoice number list, the user is prompted that the data is a unilateral account or voided invoice, and subsequent balance analysis cannot be performed on that data.

[0108] 3) Balance analysis.

[0109] 3.1) Determine which analysis method to use based on the preset analysis configuration table. The preset analysis configuration table includes three field sets: data conditions (first condition, second condition, etc.), balance analysis method, and balance type. Specifically, this table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record. It may also include a mapping relationship between the balance type and the second condition satisfied by the ticket record. For example, the first condition is the first preset account, the first preset account segment value, and the amount item.

[0110] The balance type indicates the reason why a ticket's balance is non-zero. Users can use artificial intelligence methods to analyze the reasons for historical non-zero ticket balances, thereby determining the data conditions, balance type, and balance analysis method in the preset analysis configuration table. This can then be supplemented or modified based on expert experience.

[0111] When the data's preset accounts, account segment values, and amount items meet the conditions of the transition account analysis method, transition account analysis is performed; when the data's preset accounts, account segment values, and amount items meet the conditions of the ticket tax and fee balance analysis method, ticket tax and fee balance analysis is performed.

[0112] 3.2) Transition Account Analysis. Transition Account Analysis is a simpler analysis method than ticket and tax balance analysis. Therefore, it is only necessary to determine the balance type based on the mapping relationship between the balance type and the second condition satisfied by the ticket record. The mapping relationship between the balance type and the second condition satisfied by the ticket record can also be stored in the preset analysis configuration table. Therefore, it is only necessary to screen the ticket records with non-zero balances based on the second condition in the preset analysis configuration table, such as the second preset account, the second preset account segment value, and the amount item of each data processing module. If a ticket record meets the conditions of the transition account analysis method, the balance type of the mapping relationship in the analysis configuration table is obtained to determine the reason for the ticket's end-of-period balance.

[0113] For example, the second condition includes: a. the preset account is pending settlement, b. the account segment value is 21200000, c. the sales balance at the end of the period is 0, d. the transportation balance at the end of the period is not 0, then the reason for the balance, that is, the balance type is sales not received, and the sales not received means that the carrier-related data has been received, but the sales data has not been received.

[0114] Balance types corresponding to transition account analysis include, but are not limited to: uncollected sales, return and exchange gains and losses, intermodal gains and losses, debit and credit differences, ticket payment estimates, tax and fee estimates, absenteeism and ticket loss estimates, etc.

[0115] 3.3) Matching ticket tax and fee balance analysis.

[0116] In a preferred embodiment, for a ticket record matching the ticket price and tax balance analysis method, determining the balance type based on ticket price allocation information, tax split information, and a balance statistics base table may include:

[0117] For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation information, tax split information, and the balance statistics base table to determine the process links where there are missing or incorrect ticket settlement amounts, and output the balance type.

[0118] Specifically, for ticket records matching the invoice payment and tax balance analysis method, balance analysis is performed based on the SALES_BASED principle (a sales-based revenue settlement method). The acquired invoice payment allocation information and tax split information serve as benchmark data for each business process within the ticket lifecycle. Therefore, this embodiment of the present invention compares the detailed data in the balance statistics base table with the invoice payment allocation and tax split information at the ticket and ticket package levels. This allows the identification of any missing processing steps within the ticket lifecycle, the resulting balance amount at each step, and the generation of accurate balance data.

[0119] The balance statistics table is aggregated data. The amount item summarizes the amounts of all ticket coupons of the ticket, and its granularity is at the ticket level.

[0120] The balance statistics base table contains unaggregated data, and its amount item is the amount of each ticket coupon. Its granularity is at the ticket coupon level.

[0121] For ticket-level comparisons, this embodiment compares the total apportioned amount and data aggregated by ticket number. For coupon-level comparisons, this embodiment compares the apportioned value and detailed data for each coupon. Based on the results of these comparisons at different granularities, different balance types can be identified, indicating the causes of the ending balance.

[0122] Figure 4 This is a flow chart of the method for analyzing the balance of ticket fees and taxes in an embodiment of the present invention, with reference to Figure 4 , perform the following processing on each ticket record that matches the ticket tax balance analysis method:

[0123] Step 1) Taking a single record in the current balance statistics table as an example, first obtain the detailed data associated with this ticket in the balance statistics base table based on the ID in the balance statistics table. The subsequent steps are referred to as "balance detailed data";

[0124] For example, the detailed data includes:

[0125]

[0126] They are summarized here:

[0127]

[0128] Step 2) Obtain the ticket price and tax allocation data based on the ticket company, ticket type, ticket number, and issue date;

[0129] If no matching allocation data is found, the allocation is deemed to have failed and the analysis process is terminated. This indicates that the allocation operation has failed and the user needs to correct the allocation error.

[0130] If the allocation data that meets the conditions can be retrieved, the allocation data is obtained and step 3 is continued;

[0131] Step 3) Check whether there is a record with sales type E (new ticket exchange) in the balance details data;

[0132] If such a record exists, proceed to step 4 to check whether a ticket refund or exchange is to be processed;

[0133] If no such record exists, proceed to step 5 to check whether the total allocation amount is consistent;

[0134] Step 4) Check whether there is data in the refund and exchange module in the balance details with a blank ticket number or a ticket number of 0, that is, check whether a refund process is performed;

[0135] If the ticket coupon number in the refund and exchange module does not contain any data with an empty ticket number or a ticket coupon number of 0 in the balance details, it means that the refund process has not been executed, resulting in a balance. In this case, the balance type is determined to be unrefundable, and step 6 is continued to further determine the balance type of the balance details data.

[0136] If the ticket coupon number in the refund / exchange module in the balance details is empty or 0, it means that a refund has been performed. Then, go to step 5 to check whether the total amount of the apportionment is consistent.

[0137] Step 5) Sum up the ticket price and tax apportionment amounts for all coupons of the ticket by issuing company, ticket type, and ticket number to obtain the total ticket price and tax apportionment amount. At the same time, filter out data from the detailed data that meets any of the following conditions:

[0138] Condition 1: The ticket number in the sales module or refund ticket module is empty;

[0139] Condition 2: The ticket serial number in the sales module or the refund module is 0 and the sales type is E (new ticket) or R (refund);

[0140] Sum up the amount of the filtered data by issuing company, ticket type, ticket number, and preset account (differentiated by ticket amount / tax) to obtain the detailed summary amount.

[0141] Compare the allocated total amount with the detailed summary of the invoice / taxes. If the allocated total amount is inconsistent with the detailed summary of the invoice / taxes, this is considered inconsistent with the allocated total amount. This indicates that there is a time difference between the balance statistics and the allocation result. Further analysis based on the allocation result is not possible, and the analysis process is terminated.

[0142] If the total apportioned amount is consistent with the detailed summary amount of the ticket price / tax, proceed to step 6 to further determine the balance type of the detailed data;

[0143] Step 6) Sum the balance details by ticket company, ticket type, ticket number, and ticket coupon number. For data with a ticket coupon number of 0, proceed to step 7 for determining the apportioned balance and step 8 for determining if the amount is inconsistent. For data with a ticket coupon number other than 0, proceed to step 9 for determining if the item has been sold but not shipped and step 10 for determining if the amount is inconsistent.

[0144] Step 7) For the data with ticket serial number 0, if there is no sales type 0 (old ticket) in the balance details and the corresponding allocation record has a non-zero amount, then generate the analysis result of the allocation balance and terminate the analysis process;

[0145] Step 8) For data with ticket serial number 0, if the balance details contain a sales type of 0 and a non-zero amount, and the amount in the details is inconsistent with the amount in the allocation record, an allocation result with inconsistent amounts is generated and the analysis process is terminated.

[0146] For data with ticket number 0, if the conditions of steps 7 and 8 are not met, the analysis process is terminated;

[0147] Step 9) For data with a ticket coupon number other than 0, if the balance detail amount is equal to 0 and the amount in the apportionment record is not equal to 0, then a sold but not shipped analysis result is generated, and the analysis process is terminated;

[0148] Step 10) For data with a ticket number other than 0, if the amount in the detail data is not equal to 0 but the amount in the apportionment record is equal to 0, an analysis result of inconsistent amounts is generated and the analysis process is terminated;

[0149] For data whose ticket number is not 0, if the conditions of steps 9 and 10 are not met, the analysis process is terminated;

[0150] Step 11) The process ends.

[0151] The types of balances that can be generated by the tax balance analysis method include but are not limited to unexecuted returns, inconsistent allocated balances, inconsistent allocated totals, inconsistent amounts, sales but not shipments, and allocation failures.

[0152] During implementation, steps 103 and 104 can be performed before step 102. That is, after the balance statistics base table and the balance statistics table are generated, the balance analysis method matching the non-zero balance of the ticket record can be determined. However, only for ticket records matching the ticket price, tax, and fee balance analysis method, the ticket price allocation information and tax and fee splitting information are obtained. The balance type of the ticket record matching the ticket price, tax, and fee balance analysis method is then determined based on the ticket price allocation information, tax and fee splitting information, and the balance statistics base table.

[0153] In summary, the embodiments of the present invention have the following technical advantages:

[0154] 1) Refined balance statistics: By collecting detailed ticket data and business information, it supports refined management and analysis of ticket settlement items.

[0155] 2) Balance composition analysis: By matching with allocation data and tax split data, an in-depth analysis of the balance composition is achieved to help users identify the causes of the balance.

[0156] 3) Automated carry-forwarding: Automatically generates carry-forwarding transactions based on user-configured conditions, improving the efficiency and accuracy of balance clearing.

[0157] 4) Closed-loop management: Through closed-loop operations of balance statistics, analysis, and carry-forwarding, full-process management of bill settlement accounts is achieved, reducing the risk of business losses.

[0158] Through the above technical solution, the embodiment of the present invention can effectively solve the difficult problems in the management of airline ticket settlement items and improve the efficiency and accuracy of ticket balance analysis.

[0159] The present invention also provides a device for analyzing the balance of outstanding bills, as described in the following embodiments. Because the principles underlying the device are similar to those of the method for analyzing the balance of outstanding bills, the implementation of the device can be referenced to the implementation of the method, and any repetitions will not be repeated.

[0160] Figure 5 FIG. 1 is a schematic diagram of a device for analyzing the balance of bills to be settled according to an embodiment of the present invention. Figure 5 As shown, the device 500 includes:

[0161] The ticket data collection module 501 is used to obtain all ticket record data and form a balance statistics base table and a balance statistics table. The balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records. Each ticket record includes multiple balance information for each ticket from ticket sales to settlement.

[0162] The apportioned tax and fee data acquisition module 502 is configured to filter out ticket records with non-zero balances from the balance statistics table and obtain the ticket price apportionment information and tax and fee splitting information for the tickets with non-zero balances. The ticket price apportionment information includes the apportionment of the ticket price to each ticket coupon, and the tax and fee splitting information includes the splitting of the ticket tax and fee to each ticket coupon. The ticket may have one or more ticket coupons.

[0163] The balance composition analysis module 503 is used to match each ticket record with a non-zero balance with a preset analysis configuration table to determine the balance analysis method; the balance analysis method includes a transition account analysis method and a ticket payment and tax balance analysis method, and the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record; for ticket records matching the transition account analysis method, the balance type is determined based on the mapping relationship between the balance type and the second condition satisfied by the ticket record; for ticket records matching the ticket payment and tax balance analysis method, the balance type is determined based on the ticket payment allocation information, the tax splitting information and the balance statistics base table; the balance type indicates the reason why the ticket balance is non-zero.

[0164] In one embodiment, the balance statistics base table records detailed ticket data from various data processing modules. Each ticket record in the balance statistics table includes dynamic balance information for each ticket as it passes through various data processing modules. The data processing modules include multiple business modules with different data processing functions in the process from ticket sales to settlement.

[0165] The ticket data collection module 501 is specifically used to obtain ticket record data from different data processing modules to form full ticket record data.

[0166] In one embodiment, the ticket data collection module 501 is specifically used to:

[0167] When acquiring ticket record data from different data processing modules, monitor the account transfer status of each data processing module; the account transfer status includes whether the account transfer is completed;

[0168] When the account transfer status is completed, the account transfer table of each data processing module is obtained; the account transfer table includes the ticket record data of the data processing module;

[0169] Carry forward the ending balances of the balance statistics base table and balance statistics table of the previous statistical period to the beginning balances of the current statistical period to obtain the balance statistics base table and balance statistics table for the current statistical week.

[0170] Merge the ticket record data of the current statistical period in the account guide table of each data processing module one by one according to the preset aggregation column. Write the balance information of each ticket flowing through each data processing module in the merged data into the balance statistics table of the current statistical week to be imported. Write the detailed data in the merged data into the balance statistics base table of the current statistical week to be imported, and obtain the balance statistics base table of the current statistical period.

[0171] The combined ticket data in the balance statistics base table and the balance statistics table of the current statistical period are merged; the combined ticket data includes the data of each ticket coupon of the same ticket; the combined processing means merging the data of multiple ticket coupons of the same ticket into the first ticket.

[0172] In one embodiment, the apparatus 500 may further include:

[0173] The zero table processing module is used for the ticket data collection module 501 to merge the joint ticket data in the balance statistics base table and the balance statistics table of the current statistical period, and transfer the ticket record data with zero balance at the end of the balance statistics base table and the balance statistics table of the current statistical period to the zero table; the zero table records the ticket record data with zero balance at the end of multiple historical statistical periods.

[0174] In one embodiment, the apportioned tax data acquisition module 502 is specifically configured to:

[0175] Obtaining ticket price allocation information from an allocation system and writing the ticket price allocation information into a ticket price allocation result information table; the allocation system is used to allocate the ticket price to each ticket coupon according to a first preset rule;

[0176] obtaining tax splitting information from a tax calculation system and writing the tax splitting information into a tax splitting result information table; the tax calculation system is used to allocate the ticket tax to each ticket coupon according to a second preset rule;

[0177] The balance composition analysis module 503 is specifically used to:

[0178] For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation result information table, tax and fee splitting result information table, and balance statistics base table, and output the balance type.

[0179] In one embodiment, the apparatus 500 further includes:

[0180] The balance analysis preprocessing module is used to match each non-zero balance ticket record with a preset analysis configuration table in the balance composition analysis module 503. Before determining the balance analysis method, it verifies whether each non-zero balance ticket record meets the balance analysis conditions, and obtains the non-zero balance ticket records that meet the balance analysis conditions. The balance analysis conditions include correct data merging and non-unilateral accounts and non-voided tickets.

[0181] The balance composition analysis module 503 is specifically used to:

[0182] Match ticket records with non-zero balances that meet the balance analysis criteria with the preset analysis configuration table to determine the balance analysis method.

[0183] In one embodiment, the first condition of the preset analysis configuration table includes a first preset account, a first preset account segment value, and an amount item.

[0184] In one embodiment, the second condition of the preset analysis configuration table includes a second preset subject, a second preset subject segment value, and an amount item of each data processing module.

[0185] In one embodiment, the balance types include unexecuted returns, inconsistent apportionment balances, inconsistent apportionment totals, inconsistent amounts, sold but not shipped, and apportionment failure;

[0186] The balance composition analysis module 503 is specifically used to:

[0187] For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation information, tax split information, and the balance statistics base table to determine the process links where there are missing or incorrect ticket settlement amounts, and output the balance type.

[0188] Figure 6 Schematic diagram of a computer device according to an embodiment of the present invention. Figure 6 As shown, an embodiment of the present invention further provides a computer device 600, including a processor 601, a memory 602, and a computer program 603 stored in the memory 602 and executable on the processor 601, wherein the processor 601 implements the above-mentioned method for analyzing the balance of the bill to be settled when executing the computer program 603.

[0189] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program, which implements the above-mentioned method for analyzing the balance of bills to be settled when executed by a processor.

[0190] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the above-mentioned method for analyzing the balance of the bill to be settled.

[0191] In summary, the present embodiment includes two major functions: balance statistics and balance composition analysis. The balance statistics function automatically collects the balances of each ticket across sales, returns, transportation, external billing, internal billing, tax filing, and overdue carry-forward stages, acquiring both financial accounting data and business information. This data is then consolidated using flexible aggregation dimensions to aggregate the balances at the ticket level, generating statistics on the balances at each settlement stage and calculating the beginning and ending balances. The balance composition analysis function matches the balances of each ticket's settlement account with the bill payment allocation data / ticket tax split data based on the SALES_BASED settlement principle, identifying the settlement stage where the bill payment is missing or incorrect. Furthermore, the balance composition analysis function automatically categorizes the ending balance at the ticket coupon level based on customizable balance analysis rules, categorizing the causes and amounts of the ending balances.

[0192] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0193] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0194] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0195] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0196] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for analyzing the balance of bills to be settled, characterized in that: include: Obtain all ticket record data to form a balance statistics base table and a balance statistics table; the balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records, each of which includes multiple balance information for each ticket from ticket sales to settlement; Filtering ticket records with non-zero balances from the balance statistics table, and obtaining ticket price allocation information and tax splitting information for the tickets with non-zero balances; the ticket price allocation information includes information on how the ticket price is allocated to each ticket coupon, and the tax splitting information includes information on how the ticket tax is split to each ticket coupon, where the ticket has one or more ticket coupons; Matching each ticket record with a non-zero balance with a preset analysis configuration table to determine a balance analysis method; the balance analysis method includes a transition account analysis method and a ticket payment and tax balance analysis method; the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record; For a ticket record matching the transition account analysis method, determining the balance type based on a mapping relationship between the balance type and the second condition satisfied by the ticket record; the balance type indicates the reason why the ticket balance is not zero; For ticket records matching the ticket price and tax balance analysis method, the balance type is determined based on the ticket price allocation information, tax split information, and the balance statistics base table.

2. The method according to claim 1, wherein The balance statistics base table records detailed ticket data from each data processing module. Each ticket record in the balance statistics table includes dynamic balance information for each ticket flowing through each data processing module. The data processing modules include multiple business modules with different data processing functions in the process from ticket sales to settlement. Get full ticket record data, including: Obtain ticket record data from different data processing modules to form full ticket record data.

3. The method according to claim 2, wherein Obtain all ticket record data to form a balance statistics base table and a balance statistics table, including: When acquiring ticket record data from different data processing modules, monitor the account transfer status of each data processing module; the account transfer status includes whether the account transfer is completed; When the account transfer status is completed, the account transfer table of each data processing module is obtained; the account transfer table includes the ticket record data of the data processing module; Carry forward the ending balances of the balance statistics base table and balance statistics table of the previous statistical period to the beginning balances of the current statistical period to obtain the balance statistics base table and balance statistics table for the current statistical week. Merge the ticket record data of the current statistical period in the account guide table of each data processing module one by one according to the preset aggregation column. Write the balance information of each ticket flowing through each data processing module in the merged data into the balance statistics table of the data to be imported in the current statistical week. Write the ticket certificate details in the merged data into the balance statistics base table of the data to be imported in the current statistical week to obtain the balance statistics base table of the current statistical period. The combined ticket data in the balance statistics base table and the balance statistics table of the current statistical period are merged; the combined ticket data includes the data of each ticket coupon of the same ticket; the combined processing means merging the data of multiple ticket coupons of the same ticket into the first ticket.

4. The method according to claim 1, wherein After merging the joint ticket data in the balance statistics base table and balance statistics table for the current statistical period, the following is also included: The balance statistics base table of the current statistical period and the ticket record data with zero balance at the end of the period in the balance statistics table are transferred to the zero table; the zero table records the ticket record data with zero balance at the end of multiple historical statistical periods.

5. The method according to claim 1, wherein Obtains the payment allocation and tax split information for tickets with a non-zero balance, including: Obtaining ticket price allocation information from an allocation system and writing the ticket price allocation information into a ticket price allocation result information table; the allocation system is used to allocate the ticket price to each ticket coupon according to a first preset rule; obtaining tax splitting information from a tax calculation system and writing the tax splitting information into a tax splitting result information table; the tax calculation system is used to allocate the ticket tax to each ticket coupon according to a second preset rule; For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation information, tax split information, and the balance statistics base table, and output the balance type, including: For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation result information table, tax and fee splitting result information table, and balance statistics base table, and output the balance type.

6. The method according to claim 3, wherein Match each ticket record with a non-zero balance with the preset analysis configuration table. Before determining the balance analysis method, the following steps are also included: Verify whether each ticket record with a non-zero balance meets the balance analysis conditions, and obtain the ticket records with non-zero balances that meet the balance analysis conditions. The balance analysis conditions include correct data consolidation, non-unilateral accounts, and non-voided tickets. Match each ticket record with a non-zero balance with the preset analysis configuration table to determine the balance analysis method, including: Match ticket records with non-zero balances that meet the balance analysis criteria with the preset analysis configuration table to determine the balance analysis method.

7. The method according to claim 1, wherein The first condition of the preset analysis configuration table includes a first preset subject, a first preset subject segment value, and an amount item.

8. The method according to claim 2, wherein The second condition of the preset analysis configuration table includes a second preset subject, a second preset subject segment value, and amount items of each data processing module.

9. The method according to claim 2, wherein The balance types include unfulfilled returns, inconsistent apportionment balances, inconsistent apportionment totals, inconsistent amounts, sold but not shipped, and apportionment failures; For ticket records matching the fare tax balance analysis method, the balance type is determined based on fare allocation information, tax split information, and the balance statistics base table. This includes: For ticket records matching the ticket payment and tax balance analysis method, compare and analyze the ticket payment allocation information, tax split information, and the balance statistics base table to determine the process links where there are missing or incorrect ticket settlement amounts, and output the balance type.

10. A device for analyzing the balance of bills to be settled, characterized in that: include: The ticket data collection module is used to obtain all ticket record data and form a balance statistics base table and a balance statistics table; the balance statistics base table records detailed ticket data, and the balance statistics table includes multiple ticket records, each of which includes multiple balance information for each ticket from ticket sales to settlement; A tax and fee apportionment data acquisition module is configured to filter out ticket records with non-zero balances from the balance statistics table and obtain ticket price apportionment information and tax and fee splitting information for the tickets with non-zero balances; the ticket price apportionment information includes information on the apportionment of the ticket price to each ticket coupon, and the tax and fee splitting information includes information on the splitting of the ticket tax and fee to each ticket coupon, where the ticket has one or more ticket coupons; The balance composition analysis module is used to match each ticket record with a non-zero balance with a preset analysis configuration table to determine the balance analysis method; the balance analysis method includes a transition account analysis method and a ticket payment and tax balance analysis method, and the preset analysis configuration table includes a mapping relationship between the balance analysis method and the first condition satisfied by the ticket record; for ticket records matching the transition account analysis method, the balance type is determined based on the mapping relationship between the balance type and the second condition satisfied by the ticket record; for ticket records matching the ticket payment and tax balance analysis method, the balance type is determined based on the ticket payment allocation information, the tax splitting information and the balance statistics base table; the balance type indicates the reason why the ticket balance is non-zero.

11. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

13. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images