WO2019019777A1 - Procédé et appareil de traitement de retrait de prime de police d'assurance, dispositif informatique et support de stockage - Google Patents
Procédé et appareil de traitement de retrait de prime de police d'assurance, dispositif informatique et support de stockage Download PDFInfo
- Publication number
- WO2019019777A1 WO2019019777A1 PCT/CN2018/087294 CN2018087294W WO2019019777A1 WO 2019019777 A1 WO2019019777 A1 WO 2019019777A1 CN 2018087294 W CN2018087294 W CN 2018087294W WO 2019019777 A1 WO2019019777 A1 WO 2019019777A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- value
- invoice
- refund
- invoice data
- identifier
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Definitions
- the application relates to a policy refunding method, device, computer device and storage medium.
- Insurance companies need to deal with a large number of insurance orders every day. In the daily business process, customers often cancel some or all of the policies in the policy period after the purchase of the policy, and apply for the policy refund.
- the invoice data corresponding to the policy Before the insurance company refunds the policy, in addition to the financial accounting treatment of the refund policy, the invoice data corresponding to the policy must be offset against the refund amount. Generally, when the invoice data is offset, the staff member is required to contact the corresponding customer according to the policy, and the invoice data that has been sent to the customer is retrieved, and then the invoice data corresponding to the actual remaining amount of the policy is manually re-issued.
- the refund operation can only be carried out after the completion of the invoicing data.
- the processing of refunds largely depends on the speed at which the customer returns the invoice data, and the invoice data needs to be manually verified and entered one by one. Therefore, the current policy of reimbursement of the policy is long and the work efficiency is low, and the customer's refund application cannot be effectively processed in time.
- a method for processing a policy refund including:
- a refund instruction is generated and sent to the security terminal.
- a policy for refunding a policy comprising:
- the refund request receiving module is configured to receive a policy refund request sent by the security terminal, where the policy refund request carries the policy number and the refund value;
- a first invoice finding module configured to search for invoice data with a first identifier associated with the policy number, and obtain a valid value of the invoice data having the first identifier
- a first invoice extraction module configured to acquire, according to the valid value and a preset extraction rule, invoice data that the sum of valid values in the invoice data having the first identifier is greater than or equal to the refund value;
- a deduction value calculation module configured to calculate a deduction value of each of the extracted invoice data according to a difference between the sum of the valid value and the refund value
- a second invoice generating module configured to input the deduction value of each invoice data into the invoice template having the second identifier to generate invoice data having the second identifier, and send the invoice data with the second identifier to the ticketing Terminal;
- the refund instruction generating module is configured to: after deducting the deductible value from the valid value of each of the extracted invoice data, generate a refund instruction and send the reimbursement instruction to the security terminal.
- a computer device comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by the processor, implement the steps of the policy refund processing method provided in any one of the embodiments of the present application .
- One or more non-transitory computer readable instruction storage media storing computer readable instructions, when executed by one or more processors, causing one or more processors to implement any one embodiment of the present application The steps in the policy for processing the policy refund.
- FIG. 1 is an application environment diagram of a policy for refunding a policy in accordance with one or more embodiments.
- FIG. 2 is a flow diagram of a policy for processing a policy refund in accordance with one or more embodiments.
- FIG. 3 is a block diagram showing the structure of a policy refund processing device in accordance with one or more embodiments.
- FIG. 4 is a schematic structural diagram of a policy for refunding a policy in another embodiment.
- FIG. 5 is a block diagram of a computer device in accordance with one or more embodiments.
- the application testing method provided in the embodiment of the present application can be applied to an application environment as shown in FIG. 1.
- the server 102 of the financial system is connected to the security terminal 104 and the ticketing terminal 106 via a network, respectively.
- the security terminal 104 is used for unified management of the user's insurance order.
- the security terminal 104 stores the policy information.
- the security terminal 104 receives the user's refund request for the cancelled policy, the security terminal 104 forwards the policy number and the refund amount to the server 102.
- the value of the policy refund request after receiving the policy refund request sent by the security terminal 104, the server 102 searches for the invoice data with the first identifier associated with the policy number, and extracts from the valid data of the invoice data and the preset extraction rule.
- the invoice data of the refunded value requirement, the deductible value of the extracted invoice data is calculated, the deductible value is input into the invoice template having the second identifier, and the invoice data with the second identifier is generated and sent to the ticket terminal 106, and the ticket terminal 106
- the invoice data is printed after the invoice data is received.
- the server 102 deducts the extracted invoice data
- the generated refund instruction is sent to the security terminal 104, and the security terminal 104 receives the refund instruction and then refunds the user.
- a policy for processing a policy for refunding a fee is provided.
- the method is applicable to a terminal or a server, and the method is applied to the server as an example.
- the method includes the following steps:
- Step 210 Receive a policy refund request sent by the security terminal, where the policy refund request carries the policy number and the refund value.
- the customer can cancel the insurance order that has been insured. If the insurance order contains multiple insurances, the customer can choose to cancel all or part of the insurance policy in the insurance order and apply for a refund from the insurance company. Before the insurance company refunds the fee to the customer, it needs to rush the original invoice as a tax payment receipt.
- the customer can fill out the refund application online, or apply for surrender to the agent, secure the terminal to obtain the customer's refund request, generate a policy refund request according to the refund information in the refund application, and send the policy refund request to the server.
- the policy refund request carries the policy number of the refund policy that the customer applies for, and the value of the amount of the insurance that the customer cancels the insurance, that is, the refund value.
- the policy refund request may also include information such as user information, application refund time, policy data, and the like.
- the server receives the policy refund request sent by the security terminal, and obtains the policy number and the refund value from the policy refund request.
- Step 220 Find invoice data with the first identifier associated with the policy number, and obtain a valid value of the invoice data with the first identifier.
- the invoice data with the first identification is the invoice data of the positive value, which is the data of the so-called blue invoice.
- the invoice data with the second identification mentioned below is the negative value of the invoice data, that is, the data of the generally described red-letter invoice.
- the server can determine whether the invoice data is a positive or negative value by determining whether the invoice identifier in the invoice data is the first identifier or the second identifier.
- the server When the customer insured, the server generates the invoice data with the first identifier whose ticket value is the same as the amount value according to the amount value in the customer's insurance policy, and stores the generated invoice data of the positive value in association with the customer's insurance policy.
- the server sends the generated invoice data with the first identification to the ticket terminal, and the ticket terminal prints two copies of the invoice data with the first identification, one for the insurance company and the other for the customer.
- the insurance company needs the customer to send the invoice data with the first identification to the insurance company before the refund, and the insurance company re-issues the invoice data with the first identification to the customer according to the remaining amount of the policy.
- the server searches for the invoice data with the first identifier stored in association with the policy number according to the read policy number.
- the number of the invoice data with the first identifier may be one or more.
- the server obtains valid values for each invoice data. It should be noted that the valid value here is not necessarily equal to the face value of the invoice data, and the valid value may be smaller than the face value, because some invoice data with the first identifier may be deducted.
- the server searches for the policy data according to the policy number, obtains the insurance type information in the policy data, and determines the tax rate of the invoice to be invoiced according to the insurance type information, and the server stores the found in association with the policy number.
- the invoice data with the first identifier is selected to be invoice data consistent with the invoiced tax rate, the valid value of the filtered invoice data is obtained, and the selected invoice data is subjected to the following steps.
- Step 230 Acquire, according to the valid value and the preset extraction rule, the invoice data in which the sum of the valid values in the invoice data having the first identifier is greater than or equal to the refund value.
- the server extracts the invoice data from all the invoice data of the first identifier according to the valid value of each invoice data read, according to a preset extraction rule, and the sum of the valid values of the extracted invoice data needs to be greater than or equal to the refund value.
- the step of extracting the invoice data according to the valid value and the preset extraction rule specifically includes: acquiring a generation time of each invoice data in the invoice data having the first identifier, and invoking the invoice data in a first to last order according to the generation time. Sorting; comparing the valid value of the invoice data in the first place with the refund value; when the valid value of the invoice data ranked first is less than the refund value, calculating the invoice data ranked first and the next one The sum of the valid values of the invoice data; when the sum of the valid values is less than the refund value, the valid value of the invoice data of the next digit is added to the sum of the valid values until the sum of the calculated valid values is greater than or equal to the refund value.
- the invoice data for the valid numerical sum calculation is extracted from the invoice data with the first identification.
- the server reads the generation time in each invoice data, and sorts each invoice data in order of generation time from first to last. After the sorting is completed, the server first compares the valid value of the invoice data ranked first with the refund value. When the valid value of the invoice data in the first place is greater than or equal to the refund value, the server directly extracts the invoice data in the first place. When the valid value of the invoice data in the first place is less than the refund value, the server calculates the sum of the valid values of the invoice data ranked in the first two digits, and the sum of the valid values of the invoice data ranked in the first two digits and the refund value.
- the server For comparison, when the sum of the effective values is less than the refund value, the server continues to calculate the sum of the valid values of the invoice data ranked in the top three, compares the calculated sum of the valid values with the refund value, and so on, until the server When it is calculated that the sum of the effective values ranked in the first N digits is greater than or equal to the refund value, the server extracts the invoice data ranked in the first N digits from the invoice data having the first identifier.
- the server may also perform invoice data extraction from the invoice data having the first identification according to other preset extraction rules.
- the server sorts the invoice data according to the read valid values in descending order, first comparing the maximum valid value with the refund value, and when the maximum valid value is greater than or When it is equal to the refund value, the invoice data with the largest effective value is extracted from the invoice data with the first identifier.
- the maximum effective value is less than the refund value, the calculated value is the sum of the first two valid values, the sum of the calculated valid values is compared with the refund value, and so on, until the server calculates the value.
- the invoice data of the first N digits is extracted from the invoice data having the first identifier.
- the invoice data is sorted according to the order of the effective values from small to large, the number of calculations of the server can be reduced, and the invoice data satisfying the refund value can be extracted most quickly.
- the server may also sort the invoice data in the order of the generation time from the back to the top, or may randomly sort the invoice data, and is not limited to the extraction rule in the foregoing embodiment.
- Step 240 Calculate the deducted value of each invoice data extracted according to the sum of the valid values and the refund value.
- the server also sorts the extracted invoice data in the sorted order before extraction.
- the server calculates the numerical difference between the sum of the valid values of the invoice data extracted and the refund value, and determines the deductible value of each invoice data that needs to be refunded according to the numerical difference.
- the effective value of each invoice data is the deductible value.
- the numerical difference is greater than 0, the value obtained by subtracting the numerical difference from the valid value of the last invoice data is used as the deductible value of the last invoice data, and the valid value of the other invoice data is It deducts the value.
- Step 250 Enter the deduction data of each invoice data into the invoice template having the second identifier to generate the invoice data with the second identifier, and send the invoice data with the second identifier to the ticket terminal.
- the server obtains the invoice template with the second identifier, and the number of invoice data with the second identifier acquired by the server is equal to the number of the invoice data with the first identifier extracted.
- Each invoice template contains the second identifier and contains all the fields of the negative value invoice, and the common fields have been filled in, such as insurance company information: payee taxpayer identification number, address, phone number, bank account number, etc.
- Each invoice template has a unique invoice code and invoice number that is consistent with the blank invoice issued by the tax office.
- the server obtains the current date, enters the current date into the billing date field of each invoice, and the server obtains the customer name, the insurance product name from the policy refund request, and inputs the customer name, the insurance product name, and the refund value into the corresponding fields.
- the lowercase number ie, Arabic numerals
- uppercase numbers ie, Chinese characters
- the field values for each field in the invoice template are automatically verified. Specifically, the server detects whether there is an empty field, and whether the data format of the field value is consistent with the preset data format, and the data format includes a data type, a data length, and the like.
- the server transmits the generated invoice data with the second identifier to the ticket terminal, so that the ticket terminal prints the invoice data with the second identifier.
- the server pair identifies the empty field, and obtains the field value corresponding to the empty field, and inputs the obtained field value.
- the server sends the generated invoice template with the second identifier to the auditing terminal, and after receiving the modified invoice template returned by the auditing terminal, the modified invoice is modified.
- the template is sent to the ticket terminal for printing, and the generated invoice data with the second identifier is associated with the policy number after the printing is completed.
- Step 260 After deducting the deductible value from the valid values of the extracted invoice data, generate a refund instruction and send it to the security terminal.
- the server modifies the valid value of each invoice data extracted, and modifies the valid value to the value after deducting the deductible value.
- the server generates a refund instruction, and sends the refund instruction to the security terminal, so that the security terminal performs the refund operation according to the refund instruction.
- the server when the valid value of the invoice data is 0, the invoice data is invalidally marked, and in the subsequent process of finding the policy-associated invoice, the server automatically masks the invoice data with the first identifier that is invalidated.
- the server extracts the sum of the valid values according to the valid value of the invoice data with the first identifier and the preset extraction rule by searching the invoice data with the first identifier associated with the policy number in the policy refund request.
- the invoice data with the same fee value generates the invoice data with the second identifier according to the extracted invoice data, and sends the invoice data with the second identifier to the ticket terminal for printing, and deducts the valid value from the extracted invoice data.
- the refund instruction is generated and returned to the security terminal for sending the request, thereby automatically generating the invoice data with the second identifier equal to the refund amount, and automatically deducting the invoice amount, thereby realizing the policy refund request.
- Automated processing eliminates the need for manual operations and increases processing efficiency. In addition, there is no need for the customer to return the invoice that has been issued, to increase the processing speed of the policy refund request and shorten the processing cycle.
- the policy for refunding the policy further includes: when the calculated sum of the valid values of all the invoice data in the invoice data having the first identifier is less than the refund value, respectively inputting the valid values of the invoice data into the second Generating the invoice data with the second identifier in the identified invoice template; sending the invoice data with the second identifier to the ticket terminal, so that the ticket terminal prints the invoice data with the second identifier; the sum of the valid values of all the invoice data After the difference between the refunded value and the policy number is recorded, the refund instruction is generated and sent to the security terminal, so that the security terminal performs the refund operation according to the refund instruction.
- the server When the sum of the valid values of all the invoice data in the invoice data with the first identifier calculated by the server is less than the refund value, the invoice data with the first identifier associated with the policy number cannot meet the invoice deduction requirement of the refund value. This is because the customer is currently paying but has not yet issued an invoice.
- the server In order to return the refund amount to the customer in time, the server first deducts the associated invoice data with the first identifier, and performs the difference between the sum of the valid values of the existing invoice data and the refund amount and the policy number. Recording, in the subsequent business process, when the new invoice data with the first identifier is obtained, the difference portion is deducted.
- the server inputs the valid values of all the invoice data one by one into the invoice template with the second identifier processed by the processing method of the above embodiment, generates the invoice data with the second identifier, and sends the invoice data to the invoice data to enable
- the ticket terminal prints the invoice data, and associates the printed invoice data with the second identifier with the policy number.
- the server records the difference between the sum of the valid values of all the invoice data and the refund value and the policy number, and invalidates all the invoice data with the first identifier.
- the server generates a refund instruction and sends it to the security terminal, so that the security terminal performs the refund operation according to the refund instruction.
- the server when the invoice data with the first identifier associated with the policy number cannot meet the invoice deduction requirement of the refund value, the server first generates the second identifier according to the existing invoice data with the first identifier. Invoice data, and deduct the invoice data with the first identification, record the difference part and the policy number, so that the part of the invoice deductible can be recorded, and the refund instruction can be sent to the security terminal after the recording is completed. Reimbursement to customers in a timely manner to minimize customer waiting time.
- the policy for refunding the policy further includes: when the found effective value of the invoice data with the first identifier associated with the policy number is zero, the association between the refund value and the policy number Generating a refund instruction and sending it to the security terminal; receiving an invoice request request sent by the security terminal, inputting the request value in the invoice request request into the invoice template having the first identifier, and generating the invoice data having the first identifier; in the invoice request request
- the policy number is the same as the policy number in the policy refund request, and the request value is greater than the refund value
- the refund value is input into the invoice template with the second identifier to generate the invoice data with the second identifier, and the request value is The difference in the refund value is used as the valid value of the generated invoice data with the first identifier.
- the server After the server receives the policy refund request, when the invoice data with the first identifier associated with the policy number is not found, it indicates that the insurance order corresponding to the policy number has not been invoiced, so there is no need to perform the deduction of the invoice data, the server The refund instruction is sent directly to the terminal, so that the security terminal performs the refund operation.
- the server finds the invoice data with the first identifier associated with the policy number, but the found invoice data has an invalid flag, that is, when the valid value of the invoice data is zero, the server will refund the refund value in the policy refund request. Record the association with the policy number and send a refund instruction directly to the security terminal, so that the security terminal can perform the refund operation, so that the customer can get the refund as soon as possible.
- the server when the server receives the invoice request request sent by the security terminal, the invoice application request carries the request value, and the server obtains the invoice data with the first identifier, that is, the invoice template of the positive value invoice data, having
- the invoice template of the first identifier contains all the fields of the first identifier and contains the positive value invoice, and the common fields therein have been filled in, the common fields such as the information of the insurance company: the payee taxpayer identification number, address, telephone, Bank account number, etc.
- Each invoice template has a unique invoice code and invoice number that is consistent with the blank invoice issued by the tax office.
- the server obtains the current date, inputs the current date into the billing date field in the invoice template with the first identifier, and the server obtains the customer name, the insurance product name, and the customer name, the insurance product name, and the refund value corresponding to the invoice request request.
- the lowercase number ie, Arabic numerals
- uppercase numbers ie, Chinese characters
- the field values for each field in the invoice template are automatically verified. Specifically, the server detects whether there is an empty field, and whether the data format of the field value is consistent with the preset data format, and the data format includes a data type, a data length, and the like.
- the server transmits the generated invoice data having the first identification to the ticket terminal, so that the ticket terminal prints the invoice data having the first identification.
- the server pair identifies the empty field, and obtains the field value corresponding to the empty field, and inputs the obtained field value.
- the server sends the generated invoice template with the first identifier to the auditing terminal, and after receiving the modified invoice template returned by the auditing terminal, the modified invoice is modified.
- the template is sent to the ticket terminal for printing, and the generated invoice data with the first identifier is associated with the policy number in the invoice request request after the printing is completed.
- the server When the server finds that the policy number in the invoice request request has an associated refund value record, and the policy number in the invoice request request matches the policy number in the policy refund request, the server will request the value and the recorded refund value. Comparing, when the request value is greater than the refund value, the generated invoice data with the first identifier satisfies the refund request in the policy refund request, the server obtains the invoice template with the second identifier and inputs the refund value, and the input refund After processing the invoice template with the second identification of the fee value, invoice data with the second identification is generated. The generated invoice data with the second identifier is associated with the policy number, and the refund value of the record associated with the policy number is cleared. The server sends the generated invoice data with the second identifier to the ticket terminal for invoice printing. The server will modify the valid value of the invoice data with the first identifier generated according to the invoice request request, and modify it to the difference between the requested value and the refund value.
- the server compares the request value with the recorded refund value
- the request value is input into the invoice template having the second identifier to generate the invoice data having the second identifier. Record the difference between the refunded value and the requested value and the policy number.
- the server acquires the invoice template with the second identifier and inputs the request value, and processes the invoice template with the second identifier inputting the refund value to generate the invoice data with the second identifier.
- the generated invoice data with the second identification is associated with the policy number, and the generated invoice data with the first identification is marked as invalid.
- the server sends the generated invoice data with the second identifier to the ticket terminal for invoice printing.
- the server modifies the refund value associated with the policy number and modifies it to the difference between the refund value and the requested value.
- the customer when the invoice data with the first identifier existing in the policy number cannot meet the refund deduction demand, the customer first refunds the fee, and the difference between the refund and the policy number of the deductible operation is performed.
- Correlation record when the policy number is associated with the new invoice data with the first identifier, the new invoice data with the first identifier is deducted according to the recorded refund amount difference, so that the customer obtains the refund as soon as possible. At the same time, the tax record can be realized.
- the method further includes: searching for policy data corresponding to the policy number in the invoice request request, determining whether the policy data is merged policy data; and when the policy data is merged In the policy data, the step of inputting the request value in the invoice request request into the invoice template having the first identifier to generate the invoice data having the first identifier includes: obtaining the customer name in the policy data and the insured value corresponding to the customer name And invoking the insured value corresponding to each customer name and each customer name into the invoice template having the first identifier to generate the invoice data having the first identifier.
- the server After receiving the invoice request request, the server obtains the policy number in the invoice request request and finds the policy data corresponding to the policy number.
- the policy data can be stored locally on the server, and the server can be obtained locally; the policy data can also be stored on the security terminal, and the server sends the policy data request carrying the policy number to the security terminal, and the security terminal returns the policy data corresponding to the policy number to the server. .
- the server obtains the customer name of the policy data, and judges whether the policy data is a combined policy according to the number of the customer name. When the number of customer names is single, the policy is a non-consolidated policy; when the number of customer names is multiple, the policy is a consolidated policy. When the policy is a merged policy, the server obtains an invoice target with the first identifier equal to the customer name, and inputs each customer name in the policy data and its corresponding insurance value into the invoice data with the first identifier, and insures the input. After the value of the invoice template with the first identification is processed, the invoice data with the first identification is generated.
- the customer name corresponding to the refund value is searched, and the generated first identifier corresponding to the found customer name is generated.
- the invoice data is subjected to the deduction operation as described in the above embodiment, and details are not described herein again.
- the invoice data with the first identification that is inconsistent with the generated customer name corresponding to the refund value is not processed.
- the server when the server receives the policy refund request sent by the security terminal, the policy number in the policy refund request is obtained, and the policy data corresponding to the policy number is searched for. It is judged according to the number of customer names in the policy data whether the policy data is a combined policy. When the number of customer names is only one, the policy is a non-consolidated policy; when the number of customer names is multiple, the policy is a consolidated policy.
- the server obtains the customer name in the policy refund request, and searches for the invoice data with the first identifier associated with the policy number and the customer name is consistent with the customer name in the request, according to the preset
- the extraction rule extracts the invoice data from the invoice data with the first identifier with the same customer name, and performs corresponding deduction operation.
- the policy data corresponding to the policy number in the request is the consolidated policy data
- the invoice data when the invoice data is deducted, the customer name of the application for refund in the merged policy is automatically obtained, only the name of the customer.
- the consistent invoice data with the first identification is deducted, thereby realizing the automatic processing of the invoice deduction operation of the customer consolidation policy.
- steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
- a policy refund processing device comprising:
- the refund request receiving module 310 is configured to receive a policy refund request sent by the security terminal, and the policy refund request carries the policy number and the refund value;
- the first invoice search module 320 is configured to search for invoice data with a first identifier associated with the policy number, and obtain a valid value of the invoice data having the first identifier;
- the first invoice extraction module 330 is configured to obtain, according to the valid value and the preset extraction rule, the invoice data that the sum of the valid values in the invoice data having the first identifier is greater than or equal to the refund value;
- the deduction value calculation module 340 is configured to calculate a deduction value of each invoice data extracted according to a difference between the sum of the valid value and the refund value;
- the second invoice generating module 350 is configured to input the deductible value of each invoice data into the invoice template having the second identifier to generate invoice data having the second identifier, and send the invoice data having the second identifier to the ticket terminal;
- the refund instruction generating module 360 is configured to generate a refund instruction and send it to the security terminal after deducting the deductible value from the valid value of each extracted invoice data.
- the first invoice extraction module 330 further includes:
- An invoice sorting module configured to obtain a generation time of each invoice data in the invoice data with the first identifier, and sort the invoice data in a first-to-last order according to the generation time;
- a numerical comparison module for comparing the valid value of the invoice data ranked first with the refund value
- the invoice calculation extraction module is configured to calculate the sum of the valid value of the invoice data ranked first and the invoice data of the last one when the valid value of the invoice data ranked first is less than the refund value; when the sum of the valid values is less than the return
- the valid value of the invoice data of the next one is added to the sum of the valid values, until the sum of the calculated effective values is greater than or equal to the refund value, the invoice data of the valid value sum calculation is from the first Extracted from the identified invoice data.
- the second invoice generating module 350 is further configured to: when the calculated total invoice data of the invoice data having the first identifier is less than the refund value, input the valid values of the invoice data into the first Generating the invoice data with the second identifier in the invoice template of the second identifier; sending the invoice data with the second identifier to the ticket terminal, so that the ticket terminal prints the invoice data with the second identifier;
- the refund instruction generation module 360 is further configured to generate a refund instruction and send the refund instruction to the security terminal after the difference between the valid value sum of the invoice data and the refund value is associated with the policy number, so that the security terminal is in accordance with the refund instruction. Make a refund.
- the apparatus further includes:
- the refund record recording module 322 is configured to: when the valid value of the invoice data with the first identifier associated with the policy number is found to be zero, the refund value is associated with the policy number, and a refund instruction is generated and sent To the security terminal;
- the invoice request response module 324 is configured to receive an invoice request request sent by the security terminal, and input the request value in the invoice request request into the invoice template having the first identifier to generate invoice data having the first identifier;
- the numerical processing module 326 is configured to: when the policy number in the invoice request request is consistent with the policy number in the policy refund request, and the request value is greater than the refund value, input the refund value into the invoice template having the second identifier.
- the invoice data having the second identification, the difference between the request value and the refund value is used as a valid value of the generated invoice data having the first identifier.
- the value processing module 326 is further configured to: when the request value is less than the refund value, input the request value into the invoice template having the second identifier, generate the invoice data with the second identifier, and refund the refund value and the request. The difference between the values is recorded in association with the policy number.
- the apparatus further comprises: a policy merge determination module for looking up policy data corresponding to the policy number in the invoice request request, and determining whether the policy data is merged policy data.
- the invoice request response module 324 is further configured to obtain a customer name in the policy data and an insurance value corresponding to the customer name, and input the insurance value corresponding to each customer name and each customer name into the Invoice data with the first identification is generated in an identified invoice template.
- the various modules in the above policy refund processing device may be implemented in whole or in part by software, hardware, and combinations thereof.
- Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.
- a computer device which may be a terminal or a server.
- the computer device includes a processor, memory, and network interface coupled by a system bus.
- the processor of the computer device is used to provide computing and control capabilities.
- the memory of the computer device includes a non-volatile storage medium, an internal memory.
- the non-volatile storage medium stores operating systems and computer readable instructions.
- the internal memory provides an environment for operation of an operating system and computer readable instructions in a non-volatile storage medium.
- the network interface of the computer device is used to communicate with an external terminal via a network connection.
- the computer readable instructions are executed by the processor to implement a vulnerability detection method.
- FIG. 5 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
- the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
- a computer device comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by the processor, implement the steps of the policy refund processing method provided in any one of the embodiments of the present application .
- One or more non-transitory computer readable instruction storage media storing computer readable instructions, when executed by one or more processors, causing one or more processors to implement any one embodiment of the present application The steps in the policy for processing the policy refund.
- Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
- Volatile memory can include random access memory (RAM) or external cache memory.
- RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
- SRAM static RAM
- DRAM dynamic RAM
- SDRAM synchronous DRAM
- DDRSDRAM double data rate SDRAM
- ESDRAM enhanced SDRAM
- Synchlink DRAM SLDRAM
- Memory Bus Radbus
- RDRAM Direct RAM
- DRAM Direct Memory Bus Dynamic RAM
- RDRAM Memory Bus Dynamic RAM
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710614431.0A CN107784595A (zh) | 2017-07-25 | 2017-07-25 | 保单退费处理方法、装置、计算机设备及存储介质 |
CN201710614431.0 | 2017-07-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019019777A1 true WO2019019777A1 (fr) | 2019-01-31 |
Family
ID=61437859
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/087294 WO2019019777A1 (fr) | 2017-07-25 | 2018-05-17 | Procédé et appareil de traitement de retrait de prime de police d'assurance, dispositif informatique et support de stockage |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN107784595A (fr) |
WO (1) | WO2019019777A1 (fr) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107784595A (zh) * | 2017-07-25 | 2018-03-09 | 平安科技(深圳)有限公司 | 保单退费处理方法、装置、计算机设备及存储介质 |
CN109471917B (zh) * | 2018-10-11 | 2024-01-26 | 平安科技(深圳)有限公司 | 数据处理方法、装置、设备及介质 |
CN109840852B (zh) * | 2019-01-09 | 2024-03-19 | 中国平安人寿保险股份有限公司 | 一种保单自动处理的方法及相关产品 |
CN110298686B (zh) * | 2019-05-23 | 2024-02-02 | 中国平安人寿保险股份有限公司 | 一种产品返费调配方法、装置、计算机设备及存储介质 |
CN111091468B (zh) * | 2019-11-14 | 2023-08-22 | 泰康保险集团股份有限公司 | 保单数据处理方法及装置、存储介质、电子设备 |
CN113643111B (zh) * | 2021-07-16 | 2024-06-25 | 国网山东省电力公司营销服务中心(计量中心) | 电力营销退费管理系统及方法 |
CN114445164A (zh) * | 2021-12-31 | 2022-05-06 | 北京金堤科技有限公司 | 一种发票数据处理方法和装置,以及存储介质和电子设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008045290A2 (fr) * | 2006-10-04 | 2008-04-17 | David Rudich | Produits et procédés d'assurance vie financés par des primes |
CN105654355A (zh) * | 2015-12-24 | 2016-06-08 | 税友软件集团股份有限公司 | 一种生成发票的方法和设备 |
CN106709770A (zh) * | 2016-12-28 | 2017-05-24 | 深圳市明源软件股份有限公司 | 一种用于增值税销项发票的管理系统及方法 |
CN106886946A (zh) * | 2017-02-24 | 2017-06-23 | 泰康保险集团股份有限公司 | 用于保单退保计算的方法和系统 |
CN107784595A (zh) * | 2017-07-25 | 2018-03-09 | 平安科技(深圳)有限公司 | 保单退费处理方法、装置、计算机设备及存储介质 |
-
2017
- 2017-07-25 CN CN201710614431.0A patent/CN107784595A/zh active Pending
-
2018
- 2018-05-17 WO PCT/CN2018/087294 patent/WO2019019777A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008045290A2 (fr) * | 2006-10-04 | 2008-04-17 | David Rudich | Produits et procédés d'assurance vie financés par des primes |
CN105654355A (zh) * | 2015-12-24 | 2016-06-08 | 税友软件集团股份有限公司 | 一种生成发票的方法和设备 |
CN106709770A (zh) * | 2016-12-28 | 2017-05-24 | 深圳市明源软件股份有限公司 | 一种用于增值税销项发票的管理系统及方法 |
CN106886946A (zh) * | 2017-02-24 | 2017-06-23 | 泰康保险集团股份有限公司 | 用于保单退保计算的方法和系统 |
CN107784595A (zh) * | 2017-07-25 | 2018-03-09 | 平安科技(深圳)有限公司 | 保单退费处理方法、装置、计算机设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN107784595A (zh) | 2018-03-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11663654B2 (en) | System and method for processing transaction records for users | |
WO2019019777A1 (fr) | Procédé et appareil de traitement de retrait de prime de police d'assurance, dispositif informatique et support de stockage | |
US10546351B2 (en) | System and method for automatic generation of reports based on electronic documents | |
US11062132B2 (en) | System and method for identification of missing data elements in electronic documents | |
US9286618B2 (en) | Recognizing and combining redundant merchant designations in a transaction database | |
WO2019052219A1 (fr) | Procédé et appareil de réclamation d'assurance médicale, dispositif informatique, et support d'informations | |
CN115017272B (zh) | 基于登记数据的智能核验方法及装置 | |
US20170169292A1 (en) | System and method for automatically verifying requests based on electronic documents | |
US11138372B2 (en) | System and method for reporting based on electronic documents | |
US20160203564A1 (en) | System and method for consolidating expense records | |
WO2019127889A1 (fr) | Procédé et appareil de vérification de données, dispositif informatique et support d'informations lisible | |
US20180011846A1 (en) | System and method for matching transaction electronic documents to evidencing electronic documents | |
CN112529687A (zh) | 一种贷款、还款记账方法及其装置、设备及存储介质 | |
CN112613952A (zh) | 资质审核方法、装置、计算机设备和存储介质 | |
US20180025225A1 (en) | System and method for generating consolidated data for electronic documents | |
CN111126966A (zh) | 票据审核方法、装置、计算机设备和计算机可读存储介质 | |
KR101697245B1 (ko) | Unique Key를 이용한 해외법인 부가세 자동환급방법 | |
US10387561B2 (en) | System and method for obtaining reissues of electronic documents lacking required data | |
JP6224669B2 (ja) | 入金消込システム、入金消込方法、及びプログラム | |
US20180025438A1 (en) | System and method for generating analytics based on electronic documents | |
US20170323106A1 (en) | System and method for encrypting data in electronic documents | |
US20180137578A1 (en) | System and method for prediction of deduction claim success based on an analysis of electronic documents | |
US20170169519A1 (en) | System and method for automatically verifying transactions based on electronic documents | |
CN110728566B (zh) | 报销文件中数据处理方法、装置、计算机设备和存储介质 | |
US20240311908A1 (en) | Systems and methods for providing digital trusted data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18837329 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18837329 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC , EPO FORM 1205A DATED 04.08.2020. |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18837329 Country of ref document: EP Kind code of ref document: A1 |