Centralized settlement system and method for regional ticket business management

Abstract

The invention relates to the technical field of electronic tickets, and discloses a centralized settlement system and method for regional ticket management, and the system comprises a data collection system, a preprocessing system, a settlement system, and an analysis system. The data acquisition system is used for importing ticket business data of each ticket business association main body; the preprocessing system comprises a preprocessing module for preprocessing ticket business data; the settlement system comprises a timing module, a settlement module and a secondary settlement module; the timing module is used for dividing ticket business data according to settlement time nodes; the settlement module is used for calculating cost information according to a preset settlement rule and generating a settlement sheet; the analysis system comprises a settlement comparison module which is used for collecting ticket business change behaviors between settlement time nodes and updating cost information; and the secondary settlement module is used for generating a secondary settlement sheet based on the recently updated cost information at the settlement time node. According to the invention, time-division and main-body-division settlement of regional tickets can be efficiently realized, and the correspondence of settlement can be ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic ticketing, and in particular to a centralized settlement system and method for regional ticketing management. Background Art

[0002] With the acceleration of urbanization, people's travel needs are growing. Whether it is a short or long-distance trip, passengers expect to have a convenient and efficient service experience. In order to meet this demand, transportation ticketing service providers continue to launch new products and services to meet the needs of different passenger groups. Such as product design for different travel modes (high-speed rail, train, long-distance passenger transport, etc.), different levels (first-class seats, second-class seats, etc.), different ticket types (such as one-way tickets, round-trip tickets, monthly tickets, student tickets, connecting tickets, virtual tickets, etc.), service design for different ticket purchase methods (offline window ticketing, automatic terminal ticketing, mobile APP / web ticketing), service design for different payment methods (QR code payment, NFC payment, cash payment, etc.), etc. This diversified development of transportation ticketing service has also brought many problems to transportation ticketing management:

[0003] (1) There are many existing business lines and products, and the payment flows of various products are intertwined, which leads to the complexity of financial statistics and settlement work. The platform payment flow involves multiple merchant numbers, and each merchant number is associated with multiple products such as bus tickets and intercity express buses, which makes the already complex financial processing even more difficult to manage. In particular, in the two businesses of bus tickets and intercity express buses, the huge number of tickets sold each month directly leads to a surge in settlement data, which increases the time and difficulty of data processing.

[0004] (2) There are many settlement entities and a secondary clearing workflow. That is, in actual ticketing work, each ticketing platform needs to settle with the station based on the sales time, and the station needs to settle with the transportation company based on the departure time. This different settlement time node causes differences in the amount, increasing the difficulty of reconciliation. In addition, there are many settlement entities and a large number of related bank accounts. This means that the finance department must manually check each transaction information when making public transfers, which is not only inefficient, but also very easy to cause confusion in financial data due to human errors.

[0005] (3) The settlement path is complex and changeable. For example, when settling with a transportation company, the capital flow of its parent company may also need to be considered. In addition to the station’s own settlement, the station also needs to settle the revenue of off-site stations separately, which further increases the complexity of financial work. In addition, in the actual operation process, there are special situations such as ticket changes and passenger pick-ups. These operations cause deviations between sales tickets and actual riding conditions, thereby adding more uncertainties in the secondary settlement.

[0006] (4) Abnormal orders and cross-cycle refunds will lead to inconsistent status between stations and platforms, which will affect the accuracy of settlement. Especially in the offline ticket sales process, due to the issue of cash payment, the existing settlement system is difficult to distinguish between cash payment and non-cash payment data, which undoubtedly increases the difficulty of settlement with transportation companies. Summary of the invention

[0007] The present invention aims to provide a centralized settlement system and method for regional ticket management, which can efficiently realize the time-sharing and subject-sharing settlement of regional tickets and ensure the correspondence of the settlement.

[0008] To achieve the above objectives, the present invention provides the following basic solutions.

[0009] Solution 1

[0010] A centralized settlement system for regional ticket management, comprising a data collection system, a preprocessing system, a settlement system and an analysis system; the data collection system is used to import ticket data of various ticket-related entities; the preprocessing system comprises a preprocessing module; the preprocessing module is used to preprocess ticket data; the settlement system comprises a timing module, a settlement module and a secondary settlement module; the timing module is used to set settlement time nodes and divide ticket data according to settlement time nodes; the settlement time nodes include ticket sales time and ticket dispatch time; the settlement module is used to calculate fee information based on ticket data according to preset settlement rules and generate a settlement slip;

[0011] The analysis system includes a settlement comparison module; the settlement comparison module is used to collect ticket change behaviors between settlement time nodes and update fee information based on the ticket change behaviors; the secondary settlement module is used to generate a secondary settlement order at the settlement time node based on the most recently updated fee information.

[0012] Furthermore, the ticketing-related entities include offline ticketing platforms and online ticketing platforms.

[0013] Furthermore, the preprocessing system also includes a pre-screening module; the pre-screening module is used to distinguish cash data from non-cash data in ticketing data; wherein, when distinguishing ticketing data, regular expressions are used to match and extract key fields in payment records, and the key fields include payment method and transaction amount.

[0014] Furthermore, the preprocessing system also includes a risk identification module; the risk identification module is provided with an anomaly detection algorithm; the anomaly detection algorithm is used to identify abnormal transaction behaviors in ticketing data, and mark the corresponding ticketing data as risk data.

[0015] Furthermore, the settlement system also includes an encryption module; the encryption module is used to encrypt data to perform confidential transmission of ticketing data; the encryption module uses the SSL / TLS protocol for encrypted communication.

[0016] Furthermore, the ticket change behavior includes ticket rebooking, ticket refunding, and ticket replacement.

[0017] Furthermore, it also includes a storage system; the storage system adopts a distributed storage structure.

[0018] Furthermore, the storage system also includes a database; the database is used to back up ticketing data and fee information; the database uses a combination of ClickHouse and MySQL to synchronize and store data.

[0019] Furthermore, the settlement system also includes a report module; the report module is used to generate a cross-check report based on the expense information and a preset cross-check formula.

[0020] Solution 2

[0021] A centralized calculation method for regional ticket management, using a centralized settlement system for regional ticket management as described in Scheme 1 to perform centralized settlement of regional tickets; comprising the following steps:

[0022] The ticket data of each ticket-related entity is imported through the data collection system; the ticket data is preprocessed by the preprocessing module of the preprocessing system; the timing module of the settlement system sets the settlement time node and divides the ticket data according to the settlement time node; the settlement time node includes the ticket sales time and the ticket dispatch time; the settlement module of the settlement system calculates the fee information based on the ticket data according to the preset settlement rules and generates a settlement slip;

[0023] The settlement comparison module of the analysis system collects ticket change behaviors between settlement time nodes and updates fee information based on the ticket change behaviors; the secondary settlement module of the settlement system generates a secondary settlement order at the settlement time node based on the most recently updated fee information.

[0024] The working principle and advantages of the present invention are:

[0025] The ticketing data generated by multiple platforms are summarized in this system for centralized settlement. Among them, the timing module in the settlement system divides the ticketing data according to the required settlement time nodes, which can meet the different needs of different settlement entities for settlement nodes. Here, the settlement time nodes include ticket sales time and ticket dispatch time, which can effectively match the settlement nodes between the ticketing platform-station-transportation company in the actual ticketing operation. The settlement module of the settlement system directly generates the cost information and settlement slip according to the preset settlement rules, which can be used as a one-time settlement to meet the real-time ticket settlement data needs between the ticketing platform and the station. As for the reconciliation problems caused by ticket changes between settlement time nodes, the settlement comparison module of the analysis system monitors and analyzes the ticket changes and updates the cost information; the secondary settlement module then performs secondary settlement at the settlement time node to achieve accurate secondary clearing.

[0026] The invention provides a centralized settlement system and method for regional ticket management, which can efficiently realize the time-sharing and subject-sharing settlement of regional tickets and ensure the correspondence and accuracy of the settlement. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 The diagram is a schematic diagram of the system structure of an embodiment of a centralized settlement system and method for regional ticket management according to the present invention. DETAILED DESCRIPTION

[0028] The following is a further detailed description through specific implementation methods:

[0029] The embodiment is basically as shown in the attached Figure 1 Shown: A centralized settlement system for regional ticketing management, including a data acquisition system, a preprocessing system, a settlement system, an analysis system and a storage system.

[0030] The data collection system is used to import the ticketing data of each ticketing related entity. The ticketing related entity includes an offline ticketing platform and an online ticketing platform. The ticketing data includes order information, payment information, ticketing status, station service related information, etc.

[0031] Among them, the order information includes the vehicle information corresponding to the order (basic information such as vehicle number, type, capacity, etc.), the passenger information corresponding to the order (personal information such as name, ID number, contact information, etc.), the route information corresponding to the order (origin, destination, stops along the way, departure time, arrival time, etc.), order number, order status (such as reservation, successful payment, refund, etc.), ticket purchase time, fare, etc. Payment information includes payment method (such as cash, bank card, third-party payment, etc.), payment time, transaction amount, etc. Ticket status includes whether the ticket has been printed, whether the ticket has been checked and boarded, and other status information. Station service-related information includes passenger station service fees, passenger agency fees, passenger transportation fees, surplus ticket money, refund fees, etc.

[0032] The preprocessing system includes a preprocessing module, a pre-screening module and a risk identification module.

[0033] The preprocessing module is used to preprocess the ticketing data. The preprocessing includes identifying and filtering out invalid data, duplicate data and erroneous data in the ticketing data. Erroneous data and duplicate data are filtered out by data cleaning, and invalid data is filtered out by setting a rule engine.

[0034] The pre-screening module is used to distinguish cash data from non-cash data in the ticket data; when distinguishing the ticket data, a regular expression is used to match and extract key fields in the payment record, and the key fields include payment method and transaction amount. By pre-distinguishing cash data from non-cash data, it is convenient to perform subsequent cash / non-cash single account settlement, which can meet different ticket settlement requirements.

[0035] The risk identification module is provided with an anomaly detection algorithm; the anomaly detection algorithm is used to identify abnormal transaction behaviors in ticketing data, and mark the corresponding ticketing data as risk data.

[0036] Specifically, in this embodiment, the anomaly detection algorithm used is the isolation forest algorithm.

[0037] The settlement system includes a timing module, a settlement module, a secondary settlement module, a report module and an encryption module.

[0038] The timing module is used to set the settlement time node and divide the ticket data according to the settlement time node; the settlement time node includes the ticket sales time and the ticket dispatch time. Preferably, the settlement time node also includes the intermediate node between the ticket sales time and the ticket dispatch time. In this embodiment, the setting of the intermediate node is set with reference to the refund and change rules of each type of ticket. Taking train tickets as an example, the intermediate node can be set to 8 days before the ticket dispatch (i.e. before departure), 48 hours before the ticket dispatch (i.e. before departure), and 24 hours before the ticket dispatch (i.e. before departure). With this setting, the time nodes related to the intermediate cost information (such as the refund fee) are also monitored and divided, which is convenient for accurate confirmation of the cost information.

[0039] The settlement module is used to calculate the fee information based on the ticket data according to the preset settlement rules and generate a settlement slip.

[0040] Specifically, the fee information may include ticket sales revenue, station service fees, passenger station service fees, passenger agency fees, etc. for a specified train within a specified period. The preset settlement rules are set by each ticket-related entity that generates ticket data. For example, the single-period ticket sales revenue is set to the sum of the ticket prices of the tickets sold within a month, the station service fee collection ratio is set to a% of the single-period ticket sales revenue, and the transportation company's share ratio is set to b% of the single-period ticket sales revenue.

[0041] In this embodiment, a settlement form template is also preset in the settlement module, and the settlement form template can also be set by each ticket-related entity that generates ticket data; for example, the settlement form template may include the following columns: settlement period - the time range covered by the settlement form, such as from a certain year and month to a certain year and month; settlement entity - information on the settlement party involved, including but not limited to the platform (ticketing system), station, transportation company, third-party payment service provider, etc.; total transaction amount - the total revenue amount within the settlement period; ticket details - specific ticket transaction records, including but not limited to the number of tickets sold, ticket price, ticketing time, payment method; settlement method and time; remarks and notes; signature and seal; attachment list, etc.

[0042] The analysis system includes a settlement comparison module. The settlement comparison module is used to collect ticket change behaviors between settlement time nodes and update fee information based on the ticket change behaviors. The ticket change behaviors include ticket change behaviors, ticket refund behaviors, and ticket supplement behaviors. When updating the fee information here, the settlement module can be linked to recalculate the fee information related to the ticket change behavior to update the fee information.

[0043] The settlement comparison module is also used to perform daily transaction comparison. The daily transaction comparison includes: automatically comparing the ticket data of each ticket-related platform with the ticket details in the station system every day, and confirming the consistency between the two; such as whether the order status, ticket data, ticket status, money status, refund method, refund amount, etc. in the ticket details are consistent with those shown in the ticket data.

[0044] If they are consistent, no processing will be done. If they are inconsistent, the corresponding ticket data will be counted as abnormal transaction data and summarized into an abnormal transaction list.

[0045] The secondary settlement module is used to generate a secondary settlement sheet at a settlement time node based on the most recently updated fee information.

[0046] In the secondary settlement form, in addition to the columns included in the settlement form template in the settlement module, it also includes: ticket change records - the number, amount and related fees of ticket changes, refunds and supplementary tickets; preferential policies and discounts - the number and amount of special ticket types (such as student tickets, group tickets, etc.); fees and commissions; taxes; adjustment items - abnormal transactions and their amounts; final settlement amount - the final settlement amount after adjustment of the above columns.

[0047] The report module is used to generate a cross-check report based on the expense information and a preset cross-check formula.

[0048] In this embodiment, the preset reconciliation formulas include the platform reconciliation report formula and the station reconciliation report formula, which are used to check sales receipts and expenditure accounts, check whether the logical relationship between the funds is reasonable, ensure the consistency between the various funds, and thus ensure the accuracy and completeness of the expense settlement.

[0049] The platform reconciliation report formula is specifically: current period ticket sales amount + previous period ticket sales amount - current period pre-sale amount = passenger ticket amount + surplus ticket amount + current period ticket sales and current period ticket refunds + current period ticket sales and current period ticket refunds + previous period pre-sale ticket refunds.

[0050] The formula for the station reconciliation report is specifically: current period ticket sales amount + previous period pre-sale amount - current period pre-sale amount = passenger ticket amount + surplus ticket amount + previous period pre-sale ticket refund amount + current period ticket sales and current period departure ticket refund amount.

[0051] Among them, the ticket sales amount for this period is the total ticket amount corresponding to the paid and issued tickets for the order placed in the current settlement month.

[0052] Previous pre-sale amount - the total amount of tickets paid and issued for tickets with an order placed in the previous settlement month and a departure time in the current settlement month, minus the amount of tickets sold and refunded in the previous month.

[0053] Pre-sale amount for this period - the total amount of ticket prices corresponding to the paid and issued tickets when the order is placed in the current settlement month and the departure time is in the next settlement month.

[0054] The encryption module is used to encrypt data for confidential transmission of ticket data; the encryption module uses the SSL / TLS protocol for encrypted communication, which can fully protect the security of transaction data during transmission and storage.

[0055] The storage system adopts a distributed storage structure. The storage system also includes a database; the database is used to back up ticket data and fee information; the database uses a combination of ClickHouse and MySQL to synchronize and store data; it can achieve redundant backup and load balancing of data, ensure data reliability and scalability, and improve storage efficiency.

[0056] A centralized calculation method for regional ticket management, using the centralized settlement system for regional ticket management as described above to perform centralized settlement of regional tickets; comprising the following steps:

[0057] The ticket data of each ticket-related entity is imported through the data collection system; the ticket data is preprocessed by the preprocessing module of the preprocessing system; the timing module of the settlement system sets the settlement time node and divides the ticket data according to the settlement time node; the settlement time node includes the ticket sales time and the ticket dispatch time; the settlement module of the settlement system calculates the fee information based on the ticket data according to the preset settlement rules and generates a settlement slip;

[0058] The settlement comparison module of the analysis system collects ticket change behaviors between settlement time nodes and updates fee information based on the ticket change behaviors; the secondary settlement module of the settlement system generates a secondary settlement order at the settlement time node based on the most recently updated fee information.

[0059] The centralized settlement system and method for regional ticket management provided in this embodiment can efficiently realize the time-sharing and entity-sharing settlement of regional ticketing and ensure the correspondence of the settlement.

[0060] The above is only an embodiment of the present invention. The common sense such as the known specific structure and characteristics in the scheme is not described in detail here. The ordinary technicians in the relevant field are aware of all the common technical knowledge in the technical field of the invention before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply the conventional experimental means before that date. The ordinary technicians in the relevant field can improve and implement the scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for the ordinary technicians in the relevant field to implement this application. It should be pointed out that for the technicians in this field, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent.

Claims

1. A centralized settlement system for regional ticket management, characterized in that: It includes a data collection system, a preprocessing system, a settlement system and an analysis system; the data collection system is used to import the ticket data of each ticket-related entity; the preprocessing system includes a preprocessing module; the preprocessing module is used to preprocess the ticket data; the settlement system includes a timing module, a settlement module and a secondary settlement module; the timing module is used to set the settlement time node and divide the ticket data according to the settlement time node; the settlement time node includes the ticket sales time and the ticket dispatch time; the settlement module is used to calculate the cost information based on the ticket data according to the preset settlement rules and generate a settlement order; The analysis system includes a settlement comparison module; the settlement comparison module is used to collect ticket change behaviors between settlement time nodes and update fee information based on the ticket change behaviors; the secondary settlement module is used to generate a secondary settlement order at the settlement time node based on the most recently updated fee information.

2. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The ticketing-related entities include offline ticketing platforms and online ticketing platforms.

3. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The preprocessing system also includes a pre-screening module; the pre-screening module is used to distinguish cash data from non-cash data in ticket data; wherein, when distinguishing ticket data, regular expressions are used to match and extract key fields in payment records, and the key fields include payment method and transaction amount.

4. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The preprocessing system also includes a risk identification module; an anomaly detection algorithm is provided in the risk identification module; the anomaly detection algorithm is used to identify abnormal transaction behaviors in ticketing data, and mark the corresponding ticketing data as risk data.

5. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The settlement system also includes an encryption module; the encryption module is used to encrypt data to perform confidential transmission of ticket data; the encryption module uses the SSL / TLS protocol for encrypted communication.

6. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The ticket changes include ticket changes, ticket refunds, and ticket purchases.

7. A centralized settlement system for regional ticket management according to claim 1, characterized in that: It also includes a storage system; the storage system adopts a distributed storage structure.

8. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The storage system also includes a database; the database is used to back up ticket data and fee information; the database uses a combination of ClickHouse and MySQL to synchronize and store data.

9. A centralized settlement system for regional ticket management according to claim 1, characterized in that: The settlement system also includes a report module; the report module is used to generate a cross-check report based on the cost information and a preset cross-check formula.

10. A centralized settlement method for regional ticket management, characterized in that: A centralized settlement system for regional ticket management according to any one of claims 1 to 9 is used to perform centralized settlement of regional tickets; the centralized settlement system comprises the following steps: The ticket data of each ticket-related entity is imported through the data collection system; the ticket data is preprocessed by the preprocessing module of the preprocessing system; the timing module of the settlement system sets the settlement time node and divides the ticket data according to the settlement time node; the settlement time node includes the ticket sales time and the ticket dispatch time; the settlement module of the settlement system calculates the fee information based on the ticket data according to the preset settlement rules and generates a settlement slip; The settlement comparison module of the analysis system collects ticket change behaviors between settlement time nodes and updates fee information based on the ticket change behaviors; the secondary settlement module of the settlement system generates a secondary settlement order at the settlement time node based on the most recently updated fee information.

Images