WO2019100633A1 - 发票报销的方法、装置、存储介质及终端 - Google Patents

发票报销的方法、装置、存储介质及终端 Download PDF

Info

Publication number
WO2019100633A1
WO2019100633A1 PCT/CN2018/081025 CN2018081025W WO2019100633A1 WO 2019100633 A1 WO2019100633 A1 WO 2019100633A1 CN 2018081025 W CN2018081025 W CN 2018081025W WO 2019100633 A1 WO2019100633 A1 WO 2019100633A1
Authority
WO
WIPO (PCT)
Prior art keywords
invoice
reimbursement
detailed information
terminal
information
Prior art date
Application number
PCT/CN2018/081025
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 WO2019100633A1 publication Critical patent/WO2019100633A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device
    • 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
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing

Definitions

  • the present application belongs to the field of communications technologies, and in particular, to a method, an apparatus, a storage medium, and a terminal for invoicing an invoice.
  • the prior art includes two methods.
  • the first is to initiate reimbursement by manually filling in the invoice content, the reimbursement party needs to fill all the information of the invoice to the specified page one by one, including but not limited to the invoice number, invoice code, amount, billing date, purchaser name, The name of the seller, the taxpayer identification number, the account opening bank and the account number are cumbersome and prone to the phenomenon of incorrect filling and filling, which leads to the inability to complete the reimbursement and is inefficient.
  • the second is to initiate reimbursement by uploading an electronic invoice.
  • the reimbursement unit identifies the content in the electronic invoice based on the image recognition technology and completes the automatic reimbursement. Although the method does not need to manually enter the invoice information, the reimbursement unit needs to be equipped with an electronic invoice identification device. higher cost.
  • the existing invoice reimbursement method has the problems of cumbersome operation, low efficiency and high cost.
  • the embodiment of the present invention provides a method, a device, a storage medium and a terminal for reimbursement of invoices, so as to solve the problems of cumbersome operation, low efficiency and high cost in the existing reimbursement mode.
  • the embodiment of the present application provides a method for invoicing an invoice, and the reimbursing method includes:
  • the reimbursement operation of the to-reimbursement invoice is performed based on the detailed information.
  • the method further includes:
  • the detailed information of the invoice to be reimbursed is stored in a database.
  • the method further includes:
  • the original image and the detailed information are associated and stored.
  • performing reimbursement operation on the to-reimbursement invoice based on the detailed information includes:
  • the consumption amount corresponding to the to-be-reimbursed invoice is drawn from the enterprise transaction account and stored in the user transaction account.
  • the method further includes:
  • the prompt information of the fake invoice is generated, and the prompt information is sent to the foreground terminal.
  • the embodiment of the present application further provides an apparatus for invoicing an invoice, the reimbursing apparatus comprising:
  • the obtaining module is configured to obtain two-dimensional code information of the to-be-claimed invoice sent by the front-end terminal;
  • a decoding module configured to parse the two-dimensional code information based on a preset decoding library, and acquire basic information recorded in the two-dimensional code information
  • a calling module configured to invoke a tax system interface, send the basic information to the tax system interface, and obtain detailed information corresponding to the to-reimbursement invoice returned by the tax system interface according to the basic information;
  • the reimbursement module is configured to perform a reimbursement operation on the invoice to be reimbursed based on the detailed information when acquiring the reimbursement instruction sent by the front terminal.
  • the reimbursement module includes:
  • a generating unit configured to generate an approval request corresponding to the to-be-reimbursed invoice according to the reimbursement instruction sent by the foreground terminal;
  • An approval unit configured to complete a signing approval process for detailed information of the to-be-reimbursed invoice based on the approval request, and generate a reimbursement execution instruction according to the result of the signing approval process
  • the payment unit is configured to: when the reimbursement execution instruction is to perform the reimbursement payment, the amount of the consumption corresponding to the to-be-claimed invoice is deleted from the enterprise transaction account and stored in the user transaction account.
  • the device further includes:
  • a detecting module configured to detect a network status if the detailed information of the to-be-claimed invoice returned by the tax system interface cannot be obtained;
  • the prompting module is configured to generate prompt information of the fake invoice if the network status is connected, and send the prompt information to the foreground terminal.
  • the device further includes:
  • a sending module configured to send the detailed information to the foreground terminal after obtaining the detailed information corresponding to the to-be-reimbursed invoice returned by the tax system interface according to the basic information, so that the foreground terminal presents the user to the user Details of the reimbursement invoice;
  • a storage module configured to store, in the database, the detailed information of the to-be-claimed invoice when the confirmation instruction of the to-be-claimed invoice sent by the front-end terminal is obtained.
  • the storage module can also be used to:
  • the original image and the detailed information are associated and stored.
  • the embodiment of the present application further provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or more The processor performs the following steps:
  • the reimbursement operation of the to-reimbursement invoice is performed based on the detailed information.
  • the embodiment of the present application further provides a terminal, where the terminal includes a memory, a processor, and computer readable instructions stored on the memory and executable on the processor, when the processor executes the computer readable instructions.
  • the reimbursement operation of the to-reimbursement invoice is performed based on the detailed information.
  • FIG. 1 is a first implementation flowchart of a method for invoicing an invoice provided by an embodiment of the present application
  • FIG. 2 is a second implementation flowchart of a method for invoicing an invoice provided by an embodiment of the present application
  • FIG. 3 is a third implementation flowchart of a method for invoicing an invoice provided by an embodiment of the present application.
  • FIG. 4 is a fourth implementation flowchart of a method for invoicing an invoice provided by an embodiment of the present application.
  • FIG. 5 is a structural diagram of a device for invoicing an invoice provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a terminal provided by an embodiment of the present application.
  • FIG. 1 shows a first implementation flow of a method for invoicing an invoice provided by an embodiment of the present application.
  • the invoice reimbursement process is implemented based on the front terminal and the background server.
  • the communication between the front terminal and the background server can be connected by wire or wirelessly.
  • the front-end terminal is configured to install and run a designated APP with an invoice reimbursement function, and complete interaction with the user, including but not limited to a smart phone, a tablet computer, a learning machine, and the like.
  • the background server is configured to store user account information, transaction account number, invoice detailed information, response message, and push notification of the specified APP, and complete interaction with the tax system.
  • the method for invoicing the invoice provided by the embodiment of the present application is applied to the background server. Referring to Figure 1, the method for invoicing an invoice includes:
  • step S101 the two-dimensional code information of the invoice to be reimbursed sent by the foreground terminal is acquired.
  • the to-be-claimed invoice is a paper invoice with a two-dimensional code identification, including but not limited to a special invoice and a general invoice.
  • a sweep function is integrated on the designated APP of the foreground terminal.
  • the foreground terminal turns on the camera, starts the camera, identifies the two-dimensional code information in the scan frame, and then sends the two-dimensional code information to the background server.
  • the background server receives the two-dimensional code information, and obtains indication information for performing a reimbursement operation.
  • step S102 the two-dimensional code information is parsed based on a preset decoding library, and basic information recorded in the two-dimensional code information is acquired.
  • the decoding library includes, but is not limited to, a two-dimensional code open source library Zbar and Zxing.
  • the embodiment of the present application is based on the two-dimensional code open source library Zbar or Zxing compiled from the C++ source code/interface of the github clone to parse the two-dimensional code information sent by the foreground terminal, and obtain the record in the two-dimensional code information.
  • the basic information includes, but is not limited to, an invoice number, an invoice code, an amount, and a date. Both the invoice number and the invoice code are the codes given to the invoice by the tax department, and are used as identifiers for the invoices to be reimbursed to check the authenticity of the invoice.
  • step S103 the tax system interface is invoked, the basic information is sent to the tax system interface, and detailed information corresponding to the to-reimbursement invoice returned by the tax system interface according to the basic information is obtained.
  • the embodiment of the present application further invokes the tax system interface, and sends the invoice number and the invoice code in the basic information to the tax system interface by using a post request method, to request the tax system to be reimbursed. Details of the invoice.
  • the tax system interface is an open query interface of the tax system, and the url is https://fpcy.szgs.gov.cn : 443/WebQuery/query for invoking the invoice number and the invoice code, and returning the invoice. Details.
  • the background server sends a query request to the tax system interface according to the basic information by using a post request method, and the data format adopts a JSON format.
  • the parameter in the query request includes, but is not limited to, the billing date kprq, the invoice amount fpje, the invoice type fplx, the verification code yzm, the verification code, in addition to the invoice code fpdm and the invoice number fphm. Time yzmSj, directory index, check code iv (Invoice Verification).
  • the JSON format example is as follows:
  • the invoice code is 4403162320
  • the invoice number is 24945044
  • the billing date is 20170223
  • the invoice amount is 263102
  • the invoice type is 04
  • the verification code time is 2017-08-1616:29:32
  • the catalogue is e7b9a784ae4367260cccdeda2aad7ae6
  • the check code is f7a8de45b198cf08bc9a1ca3d513c584 .
  • the tax system interface acquires the detailed information of the invoice to be reimbursed according to the invoice code fpdm and the invoice number fphm in the query request, generates a data packet in JSON format, and returns to the foreground terminal.
  • the detailed information includes, but is not limited to, consumption time, name, taxpayer identification number, address, telephone number, bank account number, unit price, and usage classification.
  • step S104 when the reimbursement instruction sent by the foreground terminal is acquired, the reimbursement operation of the to-reimbursement invoice is performed based on the detailed information.
  • the tax system interface can return the detailed information of the invoice to be reimbursed, it indicates that the invoice for reimbursement is true and valid, and when the detailed information of the invoice to be reimbursed cannot be returned, it indicates that the invoice for reimbursement is false and invalid. Therefore, if the tax system interface returns detailed information, the detailed information of the pending invoice is saved to the database.
  • the reimbursement instruction sent by the front-end terminal is obtained, the reimbursement operation of the invoice for reimbursement is completed according to the user transaction account currently registered in the user account of the specified APP, that is, a lot of the transaction account is entered into the account. Reimbursement for the amount of consumption of the invoice to be reimbursed.
  • the embodiment of the present application scans the two-dimensional code information on the invoice to be reimbursed, and obtains detailed information by calling the tax system interface, thereby avoiding the user manually inputting the invoice information, and simultaneously verifying the authenticity of the invoice, providing a kind of verification
  • the new invoice reimbursement method, the reimbursement process is more convenient and fast, and effectively solves the problem of cumbersome and inefficient operation process in the existing enterprise based on paper invoice reimbursement.
  • FIG. 2 it is a schematic diagram of a second implementation process of the method for invoicing reimbursement provided by the embodiment of the present application.
  • the method includes:
  • Steps S201 to S203 wherein the steps S201 to S203 are the same as the steps S101 to S103 described in the embodiment of the present invention.
  • steps S201 to S203 are the same as the steps S101 to S103 described in the embodiment of the present invention.
  • details refer to the description of the foregoing embodiment, and details are not described herein again.
  • the reimbursement method further includes:
  • step S204 the detailed information is transmitted to the foreground terminal such that the foreground terminal presents the user with the detailed information of the to-be-claimed invoice.
  • the foreground terminal enters the filling interface of the invoice form after scanning the two-dimensional code information of the invoice.
  • the background server sends the detailed information to the foreground terminal.
  • the front terminal After receiving the detailed information, the front terminal automatically enters the invoice form according to the field format, and fills in the corresponding field value into the filling interface to display the waiting to the user.
  • the detailed information of the reimbursement invoice is provided for the user to confirm, thereby avoiding the user to manually input the invoice information, which greatly simplifies the user's operation.
  • step S205 when the confirmation instruction of the to-be-claimed invoice sent by the front-end terminal is acquired, the detailed information of the to-be-claimed invoice is stored in a database.
  • the “confirmation” function identifier is also provided on the invoice form. If the user browses the invoice form and confirms that the confirmation is correct, the confirmation command may be input by triggering the “confirmation” function identifier. After detecting the confirmation command, the foreground terminal sends it to the background server.
  • the background server saves the detailed information of the to-be-claimed invoice to the specified database according to the confirmation instruction.
  • the embodiment of the present application saves the detailed information of the to-be-claimed invoice to the database if and only after the user confirms, which effectively reduces the inventory of the reimbursement form on the background server.
  • step S206 when the reimbursement instruction sent by the foreground terminal is acquired, the reimbursement operation of the to-reimbursement invoice is performed based on the detailed information.
  • the step S206 is the same as the step S104 described in the embodiment of the present invention. For details, refer to the description of the foregoing embodiment, and details are not described herein again.
  • the reimbursement method may further include:
  • the original image and the detailed information are associated and stored.
  • the "original upload” function identifier is also provided on the invoice form. If it is detected that the user triggers the “original upload” function identifier, the front terminal opens a local album, prompts the user to select an original image of the invoice to be reimbursed, and obtains an original image selected by the user, and sends the original image to the background server.
  • the background server associates the detailed information of the to-be-claimed invoice with the original image and then saves it to the specified database.
  • the embodiment of the present application facilitates the original verification of the detailed information of the invoice to be reimbursed by associating the original image of the invoice to be reimbursed; the original image of the invoice to be reimbursed is associated with the detailed information, and is further optimized. Management and storage operations of the background server.
  • FIG. 3 it is a schematic diagram of a third implementation process of the method for invoicing reimbursement provided by the embodiment of the present application.
  • the step S104 when acquiring the reimbursement instruction sent by the foreground terminal, performing the reimbursement operation on the to-reimbursement invoice based on the detailed information includes:
  • step S1041 an approval request corresponding to the to-be-claimed invoice is generated according to a reimbursement instruction sent by the foreground terminal.
  • the reimbursement instruction is triggered by a user of the foreground terminal, and if the reimbursement instruction is detected, the foreground terminal sends the reimbursement instruction and the user account to the background server.
  • the user account should be understood as the user credentials for the user to log in to the specified APP.
  • the server generates an approval request according to the reimbursement instruction, and transfers the workflow flow to the corresponding enterprise leader to complete the reimbursement approval operation on the to-be-reimbursed invoice, thereby realizing the online approval operation without the user offline auditing material.
  • step S1042 a signing approval process for detailed information of the to-be-claimed invoice is completed based on the approval request, and a reimbursement execution instruction is generated according to the result of the signing approval process.
  • the embodiment of the present application completes the approval and confirmation operation of the transaction order by the internal leadership of the enterprise through the approval request.
  • the approval result of the signing approval process includes two types, namely, the enterprise leader approves the invoice for reimbursement and approves the reimbursement, and does not approve the invoice for reimbursement and refuses to reimburse, and the case of not accepting includes the case
  • the reimbursement invoice does not meet the reimbursement rules.
  • the reimbursement invoice is not within the effective reimbursement period, and the consumption type of the reimbursement invoice is not a reimbursable item.
  • the reimbursement execution instruction generated by the signing approval process is the execution reimbursement payment; when the enterprise leader does not approve the reimbursement invoice and refuses to reimburse, the signing approval process
  • the generated reimbursement execution instruction is a rejection of the reimbursement payment.
  • step S1043 if the reimbursement execution instruction is to perform reimbursement payment, the amount of consumption corresponding to the to-be-reimbursed invoice is drawn from the enterprise transaction account and stored in the user transaction account.
  • both the enterprise and the user need to record the corresponding transaction account on the background server.
  • the server After receiving the reimbursement execution instruction, the server obtains the enterprise transaction account number, obtains the corresponding user transaction account number according to the user account, confirms the consumption amount of the to-be-reimbursed invoice, and then draws a reimbursement from the enterprise transaction account not less than the consumption amount. The amount, the reimbursement amount is entered into the user transaction account. The user transaction account will receive the reimbursement amount within the specified time range.
  • the embodiment of the present application realizes the online reimbursement method of the invoice by combining the user and the enterprise to record the transaction account, and adds the signing approval process, thereby ensuring the security of the reimbursement process and facilitating the elimination of the reimbursement behavior of the violation.
  • FIG. 4 it is a schematic diagram of a fourth implementation process of the method for invoicing reimbursement provided by the embodiment of the present application.
  • the tax system interface can implement the verification operation of the reimbursement invoice. If the tax system interface can return the detailed information of the invoice to be reimbursed, it indicates that the invoice to be reimbursed is true and valid, and if it cannot be returned When reimbursing the detailed information of the invoice, it indicates that the invoice for reimbursement is false and invalid.
  • the method for reimbursing the invoice may further include:
  • step S105 if the detailed information of the invoice to be reimbursed corresponding to the basic information returned by the tax system interface cannot be obtained, the network status is detected.
  • the background server when the background server detects the network status, the background server detects the network connection parameter and detects the domain name status. First, it is detected whether the network connection parameter is obtained. If the network connection parameter fails to be obtained, the status information of the network connection parameter acquisition failure is generated; if the network connection parameter is successfully obtained, the domain name is detected to be working normally, and if the domain name detection fails, the domain name is generated. If the domain name detection is unobstructed, the status information of the network connection is generated, and the network is confirmed to be unobstructed.
  • step S106 if the network status is connected, the prompt information of the fake invoice is generated, and the prompt information is sent to the foreground terminal.
  • the response time may range from 30 minutes.
  • the background server After the preset response time arrives, the background server generates prompt information of the fake invoice, and returns the prompt information to the foreground terminal, so that the foreground terminal displays the prompt information to the user, and the reimbursement cannot be initiated. Prompt message.
  • the embodiment of the present application determines the authenticity of the invoice to be reimbursed by combining the interaction status with the tax system interface and the network status of the background server, and generates prompt information of the fake invoice, which is beneficial to improving the reliability of the invoice reimbursement and eliminating the illegality. Reimbursement behavior.
  • the size of the serial number of each step does not mean the order of execution order, and the order of execution of each step should be determined by its function and internal logic, and should not constitute any implementation process of the embodiment of the present application. limited.
  • FIG. 5 is a structural diagram of the apparatus for invoicing reimbursement provided by the embodiment of the present application. For the convenience of description, only parts related to the embodiment of the present application are shown.
  • the invoicing reimbursing device is used to implement the invoice reimbursement method described in the foregoing embodiments of FIG. 1, FIG. 2, FIG. 3, and FIG. 4, and may be a software unit and a hardware unit built in the server. Or a combination of hardware and software,
  • the apparatus for invoicing the invoice includes:
  • the obtaining module 51 is configured to obtain two-dimensional code information of the to-be-claimed invoice sent by the front-end terminal;
  • the decoding module 52 is configured to parse the two-dimensional code information based on a preset decoding library, and acquire basic information recorded in the two-dimensional code information;
  • the calling module 53 is configured to invoke the tax system interface, send the basic information to the tax system interface, and obtain detailed information corresponding to the to-reimbursement invoice returned by the tax system interface according to the basic information;
  • the reimbursement module 54 is configured to perform a reimbursement operation on the invoice to be reimbursed based on the detailed information when acquiring the reimbursement instruction sent by the foreground terminal.
  • the reimbursement module 54 includes:
  • a generating unit 541, configured to generate an approval request corresponding to the to-be-claimed invoice according to the reimbursement instruction sent by the foreground terminal;
  • the approval unit 542 is configured to complete a signing approval process for the detailed information of the invoice to be reimbursed based on the approval request, and generate a reimbursement execution instruction according to the result of the signing approval process;
  • the payment unit 543 is configured to: when the reimbursement execution instruction is to perform the reimbursement payment, the payment amount corresponding to the to-reimbursement invoice is deleted from the enterprise transaction account and stored in the user transaction account.
  • the device further includes:
  • the detecting module 55 is configured to detect a network status if the detailed information of the to-be-claimed invoice returned by the tax system interface cannot be obtained;
  • the prompting module 56 is configured to generate prompt information of the fake invoice if the network status is connected, and send the prompt information to the foreground terminal.
  • the device further includes:
  • a sending module configured to send the detailed information to the foreground terminal after obtaining the detailed information corresponding to the to-be-reimbursed invoice returned by the tax system interface according to the basic information, so that the foreground terminal presents the user to the user Details of the reimbursement invoice;
  • a storage module configured to store, in the database, the detailed information of the to-be-claimed invoice when the confirmation instruction of the to-be-claimed invoice sent by the front-end terminal is obtained.
  • the sending module sends the detailed information to the foreground terminal, so that after receiving the detailed information, the front terminal automatically enters the invoice form according to the field format, and fills the corresponding field value into the filling interface to the user.
  • the detailed information of the invoice to be reimbursed is displayed for confirmation, thereby preventing the user from manually inputting the invoice information, which greatly simplifies the operation of the user.
  • the storage module saves the detailed information of the to-be-claimed invoice to the database if and only after the user confirms, thereby effectively reducing the inventory of the reimbursement form on the server.
  • the storage module is further configured to:
  • the original image and the detailed information are associated and stored.
  • the embodiment of the present application realizes the original verification of the detailed information of the to-be-claimed invoice during the reimbursement operation by associating the original image of the invoice to be reimbursed; the original image of the invoice to be reimbursed is associated with the detailed information. It facilitates the management and storage of the invoice.
  • each module/unit in the embodiment of the present application may be used to implement all the technical solutions in the foregoing method embodiments, and the specific working process may refer to the corresponding process in the foregoing method embodiments, and details are not described herein again. .
  • This embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon.
  • the one or more non-transitory readable storage mediums storing computer readable instructions, when executed by one or more processors, causing one or more processors to perform the invoice reimbursement in embodiment 1.
  • the method in order to avoid repetition, will not be described here.
  • the computer readable instructions when executed by the processor, the functions of the modules/units in the apparatus for invoicing in the embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instructions, a recording medium, a USB flash drive, a mobile hard drive, a magnetic Discs, optical discs, computer memories, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media.
  • FIG. 6 is a schematic diagram of a terminal according to an embodiment of the present disclosure, where the terminal includes but is not limited to a server and a mobile terminal.
  • the terminal 6 of this embodiment includes a processor 60, a memory 61, and computer readable instructions 62 stored in the memory 61 and executable on the processor 60.
  • the steps in the method embodiment of the above-mentioned invoice reimbursement when the processor 60 executes the computer readable instructions 62 such as steps S101 to S104 shown in FIG. 1 and steps S201 to S206 in the embodiment of FIG. 2, Steps S1041 to S1043 described in the embodiment of FIG. 3 and steps S101 to S106 described in the embodiment of FIG. 4; or, the apparatus implementation of the above-mentioned invoice reimbursement when the processor 60 executes the computer readable instructions 62
  • the functions of the modules/units in the example such as the functions of the modules 51 to 56 shown in FIG.
  • the so-called processor 60 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like, which is a control center of the terminal, and connects various parts of the entire terminal using various interfaces and lines.
  • the memory 61 can be used to store the computer readable instructions and/or modules by running or executing computer readable instructions and/or modules stored in the memory, and recalling data stored in the memory Implementing various functions of the terminal.
  • the memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored. Data created based on the use of the terminal, etc.
  • the memory may include a high-speed random access memory, and may also include non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD). , Flash Card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD).
  • SD Secure Digital
  • Flash Card at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请适用于通信技术领域，提供了一种发票报销的方法，包括：获取前台终端发送的待报销发票的二维码信息；基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。本申请提供了一种新的发票报销方式，避免了用户手动输入发票信息，报销过程更加方便、快捷，有效地解决了现有企业内部基于纸质发票报销时存在的操作过程繁琐、效率低的问题。

Description

发票报销的方法、装置、存储介质及终端
本申请以2017年11月23日提交的申请号为201711177737.0，名称为“发票报销的方法、装置、存储介质及终端”的中国发明专利申请为基础，并要求其优先权。
技术领域
本申请属于通信技术领域，尤其涉及一种发票报销的方法、装置、存储介质及终端。
背景技术
在进行发票报销时，现有技术包括两种方式。其一是通过手动填写发票内容发起报销，需要报销方将发票的所有信息一项一项地填充到指定页面，这些信息包括但不限于发票号、发票编码、金额、开票日期、购买方名称、销售方名称、纳税人识别号、开户行及账号，过程繁琐，且容易出现错填漏填的现象，从而导致无法完成报销，效率低。其二是通过上传电子发票来发起报销，由报销单位基于图像识别技术来识别电子发票中的内容，完成自动报销，尽管该方式无需手动录入发票信息，但需要报销单位配备电子发票的识别装置，成本较高。综上所述，现有的发票报销方式存在操作过程繁琐、效率低以及成本高的问题。
发明内容
本申请实施例提供了一种发票报销的方法、装置、存储介质及终端，以解决现有的报销方式存在的操作过程繁琐、效率低以及成本高的问题。
本申请实施例提供了一种发票报销的方法，所述报销方法包括：
获取前台终端发送的待报销发票的二维码信息；
基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
进一步地，在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，所述方法还包括：
将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
进一步地，在将所述详细信息发送至所述前台终端之后，所述方法还包括：
获取所述前台终端发送的待报销发票的原件图像；
关联及存储所述原件图像与所述详细信息。
进一步地，所述当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作包括：
根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
进一步地，所述方法还包括：
若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
本申请实施例还提供了一种发票报销的装置，所述报销装置包括：
获取模块，用于获取前台终端发送的待报销发票的二维码信息；
解码模块，用于基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
调用模块，用于调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
报销模块，用于当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
进一步地，所述报销模块包括：
生成单元，用于根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
审批单元，用于基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
划款单元，用于若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待 报销发票对应的消费金额存入用户交易账号。
进一步地，所述装置还包括：
检测模块，用于若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
提示模块，用于若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
进一步地，所述装置还包括：
发送模块，用于在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
存储模块，用于当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
进一步地，所述存储模块还可以用于：
获取所述前台终端发送的待报销发票的原件图像；
关联及存储所述原件图像与所述详细信息。
本申请实施例还提供了一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
获取前台终端发送的待报销发票的二维码信息；
基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
本申请实施例还提供了一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取前台终端发送的待报销发票的二维码信息；
基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
本申请的一个或多个实施例的细节在下面的附图及描述中提出。本申请的其他特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他附图。
图1是本申请实施例提供的发票报销的方法的第一实现流程图；
图2是本申请实施例提供的发票报销的方法的第二实现流程图；
图3是本申请实施例提供的发票报销的方法的第三实现流程图；
图4是本申请实施例提供的发票报销的方法的第四实现流程图；
图5是本申请实施例提供的发票报销的装置的组成结构图；
图6是本申请实施例提供的终端的示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1示出了本申请实施例提供的发票报销的方法的第一实现流程。
在本申请实施例中，发票报销过程基于前台终端和后台服务器共同实现。所述前台终端和后台服务器之间能够通过有线或无线的方式连接通信。其中，所述前台终端用于安装及运行具有发票报销功能的指定APP，完成与用户的交互，包括但不限于智能手机、平板电脑、学习机等。所述后台服务器用于存储所述指定APP的用户帐号信息、交易账号、发票详细信息、响应消息以及推送通知等，完成与税务系统的交互。本申请实施例提供的所述发票报销的方法应用于所述后台服务器。参阅图1，所述发票报销的方法包括：
在步骤S101中，获取前台终端发送的待报销发票的二维码信息。
在这里，所述待报销发票为具有二维码标识的纸质发票，包括但不限于专用发票和普通发票。前台终端的所述指定APP上集成了扫一扫功能。当检测到用户触发所述扫一扫功能标识时，所述前台终端打开摄像头，启动相机，识别扫描框内的二维码信息，然后将所述二 维码信息发送至后台服务器。后台服务器接收所述二维码信息，得到执行报销操作的指示信息。
在步骤S102中，基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息。
在这里，所述解码库包括但不限于二维码开源库Zbar和Zxing。本申请实施例基于所述二维码开源库Zbar或Zxing从github上clone的C++源码/接口编译出来的dll解析前台终端发送过来的二维码信息，得到所述二维码信息中记录的所述待报销发票的基本信息。其中，所述基本信息包括但不限于发票号码、发票代码、金额、日期。发票号码和发票代码均为是税务部门给予发票的编码，作为待报销发票的标识符，用于查询发票的真伪。
在步骤S103中，调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息。
在得到基本信息之后，本申请实施例进一步调用税务系统接口，采用post请求方式，将所述基本信息中的发票号码和发票代码发送至所述税务系统接口，以向税务系统请求所述待报销发票的详细信息。
其中，所述税务系统接口为税务系统向外开放的查询接口，url为 https://fpcy.szgs.gov.cn:443/WebQuery/query，用于传入发票号码和发票代码，以及返回发票的详细信息。后台服务器根据所述基本信息，采用post的请求方式向所述税务系统接口发送查询请求，数据格式采用JSON格式。可选地，在实际应用中，所述查询请求中的参数除了包括发票代码fpdm、发票号码fphm之后，还包括但不限于开票日期kprq、发票金额fpje、发票类型fplx、验证码yzm、验证码时间yzmSj、目录index、校验码iv(Invoice Verification)。示例性地，以上述参数为例，JSON格式示例如下：
:"{"fpdm":"4403162320","fphm":"24945044","kprq":"20170223","fpje":"263102","fplx":"04","yzm":"mm","yzmSj":"2017-08-1616:29:32","index":"e7b9a784ae4367260cccdeda2aad7ae6","iv":"f7a8de45b198cf08bc9a1ca3d513c584","salt":"96493c87ac6019035dcb9bff38351d69"}"
其中，发票代码为4403162320，发票号码为24945044，开票日期为20170223，发票金额为263102，发票类型为04，验证码时间为2017-08-1616:29:32，目录为e7b9a784ae4367260cccdeda2aad7ae6，校验码为f7a8de45b198cf08bc9a1ca3d513c584。
所述税务系统接口根据所述查询请求中的发票代码fpdm、发票号码fphm获取所述待报销发票的详细信息，生成JSON格式的数据包，并返回至所述前台终端。其中，所述详细信息包括但不限于消费时间、名称、纳税人识别号、地址、电话、开户银行账号、单价、用途分类。
在步骤S104中，当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
在这里，所述税务系统接口能返回待报销发票的详细信息时，表明所述待报销发票是真实有效的，不能返回待报销发票的详细信息时，表明所述待报销发票是虚假无效的。因此，若税务系统接口返回了详细信息，则将所述待报销发票的详细信息保存至数据库中。当获取到前台终端发送的报销指令时，根据当前登录所述指定APP的用户帐号备案的用户交易账号，完成对所述待报销发票的报销操作，即向所述用户交易账号中划入不少于所述待报销发票的消费金额的报销款。
本申请实施例通过扫描待报销发票上的二维码信息，以及通过调用税务系统接口获取详细信息，避免了用户手动输入发票信息，且同时完成了对发票真伪的校验，提供了一种新的发票报销方式，报销过程更加方便、快捷，有效地解决了现有企业内部基于纸质发票报销时存在的操作过程繁琐、效率低的问题
进一步地，基于图1提供的发票报销的方法的第一实现流程的基础上，提出本申请实施例提供的发票报销的方法的第二实现流程。
如图2所示，是本申请实施例提供的发票报销的方法的第二实现流程示意图。在本申请实施例中，所述方法包括：
步骤S201至步骤S203，其中步骤S201至步骤S203与图1实施例中所述的步骤S101至步骤S103相同，具体请参见上述实施例的叙述，此处不再赘述。
在所述步骤S103获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，所述报销方法还包括：
在步骤S204中，将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息。
在这里，所述前台终端在扫描发票的二维码信息后，进入发票表单的填充界面。后台服务器将详细信息发送至所述前台终端，所述前台终端接收到所述详细信息后，按照字段格式自动录入发票表单，将对应的字段值填写进填充界面上，以向用户展示所述待报销发票的详细信息供用户完成确认，从而避免了用户手动输入发票信息，极大地简化了用户的操作。
在步骤S205中，当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
在这里，所述发票表单上还提供了“确认”功能标识，若用户浏览所述发票表单确认无误后，可通过触发所述“确认”功能标识输入确认指令。前台终端检测到所述确认指令后， 将其发送至后台服务器。后台服务器根据所述确认指令，将所述待报销发票的详细信息保存至指定数据库中。本申请实施例当且仅当在用户确认之后，才将所述待报销发票的详细信息保存至数据库中，有效地减少了后台服务器上报销单的存量。
在步骤S206中，当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
其中，步骤S206与图1实施例中所述的步骤S104相同，具体请参见上述实施例的叙述，此处不再赘述。
作为本申请的一个优选示例，在步骤S204将所述详细信息发送至所述前台终端之后，所述报销方法还可以包括：
获取所述前台终端发送的待报销发票的原件图像；
关联及存储所述原件图像与所述详细信息。
在这里，所述发票表单上还提供了“原件上传”功能标识。若检测到用户触发所述“原件上传”功能标识时，所述前台终端打开本地相册，提示用户选取待报销发票的原件图像，并获取用户所选择的原件图像，将其发送至后台服务器。后台服务器关联所述待报销发票的详细信息和所述原件图像，然后保存至指定数据库中。本申请实施例通过关联存储待报销发票的原件图像，方便了对所述待报销发票的详细信息进行原件校验；所述待报销发票的原件图像与所述详细信息一一关联，进一步优化了后台服务器的管理、存储操作。
进一步地，基于图1提供的发票报销的方法的第一实现流程的基础上，提出本申请实施例提供的发票报销的方法的第三实现流程。
如图3所示，是本申请实施例提供的发票报销的方法的第三实现流程示意图。在本申请实施例中，所述步骤S104当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作包括：
在步骤S1041中，根据前台终端发送的报销指令生成所述待报销发票对应的审批请求。
在这里，所述报销指令由前台终端的用户触发，若检测到所述报销指令时，所述前台终端将所述报销指令和用户帐号发送至后台服务器。所述用户帐号应当理解为用户登录所述指定APP的用户凭证。服务器根据所述报销指令，生成审批请求，并将工作流流转至相应的企业领导完成对所述待报销发票的报销审批操作，从而无需用户线下审核材料，实现了在线的审批操作。
在步骤S1042中，基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令。
本申请实施例通过所述审批请求，完成企业内部领导对交易订单的审批和确认操作。在这里，所述签报审批流程的审批结果包括两种，分别为企业领导认可所述待报销发票并核定报销，和不认可所述待报销发票并拒绝报销，不认可的情况包括所述待报销发票不符合报销规则，比如待报销发票不是在有效报销时段内、待报销发票的消费类型不属于可报销项目等。因此，当企业领导认可所述待报销发票并核定报销时，签报审批流程所生成的报销执行指令为执行报销支付；当企业领导不认可所述待报销发票并拒绝报销时，签报审批流程所生成的报销执行指令为拒绝报销支付。
在步骤S1043中，若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
本申请实施例中，企业和用户需均在所述后台服务器上备案相应的交易账号。服务器接收到报销执行指令后，则获取企业交易账号以及根据用户帐号获取对应的用户交易账号，确认该待报销发票的消费金额，然后从所述企业交易账号中划出不低于消费金额的报销金额，将所述报销金额打入所述用户交易账号中。用户交易账号会在指定时间范围内收到报销金额。
本申请实施例通过联合用户及企业备案交易账号，并增设签报审批流程，实现了发票的在线报销方式，保证了报销过程的安全性，有利于杜绝违章的报销行为。
进一步地，基于图1提供的发票报销的方法的第一实现流程的基础上，提出本申请实施例提供的发票报销的方法的第四实现流程。
如图4所示，是本申请实施例提供的发票报销的方法的第四实现流程示意图。如前所述，所述税务系统接口可以实现对待报销发票的验证操作，若所述税务系统接口能返回待报销发票的详细信息时，表明所述待报销发票是真实有效的，若不能返回待报销发票的详细信息时，表明所述待报销发票是虚假无效的。
在本申请实施例中，基于图1实施例的基础上，所述发票报销的方法还可以包括：
在步骤S105中，若无法获取所述税务系统接口返回的所述基本信息对应的待报销发票的详细信息，则检测网络状态。
在本申请实施例中，所述后台服务器检测网络状态时，包括检测连网参数和检测域名状态。首先检测是否获取到连网参数，若获取连网参数失败，则生成连网参数获取失败的状态信息；若连网参数获取成功时，检测域名是否正常工作，若域名检测不通时，则生成域名不通的状态信息，若域名检测通畅时，则生成网络已连接的状态信息，确认网络是通畅的。
在步骤S106中，若所述网络状态为已连接时，生成虚假发票的提示信息，并向前台终 端发送所述提示信息。
在网络已连接的情况下，若预设的响应时间范围内无法从税务系统接口获取到待报销发票的详细信息，表明所述税务系统接口并没有就所述待报销发票返回详细信息。只有在所述待报销发票为虚假发票时，税务系统才无法识别该待报销发票，且无法获取对应的详细信息进行返回。可选地，所述响应时间范围可以为30分钟。当预设的响应时间到达后，所述后台服务器生成虚假发票的提示信息，并向所述前台终端返回所述提示信息，以使得所述前台终端向用户展示该提示信息，以及无法发起报销的提示信息。
本申请实施例通过结合与税务系统接口的交互状态以及后台服务器的网络状态，来判断所述待报销发票的真伪，生成虚假发票的提示信息，有利于提高发票报销的可靠性、杜绝违章的报销行为。
应理解，在上述实施例中，各步骤的序号的大小并不意味着执行顺序的先后，各步骤的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图5示出了本申请实施例提供的发票报销的装置的组成结构图，为了便于说明，仅示出了与本申请实施例相关的部分。
在本申请实施例中，所述发票报销的装置用于实现上述图1、图2、图3、图4实施例中所述的发票报销的方法，可以是内置于服务器的软件单元、硬件单元或者软硬件结合的单元、
参阅图5，所述发票报销的装置包括：
获取模块51，用于获取前台终端发送的待报销发票的二维码信息；
解码模块52，用于基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
调用模块53，用于调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
报销模块54，用于当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
可选地，所述报销模块54包括：
生成单元541，用于根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
审批单元542，用于基于该审批请求完成对所述待报销发票的详细信息的签报审批流 程，并根据所述签报审批流程的结果生成报销执行指令；
划款单元543，用于若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
可选地，所述装置还包括：
检测模块55，用于若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
提示模块56，用于若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
可选地，所述装置还包括：
发送模块，用于在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
存储模块，用于当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
在这里，发送模块将详细信息发送至所述前台终端，使得所述前台终端接收到所述详细信息后，按照字段格式自动录入发票表单，将对应的字段值填写进填充界面上，以向用户展示所述待报销发票的详细信息进行确认，从而避免了用户手动输入发票信息，极大地简化了用户的操作。当且仅当在用户确认之后，存储模块将所述待报销发票的详细信息保存至数据库中，从而有效地减少了服务器上报销单的存量。
进一步地，在将所述详细信息返回至所述前台终端之后，所述存储模块还可以用于：
获取所述前台终端发送的待报销发票的原件图像；
关联及存储所述原件图像与所述详细信息。
本申请实施例通过关联存储待报销发票的原件图像，实现了在报销操作时对所述待报销发票的详细信息进行原件校验；所述待报销发票的原件图像与所述详细信息一一关联，方便了对所述发票的管理、存储操作。
需要说明的是，本申请实施例中的各模块/单元可以用于实现上述方法实施例中的全部技术方案，其具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
实施例3
本实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质。该一个或多个存储有计算机可读指令的非易失性可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行实施例1中发票报销的方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中发票报销的装置中各模块/单元的功能，为避免重复，这里不再赘述。
可以理解地，一个或多个存储有计算机可读指令的非易失性可读存储介质可以包括：能够携带所述计算机可读指令的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。
实施例4
图6是本申请实施例提供的一种终端的示意图，所述终端包括但不限于服务器、移动终端。如图6所示，该实施例的终端6包括：处理器60、存储器61以及存储在所述存储器61中并可在所述处理器60上运行的计算机可读指令62。所述处理器60执行所述计算机可读指令62时实现上述发票报销的方法实施例中的步骤，例如图1所示的步骤S101至S104、图2实施例中所述的步骤S201至S206、图3实施例中所述的步骤S1041至S1043以及图4实施例中所述的步骤S101至步骤S106；或者，所述处理器60执行所述计算机可读指令62时实现上述发票报销的装置实施例中各模块/单元的功能，例如图5所示模块51至56的功能。
所称处理器60可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等，所述处理器是所述终端的控制中心，利用各种接口和线路连接整个终端的各个部分。
所述存储器61可用于存储所述计算机可读指令和/或模块，所述处理器通过运行或执行存储在所述存储器内的计算机可读指令和/或模块，以及调用存储在存储器内的数据，实现所述终端的各种功能。所述存储器可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器可以包括高速随机存取存储器，还可以包括非易失性存储器，例如硬盘、内存、插接式硬盘、智能存储卡(Smart Media  Card，SMC)、安全数字卡(Secure Digital，SD)、闪存卡(Flash Card)，至少一个磁盘存储器件、闪存器件或其他易失性固态存储器件。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种发票报销的方法，其特征在于，所述方法包括：
    获取前台终端发送的待报销发票的二维码信息；
    基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
    调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
    当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
  2. 如权利要求1所述的发票报销的方法，其特征在于，在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，所述方法还包括：
    将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
    当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
  3. 如权利要求2所述的发票报销的方法，其特征在于，在将所述详细信息发送至所述前台终端之后，所述方法还包括：
    获取所述前台终端发送的待报销发票的原件图像；
    关联及存储所述原件图像与所述详细信息。
  4. 如权利要求1至3任一项所述的发票报销的方法，其特征在于，所述当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作包括：
    根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
    基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
    若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
  5. 如权利要求1至3任一项所述的发票报销的方法，其特征在于，所述方法还包括：
    若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
    若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
  6. 一种发票报销的装置，其特征在于，所述装置包括：
    获取模块，用于获取前台终端发送的待报销发票的二维码信息；
    解码模块，用于基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
    调用模块，用于调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
    报销模块，用于当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
  7. 如权利要求6所述的发票报销的装置，其特征在于，所述装置还包括：
    发送模块，用于在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
    存储模块，用于当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
  8. 如权利要求7所述的发票报销的装置，其特征在于，所述存储模块还用于：
    获取所述前台终端发送的待报销发票的原件图像；
    关联及存储所述原件图像与所述详细信息。
  9. 如权利要求6至8任一项所述的发票报销的装置，其特征在于，所述报销模块包括：
    生成单元，用于根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
    审批单元，用于基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
    划款单元，用于若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
  10. 如权利要求6至8任一项所述的发票报销的装置，其特征在于，所述装置还包括：
    检测模块，用于若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
    提示模块，用于若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
  11. 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
    获取前台终端发送的待报销发票的二维码信息；
    基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
    调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
    当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
  12. 如权利要求11所述的非易失性可读存储介质，其特征在于，在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：
    将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
    当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
  13. 如权利要求12所述的非易失性可读存储介质，其特征在于，在将所述详细信息发送至所述前台终端之后，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：
    获取所述前台终端发送的待报销发票的原件图像；
    关联及存储所述原件图像与所述详细信息。
  14. 如权利要求11至13任一项所述的非易失性可读存储介质，其特征在于，所述当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作包括：
    根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
    基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
    若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
  15. 如权利要求11至13任一项所述的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：
    若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
    若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
  16. 一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取前台终端发送的待报销发票的二维码信息；
    基于预设的解码库解析所述二维码信息，获取所述二维码信息中记录的基本信息；
    调用税务系统接口，将所述基本信息发送至所述税务系统接口，并获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息；
    当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作。
  17. 如权利要求16所述的终端，其特征在于，在获取所述税务系统接口根据所述基本信息返回的所述待报销发票对应的详细信息之后，所述处理器执行所述计算机可读指令时还实现如下步骤：
    将所述详细信息发送至所述前台终端，以使得前台终端向用户展示所述待报销发票的详细信息；
    当获取到前台终端发送的所述待报销发票的确认指令时，将所述待报销发票的详细信息存储至数据库中。
  18. 如权利要求17所述的终端，其特征在于，在将所述详细信息发送至所述前台终端之后，所述处理器执行所述计算机可读指令时还实现如下步骤：
    获取所述前台终端发送的待报销发票的原件图像；
    关联及存储所述原件图像与所述详细信息。
  19. 如权利要求16至18任一项所述的终端，其特征在于，所述当获取到前台终端发送的报销指令时，基于所述详细信息执行对所述待报销发票的报销操作包括：
    根据前台终端发送的报销指令生成所述待报销发票对应的审批请求；
    基于该审批请求完成对所述待报销发票的详细信息的签报审批流程，并根据所述签报审批流程的结果生成报销执行指令；
    若所述报销执行指令为执行报销支付，则从企业交易账号中划出该待报销发票对应的消费金额存入用户交易账号。
  20. 如权利要求16至18任一项所述的终端，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    若无法获取所述税务系统接口返回的所述待报销发票的详细信息，则检测网络状态；
    若所述网络状态为已连接，则生成虚假发票的提示信息，并向前台终端发送所述提示信息。
PCT/CN2018/081025 2017-11-23 2018-03-29 发票报销的方法、装置、存储介质及终端 WO2019100633A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711177737.0 2017-11-23
CN201711177737.0A CN108268909A (zh) 2017-11-23 2017-11-23 发票报销的方法、装置、存储介质及终端

Publications (1)

Publication Number Publication Date
WO2019100633A1 true WO2019100633A1 (zh) 2019-05-31

Family

ID=62771708

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081025 WO2019100633A1 (zh) 2017-11-23 2018-03-29 发票报销的方法、装置、存储介质及终端

Country Status (2)

Country Link
CN (1) CN108268909A (zh)
WO (1) WO2019100633A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117474502A (zh) * 2023-12-27 2024-01-30 国网浙江省电力有限公司金华供电公司 财务数据处理方法、系统及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110738784B (zh) * 2018-07-19 2021-12-14 阿里巴巴集团控股有限公司 发票管理方法、装置、服务器和系统
CN109583827A (zh) * 2018-10-15 2019-04-05 平安科技（深圳）有限公司 发票核对方法、装置、计算机设备及存储介质
CN109685967A (zh) * 2018-12-27 2019-04-26 大象慧云信息技术有限公司 一种预防发票重复报销的系统及方法
CN110264288A (zh) * 2019-05-20 2019-09-20 深圳壹账通智能科技有限公司 基于信息识别技术的数据处理方法及相关装置
CN112597743A (zh) * 2020-12-15 2021-04-02 平安普惠企业管理有限公司 基于考勤数据的报销方法、装置、计算机设备及存储介质
CN112801765B (zh) * 2020-12-29 2024-05-03 珠海金山办公软件有限公司 报销文件的生成方法、装置、系统、电子设备及存储介质
CN113222725B (zh) * 2021-05-25 2022-08-12 支付宝(杭州)信息技术有限公司 基于区块链的数据处理方法及装置
CN113469757A (zh) * 2021-05-26 2021-10-01 杭州每刻科技有限公司 一种发票签收方法和系统
CN115996149B (zh) * 2023-01-30 2024-02-20 北京四方启点科技有限公司 一种电子报销凭证传输方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101251913A (zh) * 2008-04-10 2008-08-27 华为技术有限公司 一种自助报销管理系统及方法
CN104700169A (zh) * 2013-12-05 2015-06-10 航天信息股份有限公司 一种发票查验与管理的方法及系统
CN106504042A (zh) * 2016-10-27 2017-03-15 百望电子发票数据服务有限公司 电子发票抬头信息处理方法、开票客户端和相关设备
US20170103244A1 (en) * 2014-03-25 2017-04-13 Shenglong WU Two-dimensional code based information aquisition system and method thereof
CN107368954A (zh) * 2017-06-29 2017-11-21 苏州吉耐特信息科技有限公司 一种学校财务报销系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3179426A1 (en) * 2015-12-09 2017-06-14 ADELANTE, s.r.o. A system of electronic generation of a character sequence for a qr code image
CN106228441A (zh) * 2016-08-03 2016-12-14 北京天职信息技术有限公司西安分公司 一种基于网络的财务发票报销上传审核方法
CN107274238A (zh) * 2017-04-23 2017-10-20 西安电子科技大学 一种电子凭据服务系统及其方法
CN107368953A (zh) * 2017-06-29 2017-11-21 苏州吉耐特信息科技有限公司 一种基于app的财务报销方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101251913A (zh) * 2008-04-10 2008-08-27 华为技术有限公司 一种自助报销管理系统及方法
CN104700169A (zh) * 2013-12-05 2015-06-10 航天信息股份有限公司 一种发票查验与管理的方法及系统
US20170103244A1 (en) * 2014-03-25 2017-04-13 Shenglong WU Two-dimensional code based information aquisition system and method thereof
CN106504042A (zh) * 2016-10-27 2017-03-15 百望电子发票数据服务有限公司 电子发票抬头信息处理方法、开票客户端和相关设备
CN107368954A (zh) * 2017-06-29 2017-11-21 苏州吉耐特信息科技有限公司 一种学校财务报销系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117474502A (zh) * 2023-12-27 2024-01-30 国网浙江省电力有限公司金华供电公司 财务数据处理方法、系统及存储介质

Also Published As

Publication number Publication date
CN108268909A (zh) 2018-07-10

Similar Documents

Publication Publication Date Title
WO2019100633A1 (zh) 发票报销的方法、装置、存储介质及终端
US10182050B2 (en) Data processing based on two-dimensional code
US9390442B2 (en) Capturing of unique identifier in M-commerce transaction
US8660952B1 (en) System and method for improved remote deposit user support
CN109801051B (zh) 资源转移方法、系统、服务器和计算机可读存储介质
WO2019237718A1 (zh) 一种生成收款码的方法及扫码安全校验方法
US20140149285A1 (en) Effecting payments via mobile phones
WO2016179012A1 (en) Methods and systems for message-based bill payment
US9916486B2 (en) Method and apparatus for mobile terminal to process visual graphics code
CN104599165A (zh) 一种网络交易方法及相关设备、系统
WO2019127893A1 (zh) 一种电子签名方法、电子装置及计算机可读存储介质
US20210042150A1 (en) Method-call-chain tracking method, electronic device, and computer readable storage medium
CN109741022B (zh) 电子政务前端信息共享的方法、装置、存储介质及设备
CN107292747A (zh) 保全处理的优化方法和装置
TW202032466A (zh) 用戶年齡預測方法、裝置及設備
CN111145031A (zh) 一种保险业务定制方法、装置及系统
CN113205340A (zh) 银企直连平台的数据处理方法及相关装置
US20150170255A1 (en) Information processing apparatus, information processing method and recording medium storing information processing program
CN111275436A (zh) 一种处理信息的方法及终端
CN109816462A (zh) 一种发票信息的识别方法及装置
CN114581088A (zh) 一种用于SaaS系统的聚合支付方法、装置和系统
CN114742547A (zh) 一种互联网在线收款控制方法、装置、介质及电子设备
WO2021081704A1 (zh) 支付二维码管理方法、设备、支付系统以及存储介质
CN113239408B (zh) 电子签章系统、方法、装置、设备及存储介质
CN113792267B (zh) 一种支付机构卡面图片数字版权审核的方法和装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

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 02/10/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18881440

Country of ref document: EP

Kind code of ref document: A1