A claim settlement liability determination method and device, a storage medium and an electronic device

Abstract

The application provides a claim settlement responsibility determination method and device, a storage medium and an electronic device. The method comprises the following steps: in response to a claim settlement initiation request, obtaining a claim settlement waybill in the claim settlement initiation request; when the waybill type of the claim settlement waybill is a TC waybill, determining the abnormal type and the waybill number of the claim settlement waybill; based on the abnormal type and the waybill number, determining claim data in a quality control system, and based on the claim data, determining the claim settlement type to which the claim settlement waybill belongs; obtaining responsibility determination data corresponding to the claim settlement type in the claim settlement waybill, and determining the responsibility object of the claim settlement waybill based on the responsibility determination data. According to the abnormal type and the waybill number of the claim settlement waybill in the claim settlement initiation request, the claim data is determined, the claim settlement type to which the claim settlement waybill belongs is determined according to the claim data, the responsibility determination data corresponding to the claim settlement type in the claim settlement waybill is obtained, and then the responsibility object of the claim settlement waybill is determined according to the responsibility determination data. The whole process does not need manual parameters, effectively shortens the time required for determining the responsibility object, and improves the efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for determining liability in claims settlement, a storage medium, and an electronic device. Background Technology

[0002] With the development of e-commerce, more and more people are shopping online. Merchants use logistics or express delivery to deliver the items purchased online to the consumer's designated location. However, items purchased by consumers may be damaged or lost during transportation.

[0003] When problems arise during the transportation of goods, merchants or logistics providers need to identify the responsible party so that the responsible party can assign liability for the damaged goods on the waybill, facilitating subsequent management of the transportation. Currently, determining liability is done manually, requiring significant time and effort to manually search and verify data, resulting in extremely low efficiency. Summary of the Invention

[0004] In view of this, the present invention provides a method and apparatus for determining liability in claims settlement, a storage medium and an electronic device, which reduces human intervention in the entire liability determination process, improves the efficiency of liability determination and reduces errors.

[0005] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] The first aspect of this invention discloses a method for determining liability in claims settlement, comprising:

[0007] In response to a claim initiation request, obtain the claim waybill from the claim initiation request;

[0008] When the waybill type of the claim waybill is TC waybill, determine the abnormality type and waybill number of the claim waybill;

[0009] Based on the anomaly type and the waybill number, claim data is determined in the quality control system, and based on the claim data, the claim type of the claim waybill is determined. The claim type is one of the following: with claim letter, damaged without claim letter, or lost without claim letter.

[0010] Based on the claim type, obtain the liability determination data of the claim waybill, and determine the responsible party of the claim waybill based on the liability determination data.

[0011] Optionally, when the claim type is a claim letter type, the step of determining the liable party of the claim waybill based on the liability determination data includes:

[0012] Based on the claim creation information in the liability determination data, determine whether the claim waybill creation timed out;

[0013] If it is determined that the creation of the claim waybill has timed out, the department that created the claim letter will be identified as the responsible party for the claim waybill.

[0014] If it is determined that the creation of the claim waybill has not expired, then the cancellation data in the liability determination data is obtained to determine whether the claim waybill has been cancelled within the time limit;

[0015] If it is determined that the claim waybill was cancelled within the time limit, then the claims negotiation post will be identified as the responsible party for the claim waybill.

[0016] If it is determined that the claim waybill was not cancelled within the time limit, the responsible unit information of the claim waybill is obtained, and the responsible party of the claim waybill is determined based on the responsible unit information.

[0017] Optionally, in the above method, obtaining the reversal data from the liability determination data and determining whether the claim waybill was reversed within the time limit includes:

[0018] Determine whether the reversal data is empty;

[0019] When it is determined that the cancellation data is empty, it is determined that the claim waybill was not cancelled within the time limit;

[0020] When it is determined that the reversal data is not empty, the planned closing time and creation time of the reversal document of the claim waybill are obtained from the reversal data;

[0021] Determine whether the creation time is earlier than the planned shutdown time;

[0022] If the creation time is determined to be earlier than the planned closure time, the claim waybill is determined to be cancelled within the time limit; otherwise, the claim waybill is determined not to be cancelled within the time limit.

[0023] Optionally, when the claim type is damage without a claim letter, the step of determining the liable party of the claim waybill based on the liability determination data includes:

[0024] Based on the successful delivery data in the liability determination data, it is determined whether the claim waybill has been successfully delivered;

[0025] When it is determined that the claim waybill has not been delivered, the business data of the claim waybill is obtained, and the responsible party of the claim waybill is determined based on the business data;

[0026] Once it is determined that the claim waybill has been successfully delivered, obtain the latest routing information for the claim waybill;

[0027] Based on the routing information, determine whether the status of the claim waybill is in the warehouse entry status;

[0028] When the status of the claim waybill is determined to be "warehouse entry", the warehouse into which the claim waybill is entered is determined, and the department responsible for that warehouse is determined as the responsible party for the claim waybill.

[0029] When it is determined that the status of the claim waybill is not in the warehouse entry status, the responsible party for the claim waybill is determined based on the operation information of the department to which the routing information belongs.

[0030] Optionally, when the claim type is "no claim letter lost," the step of determining the liable party of the claim waybill based on the liability determination data includes:

[0031] Based on the successful delivery data in the liability determination data, it is determined whether the claim waybill has been successfully delivered;

[0032] When it is determined that the claim waybill has not been delivered, it is determined whether the claim waybill is in a return status;

[0033] When it is determined that the claim waybill is in a return status, the transit center to which the claim waybill belongs is identified, and the transit center is identified as the responsible party for the claim waybill;

[0034] When it is determined that the claim waybill is not in a return status, the responsible party is determined based on the warehouse information of the claim waybill;

[0035] Once it is determined that the claim waybill has been successfully delivered, obtain the latest routing information for the claim waybill;

[0036] Based on the routing information, determine whether the status of the claim waybill is in the warehouse entry status;

[0037] When the status of the claim waybill is determined to be "warehouse entry", the warehouse into which the claim waybill is entered is determined, and the department responsible for the warehouse is determined as the responsible party for the claim waybill.

[0038] When it is determined that the status of the claim waybill is not in the warehouse entry status, the responsible party for the claim waybill is determined based on the operation information of the department to which the routing information belongs.

[0039] A second aspect of the present invention discloses a claims settlement device, comprising:

[0040] The first acquisition unit is used to acquire the claim waybill in the claim initiation request in response to the claim initiation request;

[0041] The first determining unit is used to determine the abnormality type and waybill number of the claim waybill when the waybill type of the claim waybill is a TC waybill;

[0042] The second determining unit is used to determine claim data in the quality control system based on the anomaly type and the waybill number, and to determine the claim type of the claim waybill based on the claim data. The claim type is one of the following: a claim letter type, a damaged claim letter type, and a lost claim letter type.

[0043] The second acquisition unit is used to acquire the liability determination data of the claim waybill based on the claim type, and determine the responsible party of the claim waybill based on the liability determination data.

[0044] Optionally, the second acquisition unit in the aforementioned apparatus includes:

[0045] The first judgment subunit is used to determine whether the creation of the claim waybill has timed out based on the claim creation information in the liability determination data;

[0046] The first determining subunit is used to determine the department that created the claim letter as the responsible party for the claim waybill if it is determined that the creation of the claim waybill has timed out.

[0047] The first acquisition subunit is used to acquire the cancellation data in the liability determination data if it is determined that the creation of the claim waybill has not expired, and to determine whether the claim waybill has been cancelled within the time limit.

[0048] The second determining subunit is used to determine the claims negotiation post as the responsible party for the claims waybill if it is determined that the claims waybill was cancelled within the time limit.

[0049] The second acquisition subunit is used to acquire the responsible unit information of the claim waybill if it is determined that the claim waybill was not cancelled within the time limit, and to determine the responsible object of the claim waybill based on the responsible unit information.

[0050] Optionally, in the aforementioned apparatus, the first acquisition subunit includes:

[0051] The first judgment module is used to determine whether the offset data is empty;

[0052] The first determining module is used to determine that the claim waybill has not been cancelled within the time limit when the cancellation data is determined to be empty.

[0053] The first acquisition module is used to obtain the planned closing time and creation time of the claim waybill's cancellation document from the cancellation data when it is determined that the cancellation data is not empty;

[0054] The second judgment module is used to determine whether the creation time is earlier than the planned shutdown time;

[0055] The second determining module is used to determine that the claim waybill is cancelled within the time limit if the creation time is earlier than the planned closing time; otherwise, it is determined that the claim waybill is not cancelled within the time limit.

[0056] Optionally, the second acquisition unit in the aforementioned apparatus includes:

[0057] The second judgment subunit is used to determine whether the claim waybill has been successfully delivered based on the successful delivery data in the liability determination data;

[0058] The third acquisition subunit is used to acquire the business data of the claim waybill when it is determined that the claim waybill has not been delivered, and to determine the responsible party of the claim waybill based on the business data.

[0059] The fourth acquisition subunit is used to acquire the latest routing information of the claim waybill when it is determined that the claim waybill has been successfully delivered;

[0060] The third judgment subunit is used to determine whether the status of the claim waybill is in the warehouse entry status based on the routing information.

[0061] The third determining subunit is used to determine the warehouse into which the claim waybill is received when the waybill status is determined to be warehouse entry status, and to determine the responsible department of the warehouse as the responsible party of the claim waybill.

[0062] The fourth determining subunit is used to determine the responsible party of the claim waybill based on the operation information of the department to which the routing information belongs when the waybill status of the claim waybill is determined to be not in the warehouse status.

[0063] Optionally, the second acquisition unit in the aforementioned apparatus includes:

[0064] The fourth judgment subunit is used to determine whether the claim waybill has been successfully delivered based on the successful delivery data in the liability determination data;

[0065] The fifth judgment subunit is used to determine whether the claim waybill is in a return status when it is determined that the claim waybill has not been properly delivered.

[0066] The fifth determining subunit is used to determine the transit center to which the claim waybill belongs when it is determined that the claim waybill is in a return status, and to determine the transit center as the responsible party of the claim waybill;

[0067] The sixth determining subunit is used to determine the responsible party based on the warehouse information of the claim waybill when it is determined that the claim waybill is not in a return status;

[0068] The fifth acquisition subunit is used to acquire the latest routing information of the claim waybill when it is determined that the claim waybill has been successfully delivered;

[0069] The sixth judgment subunit is used to determine, based on the routing information, whether the status of the claim waybill is in the warehouse entry status;

[0070] The seventh determining subunit is used to determine the warehouse to which the claim waybill is received when the waybill status is determined to be warehouse entry status, and to determine the responsible department of the warehouse as the responsible party of the claim waybill;

[0071] The eighth determining subunit is used to determine the responsible party of the claim waybill based on the operation information of the department to which the routing information belongs when the waybill status of the claim waybill is determined to be not in the warehouse status.

[0072] A third aspect of the present invention discloses a storage medium comprising stored instructions, wherein, when the instructions are executed, the device in which the storage medium is located executes the claims settlement method as described above.

[0073] The fourth aspect of the present invention discloses an electronic device, including a memory and one or more instructions, wherein one or more instructions are stored in the memory and configured to be executed by one or more processors as described above in the claims determination method.

[0074] Compared with the prior art, the present invention has the following advantages:

[0075] This invention provides a method, apparatus, storage medium, and electronic device for determining liability in claims settlement. The method includes: responding to a claim initiation request by obtaining a claim waybill from the claim initiation request; when the waybill type of the claim waybill is a TC waybill, determining the anomaly type and waybill number of the claim waybill; based on the anomaly type and waybill number, determining claim data in a quality control system, and based on the claim data, determining the claim type to which the claim waybill belongs, wherein the claim type is one of a claim letter type, a damage type without a claim letter type, and a loss type without a claim letter type; obtaining liability determination data corresponding to the claim type in the claim waybill, and determining the liable party of the claim waybill based on the liability determination data. This invention first obtains the claim waybill from the claim initiation request, determines the claim data based on the anomaly type and waybill number of the claim waybill, determines the claim type of the claim waybill based on the claim data, obtains the liability determination data corresponding to the claim type in the claim waybill, and then determines the liable party of the claim waybill based on the liability determination data. The entire process does not require manual intervention, effectively shortening the time required to determine the liable party, thereby improving the efficiency of liability determination and claims settlement. Attached Figure Description

[0076] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0077] Figure 1 A flowchart illustrating a method for determining liability in claims settlement, as provided in an embodiment of the present invention;

[0078] Figure 2 A flowchart illustrating a method for determining the claim type of a claim waybill provided in an embodiment of the present invention;

[0079] Figure 3 This is a flowchart of a method for synchronizing data in a quality control system provided in an embodiment of the present invention;

[0080] Figure 4 A flowchart illustrating a method for determining the responsible party of a claim waybill when the claim type is a claim letter type, provided in an embodiment of the present invention.

[0081] Figure 5 A flowchart illustrating a method for determining whether claims waybill data has timed out, provided in an embodiment of the present invention.

[0082] Figure 6 A flowchart illustrating a method for determining whether a claim waybill has been cancelled within the time limit, as provided in an embodiment of the present invention.

[0083] Figure 7 This is a flowchart illustrating a method for sending a claim waybill to the corresponding staff member, as provided in an embodiment of the present invention.

[0084] Figure 8 A flowchart illustrating a method for determining the responsible party of a claim waybill when the claim type is "no claim letter lost" provided in an embodiment of the present invention;

[0085] Figure 9 A flowchart illustrating a method for determining the responsible party of a claim waybill when the claim type is "damage without a claim letter" according to an embodiment of the present invention.

[0086] Figure 10 This is a schematic diagram of the structure of a claims settlement device provided in an embodiment of the present invention;

[0087] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0088] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0089] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0090] This invention can be used in a wide variety of general-purpose or special-purpose computing environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor devices, distributed computing environments including any of the above devices, etc.

[0091] Terminology Explanation:

[0092] Redis: short for Remote Dictionary Server, is an open-source, ANSI C-written, network-enabled, in-memory or persistent log-structured key-value database.

[0093] The current process for determining liability for damaged goods in transit requires manual judgment, which is inefficient and prone to errors. When using the current method to determine liability for waybills at transfer centers (TC), staff need to manually input and output data between different systems. Furthermore, the data between these systems is independent and cannot be reused, resulting in a long and cumbersome process that negatively impacts customer experience.

[0094] To address the problems of existing technologies, this invention aims to provide a method, apparatus, storage medium, and electronic device for determining liability in claims settlement. This reduces manual intervention throughout the liability determination process, improves efficiency, and decreases the probability of errors. This invention can be applied to a liability determination system that integrates a TC (Claim Center) system, a liability assessment system, a claims settlement system, and a quality control system. The liability determination system can perform functions such as TC claims, liability assessment, claims settlement, and quality control, thereby enabling data reuse between various systems. Furthermore, it transforms the cumbersome input and output processes of frontline liability assessors to a unified, systematic process, allowing the liability determination system to perform assessment tasks on behalf of staff, thus improving efficiency and reducing error rates.

[0095] Reference Figure 1 The following is a flowchart of a claims settlement and liability determination method provided by an embodiment of the present invention, which is described in detail below:

[0096] S101: In response to a claim initiation request, obtain the claim waybill from the claim initiation request.

[0097] When a user discovers damage to an item, they need to file a claim, generating a claim initiation request and sending it to the system. This allows the system to determine liability for the item and then compensate the user. Preferably, the claim initiation request can be stored in a message queue as a message queue (MQ). The system receives claim initiation requests from the message queue in the order they are dequeued.

[0098] It should be noted that the claim initiation request includes, but is not limited to, user information, item information, and claim waybill information.

[0099] S102: Determine whether the waybill type of the claim waybill is a TC waybill. If it is determined that the waybill type of the claim waybill is a TC waybill, execute S103; otherwise, execute S106.

[0100] Preferably, the method for determining whether a claim waybill is a TC waybill can be by checking whether a TC waybill identifier exists in the claim waybill. For example, data in the waybill type field of the waybill number of the claim waybill can be extracted, and it can be determined whether the data is consistent with the preset TC waybill identifier. If they are consistent, the waybill type of the claim waybill is determined to be a TC waybill; otherwise, the waybill type of the claim waybill is determined not to be a TC waybill.

[0101] S103: Determine the anomaly type and waybill number of the claim waybill.

[0102] The waybill number can be directly extracted from the claim waybill. The type of abnormality can be determined by the data in the abnormality field of the claim waybill. Preferably, the abnormality type is one of the following: whole shipment lost / incomplete packages, damaged outside and missing inside, damaged outside, damaged outside and damaged inside, good outside and missing inside, good outside and damaged inside.

[0103] Preferably, different anomaly types have different anomaly identifiers. The anomaly identifier can be represented by a string. For example, the string for the anomaly type "order lost / package incomplete" can be "order lost / package incomplete", or it can be "order lost / package incomplete" converted into a string composed of letters and numbers. The anomaly identifiers for the anomaly types "external damage, internal shortage", "external damage", "external damage, internal damage", "external good, internal shortage", or "external good, internal damage" can refer to the description of the string for the anomaly type "order lost / package incomplete", which will not be repeated here.

[0104] S104: Based on the anomaly type and waybill number, determine the claim data in the quality control system, and based on the claim data, determine the claim type to which the claim waybill belongs. The claim type is one of the following: with claim letter, damaged without claim letter, or lost without claim letter.

[0105] Claim data includes, but is not limited to, claim forms, claim details, and evidence information. Furthermore, claim data can be data uploaded by users in a preset data supplement area, or data extracted from AI surveillance videos.

[0106] The quality control system synchronizes claim data related to the claim waybill. Therefore, when obtaining claim data related to the claim waybill, it is necessary to obtain it from the quality control system.

[0107] In the method provided by the embodiments of the present invention, different claim types correspond to different processing engines. The processing engine is set with inference liability logic corresponding to the claim type. The processing engine can infer the responsible party of the claim waybill based on the preset inference liability logic.

[0108] S105: Based on the claim type, obtain the liability determination data of the claim waybill, and determine the responsible party of the claim waybill based on the liability determination data.

[0109] It should be noted that the responsible party identified here is the unit that needs to determine the responsibility for the claim waybill. Specifically, this could be a staff member or a specific work department.

[0110] Continuing from the above explanation, the processing engine corresponding to the claim type is invoked to obtain the liability determination data of the claim waybill based on the preset inference liability logic, and the liability determination data is processed according to the inference liability logic to determine the liable party of the claim waybill; furthermore, the liability determination data obtained for different claim types are different.

[0111] S106: Send the claim initiation request to the pre-set claim settlement personnel for processing.

[0112] When the waybill type is not a TC waybill, the claim initiation request will be sent to the preset claim settlement personnel for processing. In other words, the claim initiation request will be processed manually.

[0113] In the method provided by this invention, in response to a claim initiation request, the claim waybill in the claim initiation request is obtained; when the waybill type of the claim waybill is a TC waybill, the abnormality type and waybill number of the claim waybill are determined; based on the abnormality type and waybill number, claim data is determined in the quality control system, and based on the claim data, the claim type to which the claim waybill belongs is determined, which is one of the following: with a claim letter, damaged without a claim letter, or lost without a claim letter; liability determination data corresponding to the claim type is obtained in the claim waybill, and the liable party of the claim waybill is determined based on the liability determination data. This invention first obtains the claim waybill in the claim initiation request, determines the claim data according to the abnormality type and waybill number of the claim waybill, determines the claim type to which the claim waybill belongs based on the claim data, obtains the liability determination data corresponding to the claim type in the claim waybill, and then determines the liable party of the claim waybill based on the liability determination data. The entire process reduces the degree of manual intervention, effectively shortens the time required to determine the liable party, thereby improving the efficiency of liability judgment and claims settlement.

[0114] Reference Figure 2 The following is a flowchart of a method for determining the claim type of a claim waybill according to an embodiment of the present invention, which is described in detail below:

[0115] Upon receiving a claim initiation request, the system can determine whether the waybill type of the claim initiation request is a TC waybill by calling the TC transportation interface. Preferably, the claim initiation request can be sent as a queue message. Furthermore, when the waybill type is not a TC waybill, the claim initiation request is sent to a pre-set claims settlement personnel for manual processing, which can also be understood as using a non-automated processing method to process the claim waybill. When the waybill type is a TC waybill, it is necessary to determine the exception type of the claim waybill. It should be noted that the abnormal type of the claim waybill is one of the following: lost / incomplete package, damaged outside and missing inside, damaged outside, damaged outside and damaged inside, good outside and missing inside, and good outside and damaged inside. Furthermore, when the abnormal type is good outside and missing inside or good outside and damaged inside, the claim data obtained based on the waybill number is empty, so the claim type can be directly determined. When the abnormal type of the claim waybill is good outside and missing inside, the claim type of the claim waybill can be directly determined as the lost type without claim letter. When the abnormal type of the claim waybill is good outside and damaged inside, the claim type of the claim waybill can be directly determined as the damaged type without claim letter.

[0116] When the anomaly type of a claim waybill is one of the following: total loss / incomplete packages, external damage / incomplete packages, external damage, or external damage / internal damage, it is necessary to query the claim data corresponding to that anomaly type in the quality control system and confirm that the queried claim data is not empty and that the claim data status is in one of the following states: initial, acknowledged responsibility, or closed. In the case of a claim waybill with the anomaly type of total loss / incomplete packages, if the claim data is not empty and its status is in one of the following states: initial, acknowledged responsibility, or closed, the claim type of the claim waybill is determined to be the type with a claim letter; otherwise, the claim type of the claim waybill is determined to be the type without a claim letter (loss). In the case of a claim waybill with the anomaly type of external damage / incomplete packages, if the claim data is not empty and its status is in one of the following states: initial, acknowledged responsibility, or closed, the claim type of the claim waybill is determined to be the type with a claim letter; otherwise, the claim type of the claim waybill is determined to be the type without a claim letter (loss). If the claim is in one of the following states: "Acknowledged Liability" or "Closed", the claim type of the waybill is determined to be "With Claim Letter". Otherwise, the claim type of the waybill is determined to be "Lost Without Claim Letter". If the anomaly type of the waybill is "External Damage", and the claim data is not empty and the claim data status is one of "Initial", "Acknowledged Liability", or "Closed", the claim type of the waybill is determined to be "With Claim Letter". Otherwise, the claim type of the waybill is determined to be "Damage Without Claim Letter". If the anomaly type of the waybill is "External Damage" or "Internal Damage", and the claim data is not empty and the claim data status is one of "Initial", "Acknowledged Liability", or "Closed", the claim type of the waybill is determined to be "With Claim Letter". Otherwise, the claim type of the waybill is determined to be "Damage Without Claim Letter".

[0117] Preferably, the quality control system usually synchronizes the TC claim data of the claim waybill. When querying the claim data of the claim waybill, the query can be performed from the TC claim data of the claim waybill.

[0118] In the method provided by this invention, there are corresponding processing engines for the types of claims with letters, the types of claims without letters that are lost, and the types of claims without letters that are damaged. For example, the type of claims with letters has a corresponding rule engine with letters, which presets the inference logic for claims with letters; the type of claims without letters that are lost has a corresponding rule engine for claims without letters that are lost, which presets the inference logic for claims without letters that are lost; and the type of claims without letters that are damaged has a corresponding rule engine for claims without letters that are damaged, which presets the inference logic for claims without letters that are damaged.

[0119] Furthermore, after determining the claim type of the claim waybill, the data of the claim waybill needs to be stored. The storage method can be grouped according to different states and different exception types. The system is currently set up with a single database and partitioned tables. By rewriting the Mybatis interceptor, the data is stored in a single table, grouped into three dimensions: the required parameter status, the exception reason, and the processing unit. The table and the processing unit are mapped using a Map.<object,tableName,> The object needs to override the hashCode and Equals methods based on three parameters; the processing units are: a rule engine with a claim letter, a rule engine for damage without a claim letter, and a rule engine for loss without a claim letter. Different processing engines can be used to process the corresponding data.

[0120] The claim data in this invention is obtained from the quality control system, which synchronizes the TC claim data corresponding to the claim waybill. The specific process is as follows: Figure 3 As shown, when the system receives a claim initiation request with a claim waybill type of TC waybill, it needs to obtain the data filled in by the user in a preset area. It should be noted that this claim initiation request can be considered an MQ message. The data filled in by the user can include a claim letter, claim details, etc. After receiving the user's supplementary data, it is necessary to determine whether additional data is required. Specifically, it can be determined whether the claim letter in the user's data is a cancellation claim letter. If so, supplementary data is required. This indicates that further evidence needs to be provided. At this point, an MQ message needs to be sent to the AI ​​monitoring module to obtain AI monitoring video. Evidence data corresponding to the claim waybill is extracted from the AI ​​monitoring video. Both the user-filled data and the evidence data extracted from the AI ​​monitoring video are identified as TC claim data corresponding to the claim waybill. Furthermore, TC claim data includes, but is not limited to, claim forms, claim details, and evidence information. The TC claim data is then synchronized to the quality control system. Preferably, the data can also be saved to MySQL (relational database management system).

[0121] The method provided by this invention determines the liable party differently for different types of claims, and the process for determining the liable party for different types of claims is explained.

[0122] When the claim type is "with claim letter", the specific process for determining the responsible party on the claim waybill is as follows: Figure 4 The specific details are as follows:

[0123] S201: Based on the claim creation information in the liability determination data, determine whether the claim waybill creation timed out; if it is determined that the claim waybill creation timed out, then execute S202; if it is determined that the claim waybill creation did not time out, then execute S203.

[0124] The liability determination data includes claim creation information, which can be data obtained by the system through Clover (an asynchronous task scheduling platform) to asynchronously schedule tasks and the corresponding table data of the claim waybill. Furthermore, the liability determination data includes, but is not limited to, claim creation information, document information, etc. Preferably, the number of task processing threads and the amount of data processed by a single thread can be adjusted in the task scheduling according to the business volume.

[0125] Preferred, refer to Figure 5 The flowchart below illustrates a method for determining whether claims waybill data has timed out, as provided in this embodiment of the invention.

[0126] First, obtain the claim waybill document; determine whether the document is a forward or reverse document; if the document is a forward document, determine whether to complete the delivery before the preset time on the delivery date based on the information on the document. It should be noted that the preset time can be set according to actual needs, such as 18:00; if the delivery is completed before the preset time on the delivery date, determine whether to create a claim letter on the delivery date. If a claim letter is created on the delivery date, determine that the claim waybill creation has not timed out; otherwise, determine that the claim waybill creation has timed out. If the delivery is not completed before the preset time on the delivery completion date, it will be determined whether a claim letter was created between the delivery completion date and the day following the delivery completion date. If so, it will be determined that the claim waybill creation has not exceeded the time limit; otherwise, it will be determined that the claim waybill creation has exceeded the time limit. It should be noted that the time period between the delivery completion date and the day following the delivery completion date includes the entire day following the delivery completion date. The time period between the delivery completion date and the day following the delivery completion date can be understood as the end time point from the delivery completion date to the day following the delivery completion date. Here, the end time point can be 23:59.

[0127] When the document is a reverse document, the system determines whether the delivery was completed before the preset time on the delivery date based on the document's information. If the delivery was completed before the preset time, the system determines whether a claim letter should be created between the delivery date and the following day. If the claim letter is created between the delivery date and the following day, the system determines that the claim waybill creation has not exceeded the time limit; otherwise, the system determines that the claim waybill creation has exceeded the time limit. The relevant explanation regarding the period between the delivery date and the following day is provided above and will not be repeated here. If the delivery was not completed before the preset time, the system determines whether a claim letter should be created between the delivery date and the following day. If the claim letter is created between the delivery date and the following day, the system determines that the claim waybill creation has not exceeded the time limit; otherwise, the system determines that the claim waybill creation has exceeded the time limit.

[0128] It should be noted that when retrieving claim waybills, forward and reverse documents can be obtained based on the waybill number. A recursive algorithm is used to find all forward documents corresponding to the sine of the waybill number and all reverse documents corresponding to the reverse of the waybill number. The number of recursions is limited to 10. When creating a claim letter, the full-process tracking interface must be called to confirm successful delivery and record the delivery time. Otherwise, a monitoring message is sent to the FLINK monitoring module, which is built using Apache Flink. The monitoring module saves the waybills to be monitored to Redis. FLINK monitors the entire process based on the data. If there is a 150-day successful delivery status and the data exists in Redis, an MQ message is sent to the claim system to update the claim letter's successful delivery time and record the status. Then... Figure 5 When making the logical judgment, the updated delivery time and claim letter are used to perform the logical judgment.

[0129] S202: Designate the department that created the claim letter as the responsible party for the claim waybill.

[0130] S203: Obtain the reversal data from the liability determination data and determine whether the claim waybill was reversed within the time limit; if it is determined that the claim waybill was reversed within the time limit, then execute S204; if it is determined that the claim waybill was not reversed within the time limit, then execute S205.

[0131] Reference Figure 6 The flowchart below shows a method for determining whether a claim waybill has been cancelled within the time limit, as provided in an embodiment of the present invention. The details are as follows:

[0132] S301: Determine if the reversal data is empty; if it is determined that the reversal data is empty, execute S305; if it is determined that the reversal data is not empty, execute S302.

[0133] Furthermore, the liability determination data can also include reversal data, which can be obtained from the TC claim data of the claim bill.

[0134] Determine if the reversal data is empty. If the reversal data is empty, execute S305; otherwise, execute S302.

[0135] S302: Retrieve the planned closing time and creation time of the reversal document for the claim waybill from the reversal data.

[0136] S303: Determine whether the creation time is earlier than the planned shutdown time; if the creation time is earlier than the planned shutdown time, execute S304; if the creation time is not earlier than the planned shutdown time, execute S305.

[0137] S304: Ensure that the claim waybill is cancelled within the time limit.

[0138] S305: It has been determined that the claim waybill was not cancelled within the time limit.

[0139] The above process describes the method for determining whether a claim waybill has been cancelled within the time limit. By setting up such a judgment logic, it is possible to quickly determine whether a claim waybill has been cancelled within the time limit, effectively reducing the degree of manual intervention.

[0140] S204: Designate the claims negotiation post as the responsible party for the claims waybill.

[0141] After designating the claims negotiation officer as the responsible party for the claims waybill, the claim waybill can be forwarded to the corresponding staff member. For specific procedures, please refer to [link / reference needed]. Figure 7 The specific explanation is as follows: The step of assigning the claims negotiation team to a claims negotiation team essentially identifies that team as the responsible party for the claims shipment. The claims shipment is then assigned to the claims negotiation personnel within that team. Furthermore, if the initially selected personnel has left the company, the claims negotiation personnel are reassigned according to the appeal logic, and the claims shipment is assigned to them again. This allows the claims negotiation personnel to determine liability for the shipment. If the personnel can determine liability, the responsibility is manually identified and recorded, thus completing the closed loop of determining liability for the claims shipment. If... If the claims negotiating personnel cannot determine liability, they will determine whether "same region throughout the entire process" equals "negotiation region." If "same region throughout the entire process" equals "negotiation region," the claims waybill will be forwarded to regional arbitration for final judgment. If "same region throughout the entire process" does not equal "negotiation region," the claims waybill will be forwarded to group arbitration for final judgment. It should be noted that "same region throughout the entire process" means that the claims waybill is in the same logistics region from beginning to end, such as: North China Logistics Region, South China Logistics Region, East China Logistics Region, Central China Logistics Region, Southwest Logistics Region, Northwest Logistics Region, and Northeast Logistics Region. Negotiation regions are divided according to logistics regions, and each negotiation region is responsible for processing claims documents for one region, that is, one negotiation region corresponds to one logistics region.

[0142] In the process of assigning responsibility, to ensure fairness and impartiality, a reservoir algorithm is used to ensure that the personnel processing the document have an equal probability of handling the document. By using the reservoir algorithm, big data methods for dynamic monitoring, and in conjunction with other basic technologies, the automation, efficiency, fairness, and impartiality of TC document assignment are improved.

[0143] S205: Obtain the information of the responsible unit for the claim waybill and determine the responsible party for the claim waybill based on the information of the responsible unit.

[0144] It should be noted that after obtaining the responsible unit information of the claim waybill, the system determines whether the responsible unit in the claim letter is the carrier. If the responsible unit in the claim letter is the carrier, then the carrier's self-built department is identified as the responsible party for the claim waybill, and the claim waybill is sent to the carrier's self-built department for liability determination. Preferably, the carrier's self-built department can be the carrier's designated responsible department. If the responsible unit in the claim letter is not the carrier, the system determines whether it is the self-operated fleet of the platform to which it belongs. This platform can be a large online platform. For e-commerce platforms selling goods; if it is determined that the fleet is a self-operated fleet of the platform to which the system belongs, then the self-established department of the self-operated fleet is identified as the responsible party for the claim waybill, and the claim waybill is sent to the self-established department of the self-operated fleet for determination of responsibility. Furthermore, the self-established department of the self-operated fleet can be the certification department of the self-operated fleet or the management department of the self-operated fleet; if it is determined that the fleet is not a self-operated fleet of the platform to which the system belongs, then the responsible unit of the claim letter is identified as the responsible party for the claim waybill, and the claim waybill is sent to the responsible unit of the claim letter for confirmation of responsibility.

[0145] Figure 4 The process shown can be understood as the pre-set liability inference logic of the claim letter in the claim letter rule engine mentioned above. After determining that the claim type of the claim waybill is the claim letter type, the liability determination data and the liability object of the claim waybill can be obtained according to the liability inference logic of the claim letter type.

[0146] When the claim type is "no claim letter lost," the specific process for determining the responsible party for the claim waybill is as follows: Figure 8 The specific details are as follows:

[0147] S401: Based on the successful delivery data in the liability determination data, determine whether the claim waybill has been successfully delivered; if it is determined that the claim waybill has not been successfully delivered, execute S402; if it is determined that the claim waybill has been successfully delivered, execute S403.

[0148] The successful delivery data in the liability determination data can be obtained by collecting monitoring data from the FLINK monitoring module. The successful delivery data includes data recorded by the FLINK monitoring module when monitoring the successful delivery operation of the claim waybill, such as whether the delivery was successful and the delivery time.

[0149] S402: Obtain the business data of the claims waybill and determine the responsible party of the claims waybill based on the business data.

[0150] The business data of the claims waybill is obtained, the business type of the claims waybill is determined based on the business data, and the responsible party of the claims waybill is determined based on the business type. For example, when the business type is forward delivery to the warehouse, the destination warehouse is determined based on the business data, and the management department of the destination warehouse is the responsible party of the claims waybill. Preferably, the destination warehouse can also be directly determined as the responsible party of the claims waybill. When the business type is reverse return, the return destination is determined based on the business data, and the management department of the return destination is the responsible party of the claims waybill. Preferably, the return destination can also be directly determined as the responsible party of the claims waybill.

[0151] When the business type is forward delivery, the destination warehouse determined based on the business data is the warehouse where the goods in the claim order are to be delivered; when the business type is reverse return, the return destination determined based on the business data is the location where the goods in the claim order are to be returned; different business types correspond to different business data. Furthermore, reverse return business can be specifically reverse return to TC (Trade Center) or reverse return to an external warehouse; the return destination for reverse return business can be the destination TC.

[0152] S403: Obtain the latest routing information for the claim waybill.

[0153] Call the routing interface to obtain the latest routing information for the claims waybill.

[0154] S404: Based on routing information, determine whether the status of the claim waybill is in the warehouse entry status; if it is determined that the status of the claim waybill is in the warehouse entry status, execute S405; if it is determined that the status of the claim waybill is not in the warehouse entry status, execute S406.

[0155] It should be noted that when a claim waybill is in the "warehouse receipt" or "warehouse shelving" stage, its status can be determined as "warehouse receipt"; otherwise, its status cannot be determined as "warehouse receipt".

[0156] S405: Determine the warehouse to which the claim waybill is received, and identify the department responsible for that warehouse as the party responsible for the claim waybill.

[0157] Based on the warehousing data of the claim waybill, determine the warehouse into which the claim waybill is received, designate that warehouse as the destination warehouse, and identify the responsible department of that destination warehouse as the responsible party for the claim waybill. Preferably, the destination warehouse can also be directly designated as the responsible party for the claim waybill, and the claim waybill can be sent to the destination warehouse for responsibility determination.

[0158] S406: Determine the responsible party for the claims waybill based on the operational information of the department to which the routing information belongs.

[0159] The department to which the routing information belongs is the department that sent the routing information.

[0160] Based on the operational information of the department to which the routing information belongs, it is determined whether that department has taken action to receive the goods. If the department has not taken action to receive the goods, then that department is identified as the responsible party for the claim waybill. This can be understood as identifying the department to which the latest routing information belongs as the responsible party for the claim waybill. If the department has taken action to receive the goods, it is determined whether that department has taken action to ship the goods. If the department has taken action to ship the goods, then the next department in that department is identified as the responsible party for the claim waybill; if the department has not taken action to ship the goods, then that department is identified as the responsible party for the claim waybill. Furthermore, after identifying the responsible party, the claim waybill can be pushed to that responsible party for confirmation of responsibility.

[0161] Figure 8 The process shown can be understood as the pre-set inference of liability logic for lost claim letters in the rule engine mentioned above. After determining that the claim type of the claim waybill is the lost claim letter type, the liability determination data and the responsible party of the claim waybill can be obtained according to the inference of liability logic in the lost claim letter type.

[0162] When the claim type is damage without a claim letter, the specific process for determining the responsible party on the claim waybill is as follows: Figure 9 The specific details are as follows:

[0163] S501: Based on the successful delivery data in the liability determination data, determine whether the claim waybill has been successfully delivered; if it is determined that the claim waybill has not been successfully delivered, execute S502; if it is determined that the claim waybill has been successfully delivered, execute S505.

[0164] S501 here and Figure 8 The steps in S401 are the same; for detailed instructions on S501, please refer to [link / reference]. Figure 8 The explanation in S401 is omitted here.

[0165] S502: Determine whether the claim waybill is in a return status; if it is determined that the claim waybill is in a return status, execute S503; if it is determined that the claim waybill is not in a return status, execute S504.

[0166] The status of the claim waybill is determined based on its status data. If the status data indicates a return, the claim waybill is considered to be in a return status; otherwise, it is determined that the claim waybill is not in a return status.

[0167] S503: Determine the transit center to which the claim waybill belongs, and designate the transit center as the responsible party for the claim waybill.

[0168] The transit center to which the claim waybill belongs can be understood as the destination TC. The transit center to which the claim waybill belongs can be determined through the distribution information of the claim waybill. After the responsible party is determined, the claim waybill can be pushed to the fast distribution for responsibility identification processing.

[0169] S504: Determine the responsible party based on warehouse information from the claims waybill.

[0170] When it is determined that the claim shipment is not in a return status, the warehouse information on the claim shipment is used to determine whether the destination warehouse is an external warehouse. If the destination warehouse is determined to be an external warehouse, the transit center of the claim shipment needs to be identified and designated as the responsible party for the claim shipment. Furthermore, the transit center can be the destination TC (Trade Center). Here, an external warehouse can be understood as a warehouse that does not belong to the e-commerce platform to which the system belongs. When it is determined that the destination warehouse is not an external warehouse, the destination warehouse can be designated as the responsible party for the claim shipment. It should be noted that a destination warehouse that is not an external warehouse can be understood as the destination warehouse being the warehouse of the e-commerce platform to which the system belongs.

[0171] Furthermore, once the responsible party is identified, the claim waybill can be sent to that party for accountability processing.

[0172] S505: Obtain the latest routing information for the claim waybill.

[0173] S506: Based on routing information, determine whether the status of the claim waybill is in the warehouse entry status; if it is determined that the status of the claim waybill is in the warehouse entry status, execute S507; if it is determined that the status of the claim waybill is not in the warehouse entry status, execute S508.

[0174] S507: Determine the warehouse to which the claim waybill is received, and designate the responsible department of the warehouse as the party responsible for the claim waybill.

[0175] S508: Determine the responsible party for the claims waybill based on the operational information of the department to which the routing information belongs.

[0176] The process from S505 to S508 here is related to... Figure 8 The processes from S403 to S406 are consistent; for details, please refer to [link / reference]. Figure 8 The explanations of S403 to S406 will not be repeated here.

[0177] Figure 9 The process shown can be understood as the pre-set inference of liability logic for damage without a claim letter in the damage rule engine mentioned above. After determining that the claim type of the claim bill is the damage without a claim letter type, the liability determination data and the responsible party of the claim bill can be obtained according to the inference of liability logic in the damage without a claim letter type.

[0178] and Figure 1 Corresponding to the method shown, this embodiment of the invention provides a claims settlement device, which is used to support... Figure 1 The method shown can be implemented in real life using a device that can be installed in a computer terminal or a smart terminal. A schematic diagram of the device can be found in [reference needed]. Figure 10 As shown, the specific explanation is as follows:

[0179] The first acquisition unit 601 is used to acquire the claim waybill in the claim initiation request in response to the claim initiation request;

[0180] The first determining unit 602 is used to determine the abnormality type and waybill number of the claim waybill when the waybill type of the claim waybill is TC waybill;

[0181] The second determining unit 603 is used to determine claim data in the quality control system based on the anomaly type and the waybill number, and to determine the claim type of the claim waybill based on the claim data. The claim type is one of the following: a claim letter type, a claim letter-damaged type, and a claim letter-lost type.

[0182] The second acquisition unit 604 is used to acquire the liability determination data of the claim waybill based on the claim type, and determine the responsible party of the claim waybill based on the liability determination data.

[0183] In the apparatus provided by this invention, in response to a claim initiation request, the device obtains the claim waybill from the claim initiation request; when the waybill type of the claim waybill is a TC waybill, the device determines the anomaly type and waybill number of the claim waybill; based on the anomaly type and waybill number, the device determines the claim data in the quality control system, and based on the claim data, determines the claim type to which the claim waybill belongs, which is one of the following: claim letter type, damage without claim letter type, and loss without claim letter type; the device obtains the liability determination data corresponding to the claim type in the claim waybill, and determines the liable party of the claim waybill based on the liability determination data. This invention first obtains the claim waybill from the claim initiation request, determines the claim data based on the anomaly type and waybill number of the claim waybill, determines the claim type to which the claim waybill belongs based on the claim data, obtains the liability determination data corresponding to the claim type in the claim waybill, and then determines the liable party of the claim waybill based on the liability determination data. The entire process reduces the degree of manual intervention, effectively shortens the time required to determine the liable party, thereby improving the efficiency of liability judgment and claims settlement.

[0184] In another embodiment of the present invention, the second acquisition unit 604 includes:

[0185] The first judgment subunit is used to determine whether the creation of the claim waybill has timed out based on the claim creation information in the liability determination data;

[0186] The first determining subunit is used to determine the department that created the claim letter as the responsible party for the claim waybill if it is determined that the creation of the claim waybill has timed out.

[0187] The first acquisition subunit is used to acquire the cancellation data in the liability determination data if it is determined that the creation of the claim waybill has not expired, and to determine whether the claim waybill has been cancelled within the time limit.

[0188] The second determining subunit is used to determine the claims negotiation post as the responsible party for the claims waybill if it is determined that the claims waybill was cancelled within the time limit.

[0189] The second acquisition subunit is used to acquire the responsible unit information of the claim waybill if it is determined that the claim waybill was not cancelled within the time limit, and to determine the responsible object of the claim waybill based on the responsible unit information.

[0190] In another embodiment of the present invention, the first acquisition subunit includes:

[0191] The first judgment module is used to determine whether the offset data is empty;

[0192] The first determining module is used to determine that the claim waybill has not been cancelled within the time limit when the cancellation data is determined to be empty.

[0193] The first acquisition module is used to obtain the planned closing time and creation time of the claim waybill's cancellation document from the cancellation data when it is determined that the cancellation data is not empty;

[0194] The second judgment module is used to determine whether the creation time is earlier than the planned shutdown time;

[0195] The second determining module is used to determine that the claim waybill is cancelled within the time limit if the creation time is earlier than the planned closing time; otherwise, it is determined that the claim waybill is not cancelled within the time limit.

[0196] In another embodiment of the present invention, the second acquisition unit 604 includes:

[0197] The second judgment subunit is used to determine whether the claim waybill has been successfully delivered based on the successful delivery data in the liability determination data;

[0198] The third acquisition subunit is used to acquire the business data of the claim waybill when it is determined that the claim waybill has not been delivered, and to determine the responsible party of the claim waybill based on the business data.

[0199] The fourth acquisition subunit is used to acquire the latest routing information of the claim waybill when it is determined that the claim waybill has been successfully delivered;

[0200] The third judgment subunit is used to determine whether the status of the claim waybill is in the warehouse entry status based on the routing information.

[0201] The third determining subunit is used to determine the warehouse into which the claim waybill is received when the waybill status is determined to be warehouse entry status, and to determine the responsible department of the warehouse as the responsible party of the claim waybill.

[0202] The fourth determining subunit is used to determine the responsible party of the claim waybill based on the operation information of the department to which the routing information belongs when the waybill status of the claim waybill is determined to be not in the warehouse status.

[0203] In another embodiment of the present invention, the second acquisition unit 604 includes:

[0204] The fourth judgment subunit is used to determine whether the claim waybill has been successfully delivered based on the successful delivery data in the liability determination data;

[0205] The fifth judgment subunit is used to determine whether the claim waybill is in a return status when it is determined that the claim waybill has not been properly delivered.

[0206] The fifth determining subunit is used to determine the transit center to which the claim waybill belongs when it is determined that the claim waybill is in a return status, and to determine the transit center as the responsible party of the claim waybill;

[0207] The sixth determining subunit is used to determine the responsible party based on the warehouse information of the claim waybill when it is determined that the claim waybill is not in a return status;

[0208] The fifth acquisition subunit is used to acquire the latest routing information of the claim waybill when it is determined that the claim waybill has been successfully delivered;

[0209] The sixth judgment subunit is used to determine, based on the routing information, whether the status of the claim waybill is in the warehouse entry status;

[0210] The seventh determining subunit is used to determine the warehouse to which the claim waybill is received when the waybill status is determined to be warehouse entry status, and to determine the responsible department of the warehouse as the responsible party of the claim waybill;

[0211] The eighth determining subunit is used to determine the responsible party of the claim waybill based on the operation information of the department to which the routing information belongs when the waybill status of the claim waybill is determined to be not in the warehouse status.

[0212] This invention also provides a storage medium, which includes stored instructions, wherein the execution of the instructions controls the device where the storage medium is located to perform the above-described claims settlement method.

[0213] This invention also provides an electronic device, the structural schematic of which is shown below. Figure 11 As shown, it specifically includes a memory 701 and one or more instructions 702, wherein one or more instructions 702 are stored in the memory 701 and are configured to be executed by one or more processors 703 to perform the above-mentioned claims settlement method.

[0214] The specific implementation processes and derivative methods of the above embodiments are all within the protection scope of this invention.

[0215] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0216] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0217] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for determining liability in claims settlement, characterized in that, include: In response to a claim initiation request, obtain the claim waybill from the claim initiation request; When the waybill type of the claim waybill is TC waybill, determine the abnormality type and waybill number of the claim waybill; Based on the anomaly type and the waybill number, claim data is determined in the quality control system, and based on the claim data, the claim type of the claim waybill is determined. The claim type is one of the following: with claim letter, damaged without claim letter, or lost without claim letter. Based on the claim type, obtain the liability determination data of the claim waybill, and determine the liable party of the claim waybill based on the liability determination data; The "claim letter type" refers to the claim type when the abnormality type of the claim waybill is one of the following: whole shipment lost / incomplete package, damaged outside and missing inside, damaged outside, damaged outside and damaged inside, and the corresponding claim data is not empty and the claim data is in one of the following states: initial, acknowledged responsibility, or closed. The "no claim letter loss type" refers to the claim type when the abnormal type of the claim waybill is one of the following: whole shipment lost / incomplete package, or damaged outside and missing inside; the corresponding claim data is either empty and the claim data status is one of the following: initial, acknowledged responsibility, or closed; or the claim type when the abnormal type of the claim waybill is damaged outside and missing inside. The "no claim letter damage type" refers to the claim type when the abnormality type of the claim waybill is either external damage or external / internal damage, and the corresponding claim data is either empty and in one of the following states: initial, acknowledged responsibility, or closed; or the claim type when the abnormality type of the claim waybill is external good and internal damage.

2. The method according to claim 1, characterized in that, When the claim type is a claim letter type, determining the liable party of the claim waybill based on the liability determination data includes: Based on the claim creation information in the liability determination data, determine whether the claim waybill creation timed out; If it is determined that the creation of the claim waybill has timed out, the department that created the claim letter will be identified as the responsible party for the claim waybill. If it is determined that the creation of the claim waybill has not expired, then the cancellation data in the liability determination data is obtained to determine whether the claim waybill has been cancelled within the time limit; If it is determined that the claim waybill was cancelled within the time limit, then the claims negotiation post will be identified as the responsible party for the claim waybill. If it is determined that the claim waybill was not cancelled within the time limit, the responsible unit information of the claim waybill is obtained, and the responsible party of the claim waybill is determined based on the responsible unit information.

3. The method according to claim 2, characterized in that, The step of obtaining the reversal data from the liability determination data and determining whether the claim waybill was reversed within the time limit includes: Determine whether the reversal data is empty; When it is determined that the cancellation data is empty, it is determined that the claim waybill was not cancelled within the time limit; When it is determined that the reversal data is not empty, the planned closing time and creation time of the reversal document of the claim waybill are obtained from the reversal data; Determine whether the creation time is earlier than the planned shutdown time; If the creation time is determined to be earlier than the planned closure time, the claim waybill is determined to be cancelled within the time limit; otherwise, the claim waybill is determined not to be cancelled within the time limit.

4. The method according to claim 1, characterized in that, When the claim type is damage without a claim letter, the determination of the responsible party for the claim waybill based on the liability determination data includes: Based on the successful delivery data in the liability determination data, it is determined whether the claim waybill has been successfully delivered; When it is determined that the claim waybill has not been delivered, the business data of the claim waybill is obtained, and the responsible party of the claim waybill is determined based on the business data; Once it is determined that the claim waybill has been successfully delivered, obtain the latest routing information for the claim waybill; Based on the routing information, determine whether the status of the claim waybill is in the warehouse entry status; When the status of the claim waybill is determined to be "warehouse entry", the warehouse into which the claim waybill is entered is determined, and the department responsible for that warehouse is determined as the responsible party for the claim waybill. When it is determined that the status of the claim waybill is not in the warehouse entry status, the responsible party for the claim waybill is determined based on the operation information of the department to which the routing information belongs.

5. The method according to claim 1, characterized in that, When the claim type is "no claim letter lost", the step of determining the responsible party for the claim waybill based on the liability determination data includes: Based on the successful delivery data in the liability determination data, it is determined whether the claim waybill has been successfully delivered; When it is determined that the claim waybill has not been delivered, it is determined whether the claim waybill is in a return status; When it is determined that the claim waybill is in a return status, the transit center to which the claim waybill belongs is identified, and the transit center is identified as the responsible party for the claim waybill; When it is determined that the claim waybill is not in a return status, the responsible party is determined based on the warehouse information of the claim waybill; Once it is determined that the claim waybill has been successfully delivered, obtain the latest routing information for the claim waybill; Based on the routing information, determine whether the status of the claim waybill is in the warehouse entry status; When the status of the claim waybill is determined to be "warehouse entry", the warehouse into which the claim waybill is entered is determined, and the department responsible for the warehouse is determined as the responsible party for the claim waybill. When it is determined that the status of the claim waybill is not in the warehouse entry status, the responsible party for the claim waybill is determined based on the operation information of the department to which the routing information belongs.

6. A claims settlement and liability determination device, characterized in that, include: The first acquisition unit is used to acquire the claim waybill in the claim initiation request in response to the claim initiation request; The first determining unit is used to determine the abnormality type and waybill number of the claim waybill when the waybill type of the claim waybill is a TC waybill; The second determining unit is used to determine claim data in the quality control system based on the anomaly type and the waybill number, and to determine the claim type of the claim waybill based on the claim data. The claim type is one of the following: with claim letter, without claim letter, damaged, or without claim letter. The "with claim letter" type refers to a claim waybill whose anomaly type is one of the following: lost / incomplete package, damaged exterior / incomplete interior, damaged exterior, or damaged exterior / damaged interior, and the corresponding claim data is not empty and the claim data is in one of the following states: initial, acknowledged responsibility, or closed. The "without claim letter" type refers to a claim waybill whose anomaly type is... When the claim type is one of the following: lost shipment / incomplete package, damaged exterior but missing interior, the corresponding claim data is in a state other than empty and the claim data status is in an initial, acknowledged, or closed state; or the claim type when the claim waybill's anomaly type is damaged exterior but missing interior; the "no claim letter" damage type refers to the claim type when the claim waybill's anomaly type is one of damaged exterior or damaged exterior but internal, the corresponding claim data is in a state other than empty and the claim data status is in an initial, acknowledged, or closed state; or the claim type when the claim waybill's anomaly type is damaged exterior but internal. The second acquisition unit is used to acquire the liability determination data of the claim waybill based on the claim type, and determine the responsible party of the claim waybill based on the liability determination data.

7. The apparatus according to claim 6, characterized in that, The second acquisition unit includes: The first judgment subunit is used to determine whether the creation of the claim waybill has timed out based on the claim creation information in the liability determination data; The first determining subunit is used to determine the department that created the claim letter as the responsible party for the claim waybill if it is determined that the creation of the claim waybill has timed out. The first acquisition subunit is used to acquire the cancellation data in the liability determination data if it is determined that the creation of the claim waybill has not expired, and to determine whether the claim waybill has been cancelled within the time limit. The second determining subunit is used to determine the claims negotiation post as the responsible party for the claims waybill if it is determined that the claims waybill was cancelled within the time limit. The second acquisition subunit is used to acquire the responsible unit information of the claim waybill if it is determined that the claim waybill was not cancelled within the time limit, and to determine the responsible object of the claim waybill based on the responsible unit information.

8. The apparatus according to claim 7, characterized in that, The first acquisition subunit includes: The first judgment module is used to determine whether the offset data is empty; The first determining module is used to determine that the claim waybill has not been cancelled within the time limit when the cancellation data is determined to be empty. The first acquisition module is used to obtain the planned closing time and creation time of the claim waybill's cancellation document from the cancellation data when it is determined that the cancellation data is not empty; The second judgment module is used to determine whether the creation time is earlier than the planned shutdown time; The second determining module is used to determine that the claim waybill is cancelled within the time limit if the creation time is earlier than the planned closing time; otherwise, it is determined that the claim waybill is not cancelled within the time limit.

9. A computer-readable storage medium, characterized in that, The storage medium includes stored instructions, wherein, when the instructions are executed, the device containing the storage medium is controlled to perform the claims determination method as described in any one of claims 1 to 5.

10. An electronic device, characterized in that, It includes a memory, and one or more instructions, wherein one or more instructions are stored in the memory and configured to be executed by one or more processors as described in any one of claims 1 to 5.

Images