Difference check device, difference check method, and difference check program
The difference checking device improves CASS settlement efficiency by automating the comparison of MAWB fee data with CASS data, enabling rapid identification and resolution of discrepancies.
Patent Information
- Application Number
- JP2022104452
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-06-29
- Publication Date
- 2025-09-25
- Estimated Expiration
- 2042-06-29
AI Technical Summary
Existing CASS settlement operations are inefficient due to the complexity of matching airfare data with transaction data, requiring manual checks and inability to identify discrepancies quickly.
A difference checking device equipped with a control unit that inputs and compares MAWB fee data with CASS data, identifying mismatches and calculating Net WT/CHG, and outputs a report to streamline settlement operations.
Enhances the efficiency of CASS settlement operations by quickly identifying and resolving discrepancies, reducing manual effort and improving data matching accuracy.
Smart Images

Figure 0007744304000001 
Figure 0007744304000002 
Figure 0007744304000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a difference checking device, a difference checking method, and a difference checking program. [Background technology]
[0002] For example, there is a system called CASS (Cargo Accounts Settlement System) for settling airfares between purchasers and airlines. By introducing CASS, airlines can settle all payments together through CASS without having to create individual invoices for each purchaser. Purchasers do not receive individual invoices from each airline, but receive a consolidated invoice through CASS. Purchasers then check the invoice against transaction data they manage in-house before making payments, a process known as "CASS settlement operations." For example, Patent Document 1 discloses a conventional system that uses CASS. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-244198 Summary of the Invention [Problem to be solved by the invention]
[0004] However, Patent Document 1 does not mention anything about improving the efficiency of CASS settlement operations.
[0005] The present invention has been made in consideration of the above, and aims to provide a difference checking device, a difference checking method, and a difference checking program that can make CASS settlement operations more efficient. [Means for solving the problem]
[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a difference checking device equipped with a control unit and configured to be able to communicate data with a CASS (Cargo Accounts Settlement System) via a network, wherein the control unit is characterized by comprising: an input means for inputting MAWB (Master Air Waybill) fee data for a target airline and storing it in a memory unit; an import means for downloading CASS data, which is billing data uploaded to the CASS by the target airline, from the CASS and storing it in the memory unit; and a comparison means for comparing the MAWB fee data stored in the memory unit with the CASS data and outputting a report of the comparison results.
[0007] According to one aspect of the present invention, the MAWB fee data includes MAWB NO, Date of Issue, IATA WT / CHG, Commission, Net WT / CHG, and Due Carrier, and the CASS data includes MAWB NO, IATA WT / CHG, Commission, Incentive, Due Carrier, import year and month, and first or second half term, and the matching means may match the MAWB fee data and the CASS data on a MAWB NO unit.
[0008] Furthermore, according to one aspect of the present invention, if at least one of the Net WT / CHG and Due Carrier for the MAWB fee data and the CASS data does not match, the matching means may determine that there is a mismatch, and calculate the Net WT / CHG of the CASS data as Net WT / CHG = IATA WT / CHG - Commission - Incentive.
[0009] According to another aspect of the present invention, the collating means may determine that there is no data if the Date of Issue of the MAWB fee data does not match the import date and term of the CASS data.
[0010] Furthermore, according to one aspect of the present invention, the matching means may be configured such that an operator can specify MAWB fee data or CASS data as the output main data on the extraction condition specification screen, and output a report of the matching results based on the specified data.
[0011] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a difference checking method executed by an information processing device equipped with a control unit and configured to be able to communicate data with a CASS (Cargo Accounts Settlement System) via a network, characterized in that it includes an input process executed by the control unit, in which MAWB (Master Air Waybill) fee data for a target airline is input and stored in a memory unit, an import process executed by the control unit, in which CASS data, which is billing data uploaded to the CASS by the target airline, is downloaded from the CASS and stored in the memory unit, and a comparison process in which the MAWB fee data stored in the memory unit is compared with the CASS data and a report of the comparison result is output.
[0012] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a difference check program to be executed by an information processing device having a control unit and configured to be able to communicate data with a CASS (Cargo Accounts Settlement System) via a network, the difference check program executing the following steps in the control unit: an input process of inputting MAWB (Master Air Waybill) data for a target airline and storing it in a memory unit; an import process of downloading CASS data, which is billing data uploaded to the CASS by the target airline, from the CASS and storing it in the memory unit; and a comparison process of comparing the MAWB fee data stored in the memory unit with the CASS data and outputting a report of the comparison results. [Effects of the Invention]
[0013] According to the present invention, it is possible to improve the efficiency of CASS settlement operations. [Brief explanation of the drawings]
[0014] [Figure 1] FIG. 1 is a diagram for explaining the mechanism of a conventional CASS settlement process. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the difference checking device according to this embodiment. [Figure 3] FIG. 3 is a flow chart showing an example of the overall processing of the control unit of the difference checking device according to this embodiment. [Figure 4] FIG. 4 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the difference checking device according to this embodiment. [Figure 5] FIG. 5 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the difference checking device according to this embodiment. [Figure 6] FIG. 6 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the amount difference checking device according to this embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the amount difference checking device according to this embodiment. [Figure 8] FIG. 8 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the difference checking device according to this embodiment. [Figure 9] FIG. 9 is a diagram showing sample data for explaining a specific example of the processing of the control unit of the difference checking device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0015] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.
[0016] [1. Overview] For example, there is a system called CASS (Cargo Accounts Settlement System) that is used to settle airfares between purchasers and airlines. By introducing CASS, airlines can settle all payments together through CASS without having to create individual invoices for each purchaser. Purchasers do not receive individual invoices from each airline, but receive a consolidated invoice through CASS. Purchasers then compare this with the transaction data they manage in-house before making payments, a process known as "CASS settlement."
[0017] However, CASS settlement work has traditionally been carried out using Excel, PDF, etc., but it is necessary to carry out CASS settlement work twice a month, divided into the first half (1st to 15th) and the second half (16th to the end of the month), and the billing base dates differ depending on the airline, and calculations are complicated due to special pricing unique to the industry, making it difficult to match with transaction data.
[0018] Therefore, in this embodiment, the results of matching transaction data (MAWB fee data) with CASS data (billing data) can be confirmed in a report (Cass Report), making it possible to quickly identify cases where there is a mismatch and need to be confirmed, thereby streamlining CASS settlement operations.
[0019] In addition, CASS settlement work is often carried out by accounting staff, and in the past, even if a discrepancy was identified, accounting was unable to identify the cause, forcing them to contact the site to confirm and make corrections.However, by importing transaction data, it has become possible to easily perform advance checks on site.
[0020] Figure 1 is a diagram explaining the mechanism of conventional CASS settlement operations. The mechanism of conventional CASS settlement operations will be explained with reference to Figure 1. The purchaser inputs the MAWB (Master Air Waybill), stores it in a file as transaction data (cost data), and also outputs a transportation request to an airline (for example, airlines A, B, and C). The MAWB (Master Air Waybill) is an air waybill that lists the airfare and surcharge to be paid to the airline.
[0021] When an airline receives a transportation request, it carries out the transportation and uploads billing data based on the transportation results to CASS.
[0022] The client downloads CASS data (billing data) from CASS twice a month in file formats such as PDF, CSV, and Excel. The CASS data is divided into two halves based on the MAWB issue date; the first half covers the 1st to 15th days, and the second half covers the 16th to 31st days.
[0023] The purchaser compares the transaction data (cost data) with the CASS data. Specifically, the purchaser checks whether (1) the fees match on a MAWB basis, and (2) the issue dates match on a MAWB basis.
[0024] If the verification result is a match (○), the purchaser will carry out the payment process. If the verification result is a mismatch (×), the purchaser will check the transaction data or make an inquiry to the airline.
[0025] The difference checking device of this embodiment is widely applicable to industries that handle air cargo and have introduced "CASS" for settlement with airlines.
[0026] [2. Configuration] An example of the configuration of the balance checking device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the balance checking device 100.
[0027] The balance checking device 100 is, for example, a commercially available desktop personal computer. Note that the balance checking device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.
[0028] The difference checking device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the difference checking device 100 is connected to each other so that they can communicate with each other via any communication path.
[0029] The communication interface unit 104 communicatively connects the difference check device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of exchanging data with other devices via the communication line. Here, the network 300 has a function of communicatively connecting the difference check device 100 with the server 200, airline systems 400, CASS 500, etc., and is, for example, the Internet or a local area network (LAN). The airline systems 400, for example, are systems of airlines A, B, C, etc., and are configured to communicate data with the difference check device 100 via the network 300. The CASS 500 is configured to communicate data with the difference check device 100 via the network 300, and billing data is uploaded from the airlines. The difference check device 100 is configured to download CASS data (billing data) from the CASS 500 in file formats such as PDF, CSV, and Excel.
[0030] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. Note that, hereinafter, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Displaying information on the monitor 114 and the user operating the input device 112 may be referred to as a "user operation via a UI."
[0031] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 may be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The storage unit 106 includes a transaction data file 106a, a CASS data file 106b, etc.
[0032] The transaction data file 106a is a file for storing MAWB fee data. The MAWB fee data may include MAWB No., Date of Issue, IATA WT / CHG (public fare), Commission, Net WT / CHG (fare paid to airlines), and Due Carrier (surcharge paid to airlines).
[0033] The CASS data file 106b is a file for storing CASS data. The CASS data may include MAWB NO, IATA WT / CHG, Commission, Incentive, Due Carrier, import date, and Term. The proportions of "Commission" and "Incentive" vary depending on the airline.
[0034] Returning to Figure 2, the control unit 102 is a CPU or the like that performs overall control of the difference checking device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.
[0035] The control unit 102 is configured to be able to access the transaction data file 106a, the CASS data file 106b, etc. stored in the memory unit 106. The transaction data file 106a and the CASS data file 106b may be provided in another location (e.g., the server 200) as long as the control unit 102 is able to access them.
[0036] The control unit 102 conceptually includes a MAWB input unit 102a, a CASS data acquisition unit (acquisition unit) 102b, a collating unit 102c, and a screen display control unit 102d.
[0037] The MAWB input unit 102a, for example, submits a transportation request from the website of the airline system 400 of the target airline (e.g., airlines A, B, and C), and inputs MAWB (Master Air Waybill) fee data, which is then stored in the transaction data file 106a.
[0038] The CASS data acquisition unit 102b downloads the CASS data, which is billing data uploaded to the CASS 500 by the target airline, from the CASS 500 and stores it in the CASS data file 106b.
[0039] The collation unit 102c collates the MAWB fee data stored in the transaction data file 106a with the CASS data stored in the CASS data file 106b, and outputs (displays and / or prints) a report of the collation results.
[0040] The collation unit 102c may collate the MAWB fee data and the CASS data on a MAWB No. basis. If at least one of the fees (Net WT / CHG and Due Carrier) does not match, the collation unit 102c may determine that there is a mismatch, and calculate the Net WT / CHG of the CASS data as Net WT / CHG = IATA WT / CHG - Commission - Incentive. The collation unit 102c may also collate dates, and if the Date of Issue of the MAWB fee data does not match the import year, month, and term of the CASS data, may determine that there is no data.
[0041] Furthermore, the matching unit 102c may match the MAWB fee data with the CASS data and output a report of the matching results, for example, in accordance with extraction conditions specified by the operator on an extraction condition specification screen displayed on the monitor 114. In this case, the operator may be able to specify the MAWB fee data or the CASS data as the output main data on the extraction condition specification screen, and a report of the matching results may be output using the specified MAWB fee data or the CASS data as the basis.
[0042] The screen display control unit 102d controls the display of various screens (for example, extraction condition specification screens) displayed on the monitor 114 and the inputs thereto.
[0043] [3. Specific Examples] Specific examples of the processing performed by the control unit 102 of the difference checking device 100 in this embodiment will be described with reference to FIGS.
[0044] (3-1. Overall processing) Figure 3 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the difference checking device 100 in this embodiment. With reference to Figure 3, an outline of the overall processing of the control unit 102 of the difference checking device 100 in this embodiment will be explained. Hereinafter, the difference checking device 100 may be simply referred to as the "orderer side."
[0045] 4, the MAWB input unit 102a performs MAWB input (step S1). Specifically, in MAWB input, the MAWB input unit 102a submits a transportation request from the website of the airline system 400 of the target airline (e.g., airlines A, B, and C), inputs MAWB (Master Air Waybill) fee data, and stores it in the transaction data file 106a. Upon receiving the transportation request, the airline system 400 performs transportation and uploads billing data according to the transportation performance to the CASS 500. Note that transportation requests to airlines may also be made by telephone, email, fax, etc.
[0046] The CASS data acquisition unit 102b executes a CASS data import process (step S2). Specifically, the CASS data acquisition unit 102b designates the target file on the import designation screen of the CASS 500 website, downloads the CASS data file (billing data), and stores it in the CASS data file 106b. The CASS data (billing data) is downloaded from the CASS 500 twice a month. The CASS data is divided into a first half and a second half based on the Issue Date of the MAWB, with the first half covering the 1st to 15th days and the second half covering the 16th to 31st days.
[0047] The collation unit 102c executes a collation process (step S3). Specifically, in the collation process, the collation unit 102c collates the MAWB fee data stored in the transaction data file 106a with the CASS data stored in the CASS data file 106b, and outputs a report of the collation results.
[0048] The collation unit 102c may collate the MAWB fee data and the CASS data on a MAWB No. basis. If at least one of the fees (Net WT / CHG and Due Carrier) does not match, the collation unit 102c may determine that there is a mismatch, and calculate the Net WT / CHG of the CASS data as Net WT / CHG = IATA WT / CHG - Commission - Incentive. The collation unit 102c may also collate dates, and if the Date of Issue of the MAWB fee data does not match the import year, month, and term of the CASS data, may determine that there is no data.
[0049] Furthermore, the matching unit 102c may match the MAWB fee data with the CASS data and output a report of the matching results, for example, in accordance with extraction conditions specified by the operator on an extraction condition specification screen displayed on the monitor 114. In this case, the operator may be able to specify the MAWB fee data or the CASS data as the output main data on the extraction condition specification screen, and a report of the matching results may be output using the specified MAWB fee data or the CASS data as the basis.
[0050] If the results match (○) after checking the report, you can proceed with the payment. If the results do not match (×), you can check the MAWB fare data or contact the airline.
[0051] (3-2. Sample data) 4 to 9 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the balance checking device 100 in this embodiment. A specific example of the processing by the control unit 102 of the balance checking device 100 in this embodiment will be explained with reference to FIGS. 4 to 11.
[0052] (Normal case (when the matching result is a match)) An example of a normal case (when the collation results in a match) will be described with reference to FIGS.
[0053] (S1:MAWB input) The MAWB input unit 102a, for example, submits a transportation request from the website of the airline system 400 of the target airline (e.g., airlines A, B, and C), inputs MAWB (Master Air Waybill) fee data, and stores it in the transaction data file 106a. When the airline system 400 receives the transportation request, it performs the transportation and uploads billing data according to the transportation performance to the CASS 500.
[0054] Figure 4(A) shows an example of MAWB fee data. The MAWB fee data includes the following items: MAWBNO, Date of Issue, IATA WT / CHG, Commission, Net WT / CHG (fare paid to airlines), and Due Carrier (surcharge paid to airlines). In the example shown in the figure, the first line has MAWB No. "A001", Date of Issue "2022 / 05 / 01", IATA WT / CHG "217,305", Commission "10,865", Net WT / CHG "61,460", Due Carrier "10,158", the second line has MAWB No. "A002", Date of Issue "2022 / 05 / 10", IATA WT / CHG "99,000", Commission "4,950", Net WT / CHG "30,000", Due Carrier "4,900", the third line has MAWB No. "A003", Date of Issue "2022 / 05 / 15", IATA WT / CHG "1,094,400", Commission "54,720", Net WT / CHG is 969,000 and Due Carrier is 60,920.
[0055] (S2: CASS data import processing) The CASS data acquisition unit 102b downloads the CASS data, which is billing data uploaded to the CASS 500 by the target airline, from the CASS 500 and stores it in the CASS data file 106b.
[0056] 4B is a diagram showing an example of CASS download data. The CASS download data is data uploaded to CASS 500 by the target airline.
[0057] Figure 4(C) is a diagram showing an example of the import specification screen. On the import specification screen, import specification conditions of the import year and month, term (first half or second half), and file path are specified to import billing data (invoice data). In the example shown in the figure, the import year and month "2022 / 05", term "first half", and file path "¥¥XXXXX¥CASS (first half of May)" are specified. Data that meets the import specification conditions is imported as CASS data from the CASS download data and stored in CASS data file 106b.
[0058] 4(D) is a diagram showing an example of the imported CASS data. The CASS data includes the following items: MAWBNO, IATA WT / CHG, Commission, Incentive, Due Carrier, import date, and Term. In the example shown in the figure, the first line contains MAWBNO "A001", IATA WT / CHG "217,305", Commission "10,865", Incentive "144,980", Due Carrier "10,158", Import Date "2022 / 05", Term "First Half", the second line contains MAWBNO "A002", IATA WT / CHG "99,000", Commission "4,950", Incentive "64,050", Due Carrier "4,900", Import Date "2022 / 05", Term "First Half", the third line contains MAWBNO "A003", IATA WT / CHG "1,094,400", Commission "54,720", Incentive "70,680", Due Carrier is "60,920", acquisition date is "2022 / 05", and term is "first half".
[0059] (S3: Matching process) The matching unit 102c matches the MAWB fee data with the CASS data according to, for example, the extraction conditions specified by the operator on the extraction condition specification screen displayed on the monitor 114, and outputs a CASS report, which is a report in form of the matching results.
[0060] FIG. 4(E) is a diagram showing an example of the extraction condition specification screen. On the extraction condition specification screen, you specify the output main data (MAWB fee data or CASS data), Issue Date, import year and month, first half / second half, and matching conditions (all items or only mismatches). The "output main data" is used to specify the data that will be used as the basis for the CASS Report. The matching results (match: ○, mismatch: ×) are output based on the specified data. If you specify "all items" as the matching condition, the matching results for all items will be output, and if you specify "mismatch only," only the matching results for the mismatched data will be output.
[0061] In the example shown in the figure, the output main data is "CASS data", the CASS import date is "2022 / 05", "first half", and CASS matching is "all items".
[0062] Figure 4(F) shows an example of a transfer table for MAWB fee data and CASS data. The transfer table includes output items, transfer source, and transfer items. The output items for MAWB fee data are MAWB No., Issue Date, IATA WT / CHG, Commission, Incentive, Net WT / CHG, and Due Carrier. Since Incentive is not included in the MAWB fee data items, it is calculated and transferred using the formula IATA WT / CHG-Commission-Net WT / CHG.
[0063] The output items of CASS data are MAWB No., IATA WT / CHG, Commission, Incentive, Net WT / CHG, Due Carrier, and Mismatch. Net WT / CHG is not included in the CASS data items, so it is calculated and transferred using IATA WT / CHG-Commission-Incentive. The reason why the CASS data has a "Mismatch (matching result)" item is because it is specified as the output main data in Figure 4 (E). If the output main data is MAWB fare data, the MAWB fare data will have a "Mismatch (matching result)" item.
[0064] The MAWB fee data and CASS data are matched on a MAWB number basis. Figure 5 shows an example of a CASS report. The header of a CASS report contains the period and CASS matching conditions, and the body contains the matching items (MAWB number, Issue Date, IATA WT / CHG, Commission, Incentive, Net WT / CHG, Due Carrier), MAWB fee data, CASS data value, and Mismatch. If either Net WT / CHG or Due Carrier mismatch, the Mismatch (matching result) is marked as "Mismatch: ×." If the Date of Issue, import year / month, and term do not match, it is determined that there is no data (if CASS data is used as the basis, there is no MAWB fee data, and if MAWB fee data is used as the basis, there is no CASS data).
[0065] Examples of "Mismatch" output are the following patterns 1 to 6. (Pattern 1): Match → "〇" (Pattern 2): There is a difference in Net WT / CHG → "× (Net WT / CHG)" (Pattern 3): There is a difference in the due carrier → "× (Due Carrier)" (Pattern 4): There is a difference between the Net WT / CHG and the Due Carrier → "× (Net WT / CHG & Due Carrier)" (Pattern 5): No CASS data exists → "No Cass Data" (Pattern 6): MAWB fee data does not exist → "No MAWB Data"
[0066] In the example shown in Figure 5, the matching items match for all MAWB NOs, and "Mismatch" based on CASS data is marked as "〇: Match."
[0067] (If the two parties have different understanding of the date (first half and second half)) An example in which the two parties recognize the date (first half and second half) differently will be described with reference to FIGS.
[0068] In Figure 6(A), if the Date of Issue for MAWB fee data MAWBNO "A003" is "2022 / 05 / 16", the CASS REPORT will be as shown in Figure 7. The other data in Figure 6 is the same as Figure 4.
[0069] In Figure 7, for MAWB NO "A003," if the CASS side recognized it as 2022 / 05 (first half) but the client side recognized it as 2022 / 05 (second half) (2022 / 5 / 16), the "Mismatch" based on the CASS data will be "No MAWB Data."
[0070] (If the Net WT / CHG and Due Carrier are different between the two) An example in which the Net WT / CHG and Due Carrier are different between the two will be described with reference to FIGS.
[0071] In Figure 8, if the CASS data MAWBNO "A001" has an Incentive of "134,980," the MAWB fee data MAWBNO "A002" has a Due Carrier of "6,900," and the CASS data MAWBNO "A003" has an Incentive of "96,280" and a Due Carrier of "51,860," the CASS REPORT will look like Figure 9. The other data in Figure 8 is the same as Figure 4.
[0072] "IATA WT / CHG" is the published fare listed on the MAWB, but the final fare paid (=Net WT / CHG) is the fare after "Commission" and "Incentive" are deducted from it. Because the percentages of Commission and Incentive vary from airline to airline, calculating "Net WT / CHG" is complicated, and there are many cases where the recognized amounts for both parties differ.
[0073] In Figure 9, the "Mismatch" for MAWB No. "A001" is × (Net WT / CHG), the "Mismatch" for MAWB No. "A002" is × (Due Carrier), and the "Mismatch" for MAWB No. "A003" is × (Net WT / CHG & Due Carrier).
[0074] As described above, according to this embodiment, the system is equipped with a MAWB input unit 102a that inputs MAWB (Master Air Waybill) fee data for the target airline and stores it in a transaction data file 106a, a CASS data acquisition unit 102b that downloads CASS data, which is billing data uploaded to CASS 500 by the target airline, from the CASS and stores it in a CASS data file 106b, and a matching unit 102c that compares the MAWB fee data stored in the transaction data file 106a with the CASS data stored in the CASS data file 106b and outputs a report of the comparison results.Therefore, by checking the report of the comparison results, it is possible to identify discrepancies early on and make CASS settlement operations more efficient.
[0075] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.
[0076] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.
[0077] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.
[0078] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.
[0079] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.
[0080] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.
[0081] Furthermore, with regard to the difference check device 100, the components shown in the figures are functional concepts, and the device does not necessarily have to be physically configured as shown in the figures.
[0082] For example, all or any part of the processing functions of the balance checking device 100, particularly the processing functions performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the balance checking device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.
[0083] This computer program may also be stored in an application program server connected to the balance checking device 100 via any network, and all or part of it may be downloaded as needed.
[0084] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.
[0085] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by working together with other programs, such as an OS. Note that the specific configurations and reading procedures for reading a recording medium in each device shown in the embodiments, as well as the installation procedures after reading, can use well-known configurations and procedures.
[0086] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.
[0087] The difference checking device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The difference checking device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.
[0088] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]
[0089] 100 Difference Check Device 102 Control section 102a MAWB input section 102b CASS data acquisition section 102c Matching section 102d Screen display control unit 104 Communication interface unit 106 Storage section 106a Transaction Data File 106b CASS data file 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network 400 Airline Systems 500 CASS
Claims
1. A difference check device having a control unit and configured to be able to communicate data with a CASS (Cargo Accounts Settlement System) via a network, The control unit an input means for inputting MAWB (Master Air Waybill) fee data for a target airline and storing the data in a storage unit; an importing means for downloading CAS data, which is billing data uploaded to the CAS by the target airline, from the CAS and storing the data in the storage unit; a comparison means for comparing the MAWB fee data stored in the storage unit with the CASS data and outputting a report of the comparison result; A difference check device comprising:
2. The MAWB fare data includes MAWB NO, Date of Issue, IATA WT / CHG, Commission, Net WT / CHG, and Due Carrier; The CASS data includes MAWBNO, IATA WT / CHG, Commission, Incentive, Due Carrier, import date, and first or second half term; 2. The price difference check device according to claim 1, wherein said comparing means compares said MAWB fee data with said CASS data on a MAWB number basis.
3. The difference check device according to claim 2, characterized in that the matching means determines that there is a mismatch if at least one of Net WT / CHG and Due Carrier does not match between the MAWB fee data and the CASS data, and calculates the Net WT / CHG of the CASS data as Net WT / CHG = IATA WT / CHG - Commission - Incentive.
4. 3. The difference check device according to claim 2, wherein said collating means determines that there is no data when the Date of Issue of said MAWB fee data does not match the import year / month and term of said CASS data.
5. The difference check device described in any one of claims 1 to 4 is characterized in that the matching means allows the operator to specify MAWB fee data or CASS data as the output main data on the extraction condition specification screen, and outputs a report of the matching results based on the specified data.
6. A difference check method executed by an information processing device that includes a control unit and is configured to be able to communicate data with a Cargo Accounts Settlement System (CASS) via a network, comprising: Executed in the control unit: an input step of inputting MAWB (Master Air Waybill) fee data for a target airline and storing the data in a storage unit; an import step of downloading CAS data, which is billing data uploaded to the CAS by the target airline, from the CAS and storing it in the storage unit; a matching step of matching the MAWB fee data stored in the storage unit with the CASS data and outputting a report of the matching result; A method for checking a difference, comprising:
7. A difference check program to be executed by an information processing device that includes a control unit and is configured to be able to communicate data with a CASS (Cargo Accounts Settlement System) via a network, In the control unit, an input step of inputting MAWB (Master Air Waybill) data for the target airline and storing it in a storage unit; an import step of downloading CAS data, which is billing data uploaded to the CAS by the target airline, from the CAS and storing it in the storage unit; a matching step of matching the MAWB fee data stored in the storage unit with the CASS data and outputting a report of the matching result; A difference check program to run.
Citation Information
Patent Citations
System and method for adjustment processing.
JP2001229254A
Travel expense settlement processing computer system and organizational travel expense settlement processing method
JP2006209737A
Effective sales system for cargo compartment space of aircraft
JP2006244198A
Methods and systems for global invoice processing and payment
US20130304639A1