WO2022247966A1 - 票据处理方法、装置、设备和存储介质 - Google Patents

票据处理方法、装置、设备和存储介质 Download PDF

Info

Publication number
WO2022247966A1
WO2022247966A1 PCT/CN2022/103546 CN2022103546W WO2022247966A1 WO 2022247966 A1 WO2022247966 A1 WO 2022247966A1 CN 2022103546 W CN2022103546 W CN 2022103546W WO 2022247966 A1 WO2022247966 A1 WO 2022247966A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
bill
reimbursement
editable
verification
Prior art date
Application number
PCT/CN2022/103546
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 WO2022247966A1 publication Critical patent/WO2022247966A1/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/12—Accounting
    • G06Q40/125—Finance or payroll
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G06F16/90335—Query processing
    • 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/10—Tax strategies

Definitions

  • This document relates to the field of computer technology, in particular to a bill processing method, device, equipment and storage medium.
  • An embodiment of this specification provides a bill processing method.
  • the bill processing method includes: obtaining electronic bills to be processed, order data and bill data; the bill data is generated after the order data is paid by the reimbursement code; the electronic bill is generated based on the bill data; according to the electronic bill, the order data and the bill At least one of the data, create an editable reimbursement form; according to the electronic bill, order data and billing data, conduct credible verification on the editable reimbursement form under at least one verification dimension; if all verifications pass under all verification dimensions, then Make sure that the editable expense report is a credible expense report.
  • a bill processing device including: a data acquisition unit, which acquires electronic bills to be processed, order data and bill data. Generated based on bill data; a document creation unit, which creates an editable reimbursement form according to at least one of electronic bills, order data and bill data; a document verification unit, which performs verification in at least one of the electronic bills, order data and bill data
  • the credible verification of the editable reimbursement form is carried out under the dimensions; the result determination unit, if it passes the verification under each verification dimension, determines that the editable reimbursement form is a credible reimbursement form.
  • a receipt processing device comprising a processor and a memory arranged to store computer-executable instructions.
  • the processor realizes: obtaining electronic bills to be processed, order data, and bill data, the bill data is generated after paying for the order data by using the reimbursement code, and the electronic bills are generated based on the bill data ; Create an editable reimbursement form based on at least one of electronic bills, order data, and billing data; perform credible verification on editable reimbursement forms in at least one verification dimension according to electronic bills, order data, and billing data; If all the verification dimensions pass the verification, the editable reimbursement form is determined to be a credible reimbursement form.
  • Another embodiment of this specification provides a storage medium for storing computer-executable instructions.
  • the computer-executable instructions When executed by a processor, the computer-executable instructions enable the processor to: acquire electronic bills, order data and bill data to be processed, bill The data is generated after the order data is paid using the reimbursement code, and the electronic bill is generated based on the bill data; an editable reimbursement form is created according to at least one of the electronic bill, order data, and bill data; according to the electronic bill, order data, and bill data , perform credible verification on the editable reimbursement form under at least one verification dimension; if the verification is passed under all verification dimensions, the editable reimbursement form is determined to be a credible reimbursement form.
  • FIG. 1 is a schematic flow diagram of a bill processing method provided by an embodiment of this specification
  • Fig. 2 is a schematic flowchart of a bill processing method provided by another embodiment of this specification.
  • Fig. 3 is a schematic flow chart of a bill processing method provided by another embodiment of this specification.
  • FIG. 4 is a schematic diagram of a scene of a bill processing method provided by an embodiment of this specification.
  • Fig. 5 is a schematic diagram of the module composition of the bill processing device provided by an embodiment of this specification.
  • Fig. 6 is a schematic structural diagram of a bill processing device provided by an embodiment of this specification.
  • One or more embodiments of this specification provide a bill processing method to improve reimbursement. Audit accuracy, thereby avoiding false reimbursement.
  • the bill processing method provided by one or more embodiments of this specification can be applied to and executed by the reimbursement system.
  • FIG. 1 is a schematic flowchart of a bill processing method provided by an embodiment of this specification. The method can be applied to and executed by a reimbursement system. As shown in Fig. 1, the method includes the following steps S102 to S108.
  • Step S102 obtaining electronic bills, order data and bill data to be processed.
  • the bill data is generated after the order data is paid by using the reimbursement code, and the electronic bill is generated based on the bill data.
  • Step S104 creating an editable reimbursement form according to at least one of the electronic bill, order data and bill data.
  • step S106 credible verification is performed on the editable reimbursement form in at least one verification dimension according to the electronic bill, order data and bill data.
  • step S108 if the verification is passed under each verification dimension, it is determined that the editable reimbursement form is a credible reimbursement form.
  • an editable reimbursement form can be created, and according to the electronic bill, order data and bill data, edit the editable reimbursement form under at least one verification dimension Credible verification is carried out, thereby improving the accuracy of reimbursement review and avoiding false reimbursement.
  • step S102 the reimbursement system obtains the electronic receipts, order data and bill data to be processed. There are two ways to realize this step.
  • the reimbursement system obtains the electronic bills, order data and bill data to be processed, including: (a1) obtaining the reimbursement ID submitted by the user; the reimbursement ID includes any one of the bill ID, order ID, and bill ID; (a2) Passing the reimbursement identifier into the third-party voucher system; (a3) receiving the electronic bill, order data and billing data returned by the third-party voucher system based on the reimbursement identifier.
  • multiple order data are stored in the third-party voucher system, bill data associated with each order data and electronic receipts associated with each bill data.
  • the electronic bill can be an electronic invoice.
  • the transaction system sends the user's order data to the payment system, and after the user pays for the order data through the payment system, the payment system generates billing data associated with the order data, and the payment system also sends and billing data are sent to the billing system.
  • the billing system transmits the order data, billing data and electronic bill to the third-party voucher system for storage. Therefore, the third-party voucher system stores multiple order data, each order Billing data associated with the data and electronic notes associated with each billing data.
  • the reimbursement system obtains the reimbursement identifier submitted by the user; the reimbursement identifier includes any one of a bill identifier, an order identifier, and a bill identifier.
  • the reimbursement system transfers the reimbursement ID to the third-party voucher system.
  • the third-party voucher system searches for the interrelated order data, bill data and electronic bills according to the reimbursement identification, and sends the found order data, bill data and electronic bills to the reimbursement system, so that the reimbursement system receives the third-party voucher system based on the reimbursement Identifies the returned e-ticket, order data, and billing data.
  • the reimbursement system transmits the order ID to the third-party voucher system, and the third-party voucher system looks up the order data according to the order ID, and searches for the billing data associated with the order data and the electronic bill associated with the billing data, and the found order
  • the data, billing data and electronic bills are sent to the reimbursement system, so that the reimbursement system receives the electronic bills, order data and billing data returned by the third-party voucher system based on the reimbursement identifier.
  • the reimbursement system obtains the electronic bills, order data and bill data to be processed, including: (b1) obtaining the reimbursement ID submitted by the user; the reimbursement ID includes any one of the bill ID, order ID, and bill ID; (b2) According to the reimbursement ID, look up electronic bills, order data and billing data in the third-party voucher system.
  • This method is the same as method 1 in that multiple order data are stored in the third-party voucher system, the bill data associated with each order data and the electronic bill associated with each bill data.
  • the difference is: after the reimbursement system obtains the reimbursement ID submitted by the user, it actively searches the third-party voucher system for interrelated electronic bills, order data and billing data according to the reimbursement ID.
  • the reimbursement system obtains the order ID submitted by the user, searches for the order data in the third-party system according to the order ID, and searches for the bill data associated with the order data and the electronic bill associated with the bill data, thereby obtaining the order data, bill Data and Electronic Notes.
  • the bill data is generated based on the user’s payment action for the order data.
  • Bills are obtained by invoicing billing data.
  • the billing data is generated based on the user's payment action for the order data through the reimbursement code.
  • the reimbursement code is a payment voucher set up for the user by the organization where the user is located, such as a company or enterprise, and the payment is made through the reimbursement code.
  • it can directly debit the account of the organization instead of debiting the personal account of the user, so that in the scenario of the user's business consumption, the effect of direct payment by the organization does not need to be advanced by the user.
  • step S102 Since there are multiple orders for combined payment, in one case, in the above step S102, there are multiple copies of the order data and one copy of the bill data, and the bill data is combined and paid for each order data by the user using the reimbursement code provided by the organization. generated after.
  • step S102 Since there is a situation where payment is only made for part of the order content in the order, in another case, in the above step S102, there is one copy of the order data and one copy of the bill data, and the bill data is used when the user uses the reimbursement code provided by the organization to match the order. Part of the order content in the data is generated after payment.
  • step S102 Since multiple bills can be billed in combination, in one case, in the above step S102, there is one electronic bill and multiple bill data, and the electronic bill is generated based on the merger of each bill data.
  • step S102 Since part of the content in the bill can be invoiced, in another case, in the above step S102, there is one copy of the electronic bill and one copy of the bill data, and the electronic bill is generated based on part of the bill content in the bill data.
  • the method in this embodiment can be applied to multiple scenarios such as consolidated payment, consolidated invoicing, partial payment, and partial invoicing, which are not specifically limited here.
  • the user can pass in the ticket identification of the unreimbursed electronic bill in the reimbursement system, and the reimbursement system will use the Bill identification, through the above method 1 or method 2, obtain the user's unreimbursed electronic bill, the bill data associated with the unreimbursed electronic bill, and the order data associated with the unreimbursed electronic bill, and the obtained electronic bill, order
  • the data and billing data are displayed to the user, thereby realizing the above step S102.
  • the reimbursement system creates an editable reimbursement form according to at least one of the electronic bill, order data and bill data, which specifically includes the following two methods.
  • the reimbursement system creates an editable reimbursement form based on at least one of electronic bills, order data, and billing data, including: (c1) determining at least one target selected by the user among electronic bills, order data, and billing data data; (c2) if the data content of the target data satisfies the data content requirements corresponding to the preset reimbursement form, extract keywords from the target data, and create an editable reimbursement form according to the extracted keywords.
  • the user can select at least one type of data from the electronic bills, order data and bill data displayed by the reimbursement system as the target data.
  • the reimbursement system determines at least one target data selected by the user among the electronic bill, order data and bill data according to the user's selection operation.
  • the reimbursement system judges whether the data content of the target data meets the data content requirements corresponding to the preset reimbursement form, for example, whether the data content of the target data includes all the content contained in the reimbursement form, or whether the data content of the target data can Generate all the content included in the reimbursement form. All the contents included in the reimbursement form include consumption time, reimbursement amount, reimbursement expense category and so on.
  • the reimbursement system determines that the data content of the target data meets the data content requirements of the preset reimbursement form, the reimbursement system extracts keywords from the target data, and generates all the content contained in the reimbursement form based on the extracted keywords, thereby creating a Edit the expense report.
  • the extracted keywords include consumption time, consumption amount, purchased product category and the like.
  • the reimbursement system can also select supplementary data from the data other than the above target data in the electronic bill, order data and bill data; from the target data and Extract keywords from supplementary data and create editable expense reports based on the extracted keywords.
  • the reimbursement system compares the content difference between the data content of the target data and the content contained in the reimbursement form, and based on the content difference, from The supplementary data is selected from the data other than the target data in the electronic bill, order data and bill data, and the content of the supplementary data can supplement the content difference.
  • the reimbursement system extracts keywords from the target data and supplementary data, and creates an editable reimbursement form based on the extracted keywords.
  • the extracted keywords include consumption time, consumption amount, purchased product category and the like.
  • the reimbursement system creates an editable reimbursement form based on at least one of the electronic bill, order data and bill data, including: (d1) determining at least one target selected by the user in the electronic bill, order data and bill data data; (d2) extract keywords from the target data, and write the extracted keywords into the preset reimbursement template; (d3) if there is no default item in the written reimbursement template, then write The following expense report template creates editable expense reports.
  • the user can select at least one type of data from the electronic bills, order data and bill data displayed by the reimbursement system as the target data.
  • the reimbursement system determines at least one target data selected by the user among electronic bills, order data and bill data according to the user's selection operation.
  • the reimbursement system extracts keywords from the target data, and writes the extracted keywords into a preset reimbursement form template, for example, extracts a time keyword, and writes the time into a time column in the preset reimbursement form template.
  • the reimbursement system first judges whether the extracted keywords belong to the content that needs to be written in the reimbursement form template. After the keyword extraction is completed, the reimbursement system judges whether there is a default item in the written reimbursement form template. If not, it creates an editable reimbursement form based on the written reimbursement form template. Expense template as an editable expense report.
  • the reimbursement system will select supplementary data from data other than the target data in electronic bills, order data, and bill data according to the default items, and extract keywords from the supplementary data , write the extracted keywords into the default item to create an editable expense report.
  • the reimbursement system can select supplementary data from data other than the target data in the electronic bill, order data and bill data according to the content of the default item, and the content of the supplementary data can supplement the default item. Next, the reimbursement system extracts keywords from the supplementary data, writes the extracted keywords into default items, and uses the written reimbursement form template without default items as the created editable reimbursement form.
  • the content of the editable reimbursement form comes from at least one of the order data, billing data and electronic bills, at least from the target data selected by the user, and the data content of the target data is not enough to generate an editable reimbursement
  • the reimbursement system can also automatically select supplementary data to generate an editable reimbursement form.
  • the content of the editable reimbursement form comes from at least one of order data, bill data and electronic receipts.
  • the reimbursement system can generate the reimbursement form ID for the editable reimbursement form, and establish the association between the reimbursement form ID, the order ID of the order data, the bill ID of the bill data, and the bill ID of the electronic bill, and based on the Association relationship, store editable reimbursement forms, order data, billing data and electronic bills locally or in a third-party voucher system to obtain a four-in-one data model.
  • the editable reimbursement form can be credibly reviewed (as described in the subsequent step S106).
  • corporate finance is reimbursed, it needs to make reimbursement based on electronic invoices according to tax requirements, and corporate finance can also obtain order data and billing data as data records.
  • the reimbursement system After the reimbursement system generates the editable reimbursement form, it can provide the editable reimbursement form to the user for editing. For example, an editable expense report is displayed on the screen for users to edit.
  • the user In the process of editing the editable reimbursement form, the user can edit the consumption time, reimbursement amount, reimbursement expense category, etc. in the editable reimbursement form.
  • the reimbursement system performs credible verification on the editable reimbursement form in at least one verification dimension according to the electronic bill, order data and bill data, which may be: after the user edits the editable reimbursement form, The editable reimbursement form edited by the user is obtained, and credible verification is performed on the edited editable reimbursement form under at least one verification dimension according to the electronic bill, order data and bill data.
  • the reimbursement system can also check whether there are reimbursement content items that do not meet the preset reimbursement rules in the editable reimbursement form; if there is, a corresponding prompt will be issued to the user information to prompt the user to adjust the content of the reimbursement content item.
  • the preset reimbursement rules include preset time ranges, preset amount ranges, preset category ranges, etc.
  • the reimbursement content items include consumption time, reimbursement amount, and reimbursement categories. You can check whether the consumption time in the editable reimbursement form is within the preset time range, whether the reimbursement amount is within the preset amount range, and whether the reimbursement category is within the preset category range, so as to determine whether there is any reimbursement that does not meet the preset reimbursement rules Reimbursement content item.
  • the reimbursement system can send a corresponding prompt message to the user to prompt the user to adjust the content of the reimbursement item that does not meet the preset reimbursement rules, such as modifying the consumption Time, reimbursement amount, reimbursement category, etc.
  • step S106 according to the electronic bill, order data and bill data, credible verification is performed on the editable reimbursement form in at least one verification dimension, specifically: according to the electronic bill, order data and bill data, in at least one verification dimension
  • credible verification is performed on the editable reimbursement form fed back by the user based on the above prompt information.
  • step S106 is directly executed.
  • the reimbursement system performs credible verification on the editable reimbursement form in at least one verification dimension according to the electronic bill, order data and bill data, which may be: (e1) judging the editable reimbursement form , whether the element information of the electronic bill, order data and bill data match in pairs under the verification dimension; (e2) if so, determine that the credible verification of the editable reimbursement form under the verification dimension has passed.
  • the verification dimension includes at least one dimension, and the verification dimension may include at least one of the following: consumption time, consumption amount, commodity category, commodity quantity, and commodity name.
  • the element information refers to the specific value under the verification dimension.
  • the above-mentioned actions (e1) and (e2) are executed to determine whether the editable reimbursement form under the verification dimension passes the credible verification.
  • any verification dimension as an example, in action (e1), judge whether the editable reimbursement form, electronic bill, order data, and bill data match element information pairwise under the verification dimension, such as judging the editable reimbursement form, electronic bill, order Whether the amount recorded in the data and the bill data match in pairs, and the matching rules can be defined in advance, such as defining that the reimbursement amount in the editable reimbursement form must be less than or equal to the consumption amount in the electronic bill, and less than or equal to the consumption in the order data Amount, and less than or equal to the consumption amount in the bill data, and the consumption amount in the electronic bill must be less than or equal to the consumption amount in the order data and less than or equal to the consumption amount in the bill data, and the consumption amount in the order data It must be greater than or equal to the consumption amount in the billing data.
  • Another example is to judge whether the consumption time recorded in the edited reimbursement form, electronic bill, order data and bill data are consistent. If the element information of the editable reimbursement form, electronic bill, order data and bill data match in pairs under this verification dimension, it is determined that the editable reimbursement form under this verification dimension has passed the credible verification; otherwise, it is determined that under this verification dimension The credible verification of the editable reimbursement form failed.
  • step S108 if the editable reimbursement form passes the verification under each verification dimension, it is determined that the editable reimbursement form is a credible reimbursement form.
  • Fig. 2 is a schematic flowchart of a bill processing method provided by another embodiment of this specification. As shown in Fig. 2, on the basis of Fig. 1, the method further includes step S110: if the verification fails in any verification dimension, submit The user displays corresponding prompt information to prompt the user to process at least one of editable reimbursement form, electronic bill, order data and bill data.
  • the corresponding prompt information will be displayed to the user, and the user can modify the reimbursement amount in the editable reimbursement form according to the prompt information, or re-upload the electronic bill, order data and bill At least one of the data, so as to prevent the user from falsifying the reimbursement form.
  • Fig. 3 is a schematic flowchart of a bill processing method provided by another embodiment of this specification. As shown in Fig. 3, the method is executed by the reimbursement system, and includes the following steps S302 to S316.
  • Step S302 obtaining electronic bills, order data and bill data to be processed; the bill data is generated after the order data is paid by using the reimbursement code; the electronic bill is generated based on the bill data.
  • Step S304 creating an editable reimbursement form according to at least one of the electronic bill, order data and bill data.
  • Step S306 checking whether there is any reimbursement content item in the editable reimbursement form that does not meet the preset reimbursement rules. If it exists, execute step S308; if not, execute step S312.
  • Step S308 sending corresponding first prompt information to the user to prompt the user to adjust the content of the reimbursement content item.
  • Step S310 according to the electronic bill, order data and bill data, credible verification is performed on the editable reimbursement form fed back by the user based on the prompt information under at least one verification dimension.
  • Step S312 according to the electronic bill, order data and bill data, perform credible verification on the created editable reimbursement form under at least one verification dimension.
  • step S314 if the verification is passed under each verification dimension, it is determined that the editable reimbursement form is a credible reimbursement form.
  • Step S316 if the verification fails in any verification dimension, display the corresponding second prompt information to the user to prompt the user to process at least one of editable reimbursement form, electronic receipt, order data and bill data.
  • Fig. 4 is a schematic diagram of a scenario of a bill processing method provided by an embodiment of this specification. As shown in Fig. 4, the scenario includes: a transaction system, a payment system, an invoicing system and a reimbursement system.
  • a user such as an organization employee completes an order through the transaction system to generate an order
  • the user sends the reimbursement ID through the reimbursement system, and the reimbursement system pulls invoices and associated bills and order data from the voucher system for display according to the reimbursement ID, and the user selects the invoice data to generate a reimbursement form.
  • the reimbursement form is credibly verified under one verification dimension, and if the verification is passed under each of the verification dimensions, the reimbursement form is determined to be a credible reimbursement form.
  • the reimbursement system submits the credible reimbursement form to financial personnel for reimbursement processing.
  • the three-in-one relationship between electronic bills, order data and bill data can be established, and the mutual support among orders, bills and bills can be realized to meet the authenticity of enterprise reimbursement.
  • Verification needs identify the consumption first and then invoice, the actual consumption time is not during the business travel period but the invoice time is during the business travel period, the consumption has not actually occurred, and the invoices of other business travel periods are used for reimbursement, the actual consumption amount is less than the invoiced amount, the enterprise Employees have completed their consumption but the purchased goods or services do not meet the financial regulations of the enterprise.
  • FIG. 5 is a schematic diagram of the module composition of the bill processing device provided by an embodiment of this specification.
  • the device includes: a data acquisition unit 51 , which acquires electronic bills, order data and bill data to be processed; the bill data is generated after payment is made to the order data using a reimbursement code; the electronic bill is generated based on the bill data; the bill creation unit 52, which According to at least one of the electronic note, the order data and the bill data, create an editable reimbursement form; the document verification unit 53, according to the electronic note, the order data and the bill data, in The credible verification is performed on the editable reimbursement form under at least one verification dimension; the result determination unit 54 determines that the editable reimbursement form is a credible reimbursement form if the verification is passed under each of the verification dimensions.
  • the data acquisition unit 51 acquires the reimbursement identifier submitted by the user; the reimbursement identifier includes any one of a bill identifier, an order identifier, and a bill identifier; transmits the reimbursement identifier to a third-party voucher system; receives the reimbursement identifier The third-party credential system returns the electronic bill, the order data and the bill data based on the reimbursement identifier.
  • the data acquisition unit 51 acquires the reimbursement identifier submitted by the user; the reimbursement identifier includes any one of a bill identifier, an order identifier, and a bill identifier; according to the reimbursement identifier, search for the electronic Invoices, said order data and said billing data.
  • the document creation unit 52 determines at least one target data selected by the user among the electronic note, the order data and the bill data; if the data content of the target data satisfies the preset reimbursement form According to the corresponding data content requirements, keywords are extracted from the target data, and an editable reimbursement form is created according to the extracted keywords.
  • the document creation unit 52 if the data content of the target data does not meet the preset data content requirements corresponding to the reimbursement form, delete the selecting supplementary data from data other than the target data; extracting keywords from the target data and the supplementary data, and creating an editable reimbursement form according to the extracted keywords.
  • the document creation unit 52 determines at least one target data selected by the user among the electronic bill, the order data and the bill data; extracts keywords from the target data, and converts the extracted The keyword is written into a preset expense report template; if there is no default item in the written expense report template, an editable expense report is created according to the written expense report template.
  • the document creation unit 52 if there is a default item in the written reimbursement form template, then according to the default item, the electronic note, the order data and the bill data except selecting supplementary data from data other than the target data; extracting keywords from the supplementary data, and writing the extracted keywords into the default item to create an editable reimbursement form.
  • an editing unit is further included, which provides the editable reimbursement form to the user for editing after the editable reimbursement form is generated.
  • the document verification unit 53 obtains the editable reimbursement form edited by the user after the user edits the editable reimbursement form;
  • the credible verification of the editable reimbursement form obtained by editing is performed under the dimension.
  • the document verification unit 53 judges whether the element information of the editable reimbursement form, the electronic bill, the order data, and the bill data match in pairs under the verification dimension; The credible verification of the editable reimbursement form under the verification dimension has passed.
  • an editable reimbursement form can be created, and according to the electronic bill, order data and bill data, edit the editable reimbursement form under at least one verification dimension Credible verification is carried out, thereby improving the accuracy of reimbursement review and avoiding false reimbursement.
  • the bill processing device in the embodiment of this specification can realize the entire process of the aforementioned bill processing method, and has the same effect and function, which will not be repeated here.
  • FIG. 6 is a schematic structural diagram of the bill processing device provided by an embodiment of this specification. If there is a relatively large difference, one or more processors 1501 and memory 1502 may be included, and one or more application programs or data may be stored in the memory 1502 . Wherein, the storage 1502 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 1502 may include one or more modules (not shown), and each module may include a series of computer-executable instructions in the bill processing device.
  • the processor 1501 may be configured to communicate with the memory 1502, and execute a series of computer-executable instructions in the memory 1502 on the bill processing device.
  • the bill processing device may also include one or more power sources 1503, one or more wired or wireless network interfaces 1504, one or more input and output interfaces 1505, one or more keyboards 1506 and so on.
  • the bill processing device is located in the above-mentioned reimbursement system, and the bill processing device includes a processor and a memory arranged to store computer-executable instructions.
  • the processor realizes: obtaining electronic bills, order data and bill data to be processed; Generated after payment; the electronic bill is generated based on the bill data; according to at least one of the electronic bill, the order data and the bill data, an editable reimbursement form is created; according to the electronic bill, the For the order data and the bill data, credible verification is performed on the editable reimbursement form under at least one verification dimension; if the verification is passed under each of the verification dimensions, the editable reimbursement form is determined to be a credible reimbursement form.
  • an editable reimbursement form can be created, and according to the electronic bill, order data and bill data, edit the editable reimbursement form under at least one verification dimension Credible verification is carried out, thereby improving the accuracy of reimbursement review and avoiding false reimbursement.
  • the bill processing device in the embodiment of this specification can realize the entire process of the aforementioned bill processing method, and has the same effect and function, which will not be repeated here.
  • the storage medium may be a USB flash drive, an optical disc, a hard disk, etc.
  • the computer-executable instructions stored in the storage medium when executed by the processor, enable the processor to implement the following process: obtain electronic bills, order data and bills to be processed data; the bill data is generated after payment is made to the order data using the reimbursement code; the electronic bill is generated based on the bill data; according to at least one of the electronic bill, the order data and the bill data Type, create an editable reimbursement form; according to the electronic bill, the order data and the bill data, perform credible verification on the editable reimbursement form under at least one verification dimension; If passed, it is determined that the editable reimbursement form is a credible reimbursement form.
  • an editable reimbursement form can be created, and according to the electronic bill, order data and bill data, edit the editable reimbursement form under at least one verification dimension Credible verification is carried out, thereby improving the accuracy of reimbursement review and avoiding false reimbursement.
  • the storage medium in the embodiment of this specification can realize the entire process of the above-mentioned bill processing method, and has the same effect and function, which will not be repeated here.
  • a Programmable Logic Device such as a Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory.
  • controller in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, the means for implementing various functions can be regarded as both software modules implementing the method and structures within hardware components.
  • a typical implementing device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.
  • embodiments of this specification may be provided as methods, systems, or computer program products. Accordingly, the embodiments of the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present specification may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. .
  • Embodiments of the present specification are described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to the embodiments of the present specification. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory, such as read-only memory (ROM) or flash RAM.
  • RAM random access memory
  • ROM read-only memory
  • Memory is an example of computer readable media.
  • Computer-readable media including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information.
  • Information may be computer readable instructions, data structures, modules of a program, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
  • computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
  • embodiments of this specification may be provided as methods, systems or computer program products. Accordingly, the embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present specification may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. .
  • One or more embodiments of the specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Technology Law (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Databases & Information Systems (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & 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

[根据细则37.2由ISA制定的发明名称]　票据处理方法、装置、设备和存储介质 技术领域
本文件涉及计算机技术领域，尤其涉及一种票据处理方法、装置、设备和存储介质。
背景技术
因公消费报销场景里由于财务和税务的要求，企业财务需要花费大量精力对票据进行真实性核验，比如审核票据对应的消费是否本人真实发生、消费的内容、时间和金额与票据记载是否匹配等。目前只基于报销人员提交的票据进行报销，难以对票据的真实性进行核验，容易导致虚假报销的产生。
发明内容
本说明书一个实施例提供了一种票据处理方法。所述票据处理方法，包括：获取待处理的电子票据、订单数据和账单数据；账单数据在利用报销码对订单数据进行支付后生成；电子票据基于账单数据生成；根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单；根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本说明书另一个实施例提供了一种票据处理装置，包括：数据获取单元，其获取待处理的电子票据、订单数据和账单数据，账单数据在利用报销码对订单数据进行支付后生成，电子票据基于账单数据生成；单据创建单元，其根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单；单据核验单元，其根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；结果确定单元，其若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本说明书另一个实施例提供了一种票据处理设备，包括处理器以及被安排成存储计算机可执行指令的存储器。其中，计算机可执行指令在被处理器执行时使处理器实现：获取待处理的电子票据、订单数据和账单数据，账单数据在利用报销码对订单数据进行支付后生成，电子票据基于账单数据生成；根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单；根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本说明书另一个实施例提供了一种存储介质，用于存储计算机可执行指令，计算机可执行指令在被处理器执行时使处理器实现：获取待处理的电子票据、订单数据和账单数据， 账单数据在利用报销码对订单数据进行支付后生成，电子票据基于账单数据生成；根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单；根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
附图说明
为了更清楚地说明本说明书一个或多个实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一实施例提供的票据处理方法的流程示意图；
图2为本说明书又一实施例提供的票据处理方法的流程示意图；
图3为本说明书又一实施例提供的票据处理方法的流程示意图；
图4为本说明书一实施例提供的票据处理方法的场景示意图；
图5为本说明书一实施例提供的票据处理装置的模块组成示意图；
图6为本说明书一实施例提供的票据处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
考虑到目前只基于报销人员提交的票据进行报销，难以对票据的真实性进行核验，容易导致虚假报销的产生的问题，本说明书一个或多个实施例提供了一种票据处理方法，以提高报销审核的准确性，进而避免虚假报销的产生。本说明书一个或多个实施例提供的票据处理方法，能够应用在报销系统上，由报销系统执行。
图1为本说明书一实施例提供的票据处理方法的流程示意图，该方法能够应用在报销系统上，由报销系统执行。如图1所示，该方法包括以下步骤S102至S108。
步骤S102，获取待处理的电子票据、订单数据和账单数据。其中，账单数据在利用报销码对订单数据进行支付后生成，电子票据基于账单数据生成。
步骤S104，根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单。
步骤S106，根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验。
步骤S108，若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本实施例中，在获取到待处理的电子票据、订单数据和账单数据之后，可以创建可编辑报销单，并根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，从而提高了报销审核的准确性，进而避免虚假报销的产生。
上述步骤S102中，报销系统获取待处理的电子票据、订单数据和账单数据，该步骤有两种实现方式。
方式一、报销系统获取待处理的电子票据、订单数据和账单数据，包括：(a1)获取用户提交的报销标识；报销标识包括票据标识、订单标识、账单标识中的任意一种；(a2)将报销标识传入第三方凭证系统；(a3)接收第三方凭证系统基于报销标识返回的电子票据、订单数据和账单数据。
本实施例中，第三方凭证系统中存储有多个订单数据，每个订单数据关联的账单数据和每个账单数据关联的电子票据。电子票据可以为电子发票。具体地，用户通过交易系统生成订单后，交易系统将用户的订单数据发送至支付系统，用户通过支付系统对订单数据进行支付后，支付系统生成订单数据关联的账单数据，支付系统还将订单数据和账单数据发送至开票系统。商家通过开票系统生成账单数据关联的电子票据后，开票系统将订单数据、账单数据和电子票据传送至第三方凭证系统进行存储，从而，第三方凭证系统中存储有多个订单数据，每个订单数据关联的账单数据和每个账单数据关联的电子票据。
报销系统获取用户提交的报销标识；报销标识包括票据标识、订单标识、账单标识中的任意一种。报销系统将报销标识传入第三方凭证系统。第三方凭证系统根据报销标识，查找相互关联的订单数据、账单数据和电子票据，并将查找到的订单数据、账单数据和电子票据发送至报销系统，从而，报销系统接收第三方凭证系统基于报销标识返回的电子票据、订单数据和账单数据。
一个例子中，报销系统向第三方凭证系统传入订单标识，第三方凭证系统根据订单标识查找订单数据，并查找与订单数据关联的账单数据和与账单数据关联的电子票据，将查找到的订单数据、账单数据和电子票据发送至报销系统，从而，报销系统接收第三方凭证系统基于报销标识返回的电子票据、订单数据和账单数据。
方式二、报销系统获取待处理的电子票据、订单数据和账单数据，包括：(b1)获取用户提交的报销标识；报销标识包括票据标识、订单标识、账单标识中的任意一种；(b2)根据报销标识，在第三方凭证系统查找电子票据、订单数据和账单数据。
本方式和方式一相同之处在于，第三方凭证系统中存储有多个订单数据，每个订单数据关联的账单数据和每个账单数据关联的电子票据。不同之处为：报销系统获取用提交的报销标识之后，根据报销标识，主动在第三方凭证系统查找相互关联的电子票据、订单数据和账单数据。
一个例子中，报销系统获取用户提交的订单标识，根据订单标识在第三方系统内查找订单数据，并查找与订单数据关联的账单数据和与账单数据关联的电子票据，从而查找得到订单数据、账单数据和电子票据。
根据以上方式一和方式二的描述可知，本实施例中步骤S102中所获取的电子票据、订单数据和账单数据之间具有关联关系，账单数据是基于用户对订单数据的支付动作生成的，电子票据是对账单数据进行开票得到的。在一个具体的实施例中，账单数据是基于用户通过报销码对订单数据的支付动作生成的，报销码是用户所在的机构如公司或企事业单位为用户设立的支付凭证，通过报销码进行支付后，能够直接在机构的账户中进行扣款而不在用户的个人账户中扣款，从而在用户因公消费的场景下，达到了机构直接付款不需要用户垫付的效果。
由于存在多个订单合并支付的情况，因此在一个情况下，在上述步骤S102中，订单数据有多份，账单数据有一份，账单数据在用户利用机构提供的报销码对各个订单数据进行合并支付后生成。
由于存在只针对订单中的部分订单内容进行支付的情况，因此在另一个情况下，在上述步骤S102中，订单数据有一份，账单数据有一份，账单数据在用户利用机构提供的报销码对订单数据中的部分订单内容进行支付后生成。
由于可以对多个账单进行合并开票，因此在一个情况下，在上述步骤S102中，电子票据有一份，账单数据有多份，电子票据基于各个账单数据合并生成。
由于可以对账单中的部分内容进行开票，因此在另一个情况下，在上述步骤S102中，电子票据有一份，账单数据有一份，电子票据基于账单数据中的部分账单内容生成。
本实施例中的方法可以应用于合并支付、合并开票、部分支付、部分开票等多种场景，这里不做具体限制。
在一个具体的实施例中，用户登录报销系统并进入个人的报销界面后，用户可以在报销系统中传入未报销的电子票据的票据标识，报销系统根据用户传入的未报销的电子票据的票据标识，通过以上方式一或者方式二，获取用户的未报销的电子票据、与未报销的电子票据关联的账单数据和与未报销的电子票据关联的订单数据，并将获取的电子票据、订单数据和账单数据展示给用户，从而实现上述步骤S102。
上述步骤S104中，报销系统根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单，具体包括以下两种方式。
方式一、报销系统根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单，包括：(c1)确定用户在电子票据、订单数据和账单数据中选定的至少一种目标数据；(c2)若目标数据的数据内容满足预设的报销单对应的数据内容要求，则从目标数据中提取关键字，根据所提取的关键字创建可编辑报销单。
用户可以在报销系统展示的电子票据、订单数据和账单数据中选取至少一种数据作为目标数据。报销系统根据用户的选取操作，确定用户在电子票据、订单数据和账单数据中选定的至少一种目标数据。报销系统判断目标数据的数据内容是否满足预设的报销单对应的数据内容要求，比如，判断目标数据的数据内容是否包括报销单所包含的全部内容，或者，判断根据目标数据的数据内容是否能够生成报销单所包含的全部内容。报销单所包含的全部内容包括消费时间、报销金额、报销费用类别等内容。
若报销系统确定目标数据的数据内容满足预设的报销单对应的数据内容要求，则报销系统从目标数据中提取关键字，根据所提取的关键字生成报销单所包含的全部内容，从而创建可编辑报销单。其中，提取的关键字包括消费时间、花费金额、所购买的产品类别等内容。
若目标数据的数据内容不满足预设的报销单对应的数据内容要求，则报销系统还能够在电子票据、订单数据和账单数据中除上述目标数据以外的数据中选取补充数据；从目标数据和补充数据中提取关键字，根据所提取的关键字创建可编辑报销单。
若报销系统判断目标数据的数据内容不满足预设的报销单对应的数据内容要求，则报销系统比较目标数据的数据内容和报销单所包含的内容之间的内容差异，根据该内容差异，从电子票据、订单数据和账单数据中除目标数据以外的数据中选取补充数据，补充数据的内容能够补充该内容差异。接着，报销系统从目标数据和补充数据中提取关键字，根据所提取的关键字创建可编辑报销单。其中，提取的关键字包括消费时间、花费金额、所购买的产品类别等内容。
方式二、报销系统根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单，包括：(d1)确定用户在电子票据、订单数据和账单数据中选定的至少一种目标数据；(d2)从目标数据中提取关键字，将所提取的关键字写入预设的报销单模板；(d3)若写入后的报销单模板中不存在缺省项，则根据写入后的报销单模板创建可编辑报销单。
用户可以在报销系统展示的电子票据、订单数据和账单数据中选取至少一种数据作为目标数据。报销系统根据用户的选取操作，确定用户在电子票据、订单数据和账单数据中 选定的至少一种目标数据。报销系统从目标数据中提取关键字，将所提取的关键字写入预设的报销单模板，比如，提取时间关键字，将时间写入预设的报销单模板中的时间栏。在关键字写入时，报销系统首先判断所提取的关键字是否属于报销单模板中所需要写入的内容，若属于，则进行关键字的写入，若不属于，则不写入。报销系统在关键字提取完成后，判断写入后的报销单模板中是否存在缺省项，若不存在，则根据写入后的报销单模板创建可编辑报销单，比如，将写入后的报销单模板作为可编辑报销单。
若写入后的报销单模板中存在缺省项，则报销系统根据缺省项，在电子票据、订单数据和账单数据中除目标数据以外的数据中选取补充数据，从补充数据中提取关键字，将所提取的关键字写入缺省项，以创建可编辑报销单。
报销系统可以根据缺省项的内容，在电子票据、订单数据和账单数据中除目标数据以外的数据中选取补充数据，补充数据的内容能够补充缺省项。接着，报销系统从补充数据中提取关键字，将所提取的关键字写入缺省项，将写入后的不存在缺省项的报销单模板作为创建的可编辑报销单。
综合以上两种方式可知，可编辑报销单的内容来自于订单数据、账单数据和电子票据中的至少一种，至少来自于用户选取的目标数据，在目标数据的数据内容不足以生成可编辑报销单时，报销系统还可以自动选取补充数据以生成可编辑报销单。
这里需要强调的是，本实施例中，可编辑报销单的内容来自于订单数据、账单数据和电子票据中的至少一种。在此基础上，报销系统可以为可编辑报销单生成报销单标识，并建立报销单标识、订单数据的订单标识、账单数据的账单标识以及电子票据的票据标识之间的关联关系，并根据该关联关系，在本地或者在第三方凭证系统中存储可编辑报销单、订单数据、账单数据和电子票据，得到四位一体的数据模型。通过该模型，能够对可编辑报销单进行可信审核(如后续的步骤S106所介绍)。企业财务在进行费用报销时，需要根据税务要求依据电子发票进行报销，企业财务也可以获取订单数据和账单数据作为数据留底。
报销系统在生成可编辑报销单之后，可以向用户提供可编辑报销单，以供用户进行编辑。比如，通过屏幕展示可编辑报销单，以供用户编辑。用户在编辑可编辑报销单的过程中，可以编辑可编辑报销单中的消费时间、报销金额、报销费用类别等内容。
相应地，上述步骤S106中，报销系统根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，可以是：在用户对可编辑报销单进行编辑后，获取用户编辑得到的可编辑报销单，根据电子票据、订单数据和账单数据，在至少一个核验维度下对编辑得到的可编辑报销单进行可信核验。
在一个实施例中，在步骤S104创建可编辑报销单之后，报销系统还能够检查可编辑报销单中是否存在不符合预设的报销规则的报销内容项；若存在，则向用户发出相应的提示信息，以提示用户调整所述报销内容项的内容。预设的报销规则包括预设时间范围、预设金额范围、预设类别范围等，报销内容项包括消费时间、报销金额、报销类别等。可以检查可编辑报销单中的消费时间是否位于预设时间范围内，报销金额是否位于预设金额范围内，报销类别是否位于预设类别范围内，从而判断是否存在不符合预设的报销规则的报销内容项。若检查确定存在不符合预设的报销规则的报销内容项，则报销系统可以向用户发出相应的提示信息，以提示用户调整该不符合预设的报销规则的报销内容项的内容，比如修改消费时间、报销金额、报销类别等。
相应地，步骤S106中根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，具体为：根据电子票据、订单数据和账单数据，在至少一个核验维度下对用户基于上述提示信息所反馈的可编辑报销单进行可信核验。当然，若检查确定不存在不符合预设的报销规则的报销内容项，则直接执行步骤S106。
在一个实施例中，上述步骤S106中，报销系统根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，可以是：(e1)判断可编辑报销单、电子票据、订单数据和账单数据在核验维度下的要素信息是否两两匹配；(e2)若是，则确定在核验维度下可编辑报销单可信核验通过。
本实施例中，核验维度至少包括一个维度，核验维度可以包括下述至少一种：消费时间、消费金额、商品类别、商品数量、商品名称。要素信息指的是在核验维度下的具体取值。针对每个核验维度，都执行上述的动作(e1)和(e2)，判断在该核验维度下可编辑报销单是否可信核验通过。
以任意一个核验维度为例，动作(e1)中，判断可编辑报销单、电子票据、订单数据和账单数据在核验维度下的要素信息是否两两匹配，比如判断编辑报销单、电子票据、订单数据和账单数据中记载的金额是否两两匹配，其中匹配规则可以预先定义，比如定义可编辑报销单中的报销金额要小于或者等于电子票据中的消费金额，且小于或者等于订单数据中的消费金额，且小于或者等于账单数据中的消费金额，且，电子票据中的消费金额要小于或者等于订单数据中的消费金额以及要小于或者等于账单数据中的消费金额，且订单数据中的消费金额要大于或者等于账单数据中的消费金额。又如判断编辑报销单、电子票据、订单数据和账单数据中记载的消费时间是否均一致。若可编辑报销单、电子票据、订单数据和账单数据在该核验维度下的要素信息两两匹配，则确定在该核验维度下可编辑报销单可信核验通过，反之，确定在该核验维度下可编辑报销单可信核验未通过。
上述步骤S108中，若可编辑报销单在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
图2为本说明书又一实施例提供的票据处理方法的流程示意图，如图2所示，在图1的基础上，该方法还包括步骤S110：若在任一核验维度下核验不通过，则向用户显示相应的提示信息，以提示用户对可编辑报销单、电子票据、订单数据和账单数据中的至少一种进行处理。
比如，若在消费金额核验维度下核验不通过，则向用户显示相应的提示信息，用户可以根据该提示信息，修改可编辑报销单中的报销金额，或者，重新上传电子票据、订单数据和账单数据中的至少一种，从而防止用户对报销单进行造假的虚假报销行为。
图3为本说明书又一实施例提供的票据处理方法的流程示意图，如图3所示，该方法由报销系统执行，包括以下步骤S302至S316。
步骤S302，获取待处理的电子票据、订单数据和账单数据；账单数据在利用报销码对订单数据进行支付后生成；电子票据基于账单数据生成。
步骤S304，根据电子票据、订单数据和账单数据中的至少一种，创建可编辑报销单。
步骤S306，检查可编辑报销单中是否存在不符合预设的报销规则的报销内容项。若存在，执行步骤S308，若不存在，执行步骤S312。
步骤S308，向用户发出相应的第一提示信息，以提示用户调整该报销内容项的内容。
步骤S310，根据电子票据、订单数据和账单数据，在至少一个核验维度下对用户基于提示信息所反馈的可编辑报销单进行可信核验。
步骤S312，根据电子票据、订单数据和账单数据，在至少一个核验维度下对创建的可编辑报销单进行可信核验。
步骤S314，若在各核验维度下均核验通过，则确定可编辑报销单为可信报销单。
步骤S316，若在任一核验维度下核验不通过，则向用户显示相应的第二提示信息，以提示用户对可编辑报销单、电子票据、订单数据和账单数据中的至少一种进行处理。
图3中的各个步骤可以参考前面的描述，这里不再重复。
图4为本说明书一实施例提供的票据处理方法的场景示意图，如图4所示，该场景包括：交易系统、支付系统、开票系统和报销系统。
其中，用户如机构员工通过交易系统完成下单产生订单，订单标识比如为orderid＝1，交易系统将订单信息(orderid＝1及其他订单信息)同步给支付系统。用户通过支付系统完成支付生成账单(账单标识billid＝1，关联的订单标识为orderid＝1)，并记录订单相关信息。用户基于账单(billid＝1)发起开票申请，开票系统从支付系统获取账单和订单完成开票(发票 标识为invoiceid＝1，关联的账单billid＝1)，并且输出订单(orderid＝1)、账单(billid＝1,ordered＝1)、发票(invoiceid＝1,billid＝1)数据到凭证系统，构建基于发票为中心的账单、订单三单合一的数据凭证模型，通过发票可以找到关联的账单，通过账单可以找到关联的订单。
用户通过报销系统发送报销标识，报销系统根据报销标识从凭证系统拉取发票及关联的账单和订单数据进行展示，用户选取发票数据生成报销单，报销系统根据发票、订单数据和账单数据，在至少一个核验维度下对报销单进行可信核验，若在各所述核验维度下均核验通过，则确定报销单为可信报销单。报销系统将可信报销单提交至财务人员进行报销处理。
综上，通过本实施例中的票据处理方法，能够建立电子票据、订单数据和账单数据之间的三单合一的关系，实现订单、账单和票据之间的互相佐证，满足企业报销真实性验证的需求，识别出先消费后开票、实际消费时间未在因公差旅期间但是开票时间在因公差旅期间、消费未实际发生用其他差旅期间的发票进行报销、实际消费金额小于开票金额、企业员工完成了消费但是购买的商品或者服务不符合企业财务的规定等问题。
基于上述的票据处理方法，本说明书还提供了一种票据处理装置，图5为本说明书一实施例提供的票据处理装置的模块组成示意图，如图5所示，该装置包括：数据获取单元51，其获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；单据创建单元52，其根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；单据核验单元53，其根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；结果确定单元54，其若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
可选地，数据获取单元51，获取用户提交的报销标识；所述报销标识包括票据标识、订单标识、账单标识中的任意一种；将所述报销标识传入第三方凭证系统；接收所述第三方凭证系统基于所述报销标识返回的所述电子票据、所述订单数据和所述账单数据。
可选地，数据获取单元51，获取用户提交的报销标识；所述报销标识包括票据标识、订单标识、账单标识中的任意一种；根据所述报销标识，在第三方凭证系统查找所述电子票据、所述订单数据和所述账单数据。
可选地，单据创建单元52，确定用户在所述电子票据、所述订单数据和所述账单数据中选定的至少一种目标数据；若所述目标数据的数据内容满足预设的报销单对应的数据内容要求，则从所述目标数据中提取关键字，根据所提取的关键字创建可编辑报销单。
可选地，单据创建单元52，若所述目标数据的数据内容不满足预设的报销单对应的数据内容要求，则在所述电子票据、所述订单数据和所述账单数据中除所述目标数据以外的数据中选取补充数据；从所述目标数据和所述补充数据中提取关键字，根据所提取的关键字创建可编辑报销单。
可选地，单据创建单元52，确定用户在所述电子票据、所述订单数据和所述账单数据中选定的至少一种目标数据；从所述目标数据中提取关键字，将所提取的关键字写入预设的报销单模板；若写入后的所述报销单模板中不存在缺省项，则根据写入后的报销单模板创建可编辑报销单。
可选地，单据创建单元52，若写入后的所述报销单模板中存在缺省项，则根据所述缺省项，在所述电子票据、所述订单数据和所述账单数据中除所述目标数据以外的数据中选取补充数据；从所述补充数据中提取关键字，将所提取的关键字写入所述缺省项，以创建可编辑报销单。
可选地，还包括编辑单元，在生成可编辑报销单之后，向用户提供可编辑报销单，以供用户进行编辑。
可选地，单据核验单元53，在用户对可编辑报销单进行编辑后，获取用户编辑得到的可编辑报销单；根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对编辑得到的可编辑报销单进行可信核验。
可选地，单据核验单元53，判断可编辑报销单、所述电子票据、所述订单数据和所述账单数据在所述核验维度下的要素信息是否两两匹配；若是，则确定在所述核验维度下可编辑报销单可信核验通过。
本实施例中，在获取到待处理的电子票据、订单数据和账单数据之后，可以创建可编辑报销单，并根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，从而提高了报销审核的准确性，进而避免虚假报销的产生。
本说明书实施例中的票据处理装置，能够实现前述的票据处理方法的全部过程，并具有相同的效果和功能，这里不再重复。
基于上述的票据处理方法，本说明书还提供了一种票据处理设备，图6为本说明书一实施例提供的票据处理设备的结构示意图，如图6所示，票据处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1501和存储器1502，存储器1502中可以存储有一个或一个以上应用程序或数据。其中，存储器1502可以是短暂存储或持久存储。存储在存储器1502的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括票据处理设备中的一系列计算机可执行指令。更进一步地，处理器1501 可以设置为与存储器1502通信，在票据处理设备上执行存储器1502中的一系列计算机可执行指令。票据处理设备还可以包括一个或一个以上电源1503，一个或一个以上有线或无线网络接口1504，一个或一个以上输入输出接口1505，一个或一个以上键盘1506等。
在一个具体的实施例中，票据处理设备位于上述的报销系统内，票据处理设备包括有处理器以及被安排成存储计算机可执行指令的存储器。其中，所述计算机可执行指令在被所述处理器执行时使所述处理器实现：获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本实施例中，在获取到待处理的电子票据、订单数据和账单数据之后，可以创建可编辑报销单，并根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，从而提高了报销审核的准确性，进而避免虚假报销的产生。
本说明书实施例中的票据处理设备，能够实现前述的票据处理方法的全部过程，并具有相同的效果和功能，这里不再重复。
本说明书另一实施例还提供了一种存储介质，用于存储计算机可执行指令。该存储介质可以为U盘、光盘、硬盘等，该存储介质存储的计算机可执行指令在被处理器执行时，能使所述处理器实现以下流程：获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
本实施例中，在获取到待处理的电子票据、订单数据和账单数据之后，可以创建可编辑报销单，并根据电子票据、订单数据和账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，从而提高了报销审核的准确性，进而避免虚假报销的产生。
本说明书实施例中的存储介质，能够实现前述的票据处理方法的全部过程，并具有相同的效果和功能，这里不再重复。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者 连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为 既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书的一个或多个实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书的实施例可提供为方法、系统、或计算机程序产品。因此，本说明书的实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书的实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书的实施例是参照根据本说明书实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或 非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本说明书的实施例可提供为方法、系统或计算机程序产品。因此，本说明书的实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本说明书的实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书的一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本说明书的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本说明书的实施例可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (17)

  1. 一种票据处理方法，包括：
    获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；
    根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；
    若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
  2. 根据权利要求1所述的方法，获取待处理的电子票据、订单数据和账单数据，包括：
    获取用户提交的报销标识；所述报销标识包括票据标识、订单标识、账单标识中的任意一种；
    将所述报销标识传入第三方凭证系统；
    接收所述第三方凭证系统基于所述报销标识返回的所述电子票据、所述订单数据和所述账单数据。
  3. 根据权利要求1所述的方法，获取待处理的电子票据、订单数据和账单数据，包括：
    获取用户提交的报销标识；所述报销标识包括票据标识、订单标识、账单标识中的任意一种；
    根据所述报销标识，在第三方凭证系统查找所述电子票据、所述订单数据和所述账单数据。
  4. 根据权利要求2或3所述的方法，其中，
    针对所述电子票据和所述账单数据，所述电子票据基于各个所述账单数据合并生成，或者，所述电子票据基于所述账单数据中的部分账单内容生成；
    针对所述账单数据和所述订单数据，所述账单数据在用户利用机构提供的报销码对各个所述订单数据进行合并支付后生成，或者，所述账单数据在用户利用机构提供的报销码对所述订单数据中的部分订单内容进行支付后生成。
  5. 根据权利要求1所述的方法，根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单，包括：
    确定用户在所述电子票据、所述订单数据和所述账单数据中选定的至少一种目标数据；
    若所述目标数据的数据内容满足预设的报销单对应的数据内容要求，则从所述目标数 据中提取关键字，根据所提取的关键字创建可编辑报销单。
  6. 根据权利要求5所述的方法，还包括：
    若所述目标数据的数据内容不满足预设的报销单对应的数据内容要求，则在所述电子票据、所述订单数据和所述账单数据中除所述目标数据以外的数据中选取补充数据；
    从所述目标数据和所述补充数据中提取关键字，根据所提取的关键字创建可编辑报销单。
  7. 根据权利要求1所述的方法，根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单，包括：
    确定用户在所述电子票据、所述订单数据和所述账单数据中选定的至少一种目标数据；
    从所述目标数据中提取关键字，将所提取的关键字写入预设的报销单模板；
    若写入后的所述报销单模板中不存在缺省项，则根据写入后的报销单模板创建可编辑报销单。
  8. 根据权利要求7所述的方法，还包括：
    若写入后的所述报销单模板中存在缺省项，则根据所述缺省项，在所述电子票据、所述订单数据和所述账单数据中除所述目标数据以外的数据中选取补充数据；
    从所述补充数据中提取关键字，将所提取的关键字写入所述缺省项，以创建可编辑报销单。
  9. 根据权利要求1所述的方法，还包括：
    在生成可编辑报销单之后，向用户提供可编辑报销单，以供用户进行编辑。
  10. 根据权利要求9所述的方法，根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，包括：
    在用户对可编辑报销单进行编辑后，获取用户编辑得到的可编辑报销单；
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对编辑得到的可编辑报销单进行可信核验。
  11. 根据权利要求1所述的方法，根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，包括：
    判断可编辑报销单、所述电子票据、所述订单数据和所述账单数据在所述核验维度下的要素信息是否两两匹配；
    若是，则确定在所述核验维度下可编辑报销单可信核验通过。
  12. 根据权利要求11所述的方法，其中，所述核验维度包括下述至少一种：消费时间、消费金额、商品类别、商品数量、商品名称。
  13. 根据权利要求1所述的方法，在创建可编辑报销单之后，还包括：
    检查可编辑报销单中是否存在不符合预设的报销规则的报销内容项；
    若存在，则向用户发出相应的提示信息，以提示用户调整所述报销内容项的内容；
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验，包括：
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对用户基于所述提示信息所反馈的可编辑报销单进行可信核验。
  14. 根据权利要求1所述的方法，还包括：
    若在任一所述核验维度下核验不通过，则向用户显示相应的提示信息，以提示用户对可编辑报销单、电子票据、订单数据和账单数据中的至少一种进行处理。
  15. 一种票据处理装置，包括：
    数据获取单元，其获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；
    单据创建单元，其根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；
    单据核验单元，其根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；
    结果确定单元，其若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
  16. 一种票据处理设备，包括：处理器；以及被安排成存储计算机可执行指令的存储器，所述计算机可执行指令在被所述处理器执行时使所述处理器实现：
    获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；
    根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；
    若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
  17. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时使所述处理器实现：
    获取待处理的电子票据、订单数据和账单数据；所述账单数据在利用报销码对所述订单数据进行支付后生成；所述电子票据基于所述账单数据生成；
    根据所述电子票据、所述订单数据和所述账单数据中的至少一种，创建可编辑报销单；
    根据所述电子票据、所述订单数据和所述账单数据，在至少一个核验维度下对可编辑报销单进行可信核验；
    若在各所述核验维度下均核验通过，则确定可编辑报销单为可信报销单。
PCT/CN2022/103546 2021-05-25 2022-07-04 票据处理方法、装置、设备和存储介质 WO2022247966A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110572091.6 2021-05-25
CN202110572091.6A CN113222723B (zh) 2021-05-25 2021-05-25 票据处理方法、装置、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2022247966A1 true WO2022247966A1 (zh) 2022-12-01

Family

ID=77098156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/103546 WO2022247966A1 (zh) 2021-05-25 2022-07-04 票据处理方法、装置、设备和存储介质

Country Status (2)

Country Link
CN (2) CN115049471A (zh)
WO (1) WO2022247966A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116029675A (zh) * 2023-01-30 2023-04-28 北京四方启点科技有限公司 一种报销申请单审批方法和装置
CN117474502A (zh) * 2023-12-27 2024-01-30 国网浙江省电力有限公司金华供电公司 财务数据处理方法、系统及存储介质
CN117575828A (zh) * 2024-01-16 2024-02-20 江苏航运职业技术学院 一种基于云计算的财务报销数据处理系统及方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115049471A (zh) * 2021-05-25 2022-09-13 支付宝(杭州)信息技术有限公司 票据处理方法、装置、设备和存储介质
CN113807339A (zh) * 2021-09-02 2021-12-17 支付宝(杭州)信息技术有限公司 数据处理方法、装置及设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030200173A1 (en) * 2002-04-18 2003-10-23 Benq Corporation Personalized bill information request with short message service
US20080114643A1 (en) * 2001-10-01 2008-05-15 Peggy Milovina-Meyer Methods of Creating Electronic Customs Invoices
CN110188336A (zh) * 2019-05-27 2019-08-30 厦门商集网络科技有限责任公司 一种基于oa申请单生成报销单的方法和装置
CN110264288A (zh) * 2019-05-20 2019-09-20 深圳壹账通智能科技有限公司 基于信息识别技术的数据处理方法及相关装置
CN110782329A (zh) * 2019-09-27 2020-02-11 国信电子票据平台信息服务有限公司 一种财务发票认证管理方法及系统
CN112069893A (zh) * 2020-08-03 2020-12-11 中国铁道科学研究院集团有限公司电子计算技术研究所 一种票据处理方法、装置、电子设备及存储介质
CN113222723A (zh) * 2021-05-25 2021-08-06 支付宝(杭州)信息技术有限公司 票据处理方法、装置、设备和存储介质

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014127444A1 (en) * 2013-02-19 2014-08-28 Likisoft Stores Inc. Methods and systems for facilitating on-line commerce
JP6059319B1 (ja) * 2015-09-30 2017-01-11 三井住友カード株式会社 代金支払管理システム、及び代金支払管理方法
CN105303438A (zh) * 2015-11-11 2016-02-03 中国建设银行股份有限公司 一种消费金额数据处理方法及系统
CN107644302A (zh) * 2017-10-16 2018-01-30 广州云系信息科技有限公司 跨平台订单核算方法、装置、可移动终端及支付系统
CN109087155A (zh) * 2018-06-19 2018-12-25 优识云创（北京）科技有限公司 一种发票管理的方法和设备
CN110458562B (zh) * 2019-08-08 2021-05-18 腾讯科技（深圳）有限公司 票据报销方法、装置和设备及计算机存储介质
CN112668296A (zh) * 2019-09-30 2021-04-16 北京国双科技有限公司 一种报销单生成方法和系统
CN110782331A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种打车方法及装置、电子设备、存储介质
CN110782320A (zh) * 2019-10-25 2020-02-11 上海燕汐软件信息科技有限公司 一种订单处理方法、装置、订单报消系统及存储介质
CN110889693B (zh) * 2019-11-22 2021-06-25 支付宝(杭州)信息技术有限公司 一种支付方法、装置及系统
CN111797837A (zh) * 2020-06-30 2020-10-20 远光软件股份有限公司 单据智能报销方法、系统、计算机设备及存储介质
CN112183796A (zh) * 2020-09-21 2021-01-05 远光软件股份有限公司 服务预订方法、电子设备及存储介质
CN112330266A (zh) * 2020-09-30 2021-02-05 山东浪潮通软信息科技有限公司 一种单据生成方法、设备及介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080114643A1 (en) * 2001-10-01 2008-05-15 Peggy Milovina-Meyer Methods of Creating Electronic Customs Invoices
US20030200173A1 (en) * 2002-04-18 2003-10-23 Benq Corporation Personalized bill information request with short message service
CN110264288A (zh) * 2019-05-20 2019-09-20 深圳壹账通智能科技有限公司 基于信息识别技术的数据处理方法及相关装置
CN110188336A (zh) * 2019-05-27 2019-08-30 厦门商集网络科技有限责任公司 一种基于oa申请单生成报销单的方法和装置
CN110782329A (zh) * 2019-09-27 2020-02-11 国信电子票据平台信息服务有限公司 一种财务发票认证管理方法及系统
CN112069893A (zh) * 2020-08-03 2020-12-11 中国铁道科学研究院集团有限公司电子计算技术研究所 一种票据处理方法、装置、电子设备及存储介质
CN113222723A (zh) * 2021-05-25 2021-08-06 支付宝(杭州)信息技术有限公司 票据处理方法、装置、设备和存储介质

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116029675A (zh) * 2023-01-30 2023-04-28 北京四方启点科技有限公司 一种报销申请单审批方法和装置
CN116029675B (zh) * 2023-01-30 2023-07-25 北京四方启点科技有限公司 一种报销申请单审批方法和装置
CN117474502A (zh) * 2023-12-27 2024-01-30 国网浙江省电力有限公司金华供电公司 财务数据处理方法、系统及存储介质
CN117575828A (zh) * 2024-01-16 2024-02-20 江苏航运职业技术学院 一种基于云计算的财务报销数据处理系统及方法
CN117575828B (zh) * 2024-01-16 2024-03-12 江苏航运职业技术学院 一种基于云计算的财务报销数据处理系统及方法

Also Published As

Publication number Publication date
CN113222723B (zh) 2022-07-05
CN113222723A (zh) 2021-08-06
CN115049471A (zh) 2022-09-13

Similar Documents

Publication Publication Date Title
WO2022247966A1 (zh) 票据处理方法、装置、设备和存储介质
US7739193B2 (en) Paying multiple payees through integration of a third-party on-line payment system with an enterprise information technology system
US10121208B2 (en) Thematic repositories for transaction management
WO2021063045A1 (zh) 基于区块链的交易查询、交易数据处理方法、装置及设备
US7913173B2 (en) Method and apparatus for acquiring data presented within a web browser
WO2022247968A1 (zh) 数据处理
CN106776515A (zh) 数据处理的方法及装置
JP2007157144A (ja) データ要素のモデル化
US20080162340A1 (en) Integrating enterprise information technology systems with a third-party on-line payment system
US10366457B2 (en) Thematic repositories for transaction management
WO2022247964A1 (zh) 票据处理方法、装置、电子设备及存储介质
WO2022247963A1 (zh) 票据的生成
CN112352444A (zh) 用于管理并提供用户体验的位置平台
CN110390182A (zh) 一种确定小程序类目的方法、系统及设备
WO2022247965A1 (zh) 账单处理
WO2023284558A1 (zh) 基于聚合码的支付页面发送
WO2018063659A1 (en) Systems and methods for generating customized reports based on operational stage rules
WO2024032350A1 (zh) 交易账单的票据处理方法及装置
CN110018819A (zh) 一种数据核对脚本生成方法、装置及设备
WO2023151438A1 (zh) 支付交互处理
CN109947797A (zh) 一种数据检查装置及方法
US20150363889A1 (en) Methods and Systems for Electronic Receipt Tracking, Storage, and Provision
US10394885B1 (en) Methods, systems and computer program products for generating personalized financial podcasts
CN110223052A (zh) 数据处理方法、装置和机器可读介质
Rajalakshmi et al. Smart Ration System using Application Development with MONGO Database

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: 22810689

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18563603

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE