A tripartite settlement method and device for flight delay service
Through the three-party settlement method of flight delay service, the data state-driven settlement process and rigorous audit mechanism are used to solve the differences in settlement fees of flight delay service settlement fees and difficulty, and realize the settlement logic standard management and settlement process of flight delay service. Transparency.
Patent Information
- Application Number
- CN202011191435.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-10-30
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-10-30
AI Technical Summary
During the settlement process of flight delay service, the authorization form is inconsistent with the actual service execution, the settlement cycle is long, and the number of diversified service providers and agent airlines, resulting in differences in service settlement fees and difficulty in processing.
A three-party settlement method for flight delay service is proposed. Through the data state-driven settlement process, the data status of the settlement stage is recorded, and subsequent operations are triggered through the status change, a rigorous submission and review confirmation mechanism is established, and the settlement process is standardized, including the settlement to be confirmed, In the status of being submitted, being reviewed, being approved, being settled, etc., service reports and billing data are generated, and gradually reviewed and confirmed to form settlement tasks for suppliers and airlines.
It realizes the standardized management of settlement logic of flight delay services, reduces the difficulty of processing, ensures the transparency and accuracy of the settlement process, and reduces the differences in service settlement fees.
Smart Images

Figure CN112308517B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology, and in particular to a three-party settlement method and device for flight delay services. Background Art
[0002] At present, when making decisions on flight delay services, the airline usually informs the airport ground service agency to confirm, or the airport ground service agency takes the initiative to contact the airline for confirmation. If the airline has staff on site, the airport ground service agency needs to obtain the airline's authorization form (including service items and service quantities) with signatures and authorizations before contacting the service provider to perform the service; if the airline does not have staff on site, the airport ground service agency can only obtain the airline's non-written authorization, and then reissue the written service authorization form to the airline for confirmation after the service is completed.
[0003] In the actual implementation process, passengers may change their tickets, cancel their trips, or make other service requests, which may lead to inconsistencies between the authorization form signed in advance by the airline and the actual service implementation; when supplementing the authorization form afterwards, the service content of the service authorization form may not be confirmed due to untimely on-site communication; due to the long settlement cycle, the large number of delayed flights, the number of passengers involved and the complexity of service items, the service process is difficult to trace during settlement; the diversity of service providers and the large number of agency airlines often lead to the problem of contracts not being signed in time when they expire. The above problems will lead to differences in service settlement fees, making service settlement difficult to handle.
[0004] Therefore, it is necessary to provide a three-party settlement method for flight delay services for suppliers, airports and airlines, combining the service specifications in the flight delay management system with the delayed flight passenger service data. Summary of the invention
[0005] In view of this, the present invention provides a three-party settlement method and device for flight delay services, which is used to solve the problem that differences in service settlement fees will be caused in the existing settlement process, which brings difficulties to the service settlement work. The specific scheme is as follows:
[0006] A three-party settlement method for flight delay services, applied to suppliers, airports and airlines, comprising:
[0007] After the flight delay service is completed, a first review result of the service report and the supplier billing data is obtained, and when the first review result is that the review is completed, a service list and airline billing data are generated based on the service report;
[0008] Obtaining a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data;
[0009] When the preset settlement cycle is reached, the billing data of each supplier is summarized, a supplier settlement task is generated based on the billing data of each supplier, the supplier settlement task is sent to the corresponding supplier for confirmation, and the status of the corresponding supplier billing data is updated synchronously;
[0010] Send the supplier settlement task to the airport for review, synchronously update the corresponding supplier bill data, obtain the third review result of the supplier settlement task, and if the third review result is that the review is completed, summarize the bill data of each airline to trigger the generation of the airline settlement task, and obtain the fourth review result of the airline settlement task;
[0011] When the fourth review result is confirmed to be completed, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated.
[0012] Compared with the prior art, the present invention has the following advantages:
[0013] The present invention discloses a three-party settlement method for flight delay service, including: after the flight delay service is completed, when the service report and supplier billing data are reviewed, a service list and airline billing data are generated and confirmed by the airport, and the service list and airline billing data are sent to the airline for review; when the preset settlement cycle is reached, a supplier settlement task is generated based on the supplier billing data, and the supplier settlement task is sent to the corresponding supplier for confirmation; the supplier settlement task is sent to the airport for review, and when the review is completed, the airline billing data of each airline is summarized to generate an airline settlement task, and when the airport confirms the completion, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated. The above method realizes the standardized management of settlement and reduces the processing difficulty by the settlement logic between the airport, the airline and the supplier.
[0014] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0016] Figure 1 A flow chart of a three-party settlement method for a flight delay service disclosed in an embodiment of the present application;
[0017] Figure 2 Another flow chart of a three-party settlement method for a flight delay service disclosed in an embodiment of the present application;
[0018] Figure 3 Another flow chart of a three-party settlement method for a flight delay service disclosed in an embodiment of the present application;
[0019] Figure 4 This is a structural block diagram of a three-party settlement device for a flight delay service disclosed in an embodiment of the present application. DETAILED DESCRIPTION
[0020] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0021] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0022] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0023] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0024] The present invention discloses a three-party settlement method for flight delay service, which is applied between airports, airlines and suppliers. At present, when making flight delay service decisions, the airline generally informs the airport ground service agency to determine, or the airport ground service agency actively contacts the airline for confirmation. In the case that the airline has staff on site, the airport ground service agent needs to obtain the airline authorization form (including service items and service quantity) signed and authorized, and then contact the service provider to perform the service; if the airline has no staff on site, the airport ground service agent can only obtain the airline's non-written authorization, and reissue the written service authorization form to the airline for confirmation after the service is completed. In the actual implementation process, since passengers may change their tickets, cancel their itineraries or make other service demands, this will cause the authorization form signed in advance by the airline to be inconsistent with the actual service execution; when supplementing the authorization form afterwards, the service content of the service authorization form may not be confirmed due to untimely on-site communication; due to the long settlement cycle, the large number of delayed flights, the number of passengers involved and the complexity of service items, the service process is difficult to trace during settlement; the diversity of service providers, and the large number of agency airlines, often have the problem of not signing the contract in time when it expires. The above problems will cause differences in service settlement costs, which will bring processing difficulties to service settlement work. Based on the above problems, the present invention provides a three-party settlement method for flight delay services. The settlement method is driven by data status, splits the entire three-party service fee settlement process, uses different data statuses to record the stage of settlement, and triggers operation reminders for subsequent settlement links through data status changes. The present invention provides a complete and standard operating process for the delayed flight passenger service settlement involving suppliers, airports, and airlines, establishes a rigorous submission, review and confirmation mechanism, and standardizes the entire settlement process. Among them, the data status includes:
[0025] To be confirmed: During the service execution phase, service reports generated by scanning the service execution details recorded by the APP and not manually entered or modified, such service reports and the supplier bill data generated by their aggregation are in the status of To be confirmed;
[0026] To be submitted: During the service execution phase, service reports that are not generated through the APP system to record service execution details or are manually entered or modified, and the supplier bill data generated by the summary are all in the status of To be submitted. In addition, the service list data generated by the system and the airline bill data generated by the summary are all in the status of To be submitted;
[0027] Pending Review: During the report review stage, suppliers submit service reports and airports submit service lists. The status of the corresponding service reports, supplier billing data, service lists, and airline billing data are all pending review.
[0028] Failed review: During the report review stage, the submitted service report / service list is returned due to failure in review, and the status of the corresponding service report / service list, supplier billing data / airline billing data are all Failed review;
[0029] Approved: During the report / list review stage, the submitted service report / list is approved, and the status of the corresponding service report / list, supplier billing data / airline billing data are all approved;
[0030] To be settled: During the settlement task review stage, all approved supplier bill data / airline bill data associated with the supplier / airline settlement task will be marked as to be settled;
[0031] Settlement passed: During the settlement task review stage, if the supplier / airline settlement task is settled, all the supplier bill data and airline bill data in the pending settlement status associated with the settlement task will be marked as settled;
[0032] Settlement failed: During the settlement task review stage, if the supplier / airline settlement task fails, the user can mark one or more supplier bill data / airline bill data as settlement failed;
[0033] Delayed settlement: The supplier billing data / airline billing data in the supplier / airline settlement task will not be included in the settlement of the current month and will be delayed to the next billing date;
[0034] No settlement: The supplier bill data / airline bill data in the supplier / airline settlement task will never be included in the settlement.
[0035] The service report refers to a report generated with the supplier as the dimension, which summarizes the detailed data of all flight delay services performed by the supplier on a certain flight, wherein the detailed data includes: service flights, service items, passenger ticket numbers, boarding numbers, cabin classes, frequent flyer information, etc. The service report data includes: service flights, service items, service trips, service unit prices, etc.
[0036] The service list refers to a list generated based on a single flight, which summarizes the service report data of all suppliers of the flight.
[0037] The supplier bill data refers to expense bill data generated based on the supplier as the dimension, which is generated based on the service report statistics of the supplier for a certain flight, and includes the types of services provided, passenger accommodation service fees, crew accommodation service fees, passenger meal service fees, crew meal service fees, passenger car service fees, and crew car service fees.
[0038] The airline billing data refers to the expense billing data generated based on a single flight, which is generated based on the service list statistics of the flight, and includes the number of passengers served, the number of crew members served, passenger accommodation service fees, crew accommodation service fees, passenger meal service fees, crew meal service fees, passenger car service fees, and crew car service fees.
[0039] The supplier settlement task refers to the supplier's monthly settlement task, which is composed of all supplier bill data of the supplier within the settlement period and requires supplier confirmation and airport review.
[0040] The airline settlement task refers to the airline's monthly settlement task, which is composed of all airline billing data of the airline within the settlement period and requires airport confirmation and airline review.
[0041] In the embodiment of the present invention, the execution process of the settlement method is as follows: Figure 1 As shown, the steps include:
[0042] S101, after the flight delay service is completed, obtaining a first review result of the service report and the supplier billing data, and when the first review result is that the review is completed, generating a service list and airline billing data according to the service report;
[0043] In an embodiment of the present invention, after the flight delay service is completed, a service report and supplier billing data will be generated according to the service execution details of the supplier on the flight, wherein the supplier is at least one, and each supplier will correspond to a service report and supplier billing data. At this time, the initial status of the service report and the supplier billing data is to be confirmed, and the service report and the supplier billing data are sent to the corresponding supplier for review, and the current status of the service report and the supplier billing data is updated, wherein the current status is to be confirmed or to be submitted. If the current status is to be confirmed, when the first review result of the service report and the supplier billing data is completed, a service list and airline billing data are generated according to the service report, and at this time, the initial status of the service list and the airline billing data is to be submitted. If the current status is to be submitted, the service report and the supplier billing data are sent to the airport for review, and when the first review result of the service report and the supplier billing data is the review is completed, a service list and airline billing data are generated according to the service report, and at this time, the initial status of the service list and the airline billing data is to be submitted.
[0044] S102, obtaining a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data;
[0045] In an embodiment of the present invention, reviewing the service list and the airline billing data includes: reviewing the service list, synchronously updating the status of the airline billing data to pending review, obtaining a second review result, the airport obtaining the second review result, and self-reviewing the second review result. If the second review result is confirmed to be completed, the service list and the airline billing data are sent to the airline for review, and the status of the airline billing data is updated. The specific steps are as follows: obtaining the airline's review result of the service list, wherein the review result is passed or failed; if the review result is failed, updating the status of the airline billing data and returning to the airport for re-modification; if the review result is passed, updating the status of the airline billing data.
[0046] S103. When a preset settlement cycle is reached, the billing data of each supplier is aggregated, a supplier settlement task is generated based on the billing data of each supplier, the supplier settlement task is sent to the corresponding supplier for confirmation, and the status of the corresponding supplier billing data is synchronously updated;
[0047] In an embodiment of the present invention, the preset settlement cycle may be one week, one month, or one quarter, etc. In the implementation of the present invention, the preset settlement cycle is a certain day of the month. When the preset settlement cycle is reached, the bill data of each supplier is summarized, and a supplier settlement task is generated based on the bill data of each supplier. The supplier settlement task is sent to the corresponding supplier for confirmation. If there is data in the supplier settlement task whose status is to be confirmed, to be submitted, to be reviewed, or not passed, the status of the corresponding supplier bill data is synchronously updated to passed, wherein the specific update process is the same as the review process of the service report and the supplier bill data in S101, and will not be repeated here; if there is data in the supplier settlement task whose corresponding supplier bill data status is not passed, if the supplier can set it to delayed settlement or not settled, the status of the corresponding supplier bill data is synchronously updated to delayed settlement or not settled; if the status of all supplier bill data associated with the supplier settlement task is to be settled, not passed settlement, delayed settlement, or not settled, the supplier settlement task is submitted to the airport for review, and the supplier bill data with the status of passed review and not passed settlement is synchronously updated to the status to be settled.
[0048] S104, sending the supplier settlement task to the airport for review, synchronously updating the corresponding supplier billing data, obtaining a third review result of the supplier settlement task, and if the third review result is that the review is completed, aggregating the billing data of each airline to trigger the generation of an airline settlement task, and obtaining a fourth review result of the airline settlement task;
[0049] In an embodiment of the present invention, the supplier settlement task is sent to the airport for review. If the operation of some supplier bill data of the airport supplier settlement task is settlement failure, the corresponding data status is synchronously updated to settlement failure, and the supplier settlement task is returned to the supplier for processing; if the airport operates the supplier settlement task as settlement passing, the status of the supplier bill data to be settled associated with the task is synchronously updated to settlement passing, and the review of a single supplier bill is completed. The third review result of the supplier settlement task is obtained, wherein the third review result is the review result of the supplier bills of each supplier. If the third review result is review completion, the status of the airline bill data with delayed settlement status in the current settlement cycle is updated to review passing, and participates in the airline settlement task; if the current supplier has unprocessed airline settlement tasks, the airline bill data with data status that meets the requirements from the previous settlement date to the day before the current settlement date is summarized to participate in the airline settlement task; if the current supplier does not have unprocessed airline settlement tasks, the airline bill data with data status that meets the requirements before the current settlement date is summarized and settled to participate in the airline settlement task.
[0050] The airport reviews the airline settlement task, modifies and submits the airline settlement task, and simultaneously updates the status of the airline bill data to obtain a fourth review result.
[0051] S105. When the fourth review result is confirmed to be completed, the airline settlement task is sent to the airline for review, and the status of the corresponding airline bill data is synchronously updated.
[0052] In the embodiment of the present invention, when the fourth review result is confirmed to be completed, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated, wherein the status is settlement passed or settlement failed.
[0053] The present invention discloses a three-party settlement method for flight delay service, including: after the flight delay service is completed, when the service report and supplier billing data are reviewed, a service list and airline billing data are generated and confirmed by the airport, and the service list and airline billing data are sent to the airline for review; when the preset settlement cycle is reached, a supplier settlement task is generated based on the supplier billing data, and the supplier settlement task is sent to the corresponding supplier for confirmation; the supplier settlement task is sent to the airport for review, and when the review is completed, the airline billing data of each airline is summarized to generate an airline settlement task, and when the airport confirms the completion, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated. The above method realizes the standardized management of settlement and reduces the processing difficulty by the settlement logic between the airport, the airline and the supplier.
[0054] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0055] In the embodiment of the present invention, an example is given based on the above-mentioned settlement method, and the service execution detail data is automatically recorded by scanning boarding passes and other means; when the flight delay service guarantee is completed, a service report is generated based on the recorded service execution details and provided to the supplier and the airport for confirmation and review, and the supplier billing data is generated simultaneously; after the service report review is completed, a corresponding service list is generated for the airport and the airline to confirm and review, and the airline billing data is generated simultaneously; based on the supplier billing data and the airline billing data within the settlement scope, the supplier settlement tasks and the airline settlement tasks are generated respectively, and the confirmation, submission and review of the billing tasks are completed by the supplier, the airport and the airline to complete the entire settlement process. The specific execution process is as follows: Figure 2 As shown, the following steps are included:
[0056] Step 1. After the flight delay service is completed, a service report and supplier bill data will be generated based on the supplier's service execution details for the flight. At this time, the initial status of the service report and supplier bill data is both pending confirmation;
[0057] Step 2. If the supplier has any objection to the service report, he can manually modify or increase the quantity of the service items provided in the service report. After the operation is saved, the service report is changed to pending submission, and the supplier bill data is updated according to the modified content of the service report, and the status of the supplier bill data is simultaneously updated to pending submission;
[0058] Step 3. The supplier submits the service report to the airport, and the status of the supplier's billing data is updated synchronously;
[0059] In the embodiment of the present invention, the specific execution process of step 3 is as follows:
[0060] Step 3.1. If the supplier bill data status is pending confirmation, the supplier submits the service report for review, and the supplier bill data status is synchronously updated to approved, completing the automatic review of the service report and proceeding to step 5;
[0061] Step 3.2. If the supplier bill data status is pending submission, the supplier submits the service report for review, and the supplier bill data status is synchronously updated to pending review. The review task is transferred to the airport and proceed to step 4.
[0062] Step 4. The airport reviews the service quantity of the passenger type corresponding to the service item in the service report to be reviewed, and simultaneously updates the status of the supplier bill data;
[0063] In the embodiment of the present invention, the execution process of step 4 is as follows:
[0064] Step 4.1. If the airport fails to approve the service report, the supplier's bill data status will be updated to "failed to approve" and the service report will be returned to the supplier for modification, and the process will return to step 2.
[0065] Step 4.2. If the airport approves the service report, the supplier bill data status is synchronously updated to approved, completing the review of the supplier service report task and proceeding to step 5.
[0066] Step 5. When all suppliers' service reports are reviewed, the system automatically generates a service list and airline bill data based on all service reports of the flight by flight ID, service item, passenger type, total number of service personnel and service amount. At this time, the initial status of the airline bill data is to be submitted;
[0067] Step 6. If the airport has any objection to the service list, it can manually modify the quantity of service items provided in the service list. After the operation is submitted to the airline for review, the service list is changed to pending review, and the airline billing data is updated according to the modified content of the service list, and the airline billing data status is simultaneously updated to pending review;
[0068] Step 7. The airline reviews the service list to be reviewed and simultaneously updates the status of the airline's billing data;
[0069] In the embodiment of the present invention, the execution process of step 7 is as follows:
[0070] Step 7.1. If the airline fails to approve the service list, the airline bill data status is synchronously updated to "failed to approve", the service list is returned to the airport for modification, and the process returns to step 6;
[0071] Step 7.2. If the airline approves the service list, the airline billing data status is synchronously updated to approved, completing the review of the flight service list task and proceeding to step 8.
[0072] The specific execution process for steps 1 to 7 is as follows: Figure 3 As shown, first determine whether the flight delay service guarantee is completed. If not, end directly. If so, generate a service report and supplier billing data. The supplier submits the service report and determines whether the data status is pending confirmation. If not, feedback is given to the airport for review. If the review fails, the supplier modifies the service report. If so, determine whether all suppliers have completed the review. If not, wait for other suppliers' service reports to be submitted. If so, generate a service list and airline billing data. The airport submits the service list to the airline for review. If the review fails, return to the airport for modification. If the review passes, end.
[0073] Step 8. Summarize supplier billing data regularly according to the preset billing date and trigger the generation of supplier settlement tasks;
[0074] In the embodiment of the present invention, the execution process of step 8 is as follows:
[0075] Step 8.1. Update the supplier bill data with delayed settlement status in the historical settlement cycle to approved and participate in the settlement of this settlement cycle;
[0076] Step 8.2. If there are unprocessed supplier settlement tasks, this supplier settlement task will summarize and associate the supplier bill data whose data status meets the requirements from the previous settlement date to the day before this settlement date, including pending confirmation, pending submission, pending review, failed review, and passed review;
[0077] Step 8.3. If there is no unprocessed supplier settlement task for the supplier, this supplier settlement task will summarize and associate the supplier bill data whose data status meets the requirements before this settlement date, including pending confirmation, pending submission, pending review, failed review, and passed review status.
[0078] Step 9. The supplier operates to modify and submit the supplier settlement task, and simultaneously updates the status of the supplier bill data;
[0079] In the embodiment of the present invention, the execution process of step 9 is as follows:
[0080] Step 9.1. If the supplier bill data status of the supplier settlement task is pending confirmation, pending submission, pending review, or failed review, the supplier bill data status can be synchronously updated to passed review through steps 2-4;
[0081] Step 9.2. If the supplier bill data status of the supplier settlement task is "settlement failed", the supplier can set it as delayed settlement, and the corresponding data status will be synchronously updated to delayed settlement;
[0082] Step 9.3. If the supplier bill data status of the supplier settlement task is "settlement failed", the supplier can set it to "not settled", and the corresponding data status will be synchronously updated to "not settled";
[0083] Step 9.4. The status of all supplier bill data associated with the supplier settlement task is pending settlement, settlement failed, delayed settlement, and not settled. The supplier can submit the supplier settlement task to the airport for review. All supplier bill data with status of review passed and settlement failed will be synchronously updated to pending settlement status and proceed to step 10.
[0084] Step 10. The airport reviews the supplier settlement tasks submitted by the supplier and simultaneously updates the status of the supplier bill data;
[0085] In the embodiment of the present invention, the execution process of step 10 is as follows:
[0086] Step 10.1. If the airport fails to settle some of the supplier bill data in the supplier settlement task, the corresponding data status is synchronously updated to settlement failure, and the supplier settlement task is returned to the supplier for processing, and the process returns to step 9;
[0087] Step 10.2. If the airport's operation on the supplier settlement task is settlement passed, the data status of the supplier bill to be settled associated with the task will be synchronously updated to settlement passed, completing the review of the single supplier bill and proceeding to step 11.
[0088] Step 11. After all supplier settlement tasks are settled, summarize the airline billing data and trigger the generation of airline settlement tasks;
[0089] In the embodiment of the present invention, the execution process of step 11 is as follows:
[0090] Step 11.1. Update the airline billing data with delayed settlement status in the historical settlement cycle to the approved status and participate in the settlement of this settlement cycle;
[0091] Step 11.2. If the supplier has unprocessed airline settlement tasks, this airline settlement task will summarize and associate the airline bill data whose data status meets the requirements from the previous settlement date to the day before this settlement date, including pending confirmation, pending submission, pending review, failed review, and passed review;
[0092] Step 11.3. If the supplier has no unprocessed airline settlement tasks, the airline billing data will be aggregated and associated with the airline billing data whose data status meets the requirements before this settlement date, including pending confirmation, pending submission, pending review, failed review, and passed review status.
[0093] Step 12. The airport operation modifies and submits the airline settlement task, and simultaneously updates the status of the airline billing data;
[0094] In the embodiment of the present invention, the execution process of step 12 is as follows:
[0095] Step 12.1. If the airline billing data status of the airline settlement task is pending confirmation, pending submission, pending review, or unapproved, the airline billing data status can be synchronously updated to approved through steps 6-7;
[0096] Step 12.2. If the airline billing data status of the airline settlement task is set as settlement failure, the airport can set it as delayed settlement, and the corresponding data status will be synchronously updated to delayed settlement;
[0097] Step 12.3. If the airline billing data status of the airline settlement task is not settled, the airport can set it to not settle, and the corresponding data status will be synchronously updated to not settle;
[0098] Step 12.4. The status of all airline billing data associated with the airline settlement task is pending settlement, settlement failed, delayed settlement, and not settled. The airport can submit the airline settlement task to the airline for review. All supplier billing data with status of review passed and settlement failed will be synchronously updated to pending settlement status and proceed to step 13.
[0099] Step 13. The airline reviews the airline settlement tasks submitted by the airport and simultaneously updates the status of the airline billing data.
[0100] In the embodiment of the present invention, the execution process of step 13 is as follows:
[0101] Step 13.1. If the airline fails to settle part of the airline bill data of the airline settlement task, the corresponding data status is synchronously updated to settlement failure, and the airline settlement task is returned to the airport for processing, and the process returns to step 12;
[0102] Step 13.2. If the airline's operation on the airline settlement task is settlement passed, the status of the airline bill data to be settled associated with the task is synchronously updated to settlement passed, completing the review of the single airline bill.
[0103] Although operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.
[0104] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.
[0105] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).
[0106] In the embodiment of the present invention, based on the above-mentioned three-party settlement method for flight delay service, the embodiment of the present invention also provides a three-party settlement device for flight delay service, which is applied to suppliers, airports and airlines. The structural block diagram of the settlement device is as follows: Figure 4 As shown, including:
[0107] Review and generation module 201 , acquisition and review module 202 , generation and review module 203 , review and summary module 204 and review and update module 205 .
[0108] in,
[0109] The review and generation module 201 is used to obtain a first review result of the service report and supplier billing data after the flight delay service is completed, and when the first review result is that the review is completed, generate a service list and airline billing data based on the service report;
[0110] The acquisition and review module 202 is used to obtain a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, send the service list and the airline billing data to the airline for review, and update the status of the airline billing data;
[0111] The generation and review module 203 is used to summarize the billing data of each supplier when a preset settlement cycle is reached, generate a supplier settlement task based on the billing data of each supplier, send the supplier settlement task to the corresponding supplier for confirmation, and synchronously update the status of the corresponding supplier billing data;
[0112] The review and summary module 204 is used to send the supplier settlement task to the airport for review, synchronously update the corresponding supplier billing data, obtain the third review result of the supplier settlement task, and if the third review result is that the review is completed, summarize the billing data of each airline to trigger the generation of the airline settlement task, and obtain the fourth review result of the airline settlement task;
[0113] The review and update module 205 is used to send the airline settlement task to the airline for review and simultaneously update the status of the corresponding airline bill data when the fourth review result is confirmed to be completed.
[0114] The present invention discloses a tripartite settlement device for flight delay service, comprising: after the flight delay service is finished, when the service report and supplier billing data are reviewed, a service list and airline billing data are generated, and when the airport confirms the completion, the service list and airline billing data are sent to the airline for review; when the preset settlement cycle is reached, a supplier settlement task is generated based on the supplier billing data, and the supplier settlement task is sent to the corresponding supplier for confirmation; the supplier settlement task is sent to the airport for review, and when the review is completed, the airline billing data of each airline is summarized to generate an airline settlement task, and when the airport confirms the completion, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated. The above device, with the settlement logic between the airport, the airline and the supplier, realizes the standardized management of the settlement and reduces the processing difficulty.
[0115] In the embodiment of the present invention, the review and generation module 201 includes:
[0116] The first review and update unit 206 , the first review and generation unit 207 , and the second review and generation unit 208 .
[0117] in,
[0118] The first review and update unit 206 is used to obtain the service report and the supplier bill data, send the service report and the supplier bill data to the corresponding supplier for confirmation, and update the current status of the service report and the supplier bill data, wherein the current status is pending confirmation or pending submission;
[0119] The first review and generation unit 207 is used to generate a service list and airline billing data according to the service report when the service report and the supplier billing data are reviewed and completed if the current status is pending confirmation.
[0120] The second review and generation unit 208 is used to send the service report and the supplier billing data to the airport for review if the current status is to be submitted. When the review of the service report and the supplier billing data is completed, a service list and airline billing data are generated based on the service report.
[0121] In the embodiment of the present invention, the acquisition and review module 202 includes:
[0122] An acquisition unit 209 , a first updating unit 210 , and a second updating unit 211 .
[0123] in,
[0124] The acquisition unit 209 is used to acquire the audit result of the airline on the service list, wherein the audit result is passed or failed;
[0125] The first updating unit 210 is used to update the status of the airline bill data and return to the airport for re-modification if the audit result is failure to pass the audit;
[0126] The second updating unit 211 is used to update the status of the airline bill data if the audit result is passed.
[0127] In the embodiment of the present invention, the generation and review module 203 includes:
[0128] The third updating unit 212 , the fourth updating unit 213 and the second review and updating unit 214 .
[0129] in,
[0130] The third updating unit 212 is used to synchronously update the status of the corresponding supplier bill data to approved if the status of the supplier bill data in the supplier settlement task is to be confirmed, to be submitted, to be reviewed, or to be rejected;
[0131] The fourth updating unit 213 is used to update the status of the corresponding supplier bill data to delayed settlement or non-settlement synchronously if the supplier settlement task has corresponding supplier bill data whose status is data of settlement failure, and if the supplier can set it to delayed settlement or non-settlement
[0132] The second review and update unit 214 is used to submit the supplier settlement task to the airport for review if the status of all supplier bill data associated with the supplier settlement task is pending settlement, settlement failed, delayed settlement, or not settled, and to synchronously update the supplier bill data with the status of review passed and settlement failed to the pending settlement status.
[0133] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a unit does not limit the unit itself in some cases. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses".
[0134] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0135] According to one or more embodiments of the present disclosure, a three-party settlement method for flight delay service is provided, which is applied to suppliers, airports and airlines, and the method includes:
[0136] After the flight delay service is completed, a first review result of the service report and the supplier billing data is obtained, and when the first review result is that the review is completed, a service list and airline billing data are generated based on the service report;
[0137] Obtaining a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data;
[0138] When the preset settlement cycle is reached, the billing data of each supplier is summarized, a supplier settlement task is generated based on the billing data of each supplier, the supplier settlement task is sent to the corresponding supplier for confirmation, and the status of the corresponding supplier billing data is updated synchronously;
[0139] Send the supplier settlement task to the airport for review, synchronously update the corresponding supplier bill data, obtain the third review result of the supplier settlement task, and if the third review result is that the review is completed, summarize the bill data of each airline to trigger the generation of the airline settlement task, and obtain the fourth review result of the airline settlement task;
[0140] When the fourth review result is confirmed to be completed, the airline settlement task is sent to the airline for review, and the status of the corresponding airline billing data is synchronously updated.
[0141] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0142] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0143] For the convenience of description, the above device is described as being divided into various units according to their functions. Of course, when implementing the present invention, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0144] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present invention or certain parts of the embodiments.
[0145] The above is a detailed introduction to the three-party settlement method and device for a flight delay service provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as limiting the present invention.
Claims
1. A three-party settlement method for flight delay services, characterized in that: Applicable to suppliers, airports and airlines, the method includes: After the flight delay service is completed, a first review result of the service report and the supplier billing data is obtained, and when the first review result is that the review is completed, a service list and airline billing data are generated based on the service report; Obtaining a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data; When the preset settlement cycle is reached, the billing data of each supplier is summarized, a supplier settlement task is generated based on the billing data of each supplier, the supplier settlement task is sent to the corresponding supplier for confirmation, and the status of the corresponding supplier billing data is updated synchronously; Send the supplier settlement task to the airport for review, synchronously update the corresponding supplier bill data, obtain the third review result of the supplier settlement task, and if the third review result is that the review is completed, summarize the bill data of each airline to trigger the generation of the airline settlement task, and obtain the fourth review result of the airline settlement task; When the fourth review result is confirmed to be completed, the airline settlement task is sent to the airline for review, and the status of the corresponding airline bill data is updated synchronously; The first audit result of the service report and the supplier bill data is obtained, and when the first audit result is that the audit is completed, a service list and airline bill data are generated according to the service report, including: Obtaining service reports and supplier billing data, sending the service reports and supplier billing data to corresponding suppliers for review, and updating the current status of the service reports and supplier billing data, wherein the current status is pending confirmation or pending submission; If the current status is pending confirmation, when the service report and the supplier billing data are reviewed, a service list and airline billing data are generated based on the service report; If the current status is to be submitted, the service report and the supplier billing data are sent to the airport for review. When the review of the service report and the supplier billing data is completed, a service list and airline billing data are generated based on the service report; Wherein, obtaining a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data, includes: The service list is reviewed, and the status of the airline billing data is simultaneously updated to pending review, and a second review result is obtained. The airport obtains the second review result, and performs a self-review on the second review result. If the second review result is confirmed to be completed, the service list and the airline billing data are sent to the airline for review, and the status of the airline billing data is updated.
2. The method according to claim 1, characterized in that Sending the service list and the airline billing data to the airline for review, and updating the status of the airline billing data, including: Obtaining the airline's review result on the service list, wherein the review result is passed or failed; If the audit result is failure, the status of the airline bill data is updated and returned to the airport for re-modification; If the audit result is passed, the status of the airline bill data is updated.
3. The method according to claim 1, characterized in that Send the supplier settlement task to the corresponding supplier for confirmation, and simultaneously update the status of the corresponding supplier bill data, including: If there is supplier bill data in the supplier settlement task whose status is to be confirmed, to be submitted, to be reviewed, or not passed, the status of the corresponding supplier bill data will be synchronously updated to passed; If the supplier settlement task has corresponding supplier bill data whose status is settlement failed, and if the supplier can set it to delayed settlement or non-settlement, the status of the corresponding supplier bill data is synchronously updated to delayed settlement or non-settlement; If the status of all supplier bill data associated with the supplier settlement task is pending settlement, settlement failed, delayed settlement, or not settled, the supplier settlement task will be submitted to the airport for review, and the supplier bill data with the status of review passed and settlement failed will be synchronously updated to the pending settlement status.
4. The method according to claim 1, characterized in that: Aggregate the billing data of each airline to trigger the generation of airline settlement tasks, including: Update the status of the airline billing data with delayed settlement status in the current settlement cycle to approved, and participate in the settlement task of the airline; If the current supplier has unprocessed airline settlement tasks, the airline bill data with data status that meets the requirements from the last settlement date to the day before the current settlement date shall be aggregated to participate in the airline settlement task; If the current supplier has no unprocessed airline settlement tasks, the airline billing data whose data status meets the requirements before the current settlement date will be summarized and settled to participate in the airline settlement task.
5. The method according to claim 1, characterized in that Also includes: An initial status is assigned to the service report, the vendor billing data, the vendor bill number, the service list, the airline billing data, and the airline billing data.
6. A tripartite settlement device for flight delay services, characterized in that: Applied to suppliers, airports and airlines, the device includes: The review and generation module is used to obtain a first review result of the service report and the supplier billing data after the flight delay service is completed, and when the first review result is that the review is completed, generate a service list and airline billing data according to the service report; an acquisition and review module, configured to acquire a second review result of the service list and the airline billing data, and if the second review result is confirmation completion, send the service list and the airline billing data to the airline for review, and update the status of the airline billing data; A generation and review module is used to summarize the billing data of each supplier when a preset settlement cycle is reached, generate a supplier settlement task based on the billing data of each supplier, send the supplier settlement task to the corresponding supplier for confirmation, and synchronously update the status of the corresponding supplier billing data; The review and summary module is used to send the supplier settlement task to the airport for review, synchronously update the corresponding supplier billing data, obtain the third review result of the supplier settlement task, and if the third review result is that the review is completed, summarize the billing data of each airline to trigger the generation of the airline settlement task, and obtain the fourth review result of the airline settlement task; A review and update module, configured to send the airline settlement task to the airline for review and synchronously update the status of the corresponding airline bill data when the fourth review result is confirmed to be completed; Wherein, the review and generation module includes: A first review and update unit, configured to obtain a service report and supplier bill data, send the service report and supplier bill data to a corresponding supplier for review, and update a current status of the service report and supplier bill data, wherein the current status is pending confirmation or pending submission; A first review and generation unit, configured to generate a service list and airline billing data according to the service report when the review of the service report and the supplier billing data is completed if the current status is pending confirmation; A second review and generation unit is used to send the service report and the supplier billing data to the airport for review if the current status is to be submitted, and generate a service list and airline billing data according to the service report when the review of the service report and the supplier billing data is completed; The acquisition and review module is specifically used for: The service list is reviewed, and the status of the airline billing data is simultaneously updated to pending review, and a second review result is obtained. The airport obtains the second review result, and performs a self-review on the second review result. If the second review result is confirmed to be completed, the service list and the airline billing data are sent to the airline for review, and the status of the airline billing data is updated.
7. The device according to claim 6, characterized in that The acquisition and review module includes: An acquisition unit, configured to acquire a review result of the service list by the airline, wherein the review result is a pass or a fail; A first updating unit, for updating the status of the airline bill data and returning to the airport for re-modification if the audit result is a failure to pass the audit; The second updating unit is used to update the status of the airline bill data if the audit result is passed.
8. The device according to claim 6, characterized in that The generation and review module includes: The third updating unit is used to synchronously update the status of the corresponding supplier bill data to approved if the supplier bill data in the supplier settlement task is in the status of pending confirmation, pending submission, pending review, or data that has not passed the review; A fourth updating unit is used for, if the supplier settlement task has corresponding supplier bill data whose status is data of settlement failure, and if the supplier can set it as delayed settlement or non-settlement, then the status of the corresponding supplier bill data is synchronously updated to delayed settlement or non-settlement; The second review and update unit is used to submit the supplier settlement task to the airport for review if the status of all supplier bill data associated with the supplier settlement task is pending settlement, settlement failed, delayed settlement, or not settled, and to synchronously update the supplier bill data with the status of review passed and settlement failed to the pending settlement status.
