WO2019019777A1 - 保单退费处理方法、装置、计算机设备和存储介质 - Google Patents

保单退费处理方法、装置、计算机设备和存储介质 Download PDF

Info

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
Application number
PCT/CN2018/087294
Other languages
English (en)
French (fr)
Inventor
冯超
田正伟
李敏
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019019777A1 publication Critical patent/WO2019019777A1/zh

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)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (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

一种保单退费处理方法，包括：接收保全终端发送的保单退费请求，保单退费请求中携带保单号和退费数值，查找与保单号相关联的具有第一标识的发票数据，获取具有第一标识的发票数据的有效数值，根据有效数值和预设提取规则，获取具有第一标识的发票数据中有效数值总和大于或等于退费数值的发票数据，根据有效数值总和与退费数值计算抽取出的各发票数据的抵扣数值，将各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，从抽取出的各发票数据的有效数值中扣除抵扣数值后生成退费指令。

Description

保单退费处理方法、装置、计算机设备和存储介质
相关申请的交叉引用
本申请要求于2017年07月25日提交中国专利局、申请号为2017106144310、发明名称为“保单退费处理方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请是涉及一种保单退费处理方法、装置、计算机设备及存储介质。
背景技术
保险公司每天都需处理大量的保险订单，在日常的业务过程中，经常会出现客户在购买保单之后，在保险合同的有效期内取消保单中的部分或全部保单，并且申请保单退费的情况。
保险公司在对保单进行退费之前，除了要对退费保单进行财务的记账处理之外，还需对保单对应的发票数据进行与退费金额相对应的抵充处理。一般地，在对发票数据进行抵充处理时，需要工作人员根据保单联系相应的客户，将已寄送给客户的发票数据取回后，再人工重新开具与保单实际剩余金额相对应的发票数据，在完成发票数据的开具工作后才能进行退费操作。退费处理工作很大程度上需要依赖客户返回发票数据的速度，并且开具发票数据时需要人工对发票信息逐一进行核实和输入。因此，目前的保单退费处理过程的周期长、工作效率低，无法及时地对客户的退费申请进行有效处理。
发明内容
根据本申请公开的各种实施例，提供一种保单退费处理方法、装置、计算机设备及存储介质。
一种保单退费处理方法，包括：
接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票数据的有效数值；
根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
根据所述有效数值总和与所述退费数值计算抽取出的各发票数据的抵扣数值；
将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
一种保单退费处理装置，包括：
退费请求接收模块，用于接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
第一发票查找模块，用于查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票数据的有效数值；
第一发票提取模块，用于根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
抵扣数值计算模块，用于根据所述有效数值总和与所述退费数值的差值计算出所述抽取出的各发票数据的抵扣数值；
第二发票生成模块，用于将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
退费指令生成模块，用于从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
一种计算机设备，包括存储器和一个或多个处理器，存储器中存储有计算机可读指令，计算机可读指令被处理器执行时实现本申请任意一个实施例中提供的保单退费处理方法的步骤。
一个或多个存储有计算机可读指令的非易失性计算机可读指令存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器实现本申请任意一个实施例中提供的保单退费处理方法的步骤。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中保单退费处理方法的应用环境图。
图2为根据一个或多个实施例中保单退费处理方法的流程图。
图3为根据一个或多个实施例中保单退费处理装置的结构示意图。
图4为另一个实施例中保单退费处理装置的结构示意图。
图5为根据一个或多个实施例中计算机设备的框图。
具体实施方式
为了使本申请的技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例中所提供的应用程序测试方法可以应用于如图1所示的应用环境中。财务系统的服务器102分别与保全终端104和票务终端106通过网络进行连接。保全终端104用于对用户的保险订单进行统一管理，保全终端104上存储有保单信息，当保全终端104收到用户对取消的保单的退费请求时，向服务器102转发携带保单号和退费数值的保单退费请求，服务器102接收保全终端104发送的保单退费请求后，查找保单号所关联的具有第一标识的发票数据，并根据发票数据的有效数值和预设提取规则从中抽取满足退费数值需求的发票数据，计算抽取出的发票数据的抵扣数值，将抵扣数值输入具有第二标识的发票模板中生成具有第二标识的发票数据并发送给票务终端106，票务终端106收到发票数据后对发票数据进行打印。服务器102将抽取出的发票数据进行数值抵扣后，生成退费指令发送给保全终端104，保全终端104收到退费指令后对用户进行退费处理。
在一个实施例中，如图2所示，提供了一种保单退费处理方法，该方法可应用于终端或服务器，以该方法应用于服务器为例进行说明，所述方法包括以下步骤：
步骤210，接收保全终端发送的保单退费请求，保单退费请求中携带保单号和退费数值。
客户在购买保险后，可以撤销已投保的保险订单，若保险订单中包含多份保险，客户可以选择撤销保险订单中的全部或者部分投保保险，并向保险公司申请退费。保险公司在向客户退费之前，需要对原来开具的发票进行冲抵操以作为完税凭证。
客户可以网上填写退费申请，也可以向座席人员申请退保，保全终端获取客户的退费申请，根据退费申请中的退费信息生成保单退费请求，并将保单退费请求发送给服务器。保单退费请求中携带客户所申请退费保单的保单号，以及客户撤销投保保险的金额值，即退费数值。此外，保单退费请求中也可包含用户信息、申请退费时间、保单数据等信息。服务器接收保全终端发送的保单退费请求，并从保单退费请求中获取保单号和退费数值。
步骤220，查找与保单号相关联的具有第一标识的发票数据，获取具有第一标识的发票数据的有效数值。
具有第一标识的发票数据为正数数值的发票数据，即通常所说的蓝字发票的数据。同理，下面所提到的具有第二标识的发票数据为负数数值的发票数据，即通常所述的红字发票的数据。服务器可以通过判断发票数据中的发票标识为第一标识还是第二标识，来判断发票数据是正数数值还是负数数值。
在客户进行投保时，服务器根据客户投保保单中的金额值生成票面数值与金额值一致的具有第一标识的发票数据，并将生成的正数数值的发票数据与客户的投保保单进行关联存储。服务器将生成的具有第一标识的发票数据发送给票务终端，票务终端将具有第一标 识的发票数据打印两份，一份由保险公司存底，另一份由客户持有。目前，保险公司在进行退费之前需要客户将持有的具有第一标识的发票数据寄回保险公司，保险公司根据保单的剩余金额重新开具具有第一标识的发票数据寄还客户。
服务器根据读取的保单号，查找与保单号关联存储的具有第一标识的发票数据，具有第一标识的发票数据的数量可以为一个，也可以为多个。服务器分别获取各发票数据的有效数值。需要说明的是，这里的有效数值并不一定等于发票数据的票面数值，有效数值有可能小于票面数值，因为某些具有第一标识的发票数据可能进行过抵扣操作。
在一些实施例中，服务器根据保单号查找保单数据，获取保单数据中的保险险种信息，根据保险险种信息判断保单数据所对应的应开发票的税率，服务器在查找到的与保单号关联存储的具有第一标识的发票数据中筛选出与应开发票税率相一致的发票数据，获取筛选出的发票数据的有效数值，对筛选出的发票数据进行如下述步骤的操作。
步骤230，根据有效数值和预设提取规则，获取具有第一标识的发票数据中有效数值总和大于或等于退费数值的发票数据。
服务器根据读取的各发票数据的有效数值，按照预设的提取规则从所有的第一标识的发票数据中抽取发票数据，抽取出的发票数据的有效数值的总和需大于或等于退费数值。
在一些实施例中，根据有效数值和预设提取规则抽取发票数据的步骤具体包括：获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对发票数据进行排序；将排在首位的发票数据的有效数值与退费数值进行比较；当排在首位的发票数据的有效数值小于退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；当有效数值总和小于退费数值时，将排在再后一位的发票数据的有效数值加入有效数值总和，直至计算出的有效数值总和大于或等于退费数值时，将进行有效数值总和计算的发票数据从具有第一标识的发票数据中提取出。
服务器读取各发票数据中的生成时间，并将各发票数据按照生成时间由先到后的顺序进行排序。排序完成后，服务器先将排在首位的发票数据的有效数值与退费数值进行比较。当排在首位的发票数据的有效数值大于或等于退费数值时，服务器直接将排在首位的发票数据抽取出。当排在首位的发票数据的有效数值小于退费数值时，服务器计算排在前两位的发票数据的有效数值的总和，并将排在前两位的发票数据的有效值总和与退费数值进行比较，当有效值总和小于退费数值时，服务器继续计算排在前三位的发票数据的有效数值的总和，将计算出的有效数值总和与退费数值进行比较，以此类推，直至服务器计算出排在前N位的有效数值总和大于或等于退费数值时，服务器将排在前N位的发票数据从具有第一标识的发票数据中提取出。
服务器还可以根据其他预设提取规则从具有第一标识的发票数据中进行发票数据提取。在一些实施例中，优选地，服务器根据读取的有效数值由大到小的顺序对发票数据进行排序，先将数值最大的有效数值与退费数值进行比较，当数值最大的有效数值大于或等于退费数值时，将有效数值最大的发票数据从从具有第一标识的发票数据中提取出。当数 值最大的有效数值小于退费数值时，计算数值大小排在前两位的有效数值的总和，将计算出的有效数值总和再与退费数值进行比较，以此类推，直至服务器计算出数值大小排在前N位的有效数值总和大于或等于退费数值时，将在前N位的发票数据从具有第一标识的发票数据中提取出。在本实施例中，根据有效数值由小到大的顺序对发票数据进行排序，可以减小服务器的计算次数，能够最快速地抽取出满足退费数值的发票数据。
需要说明的是，在其他实施例中，服务器还可以按照生成时间由后到前的顺序对发票数据进行排序，也可对发票数据进行随机排序，并不限于上述实施例中的提取规则。
步骤240，根据有效数值总和与退费数值计算抽取出的各发票数据的抵扣数值。
服务器对抽取出的发票数据也按照抽取前的排列顺序进行排序。服务器计算抽取出的发票数据的有效值总和与退费数值的数值差值，并根据数值差值确定各发票数据的需要进行退费抵扣的抵扣数值。在本实施例中，当数值差值等于0时，各发票数据的有效数值即为抵扣数值。当数值差值大于0时，将排在最后的发票数据的有效数值减去数值差值得到的值，作为排在最后的发票数据的抵扣数值，其他抽取出的发票数据的有效数值即为其抵扣数值。
步骤250，将各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将具有第二标识的发票数据发送给票务终端。
服务器获取具有第二标识的发票模板，服务器获取的具有第二标识的发票数据数量与抽取出的具有第一标识的发票数据的数量相等。每个发票模板中包含第二标识且包含负数数值发票的所有字段，并且通用字段已填入，如保险公司的信息：收款方纳税人识别号、地址、电话、开户银行账号等。每个发票模板具有与税务局发放的空白发票相一致的唯一发票代码和发票号码。
服务器获取当前日期，将当前日期输入每个发票的开票日期字段，服务器从保单退费请求中获取客户名称，保险产品名称，将客户名称、保险产品名称以及退费数值输入对应的字段中。服务器输入退费数值后，根据大小写数字映射表将小写数字(即阿拉伯数字)自动转换成大写数字(即中文汉字)。服务器将计算出的各发票数据的抵扣数值逐一输入经过上述处理的具有第二标识的发票模板中。
在一些实施例中，服务器将抵扣数值输入具有第二标识的发票模板中之后，对发票模板中每个字段的字段值进行自动校验。具体的，服务器检测是否存在空字段，字段值的数据格式是否与预设数据格式一致，数据格式包括数据类型、数据长度等。当发票模板通过校验时，服务器将生成的具有第二标识的发票数据发送给票务终端，以使票务终端对具有第二标识的发票数据进行打印。当发票模板中存在空字段时，服务器对识别空字段，并获取与空字段对应的字段值，输入获取的字段值。当发票模板中字段值的数据格式与预设数据格式不一致时，服务器将生成的具有第二标识的发票模板发送给审核终端，接收审核终端返回的修改后的发票模板后，将修改后的发票模板发送给票务终端进行打印，打印完成后将生成的具有第二标识的发票数据与保单号相关联。
步骤260，从抽取出的各发票数据的有效数值中扣除抵扣数值后，生成退费指令并发送给保全终端。
服务器对抽取出的各发票数据的有效数值进行修改，将有效数值修改为扣除抵扣数值后的值。服务器生成退费指令，将退费指令发送给保全终端，以使保全终端根据退费指令进行退费操作。
在一些实施例中，当发票数据的有效数值为0时，对发票数据进行无效标记，在后续查找保单关联发票的过程中，服务器将进行无效标记的具有第一标识的发票数据进行自动屏蔽。
在本实施例中，服务器通过查找保单退费请求中保单号所关联的具有第一标识的发票数据，根据具有第一标识的发票数据的有效数值和预设提取规则提取出有效数值总和与退费数值相等的发票数据，根据提取出的发票数据生成具有第二标识的发票数据，并将具有第二标识的发票数据发送给票务终端进行打印，并对抽取出的发票数据进行有效数值的扣除，扣除后生成退费指令返回给发送请求的保全终端，由此可以自动生成与退费金额等额的具有第二标识的发票数据，对发票数额进行自动抵扣，从而实现对保单退费请求的自动化处理，无需人工进行操作，提高处理效率。此外，也无需客户返回已开具的正数数值发票，提高保单退费请求的处理速度，缩短处理周期。
在一些实施例中，保单退费处理方法还包括：当计算出的具有第一标识的发票数据中所有发票数据有效数值总和小于退费数值时，将各发票数据的有效数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据；将具有第二标识的发票数据发送给票务终端，以使得票务终端对具有第二标识的发票数据进行打印；对所有发票数据的有效数值总和与退费数值的差值与保单号进行关联记录后，生成退费指令并发送给保全终端，以使得保全终端根据退费指令进行退费操作。
当服务器计算出的具有第一标识的发票数据中所有发票数据的有效数值的总和小于退费数值时，与保单号相关联的具有第一标识的发票数据无法满足退费数值的发票抵扣需求，这是因为客户当前已付款但还未开具发票。为了及时向客户返回退费金额，服务器先对已关联的具有第一标识的发票数据进行抵扣操作，并对与已有发票数据的有效数值的总和与退费金额的差值与保单号进行记录，待后续的业务过程中，获取到新的具有第一标识的发票数据时，再对差值部分进行抵扣。
具体的，服务器将所有发票数据的有效数值，逐个输入经如上述实施例的处理方法处理的具有第二标识的发票模板中，生成具有第二标识的发票数据，将其发送给发票数据以使票务终端打印发票数据，将打印好的具有第二标识的发票数据与保单号相关联。服务器将所有发票数据的有效数值总和与退费数值的差值与保单号进行关联记录，并将所有的具有第一标识的发票数据进行无效标记。服务器生成退费指令发送给保全终端，以使得保全终端根据退费指令进行退费操作。
在本实施例中，当保单号相关联的具有第一标识的发票数据无法满足退费数值的发票 抵扣需求时，服务器先根据已有的具有第一标识的发票数据生成具有第二标识的发票数据，并对具有第一标识的发票数据进行抵扣、将差值部分与保单号进行记录，从而可以对发票抵扣不足的部分进行记录，记录完成后即可向保全终端发送退费指令，及时向客户退费，最大化地减少客户的等待时间。
在一些实施例中，保单退费处理方法还包括：当查找到的与保单号相关联的具有第一标识的发票数据的有效数值均为零时，将退费数值与保单号进行关联记录后生成退费指令并发送给保全终端；接收保全终端发送的发票申请请求，将发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据；当发票申请请求中的保单号与保单退费请求中的保单号一致时，且请求数值大于退费数值时，将退费数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将请求数值与退费数值的差值作为生成的具有第一标识的发票数据的有效数值。
服务器接收到保单退费请求后，当查找不到保单号相关联的具有第一标识的发票数据时，表明该保单号对应的保险订单尚未开具发票，因此无需进行发票数据的抵扣操作，服务器直接向终端发送退费指令，以使保全终端进行退费操作。
当服务器查找到与保单号相关联的具有第一标识的发票数据，但是查找到的发票数据均具有无效标记，即发票数据的有效数值为零时，服务器将保单退费请求中的退费数值与保单号进行关联记录，并直接向保全终端发送退费指令，以使保全终端进行退费操作，使客户能够尽快获得退费。
在后续的业务操作过程中，当服务器接收到保全终端发送的发票申请请求时，发票申请请求中携带请求数值，服务器获取具有第一标识的发票数据，即正数数值发票数据的发票模板，具有第一标识的发票模板中包含第一标识且包含正数数值发票的所有字段，并且其中的通用字段已填入，通用字段如保险公司的信息：收款方纳税人识别号、地址、电话、开户银行账号等。每个发票模板具有与税务局发放的空白发票相一致的唯一发票代码和发票号码。
服务器获取当前日期，将当前日期输入具有第一标识的发票模板中的开票日期字段，服务器从发票申请请求中获取客户名称，保险产品名称，将客户名称、保险产品名称以及退费数值输入对应的字段中。服务器输入退费数值后，根据大小写数字映射表将小写数字(即阿拉伯数字)自动转换成大写数字(即中文汉字)。服务器将发票申请请求中携带的请求数值输入经过上述处理的具有第一标识的发票模板中生成具有第一标识的发票数据。
在一些实施例中，服务器将请求数值输入具有第二标识的发票模板中之后，对发票模板中每个字段的字段值进行自动校验。具体的，服务器检测是否存在空字段，字段值的数据格式是否与预设数据格式一致，数据格式包括数据类型、数据长度等。当发票模板通过校验时，服务器将生成的具有第一标识的发票数据发送给票务终端，以使票务终端对具有第一标识的发票数据进行打印。当发票模板中存在空字段时，服务器对识别空字段，并获取与空字段对应的字段值，输入获取的字段值。当发票模板中字段值的数据格式与预设数 据格式不一致时，服务器将生成的具有第一标识的发票模板发送给审核终端，接收审核终端返回的修改后的发票模板后，将修改后的发票模板发送给票务终端进行打印，打印完成后将生成的具有第一标识的发票数据与发票申请请求中的保单号相关联。
当服务器查找到发票申请请求中的保单号有关联的退费数值记录，且发票申请请求中的保单号与保单退费请求中的保单号一致时，服务器将请求数值与记录的退费数值进行比较，当请求数值大于退费数值时，已生成的具有第一标识的发票数据满足保单退费请求中的退费需求，服务器获取具有第二标识的发票模板并输入退费数值，对输入退费数值的具有第二标识的发票模板进行处理后，生成具有第二标识的发票数据。将生成的具有第二标识的发票数据与保单号关联记录，并清除与保单号关联记录的退费数值。服务器将生成的具有第二标识的发票数据发送给票务终端进行发票打印。服务器将根据发票申请请求生成的具有第一标识的发票数据的有效数值进行修改，将其修改为请求数值与退费数值的差值。
在一些实施例中，服务器将请求数值与记录的退费数值进行比较之后，当请求数值小于退费数值时，将请求数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将退费数值与请求数值的差值与保单号进行关联记录。
当请求数值小于退费数值时，服务器获取具有第二标识的发票模板并输入请求数值，对输入退费数值的具有第二标识的发票模板进行处理后，生成具有第二标识的发票数据。将生成的具有第二标识的发票数据与保单号关联记录，并将生成的具有第一标识的发票数据标记为无效。服务器将生成的具有第二标识的发票数据发送给票务终端进行发票打印。服务器将保单号关联的退费数值进行修改，将其修改为退费数值与请求数值的差值。待后续业务过程中再接收到保单号与保单退费请求的保单号一致的发票申请请求时，生成具有第一标识的发票数据时，继续根据发票申请请求中的请求数值和修改后的退费数值进行发票数据抵扣操作，直至退费数值被清零为止。
在本实施例中，当保单号已有的具有第一标识的发票数据不能满足退费抵扣需求时，先行向客户退费，通过将未进行抵扣操作的退费差值与保单号进行关联记录，可以当保单号关联有新的具有第一标识的发票数据时，根据记录的退费差值对新的具有第一标识的发票数据进行抵扣操作，在使客户尽早获取退费的同时也能实现完税记录。
在一些实施例中，接收保全终端发送的发票申请请求的步骤之后，还包括：查找与发票申请请求中的保单号相对应的保单数据，判断保单数据是否为合并保单数据；当保单数据为合并保单数据时，将发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据的步骤，包括：获取保单数据中的客户名称和与客户名称相对应的投保数值，将各客户名称和各客户名称对应的投保数值分别输入具有第一标识的发票模板中生成具有第一标识的发票数据。
服务器接收发票申请请求之后，获取发票申请请求中的保单号，并查找与保单号相对应的保单数据。保单数据可以存储服务器本地，服务器可以从本地获取；保单数据也可以 存储在保全终端上，服务器向保全终端发送携带有保单号的保单数据请求，保全终端向服务器返回与保单号相对应的保单数据。
服务器获取保单数据的客户名称，根据客户名称的数量判断保单数据是否为合并保单。当客户名称数量为单个时，保单为非合并保单；当客户名称数量为多个时，保单为合并保单。当保单为合并保单时，服务器获取与客户名称相等数量的具有第一标识的发票目标，将保单数据中各客户名称及其对应的投保数值分别输入具有第一标识的发票数据中，对输入投保数值的具有第一标识的发票模板进行处理后，生成具有第一标识的发票数据。
在一些实施例中，当服务器获取的发票申请请求中的保单号有关联的退费数值，查找退费数值所对应的客户名称，对生成的与查找到的客户名称一致的具有第一标识的发票数据进行如上述实施例中所述的抵扣操作，在此不再赘述。对于生成的与退费数值所对应的客户名称不一致的具有第一标识的发票数据不作处理。
在一些实施例中的，当服务器接收保全终端发送的保单退费请求时，获取保单退费请求中的保单号，并查找与保单号相对应的保单数据。根据保单数据中根据客户名称的数量判断保单数据是否为合并保单。当客户名称数量只为一个时，保单为非合并保单；当客户名称数量为多个时，保单为合并保单。当保单为合并保单时，服务器获取保单退费请求中的客户名称，并查找与保单号相关联的、且客户名称与请求中的客户名称相一致的具有第一标识的发票数据，根据预设提取规则从客户名称一致的具有第一标识的发票数据中抽取发票数据，并进行相应的抵扣操作。
在本实施例中，当请求中的保单号所对应的保单数据为合并保单数据时，在进行发票数据的抵扣操作时，自动获取合并保单中申请退费的客户名称，只对与客户名称一致的具有第一标识的发票数据进行抵扣操作，从而实现对客户合并保单的发票抵扣操作的自动化处理。
应该理解的是，虽然图2的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在一个实施例中，如图3所示，提供了一种保单退费处理装置，所述装置包括：
退费请求接收模块310，用于接收保全终端发送的保单退费请求，保单退费请求中携带保单号和退费数值；
第一发票查找模块320，用于查找与保单号相关联的具有第一标识的发票数据，获取具有第一标识的发票数据的有效数值；
第一发票提取模块330，用于根据有效数值和预设提取规则，获取具有第一标识的发票数据中有效数值总和大于或等于退费数值的发票数据；
抵扣数值计算模块340，用于根据有效数值总和与退费数值的差值计算出抽取出的各发票数据的抵扣数值；
第二发票生成模块350，用于将各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将具有第二标识的发票数据发送给票务终端；
退费指令生成模块360，用于从抽取出的各发票数据的有效数值中扣除抵扣数值后，生成退费指令并发送给保全终端。
在一些实施例中，第一发票提取模块330还包括：
发票排序模块，用于获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对发票数据进行排序；
数值比较模块，用于将排在首位的发票数据的有效数值与退费数值进行比较；
发票计算抽取模块，用于当排在首位的发票数据的有效数值小于退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；当有效数值总和小于退费数值时，将排在再后一位的发票数据的有效数值加入有效数值总和，直至计算出的有效数值总和大于或等于退费数值时，将进行有效数值总和计算的发票数据从具有第一标识的发票数据中提取出。
在一些实施例中，第二发票生成模块350还用于当计算出的具有第一标识的发票数据中所有发票数据有效数值总和小于退费数值时，将各发票数据的有效数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据；将具有第二标识的发票数据发送给票务终端，以使得票务终端对具有第二标识的发票数据进行打印；
退费指令生成模块360还用于对所有发票数据的有效数值总和与退费数值的差值与保单号进行关联记录后，生成退费指令并发送给保全终端，以使得保全终端根据退费指令进行退费操作。
在一些实施例中，如图4所示，所述装置还包括：
退费记录模块322，用于当查找到的与保单号相关联的具有第一标识的发票数据的有效数值均为零时，将退费数值与保单号进行关联记录后生成退费指令并发送给保全终端；
发票请求响应模块324，用于接收保全终端发送的发票申请请求，将发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据；
数值处理模块326，用于当发票申请请求中的保单号与保单退费请求中的保单号一致时，且请求数值大于退费数值时，将退费数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将请求数值与退费数值的差值作为生成的具有第一标识的发票数据的有效数值。
在一些实施例中，数值处理模块326，还用于当请求数值小于退费数值时，将请求数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将退费数值与请求数值的差值与保单号进行关联记录。
在一些实施例中，所述装置还包括：保单合并判断模块，用于查找与所述发票申请请 求中的保单号相对应的保单数据，判断所述保单数据是否为合并保单数据。
发票请求响应模块324，还用于获取保单数据中的客户名称和与所述客户名称相对应的投保数值，将所述各客户名称和所述各客户名称对应的投保数值分别输入所述具有第一标识的发票模板中生成具有第一标识的发票数据。
关于保单退费处理装置的具体限定可以参见上文中对于保单退费处理方法的限定，在此不再赘述。上述保单退费处理装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是终端，也可以是服务器。当该计算机设备为服务器时，其内部结构图可以如图5所示。该计算机设备包括通过系统总线连接的处理器、存储器和网络接口。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机可读指令。该内存储器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现一种漏洞检测方法。本领域技术人员可以理解，图5中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
一种计算机设备，包括存储器和一个或多个处理器，存储器中存储有计算机可读指令，计算机可读指令被处理器执行时实现本申请任意一个实施例中提供的保单退费处理方法的步骤。
一个或多个存储有计算机可读指令的非易失性计算机可读指令存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器实现本申请任意一个实施例中提供的保单退费处理方法的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接 RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种保单退费处理方法，包括：
    接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
    查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票数据的有效数值；
    根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
    根据所述有效数值总和与所述退费数值计算抽取出的各发票数据的抵扣数值；
    将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
    从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
  2. 根据权利要求1所述的保单退费处理方法，其特征在于，所述根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据，包括：
    获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对所述发票数据进行排序；
    将排在首位的发票数据的有效数值与所述退费数值进行比较；
    当所述排在首位的发票数据的有效数值小于所述退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；及
    当所述有效数值总和小于所述退费数值时，将排在再后一位的发票数据的有效数值加入所述有效数值总和，直至计算出的有效数值总和大于或等于所述退费数值时，将进行有效数值总和计算的发票数据从所述具有第一标识的发票数据中提取出。
  3. 根据权利要求2所述的保单退费处理方法，其特征在于，所述方法还包括：
    当计算出的所述具有第一标识的发票数据中所有发票数据有效数值总和小于所述退费数值时，将所述各发票数据的有效数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据；
    将所述具有第二标识的发票数据发送给票务终端，以使得所述票务终端对所述具有第二标识的发票数据进行打印；及
    对所有发票数据的有效数值总和与所述退费数值的差值与所述保单号进行关联记录后，生成退费指令并发送给保全终端，以使得所述保全终端根据所述退费指令进行退费操作。
  4. 根据权利要求1所述的保单退费处理方法，其特征在于，所述方法还包括：
    当查找到的与所述保单号相关联的具有第一标识的发票数据的有效数值均为零时，将所述退费数值与所述保单号进行关联记录后生成退费指令并发送给保全终端；
    接收保全终端发送的发票申请请求，将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据；及
    当所述发票申请请求中的保单号与所述保单退费请求中的保单号一致时，且所述请求数值大于所述退费数值时，将所述退费数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述请求数值与所述退费数值的差值作为所述生成的具有第一标识的发票数据的有效数值。
  5. 根据权利要求4所述的保单退费处理方法，其特征在于，所述方法还包括：
    当所述请求数值小于所述退费数值时，将所述请求数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述退费数值与所述请求数值的差值与所述保单号进行关联记录。
  6. 根据权利要求4所述的保单退费处理方法，其特征在于，在接收保全终端发送的发票申请请求之后，所述方法还包括：
    查找与所述发票申请请求中的保单号相对应的保单数据，判断所述保单数据是否为合并保单数据；
    当所述保单数据为合并保单数据时，所述将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据，包括：
    获取保单数据中的客户名称和与所述客户名称相对应的投保数值，将所述各客户名称和所述各客户名称对应的投保数值分别输入所述具有第一标识的发票模板中生成具有第一标识的发票数据。
  7. 一种保单退费处理装置，包括：
    退费请求接收模块，用于接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
    第一发票查找模块，用于查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票数据的有效数值；
    第一发票提取模块，用于根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
    抵扣数值计算模块，用于根据所述有效数值总和与所述退费数值的差值计算出所述抽取出的各发票数据的抵扣数值；
    第二发票生成模块，用于将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
    退费指令生成模块，用于从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
  8. 根据权利要求7所述的保单退费处理装置，其特征在于，所述第一发票提取模块 还包括：
    发票排序模块，用于获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对所述发票数据进行排序；
    数值比较模块，用于将排在首位的发票数据的有效数值与所述退费数值进行比较；及
    发票计算抽取模块，用于当所述排在首位的发票数据的有效数值小于所述退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；当所述有效数值总和小于所述退费数值时，将排在再后一位的发票数据的有效数值加入所述有效数值总和，直至计算出的有效数值总和大于或等于所述退费数值时，将进行有效数值总和计算的发票数据从所述具有第一标识的发票数据中提取出。
  9. 一种计算机设备，包括存储器及一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
    接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
    查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票数据的有效数值；
    根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
    根据所述有效数值总和与所述退费数值计算抽取出的各发票数据的抵扣数值；
    将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
    从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
  10. 根据权利要求9所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对所述发票数据进行排序；
    将排在首位的发票数据的有效数值与所述退费数值进行比较；
    当所述排在首位的发票数据的有效数值小于所述退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；及
    当所述有效数值总和小于所述退费数值时，将排在再后一位的发票数据的有效数值加入所述有效数值总和，直至计算出的有效数值总和大于或等于所述退费数值时，将进行有效数值总和计算的发票数据从所述具有第一标识的发票数据中提取出。
  11. 根据权利要求10所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    当计算出的所述具有第一标识的发票数据中所有发票数据有效数值总和小于所述退 费数值时，将所述各发票数据的有效数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据；
    将所述具有第二标识的发票数据发送给票务终端，以使得所述票务终端对所述具有第二标识的发票数据进行打印；及
    对所有发票数据的有效数值总和与所述退费数值的差值与所述保单号进行关联记录后，生成退费指令并发送给保全终端，以使得所述保全终端根据所述退费指令进行退费操作。
  12. 根据权利要求9所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    当查找到的与所述保单号相关联的具有第一标识的发票数据的有效数值均为零时，将所述退费数值与所述保单号进行关联记录后生成退费指令并发送给保全终端；
    接收保全终端发送的发票申请请求，将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据；及
    当所述发票申请请求中的保单号与所述保单退费请求中的保单号一致时，且所述请求数值大于所述退费数值时，将所述退费数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述请求数值与所述退费数值的差值作为所述生成的具有第一标识的发票数据的有效数值。
  13. 根据权利要求12所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    当所述请求数值小于所述退费数值时，将所述请求数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述退费数值与所述请求数值的差值与所述保单号进行关联记录。
  14. 根据权利要求12所述的计算机设备，其特征在于，所述处理器执行所述计算机可读指令时还执行以下步骤：
    查找与所述发票申请请求中的保单号相对应的保单数据，判断所述保单数据是否为合并保单数据；
    当所述保单数据为合并保单数据时，所述将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据，包括：
    获取保单数据中的客户名称和与所述客户名称相对应的投保数值，将所述各客户名称和所述各客户名称对应的投保数值分别输入所述具有第一标识的发票模板中生成具有第一标识的发票数据。
  15. 一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行以下步骤：
    接收保全终端发送的保单退费请求，所述保单退费请求中携带保单号和退费数值；
    查找与所述保单号相关联的具有第一标识的发票数据，获取所述具有第一标识的发票 数据的有效数值；
    根据所述有效数值和预设提取规则，获取所述具有第一标识的发票数据中有效数值总和大于或等于所述退费数值的发票数据；
    根据所述有效数值总和与所述退费数值计算抽取出的各发票数据的抵扣数值；
    将所述各发票数据的抵扣数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述具有第二标识的发票数据发送给票务终端；及
    从所述抽取出的各发票数据的有效数值中扣除所述抵扣数值后，生成退费指令并发送给所述保全终端。
  16. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    获取具有第一标识的发票数据中各发票数据的生成时间，按照生成时间由先到后的顺序对所述发票数据进行排序；
    将排在首位的发票数据的有效数值与所述退费数值进行比较；
    当所述排在首位的发票数据的有效数值小于所述退费数值时，计算排在首位的发票数据与排在后一位的发票数据的有效数值总和；及
    当所述有效数值总和小于所述退费数值时，将排在再后一位的发票数据的有效数值加入所述有效数值总和，直至计算出的有效数值总和大于或等于所述退费数值时，将进行有效数值总和计算的发票数据从所述具有第一标识的发票数据中提取出。
  17. 根据权利要求16所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    当计算出的所述具有第一标识的发票数据中所有发票数据有效数值总和小于所述退费数值时，将所述各发票数据的有效数值分别输入具有第二标识的发票模板中生成具有第二标识的发票数据；
    将所述具有第二标识的发票数据发送给票务终端，以使得所述票务终端对所述具有第二标识的发票数据进行打印；及
    对所有发票数据的有效数值总和与所述退费数值的差值与所述保单号进行关联记录后，生成退费指令并发送给保全终端，以使得所述保全终端根据所述退费指令进行退费操作。
  18. 根据权利要求15所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    当查找到的与所述保单号相关联的具有第一标识的发票数据的有效数值均为零时，将所述退费数值与所述保单号进行关联记录后生成退费指令并发送给保全终端；
    接收保全终端发送的发票申请请求，将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据；及
    当所述发票申请请求中的保单号与所述保单退费请求中的保单号一致时，且所述请求 数值大于所述退费数值时，将所述退费数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述请求数值与所述退费数值的差值作为所述生成的具有第一标识的发票数据的有效数值。
  19. 根据权利要求18所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    当所述请求数值小于所述退费数值时，将所述请求数值输入具有第二标识的发票模板中生成具有第二标识的发票数据，将所述退费数值与所述请求数值的差值与所述保单号进行关联记录。
  20. 根据权利要求18所述的存储介质，其特征在于，所述计算机可读指令被所述处理器执行时还执行以下步骤：
    查找与所述发票申请请求中的保单号相对应的保单数据，判断所述保单数据是否为合并保单数据；
    当所述保单数据为合并保单数据时，所述将所述发票申请请求中的请求数值输入具有第一标识的发票模板中生成具有第一标识的发票数据，包括：
    获取保单数据中的客户名称和与所述客户名称相对应的投保数值，将所述各客户名称和所述各客户名称对应的投保数值分别输入所述具有第一标识的发票模板中生成具有第一标识的发票数据。
PCT/CN2018/087294 2017-07-25 2018-05-17 保单退费处理方法、装置、计算机设备和存储介质 WO2019019777A1 (zh)

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 (zh) 2019-01-31

Family

ID=61437859

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/087294 WO2019019777A1 (zh) 2017-07-25 2018-05-17 保单退费处理方法、装置、计算机设备和存储介质

Country Status (2)

Country Link
CN (1) CN107784595A (zh)
WO (1) WO2019019777A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
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 北京金堤科技有限公司 一种发票数据处理方法和装置，以及存储介质和电子设备
CN118505222A (zh) * 2024-05-08 2024-08-16 广州今之港教育咨询有限公司 基于操作批次的退款管理方法、系统、装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008045290A2 (en) * 2006-10-04 2008-04-17 David Rudich Premium financed life insurance products and methods
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 平安科技（深圳）有限公司 保单退费处理方法、装置、计算机设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008045290A2 (en) * 2006-10-04 2008-04-17 David Rudich Premium financed life insurance products and methods
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
WO2019019777A1 (zh) 保单退费处理方法、装置、计算机设备和存储介质
US20230377032A1 (en) System and method for processing transaction records for users
US10546351B2 (en) System and method for automatic generation of reports based on electronic documents
US9286618B2 (en) Recognizing and combining redundant merchant designations in a transaction database
US11062132B2 (en) System and method for identification of missing data elements in electronic documents
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 (zh) 数据核对方法、装置、计算机设备及可读存储介质
CN112529687A (zh) 一种贷款、还款记账方法及其装置、设备及存储介质
CN112613952A (zh) 资质审核方法、装置、计算机设备和存储介质
US20180011846A1 (en) System and method for matching transaction electronic documents to evidencing electronic documents
CN102208061A (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
US20180025438A1 (en) System and method for generating analytics based on electronic documents
CN110728566B (zh) 报销文件中数据处理方法、装置、计算机设备和存储介质
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
US11989774B1 (en) Systems and methods for providing digital trusted data
US20170011456A1 (en) System and method for an electronic consumer debt extinguishment process

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